Database Develop

Rooted Nexus 6 and updating to android 6.0

Hello all,
i rooted my nexus 6 and now that android 6.0 has been release i can't install the upgrade. My phone shows there is a system upgrade available. I have clicked to download the upgrade. Now its showing that a system upgrade has been downloaded and verified. Once i click on install update, it reboots to the teamwin. And to be honest, i don't really know if its taking the updated or how i can upgrade if possible.
can someone help me please?!!!!

Same answer every time. You can't get the OTA if you're rooted.
Options are :
- flash factory image (see sticky roll-up in general)
- flash a pre-rooted zip from recovery.

if you dont want to lose your data. just flash system.img, boot.img and recovery.img of your current build.
you can extract the images from the factory image...

Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it, as I did with my Nexus 10 a couple of years ago.
Your best bet is to use Wugfresh's Nexus Root Toolkit (NRT). Since this is a major upgrade you can't use the "no wipe" option, so you'll lose any data that you haven't backed up first - photos, etc. - so do that before you do anything. Also take a TWRP backup of your current ROM and copy it to your PC so that at least you can recover to where you are now. NRT also has a backup option.
If you tell NRT that your current ROM is MRA58K (Android 6.0) and then tell it to flash stock and unroot, it will pull down all the required files before applying them to your Nexus. You can then re-root if you want to. It's a beautifully-engineered program, pretty well foolproof if you follow the instructions and choose the right ROM for your device.

dahawthorne said:
Not only that, but by attempting to apply the OTA on a rooted device you risk bootlooping it
Click to expand...
Click to collapse
It cant get to that stage any more.

Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.

dahawthorne said:
Thats good news. What changed? Ever since that experience I haven't even tried an OTA. I was abroad at the time and lost the use of my Nexus 10 for most of the holiday.
Click to expand...
Click to collapse
OTA zips used to check individual files in system to ensure they matched before updating. It checks either md5 or sha hash. It didn't take account of every file or even files added by the users. so upgrading could cause issues.
Now, it checks the md5/hash of the entire system, which means all files are taken into account.. It will not flash of anything is changed.

Thanks - happy to roll you over to 19,400...

Issues with android security patch level

Hello everyone.
I`ve got rooted Nexus 6 with Franco kernel. From time to time it shows system security updates, which I install`s. But I notices on my android security patch level stops on January 2016 and still want to install February updates. Everytime N6 tries to install February updates. Does anybody know whats going on? Maybe it`s because I locked with security password on my twrp? After rebooting twrp show`s and I really dont know are updates installed well. I quess not. Can someone help?
And another question, does this android security updates will remove my root?

Shantarien said:
And another question, does this android security updates will remove my root?
Click to expand...
Click to collapse
Security updates will not work; unless the device is completely stock.

You should look at installing the OTA from this page - instructions are provided. If you want to retain the kernel,TWRP & and root you'll have to re-flash them when you're finished.
https://developers.google.com/android/nexus/ota
If you're unencrypted (I'm not - I prefer the security to an extra 10 minutes of battery life) do some reading first - I'm not sure how the OTA works with an unencrypted device. Maybe other members can advise both of us on this point.

Thx for answer`s.
Correct me if I wrong, but I`ve got stock rom, but with Franco kernel, and root, but it`s still stock, right? Does this could be a reason? All my data are encrypted, so maybe this could be a reason ( however after every update reboot I decrypt`s my data), I`ll switch off encrypting my N6 and try again update it.
----------EDIT------------
Guess, NLBeev was right. I can`t make an OTA update when my N6 is rooted, only manually method. I really afraid of this manually updates, because of losing something from my phone, or even brick it.

fear is something that xda can not help you with. itll happen through out life, in many situations. the only thing that you can do is deal with it and move on.

I manually update mine every update and have yet to have an issue.

I f you're encrypted (good!) then my earlier concern is irrelevant. Sideload the newest OTA at the link I gave you. I've done it now several times with two Nexus 5s and a Nexus 6. It's quick and simple and doesn't touch your data.
But I still always take a TWRP backup first and copy it to my laptop. Can't be too careful...

