Well over night my z2 force updated itself to Oreo, before I could unlock the bootloader.. Now when in fastboot and type "fastboot oem get_unlock_data", all I get is waiting on device.. I have usb debugging enabled, and oem unlock enabled. I also have the latest drivers installed.. I had no issue unlock my g5s plus, but this one is given me trouble.. Any suggestions
I activated my new phone yesterday, after receiving all the latest updates. Android 8.0 Security patch May 1st, Build # OCXS27.109-48-6
The phone is a Z2F XT1789-03 Sprint.
I had no issues unlocking BL after all the updates.
double check everything your doing.
check your cable, after you put your phone in FB mode, then plug in cable does your phone say transfer mode : USB ready?
Do you have the Motorola Drivers in your PC?
Marcowe said:
Do you have the Motorola Drivers in your PC?
Click to expand...
Click to collapse
I have Motorolad drivers installed.. If you go adb devices it shows the phone.. Then adb rebootbootloader boots you into bootloader. Then if I go fastboot devices it show nothing. If I type in the fastboot oem get_unlock_data is does nothing. No matter what I do it does nothing.. This is a new phone I just got yesterday....
TwoBuells said:
I activated my new phone yesterday, after receiving all the latest updates. Android 8.0 Security patch May 1st, Build # OCXS27.109-48-6
The phone is a Z2F XT1789-03 Sprint.
I had no issues unlocking BL after all the updates.
double check everything your doing.
check your cable, after you put your phone in FB mode, then plug in cable does your phone say transfer mode : USB ready?
Click to expand...
Click to collapse
Nope just says waiting on device. I have tried multiple usb ports on my computer. Funny thing I had no problems with my g5s plus.
It's either the cable or drivers. Can you see your phone and copy files to and from your computer? If not then it's the cable. If cable is ok download and reinstall drivers from Motorola's boot loader unlock page/ website.
---------- Post added at 10:06 PM ---------- Previous post was at 10:03 PM ----------
Which carrier phone are u trying to unlock?
Thank you sprint.. I got it figured out, but do not qualify for bootloader unlock.. Must be something they did during one of the updates.. I pissed.
doubledragon5 said:
Thank you sprint.. I got it figured out, but do not qualify for bootloader unlock.. Must be something they did during one of the updates.. I pissed.
Click to expand...
Click to collapse
I just unlocked my BL two days ago. the phone is Sprint XT1789-03 that I bought from Motorola, the phone came with a Sprint Sim card. I activated the phone with Sprint B4 I unlocked the BL
TwoBuells said:
I just unlocked my BL two days ago. the phone is Sprint XT1789-03 that I bought from Motorola, the phone came with a Sprint Sim card. I activated the phone with Sprint B4 I unlocked the BL
Click to expand...
Click to collapse
I don't know what the deal is then I must be doing something wrong cuz mine was sent to me directly from Sprint
doubledragon5 said:
I don't know what the deal is then I must be doing something wrong cuz mine was sent to me directly from Sprint
Click to expand...
Click to collapse
Mine came with a SIM card as well I activated with with Sprint as well mine originally had the August 2017 security patch and then it just kept on updating and then overnight it automatically updated me from nougat to Oreo so I don't know if having the Oriole bootloader is what causing it I'm not sure was
SUCCESS: Did it again, and made sure there was no spaces which ended up being the problem.. Bootloader now unlocked..
Next How do we root and install twrp with oreo.
SUCCESS again installing twrp and magisk v16.6 Now to debloat this phone, and install what I wish.
Related
Alright, let's get right to it.
I am receiving a replacement Pixel XL after sending my original one back to Google. I purchased my original Pixel from Verizon and sent back to Google a Verizon Pixel with a locked bootloader (from 7.1.1 patch). Few questions....
1. Am I receiving a Google pixel XL with an unlocked bootloader?
I have read that I can unlock the bootloader and successfully root BEFORE I set up wifi and put the SIM card in... So
2. Will the device ship with 7.1.1 (Verizon), ending any chance of me unlocking the bootloader?
3. If the device ships with 7.1, can I prevent the update being installed in the background?
I put a screenshot with the email from google about the replacement device below.
Splatlame said:
Alright, let's get right to it.
I am receiving a replacement Pixel XL after sending my original one back to Google. I purchased my original Pixel from Verizon and sent back to Google a Verizon Pixel with a locked bootloader (from 7.1.1 patch). Few questions....
1. Am I receiving a Google pixel XL with an unlocked bootloader?
I have read that I can unlock the bootloader and successfully root BEFORE I set up wifi and put the SIM card in... So
2. Will the device ship with 7.1.1 (Verizon), ending any chance of me unlocking the bootloader?
3. If the device ships with 7.1, can I prevent the update being installed in the background?
I put a screenshot with the email from google about the replacement device below.
Click to expand...
Click to collapse
1a. It says Verizon but you won't really know til you get it.
1b. You can only do that if the phone comes with 7.1 to avoid it updating to 7.1.1
2. Verizon does seem to be updating some of the phones now and I would assume the refurbished will have a higher chance of it.
3. You can shut off automatic updates but it seems to ignore it at times, so you should unlock right away if you want to do anything in the future.
jjayzx said:
1a. It says Verizon but you won't really know til you get it.
1b. You can only do that if the phone comes with 7.1 to avoid it updating to 7.1.1
2. Verizon does seem to be updating some of the phones now and I would assume the refurbished will have a higher chance of it.
3. You can shut off automatic updates but it seems to ignore it at times, so you should unlock right away if you want to do anything in the future.
Click to expand...
Click to collapse
Excellent answers.
One more question though, I read that when you put in a Verizon sim card, that's what triggers the locking of the bootloader. So let's say I'm able to lock the bootloader, install TWRP, and SuperSU, and then I put in my sim card so I can actually use the phone, will putting in sim card have any affect on anything?
Splatlame said:
Excellent answers.
One more question though, I read that when you put in a Verizon sim card, that's what triggers the locking of the bootloader. So let's say I'm able to lock the bootloader, install TWRP, and SuperSU, and then I put in my sim card so I can actually use the phone, will putting in sim card have any affect on anything?
Click to expand...
Click to collapse
I have a Pixel XL that I purchased directly from Google and I use it on Verizon. Powering up the phone the first time with the Verizon SIM gave me a message that the phone was activated but it did not re-lock my bootloader. That was my experience. Originally it would only connect to 3G and not LTE. I had previously used it on Fi. I had to delete the data(NOT Factory Reset) from the Fi app(with the Fi SIM still installed) and then power down, switch SIM's, then power up to get full 4G LTE connection on Verizon. After I deleted that Fi app data and powered up with the Verizon SIM it selected the normal VZWINTERNET APN and worked fine. Hope this helps. Again though the Verizon SIM did not re-lock my bootloader. This isn't to say they won't try to re-lock it in the future with an update.
Splatlame said:
I read that when you put in a Verizon sim card, that's what triggers the locking of the bootloader.
Click to expand...
Click to collapse
Not true. I have a VZW Pixel on Project Fi. My bootloader can not be unlocked.
Now does unlocking the bootloader with 7.1 before the update kicks in a confirmed solution? Has this been tested? Or this is a theory?
And if this is a real way of doing it can someone link me to a thread with a verified procedure or help me out here.
I want to be 100% sure by the time the device comes in.
Splatlame said:
Now does unlocking the bootloader with 7.1 before the update kicks in a confirmed solution? Has this been tested? Or this is a theory?
And if this is a real way of doing it can someone link me to a thread with a verified procedure or help me out here.
I want to be 100% sure by the time the device comes in.
Click to expand...
Click to collapse
Here is what you need if it is on 7.1
http://theroot.ninja/depixel8.html
TonikJDK said:
Here is what you need if it is on 7.1
http://theroot.ninja/depixel8.html
Click to expand...
Click to collapse
That method does not work anymore.
bradhoschar said:
That method does not work anymore.
Click to expand...
Click to collapse
He said if it's on 7.1
jjayzx said:
He said if it's on 7.1
Click to expand...
Click to collapse
You're right.
On a side note, if anybody has a TRULY defective device on Verizon and want a Google replacement, see my post here:
https://forum.xda-developers.com/pi...-buying-verizon-edition-t3581406/post71866381
So, i broke my direct from google pixel xl, that was unlocked. I had insurance through verizon and they sent me a new one. Now, i know the verizon versions are locked, which is what i didn;t want, but i had no choice through asurion. The phone i received is on NHG47L which isn't the verizon version, but the OEM unlock is still grayed out. can anyone tell me why i can't unlock even though this seems to be a google fi/tmobile build?
i have no put a sim in it yet, i've only connected it to wifi. i'm waiting till i have a firm answer one way or the other.
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
cam30era said:
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
Click to expand...
Click to collapse
i did connect it to wifi, it did not change the OEM unlock option.
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
cam30era said:
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
Click to expand...
Click to collapse
Would flashing a factory image do anything, maybe a previous version?
Legacystar said:
Would flashing a factory image do anything, maybe a previous version?
Click to expand...
Click to collapse
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
cam30era said:
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
Click to expand...
Click to collapse
so, if the bootloader was never unlockable, how would one change the software version?
Legacystar said:
so, if the bootloader was never unlockable, how would one change the software version?
Click to expand...
Click to collapse
ADB sideload. Or wait for OTA to be pushed.
cam30era said:
ADB sideload. Or wait for OTA to be pushed.
Click to expand...
Click to collapse
i meant, how did this phone's software get changed?
Legacystar said:
i meant, how did this phone's software get changed?
Click to expand...
Click to collapse
The firmware is downloaded based on the sim in the device. Not where it was purchased
pcriz said:
The firmware is downloaded based on the sim in the device. Not where it was purchased
Click to expand...
Click to collapse
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
mattwheat said:
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
Click to expand...
Click to collapse
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
pcriz said:
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
Click to expand...
Click to collapse
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
mattwheat said:
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
Click to expand...
Click to collapse
Verizon isn't the only carrier to lock it down. Google has never been implicitly root friendly, also I'm sure a partner ship with verizon is to their benefit. Like getting their foot in the door to a wider market. The trade off is the bootloader.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
These coolicool phones always come with the wrong firmware install, the simple solution to that is to flash the correct firmware which is plain old RETAIL. Solved. That's for anyone who might have or end up with one of these phones.
As for your phone and since you're in the situation you are I'd flash VZW pie. That isn't the correct firmware for your phone, but you've got a locked BL with VZW on it now and nothing is working. Since your ultimate goal is to flash pie anyways, that's what I'd do. Maybe that will clean up your system enough to enable oem unlock. If you can get your BL unlocked, then you're half way there. Surely by now you've realized that you haven't got many if any options.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Yes, I put my self in prison by locking bootloader, I already downloaded this firmware, but how can I update this firmware via ADB Sideload or Micro SD?
as you know bootloader locked and there isn't a simple way, with locked bootloader I can't flash this file, (Remote Failure) error
thanks a lot
41rw4lk said:
These coolicool phones always come with the wrong firmware install, the simple solution to that is to flash the correct firmware which is plain old RETAIL. Solved. That's for anyone who might have or end up with one of these phones.
As for your phone and since you're in the situation you are I'd flash VZW pie. That isn't the correct firmware for your phone, but you've got a locked BL with VZW on it now and nothing is working. Since your ultimate goal is to flash pie anyways, that's what I'd do. Maybe that will clean up your system enough to enable oem unlock. If you can get your BL unlocked, then you're half way there. Surely by now you've realized that you haven't got many if any options.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Hello, anybody?????
There is any way to Upgrade Android 8 to Android 9 with locked bootloader?
My Device state: flashing_locked
is it possible to FORCE UNLOCK?
or is it possible to open hardware device and make it force unlock?
please help me,
someone?
solution
I need help, PLEAAAAAAAAAAAAAAAAAAAASSSSSSSSSSSSSEEEE
Have you tried using Lenovo moto smart assistant?
Leonardoliveira said:
Have you tried using Lenovo moto smart assistant?
Click to expand...
Click to collapse
Yes, I did, not work
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
gamc01 said:
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
Click to expand...
Click to collapse
You need to elaborate. Is oem unlocking grey out? Are you signed into google services? Do you have wifi and/or radio?
gamc01 said:
Hi, could you solve your problem? I have a moto xt1789-05 with the bootloader locked and it doesn't allow me to start the developer options. I'm looking for a solution if you could?
Click to expand...
Click to collapse
I couldn't do anything, I just send to Motorola repair and they change mainboard
sorry, I didn't find any solution
Ok I'll keep looking for some solution thanks
---------- Post added at 04:27 AM ---------- Previous post was at 04:13 AM ----------
41rw4lk said:
You need to elaborate. Is oem unlocking grey out? Are you signed into google services? Do you have wifi and/or radio?
Click to expand...
Click to collapse
thank you for responding 41rw4lk, what happens is that I can not access because it does not pass from the logo of motorola then it restarts when i try flash whith the retail version of brazil, but when i flash whith the versions at&t oreo or amx of telcel when turning on the moto I get the message your device is corrupt it cant be trusted and will not boot. I have seen some videos In which it has worked but not specify the bootloader status
gamc01 said:
Ok I'll keep looking for some solution thanks
---------- Post added at 04:27 AM ---------- Previous post was at 04:13 AM ----------
thank you for responding 41rw4lk, what happens is that I can not access because it does not pass from the logo of motorola then it restarts when i try flash whith the retail version of brazil, but when i flash whith the versions at&t oreo or amx of telcel when turning on the moto I get the message your device is corrupt it cant be trusted and will not boot. I have seen some videos In which it has worked but not specify the bootloader status
Click to expand...
Click to collapse
You shouldn't flash firmware from other variants like att, etc. However, if you're able to flash those firmwares and not get any permission denied errors then your bootloader is unlocked, which is good. If you have NOT flashed a pie firmware, good, do NOT do it until everything is up and running and you're sorted. If you have, then you'll need to use pie firmware to fix it since once you flash a pie modem there is no going back to an oreo modem.
Run this command from bootloader/fastboot mode and post back your output.
PHP:
fastboot getvar all
You can omit your imei and your serial no. for privacy.
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
What software channel does it have listed in about phone settings?
Here
41rw4lk said:
What software channel does it have listed in about phone settings?
Click to expand...
Click to collapse
Its here
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
41rw4lk said:
Since it's an -05 variant, with retbr, and has had pie flashed in some form I'd try flashing retbr pie firmware.
Firmware - https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flashall - https://forum.xda-developers.com/attachment.php?attachmentid=4812854&d=1567089696
adb and fasboot files - https://forum.xda-developers.com/attachment.php?attachmentid=4781024&d=1561215357
General guide on how to flash. Use the firmware and flashall I posted. - https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
It might not correct your problem, not sure how much of a mess is going on there, but this will be a good starting point. Just pay attention to what is going on and what (if any) errors you receive.
Click to expand...
Click to collapse
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
crpcnt.cpc said:
Nothing yet, I tried what you sent but as it has the bootloader locked I believe it is preventing.
Will I have to stay connected 7 days to enable OEM unlock?
Click to expand...
Click to collapse
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
41rw4lk said:
No. You just need to sign into google on your phone to enable oem unlocking. Might try pairing bluetooth to get a connection if possible. Might try using the lenovo moto smart tool to see if it'll do a rescue on it. With a locked bootloader typically you can only flash official signed firmware that is either the version or newer. Again, depending on what kind of mess you've got there you might not get anything to flash.
Click to expand...
Click to collapse
I logged into my google account, but it doesn't enable OEM unlock yet, so the mess was big on it.
crpcnt.cpc said:
Hi guys,
I recently got a Moto Z2 Force XT1789-05 variant from Brazil which apparently tried to force an update to the pie but it must have been the wrong firmware so it lost imei and wifi. And it seems to relock the boot loader and have returned to oreo. Then I can not activate the OEM unlock, I even tried to use the internet from the PC via USB but still does not enable the option. I'm not sure what else to do does anyone know what to do ??? Help
Sorry my bad english
Click to expand...
Click to collapse
I'm in the same situation, I've tried everything, I've had several people helping me, I have the same model and variant and I can't recover at all.
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
fryedmonk911 said:
I got replacement pixel 2 xl on android 10 security patch October 6/2019 I tried everything from fastboot I get error saying locked I don't know what carrier I checked imei and meid all good its networked unlocked I even went into safe mode and removed guest rebooted nothing …...I hate android 10 my signal sucks compared to android 9
oem unlock bootloader is grayed out
Click to expand...
Click to collapse
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Badger50 said:
Sounds like you got a Verizon variant device instead of a google one. If you can't toggle OEM unlocking from the get go, you really can't unlock the bootloader. Sorry man
Click to expand...
Click to collapse
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
crixley said:
I'm Canadian and I got three pixel 2 refurbs before giving up. There's a huge support thread about how all refurb bootloaders cannot be unlocked. Not sure why. I had a slot unbootable error, this was on my non xl variant.
Click to expand...
Click to collapse
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
sinkoo1979 said:
Mine have oem unlock option but can't unlock the bootloader. tried all the commands but won't let me unlock the bootloader. any help will be greatly appreciated. running android 10
Click to expand...
Click to collapse
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Badger50 said:
Are platform-tools up to date?
Are you using a USB a to USB C cable?
Does your phone get recognized when you type in fastboot devices?
Are you using power shell?
Is USB debugging turned on?
Click to expand...
Click to collapse
didn't check
yes
yes
yes
yes
sinkoo1979 said:
didn't check
yes
yes
yes
yes
Click to expand...
Click to collapse
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Badger50 said:
Check your platform-tools, and don't use power shell commands. Open your command prompt directly on your platform-tools folder.
Click to expand...
Click to collapse
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
sinkoo1979 said:
will try. Thank you
Update: unlocked bootloader with minimal adb and fastboot.
Click to expand...
Click to collapse
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
fryedmonk911 said:
thank you all for responding , I did contact google yesterday and was told all pixel devices that come from google are fully unlock they told me to call Verizon up I did last night and it is one of there phones I am sending it back to the seller and explaining to him what I want .were I live we have a hybrid tower and for some reason android 10 sucks compard to 9
Click to expand...
Click to collapse
I'm guessing when Google told you that all phones coming from Google were fully unlocked they were talking about being carrier unlocked instead of having the capability of unlocking the bootloader.
When buying a LG phone (e.g. Pixel 2 XL) it's good to have the seller run an IMEI check and post the screenshot for you from this site... https://www.imeipro.info/check_lg.html
Under they buyer name you can tell if you are getting a Google or Verizon variant.
Badger50 said:
Congrats :good: However, I would recommend getting rid of minimal adb and just use platform-tools going forward. Minimal adb can cause problems when it comes to fastbooting factory images :good:
Click to expand...
Click to collapse
Since all Minimal ADB and Fastboot does is bundle up the platform tools and add a Windows executable stub to them, removing it isn't a bad idea. An alternative - that I took - would be to update the platform tools in the Minimal ADB folder with the latest from Google.