How Do I Grant Root Access To Certain Apps Using Adb

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

#3,821

I unlocked critical and regular bootloader, but I keep getting an error when trying to flash TWRP from the TWRP temp boot. Ideas?

"ERROR: 1. Failed to unpack image"

#3,822

Sorry if this has been answered, I looked through a few pages, but not the full 192 page history...

I have a Pixel 2 that I purchased from Google (so no carrier blocks) that I am unable to unlock the bootloader for.
I have tried the steps here, as well as some other steps I found around the forum, but with no luck.

Upon fresh factory reset, I can flip the OEM unlock to true.
I reboot into bootloader and attempt to run fastboot commands, but they fail with "Flashing Unlock is not allowed" error.
I boot back into the regular OS and now the OEM unlock is false and greyed out.
I must then factory reset to get the OEM unlock set to true again.

I have the latest ADB executables and have tried on my old laptop, in case USB 3.0+ was the issue.

Any help is greatly appreciated!

#3,823

Sorry if this has been answered, I looked through a few pages, but not the full 192 page history...
I have a Pixel 2 that I purchased from Google (so no carrier blocks) that I am unable to unlock the bootloader for.
I have tried the steps here, as well as some other steps I found around the forum, but with no luck.

Upon fresh factory reset, I can flip the OEM unlock to true.
I reboot into bootloader and attempt to run fastboot commands, but they fail with "Flashing Unlock is not allowed" error.
I boot back into the regular OS and now the OEM unlock is false and greyed out.
I must then factory reset to get the OEM unlock set to true again.

I have the latest ADB executables and have tried on my old laptop, in case USB 3.0+ was the issue.

Any help is greatly appreciated!

Do you have the latest platform tools? Check for updates.

#3,824

Do you have the latest platform tools? Check for updates.

when you plug in your device (before reboot to fastboot) open a terminal on your computer and type adb devices
Once entered this should trigger the handshake. a message will come up on your phone asking if you want to allow to your phone to connect. I check the "always allow" box. when I read your description it sounds like you turn on oem unlock but then immediately boot into fastboot to unlock before you've had a chance to plug the phone in and check if the computer can communicate with your phone. you did a factory reset so you could turn on oem unlock but the reset also means you need to reauthorize your device to communicate with the computer. I hope you get it.

#3,825

I recently brought a NIB Pixel 2 XL from Newegg. The phone came with a verizon sim on it but dont think it was never activated on verizon.

My Phone Infos
Android Version: 8.1.0
Android security patch level: Dec 5, 2017
Build number: OPM1.171019.011

I am hoping somebody cna give me tips on how to unlock the bootloader and root the device and flash a new kernel.

I dont have too much experience in these matters. My goal is to get to Android 10 and flash the elemental kernel. Are the instructions in the OP good enough. How do i go to android 10 once I root ? TIA

#3,826

I have written my notes here

#3,827

I recently brought a NIB Pixel 2 XL from Newegg. The phone came with a verizon sim on it but dont think it was never activated on verizon.
My Phone Infos
Android Version: 8.1.0
Android security patch level: Dec 5, 2017
Build number: OPM1.171019.011

I am hoping somebody cna give me tips on how to unlock the bootloader and root the device and flash a new kernel.

I dont have too much experience in these matters. My goal is to get to Android 10 and flash the elemental kernel. Are the instructions in the OP good enough. How do i go to android 10 once I root ? TIA

Go here https://www.verizon.com/bring-your-own-device/#checkDevice
and type in your IMEI and if it's not Verizon it will say NOT VZN. If it is Verizon then the bootloader unlock is a no go as far as I know. Hope that helps.

#3,828

Hello. I'm looking for steps to reacquire root. I was rooted on stock 10. The OTA was downloaded somehow and I had to recently reboot. I now lost root and would like to get it back. Following are the steps I believe to be the path:

1. adb reboot bootloader
2. fastboot boot (twrp.img)
3. flash factory image <-- Question: Since the OTA is installed, should I use that image or the other? I dont want to wipe... (remove -w)
4. boot
5. adb reboot booloader
6. flash twrp.zip
7. flash magisk
8. reboot and enjoy root.

Please correct any step or entire process. I used to do this stuff all the time but the past couple of years, Im way too busy to mess with my phone all the time, and, I need stable functionality for work purposes.

Thanks in advance.

#3,829