Once again thanks for help! I`ll try install them manually, as fast as I make backup by twrp.
Ach, I forgot, last question, which update should I download? I`ve got January system security updates, so should I download every single one by one? Or just last one (July 6.0.1 (MOB30O))?
Regards!

By "manually' do you mean extracting the separate components (system, radio, boot...)? I strongly recommend the OTA sideload method. Fast and simple, with no data loss.
You need only do it once. Download the MOB30O OTA and sideload it. Then if you want you can flash TWRP and root.

What is the purpose of each of the 3 different update zip files ?

Hi,
Sorry of this is a bit of a newbie question but:
What is the purpose of each of the 3 different update zip files ?
And do I have to apply them all - and in what order ?
In my case, I am about to update to B389, and I have downloaded 3 files for VIE-L29C636B389 (currently on VIE-L29C636B130), and I have an update.zip, an update_full_VIE-L29_hw_spcseas.zip and an update_data_full_public.zip.
I was planning on doing the first two by the dload method (with reboots in between), but the update_data_full_public.zip doesn't appear to have an update.app, so how do I load that ? (I do have TWRP on my phone, so could probably figure it out - eventually).
Cheers,
SZ

same question
I read somewhere that it should be flashed in that exact order. i'm guessing that is the same procedure as with auto OTA updates, except now we have rooted phones, so bye-bye to auto updates. I am currently on VIE-L29CB636B387 and i received an automatic Huawei notification of a new version (VIE-L29CB636B388) about a week ago. I tried to update to that version in System Update-Quick Update, but that didn't work (surprise!). There was no issue though as when I rebooted it just went back to 387. However, I now have a red "New Version" notification in my System Update. Please tell me how your upgrade went if you went ahead and flashed 389. I have the three files already from filefinder, i also have TWRP and/or I could use adb fastboot to install. Thanks in advance.

Hey,
I am not sure I want to proceed on the basis of something that somebody 'read somewhere' ....
Anyhow - I've not run these updates yet, as I wanted to backup my phone first, but TWRP keeps blowing up with an error in the middle of the backup, so I am not going to try anything until I get to the bottom of that.
Will let you know if/when I ever go ahead!
Cheers,
SZ

Hi,
TWRP blowing up during NAND backups? thats not a good thing. Upon the advice of a forum member (xzanium) I flashed TWRP 3.1.1-1 instead of TWRP-3.2.1-0-vienna. No hitches so far, solid backups and no hiccups in flashing SuperSU, also got xposed to work seamlessly and other stuff. I hope you are able to resolve the issue you mentioned and get around to getting VIE-L29CB636B389 on your phone.
Well good luck to you, and post here any progress if you would.

SZ,
I have an idea on what the purpose of each of the 3 different update zip files are for and whether you have to apply them all - and in what order.
Since I could make a NAND backup using TWRP without issues, and there was an OTA update notice for an upgrade to VIE-L29CB636B388 which I couldn't upgrade to while rooted, I decided to unroot in order to upgrade to that. First i did the requisite steps - uninstalled the xposed framework and proceeded with the full unroot with SuperSU. Then I performed the dload method to flash the update.app that I extracted from the update.zip.
It was here where i hit a snag. What followed was, I found out that Huawei needs a verified stock rom, meaning it has to be a fullOTA-MF-PV in order that the bootloader could be relocked. So I tried my luck and downloaded the stock ROM VIE-L29C636B370 and flashed that. Success! From there, and several auto upgrades later I was back to L29C636B370. Reinstalling my Google account also locked back FRP. At this point i am full stock EMUI 5
Now, to answer your question. When I tried to upgrade to VIE-L29C636B388 via system update quick update. I only saw one file - update.zip therefore this must the only one needed for incremental patches. The same holds true with update_data_full_public.zip as I later learned when I decided to use the proxy upgrade method in MT filefinder . It applied a 2nd patch. The third file, namely, update_full_VIE-L29_hw_spcseas.zip was not required for this incremental update. In fact, the update process was cut short and an error message appeared that the file could not be located, even though i copied that to the HwOUC folder. It appears that this was deleted before the fullOTA update could finish during the incremental update process. Clearly, this last zip is not necessary for incremental updates. So this must be the package which delivers the rest of the ROM, or the parts of it that needs to be changed.
So, obviously what "I read somewhere" was legit. I hope that answers your question.
cheers!
mm

