Pretty self explanatory. I have the update pending for 8.0 but I've heard mixed reviews of the Oreo updates. So please, if anyone can be honest and tell me weather to proceed, or should I wait and why. Thanks you.
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
liriolebron said:
If it's a Verizon model you just have a gem in your hands, look on how to unlock the bootloader before update, if it's a Google version, then all you get are improvements and new features without compromises.
Click to expand...
Click to collapse
What's the best way to check if it's Verizon? And I don't need to root or anything honestly. I'm asking if the bugs with 8.0 are worth updating at the current state.
I recommend unlocking bootloader first and then update
So by unlocking the bootloader, I won't run into problems taking official updates?
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
No. If you modify system (root, Magisk, custom ROMs/kernels, TWRP recovery, etc) then you won't be able to take official OTA updates. But you can take them just fine with an unlocked bootloader.
Also, I'm on stock 8.1 and have no issues to speak of. I say go for it.
Sent from my Pixel XL using Tapatalk
nellycruzz said:
So by unlocking the bootloader, I won't run into problems taking official updates?
Click to expand...
Click to collapse
FYI If phone is a Verizon version an on 7.1.1 you are able to unlock it. If you update beyond 7.1.1 without unlocking you will Never be able to unlock it. If it's a Google version no worries.
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
asj0422 said:
There's no reason to unlock the bootloader if you're not rooting. That's just introducing a security issue. The Oreo update is safe and stable to install. You're good to go on hitting that update button.
Click to expand...
Click to collapse
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Sent from my Pixel XL using Tapatalk
borxnx said:
I disagree. On rare occasion, the OTA update can cause issues, and with a locked bootloader you are unable to install an image. Even if I don't root my devices, I still unlock the bootloader just so I can have the option of installing a factory image just in case something goes wrong.
Click to expand...
Click to collapse
He's right though. Unlocking will lead to security issues and may take away the ability to use important apps. If he prioritizes functionality, then it's best to keep it locked but if he wants to tinker, it'll come with compromises.
Since he just bought it, I don't see why he couldn't just warranty it if an update goes wrong, which is extremely rare. From what I've seen from people with bricked devices, the majority of them were unlocked and tried to update using non-conventional ways.
Bootloaders are locked from factory for a reason, not for inconvenience.
Related
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Fakusnamus said:
I've heard that using towelroot will root your phone but not unlock your bootloader. What does this entail? Can I still use Xposed Installer/ other root apps? Can I recieve OTA updates? Can I unroot again? Are there any downsides?
Looking forward to hearing about any experiences with this app.
Click to expand...
Click to collapse
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
But...
utsmaster18 said:
I just got my N7 and I unlocked the bootloader. I then used towelroot to root it and it worked fine. I have not flashed a custom recovery so I don't think OTA should be an issue.
Click to expand...
Click to collapse
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Fakusnamus said:
It's just that some of my other devices (samsung ones, admittedly) don't get OTA updates since I've rooted them, even though they're available. I've also heard that rooting most devices sort of cuts off the updates, and that towelroot prevents that by leaving the bootloader alone.
Click to expand...
Click to collapse
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
DroidIt! said:
After rooting you don't need to worry about updates with a nexus device (or any other really). As you'll notice in the N7 Android Development section, there are a TON of lollipop builds and it hasn't been officially released yet. In other words, all updates will be baked into custom ROM's so there's no need to worry about official updates. And to root a nexus, simply unlock the bootloader and flash a custom recovery like TWRP, there's no need for tools
Click to expand...
Click to collapse
Ugh...Yeah I was aware of that. If you read my question again, that was not what I was asking for. My queries were about the towelroot application in particular and if I could recieve OTA updates if I left the bootloader alone. I did not ask for alternatives.
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
nhizzat said:
I don't understand why you would rely on an app for root with a locked bootloader on a Nexus device. It's so simple to unlock the bootloader and root. There's only, at a minimum, thousands of guides on how to do it. If you're worried about updates, unlock the bootloader.
Click to expand...
Click to collapse
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Just another thought and I get your question, but if you did unlock the boot loader and then just downloaded the factory image from here https://developers.google.com/android/nexus/images you WOULD be downloading it from Google so you should get the same speeds. Now I know you asked about towelroot and I've not used it, but if you're worried about download speeds the images in that link are directly from Google. I know what you mean though, I have very good download speeds and no matter what I download it does seem like the one's direct from Google are about 25% faster. They've got good networking that's for sure.
Fakusnamus said:
Because I've heard unlocking the bootloader stops OTA updates. I don't want to have to download roms as my download speed is abysmal. Google services have (on average) 8 times the normal download speed at my place (no idea why), so I'd much rather recieve OTA updates from Google than download a rom.
Click to expand...
Click to collapse
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
nhizzat said:
Heard that an unlocked bootloader prevents OTAs? I don't know where you heard that, but that's completely wrong. Bootloader state has absolutely no affect on OTAs. What an unlocked bootloader does is give you the ability to have complete control over your device. Flash any rom, flash any recovery, and never have to worry about losing root.
Take some time to read and learn before you start tinkering.
Click to expand...
Click to collapse
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Fakusnamus said:
When I've rooted my phones in the past, I've stopped recieving OTA updates, even though they put out new ones. My friend who unlocked the bootloader on (and rooted) his nexus 7 also stopped recieving OTA updates. Are you saying that I can unlock bootloader and root my nexus 7 and I'll still receive OTA updates and/or can update to Lollipop when they release it a few weeks later for the device?
Click to expand...
Click to collapse
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) and then back to custom after the OTA. takes 2min extra work before and after the OTA.
esmith13 said:
USUALLY it's a custom recovery that prevents OTAs not an unlocked bootloader or rooted device.
For example, I have a nVidia Shield which I prefer to get the OTAs for as the stock OS is perfect for my needs. Whenever an OTA is available, I have to reflash the stock recovery, apply the OTA and then I can flash a custom recovery again. I could have chosen to not use a custom recovery but I prefer to - so I just flash the stock one (1.0-3.0Mb size maybe?) abd then back to custom after the OTA. takes 2min extra work before and after OTA.
Click to expand...
Click to collapse
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Fakusnamus said:
I can tell you for sure that neither me, nor my friend have flashed custom recovery. Still no updates.
Click to expand...
Click to collapse
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
The best way is to use towelroot now, and backup your data with titanium backup, then you can unlock your bootloader if you want for lollipop.
esmith13 said:
What android version and kernel date do you currently show in "About Tablet" at the bottom of the settings screen?
Click to expand...
Click to collapse
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
Question still stands... What Android version and what Kernel date?
Okay...
Okay, this is going on a massive tangent. My question was : If I root the nexus 7 with towelroot, can I still update to lollipop when the update rolls out? What can or can't I do with towelroot? (except not flash custom recovery or roms)
Fakusnamus said:
I haven't done anything to the tablet yet, it's still brand new. That was my friend with the updateless tablet.
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
esmith13 said:
Question still stands... What Android version and what Kernel date?
Click to expand...
Click to collapse
I don't have it on me right now, but its a brand new one, and I've done nothing to it, so whatever kernel that is. I'm guessing the android version is 4.3 .
Just unlock the bootloader now. It'll save you so much time and headache in the future.
Okay, I think I know the answer to this question, so forgive me. Just want to be sure before I go blow $500.
For the Nexus devices, regardless of the carrier, we'll be able to root them and ROM them as well as install new Kernel's because the bootloaders will be unlocked?
If that's correct please say so. If it's only partially correct, please explain it all to me.
Disgruntled Verizon User with a S6 Edge
THANK YOU IN ADVANCE!!!
Yes, its easy as pie.
nexuses are always devs favorites...
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Yes! Though I am not sure about the Pixel C. I am wondering if Google giving products the Pixel name means they lock them down? Sorry, little off topic.
I'm only curious how/if Google has the fingerprint security locked down when it comes to root
shimp208 said:
@mrbigdrawsz As a fellow Verizon user, I know exactly were your coming from. And yes since this is a nexus device coming directly from Google and not being sold or touched by Verizon, it will be good to go for all your rooting, ROM'ing, Bootloader unlocking, and custom kernel needs.
Click to expand...
Click to collapse
Thank the sweet, tiny, infant squishy baby Jesus! I have yet to own a nexus phone (fed up with my GS5) and am about to pre order the 5X. I miss getting to try out different roms and such, so i'm really pumped about the 5X. the 6P is just too big of a phone for me i think.
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
owenrg said:
Forgive me if this has been covered elsewhere, is there any word on xposed for android M?
Click to expand...
Click to collapse
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
If I unlock bootload, will I have problem with OTA?
shimp208 said:
They are still working out the bugs on getting it to run on 5.x completely as they want and those devs on the Xposed team do a phenomenal job. Support for 6.0 marshmallow will eventually come but it will be a little bit yet.
Click to expand...
Click to collapse
Awesome thanks!
Sent from my iPad using Tapatalk
menaceinc said:
If I unlock bootload, will I have problem with OTA?
Click to expand...
Click to collapse
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Thanks, I will just do that, unlocking bootloader. I really missed OTA as my current N5 is rooted.
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
shimp208 said:
If you just unlock the bootloader you will be fine for OTA's, if you root or then install a custom recovery then you'll have to apply the OTA updates a different way then usual.
Click to expand...
Click to collapse
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
In my experience, installing an OTA over a rooted phone would just kill root and you'd have to root it again, however, installing a custom ROM, the developer usually kills OTA so that all the custom stuff doesn't get jacked up.
Tank87 said:
Will rooting affect OTA? or will OTA just update and revert the device back to a non rooted state?
Click to expand...
Click to collapse
Rooting will effect the built in method of OTA updates. This is not a problem though. 99% of the time you will have access to the updated via the nexus factory image site before you receive notification of an OTA update on your device. Download the update and extract the boot, bootloader, radio, and system images. Flash via fastboot in bootloader mode and you will update your device without losing data/settings. I believe that you can flash img files with recent TWRP builds also.
To root after update just reboot to TWRP recovery and reboot. You will be prompted to install root before system reboots.
May seem a little overwhelming if its your first nexus device but a lot easier than updating a non nexus rooted Android device.
For more info check out any one of the recent nexus routing guides sticky threads
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
SlyUK said:
I know many people rooted etc their Nexus 5s using the Wugfresh Nexus Root ToolKit. Undoubtably a version will be introduced for the 5X,
If you root your device then flash a custom rom, you will be notified of the update via OTA or otherwise (eg Pushbullet) for that specific rom that you have flashed.
Click to expand...
Click to collapse
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
metpage said:
Why use a Toolkit to root? Just using ADB and Fastboot is better/easier since you can actually see what is happening during the process. Using a toolkit removes that element and if it hangs you don't where in the process it failed on.
Click to expand...
Click to collapse
Yes thats true, but I haven't heard of many people who have had problems with Wugfresh and it is a popular method. Everyone is different
I always rooted my Nexus (N4, N5 & N7), but I am not going to root my new upcoming Nexus 5X. Why? It just too much to flash/root since Google will release monthly security updates. Yes, I did use "fastboot flash xxx xxx.img" method. However, I will unlock the bootloader in case I change my mind in the future. With unlocked bootloader, I can always fix phone via flash factory images.
I've unlocked my bootloader but I am stock with no root. I haven't done anything yet because I'm waiting for twrp and Roms to mature a bit before I dive right in. Does anybody know if it's safe to update and keep the unlocked bootloader?
I know it should be safe to do the full image flash from a computer using fastboot. I am specifically talking about the ota
lars1110 said:
I know it should be safe to do the full image flash from a computer using fastboot. I am specifically talking about the ota
Click to expand...
Click to collapse
Yes, it's safe to take the OTA as long as your bootloader is already unlocked.
Yes, I installed it with no problem. Boot loader is still unlocked, and the new move gestures are mostly OK.
I lost the ability to use the native Hotspot with my unlimited data plan on Verizon. It appears the update closed the workaround where you could use network refresher and bypass the provisioning check.
Awesome thanks everybody about to do the OTA now
Mike01680 said:
I lost the ability to use the native Hotspot with my unlimited data plan on Verizon. It appears the update closed the workaround where you could use network refresher and bypass the provisioning check.
Click to expand...
Click to collapse
Damn that sucks. I'll be avoiding it for now then. Really don't want to root. I like android pay. But I need tethering
You can update... The OTA didn't work on my phone so I had to sideload it through ADB, still unlocked and worked like a charm
wrong thread
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Click to expand...
Click to collapse
You can before this update that was just released. You have to unlock before taking update or you won't be able to unlock. Once you unlock you can still update with no problem
Sent from my Pixel XL using XDA-Developers mobile app
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Sent from my Pixel XL
Click to expand...
Click to collapse
There is a tool that can force unlock the bootloader (depixel8?), but the exploit that it uses has been closed with this update.
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Click to expand...
Click to collapse
You can if your on 7.1 but not if your on 7.1.1
EDIT: I misread the posting. It is locked in 7.1.1.
Scott said:
This is not correct. @jcase stated he updated the tool to work with 7.1.1...
I'll see if I can find that post again...
Click to expand...
Click to collapse
Really?? The news has been all over that the 7.1.1 update patched dePixel8. He even posted on his website about it and said to not ask for further support. I assumed he didn't have a pixel so wasn't going to spend any more time on it. From my understanding the first method was very simple for them to figure out.
Please reply if you can find the post this will be big for everyone!
Krunk83 said:
I thought the Verizon pixel couldn't unlock the bootloader. Is that true?
Click to expand...
Click to collapse
You can unlock the bootloader with the dePixel8 method
Ad nauseum to the can you unlock or not. The latest update from Verizon makes the Verizon model locked. Period. If you haven't unlocked already, don't update to 7.1.1. If you plan to unlock. Depixel8 DOES NOT work for verizon pixel once the 7.1.1 update has been applied. If you unlock.... Don't relock. End of story. Stop with the round and round.
318sugarhill said:
Damn that sucks. I'll be avoiding it for now then. Really don't want to root. I like android pay. But I need tethering
Click to expand...
Click to collapse
I'm pretty sure you can root, change the build.prop to allow tethering, unroot, then install a custom kernel with the safetynet bypass feature and still use android pay.
So taking the OTA and flashing boot to root after will work if I'm understanding everything I've read this far? Also I have been unable to find the build specific for 7.1.1 for Verizon to download.
cntryby429 said:
I'm pretty sure you can root, change the build.prop to allow tethering, unroot, then install a custom kernel with the safetynet bypass feature and still use android pay.
Click to expand...
Click to collapse
Is this true? If so where is the post to someone doing this exact thing?
Is there any way to Remove unlocked bootoader warning (while booting) ? I have heard that in moto devices if we flash custom logo.bin, we can regret it!!
Is there any way like that?
Me interested too
+1 Just picked up this phone today on the recommendation of XDA as the best budget phone. Now I see that there really is limited support and ROMS available. I have been running Lineage/ Cyan for years now and it's unavailable to the BND L24.
I want to root to get rid of all the google crap but don't want to start the process and be left with the unlocked warning. Will unlocking and rooting but keeping the stock rom make me miss out on the OTA updates if I keep the stock Oreo ?
I'm interested too.
I've flashed RROS (here https://openkirin.net/download/) and i'd like delete the bootloader warning for more comfort in use
FieryAura said:
I'm interested too.
I've flashed RROS (here https://openkirin.net/download/) and i'd like delete the bootloader warning for more comfort in use
Click to expand...
Click to collapse
There is no way to do so.
h2odiver said:
+1 Just picked up this phone today on the recommendation of XDA as the best budget phone. Now I see that there really is limited support and ROMS available. I have been running Lineage/ Cyan for years now and it's unavailable to the BND L24.
I want to root to get rid of all the google crap but don't want to start the process and be left with the unlocked warning. Will unlocking and rooting but keeping the stock rom make me miss out on the OTA updates if I keep the stock Oreo ?
Click to expand...
Click to collapse
First, LineageOS is avalible via OpenKirin.
If you unlock and root, you will have the unlocked warning and also won't get OTA updates anymore. However, having just the bootloader unlocked, you will STILL get OTA updates but installation will always fail.
pradeep494ammu said:
Is there any way to Remove unlocked bootoader warning (while booting) ? I have heard that in moto devices if we flash custom logo.bin, we can regret it!!
Is there any way like that?
Click to expand...
Click to collapse
That warning actually useful, you will get to know when u mess up with your phone ! Everything is there for a reason !
steven360 said:
There is no way to do so.
First, LineageOS is avalible via OpenKirin.
If you unlock and root, you will have the unlocked warning and also won't get OTA updates anymore. However, having just the bootloader unlocked, you will STILL get OTA updates but installation will always fail.
Click to expand...
Click to collapse
OTA updates installation will fail maybe that why the new update fails really thank you and will lock it back and test it
I was given a Google Pixel 2 XL from a friend, who told me he partially rooted it. And indeed, the bootloader is unlocked, but I can't tell if he went further than that, and I can't ask him because he's... inaccessible at the moment, but another mutual friend seems to think that unlocking the bootloader is as far as he got. I want to undo what he did though, and return it to stock, but I'm wary without knowing for sure. Is there a way to see how far he got? I know that's kinda vague. Or would flashing a stock image and then locking the bootloader fix it regardless of how far he got? I wish I knew if it was as simple a job as just relocking the bootloader but I can't know for sure.
A root checking app from the Play Store indicated that root wasn't properly installed.
Ultimately, I'd like to update my phone to Android 11 (as it's still on 10), and potentially use Google Pay.
Flashing a stock Android 11 image will remove root from the device if it is installed, so that will take care of any issues you may have. Locking the bootloader afterward is up to you. Personally I wouldn't bother; the bootloader status I don't believe affects your use of Google Pay.
Strephon Alkhalikoi said:
Flashing a stock Android 11 image will remove root from the device if it is installed, so that will take care of any issues you may have. Locking the bootloader afterward is up to you. Personally I wouldn't bother; the bootloader status I don't believe affects your use of Google Pay.
Click to expand...
Click to collapse
Thank you, I thought that was probably the case, but wanted to make sure. I wanted it undone but also didn't want to brick my phone either. Lol