Hello. I'm looking for steps to reacquire root. I was rooted on stock 10. The OTA was downloaded somehow and I had to recently reboot. I now lost root and would like to get it back. Following are the steps I believe to be the path:
1. adb reboot bootloader
2. fastboot boot (twrp.img)
3. flash factory image <-- Question: Since the OTA is installed, should I use that image or the other? I dont want to wipe... (remove -w)
4. boot
5. adb reboot booloader
6. flash twrp.zip
7. flash magisk
8. reboot and enjoy root.

Please correct any step or entire process. I used to do this stuff all the time but the past couple of years, Im way too busy to mess with my phone all the time, and, I need stable functionality for work purposes.

Thanks in advance.

was it a verizon phone?

#3,830

Probably not as they had root before the update

#3,831

Hello. I'm looking for steps to reacquire root. I was rooted on stock 10. The OTA was downloaded somehow and I had to recently reboot. I now lost root and would like to get it back. Following are the steps I believe to be the path:
1. adb reboot bootloader
2. fastboot boot (twrp.img)
3. flash factory image <-- Question: Since the OTA is installed, should I use that image or the other? I dont want to wipe... (remove -w)
4. boot
5. adb reboot booloader
6. flash twrp.zip
7. flash magisk
8. reboot and enjoy root.

Please correct any step or entire process. I used to do this stuff all the time but the past couple of years, Im way too busy to mess with my phone all the time, and, I need stable functionality for work purposes.

Thanks in advance.

If all you want is root back, just download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk

Rename it to Magisk.-v23.0.zip, and flash it with twrp. No need to flash a new factory image.

#3,832

I am trying to root my phone and am currently on 8.1. Is the Magisk version dependent on the OS version ? TIA

#3,833

I am trying to root my phone and am currently on 8.1. Is the Magisk version dependent on the OS version ? TIA

No, not dependent. I'd stay with stable Magisk, though. Version 23.0.

#3,834

No, not dependent. I'd stay with stable Magisk, though. Version 23.0.

Thanks for your help. I think I rooted the phone. I checked it with root checker and it tells me that "Sorry! Root access is not properely installed on this device". Not sure what I am doing wrong. Is this normal or did I skip a step somewhere.

I downloaded version 23 of magisk apk.
Renamed the apk to zip and flashed it through TWRP.

#3,835

Uninstall magisk and try rooting with canary build, if all checks out then change the update channel in the app to stable for the next update.

#3,836

Thanks for your help. I think I rooted the phone. I checked it with root checker and it tells me that "Sorry! Root access is not properely installed on this device". Not sure what I am doing wrong. Is this normal or did I skip a step somewhere.
I downloaded version 23 of magisk apk.
Renamed the apk to zip and flashed it through TWRP.

Was the Magisk Manager app available after you rebooted? If not, install Magisk.apk. Open the Magisk Manager app. There are two Install buttons on the top right of the screen. To the left of the top button, it should have "Installed 23.0 (23000)". If it has "N/A", tap Install, Direct Install.

If that does not fix it, post a screenshot of the Magisk Manager app.

There are a lot of root checker apps, and I have no idea how valid they are. The way I check for root is just open a terminal and type su. That should put you at a root # prompt. The first time you will get a popup to grant root access.

#3,837

Was the Magisk Manager app available after you rebooted? If not, install Magisk.apk. Open the Magisk Manager app. There are two Install buttons on the top right of the screen. To the left of the top button, it should have "Installed 23.0 (23000)". If it has "N/A", tap Install, Direct Install.
If that does not fix it, post a screenshot of the Magisk Manager app.

There are a lot of root checker apps, and I have no idea how valid they are. The way I check for root is just open a terminal and type su. That should put you at a root # prompt. The first time you will get a popup to grant root access.

Looks like I did not reboot after I installed Magisk. After the reboot the root shows up. thx for your help.

#3,838

Uninstall magisk and try rooting with canary build, if all checks out then change the update channel in the app to stable for the next update.

Looks like I did not reboot after I installed Magisk. After the reboot the root shows up.

#3,839

I'm trying to root a new Pixel 2 XL. By mistake I first flashed unlock_critical before the regular unlock. The bootloader is unlocked but when I try to install the latest Lineage using booted TWRP I get the following error, "Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)". is this caused by the unlocking error? If so, how can I correct it? Thanks.

#3,840

I'm trying to root a new Pixel 2 XL. By mistake I first flashed unlock_critical before the regular unlock. The bootloader is unlocked but when I try to install the latest Lineage using booted TWRP I get the following error, "Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)". is this caused by the unlocking error? If so, how can I correct it? Thanks.

It turns out the most recent TWRP version was the cause. Version 3.3.0 was able to install without errors,

Similar threads