Can I do OTA updates with Magisk?

If I root my OnePlus 6T with Magisk, will it stop me from updating the OS via OTA updates? I don't want to lock myself down to Android 9 in case the next version is around the corner.

When you have root and you update with OTA you will soft brick your phone. Always update with full rom.
Tapatalk - OnePlus6

https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Ok help me get this straight. The first reply indicates that I will brick my phone if I do the update. Second reply is a guide on how to do it.. Which of them are correct?

Since the guide in question is written by the developer of Magisk, I would trust that more...
The other reply is likely referring to what could happen if you did not follow the procedure outlined in the guide and just tried installing the OTA straight up.
Edit: Reminder - always have a backup of any important data...

Didgeridoohan said:
Since the guide in question is written by the developer of Magisk, I would trust that more...
The other reply is likely referring to what could happen if you did not follow the procedure outlined in the guide and just tried installing the OTA straight up.
Edit: Reminder - always have a backup of any important data...
Click to expand...
Click to collapse
Got it! Thanks a lot! I'm bookmarking this guide

You'll still receive OTA via setting, but it's a full download.
Download it, enter recovery and flash the zip, then flags magisk right after and you're good.
That's how I've been doing it, since Orea and many betas

Question Can't update to Dec OTA [SOLVED]

Hey, I followed this tutorial https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/ (recommended method) and I'm not getting results. After flashing the original boot img, etc. my update screen says my device is updated so I'm not getting Dec. OTA.
I tried also with the Uninstall Magisk (restore images) method and I'm getting the same results, not OTA available.
I'm doing it with all modules disabled.
What am I missing?

alsansan said:
Hey, I followed this tutorial https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/ (recommended method) and I'm not getting results. After flashing the original boot img, etc. my update screen says my device is updated so I'm not getting Dec. OTA.
I tried also with the Uninstall Magisk (restore images) method and I'm getting the same results, not OTA available.
I'm doing it with all modules disabled.
What am I missing?
Click to expand...
Click to collapse
You may have to wait for the update over the internet, then once it starts there's more waiting for the installation to complete, plus you could end up with a "problem" error after everything seemed fine during the first 20 minutes. OTA updates will be less frustrating and faster using adb to sideload over USB.
This guide for Pixel 6 is a good reference for most Pixel 7 situations (the main difference with 7 is to patch, flash or restore init_boot.img instead of boot.img).

alsansan said:
Hey, I followed this tutorial https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/ (recommended method) and I'm not getting results. After flashing the original boot img, etc. my update screen says my device is updated so I'm not getting Dec. OTA.
I tried also with the Uninstall Magisk (restore images) method and I'm getting the same results, not OTA available.
I'm doing it with all modules disabled.
What am I missing?
Click to expand...
Click to collapse
If it helps..
I just happened to use my P7 as an example in a different thread.
[Discussion] Magisk - The Age of Zygisk - Post # 2,648​
Includes a Github link showing the modification to the flash-all script I use.
Includes a Pastbin link showing my update from Nov -> Dec.
Cheers.
PS.
Just to be clear, I (always) use full factory images for Pixel updates.
- Factory Images for Nexus and Pixel Devices
Not the incremental OTA(s).
- Full OTA Images for Nexus and Pixel Devices

manjaroid said:
You may have to wait for the update over the internet, then once it starts there's more waiting for the installation to complete, plus you could end up with a "problem" error after everything seemed fine during the first 20 minutes. OTA updates will be less frustrating and faster using adb to sideload over USB.
This guide for Pixel 6 is a good reference for most Pixel 7 situations (the main difference with 7 is to patch, flash or restore init_boot.img instead of boot.img).
Click to expand...
Click to collapse
Thanks, I want to try the adb to sideload method, but I have doubts. it is technically detrimental to update flashing factory image / ota over the previous factory image? It's been years since my last rooted phone and I remember people suggested not to do this (I think they recommended full wipe), but I don't know how it goes today.

ipdev said:
If it helps..
Click to expand...
Click to collapse
Helps me! Learned some new stuff and added it to my notes.

