Related
Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
greategress said:
Sorry my first post is a plea for help, but here we are.
I flashed the latest (2013-5-10) version of ..Cory..'s unofficial Cyanogenmod this morning and I'm having issues with video, including my camera viewfinder. Both Youtube and my camera lag to the point of uselessness, though audio on videos plays just fine.
Also sometimes my desktop icons stick around when I pull up the recent apps or notification drawer.
Has anyone else experienced either one of these? I'd post this in the thread for the ROM, but I need to hit my post count first.
And lest I sound ungrateful, big thanks to ..Cory.. for keeping things moving forward while the official version is on hiatus!
Click to expand...
Click to collapse
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
greategress said:
So I tried disabling HW in dev settings, and that seems to work for now. Still curious if anyone else has run into this issue.
Click to expand...
Click to collapse
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
imutau said:
Not that I could see on my end. But I did do a factory reset in TWRP first before I flashed?
Click to expand...
Click to collapse
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
greategress said:
So did I, unfortunately. Might have to just try it again this weekend and see if that works. :fingers-crossed:
Click to expand...
Click to collapse
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
exad said:
Check MD5 of your ROM, make sure it matches up if you haven't.
Also, If you haven't done so, try fastboot erase cache prior to wiping and flashing.
Click to expand...
Click to collapse
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
greategress said:
Thanks for the advice, exad! I'll try to fastboot erase cache step this weekend. Didn't do it this time because I thought I didn't have to use fastboot now that I have S-OFF.
Click to expand...
Click to collapse
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
exad said:
That command clears the cache for fastboot and recovery, this will ensure that recovery is properly wiping your partitions so be sure to do it before wiping and flashing your rom.
Click to expand...
Click to collapse
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
greategress said:
Do you know a decent guide that includes this step? None of the ones I used previously included this step. I get this is an ADB command, but I try to avoid using ADB directly as much as possible due to noobness. Not sure what state my phone has to be in to use the command, etc.
Click to expand...
Click to collapse
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
exad said:
There are no guides because it's assumed that you are familiar with ADB and fastboot if you are on this forum.
fastboot and adb don't rely on states.
fastboot is a tool for pushing and pulling information/files to and from your phone while in bootloader
ADB is a tool that allows you to access your phone via a command line shell interface.
If this is confusing to you, why would you root your phone? And I'm not trying to be rude, this isn't an iphone jailbreak, rooting is COMPLETELY different and can be dangerous if you don't understand. Avoiding adb and fastboot does not make it any less dangerous either.
Click to expand...
Click to collapse
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
greategress said:
I considered not asking for advice, but then I thought "Naw, he's already here. I'm sure he won't mind." My apologies for forcing you to deal with my inexperience.
I used the word "state" incorrectly, not remembering at the time it had a specific programming meaning. You still managed to answer my question, though, pointing out my phone needs to be in the bootloader. You also cleared up that fastboot is its own tool rather than just a command used in ADB. Thank you for both those things. I'll figure it out from here.
As for why I'd want to root my phone? Who wouldn't? I don't want to be stuck with whatever AT&T thinks is good enough. I'm sorry if I'm making this club less exclusive, but if people here are going to hack together all this great stuff and give it away for free, I'm going to take advantage of that.
Click to expand...
Click to collapse
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Same issue
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
exad said:
You're misunderstanding, the exclusivity of this site makes no difference to me, I want everyone to be able to root and do cool things with their phones, hell, it's your phone, you bought it, own it, you should be able to do whatever you want with it. You didn't need me to tell you what fasboot and adb are. They're well documented tools with help manuals included. Even a quick google search would tell you everything you need to know about them and more.
You chose to ignore them and hope it won't affect you that you're not understanding what you're doing to your phone. You ask in here hoping for the quick and lazy way to accomplish your task without taking the time to learn what you're doing. I love helping people that's why I'm here posting every day. but you're taking advantage of my good nature and not trying to help yourself by reading, learning and understanding what you're doing.
I wish you luck and I don't want to discourage you for asking for help here when you need it, but please take the time to help yourself first.
Click to expand...
Click to collapse
*sigh* You're right. I'm sorry for getting snappy. Just not used to being the guy who doesn't know what he's doing, y'know?
Anyway, I sincerely appreciate the help, exad. And I doubly appreciate the reminder that I need to turn to Google before I come begging to you guys.
nlyang said:
I have the same issue with Youtube in landscape mode. I've noticed others have run into it as well.
Click to expand...
Click to collapse
Hmm. Heard anything about how to fix it?
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
exad said:
Have you tried flashing a different kernel? Like jacob.b2 or oc-vm-linaro?
Click to expand...
Click to collapse
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
greategress said:
I actually just got done following your original advice about clearing the cache via fastboot. Did that, then re-flashed the ROM and everything seems to be working. Thanks again for the help (and tough love )!
Click to expand...
Click to collapse
Anytime friend!
the only thing that worked for me...
greategress said:
Hmm. Heard anything about how to fix it?
Click to expand...
Click to collapse
i tried erasing the cache via fastboot before the wipe+flash, but unfortunately I still had the issue. the only temp fix that works for me so far is disabling HW overlays in the developer options.
You could also try another kernel.
Sent from my One X using xda app-developers app
exad said:
You could also try another kernel.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Any kernel you'd recommend over the others? You mentioned the jacob.b2 and oc-vm-linaro before. Like one more than the other?
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
this seems more like a user made htc dev, not what true s-off "bootloader unlocked" would be. non the less it should work fine. this probably wont touch the write enabled protection on the device. the only issues i see is until we are truly unlocked we will always have that "samsung custom" on out bootscreens.
spyz88 said:
I was wondering now that djrbliss has released the vulnerability for AT&T SGS4 do we have to wait for devs to do something with it? For Loki tools it seems as if you have to have a recovery already made. Will a current one work?
https://github.com/djrbliss/loki
Click to expand...
Click to collapse
He released his source code and such so we need to have someone compile it into a .bat or .exe so we can flash a custom recovery/rom
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
shabbypenguin said:
its linux only, and devs need to use/make teh loki_patch.
someone could make a windows/android app to interface with loki_flash for end users though...
Click to expand...
Click to collapse
well i cant use it as i don't use linux lol.
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
fix-this! said:
well i cant use it as i don't use linux lol.
Click to expand...
Click to collapse
well if you dont use linux you cant make kernels or recoveries
luckily the loki_flash utility that is used to actually put the patched img onto the device works on android so it doenst matter what kind of computer you have
alacrify said:
Everyone - if you don't know what to do with those files without asking, don't try it yourself. There's already one in process in the development thread, and there will be cleaner and simpler ones out within just a few hours, I'm sure - with complete instructions.
Until you can nandroid the phone, this is not something to screw around with
Click to expand...
Click to collapse
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
just means soon we will have bootloader unlocked.... patience
lorijuan1024 said:
just means soon we will have bootloader unlocked.... patience
Click to expand...
Click to collapse
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Bjray said:
A mod should put that up as a temp announcement in these forums. Seriously. Can't wait for the noobs to start crying in the Q&A area.... haha.
Click to expand...
Click to collapse
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Update: nand backup was successful. Good start for us, just need the perm fix, but for now, it rocks, it was so nice to see the recovery screen. SWEET
TheAxman said:
Exactly, I have one phone booting to recovery now, no issues. YET! better know what you are doing, or you will have a serious paperweight.
I re-booted out of successful, so will see.
Click to expand...
Click to collapse
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
fix-this! said:
i thought that's what this tool did. maybe this is why adam is still working on a bootloader unlock thats permanent. this should tide us over though.
Click to expand...
Click to collapse
what i meant was a tool that us people that aren't good with the programming language can use.
fix-this! said:
im not going to try the method yet, at least for a few days. i also see alot of soft bricked devices tonight.
Click to expand...
Click to collapse
Agreed, but I do have a jtag box here in hand, and there is no fix for that either, I might have one phone down soon..:
Incoming update from Samsung in 3....2....1.....
I flashed what shabbypenguin provided in his recovery thread and now have a working recovery on my ATT i337!!! :laugh::good::highfive::fingers-crossed:
Thanks to djrbliss for his awesome work!
mr_blanket said:
Incoming update from Samsung in 3....2....1.....
Click to expand...
Click to collapse
simple solution is to not take the OTA. but yes, i see one coming to.
fix-this! said:
simple solution is to not take the OTA. but yes, i see one coming to.
Click to expand...
Click to collapse
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
mattdm said:
Yes, everyone needs to keep the OTA .apk's frozen from now on. Or use a custom rom that doesn't have them.
Click to expand...
Click to collapse
hopefully adam can get us a more permanent solution. but props to dan for his tool.
Couldn't be happier after I get home from watching the hangover I get to unlock this bad boy
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Hello guys , is There a Way To remove the orange screen advising the bootloader has been unlocked?
noky76 said:
Hello guys , is There a Way To remove the orange screen advising the bootloader has been unlocked?
Click to expand...
Click to collapse
Right now there is no any method to remove that. I want to remove it too. But as development progresses, I believe there will be a solution.
For now, it's a no
I hope it gets fixed soon.
It's baked into the boot image. If you follow a logcat closely, you can see where it pulls in the insecure bootloader screen. I believe it's doing it by offset and length. It may be possible to modify the boot image to put in a different image but I've not delved that deeply.
Telperion said:
It's baked into the boot image. If you follow a logcat closely, you can see where it pulls in the insecure bootloader screen. I believe it's doing it by offset and length. It may be possible to modify the boot image to put in a different image but I've not delved that deeply.
Click to expand...
Click to collapse
Can you try man? That warning screen would be a big sigh of relief if removed.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Can you try man? That warning screen would be a big sigh of relief if removed.
Click to expand...
Click to collapse
It's more than I'm able to really do, perhaps someone else can give it a shot. It's annoying but doesn't impact the device at all.
Telperion said:
It's more than I'm able to really do, perhaps someone else can give it a shot. It's annoying but doesn't impact the device at all.
Click to expand...
Click to collapse
Maybe the OpenKirin team can.
Sent from my Honor 8 using XDA Labs
It's harder than it seems :/
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Edit: I guess it just took a passion and a situation. See thread for unlock.
Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
Fastboot flashing lock_critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you
Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.
Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
@SoloTSi97 has confirmed this does work on the January 5th security patch!
Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.
D3RP_ said:
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Click to expand...
Click to collapse
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
lmao not that I know of. But I know it's possible to update any android through adb sideload. I'm really just grasping for straws. But because of my current situation I have a Pixel 2 from Verizon, and i'm gonna have it for a while.
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
tailsthecat3 said:
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
Click to expand...
Click to collapse
Unless you know some magic way, it is locked. I don't even know where to start with this thing.
Sell the Verizon one to someone who doesn't care for root and buy one from Google?
I used Sunshine Root for my HTC m8 years ago. They might be an option in the future. Yet again, since the Google version is easily unlocked & rooted, I don't think anyone has even tried.
Sent from my Pixel 2 using Tapatalk
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
tailsthecat3 said:
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
Click to expand...
Click to collapse
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
D3RP_ said:
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Click to expand...
Click to collapse
^^
tailsthecat3 said:
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
^^
Click to expand...
Click to collapse
OEM unlocking says Bootloader is unlocked. So uh, it was that easy... Gonna root and install TWRP in a second.
Final Update
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
D3RP_ said:
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
Click to expand...
Click to collapse
Can you give some screenshot proof on this?
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
Does that prove anything?
D3RP_ said:
Does that prove anything?
Click to expand...
Click to collapse
This doesn't prove anything. Show us the bootloader screen with your phone's info. There will be a baseband number and the status of the bootloader. Cover your serial number.
[Edit]
You do have a custom kernel flashed though.. so I guess.
xtacocorex said:
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
Click to expand...
Click to collapse
Sorry for the late reply. When I do that, I get
Code:
(bootloader) get_unlock_ability: 0
I made a thread about this in the original Pixel XL section. In the OP I quickly jolted down what you did, can you go and explain in detail as it might also work with the OG Pixel's.
Thanks in advance :
https://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-bootloader-unlocked-t3726672
How did the OP pass the cert check and update checks?
TonikJDK said:
How did the OP pass the cert check and update checks?
Click to expand...
Click to collapse
edit
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
I just ran the command like OP said and the "unlock bootloader prompt" appeared. I ran this from a stock verizon on 8.0. I now flashed twrp, magisk and have the current google 8.1 ota. I will give proof if you tell me what will suffice.
Followed the same instructions here: https://www.the***********.com/unlock-bootloader-google-pixel-3-xl-guide/
and it worked. I know this is probably obvious to everyone on this forum, but just in case anyone was wondering if the version from google was easily unlock able out of the box, it is. I was able to get the device early as a product advocate. Being that not a lot of people on XDA have the device yet, I may be the first person to unlock their Pixel 4 XL? :angel:
elsamuraiguapo said:
Followed the same instructions here: https://www.the***********.com/unlock-bootloader-google-pixel-3-xl-guide/
and it worked. I know this is probably obvious to everyone on this forum, but just in case anyone was wondering if the version from google was easily unlock able out of the box, it is. I was able to get the device early as a product advocate. Being that not a lot of people on XDA have the device yet, I may be the first person to unlock their Pixel 4 XL? :angel:
Click to expand...
Click to collapse
Thanks for the info, excellent news for Verizon subscribers with Pixel 4!
Not from THAT link....
Sent from my Pixel 2 XL using Tapatalk
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
ZeroKool76 said:
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
Click to expand...
Click to collapse
Sometimes it's about the peace of mind to make sure it's being done properly
ZeroKool76 said:
I don't understand what you need a link for. Isn't it like every other device? Turn it on fastboot mode, hook up to your PC, check to make sure it's read, type in fastboot oem unlock, boom. Am I missing something?
Click to expand...
Click to collapse
Why put the link in there if it's not a valid link?
Sent from my Pixel 2 XL using Tapatalk
samteeee said:
Thanks for the info, excellent news for Verizon subscribers with Pixel 4!
Click to expand...
Click to collapse
The Verizon version will be locked.
Have you tried booting Magisk on it yet?
Did you have to turn it on and enable OEM unlocking in Developer options first or nah?
did you try root it ?
mine is coming today
it shipped last night before i went to bed lol
please system dump
brownkid said:
Did you have to turn it on and enable OEM unlocking in Developer options first or nah?
Click to expand...
Click to collapse
You need to turn it on and enable it
I just got my Pixel 4 XL. I want to root, but without the system image how can I get the boot image to patch?
---------- Post added at 07:53 PM ---------- Previous post was at 07:52 PM ----------
MishaalRahman said:
Have you tried booting Magisk on it yet?
Click to expand...
Click to collapse
What do you mean by booting Magisk?
MicroMod777 said:
The Verizon version will be locked.
Click to expand...
Click to collapse
Most likely.
MishaalRahman said:
Have you tried booting Magisk on it yet?
Click to expand...
Click to collapse
What do you mean by booting Magisk? @MishaalRahman
Followed the same steps as OP. Unlocked my 4XL the same way I unlocked my 3XL
northmendo said:
What do you mean by booting Magisk? @MishaalRahman
Click to expand...
Click to collapse
I think he means patching the boot image with magisk
northmendo said:
What do you mean by booting Magisk? @MishaalRahman
Click to expand...
Click to collapse
ZeroKool76 said:
I think he means patching the boot image with magisk
Click to expand...
Click to collapse
And then fastbooting the image that magisk patched :good:
For those asking, no I haven't tried to root it yet. I just wanted to start playing with the device and signing in to all my stuff. No point in doing that first without unlocking the bootloader cause just like with any other phone that will factory reset everything. Better to unlock the device first before you start customizing it to you liking. Most likely root can be achieved without wiping again.
What command are you using? I tried fastboot flashing unlock and it just shows the help menu and fastboot oem unlock gives an error. On win 10 here. That link is incomplete?
ETA: I ended up using a tool and setting it to pixel/ pixel xl and it worked but its all for not, I think I'm returning the phone. I just am not happy with the way the face unlock works with ambient display, it ends up unlocking the phone when I just want to check my notifications lol. C'est la vie!