I have installed the adb drivers and it recognized my device and installed drivers. I have enabled debugging. I use the commands for dpixel8. adb push dePixel8 /data/local/tmp
adb shell chmod 755 /data/local/tmp/dePixel8
adb shell /data/local/tmp/dePixel8
It reboots the device but does not reboot into bootloader as it is suppose to. It just reboots into normal mode. Any suggestions. Please give me a step by step on how to unlock and root my phone. Thanks
You have to tick that OEM unlock thing under Dev settings where you enabled debugging. And the command to reboot in bootloader is adb reboot bootloader!
PS: Sorry never mind.
ithehappy said:
You have to tick that OEM unlock thing under Dev settings where you enabled debugging. And the command to reboot in bootloader is adb reboot bootloader!
Click to expand...
Click to collapse
No he does not. He clearly just stated he's using depixel8 which means he's on a vzw pixel. Which means no switching on OEM unlock. Hence using depixel8.
Have you tried doing it a second time.
I take it you're not on 7.1.1 though?
toknitup420 said:
No he does not. He clearly just stated he's using depixel8 which means he's on a vzw pixel. Which means no switching on OEM unlock. Hence using depixel8.
Have you tried doing it a second time.
Click to expand...
Click to collapse
Yes. I have tried it several times. It keeps telling me it did not work please try again.
DaveHTC200 said:
I take it you're not on 7.1.1 though?
Click to expand...
Click to collapse
Yes. It is 7.1.1. I am wondering if google came out with another security update to counter dpixel8
mewilson666 said:
Yes. I have tried it several times. It keeps telling me it did not work please try again.
Click to expand...
Click to collapse
Are you on 7.1.1???
mewilson666 said:
Yes. It is 7.1.1. I am wondering if google came out with another security update to counter dpixel8
Click to expand...
Click to collapse
depixel8 can not unlock the bootloader of a Verizon Pixel once 7.1.1 is flashed onto it, either at the factory or by the update.
Downgrading to 7.1 will not restore the bootloader to the one that depixel8 can exploit.
aholeinthewor1d said:
Are you on 7.1.1???
Click to expand...
Click to collapse
Yes I am on 7.7.1
pTeronaut said:
depixel8 can not unlock the bootloader of a Verizon Pixel once 7.1.1 is flashed onto it, either at the factory or by the update.
Downgrading to 7.1 will not restore the bootloader to the one that depixel8 can exploit.
Click to expand...
Click to collapse
Anyone or anything that can?
mewilson666 said:
Yes I am on 7.7.1
Click to expand...
Click to collapse
That would explain it. You can't unlock your bootloader now. The exploit dePixel8 uses was patched with the 7.1.1 update.
mewilson666 said:
Anyone or anything that can?
Click to expand...
Click to collapse
At this moment in time, nothing can unlock the bootloader of a Verizon sold Pixel once 7.1.1 is flashed onto it.
If there was, or will be, you can bet that there will be a thread on XDA about it.
pTeronaut said:
At this moment in time, nothing can unlock the bootloader of a Verizon sold Pixel once 7.1.1 is flashed onto it.
If there was, or will be, you can bet that there will be a thread on XDA about it.
Click to expand...
Click to collapse
Not what I wanted to hear. Haha. Anybody know how I can change the font size? I can not see that little stuff
mewilson666 said:
Not what I wanted to hear. Haha. Anybody know how I can change the font size? I can not see that little stuff
Click to expand...
Click to collapse
Settings - Display - Text size
quangtran1 said:
Settings - Display - Text size
Click to expand...
Click to collapse
Haha Duh! Thanks
mewilson666 said:
Haha Duh! Thanks
Click to expand...
Click to collapse
LOL.
Related
So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
SomeFknGuy said:
So, I was installing ADB and such with android toolkit, It rebooted my phone into FASTBOOT in order to check the status of bootloader. Got the info I needed, then the phone rebooted, I went to download depixel8 and get ready to unlock and start the root shenanigans...and boom. The phone installs the NMF26U update without me even telling it to/letting it. Am I completely screwed on here as far as now being able to root and unlock my phone?
Click to expand...
Click to collapse
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
k.s.deviate said:
The toolkit updated your phone, or your phone took an ota? The toolkit should not have been able to update if you weren't already unlocked. Unless there's something I'm missing here..
Click to expand...
Click to collapse
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
SomeFknGuy said:
The OTA update notification was there, but I've been avoiding and ignoring it. When ADB/Toolkit rebooted my phone to check the status of the bootloader all was good, the second my phone rebooted from all that the notification bar showed that it was finishing the update. Went into the settings window to check the build version and it is now showing 7.1.1 and NMF26U. I'm without a solid hotspot work around now since foxfi is dead and I'm too lazy to pull my phone case constantly to remove and replace the sim heh. Just wondering what toolkit triggered to allow and instigate the update install
Click to expand...
Click to collapse
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
k.s.deviate said:
I'm pretty sure the ota automatically downloads, when the toolkit rebooted the device it finished the install. If your device is Verizon then yes I think you're boned.
Click to expand...
Click to collapse
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
There is. "fastboot --set-active=_a" (or _b). Here is a list of all known fastboot commands. https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-fastboot-commands-t3490080
mikaole said:
Is there no way to change the boot slot? Old system is still on the now not active bootslot.
So my question is there a way to change the bootslot without twrp.
Click to expand...
Click to collapse
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
imnuts said:
Isn't the old system partition updated in the background then after the update is complete? Even if it isn't, the radio and bootloader are still updated.
Sent from my Pixel XL
Click to expand...
Click to collapse
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Sent from my Pixel XL using Tapatalk
superchilpil said:
Nope, they aren't updated until a new update comes. Also there are two slots for radio and bootloader just like everything else so in theory if he could use fastboot he could switch boot slots.
Click to expand...
Click to collapse
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
aholeinthewor1d said:
Unfortunately this won't help. If he installed the update his bootloader is now locked and there is no way to unlock it.
Click to expand...
Click to collapse
I sry to say..but I completely agree. If your on 7.1.1 and still locked your stuck locked.
SomeFknGuy said:
oy... i was afraid of that... maybe someone can find a work around to at least get my hot spot working...
Click to expand...
Click to collapse
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
No there is a way past this it happened to me, @jcase knows the command you need to get by this.
mwalt201 said:
Pop the sim card, push it back in, wait 4 seconds, turn on hotspot.
Click to expand...
Click to collapse
actually been doing just this. just a little bit of a pain to do with the cover that I'm running. worth it though, until verizon figures out a fix for that :|
Received the set from friend, seeking for help on 7.1.1 january 2017 frp unlock. tried all the way on google but stuck at the stage that cannot disabled google account manager 7.1.1 (com.google.android.gsf..login). Think google had disabled this on latest update? Anyway to unlock it or downgrade to 7.1?
Set is bootloader LOCKED. I can't even enable the USB Debug to unlock it.
kelvin_ngu said:
Received the set from friend, seeking for help on 7.1.1 january 2017 frp unlock. tried all the way on google but stuck at the stage that cannot disabled google account manager 7.1.1 (com.google.android.gsf..login). Think google had disabled this on latest update? Anyway to unlock it or downgrade to 7.1?
Set is bootloader LOCKED. I can't even enable the USB Debug to unlock it.
Click to expand...
Click to collapse
Simple answer is: no.
Since you received it from a friend, ask him to login on the phone and remove his Google account. Problem solved... :good:
Good luck...
Yes, you need them to remove it first. Pretty easy when you know the person, very hard when you buy a phone from a third party.
google it
there are ways to unlock it with adb
flex360 said:
google it
there are ways to unlock it with adb
Click to expand...
Click to collapse
Without root?
bobby janow said:
Without root?
Click to expand...
Click to collapse
yes you need to flash a zip that enables adb then you can run the adb commands while the phone is on the setup screen
i did that for a galaxy phone just a week ago
if he is your friend why dont you ask him
unless you stole it
flex360 said:
if he is your friend why dont you ask him
unless you stole it
Click to expand...
Click to collapse
Ouch!
flex360 said:
yes you need to flash a zip that enables adb then you can run the adb commands while the phone is on the setup screen
i did that for a galaxy phone just a week ago
Click to expand...
Click to collapse
Can you post the link sir? TQ
flex360 said:
if he is your friend why dont you ask him
unless you stole it
Click to expand...
Click to collapse
As I mention, is from a friend asking for "help". If he knows the login, he won't look for me. I donno where he got it and is not me who "Stole it"
flex360 said:
yes you need to flash a zip that enables adb then you can run the adb commands while the phone is on the setup screen
i did that for a galaxy phone just a week ago
Click to expand...
Click to collapse
Now I'm curious..I just bought the pixel XL yesterday from Verizon.. Of course it got the OTA update of the latest March patch
Sent from my Pixel XL using Tapatalk
Frp Google pixel
Can any one help me i have frp on my phone google pixel patch 5.march.2017
flex360 said:
yes you need to flash a zip that enables adb then you can run the adb commands while the phone is on the setup screen
i did that for a galaxy phone just a week ago
Click to expand...
Click to collapse
That method only works on Samsung phones, it requires flashing a engineering boot.img which will in turn enable USB Debugging, allowing you to run the necessary adb commands. Only some Samsung phones have a engineering boot.img to flash.
The other is booting into Maintenance Boot Mode (not all Samsung phones have it) and turning on USB Debugging, and again, running the proper adb commands once booted.
-----------------
When the dirtycow exploit was patched with the December 2016 security update, removing FRP from a Pixel/XL became impossible, at least for the time being.
At the end of the day, just get your friend to login to the phone again, and FRP will be removed. :good:
i need how its work
flex360 said:
yes you need to flash a zip that enables adb then you can run the adb commands while the phone is on the setup screen
i did that for a galaxy phone just a week ago
Click to expand...
Click to collapse
sir i need how its work i have pixel January 5 2017 security patch
Just a thought, has anyone tried this? Just curious.
I don't believe there are any devs working on it since the last update that patched the "Depixel8" software. Seems they've given up on the VZW variant. There is a bounty somewhere in these forums. For both bootloader unlock exploit and temp root to flash TWRP and hopefully SuperSU. But I don't know if anyone is trying or what.
Bunch of quitters. lol
I have it works perfectly
ASwedishDragon said:
I have it works perfectly
Click to expand...
Click to collapse
You have what?
toknitup420 said:
You have what?
Click to expand...
Click to collapse
I don't even know why I posted that comment, I'm running 7.1.2. Just ignore the comment
jfishbone311 said:
Bunch of quitters. lol
Click to expand...
Click to collapse
Let's you try unlocking and temp root it.
awakenedwithin said:
Let's you try unlocking and temp root it.
Click to expand...
Click to collapse
I am.
mattwheat said:
I don't believe there are any devs working on it since the last update that patched the "Depixel8" software. Seems they've given up on the VZW variant. There is a bounty somewhere in these forums. For both bootloader unlock exploit and temp root to flash TWRP and hopefully SuperSU. But I don't know if anyone is trying or what.
Click to expand...
Click to collapse
Honestly what is in it for the devs to find another exploit, just for it to be patched again, especially that there is an unlocked model of the phone. If they all were locked down, most likely they would try. Honestly just sell the VZW Version and buy the GPE. It is still locked on O, while being TMO.
I have a Pixel 2xl which is factory unlocked, not Verizon unlocked. In order to root it, i believe that i first have to relock the bootloader. I haven't been able to root it, and i believe that this is why. Any info to resolve this issue would be greatly appreciated. Thanks.
grunt0300 said:
I have a Pixel 2xl which is factory unlocked, not Verizon unlocked. In order to root it, i believe that i first have to relock the bootloader. I haven't been able to root it, and i believe that this is why. Any info to resolve this issue would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
No, you do not need to lock the bootloader, and wouldn't recommend it as well! You'll need to install platform-tools on your pc, the twrp.img in your platform-tools folder, the twrp installation zip and magisk on your phone. Then fastboot into twrp, swipe to allow modifications, then flash the twrp installer.zip, then flash the magisk.zip, then boot up and you should have root :good:
Badger50 said:
No, you do not need to lock the bootloader, and wouldn't recommend it as well! You'll need to install platform-tools on your pc, the twrp.img in your platform-tools folder, the twrp installation zip and magisk on your phone. Then fastboot into twrp, swipe to allow modifications, then flash the twrp installer.zip, then flash the magisk.zip, then boot up and you should have root :good:
Click to expand...
Click to collapse
I've got it set up, but how do i "fastboot into twrp"? I can get into fastboot mode, but where is twrp? Sorry, but i'm getting confused.
grunt0300 said:
I've got it set up, but how do i "fastboot into twrp"? I can get into fastboot mode, but where is twrp? Sorry, but i'm getting confused.
Click to expand...
Click to collapse
I think you would do well to read and study this guide for a little bit, then you'll have a better understanding of what to do :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Badger50 said:
I think you would do well to read and study this guide for a little bit, then you'll have a better understanding of what to do :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
Read the guide, studied the guide. Six hours later, i still can't root this phone. I'm done.
grunt0300 said:
Read the guide, studied the guide. Six hours later, i still can't root this phone. I'm done.
Click to expand...
Click to collapse
Where are you getting stuck at??
grunt0300 said:
Read the guide, studied the guide. Six hours later, i still can't root this phone. I'm done.
Click to expand...
Click to collapse
Don't give up until you try this, I was not able to unlock my Bootloader with fastboot, but the deuces method works. :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Droid_Nut said:
Don't give up until you try this, I was not able to unlock my Bootloader with fastboot, but the deuces method works. :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
My bootloader is unlocked. That's the problem. If i lock it, then follow the unlocking procedure, everything may work.
grunt0300 said:
My bootloader is unlocked. That's the problem. If i lock it, then follow the unlocking procedure, everything may work.
Click to expand...
Click to collapse
Again, where are you getting stuck at??
Fastbooting twrp??
Phone/pc communication??
Platform-tools up to date??
Tried different 2.0 USB A to USB C cables and ports?
grunt0300 said:
My bootloader is unlocked. That's the problem. If i lock it, then follow the unlocking procedure, everything may work.
Click to expand...
Click to collapse
The title of your thread, led me to believe you wanted to unlock the bootloader, and it was only carrier unlocked?
Actually when I rooted mine, Magisk said it was not rooted, after a reboot it was showing root? Maybe something quirky in Magisk? You may have root, but Magisk is not properly reporting it?
Badger50 said:
Again, where are you getting stuck at??
Fastbooting twrp??
Phone/pc communication??
Platform-tools up to date??
Tried different 2.0 USB A to USB C cables and ports?
Click to expand...
Click to collapse
Not stuck any more. Locked the bootloader, and i'm done. No root, no worries. Maybe someday, in a galaxy far, far away, i'll try again. For now, i'll stay unrooted and keep my sanity. Thanks for trying to help.
grunt0300 said:
Not stuck any more. Locked the bootloader, and i'm done. No root, no worries. Maybe someday, in a galaxy far, far away, i'll try again. For now, i'll stay unrooted and keep my sanity. Thanks for trying to help.
Click to expand...
Click to collapse
Happy trails then my friend. However, if your feeling adventurous in the future, look me up. Bet we could get that sucker rooted! :good::laugh:
So I have determined my Pixel unfortunately has the Verizon brand and can't unlock the bootloader. When I bought it Android 11 was installed and I would still like to take it back to Android 10. According to what I read I can sideload, I think the term is, an OTA image without unlocking the bootloader. Is that correct brfore I think about trying? My blink light is intermittent and the weather widget doesn't work, figured maybe if I backed up I could have better success. Thanks....
Yes. Sideloading an OTA update should work regardless of the lock status of the bootloader as the package is signed by Google.
Strephon Alkhalikoi said:
Yes. Sideloading an OTA update should work regardless of the lock status of the bootloader as the package is signed by Google.
Click to expand...
Click to collapse
OK thanks for reaffirming that for me. If I get enough nerve to try this I will give it a shot, if it doesn't go well is there a way to back out to the present status of Android 11?
bcsman said:
OK thanks for reaffirming that for me. If I get enough nerve to try this I will give it a shot, if it doesn't go well is there a way to back out to the present status of Android 11?
Click to expand...
Click to collapse
There are ways. Unfortunately I don't know if the locked bootloader will stymie those ways.
Strephon Alkhalikoi said:
There are ways. Unfortunately I don't know if the locked bootloader will stymie those ways.
Click to expand...
Click to collapse
Yes kind of figured as much....