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
Related
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.
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 :|
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Badger50 said:
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Click to expand...
Click to collapse
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Badger50 said:
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Click to expand...
Click to collapse
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
ryanispd said:
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
Click to expand...
Click to collapse
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Badger50 said:
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Click to expand...
Click to collapse
I checked via verizon's imei checker (https://www.verizonwireless.com/prospect/bring-your-own-device#/checkDevice)
looks like it isn't actually a verizon model, I'm in luck I guess.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
It will not relock. I am 100 percent sure. There are several reasons it wont. One is that relock will wipe your data, can you imagine the lawsuits if Google and Verizon send an update that they knew would wipe your data.
The second reason is that it is technologically impossible. You are thinking of when a VZ update breaks root o other phones. This phone is way different. It won't happen.
Relax, update.
You will lose root when you update. Easy enough to restore though.
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
I also have a Verizon phone that randomly let me unlock the bootloader. I was running DU and just flashed the OTA in TWRP. Booted right up. No issues with it relocking the bootloader or any other nonsense.
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Google has implemented a rollback prevention system on their devices. You cannot install an earlier version of Android over a later one. Attempting to do so generates an error message and the device will not boot. I believe this applies regardless of the lock status of the bootloader, but I'm sure someone more knowledgeable will chime in.
Sell your device on Swappa. Then purchase an unlocked model off Swappa, if available. No sane person is going to trade their unlockable device for your Verizon model.
if you unlock the bootloader, and wipe the device, you can downgrade to any version that google has published for the device.
If you do NOT unlock the bootloader, it is not possible.
@uicrnen: He has a Verizon device, so he can't unlock it.
Strephon Alkhalikoi said:
@uicrnen: He has a Verizon device, so he can't unlock it.
Click to expand...
Click to collapse
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
uicnren said:
correct, therefore they cannot downgrade.
If they had an unlockable version of the phone, they could downgrade, should they desire to.
Click to expand...
Click to collapse
Which is why I gave your post a thumbs up. Rollback protection then is similar to Factory Reset Protection in this regard. So long as OEM Unlocking is enabled in developer options and the bootloader unlocked, neither will kick in.
uicnren said:
if you unlock the bootloader
Click to expand...
Click to collapse
Please can you recommend the safest/most reliable way to accomplish this.
uicnren said:
...and wipe the device, you can downgrade to any version that google has published for the device.
Click to expand...
Click to collapse
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
IconBoy said:
Please can you recommend the safest/most reliable way to accomplish this.
Once I do this, I presume I can then relock the bootloader...?
I am finding that I prefer Oreo over Pie and my Pixel 2 XL has to be restarted more regularly than when I was on Oreo. Sigh....
I'm happy having a non-rooted device as my biggest peeve is the ads, so use DNS66 to block ads successfully.
Plus, I want to be able to use Google Pay and (Barclays) banking apps. Barclays mobile app doesn't show up in USA Google Play Store but does once you install it from APK. (Had a UK friend send me the APK. Seriously banks, do you think only folks from your country have accounts? ?).
Over the years I have frequently rooted from the get-go but am enjoying being able to update OTA and have Google Pay work seamlessly.
Most apps I use that are beneficial use the ADB Write Settings commands now which accomplish what rooted device did. Wish Titanium Backup could do this with ADB Write command.
Thanks for any help.
Click to expand...
Click to collapse
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
1. BACKUP. Save anything you deem important, as your device will be erased.
1a. Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts.
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images ***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Worth mentioning to him if he's on Verizon, it isn't gonna work.
Upgraded anyway. Handful of issues but not enough to regret it. I do regret buying through Verizon though...
forwardthinking said:
Verizon phone, hate my life.
Haven't upgraded yet but worried my stuff will stop working, and I'll be stuck. Sorry if this is covered elsewhere, I searched.
Alternative solution anyone want to trade for your unlocked phone? :crying:
Click to expand...
Click to collapse
Sell it on swappa ms buy what you want.
uicnren said:
Assuming you have a Pixel 2 XL, which the bootloader is unlockable:
Click to expand...
Click to collapse
Unlocked Pixel 2 XL bought from Google Store.
uicnren said:
Be sure you have the latest adb/fastboot installed/working, available from: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Will 15 Second ADB be sufficient, as I've always had success with that...?
Hopefully the ADB Fastboot file from Android Developer I can unzip and copy the updated contents to 15 Second ADB as their batch file installs system wide which is so helpful.
uicnren said:
2. Enable developer options. Settings > System > About then tap on build number 7 times, follow prompts
Click to expand...
Click to collapse
Done that already. :good:
uicnren said:
3. Settings > System > Advanced > either enable or make sure that 'OEM unlocking' is enabled.
4. Download (the version you wish to install) and follow ALL instructions from: https://developers.google.com/android/images
Click to expand...
Click to collapse
As my device is unlocked and not specific to any carrier, am I correct in choosing the sixth from bottom from the list:
Taimen 8.1.0 (OPM2.171026.006.H1, Jul 2018)?
uicnren said:
***this includes performing BOTH fastboot flasshing unlock AND fastboot flashing unlock_critical***
Thats all there is to it.
Click to expand...
Click to collapse
Duly noted!
uicnren said:
After doing above, re-enable developer options and again make sure to re-enable OEM unlocking. Be sure to do this BEFORE re-locking the bootloader.
Click to expand...
Click to collapse
Once the device first boots from doing all this, is it okay if I skip all the Google account setup and just enable Developer Options and enable OEM unlock?
uicnren said:
If you wish to re-lock the bootloader, be 100% certain that you are completely stock ROM. There have been issues (sometimes catastrophic) when re-locking the bootloader when the device is not 100% stock.
Click to expand...
Click to collapse
So the file I chose from the Android Developers Images page above, would be 100% stock?...and I can just go ahead and relock bootloader?
Should I factory reset after bootloader is relocked?
Thank you for clarifying the steps.
Hey guys, I have a Pixel 3 XL that I am trying to repair because it's touchscreen doesn't work, however while doing the repair I found that it does not have the correct firmware and I cannot install the correct one. When in fastboot mode, it shows the product revision as "crosshatch MP1.0(ROW)" however when I go to recovery, at the top it says: "google/blueline/blueline" . I can only flash Pixel 3(blueline) firmware to it through adb sideload since the bootloader is locked. When I try to flash crosshatch firmware through adb sideload it makes it about 50% before failing due to inaccurate signature. Does anyone know how I can correctly return it's firmware to crosshatch. The touchscreen doesn't work due to I assume it having the wrong firmware. Any help is appreciated thanks .
Try unlocking bootloader first and clean up everything that is data and system and reboot back to bootloader and use flash-all script from the rim downloaded and let us know what happened.
lingarajug said:
Try unlocking bootloader first and clean up everything that is data and system and reboot back to bootloader and use flash-all script from the rim downloaded and let us know what happened.
Click to expand...
Click to collapse
Unfortunately I have no way to unlock the bootloader since the touchscreen doesn't work. I've been flashing through adb sideload as flash-all wasn't available to me due to the locked bootloader.
unifiedEthan said:
Unfortunately I have no way to unlock the bootloader since the touchscreen doesn't work. I've been flashing through adb sideload as flash-all wasn't available to me due to the locked bootloader.
Click to expand...
Click to collapse
Just a question why do you need a functioning digitizer to access or interact with the bootloader? Volume buttons are used to cycle through options and the power button confirms the highlighted option in both low level modes.
RagedElimanator said:
Just a question why do you need a functioning digitizer to access or interact with the bootloader? Volume buttons are used to cycle through options and the power button confirms the highlighted option in both low level modes.
Click to expand...
Click to collapse
Need to toggle it in dev options I think. I guess you could attach a pointer device?
wangdaning said:
Need to toggle it in dev options I think. I guess you could attach a pointer device?
Click to expand...
Click to collapse
Ah so you have access to the Android system locally, then if you could try attaching a mouse that should reverse the current situation you are in.
RagedElimanator said:
Ah so you have access to the Android system locally, then if you could try attaching a mouse that should reverse the current situation you are in.
Click to expand...
Click to collapse
I attached a mouse and was able to navigate around, however I am still not able to unlock the bootloader and the Pixel 3 OS crashes a lot on the Pixel 3 XL.
RagedElimanator said:
Ah so you have access to the Android system locally, then if you could try attaching a mouse that should reverse the current situation you are in.
Click to expand...
Click to collapse
I attached a mouse and was able to navigate around, however I am still not able to unlock the bootloader and the Pixel 3 OS crashes a lot on the Pixel 3 XL.
unifiedEthan said:
I attached a mouse and was able to navigate around, however I am still not able to unlock the bootloader and the Pixel 3 OS crashes a lot on the Pixel 3 XL.
Click to expand...
Click to collapse
Just out of curiosity where did you get this device?
RagedElimanator said:
Just out of curiosity where did you get this device?
Click to expand...
Click to collapse
I work at a tech repair site that buys phones and sells them online refurbished. I do software repair there and came across this phone while working there and it has me stumped. I think it might just be bad.
unifiedEthan said:
I work at a tech repair site that buys phones and sells them online refurbished. I do software repair there and came across this phone while working there and it has me stumped. I think it might just be bad.
Click to expand...
Click to collapse
Well if there is any chance you go flash the bootloader separately via fastboot try that. If that is successful then maybe the flash-all script could work
May be power off phone and hold volume down and connect to PC with cable and it should directly go to bootloader, make sure to download Google Android tools before hand and cmd to that folder and then u can unlock bootloader, let us know.
www.frpunlocked.com