Database Users

[Q] Nexus 7 Root & Unlocking bootloader

Hello,
I have a question... If I root and unlock bootloader on my Nexus 7, will I be able to recieve OTA updates? I'm asking because of come of new Android 4.2
Thank you for all your answers

You can definetely receive the OTA Update being rooted and unlocked, mine just rolled in.
Didn't install it yet due to being unsure about CWM working after the update, I'm abroad right now and will do this at home with a PC nearby

ecki2k said:
You can definetely receive the OTA Update being rooted and unlocked, mine just rolled in.
Didn't install it yet due to being unsure about CWM working after the update, I'm abroad right now and will do this at home with a PC nearby
Click to expand...
Click to collapse
Wow thank you so much for quick answer And I have one more question... after update, will it be still rooted? Or I have to root it again?

[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop

If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.

Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?

^^^I'm not sure, but I've been postponing mine since the Ota was pushed.

Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.

When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"

itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"

rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.

Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated

Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!

So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?

hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man

samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.

I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.

Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?

There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it

So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?

As of now it makes no difference.

Stupid question, but how do you turn off automatic OTA on lollipop?

Can I rollback the 7.1.1 December update?

I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?

mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Sadly no.

Thanks I had a feeling

Have you even tried?

Scott said:
Have you even tried?
Click to expand...
Click to collapse
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.

cam30era said:
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
Did this myself. Unlocked bootloader, rolled back from Q to O. Was unable to flash OTA (with locked bootloader), due to being older.

So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk

ahent said:
So is Q Europe only, I have O but everytime I check for Q it says I am up to date. Not rooted or bootloader unlocked and I have a Verizon sim. The only reason I ask is because Verizon uses band 4 in my area and I am having some problems and I noticed a few people in Europe saying Q helped with band 4 issues.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....

Thanks, I hope it just pushes OTA I don't want to mess with flashing it. By the time I get around to flashing it January may be out and it will be a moot point.
Sent from my Pixel XL using Tapatalk

cam30era said:
I tried sideloading NDE63V, after having installed NDE63X. OTA sideload failed with a message to the effect that "V" was an older build. I'm now on NMF26O and haven't even tried to sideload a November build. I assumed it to would fail for the same reason.
Of course with an unlocked bootloader one can flash the earlier factory image. But I suspect all bets are off with a locked bootloader on 7.1.1.
Click to expand...
Click to collapse
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
---------- Post added at 09:02 PM ---------- Previous post was at 09:01 PM ----------
cam30era said:
There's not much official from Google, other than a brief mention of resolution of MMS issues for O2 carrier. But I did see a comment in a different thread where someone commented that Q did solve their ba d 4 issues. The only way you're going to get an answer is try it yourself....
Click to expand...
Click to collapse
IMHO I think the band 4 issues is pseudo.. since it does not update the radio or boot at all.. Unless its a "setting" that's changed that makes it work.

clockcycle said:
You can probably flash the complete rom. I dont think sideloading ota downgrading works. You'd need to flash the older boot.img first somehow
Note, I've flashed the full release down and back up, but I do have an unlocked bootloader which I dont think makes a difference, since they are signed..
Unlocked bootloader definitely makes a difference, you can't flash a factory image without it.
Click to expand...
Click to collapse

mkenny2 said:
I made a stupid mistake and upgraded before researching depixel8 and unlocking my bootloader. Is there anyway to revert back?
Click to expand...
Click to collapse
Return the phone if you can and get another one. Odds are that the stock on the shelves hasn't been updated yet.
Sent from my Pixel XL using XDA Labs

Changing builds

Want to change my build from Verizon NBD91V to N4F26O for all other carriers. Any easy way to do it? Can I side load an OTA or do I have to side load a factory image and lose all my stuff? Any other way to do it? I'm stuck on 7.0 and would like to update to 7.1.1. or 7.1.2.
Thanks
Sent from my Nexus 6P using Tapatalk

Yes, you can easily flash between builds/carriers with no ill effects. Download the full Google stock image (not OTA) and do it manually with flash-all.bat (first edit this file in Notepad to remove the -w (wipe) switch so as to not lose your userdata) or you can install and use a toolkit like NRT or Skipsoft found here on XDA to automate the process. Google has released a few images specific to Verizon that included a modified radio, but that radio also works well on all networks. Current radio version is v03.79 for Verizon and v03.78 for all others.

You could always flash a custom rom.

So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Sent from my Nexus 6P using Tapatalk

08BlackWRX said:
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Click to expand...
Click to collapse
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.

v12xke said:
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Sent from my Nexus 6P using Tapatalk

08BlackWRX said:
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Click to expand...
Click to collapse
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.

v12xke said:
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
Good to know, thanks.
Sent from my Nexus 6P using Tapatalk

08BlackWRX said:
Good to know, thanks.
Click to expand...
Click to collapse
Boom!

Android P DP2 now available

https://www.google.com/android/beta
Factory image direct link: http://storage.googleapis.com/androiddevelopers/shareables/preview/factory/taimen-ppp2.180412.013-factory-546fdc1f.zip

Cool beans!

Suggest new title: Android Beta Program now open.
DP2 has not been made available yet.

PhoenixPath said:
Suggest new title: Android Beta Program now open.
DP2 has not been made available yet.
Click to expand...
Click to collapse
Redditors are reportedly getting the OTA as we speak.

snowrelyt said:
Redditors are reportedly getting the OTA as we speak.
Click to expand...
Click to collapse
Within the last few minutes, yes. (After the Android P presentation was completed)
I am getting it now myself. Had no idea how quick they'd release it, so suggested playing it safe. Doesn't matter much now, I suppose.

Can we get Ota on rooted/unlocked bootloader? I know we can't install Ota on a rooted phone with custom recovery, but I haven't even gotten monthly security updates ever since I rooted my pixel. I enrolled in the beta as soon as it was announced but will i get an Ota since my phone is rooted?

...

Yasharkhan said:
Can we get Ota on rooted/unlocked bootloader? I know we can't install Ota on a rooted phone with custom recovery, but I haven't even gotten monthly security updates ever since I rooted my pixel. I enrolled in the beta as soon as it was announced but will i get an Ota since my phone is rooted?
Click to expand...
Click to collapse
I just got my OTA notification on my unlocked/rooted Pixel 2XL.

Yasharkhan said:
Can we get Ota on rooted/unlocked bootloader? I know we can't install Ota on a rooted phone with custom recovery, but I haven't even gotten monthly security updates ever since I rooted my pixel. I enrolled in the beta as soon as it was announced but will i get an Ota since my phone is rooted?
Click to expand...
Click to collapse
Same as me.im on dp1 with root..need a guide how to install dp2 from here

So dumb question but where does this OTA download to on the phone? I would like to grab a copy of it after it finishes downloading.

mprziv said:
I just got my OTA notification on my unlocked/rooted Pixel 2XL.
Click to expand...
Click to collapse
Did you install it?

The Beta OTA is coming to DP1 or is coming to Android Oreo? Whoever has received can they confirm.

gettinwicked said:
Did you install it?
Click to expand...
Click to collapse
I got the notification and currently downloading it right now

Does anyone know how to clear any rootless navbar customizations? Essentially clearing it back to stock, but without factory resetting. I thought I reset it through Custom Navbar but now my Navbar keeps defaulting back to the old 3 buttons (the new gesture navbar won't stay)
Edit: under Settings>System>Gestures you can turn on the gesture-based navigation.

I have unlocked bootloader but installed full May factory image without rooting. Have notification about Android P beta update but stuck on downloading OTA... Could I install it on the unlocked bootloader?

Phelicks said:
I have unlocked bootloader but installed full May factory image without rooting. Have notification about Android P beta update but stuck on downloading OTA... Could I install it on the unlocked bootloader?
Click to expand...
Click to collapse
It just takes some time

fiffan86 said:
I got the notification and currently downloading it right now
Click to expand...
Click to collapse
Let us know how it goes! Like, do you lose root/custom recovery, anything like that. I'm waiting to install mine until I know the correct way to do it being rooted/custom recovery.
Thanks in advance!

Factory image is live but there is an error when downloading
https://developer.android.com/preview/download

Phelicks said:
Factory image is live but there is an error when downloading
https://developer.android.com/preview/download
Click to expand...
Click to collapse
Thanks, added the link to the op

Phelicks said:
Factory image is live but there is an error when downloading
https://developer.android.com/preview/download
Click to expand...
Click to collapse
Yep i also get an error