alsansan said:
Thanks, I want to try the adb to sideload method, but I have doubts. it is technically detrimental to update flashing factory image / ota over the previous factory image? It's been years since my last rooted phone and I remember people suggested not to do this (I think they recommended full wipe), but I don't know how it goes today.
Click to expand...
Click to collapse
Flashing the OTA doesn't wipe but factory will wipe if you run flash-all (.bat for Windows, .sh for Linux) without removing the -w argument on the fastboot line. i.e., Flashing the OTA will get you updated without losing anything but flashing factory is preferable for updates as long as wiping is disabled.
The factory zip is what PixelFlasher uses for non-destructive updates without having to uninstall Magisk. It's the easiest way to update a rooted Pixel, but mistakes still happen. Like its developer recommends, best to tackle command line methods before jumping into GUI methods.
As far as detrimental flashing goes, with Pixels and stock firmware you would have to stray far off the trail to break the phone.

manjaroid said:
Flashing the OTA doesn't wipe but factory will wipe if you run flash-all (.bat for Windows, .sh for Linux) without removing the -w argument on the fastboot line. i.e., Flashing the OTA will get you updated without losing anything but flashing factory is preferable for updates as long as wiping is disabled.
The factory zip is what PixelFlasher uses for non-destructive updates without having to uninstall Magisk. It's the easiest way to update a rooted Pixel, but mistakes still happen. Like its developer recommends, best to tackle command line methods before jumping into GUI methods.
As far as detrimental flashing goes, with Pixels and stock firmware you would have to stray far off the trail to break the phone.
Click to expand...
Click to collapse
Thank you manjaroid! Finally I updated flashing the Dec factory image with flash-all.bat script (-w removed) and rerooted with the new patched init_boot.img it's really easy but we have doubts the first time. You answered my question (flashing factory is preferable for updates), but why is that? I want to understand a little bit more. And whats the difference between an destructive/non-destructive update?

alsansan said:
...You answered my question (flashing factory is preferable for updates), but why is that? I want to understand a little bit more.
Click to expand...
Click to collapse
How I might explain it is OTA's are incremental updates that patch specific particular parts of the system. You might want to look at it like in an instance of laying a foundation/base, OTA's would be like replacing cracked/broken/weak sections with bricks. As time goes on and more OTA's are released and patched, more of the foundation is put together by more and more bricks -- which may be (quick and easy) or may not be (not a single solid base/structure) more detrimental as time progresses (cumulative patches may inadvertently cause glitches/bugs down the road vs. a full factory [non-patch] update). While holding up upon that patchworks of bricks among the "foundation" is perfectly serviceable and can well enough hold up whatever structure is placed on it, having a whole piece unpatched foundation (Full Factory image) is still preferable as a base/foundation because implementing that "foundation" (versus a foundation with various patchworks in it [OTA's]) would include in itself whatever fix/reinforcement the bricks patched(cracked/broken/weak sections) [what the OTA's did] while establishing a complete whole unseparated-in-any-place base/foundation.
So, in the end, it's preferable to have a solid, whole, almost from-scratch Full Factory image firmware update than a circumstance of patching upon patching the way OTA's implement their updates.
Also, unless you update the device by OTA's from the OS and it's as simple as that (although it can take pretty long; upwards to seemingly 20 minutes) -- because you have an locked bootloader -- the only other way to install an OTA is sideloading it which means you have to download it to a computer, boot up the device in a certain way, and run a command on the computer; which is very similar and not too much different than what you would do if updating using a Full Factory image anyway -- download image (Full Factory instead of OTA), load up device in a certain way (bootloader/fastboot mode instead of recovery) and run a command (flash-all.bat instead of adb sideload .zip); one major difference is you must edit the flash-all.bat script so it doesn't delete user data and factory reset the device.
Sorry for the long explanation, but that is why IMHO it is more preferable to update using the Full Factory image than OTA...

alsansan said:
whats the difference between an destructive/non-destructive update?
Click to expand...
Click to collapse
Not a good choice of words ("non-destructive updates"). That's kinda redundant since most of us don't intend to lose anything when updating. fastboot has to be told to wipe or not so calling it non-destructive flashing would have made better sense.