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.
Related
As stated in the title, I bought a Droid Maxx that apparently is bootloader unlocked. Does this mean I accidentally got a dev edition? Because as far as I know, it's impossible to unlock the retail version...
kuz142 said:
As stated in the title, I bought a Droid Maxx that apparently is bootloader unlocked. Does this mean I accidentally got a dev edition? Because as far as I know, it's impossible to unlock the retail version...
Click to expand...
Click to collapse
does it say Developer Edition below the Verizon logo on the back of the phone? If not you might want to talk with a developer on here....
BladeRunner said:
does it say Developer Edition below the Verizon logo on the back of the phone? If not you might want to talk with a developer on here....
Click to expand...
Click to collapse
No it doesn't actually, I've looked at as many possible distinguishing characteristics on the device and it seems to be the retail version...
kuz142 said:
No it doesn't actually, I've looked at as many possible distinguishing characteristics on the device and it seems to be the retail version...
Click to expand...
Click to collapse
So are you able to flash a custom recovery on that?
BladeRunner said:
So are you able to flash a custom recovery on that?
Click to expand...
Click to collapse
Not sure, is it worth trying? As of now I'm still on 4.2.2 with root and write protect off, and don't want to have to do any full resets if I screw anything up. Also, are there even any custom recoveries available for these devices?
kuz142 said:
Not sure, is it worth trying? As of now I'm still on 4.2.2 with root and write protect off, and don't want to have to do any full resets if I screw anything up. Also, are there even any custom recoveries available for these devices?
Click to expand...
Click to collapse
Here is a version of TWRP for 4.2.2 http://forum.xda-developers.com/showthread.php?t=2458449&page=7 link is in post #3. You can try flashing it in fastboot to see if it will overwrite the stock recovery. I don't believe there is any risk. If it's not compatible it will simply fail.
Method is to flash via fastboot, reboot bootloader, reboot to recovery then reboot system.
BladeRunner said:
Here is a version of TWRP for 4.2.2 http://forum.xda-developers.com/showthread.php?t=2458449&page=7 link is in post #3. You can try flashing it in fastboot to see if it will overwrite the stock recovery. I don't believe there is any risk. If it's not compatible it will simply fail.
Method is to flash via fastboot, reboot bootloader, reboot to recovery then reboot system.
Click to expand...
Click to collapse
Worked great, running full TWRP now!
*survived a reboot too
kuz142 said:
Worked great, running full TWRP now!
*survived a reboot too
Click to expand...
Click to collapse
Was this a new phone or did you buy it used?
BladeRunner said:
Was this a new phone or did you buy it used?
Click to expand...
Click to collapse
Used, bought on swappa because I needed one with 4.2.2, screwed up my old maxx on 4.4 and no way to fix that w/o losing root
kuz142 said:
Used, bought on swappa because I needed one with 4.2.2, screwed up my old maxx on 4.4 and no way to fix that w/o losing root
Click to expand...
Click to collapse
anyway you can post a picture of your bootloader screen?
---------- Post added at 10:51 AM ---------- Previous post was at 10:45 AM ----------
kuz142 said:
Used, bought on swappa because I needed one with 4.2.2, screwed up my old maxx on 4.4 and no way to fix that w/o losing root
Click to expand...
Click to collapse
Which listing on Swappa was it? I was looking at the recently sold ones and am trying to figure out the history.
BladeRunner said:
anyway you can post a picture of your bootloader screen?
Click to expand...
Click to collapse
Differences from bootloader screen of my old maxx are: of course the "unlocked" and status code 1, and the option to "switch console"
Which listing on Swappa was it? I was looking at the recently sold ones and am trying to figure out the history.
Click to expand...
Click to collapse
http://swappa.com/listing/GGX337/view
kuz142 said:
http://swappa.com/listing/GGX337/view
Click to expand...
Click to collapse
Interesting. I think I've seen someone else post pics of a phone like this. They may have been factory test/development phones.
BladeRunner said:
Interesting. I think I've seen someone else post pics of a phone like this. They may have been factory test/development phones.
Click to expand...
Click to collapse
this is what i was about to post. but if not you should try and find out who actually had the phone before the swapa seller
Awesome! It could be just a developer unit, or you might have just found the holy grail of Maxx development. Either way, enjoy your unlocked bootloader and don't hold out for too much cash when some wonderful developer wants to buy it off of you and discover its secrets!
OMG its indeed and Regular Droid Maxx with unlocked bootloader!!
Good Find!
maybe its the first batch of new Droids by lenovo or the owner found a way to unlock the bootloader or was a test device, who knows, anyway its amazing!
I rooted my Google Pixel 2, but I'm returning it to Google and I want to unroot it before I do so. Can someone provide me on a good/safe guide or procedure on how to do this? Thanks!
If you're going to return it, just flash the factory image provided here: https://developers.google.com/android/images and relock the bootloader.
thedesp said:
If you're going to return it, just flash the factory image provided here: https://developers.google.com/android/images and relock the bootloader.
Click to expand...
Click to collapse
Ok thanks. I figured this, but is there a good guide out there? Don't want to have any issues and it'd be nice to follow a solid guide. I found some, but I want to be sure it works for a pixel 2 and I'm not doing something improperly.
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
change from "fastboot flashing unlock" to "fastboot flashing lock" instead.
thedesp said:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
change from "fastboot flashing unlock" to "fastboot flashing lock" instead.
Click to expand...
Click to collapse
Ok. I'm just afraid I'll mess something up.
I'm just going to follow this: https://www.youtube.com/watch?v=HDG4W8QI1ZE
Looks a little different then what you said, but I think it's OK...What do you think?
upperbladez said:
Ok. I'm just afraid I'll mess something up.
Click to expand...
Click to collapse
I'm honestly concerned that you should not have rooted your device in the first place if you are but familiar enough with simple adb commands to relock your device. Please read read read read read, then root.
PuffDaddy_d said:
I'm honestly concerned that you should not have rooted your device in the first place if you are but familiar enough with simple adb commands to relock your device. Please read read read read read, then root.
Click to expand...
Click to collapse
I've rooted devices in the past - was long ago though...so I'm just relearning it. Thanks for your concern, but I know enough to do what I need to do. Just looking for verification that Youtube video is good enough. Thanks!
For anyone who hasn't been able to sideload the update or wants the factory images, it is now on the Razer Development Portal
thanks! i've been waiting for this to update
So does this mean that maybe custom Rom/Kernel development may start?
Anyone know if it's safe to update to global 8.1 straight from the Three UK branded 7.1.1 version?
Sent from my Phone using Tapatalk
How do I install this on a three branded handset only got phone today so if Any one could post a guide I'd be most appreciated
patient81 said:
Anyone know if it's safe to update to global 8.1 straight from the Three UK branded 7.1.1 version?
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
Yes it is mate. I'm running 8.1 from 7.1.1 on my three razer phone
Strangeland16 said:
How do I install this on a three branded handset only got phone today so if Any one could post a guide I'd be most appreciated
Click to expand...
Click to collapse
Download the Global Rom and unzip it. Make sure ADB and fastboot drivers are installed on your PC. Open command prompt with Administrator Privileges. Change directory to where you unzipped your rom, type ADB reboot bootloader, run the command flash_all.
Edit: make sure you have usb debugging enabled on your phone
Thanks for this do I need to delete anything off phone first does the bootloader need to be unlocked first sorry complete noob to razor though flashed recoveries and roms on my galaxy s8 .once I've done this will the phone be rebranded orndo I need to do that first.will I be able to download updates after ??
---------- Post added at 09:33 PM ---------- Previous post was at 09:31 PM ----------
Thanks do i need to debrand or unlock bootloader first will this then update from razer not three after ??
Strangeland16 said:
Thanks for this do I need to delete anything off phone first does the bootloader need to be unlocked first sorry complete noob to razor though flashed recoveries and roms on my galaxy s8 .once I've done this will the phone be rebranded orndo I need to do that first.will I be able to download updates after ??
Click to expand...
Click to collapse
This will show you the exact process mate. Yes this will update with razer instead of three. You won't have to hang around for three to release updates
https://developer.razer.com/razer-p...6.2088813517.1524083559-1692679314.1524083559
Thanks I'll gather some courage and have a go
Love this phone but Substratum/Andromeda still doesn't work on 8.1, still a conflict with Razer theme engine? Any way to disable Razer theme engine under root and enable substratum?!?! Or any other way short of flashing LOS, which I tried and failed to do?
Hi
Strangeland16 said:
Thanks I'll gather some courage and have a go
Click to expand...
Click to collapse
Doing this will void your warranty ! Just a heads up. ?
arnookie said:
Doing this will void your warranty ! Just a heads up.
Click to expand...
Click to collapse
Very true but you just need to relock bootloader to make a RMA claim through Razer. Had to do that with my first phone. Surprised this phone doesn't have a tamper flag on it.
I can't open Netflix does anyone have the same problem?
bootloader and critical unlocked but I use Magisk and safety net is ok double true
kaze2295 said:
I can't open Netflix does anyone have the same problem?
bootloader and critical unlocked but I use Magisk and safety net is ok double true
Click to expand...
Click to collapse
Yes I did. I downloaded the latest APK. Just search Google to find it and all is working.
kaze2295 said:
I can't open Netflix does anyone have the same problem?
bootloader and critical unlocked but I use Magisk and safety net is ok double true
Click to expand...
Click to collapse
Did you hide the Netflix app in Magisk?
silvercat said:
Did you hide the Netflix app in Magisk?
Click to expand...
Click to collapse
No. I literally downloaded the Netflix APK and installed it. Presume it installed over the top.
Guys .. Is there any plan for any custom ROMs?!
Thanks.
Mulham82 said:
Guys .. Is there any plan for any custom ROMs?!
Thanks.
Click to expand...
Click to collapse
Just thought GSI, seems like the new wey to do it.
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs
junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs
Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?
aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.
Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks
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!