Just a thread for the few USCC people here - I've tried to UL the bootloader using TMO instructions - no go. It will reboot into the bootloader but it asks for the unlock.bin key (fastboot oem unlock returns an unknown command error). So at least theirs that much
Phone will also boot into recovery, and I get the associated normal options there (clear, mount /system, wide device/cache, load update via ADB, load update via SD, view recovery logs, etc). Interesting thing happens when I select "run graphics test" from the recovery menu - it gives an error, then the "no command" icon, then multicolor circles rotating - but it says "erasing" then "installing system update" then goes back to the recovery menu. Not sure if it's normal, but it's interesting.
I'm not a dev or a software guy really, but would like to hear some thoughts on the USCC version...would love to have root like the TMO - especially since it will get into the fastboot menu. Wish I knew more so I could be more help.
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Killah1994 said:
Same I'd like to here more about this since the unlocked version comes with an unlocked bootloader. I think it's because the T-Mobile version got released first so they had the jump start, and the unlocked version took till the 11th to be released so it's like we're late.
Click to expand...
Click to collapse
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
elliwigy said:
you are talking about three different devices lol.. apparently USCC v20 is locked like everyone else.. TMobile typically allows BL unlocks, not because it was out first? and the unlocked variant is obviously from LG and unlockable by default...
Click to expand...
Click to collapse
There you go, knew I was getting something mixed up.
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Sent from my LG-US996 using Tapatalk
jayochs said:
us996 comes with an unlocked bootloader? what? I'm pretty sure mines locked like the rest...
Click to expand...
Click to collapse
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
does he have a copy of the debug kernel? you can pm me a link if possible thatd be great so we can take a look at it.. if it is an eng kernel, it could potentially help to root other variants with locked BLs
---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------
Ephemera said:
I recommended the officially unlocked variant of the V20 to @Abumarf believing he'd have no issues whatsoever in unlocking the bootloader. He purchased one off eBay before the phone was officially released and I believe it came with a user debug kernel. It seems similar to the engineering kernels for Samsung devices, as he has root access through the adb shell. Unlike the temporary root method that @me2151 had posted, it can survive reboots. Yet I'm surprised the fastboot command to unlock the bootloader returns with failure.
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
---------- Post added at 02:41 AM ---------- Previous post was at 02:41 AM ----------
Abumarf said:
I seem to have a US996, but I got it early on. I believe it to be bootloader locked though, even though it's a developers device. I'm almost 100% sure it's the sim unlocked version as I tried a few sims and they worked. Anything I can do to help?
Click to expand...
Click to collapse
can you upload your aboot and kernel etc? if theyre eng or debug files im interested to check them out
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
hopefully you are able to as it shouldnt really take any time at all lol.. it would really help a lot of ppl out if it is in fact a debug kernel..
the root we have is a temp tcp root shell using a context we cant really do anything we need to do at all so it was pretty much a dead end so far
Abumarf said:
@elliwigy I will most likely be selling the phone or handing it over to @Ephemera as I can't use it as a daily driver. We'll update you on what happens. If we do decide to sell, I'll see if we can extract and send them your way before we do.
Click to expand...
Click to collapse
I will pay you for the debug files
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
you wont b doing anything to the phone.. if u have an adb root shell would just be copying a few files from the phone.. we can even tell you exactly what commands to use to make it easy.. we can invite you to a google hangout even so we can explain each step
Abumarf said:
I'm no developer or modder. I don't know too much about all that. I would rather not play with it, and that's the reason I'm selling it.
Click to expand...
Click to collapse
Whay are you asking for the phone?
I was looking to get what I spent for it, around $800
elliwigy said:
if u read my previous post u can see i said the uscc BL is locked lol like everyone else
Click to expand...
Click to collapse
yeah, the US cellular us996. it's different from the American unlocked us996. according to LG anyway, it lists it as two different phones.
I'm not on a US cellular one. I'm in an unlocked one with Verizon. the post above you said unlocked had unlocked bootloader. mines as unlocked as you get, and it doesn't have an unlocked bootloader.
Sent from my LG V20 US996
http://developer.lge.com/community/...nuId=38&contsTypeCode=QUE&prodTypeCode=MOBILE
Make yourselves heard. Let LG know we want the bootloader to be unlockable on the US996. I've talked to their live chat and they claim that they "didn't know people would want to unlock their bootloader". Show them we do.
Abumarf said:
I was looking to get what I spent for it, around $800
Click to expand...
Click to collapse
Ok if you download terminal emulator and type in get prop and send me the screen shots so i can verify it is indeed a debug kernel i will buy it from you but i would like to have proof of debug kernel
Sure, here it is: https://drive.google.com/file/d/0BwI6DTQJV37Ob1BwRkRab0xPRkk/view?usp=drivesdk
Also the phone is already up on Swappa
---------- Post added at 08:45 PM ---------- Previous post was at 08:36 PM ----------
@rickberg forgot to tag you
Related
Has anyone thought that maybe google has made 2.3 unrootable? Scary thought i know, but its kind of like a cat and mouse game with the developers and google/manufacturers with root patches.
Maybe google finally will put the nail in the coffin here?
WOOT. It's rooted, im happily wrong.
It's a developer phone, so why would Google want to make devs waste time trying to root.
could it be possible that Google enable root access by default, then?
djfoo000 said:
could it be possible that Google enable root access by default, then?
Click to expand...
Click to collapse
Definately not.
Dev phones have always been rootable, i doubt that will change.
The phones that have trouble being rooted are always manufacture customized ones.
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
I'd bet that it will be rooted BEFORE!
The developer build on my Nexus One is already rooted. I don't imagine the release build will be any different from all of the previous OTAs.
jroid said:
it's still able to fastboot oem unlock from what i've heard. Will be rooted same day it's available for purchase guaranteed.
Click to expand...
Click to collapse
You are correct.
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
fastboot oem unlock
FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Your right, as of now I don't think Samsung locked any of their phones, but the only thing Samsung has on this phone is the hardware aspect. All the software aspect is by Google.
FPRobber said:
Samsung never locked their (Android?) phones. Personally I've installed custom ROMs on the Galaxy Spica and international S and both came factory unlocked. Unlike with some of HTC's devices you can flash anything you want without using exploits.
Click to expand...
Click to collapse
Then how do you explain threads like this (on the samsung galaxy sub forums):
[HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!]
It seems like you have carrier/sim lock and root confused. Just like nearly every phone on the market, they are locked. You will also need root to do anything that says "please root your phone". They do not ship this way...
I'm sure it will be rootable... Google doesn't want to block out developers
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
Very true
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
luckyduck69 said:
Look right above the Youtube icon.... http://www.google.com/nexus/#!/features
Click to expand...
Click to collapse
that's unlocked for carriers with gsm...that's not root. Simply meaning it will work with at&t or tmobile by changing the sim card. Root lets you edit system files and a custom recovery to flash roms
Lmao no one so far in this thread should get one of these developer phones as you plainly do not understand what you are doing here when it comes to deciding what the difference is between root permissions and unlocked to all networks.
lets put it this way, if you are one of the above who are having trouble, dream on and steer clear from the prospects of rooting all together
unless that is you fancy yourself a very expensive paperweight?
Igotsanevo4g said:
Just food for thought i guess, we cant know until its released anyways.
What exactly is fastboot oem unlock ?
Click to expand...
Click to collapse
This command unlocks your bootloader on the N1/N-S allowing you to flash custom roms, but visibly voids your warranty (bootloader screen shows that it's unlocked)
Can you use a Verizon bootloader locked Pixel 2 international? With another simcard?
And is it possible to flash an ota file from Google on it and not the Verizon version? Or is that not needed?
Thanks
I'm pretty sure all phones manufactured after a certain year(think it was 2014) were made so they can be used anywhere. As long as it has the necessary bands. You will not be able to flash other firmware, unless the bootloader gets unlocked and root becomes available...
Sent from my Pixel 2 XL using Tapatalk
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
mikeyinid said:
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
Click to expand...
Click to collapse
It's not quite the same. It is unlocked, but the bootloader cannot be unlocked.
Erik1805 said:
Can you use a Verizon bootloader locked Pixel 2 international? With another simcard?
And is it possible to flash an ota file from Google on it and not the Verizon version? Or is that not needed?
Thanks
Click to expand...
Click to collapse
Yes, you can use the Verizon version withe the locked bootloader, internationally. I have one in the EU, running on Vodafone. Runs without issues.
Verizon prevents you from getting over the air updates unless you have an activated Verizon sim and the phone comes with a deactivated Verizon sim pre-installed. When I got mine it was two versions behind and on the September security patch. I tried all sorts of tricks to get it to update with my Vodafone sim, with the Verizon sim, but the best I could get it to do was say there was an update available before it bailed out one me. However, using adb and the Google images for OTA's they provide I was able to flash each update no problem using a USB cable.
Hope this helps!
Lenny
---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------
mikeyinid said:
The Verizon version is EXACTLY the same as the Google version. It is unlocked and will work anywhere in the world. Since software updates come directly from Google you won't have to worry about getting OTA's either.
Click to expand...
Click to collapse
Just an FYI, they are slightly different. The phone itself is carrier unlocked. Any carrier can use the Verizon version just like a non-Verizon version. The difference is the Verizon bootloader is locked down, can't unlock that (unless you got one way early, on 7.1 or something like that). You also only get OTA updates for the Verizon version if you have an active Verizon sim in the phone. Manually updating using the OTA files from Googles website works with ADB, so not a big deal, but makes it a little more manual and technical than it would be otherwise. You'll notice there are different OTA's and different versions used for Verizon's files - keeping them slightly different.
IDroidThere4Iam said:
Yes, you can use the Verizon version withe the locked bootloader, internationally. I have one in the EU, running on Vodafone. Runs without issues.
Verizon prevents you from getting over the air updates unless you have an activated Verizon sim and the phone comes with a deactivated Verizon sim pre-installed. When I got mine it was two versions behind and on the September security patch. I tried all sorts of tricks to get it to update with my Vodafone sim, with the Verizon sim, but the best I could get it to do was say there was an update available before it bailed out one me. However, using adb and the Google images for OTA's they provide I was able to flash each update no problem using a USB cable.
Hope this helps!
Lenny
---------- Post added at 01:04 PM ---------- Previous post was at 01:00 PM ----------
Just an FYI, they are slightly different. The phone itself is carrier unlocked. Any carrier can use the Verizon version just like a non-Verizon version. The difference is the Verizon bootloader is locked down, can't unlock that (unless you got one way early, on 7.1 or something like that). You also only get OTA updates for the Verizon version if you have an active Verizon sim in the phone. Manually updating using the OTA files from Googles website works with ADB, so not a big deal, but makes it a little more manual and technical than it would be otherwise. You'll notice there are different OTA's and different versions used for Verizon's files - keeping them slightly different.
Click to expand...
Click to collapse
You can't flash images on the Verizon version. The bootloader needs to be unlocked, and that obviously isn't happening. I don't think it matters which sim you have in the Verizon version, you'll get OTA updates no matter what. The phones aren't as different as you guys think. The only reason there are different factory images for the Verizon version is they install Verizon bloat on first boot.
mikeyinid said:
You can't flash images on the Verizon version. The bootloader needs to be unlocked, and that obviously isn't happening. I don't think it matters which sim you have in the Verizon version, you'll get OTA updates no matter what. The phones aren't as different as you guys think. The only reason there are different factory images for the Verizon version is they install Verizon bloat on first boot.
Click to expand...
Click to collapse
You can ADB sideload. Did the same this week. No problems. You just cannot flash a another room.
Erik1805 said:
You can ADB sideload. Did the same this week. No problems. You just cannot flash a another room.
Click to expand...
Click to collapse
How do you adb sideload with a locked bootloader?
mikeyinid said:
How do you adb sideload with a locked bootloader?
Click to expand...
Click to collapse
Used this. Went great.
https://developers.google.com/android/ota
Erik1805 said:
Used this. Went great.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
Yea, we're talking about two different things.
mikeyinid said:
Yea, we're talking about two different things.
Click to expand...
Click to collapse
Yes thought so. No custom rom flashing for me, thats what you ment
Erik1805 said:
Yes thought so. No custom rom flashing for me, thats what you ment
Click to expand...
Click to collapse
But, I just learned something because I had no idea Google posted the OTA files like that
Erik1805 said:
Used this. Went great.
https://developers.google.com/android/ota
Click to expand...
Click to collapse
this is an old post but im trying to see if anyone can help me with this adb sidload. I get an error that footer is wrong and cant get the android P beta to flash. any thoughts?
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
wheelbarrel said:
I had my bootloader unlocked since the pixel came out, and just recently re-locked it through SkipSoft Android ToolKit. I needed to use the Android Pay and didn't have the time to figure out and install Magdisk. I had foolishly assumed that since it was already unlocked that I could easily unlock it again. I was wrong lol. I tried several times in the toolkit with no success.
Is there any hope for this pixel?
Click to expand...
Click to collapse
If it's a Verizon one probably not. If it's a Google store pixel, Yes just unlock it again. It will wipe again.
Why did you relock it in the first place
KittyRgnarok said:
Why did you relock it in the first place
Click to expand...
Click to collapse
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
KittyRgnarok said:
Magisk very easily fixes Android pay not working with an unlocked phone. There are like 3 different threads specifically saying hey there is no real reason to ever relock this phone and if you do to be extremely careful
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Also you purchased it through Verizon so no it isn't easy to reunlock. You will be stuck with the locked bootloader for the foreseeable future. For future reference do not ever buy a phone you intend to mod from Verizon or AT&T
Click to expand...
Click to collapse
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
b00ster23 said:
Yeah, it does appear that you'll be stuck with a locked bootloader on the Verizon branded phone. I believe that BigRed is using the IMEI number so regardless of SIM, the 'mothership' sends out the command to lock it down. However, I would be interested to see what would happen if you send the OEM Unlock command.
And as far as saying that "do not ever buy a phone you intend to mode frrom VZW or AT&T" not sure I agree entirely...but certainly have to know the risks and limitations, especially if exploits are found. That's one of the reasons I don't use automated kits. I need to know exactly what's happening and commands being sent to my VZW phones. I've been on Verizon and AT&T for quite some time. However, I always find a phone that has an exploit for root. Good luck!
Click to expand...
Click to collapse
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
KittyRgnarok said:
Using them as a carrier is (almost) fine, but it shouldn't be necessary to use an exploit to unlock your phone and they do shady custom bootloader **** on almost all of their phones
Click to expand...
Click to collapse
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
b00ster23 said:
Yup... agreed. Shouldn't be necessary, but unfortunately the law is in their side. They lock bootloaders to offset reduced hardware pricing, in an effort to cut support cost and limiting possible bricked phones. Trust me don't like it, but if I can get a significantly reduced cost on the phone, and have full admin rights....uhhhh thank u...
Click to expand...
Click to collapse
Tru Tru
wheelbarrel said:
I needed to use Android Pay, the Tap 'n Go feature. I didnt have time to figure out how to hide root so the app would work. I just thought since it was already unlocked it could easily unlock. I guess I am staying stock lol
And it was purchased through verizon but is now on T-Mobile.
Click to expand...
Click to collapse
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Poebat said:
My pixel passed safety net without any issues with an unlocked bootloader running a custom kernel without root. I don't think safety net checks the bootloader (could be wrong)
Click to expand...
Click to collapse
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
Ah. I figured that might be the case.
b00ster23 said:
Yes Safety Net does check the BL. The reason yours passes is because of the custom kernel. I seen a post for an 'almost' stock kernel for the PIXEL2 that passes SN, without root if that's all u need. The kernel has a patch for only the Safety Net. But again that's the PIXEL2
Click to expand...
Click to collapse
I mean almost every custom kernel for pixel og has proper safety net support
I appreciate all your input everyone! Unfortunately I am going to have to wait until it's time to buy a Pixel 2 lol, which is getting close
This is proof you should read EVERYTHING first lol
These may be stupid questions but I have tried everything I can think of.
I am on a Verizon pixel 2, locked bootloader, running the current release of android 9.
I am unable to toggle the "OEM Unlocking" option in developer settings
I followed this guide to enable the toggle but ADB/Fastboot still gives me the "Flashing Unlock is not allowed" message when i try to run "fastboot oem unlock" or "fastboot flashing unlock".
Ultimately I would like to be able to root my Pixel 2, but right now I would settle for being able to downgrade Google Play Services to version 12.6.85 because reasons. There does not appear to be a compatible APK for this version of play services and Android 9 on the Pixel 2 (that I have been able to find yet)
Is anyone aware of how I could do the following:
1. unlock my bootloader?
or
2. downgrade to any android 8 version?
or
3. downgrade google play services to 12.6.85 on Pixel 2 Android 9?
The guide you posted is for the original Pixel.
Verizon Pixel 2 has a locked bootloader, and Verizon has disallowed the option of unlocking.
Early in the year, a user here stumbled upon a few commands that would bootloader-unlock the vzw p2. However, any firmware past January (I think) has been updated to protect against this exploit. So you missed the window on that.
I don't think android allows downgrading while the bootloader is locked.
I'm not sure about downgrading play services, but you could easily get the desired .apk from apk-mirror, and attempt to install it. I'm guessing you're going to get an error. In that case, considering you don't have system r/w permission, I don't see any way you'd be able to downgrade play services.
So, short of someone coming along and finding another way to bypass vzw's restrictions, you're stuck on 9.
use skipsoft android toolkit.
bmw9651 said:
use skipsoft android toolkit.
Click to expand...
Click to collapse
That won't work. You can't downgrade to an earlier version, and if you've taken any updates past the January VZW variant, nothing can be done. Sorry....
I was able to wipe system and install 8.1.0 after bricking on 9 pie.
bmw9651 said:
I was able to wipe system and install 8.1.0 after bricking on 9 pie.
Click to expand...
Click to collapse
With a locked bootloader on a Verizon Pixel 2?
yes I wiped it and went back to 810. bootloader has been unlocked as well. use fastboot and adb....... code: fastboot flash lock_critical. to unlock BL.
use skipsoft tool kit to wipe and reinstall OS to 8.1.,0.
bmw9651 said:
yes I wiped it and went back to 810. bootloader has been unlocked as well. use fastboot and adb....... code: fastboot flash lock_critical. to unlock BL.
use skipsoft tool kit to wipe and reinstall OS to 8.1.,0.
Click to expand...
Click to collapse
What I'm getting at is that your bootloader was unlocked _before_ you did everything. OP doesn't have that luxury.
DuckRuckus said:
What I'm getting at is that your bootloader was unlocked _before_ you did everything. OP doesn't have that luxury.
Click to expand...
Click to collapse
Yeah he's full of it if he's saying otherwise. There is no way it would let you downgrade bootloaders in stock recovery.
Yes BL was unlocked before doing the change. I just rooted it with the skipsoft toolkit Magsik way. after trying others on it. with the skipsoft toolkit you can wipe it and go back to jan 2018 builds of you wish. there are many options on it to choose from.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
when i got my pixel 2 first thing I did was unlock boot-loader. fastboot flash lock_critical. is the command to do this . To the OP don't worry too much the pixel 3 is coming out soon. BUY it From the Google Store. you will be able to unlock BL and do as you please. DO NOT Buy from Verizon.
bmw9651 said:
Yes BL was unlocked before doing the change. I just rooted it with the skipsoft toolkit Magsik way. after trying others on it. with the skipsoft toolkit you can wipe it and go back to jan 2018 builds of you wish. there are many options on it to choose from.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
when i got my pixel 2 first thing I did was unlock boot-loader. fastboot flash lock_critical. is the command to do this . To the OP don't worry too much the pixel 3 is coming out soon. BUY it From the Google Store. you will be able to unlock BL and do as you please. DO NOT Buy from Verizon.
Click to expand...
Click to collapse
unless you need to get an RMA, in which case you get a device that cannot be unlocked, like mine for example.
crixley said:
unless you need to get an RMA, in which case you get a device that cannot be unlocked, like mine for example.
Click to expand...
Click to collapse
By that do you mean that you submitted a warranty claim to google? You must not have. I am a Project Fi customer so I never have to think about such things. But yeah, if you bought your pixel from the google website, hooked it up to Verizon service and THEN called Verizon customer service and requested a warranty replacement or an Insurance claim then yeah. In that case you probably would receive a device with a locked bootloader because that's all Verizon deals with as far as I know. I submitted a warranty claim to Project Fi and The device they sent me came with an unlocked bootloader. I think I would have thrown a fit if they had sent a locked one. I would have been on the phone with a Supervisor stating that "the unlocked bootloader feature was 100% the reason I chose to buy the phone directly from google!" I would not have left them alone until I got my way. lol
KirkH420 said:
By that do you mean that you submitted a warranty claim to google? You must not have. I am a Project Fi customer so I never have to think about such things. But yeah, if you bought your pixel from the google website, hooked it up to Verizon service and THEN called Verizon customer service and requested a warranty replacement or an Insurance claim then yeah. In that case you probably would receive a device with a locked bootloader because that's all Verizon deals with as far as I know. I submitted a warranty claim to Project Fi and The device they sent me came with an unlocked bootloader. I think I would have thrown a fit if they had sent a locked one. I would have been on the phone with a Supervisor stating that "the unlocked bootloader feature was 100% the reason I chose to buy the phone directly from google!" I would not have left them alone until I got my way. lol
Click to expand...
Click to collapse
Yes, as have many others. I'm from Canada, device was bought through google and RMA'd through google. Has nothing to do with Verizon, there are tons of threads about it.
Another alternative, albeit a bit more convoluted, would be to update your current device to the latest update. Back up your user data as best you can, then factory reset, put it on Swappa, and then use the proceeds to purchase a secondhand Google variant with identical specs as the original. At least that way you won't have to deal with any more bootloader shenanigans. If your device is still in good shape and you're savvy enough about it, you may be able to come close to break-even.
I have an option to get new phone with contract reneval. I like devices with strange "additions", thats why I had Moto Z3 Play before. And now I'm thinking about Velvet coz of it's Dual Screen.
However I need root for few apps I use (some for my own usage, some work related).
Do You believe that there will be a way to root Velvet in the nearest feature? Or ever?
I'm more asking if You believe there will be a way to fash Magisk patched kernel.
I know that nonflagship LG device doesnt even have an option to unlock bootoloader nd even the flagships (V60?) have blocked fastboot command, so unlocking does nothing...
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0703
Sad to see this after I chose something else...
Still, as I read about other LG devices it seems that unlockable bootloader doesn't have to mean that there is access to fastboot commands. An without that there is no reason to unlock it.
I thought about a new phone for a long time and I hope you are wrong. because I chose velvet. previously i had g6 and i already miss & root mods a lot. and what did you buy?
Realme X3 Superzoom. At least there is a root solution already
And they should share the sources like they did with older devices.
I'll miss the 2nd screen, but... Had a chance to play with it and my carrier gives it for free (screen or headphones) along with 3rd year of warranty.
I waiting for headphines ? they add choice (screen or it) after i buy phone :laugh: and i worry about lg is coming down with smartphone ... Have nice day and good luck with powerusing :victory:
Headphones? I'd choose the screen. F**k their DAC
Maybe one day I'll get LG with Dual Screen? Will see. As I signed the contract in the store I have no way to change it (not sure if I want to).
Anyway, nice day to You too. I miejmy nadzieje, ze znajdzie sie sposob na roota na Velveta
support unlocking the bootloader: • LG VELVET: LMG900EM/LMG
The following devices support unlocking the bootloader:
• LG VELVET: LMG900EM/LMG900EMW/LMG900EMX/LMG900D for the European market
dietoro said:
The following devices support unlocking the bootloader:
• LG VELVET: LMG900EM/LMG900EMW/LMG900EMX/LMG900D for the European market
Click to expand...
Click to collapse
I’ve been seeing the LMG900M a lot on ebay, wondering if this works too as i haven’t seen it on this list?
In the dark
Is there anyway us as a collective to unlock the bootloader ourselves. I literally don't know like I'm very new to this and want to try it out a rooted device
got a velvet.
unlock bootloader was no prob.
but stock roms are in kdz format. uncompressable since last dev of un-kdz un-dz seems to support just old and smaller formats.
tried several boot.img's and twrp's that seem to be same chipset.
nothing worked so far. hopin some of the rom-gurus gets hot on that dual-screen feature/case...which works really good.
i didnt get it to work with root, but i dont give up hope.
---------- Post added at 09:47 PM ---------- Previous post was at 09:30 PM ----------
Catrock31 said:
Is there anyway us as a collective to unlock the bootloader ourselves. I literally don't know like I'm very new to this and want to try it out a rooted device
Click to expand...
Click to collapse
just complete the process that wifredzik posted as link.
you ll get an unlock file from lg immediately.
enable developer options on your phone and in the following usb debugging.
boot into bootloader via adb and unlock as lg describes in the manual.
thats whats worked for me so far.
payed around with stock roms of other new mobile-phones that have the same chipset to extract the boot.img and modify it with magisk.
my strategy is to boot in with root, but without flashing partitions so that i can dump the original boot.img and modify with magisk just to flash it back.
but no other boot.img worked so far.
if there is somebody out there who can breakup the lg velvet stock rom (kdz-format) to intact img files please let me know.
BR
Mike
MikGx said:
got a velvet.
unlock bootloader was no prob.
but stock roms are in kdz format. uncompressable since last dev of un-kdz un-dz seems to support just old and smaller formats.
tried several boot.img's and twrp's that seem to be same chipset.
nothing worked so far. hopin some of the rom-gurus gets hot on that dual-screen feature/case...which works really good.
i didnt get it to work with root, but i dont give up hope.
---------- Post added at 09:47 PM ---------- Previous post was at 09:30 PM ----------
just complete the process that wifredzik posted as link.
you ll get an unlock file from lg immediately.
enable developer options on your phone and in the following usb debugging.
boot into bootloader via adb and unlock as lg describes in the manual.
thats whats worked for me so far.
Click to expand...
Click to collapse
Problem, i got the Canadian version witch is not one of the models listed on their site
Catrock31 said:
Problem, i got the Canadian version witch is not one of the models listed on their site
Click to expand...
Click to collapse
hm...i would try it anyways.
the worst that can happen is that lg dont sends back the unlock.bin.
iv`e taken a look inside the file.
its encrypted. so, no way to create it the easy way by yourself...
br
Mike
Lg Velvet Stock Ringtones
Anyone could please upload the stock ringtones? thanks
Root LG Velvet (LM-G900EM)
As i've found a way to root the Velvet i opended a new thread ind the Velvet section.
Have fun!
BR
Mike