Develop Bugs

Trying to unlock Google Pixel XL

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.

[Q] Safe to relock bootloader via fastboot? No custom kernels / ROMs

[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?

burnface said:
[SOLVED] I followed this thread to get everything updated and make sure I was all stock, and then went to bootloader and ran fastboot flashing lock to relock the bootloader. Everything working great now.
I'm trading my Verizon Pixel XL for a normal Pixel, and need to relock the bootloader first. I haven't installed a custom kernal or ROMs or anything, so can I just lock via fastboot safely?
I don't want to do something that will brick it!
I'm aware this is stupid and I'd rather just leave it, but dude is sketched out by warning on startup and won't trade till it's gone :/
Thanks!
[Edit] it should maybe be noted that I haven't installed any updates since rooting, and I'm not sure if those are important first or not?
Click to expand...
Click to collapse
Hey man, do you remember which FW built were you on ? NDE63X ?

andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.

milan187 said:
Yes if you are stock you can safely lock the bootloader.
run
fastboot flashing lock
phone will factory reset and appear frozen on that screen 30seconds or so.
Click to expand...
Click to collapse
Cool man, thanks!

andrep182 said:
Hey man, do you remember which FW built were you on ? NDE63X ?
Click to expand...
Click to collapse
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!

burnface said:
Damn. I honestly don't remember... I didn't do enough with that phone for anything specific to stick out.. Sorry!
Click to expand...
Click to collapse
It's all good man. My heart was pounding as I about to hit 'yes' for locking my bootloader. Did the deed and all is well =) Thanks!

just flash twrp . lost fastboot

just got my pixel xl today. unlocked the bootloader fine.
next step flash twrp. i fastboot boot twrp img. temp twrp , installed the zip.. i reboot to recovery. that where everything F up.. now i can not get into fastboot.. is there a way for me to get fastboot mode back ??

never mind just had to reboot the phone 3 times..

Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!

sytayeth said:
Hello. I think I am near you. I was on the latest stock 7.1.2 of may. Unlocked bootloader ok. Then boot the TWRP and flash the TWRP zip. After that I have bootloop all time. I can put the phone in bootloader but now my phone is not recognised by the computer. The first time I connected the phone he asked me what to do and I said transfers data. But now I cannot do anything.
How did you get in fastboot mode???
Any idea how to help me???
I really appreciate help!!
Click to expand...
Click to collapse
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...

5.1 said:
Hello,
You need to read this post: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
The thread contains a zip (verified boot signer v2 zip) that you must install right after you install the TWRP zip on latest May version...
This is weird your phone is not recognized while in bootloader.
Boot the bootloader and issue:
fastboot devices
Does it output your serial number in the command prompt?
Good luck...
Click to expand...
Click to collapse
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.

sytayeth said:
Thank for your answer. The real problem was that in fastboot the phone is not recognised. There were no serial number. And I write in past because I could made it work.
I am very happy you worried about me. You have a new friend in Spain.
Thanks.
Click to expand...
Click to collapse
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...

5.1 said:
Hey,
No problem. Glad you solved it by yourself anyway. What was the issue? Maybe others with the same problem could benefit from your experience?
Why your computer didn't recognized your phone while in bootloader?
Cheers...
Click to expand...
Click to collapse
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!

sytayeth said:
I really don't know the problem. I was just about to cry when I saw a post about skipsoft toolkit. And I thought why not to try. I installed that software in other pc, follow the instructions and now I am here again.
Yesssss!!!!
Click to expand...
Click to collapse
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.

toknitup420 said:
You shouldn't be modding you're device if you have to rely on a toolkit to save you. What if there wasn't a toolkit. You'd be SOL.
I highly recommend you learn how to use fastboot and adb, and do this stuff the right way. I'm not trying to be mean or anything. I just would hate to see you brick you're device. These pixel phones cost way too much to be screwing around with if you don't know what you're doing.
Click to expand...
Click to collapse
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.

sytayeth said:
Thanks. I am trying to learn. Not only fastboot or adb. English too. But sometimes I am a bit risky or only stupid.
By the way, recommend me a post or a place to learn.
Click to expand...
Click to collapse
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

toknitup420 said:
Honestly the best way I found to learn adb and fastboot is YouTube. It's so much easier to watch how to do it. Thats how I learned. There's also @Heisenberg 6p guide. That can get you all setup for adb and fastboot too. It's very comprehensive.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks. I'll try.

Pixel 2xl Can't Find Valid Operating System.

I've tried to lock the bootloader. But after locking the bootloader the phone restarts and shows the message that Can't Find Valid Operating System.
In FastBoot Mode it shows:
Secure Boot -Yes
Device State - Locked
My Bootloader Version - TMZ20k
Baseband Version - g8998-00253-1809191716
What's the solution?

Hope you didn't try to lock the bootloader without being fully stock...
If so, you've just bricked your phone.
If you're fully stock, you can bootloader unlock the phone again and start over.

ilal2ielli said:
Hope you didn't try to lock the bootloader without being fully stock...
If so, you've just bricked your phone.
If you're fully stock, you can bootloader unlock the phone again and start over.
Click to expand...
Click to collapse
The phone was in full stock.
I didn't changed any rom.
How can I unlock the phone again and start over?

msnahad98 said:
The phone was in full stock.
I didn't changed any rom.
How can I unlock the phone again and start over?
Click to expand...
Click to collapse
does your computer recognize your phone?
if so make sure you have up to date adb/fastboot
boot into bootloader then open command prompt
type fastboot flashing_unlock
why did you relock your bootloader?
maybe try deuce's script or the all in one tool. They're pretty handy

Edmontonchef said:
does your computer recognize your phone?
if so make sure you have up to date adb/fastboot
boot into bootloader then open command prompt
type fastboot flashing_unlock
why did you relock your bootloader?
maybe try deuce's script or the all in one tool. They're pretty handy
Click to expand...
Click to collapse
Yes My Computer recognize my phone.
After entering this command "fastboot flashing unlock"
It Shows:
FAILED (remote: 'Flashing Unlock is not allowed')

Have you tried adb sideloading an ota file?
If that doesn't work I'm not sure what else you can do.

msnahad98 said:
I've tried to lock the bootloader. But after locking the bootloader the phone restarts and shows the message that Can't Find Valid Operating System.
In FastBoot Mode it shows:
Secure Boot -Yes
Device State - Locked
My Bootloader Version - TMZ20k
Baseband Version - g8998-00253-1809191716
What's the solution?
Click to expand...
Click to collapse
By chance did you turn off OEM unlocking and USB debugging before you locked the bootloader? If so, it's......Brickhouse time! :fingers-crossed:

Badger50 said:
By chance did you turn off OEM unlocking and USB debugging before you locked the bootloader? If so, it's......Brickhouse time! :fingers-crossed:
Click to expand...
Click to collapse
Yes unfortunately I've turned off OEM unlocking and USB debugging before locking the bootloader.
Isn't there any kind of solution???:crying:

If you're under warranty you can return it.

Edmontonchef said:
If you're under warranty you can return it.
Click to expand...
Click to collapse
I don't have any warranty.

msnahad98 said:
Yes unfortunately I've turned off OEM unlocking and USB debugging before locking the bootloader.
Isn't there any kind of solution???:crying:
Click to expand...
Click to collapse
msnahad98 said:
I don't have any warranty.
Click to expand...
Click to collapse
You could try sideloading the OTA through stock recovery like @Edmontonchef suggested. I don't think it'll work, but at this point, anything is worth a try.

Could somebody PLEASE sticky a warning on every section to NOT RELOCK BOOTLOADER?? Pretty please??

CyberpodS2 said:
Could somebody PLEASE sticky a warning on every section to NOT RELOCK BOOTLOADER?? Pretty please??
Click to expand...
Click to collapse
While that would be nice my friend, I also think that there is enough information out there already that if users were willing to search for it, they would find out quickly that this is a no no. Unless of course, it's done in the correct manner. :fingers-crossed:

Why did you relock the bootloader? What advantage did you expect to gain from that?

CyberpodS2 said:
Could somebody PLEASE sticky a warning on every section to NOT RELOCK BOOTLOADER?? Pretty please??
Click to expand...
Click to collapse
Badger50 said:
While that would be nice my friend, I also think that there is enough information out there already that if users were willing to search for it, they would find out quickly that this is a no no. Unless of course, it's done in the correct manner. :fingers-crossed:
Click to expand...
Click to collapse
You mean, put THAT sticky right next to the sticky that states, SEARCH FIRST, or the one that states "generic questions belong in the Q&A section for each device"?
Edited out of compassion

Az Biker said:
You mean, put THAT sticky right next to the sticky that states, SEARCH FIRST?
Or next to the sticky that states "generic questions belong in the Q&A section for each device"?
Or any of the other 100s of stickies that the vast majority never read?
Those stickies?
I'm actually AMAZED at the "right now, immediate gratification" mentality of so many people nowadays.
I have this $800+ device, I want to customize it, what should I do first?
1) read the OPs and research the guides for my device PRIOR to messing with it,
or
2) skip all the research and OPs and flash my new device the way I flashed my Note 3 from five years ago?
Who in their ever loving right mind picks 2??????
Click to expand...
Click to collapse
Amen by brother! No truer words have ever been spoken! :good:

