Related
I've just bought my Galaxy Nexus for two days to replace my dead Nexus One.
The UI of ICS is so great but I miss the function from DEVs, like vibrate when the call made.
I have rooted my Nexus One without unlocking the bootloader and I would love to root my Galaxy Nexus without unlocking too.
Is there any DEV going to work on this?
I don't believe anybody is working on this since BL unlock is so simple, and there aren't really any disadvantages (that I know of). In order for root to occur without BL unlock, there would have to be an exploit found in the stock image. Is there a particular reason you don't want to unlock it? You have only had the phone two days, so I imagine your data loss won't be that big of an issue.
kekspernikai said:
I don't believe anybody is working on this since BL unlock is so simple, and there aren't really any disadvantages (that I know of). In order for root to occur without BL unlock, there would have to be an exploit found in the stock image. Is there a particular reason you don't want to unlock it? You have only had the phone two days, so I imagine your data loss won't be that big of an issue.
Click to expand...
Click to collapse
unlocking BL void the warranty
Booker-T said:
unlocking BL void the warranty
Click to expand...
Click to collapse
And rooting doesn't? After all, it does allow for modification/deletion of system files. In any case, you can re-lock it just as easily.
Booker-T said:
unlocking BL void the warranty
Click to expand...
Click to collapse
Accidentally thanked you haha - missed the quote button.
You can lock it if you have to send it in or return it, you know. The lock command is just as simple as the unlock!
zombieflanders said:
And rooting doesn't? After all, it does allow for modification/deletion of system files. In any case, you can re-lock it just as easily.
Click to expand...
Click to collapse
Rooting doesn't make the splash screen change (the lock under "Google"), so it can be easily unroot by deleting related files in the system and make it look like stock.
Are you sure a unlocked devices can lock again? Nexus One can't do this.
Booker-T said:
Rooting doesn't make the splash screen change (the lock under "Google"), so it can be easily unroot by deleting related files in the system and make it look like stock.
Are you sure a unlocked devices can lock again? Nexus One can't do this.
Click to expand...
Click to collapse
Yes, "fastboot oem lock" will re-lock the bootloader and make the padlock go away. Here is the write-up by droid-life (I can't view it at work, so I hope it has the right info!)
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
kekspernikai said:
Yes, "fastboot oem lock" will re-lock the bootloader and make the padlock go away. Here is the write-up by droid-life (I can't view it at work, so I hope it has the right info!)
http://www.droid-life.com/2011/12/1...the-bootloader-and-return-to-a-factory-state/
Click to expand...
Click to collapse
Mine one is the GSM one, I have searched on Googles, there is no GSM version re-lock tutorial there, so I doubt GSM version cannot re-lock.
And I don't have the stock image.
Booker-T said:
Mine one is the GSM one, I have searched on Googles, there is no GSM version re-lock tutorial there, so I doubt GSM version cannot re-lock.
And I don't have the stock image.
Click to expand...
Click to collapse
I thought the GSM factory image was pretty widely available?
http://www.theverge.com/2011/12/4/2610060/google-galaxy-nexus-factory-image-restore-phone
I am fairly certain people with the GSM variant have re-locked their phones, but I would check the Nexus android development section (GSM) for proof.
I've tested relocking and can confirm it works fine
Sent from my Galaxy Nexus using XDA App
Booker-T said:
unlocking BL void the warranty
Click to expand...
Click to collapse
I feel like this is a myth. You're not using an exploit, or anything like that, you're using a manufacturer provided tool to unlock the bootloader. Taken from android.com:
On Nexus One, Nexus S, Nexus S 4G, Xoom, and Galaxy Nexus, the bootloader is locked by default. With the device in fastboot mode, the bootloader is unlocked with
$ fastboot oem unlock
The procedure must be confirmed on-screen, and deletes the user data for privacy reasons. It only needs to be run once.
On Nexus One, the operation voids the warranty and is irreversible.
On Nexus S, Nexus S 4G, Xoom, and Galaxy Nexus, the bootloader can be locked back with
$ fastboot oem lock
Click to expand...
Click to collapse
I would love a way to root without unlocking the bootloader -- coming from the Nexus One, which I easily rooted without ever touching the bootloader -- it didn't occur to me that rooting would require unlocking the bootloader. Of course, I wish now that I'd unlocked the bootloader right when I took the phone out of the box, which is, I see now, what everyone recommends. But I've more data on the phone than I want to deal with losing right now.
So if anyone following this thread turns up a way to root without unlocking the bootloader, please let us know!
You won't see this feature arrive until manufacturers start selling ICS phones with locked bootloaders (I'm looking at you HTC, LG, etc). Devs will then try to punch a hole through the OS instead of using simple fastboot commands, as the bootloader will be locked down.
I don't understand why you would wait though, just fastboot oem unlock, root, then fastboot oem lock. The only way your warranty is going to be voided is if you have a rooted rom, that padlock means nothing on the Galaxy Nexus. IF THEY SEE SUPERUSER, THEY KNOW YOU ROOTED. They don't give a **** about the splash screen
I've read that when unlocking the bootloader with "fastboot oem unlock" it sets s-off. Is possible to set it again to s-on for warranty purposes?
In the wikipedia says that:
Once the user accepts the terms the protocol is enabled and a security flag showing that the device has been unlocked is permanently set.
Click to expand...
Click to collapse
Did you try "fastboot oem lock" ?
Sent from my Galaxy Nexus
milltronics said:
Did you try "fastboot oem lock" ?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
No, I still have the bootloader locked and would like to know before if is even possible.
Yes, fastboot oem lock will relock the bootloader.
Sent from my Galaxy Nexus using xda premium
El Daddy said:
Yes, fastboot oem lock will relock the bootloader.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
And that is what preserves warranty? I mean, after installing official rom and relocking that's it?
scandiun said:
And that is what preserves warranty? I mean, after installing official rom and relocking that's it?
Click to expand...
Click to collapse
Should be.
Depends, though. I returned my GNex with AOKP build twenty something, franco's kernel and what not.
S-on/s-off is only an htc thing I believe. Only htc phones have that from my understanding, not Samsung phones and especially no nexus phones regardless of manufacturer.
RogerPodacter said:
S-on/s-off is only an htc thing I believe. Only htc phones have that from my understanding, not Samsung phones and especially no nexus phones regardless of manufacturer.
Click to expand...
Click to collapse
You refreshed my mind just right now. The s-on and s-off is a HTC thing, I saw it on htc subforums.
I've tested 'fastboot oem lock' and does relock the bootloader, provided that you have stock rom installed. So this will preserve warranty.
Thank you.
RogerPodacter said:
S-on/s-off is only an htc thing I believe. Only htc phones have that from my understanding, not Samsung phones and especially no nexus phones regardless of manufacturer.
Click to expand...
Click to collapse
Well, you are half right. It is an HTC term and it refers to the NAND lock. Other manufacturers use locks as well -- Motorola being a prime example.
However, you are wrong about no Nexus devices being S-ON. The Nexus One is an S-ON device. Yes, it has an unlockable bootloader, but it is not relockable, and you did not have write (and in some cases, read) access to all the partitions.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Well, you are half right. It is an HTC term and it refers to the NAND lock. Other manufacturers use locks as well -- Motorola being a prime example.
However, you are wrong about no Nexus devices being S-ON. The Nexus One is an S-ON device. Yes, it has an unlockable bootloader, but it is not relockable, and you did not have write (and in some cases, read) access to all the partitions.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I presume it is the "oem" command that does the trick
scandiun said:
I presume it is the "oem" command that does the trick
Click to expand...
Click to collapse
On HTC devices, in order to get true S-OFF, you need a special SIM card, or SIM emulator to write directly to the NVRAM, which contains the security flag. Not sure on Motorola devices, as I don't believe anyone has figured it out yet.
On HTC devices, using the "oem" qualifier after "fastboot" gives you access to a huge list of other fastboot commands, but only with an engineering bootloader flashed. Some examples: dumping partitions straight from fastboot, flashing partitions not normally written to, etc.
On the Galaxy Nexus (using a shipping bootloader), it seems that the only "oem" commands available to us are lock and unlock.
EDIT: Solution: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
frap129 said:
Purchased mine from the Google store, non carrier locked. Using the latest fastboot but can't unlock b/l. I've tried fastboot oem unlock, fastboot oem unlocking, and fastboot flashing unlock but no dice. Any one else experience this or find a way around?
Click to expand...
Click to collapse
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Sent from my MHA-L29 using Tapatalk
danon.brown said:
Same issue with the essential phone. The command is different. Check over there for the new command to try it.
Click to expand...
Click to collapse
I already tried that command as I said in my post (unless there's one other than "fastboot flashing unlock" that I'm not seeing in the essential forum)
Can you see your phone with fastboot devices?
Sent from my MHA-L29 using Tapatalk
A few others with the phone have reported the same issue in the "rooting" thread...not sure what's going on!
I had the essential phone and had to get a more current Version of adb.
Sent from my MHA-L29 using Tapatalk
did you enable developer settings and see if there is a setting to allow OEM unlock?
Code:
fastboot flashing unlock
will unlock it
When I first booted the phone and enabled USB debugging, the OEM Unlock was greyed out. I had to put my sim card in for it to allow me to enable it. Then using the fastboot flashing unlock worked from bootloader.
fastboot flashing unlock worked for me.
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
@frap129 hope you get it sorted. Glad to see you got a 2 XL as well! Would love to eventually see Carbon and Electron on the 2 XL. Have been missing them since I RMA'd my 6P for an XL. :good:
What is the point if the stock android phone has locked bootloader!
I miss NEXUS phones
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Thanks for all the responses, I guess it's just my fastboot version. I have the latest that's on the aur, but I'll try manually downloading from Google's site.
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
cryppie said:
This would be a great time to separate the Verizon and Google subforums:
Google Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
Verizon Pixel 2 XL ROMs, Kernels, Recoveries, & Other Development
MDK vs non MDK Galaxy S4 forums were a nightmare. Thousands of posts asking how to unlock the non-MDK bootloader which of course never happened. Same thing will happen with the Verizon version P2's..
Click to expand...
Click to collapse
Disagreed. This was not necessary with the OG Pixel.
Further, I think most people here know that the chances of unlocking a Verizon bought Pixel are slim to none.
dirtyfingers said:
I'm not sure if this is why it finally worked for me or not. I tried a dozen times to unlock with the "fastboot flashing unlock" command and it failed every time when I booted to bootloader from adb with the "adb reboot bootloader" command. It only worked for me when I turned the phone off, booted into bootloader by holding the power and volume down button, and then connect the cable and type the command. My phone was recognized in fastboot either way so i'm not sure why it didn't work before, but at least I got it now.
Click to expand...
Click to collapse
Ive been using adb reboot the whole time and can't get it to work, thanks for the heads up!
UPDATE: Didnt work with latest linux binaries (26.0.1) but using minimal adb and fastboot worked on windows. If you have the same issue, try a windows machine if you have access.
Sorry for the double post, I just wanted to make sure anyone following this with the same issue gets the solution.
cwalker0906 said:
Those of us that had a pixel will know this, but if you do not have updated adb and fastboot, it will not work on the pixel. On the first pixel I had to start from scratch and erase every remenant and download Android sdk and start over
Click to expand...
Click to collapse
You could have also used the sdk manager to update the platform-tools.
Is it too soon to start a bounty for a bootloader unlock? Do we even have any devs using this device(Lm-G710TM)? Im good for $100+.
It's not soon for USA unlocked (G710ULM) because 11th July was the release, till now why there's no bootloader for this unlocked variant! Already European variant enjoying root.
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
totally agree, this is a great and solid phone. Could use a few tweaks and it'll be even better!
Alcolawl said:
I usually give it like two months before I expect activity to pick up for new phones; even when owning Nexus phones. But, it's very discouraging to see how dead this place is, especially for any US variants. If there's no encouraging development for this phone by the time the Pixel 3 drops, I might just ditch this phone for that instead. This is a solid phone, but it could be absolutely great with a custom ROM/kernel.
Click to expand...
Click to collapse
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I know VZW it's all locked The OEM switch is missing also. I'm assuming for at least Verizon there needs to be an exploit if ever found.
For now, I am just talking about the TMO version.
-- Brian
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-g7-thinq/help/t-mobile-oem-unlock-t3833156
runningnak3d said:
For now, I am just talking about the TMO version.
-- Brian
Click to expand...
Click to collapse
Welcome aboard mate, been looking for your presence here but was doubting it as you don't have this device as of yet. I'm happy to see you and say that I was wrong, can't thank you enough for the work you have done on other devices.
Will be more than willing to help anyway I can, although I am currently on the sprint variant for the moment.
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
runningnak3d said:
Hey @ps3hacker3 Long time no speak
Yea, I have learned enough that it is getting a lot easier even if I don't have the phone. However, I am going to need some info from people that DO have the G710TM.
-- Brian
Click to expand...
Click to collapse
LG G710ULM owner here. I know it's not specifically a T-Mobile version but it does allow OEM unlocking by default. I could be wrong, but I'm guessing the differences between the G710TM and G710ULM aren't that big (if any at all). If you need any info from my end, let me know. I'd love to get the ball rolling on bootloader unlocks for this phone. Lots of untapped potential here.
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Upon rebooting into Bootloader I'm presented with a quick guide for unlocking the phone:
1) Read Device ID
:fastboot oem device-id
2) Write Unlock Key
:fastboot flash unlock unlock.bin
3)Check bootloader is unlocked
:fastboot getvar unlocked
fastboot oem unlock results in a FAILED (remote: 'unknown command') message. Screenshot attached. My first attempt didn't work because I guess I didn't have the right bootloader drivers installed.
So it looks like even the unlocked models are in the same boat as everyone else, except Europe.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
20degrees said:
The T-Mobile version has the oem unlock slider.
Edit: if I run the fastboot oem unlock command, nothing happens. The phone when using reboot bootloader, gives me 3 options. Get ID, check unlock, I forget the wording on the other, but it's basically to input your unlock file I think.
Click to expand...
Click to collapse
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Alcolawl said:
On my Windows 10 machine, when this phone is in Bootloader and plugged in via USB, Device Manager showed it as just "Android" with a warning symbol next to it. Had to grab the latest Google ADB and Fastboot drivers and force install the drivers (Choose from list, Have Disk..., Android Bootloader Interface, etc.) in order for the computer to actually recognize the phone properly when in the Bootloader. Otherwise issuing Fastboot commands just resulted in <waiting for any device> or whatever. Strange, because I haven't touched this OS install in probably a year and I had no problems issuing commands to my Pixel XL in Bootloader this spring.
Anyways, looks like until LG decides they want to support unlocking other variants, we're dead in the water.
Click to expand...
Click to collapse
Be forewarned, I've noticed that fastboot doesn't always work, despite latest drivers. As of late, the Pixel has been known to hang on these same commands at times as well. My Moto Z2 Force suffers from this error as well.
---------- Post added at 04:11 AM ---------- Previous post was at 04:04 AM ----------
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I hope you know many are INCREDIBLY excited to have you on board! I'm not advanced, but once I receive my computer back, I'll definitely be available to help with providing info and helping test, as I have a TMO variant (I may or may not work for TMO as well, so yeah... )
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Own a TMobile variant, oem unlocking option is there, fastboot commands do not work (or are extremely limited)
getprop | grep unlock (if it means anything)
[Ro.oem_unlock_supported]: [1]
[Sys.oem_unlock_allowed]: [1]
I know I probably didn't help out much, if you have any other questions feel free to ask I'll help out as much as I can. thank you for contributions and congrats on the V30 root.
runningnak3d said:
Now that I took care of the H932 V30 getting root, it is time to move on to you guys....
So, since I don't own this phone, I need some details if you guys would like me to help you get it rooted.
1 - Did T-Mobile pull fastboot oem unlock, or can you still at least unlock your bootloader?
2 - If they did pull the ability, how do other G7s unlock their bootloader?
3 - Can someone provide me with a dump of laf? Maybe there is a KDZ around here that I missed, but it is early, and I am not going searching just yet.
-- Brian
Click to expand...
Click to collapse
I have the tmobile variant. Let me know what you might need.
Unlock Slider is present in developer settings and is not greyed out. Unlock command just hangs.
runningnak3d said:
So you have the slider in developer options for "Allow OEM Unlocking" .. do you have fastboot oem unlock?
-- Brian
Click to expand...
Click to collapse
Sprint variant also has "Allow OEM unlocking" available and it is changeable
So you can issue fastboot flashing unlock_critical but not fastboot flashing unlock -- that is just weird.
If you issue the unlock_critical, do you get the warning that your phone is possibly corrupt, but will continue to boot?
-- Brian
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.