Related
Hey folks,
Long story short, I got rid of my 6P for an iPhone. I switch back and forth every year between both platforms, but man i'm missing android really bad lately, after only 2 months.
Can you root, unlock the bootloader, or put a custom kernel on the verizon pixel?
I dont really care for ROMs because flashing was becoming too time consuming, I just want stock image with a kernel.
Thanks,
Kinesics
With the release of Android 7.1.1 two days ago you can no longer unlock the Verizon bootloader using the depixel8 exploit. Of course if you get a phone that hasn't updated yet and can prevent that update you can unlock it.
I suggest you buy the Google store version instead. Fully unlockable and 100℅ compatible on Verizon. Even Verizon video chat works on the non Verizon one.
larsdennert said:
I suggest you buy the Google store version instead. Fully unlockable and 100℅ compatible on Verizon. Even Verizon video chat works on the non Verizon one.
Click to expand...
Click to collapse
I would but my connect at Verizon is letting me do a return on my iPhone after 60 days, so really I'd pay nothing. Since the patch just came out 3 days ago I'm pretty sure i can find a phone thats been sitting on the self for 2 weeks.
kinesics said:
I would but my connect at Verizon is letting me do a return on my iPhone after 60 days, so really I'd pay nothing. Since the patch just came out 3 days ago I'm pretty sure i can find a phone thats been sitting on the self for 2 weeks.
Click to expand...
Click to collapse
Totally get that, some of the vzw deals are amazing. Just be careful when you first turn it on, read the various threads here and in the Pixel XL forums. Some say you can bypass setup to depixel8 and others have not been able to. Simply, plan it out really thoroughly.
As for just unlocking in order to install a kernel, I'm not really sure you need it. I've been bootloader locked since DP2 on my N5x and battery life is amazing on that and this device. So if you do unlock then update to 7.1.1 after that and run stock kernel for a week. You might want to give up flashing all together.. well other than the OTA which you can sideload.
rpjwalter said:
With the release of Android 7.1.1 two days ago you can no longer unlock the Verizon bootloader using the depixel8 exploit. Of course if you get a phone that hasn't updated yet and can prevent that update you can unlock it.
Click to expand...
Click to collapse
kinesics said:
I would but my connect at Verizon is letting me do a return on my iPhone after 60 days, so really I'd pay nothing. Since the patch just came out 3 days ago I'm pretty sure i can find a phone thats been sitting on the self for 2 weeks.
Click to expand...
Click to collapse
I've had mine for about 36 hours. It's unlocked and rooted already!
Got my Pixel last week followed the steps and I'm in business. Unlocked and feeling right at home, no more sea of icons!
bobby janow said:
Totally get that, some of the vzw deals are amazing. Just be careful when you first turn it on, read the various threads here and in the Pixel XL forums. Some say you can bypass setup to depixel8 and others have not been able to. Simply, plan it out really thoroughly.
As for just unlocking in order to install a kernel, I'm not really sure you need it. I've been bootloader locked since DP2 on my N5x and battery life is amazing on that and this device. So if you do unlock then update to 7.1.1 after that and run stock kernel for a week. You might want to give up flashing all together.. well other than the OTA which you can sideload.
Click to expand...
Click to collapse
Thanks for help, went with stock OS and Franco kernel. I just cant be 100% stock. I did stay all stock for a few days but ultimately enjoy Franco's work.
Hey everyone I was just wondering if anyone who has the Nougat Beta, have you gotten the official update yet? and if so when is the soonest we could possibly be getting a zip file? I tried the VZW version and it was smooth for about the first week, then I noticed some random rebooting and battery life issues as to be expected since it was only a first beta version. Not rushing anything but I'm a little impatient as well as some of you are to get your hands on the Nougat goodness. The whole reason for me even flashing the TMO version is because I bought the Metro PCS version and usually their updates roll out a lot later than TMOs updates. Thanks all
jawshdarnit said:
Hey everyone I was just wondering if anyone who has the Nougat Beta, have you gotten the official update yet? and if so when is the soonest we could possibly be getting a zip file? I tried the VZW version and it was smooth for about the first week, then I noticed some random rebooting and battery life issues as to be expected since it was only a first beta version. Not rushing anything but I'm a little impatient as well as some of you are to get your hands on the Nougat goodness. The whole reason for me even flashing the TMO version is because I bought the Metro PCS version and usually their updates roll out a lot later than TMOs updates. Thanks all
Click to expand...
Click to collapse
Only uk have it so far China is being delayed and T-Mobile (obviously) is coming out later this month if not well **** me and call me billy
Anyone else get an update yesterday?
Yes, got it on mine last night. No clue what it supposedly does yet. Probably just the July security update.
The update notes said it fixed something with corporate email performance and integrated typical android security updates....took it today, i dont notice anything new.
I cannot install the update on any of my rooted phones (which isn't a huge surprise to me). However, the update has been out for a few days, and I haven't seen anything about the update here on the forum until today. I'm hoping someone posts an update method for those of us with rooted phones.
Does anyone know can we use BT firmware from S6 onto S7? I have problem connecting my car hands free system, thought no such problem with S6
BQG1 improves network speed.
Averix said:
Yes, got it on mine last night. No clue what it supposedly does yet. Probably just the July security update.
Click to expand...
Click to collapse
Got the BQG1 update on 7/29 and after stabilizing for an hour ran speed test via WiFi. I had noticed a drop to around 140Mbps on my Comcast service with the last update and couldn't figure out why. With BQG1, my downlaod speed is back up to 230Mbps and running very smooth. Don't know what VZ did, bit it works!
Hope that helps.
neyenlives said:
The update notes said it fixed something with corporate email performance and integrated typical android security updates....took it today, i don't notice anything new.
Click to expand...
Click to collapse
I wanted to give a quick update.
Following suggestions I found on a few threads here, I went ahead and updated all three of my rooted phones to firmware QH1 on Friday, and they are all still rooted.
I used ODIN to re-flash the stock firmware (using HOME-CSC to keep my apps and settings intact. I downloaded the firmware from one of the links I found here on XDA.
I then re-rooted using the procedure in the OP.
I had two issues (that I can think of):
1. A few of the settings (lock screen settings, specifically - maybe one or two others?) were cleared in the process - and I had to set them up again.
2. One of the phone (the one *I* use, of course), rooted okay, but SuperSU was missing after the reboot. Installing it from the Play store appeared to break root. So I just re-rooted it again.
Other than those issues, I think everything else went pretty smoothly.
I hope this is helpful to others.
Maybe there is already a thread of this somewhere already, but I didn't see one, apologies if it is, just thought I'd share my thoughts. Or maybe this is just super obvious so nobody posted about it. Anyway...
So as of the time of this writing they're still accepting people into the Oreo Beta. I only registered my phone about an hour ago (just before midnight, Nov. 1st) in the Samsung+ app and it let me get the Beta, so I imagine all the spots aren't full yet.
To those of you on the wrong carrier (But still in the U.S.) the process is easy! Simply go to this tutorial HERE to flash the unlocked firmware on your device.
After set-up, download the Samsung+ app, and register for the beta. Then, head to "Update" in your settings, and search for updates. It will have to go through *every* update between that firmware and the latest release, before finally downloading Oreo. My phone updated *four times* so be prepared to waste some time.
cadetprewitt1992 said:
Maybe there is already a thread of this somewhere already, but I didn't see one, apologies if it is, just thought I'd share my thoughts. Or maybe this is just super obvious so nobody posted about it. Anyway...
So as of the time of this writing they're still accepting people into the Oreo Beta. I only registered my phone about an hour ago (just before midnight, Nov. 1st) in the Samsung+ app and it let me get the Beta, so I imagine all the spots aren't full yet.
To those of you on the wrong carrier (But still in the U.S.) the process is easy! Simply go to this tutorial HERE to flash the unlocked firmware on your device.
After set-up, download the Samsung+ app, and register for the beta. Then, head to "Update" in your settings, and search for updates. It will have to go through *every* update between that firmware and the latest release, before finally downloading Oreo. My phone updated *four times* so be prepared to waste some time.
Click to expand...
Click to collapse
Why do you say non tmo
pro_granade said:
Why do you say non tmo
Click to expand...
Click to collapse
Because so far only t mobile and Sprint carriers and g950u1 users can get the beta. Other carriers can't so that's why he said for non tmo and Sprint users
adj998 said:
Because so far only t mobile and Sprint carriers and g950u1 users can get the beta. Other carriers can't so that's why he said for non tmo and Sprint users
Click to expand...
Click to collapse
It's closed now, they removed the script to even bring the beta button onto the app, if you use the fiddler thing to make it come up, it makes no difference, and I private glitch I had to get the beta signup to come up doesn't work either.
pro_granade said:
It's closed now, they removed the script to even bring the beta button onto the app, if you use the fiddler thing to make it come up, it makes no difference, and I private glitch I had to get the beta signup to come up doesn't work either.
Click to expand...
Click to collapse
That's too bad. I lost beta apparently. I was running TURBO rom and registered then I flashed g950u1 firmware, still had the beta but after 12 hours I never got the update, now I'm back on VZW AQJA firmware and it's gone. Oh well, maybe someone will make a flashforward zip or I cross my fingers and Samsung releases this sometime early next year
Is anyone else still waiting for the December update to be available for OTA download? Google Pixel 3, unlocked, not rooted, not happy. Never waited this long before.
Is it a Verizon phone? Verizon updates are supposed to roll out this week. The update for non-Verizon phones was available last Monday.
I don't get OTA updates on my rooted phone because of root. I don't know if just being unlocked prevents OTA. You can always download the factory image and manually update. The images are at https://developers.google.com/android/images.
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Fat fingers! 1st sentence intended to be "Thank you for the response".
BlackKeys said:
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Click to expand...
Click to collapse
In that case, you will have to apply the update manually. The factory image is at the URL I gave previously. Edit flash-all.bat/sh to remove the -w from the last line in the file so the phone is not wiped.
You could also apply just the OTA manually. The OTA images are at https://developers.google.com/android/ota. I have not done that - I use the factory image method.
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
BlackKeys said:
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
Click to expand...
Click to collapse
You can search for update errors in logcat. See https://forum.xda-developers.com/t/tutorial-how-to-logcat.1726238/ on how to get a logcat. If you did the manual "Check for update" look in the log at the time you did the check. Logs are kept for quite a while, so the info should still be available.
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
dcarvil said:
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
Click to expand...
Click to collapse
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
TonikJDK said:
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
Click to expand...
Click to collapse
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
dcarvil said:
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
Click to expand...
Click to collapse
That has always been there, very sure of that. A lot of us went done that rabbit hole with the Pixel 1 or 2. We never new for sure what it did, but I remember freezing it and had all kinds of connection problems.
Other carriers have those types of things too. They are built into the image and go live when the phone sees what carrier it is on.