Badger50 said:
Amen by brother! No truer words have ever been spoken! :good:
Click to expand...
Click to collapse
I feel bad for new members like the OP. No doubt this will be a learning moment for him, and he seems sharp enough that I think he'll be okay down the road and will do the research needed before customizing his devices.
The members who have been with Xda for years and STILL don't research, read OPs, read stickies.... those are the folks who chap my hide

Az Biker said:
I feel bad for new members like the OP. No doubt this will be a learning moment for him, and he seems sharp enough that I think he'll be okay down the road and will do the research needed before customizing his devices.
The members who have been with Xda for years and STILL don't research, read OPs, read stickies.... those are the folks who chap my hide
Click to expand...
Click to collapse
Yeah, don't let it get ya down Hoss! Some folks just like learning things the hard way I reckon. We both did. And, in the long run, they'll be better off for it :good:

Question Fastbook flashing unlock not recognized?

Hi guys, I'm stucked at this weird problem, basically when I type that command, fastboot reply with the list of options, like the command itself doesn't exist. Funny things is, to confirm it should work, I've tried to launch it with the device connected but not in fastboot, and it says "waiting for device" so the command actual exists.
I've tried so far: dl the last adb sdb from the official page
put the phone through fastboot using adb fastboot devices (it works)
launch the command: nothing works
This is hmm my 4th? Oneplus, so isn't like I'm new to unlock bootloaders but now I'm stucked, any ideas?
Of course OEM debug is on and also OEM unlock
ps.: I've also tried the old command but no resuts

