I keep checking for the update to 5.0.x and it keeps saying device is upto date...
But I think 5.0.x has rolled out right? Any ideas how to get it updated?
You could sideload it via ADB.
fury683 said:
You could sideload it via ADB.
Click to expand...
Click to collapse
Thanks found an article on how to do it. I assume the device is "Razor"? And the current is 5.0.1?
I think I need to do OTA KTU84P -> LRX21P
then have to do LRX21P -> LRX33C
Sound right?
https://www.google.com/?q=nexus 7 sideload 5.0.1
Download the OTA, put the device in ADB OTA mode and follow the instructions. It will only work on a 100% stock unmodified system.
fury683 said:
https://www.google.com/?q=nexus 7 sideload 5.0.1
Download the OTA, put the device in ADB OTA mode and follow the instructions. It will only work on a 100% stock unmodified system.
Click to expand...
Click to collapse
Google officially pushed it out right? Or is it being held back for some reason?
It did release, its just slow pushing out to all devices as there are still kinks with the update. Google usually pushes updates in waves, its just taking longer this time around. You can sideload it. And fury683 is incorrect in the device needing to be unmodified, at least in terms of root it is okay if your tablet is rooted. Just make sure you have an unlocked bootloader and adb devices and fastboot devices detects your tablet before sideloading.
renold458 said:
It did release, its just slow pushing out to all devices as there are still kinks with the update. Google usually pushes updates in waves, its just taking longer this time around. You can sideload it. And fury683 is incorrect in the device needing to be unmodified, at least in terms of root it is okay if your tablet is rooted. Just make sure you have an unlocked bootloader and adb devices and fastboot devices detects your tablet before sideloading.
Click to expand...
Click to collapse
If there are changes to your /system or /recovery (very common when the device is rooted) the OTA will likely fail verification, which it did for me when I tried. I had to use the factory images to go from 4.4.4 and 5.0 and eventually 5.0 to 5.0.1.
You can remove the -w flag from the flash-all.bat file in the factory images zip to prevent it from wiping data and it takes about 2 minutes to flash everything.
Well yes in terms of OTA it will most likely not work,I meant in terms of sideloading the image it is okay to be rooted and have a custom recovery. However as a note, my custom recovery and root was removed after sideloading, so I had to reroot and reflash TWRP as my tablet no longer had a recovery image.
renold458 said:
Well yes in terms of OTA it will most likely not work,I meant in terms of sideloading the image it is okay to be rooted and have a custom recovery. However as a note, my custom recovery and root was removed after sideloading, so I had to reroot and reflash TWRP as my tablet no longer had a recovery image.
Click to expand...
Click to collapse
I think I will just sit tight. I am told by google that they are still rolling out...
Related
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Norcalz71 said:
Long story short, I was a victim of the bricked/unrecoverable OTA update situation that seems to be plaguing everyone lately. ASUS did repair my tablet, so it got back to me last week and it a fresh, untouched 4.4.2 as far as I can tell.
I am trying to get a better handle on the "proper", manual non-toolkit way of doing everything. I am up to the unlocked bootloader and have TWRP 2.8.4.0 flashed for recovery - now to root and updating.
My confusion with with flashing the SuperSU zip - should you just always us the most updated version (and where is the "proper" source everyone uses) or are there certain versions of SuperSU that pair correctly with different OS numbers (4.4.2, 4.4.4, 5.0.2, etc)? Is it always as simple as flashing the SuperSU.zip through TWRP after updating via factory image flash to a different OS version #? (Say from 4.4.2 now and flashing to 4.4.4 or 5.0.2)?
When I exited TWRP the first time after flashing it, it said I did not have superSU installed and did I want to - will that process auto-flash the zip and root the N7 with the correct superSU version (it is the latest TWRP release 2.8.4.0) or do I need to download the proper superSU.zip for TWRP to then find on my internal storage when that prompt comes up?
Thanks,
Click to expand...
Click to collapse
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then let TWRP install SU. I actually just did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
I'm pretty sure it works the same for lollipop now too. Originally you needed to flash a special kernel, but I think now you can root it the same way as Kit Kat, ie. via recovery. Someone can correct me if I'm wrong but I don't think I am.
_MetalHead_ said:
You got it, flash recovery and select yes when it asks you if you want to install SU binary. If you plan on sticking with KitKat (that's what I'm doing, I hate Lollipop), then I recommend flashing the 4.4.4 system image via fastboot first, then flash recovery again, and then TWRP install SU. I did this yesterday. I dusted off my N7 after a year of not using it and it was still on 4.4.2 so yesterday I updated it to 4.4.4 by flashing a system image. Wanted a clean start.
Click to expand...
Click to collapse
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Norcalz71 said:
10-4, thanks. So the 2.8.4.0 version of TWRP should already have that SU binary ready to roll (could either choose to flash it now and be rooted on 4.4.2, or fastboot flash the factory 4.4.4 and then reflash TWRP and flash the su zip?) No further superSU.zip/binary downloads, essentially?
I also think I will go with 4.4.4 for now, the 5.0.1 bricking my tablet left a bad aftertaste, it was OTA though. Perhaps fastboot factory image would have no issues.
Click to expand...
Click to collapse
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
_MetalHead_ said:
It'll install the SU binary but then once you boot into the OS it prompts you to download SuperSU from the play store. Once you download it and open it, it'll prompt you to update the SU binary. Just hit yes and it'll do it for you, and then you reboot and you're done.
Click to expand...
Click to collapse
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Norcalz71 said:
Awesome, thanks man. From all the various threads about how to root, it makes it seem WAY more involved than that.
Click to expand...
Click to collapse
No prob bud. One of the big benefits of Nexus devices is that they are super simple to root. Heck, they are super simple to do pretty much anything on. That's the only reason why I decided to start from scratch yesterday, because it's like nothing to do. The longest part was re-downloading all my apps, but still the whole process took about 30 min start to finish. If you're not downloading a ton of apps, it'll take you 5 minutes.
Hi, I have a Nexus 5X with unlocked bootloader and with rooted. Since some days ago, I have a notification with a security update, but with the custom recovery it is not automatically installed.
Is there any way to install this OTA updates?
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
martyfried said:
If you install TWRP (which you should, IMHO), it is easy. I'm not at all experienced, but I did it without losing any data. But with TWRP, you can do a full backup first. Everything I've done came from this single guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Click to expand...
Click to collapse
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The updates will not install on a rooted phone. Updates check if your software is stock and if not it will not update, includes recovery partition. Your best bet is to just update the ROM you're on. The ROM developer typically updates his base on a regular basis especially if it's one of the more active ones like Pure Nexus or Chroma among others.
If you really need Google updates to happen then you must go back to stock image and updates will work then.
Edit #2: If you are rooted but stock w/ TWRP, just unroot and flash stock recovery and the updates will work or you can ADB sideload the update zip w/ TWRP.
Reyengine said:
i have TWRP ... and when try to install the updade i end up in recovery mode - after rebooting nothing changed ant the ota update notification is still there
Click to expand...
Click to collapse
The link I provided has explicit instructions. I remembered wrong, though. You don't need TWRP, you need to do it in Fastboot mode, so you need to find the latest Fastboot program, or install the Android SDK. Then follow step 10 in the link I provided.
Hi!
I had 2 nexus 5x phones. One rooting went fine, the other is stuck at the Welcome to Android cycle.
I unlocked the bootloader, and I used chainfire auto-root script from linux.
When the phone boots up it has the blue welcome screen. I setup wifi and then it forces me to install an android update. It downloads the update, reboots, tries to install it, fails, and then boots into android where it tries to force me into the update.
How can get out of the loop?
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
draggehn said:
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
Click to expand...
Click to collapse
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
OP, the way googles OTAs work these days, is that they basically check your system partitions for any modification (e.g. root). if that check fails, so does the update. now what can you do about your little update trap?
if i recall correctly, chainfire includes ways to revert to unrooted. so there is you first possible option. use it, fire up your phone, let it take the OTA (make sure you're on the latest version after that) and attempt to root again.
if that is not an option, you could grab the newest factory image directly from google, flash the whole thing and then root again.
once your phone is up and running (and rooted ofc), it won't be able to apply future OTAs, but instead of forcing you to update, it will only show a notification.
Broken303 said:
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
Click to expand...
Click to collapse
Which is why there was a parenthetical note that you can also flash stock.
I have 5.01 and I want to update to 6.01. I want to wipe it clean. Got factory image from Google site.
What's the difference between the OTA and factory downloads?
I can just flash the factory in TWRP right? Will I lose root, or will TWRP ask if I want to keep root?
I still have boot loader unlocked.I just can't remember for the life of me, haven't done flashing etc in a few years.
Thanks!
So...not a single person can tell me if I lose root, or if TWRP will re-root?
Please?
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Sent from my XT1565 using Tapatalk
k23m said:
N7 is no longer supported by Google and there will be no more OTA.
You can't flash the entire factory image directly from TWRP (but it is doable).
When you flash the factory image, you will lose root, TWRP and all your data.
NRT can simplify flashing, rooting and restoring TWRP.
Click to expand...
Click to collapse
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
atifsh said:
You have unlocked boot loader
Just fastboot flash all as yiu want clean install
After that fastboot flash twrp
After that flash superSU
Done.
No need for any toolkit's, try to stay away of them and do it manually.
Click to expand...
Click to collapse
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Syntax323 said:
I know it isn't supported anymore. They still have the image's though.
Im just confused... Long time ago when I was really into all this, I just went to Googles page, downloaded the .zip and flashed it in TWRP. Now, the Google page is different and there isn't just 1 anymore. Can I just open the factory image and unzip the update part and flash that in TWRP?
The OTA files are only for updating from version to version correct? Can't go from what I'm on, 5.01 to the current 6.1 right? That's what I talking about and why I'm so confused now
Googles page used to have the OTA zip to update from prior newest to newest(5.0 to 5.01 for example) but than they also had the full OTA so you could do a 4.0 to 5.1 or whatever. Why they change the site? Which one do I use now to go from my 5.01 to current 6.1?
That's the pronlem, normally yes I would do that no problem. I'm in the middle of upgrading my PC after had a surge or something and fried my ****.
That's why I want to do it via TWRP like I always did before. Every time TWRP asked if I wanted to retain root after updating also. So what in the world happened in the last year that It doesn't seem like I can now? Like I said above, I can't find a full update OTA on!y the incremental OTAs...
Click to expand...
Click to collapse
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
atifsh said:
Ok yes that's possible
If you have twrp already
Check development forum and choose one of the ROM.
Download it to your tablet plus gapps
Wipe system, cache and data leaving internal storage.
Flash ROM reboot, come back to twrp and flash gapps. ( Can do ROM + Gapps in one go)
Download SuperSU and flash to get root.
You can't flash stock image / OTA via twrp.
While you're doing all this try the 7.0 ROM its good enough now.
Click to expand...
Click to collapse
Ahhh what happened??? Why can you not flash them with TWRP???
Thats what I used to do no problem. Not referring to custom roms either.
I am wanting stock rooted.
I used to download the update when one was released from Google's site, put the update.zip in main directory, go in recovery and flash update.zip. TWRP would ask me if I wanted to keep root, I say yes, reboot, update installs... than i'm on the new Android version still rooted.
How is that not possible now?
I am so annoyed... I never had to go through ADB or fastboot to update to latest. I did everything on my N7, it kept root for me and everything.
I feel so dumb right now its ridiculous lol
So than what way can I go about updating my N7 2013 Wifi, which I currently have 5.01. I am Rooted w/ unlocked bootloader.
What is the best way not using ADB, or a PC at all for that matter to update to the latest, 6.01. If possible, how can I keep root, if not i'm not worried about it, i'll just re-root myself.
I appreciate all the responses, sorry if i'm just being an idiot. I just know for a fact I never had to use ADB or my PC to update and keep root...
I'm not familiar with Stock OTA done with twrp (if that's even possible)
Already told you get a custom ROM, get the one mostly stock or if there's a stock ROM in zip format available.
In future you might need to update that bootloader of yours for newer ROMs
Sorry if this sounds harsh why are you so into keeping root as you can't do it again? It's simple as flashing SuperSU. Root method changed after 6 you cant have old methods with 6.
Best bet for you at the moment.
http://forum.xda-developers.com/showthread.php?t=3219148
Sent from my XT1565 using Tapatalk
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Cyber Akuma said:
So, I have a Sprint HTC 10. It was rooted, and then an OTA update came out about a week or so ago, version 1.80.651.10.
I unrooted and installed it, since I have TWRP it seems to take over the install process, but more or less does install it correctly.
Once my phone rebooted, it complained that the download was corrupt like it always does (likely due to TWRP) but this has happened before and the update always actually does install successfully. Going to system settings I can confirm that I am on version 1.80.651.10.
However, this time, it seems hell-bent on assuming that the update didn't install. It keeps putting an update notification in the notification bar that refuses to go away. If I go to check for updates, it confirms that I am up to date and the notification disappears.... for a short while, but then appears again asking me to install the update.
How can I get rid of this annoying thing? I haven't even gotten around to re-rooting my phone yet, as been confirmed by root and safetynet checkers, the ROM is basically at stock right now.
Click to expand...
Click to collapse
If you have twrp installed it wont update the firmware only software. You need to flash firmware seperatly with fastboot.
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Cyber Akuma said:
So I would need to extract the firmware or something out of the OTA file and flash that manually? What partitions would the firmware be updating?
And I am assuming this would overwrite TWRP and I would have to reinstall it?
Click to expand...
Click to collapse
Correct.:good:
Can somebody please explain how to flash the firmware with fastboot?
So I have to flash the OTA with TWRP, afterwards I have to extract the firmware file out of the OTA.zip and flash it with fastboot. But which commands are necessary in fastboot?
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
kjjejones42 said:
To get this out of the way, you can only flash firmware over fastboot if you're S-OFF. Otherwise, you'll need to restore completely to stock via custom recovery or RUU then update by OTA.
The best guide I've found for this is at http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520.
Click to expand...
Click to collapse
Thats not true. You flash in ruu mode when S - ON. If your are S - Off you can do it from download mode. I think you are a little confused with that thread. Those firmwares are modified and for S -Off phones only.
yldlj said:
Thats not true. You flash in ruu mode. If soff you can do it from download mode.
Click to expand...
Click to collapse
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
kjjejones42 said:
Ah, you're right! Sorry. To flash while S-ON, the CID and MID must match the zip + the bootloader must be locked, right?
Click to expand...
Click to collapse
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
yldlj said:
Im not sure about locked or relocked bootloader, i think it will work with unlocked but i could be wrong.
Click to expand...
Click to collapse
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
kjjejones42 said:
I just had another thought, correct me if I'm wrong. You can flash the OTA manually through the stock recovery as a ZIP.
The OTA ZIP can either be downloaded in various places online, or you can download it on the phone as usual then find it in /data/data/com.htc.updater/files (if your device is rooted). More info at http://forum.xda-developers.com/showpost.php?p=66548846&postcount=3.
You can then flash the OTA through recovery if you have;
* 100% unmodified system (can be restored from TWRP backup)
* Stock recovery
Click to expand...
Click to collapse
Correct. Also unmodified boot. But if your flashing unmodified system image, boot and stock recovery you may aswell just boot to android and take the ota.