here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock

MrSteelX said:
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
Click to expand...
Click to collapse
Ty, I've done it properly but sadly, I'm in the loop now, because following the guide to unlock:
because of the mismatch of the step 3 (which stated correctly I guess, "init_boot", and the pic, I've wrote boot instead of init_boot and flashed the patched magisk file to the boot.
Do you know/have where find the correct boot file to patch it back? My model is the CPH2449 A09 BA (europe) for what I remember...
Or, what guide can I follow withouth worst the situation... For now, I can still enter in the fastboot mode

If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.

surajpai524 said:
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
Click to expand...
Click to collapse
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...

takui said:
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
Click to expand...
Click to collapse
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com

surajpai524 said:
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
Click to expand...
Click to collapse
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!

takui said:
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
Click to expand...
Click to collapse
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.

surajpai524 said:
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
Click to expand...
Click to collapse
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?

takui said:
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
Click to expand...
Click to collapse
Only is to fix phone lock issue is by relocking bootloader and unlocking it till it works. This must be done only if not rooted. No other method was found till now.

I've tried at least 5+ times, nothing. I've read first we need to flash stock then lock again, but idk how to flash stock frankly....now desperately I'm flashing it through enhanced fastboot tool, even if a guide said to avoid cuz some op10R got bricked... let's see....