Related
getting errors when trying to take the january OTA security update
im using systemless root 2.66
twrp wont install the ota. anyone know how?
With TWRP, you can't take an OTA. You need to have stock Android recovery, unmodified /system, and unmodified boot.img (so no custom kernel). Otherwise the OTA will fail.
ugh i thought one of th ebenefit of systemless root was to be able to easily to ota updates. anyone have a flashable zip?
If you need twrp just boot from it in fastboot and retain stock recovery
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Chainfire wrote that if you use the SuperSU unroot function you should be able to apply the "real" OTA (i.e. not a sideload of a downloaded OTA, though maybe that might work too) and then reroot.
Alternatively, download the full image, unzip everything including the zip within the zip, copy the system.img, boot.img, and the TWRP for your device to your ADB folder. Copy SuperSU v2.67 to a folder on your phone. Then boot into bootloader, flash system, boot & TWRP, boot into TWRP recovery, and install SuperSU. Job done. No settings, data or apps lost. I know because I did it last night on my Nexus 6 & Nexus 10.
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
JimSmith94 said:
Where did you find the OTA update? All I have found is the factory image, which is a different animal, here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
Not_A_Dev said:
Folks, please correct me if I'm wrong here, but I would think that the installation of the OTA will fail simply because the OTA encounters a custom recovery (TWRP), as opposed to the expected stock recovery. Let alone anything that may or may not have been done to /system.
Click to expand...
Click to collapse
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
RMarkwald said:
http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493/page124
There's the OTA for MMB29S to MMB29Q.
---------- Post added at 11:45 AM ---------- Previous post was at 11:44 AM ----------
It will fail if /system has been modified, and if there is a custom boot.img that was installed other than the stock one, plus custom recovery as stated.
Click to expand...
Click to collapse
Thanks! I have already installed MMB29Q with fastboot, but next time I might try OTA with Chainfire's FlashFire: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx
Sent from my Nexus 6 using Tapatalk
Anyone have the ota from mmb29k?
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot flash system system.img
8. fastboot flash boot boot.img
9. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Not_A_Dev said:
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
13. fastboot reboot-bootloader
14. reflash superSu
15. reflash Xposed
Would this work?
Click to expand...
Click to collapse
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
This method (outlined above) works great. This is exactly the same setup I have (n6 + root + xposed) and is also precisely how I've been applying the monthly updates. Never experienced any issues.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
I'll give it a shot. I agree, and thanks for the suggestion.
Edit: Happy to report that the method in post #13 leads to a successful update of the most recent Shamu image. My device is now updated to MMB29Q, still runs TWRP, is rooted, and runs Xposed. 20 minutes tops for the whole project.
RMarkwald said:
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Click to expand...
Click to collapse
Excellent may i knidly ask pls
last two steps:
what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Thanks tonnes...I believe my user data is preserved
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Most of the time they don't update bootloader and radio...
90% of the time, you can just fastboot flash only system. Basically the equivalent of dirty flashing your rom.
The above where you clear everything before flashing is basically the equivalent of wiping cache 3x... It wipes the partition when you flash. Think about it, if you flash userdata... you end up with all your data being deleted and a blank userdata partition. It doesn't copy the img on top of what is currently there, it replaces it. You can do extra steps if you want... But you really don't need to.
sunandoghosh said:
Excellent may i knidly ask pls
last two steps: what are commands for reflash supersu and reflash exposed and where are latest files which are compatible?
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
There are no Fastboot commands for SuperSU or Xposed. Each is available as a flashable zip, installed using TWRP.
Click to expand...
Click to collapse
^ This. One step that's also missing above is that once system.img and supersu have been flashed, there is hardly any space on /system to flash xposed (that's just how Google does things these days). So one would have to remove a few non-essential system apps (files, such as Google Books, Google Newsstand or the like) to make some room for xposed.
This thread is turning into a fastboot flash factory image thread rather than an ota thread. That's ok, it's a good thing ...I've been waiting for a thread like this and your posts inspired me to do my first flash to update security for my rooted phone (with xposed) since I initially set it up in December.
My recommendations below in red. I would erase the partition first, then flash the img file just to make sure you are putting down a clean image flash.
Quote:
Originally Posted by Not_A_Dev
Ok, I'm on MMB29S (January security update), rooted N6, running Xposed.
Here's my plan to update to the February security update without losing TWRP and userdata:
1. Download MMB29Q factory image and extract files.
2. adb reboot bootloader
3. fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
4. fastboot reboot-bootloader
5. fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img
6. fastboot reboot-bootloader
7. fastboot erase system
8. fastboot flash system system.img
9. fastboot erase boot
10. fastboot flash boot boot.img
11. fastboot erase cache
12. fastboot flash cache cache.img
10. fastboot reboot-bootloader
11. reflash superSu
12. reflash Xposed
Would this work?
Click to expand...
Click to collapse
I roughly followed above steps, but had some comments/questions along the way:
I skipped the first and second erases as suggested above, but I kept the third erase (cache) because it is included in the xda n6 stock flashing tutorial here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I rebooted to android system between steps 10 and 11 because I wanted to make sure everything was ok. But that was a bad idea because:
A- it overwrote my twrp with stock recovery (even though I never flashed recovery)! So I had to fastboot boot twrp later.
B- it took extra time formatting stuff that was probably undone later.
And yet I still have to boot into android at some point in time to clear space before I flash the xposed zip in twrp. Maybe next time I should reboot to clear space between steps 11 and 12?
I was pleasantly surprised to see when completed flashing the xposed zip that I didn't have to reinstall the xposed apk and that the xposed modules were already enabled and configured exactly the way I left them. Good stuff.
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
agel1 said:
can somebody tell me how to do it without losing data or root ?
Click to expand...
Click to collapse
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
NLBeev said:
First root; flash TWRP-recovery; make a backup with TWRP; flash a stock ROM https://forum.xda-developers.com/showthread.php?p=59561445/; restore data; Unroot.
Click to expand...
Click to collapse
sorry dont understand
Im already rooted and with twrp installed
agel1 said:
hi my nexus 6 its running 7.0 NBD90Z, and want to update to 7.1.1 march update
this is the 7.0 version im running https://forum.xda-developers.com/nexus-6/general/android-nougat-nbd90z-flashable-image-t3474572
can somebody tell me how to do it without losing data or root ?
thank you
Click to expand...
Click to collapse
Download the factory image of the version you desire to end up on.
Unzip it, then unzip the folder contained in it, then in a terminal/cmd run:
Code:
fastboot flash bootloader bootloader-shamu-*.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-*.img
fastboot reboot-bootloader
cd shamu-*
fastboot flash boot boot.img
fastboot flash system system.img
Now, you said you wanted to retain root too, if that isn't the case, just run:
Code:
fastboot reboot
If you do still want root, download TWRP, cd to the Downloads directory, then either run:
Code:
fastboot boot twrp-3.1.0-0-shamu.img
if you want to keep the stock recovery
OR
Code:
fastboot flash recovery twrp-3.1.0-0-shamu.img
if you want to keep TWRP.
Now that you're on TWRP, just use file explorer to drag and drop the newest SuperSU zip (at the time of writing this, 2.79 is the latest stable, and SR3-2.79 is the latest beta) if you're on Windows or Linux, or use
Code:
adb push [I]nameofsupersu[/I].zip /sdcard/
.
Now reboot.
Have fun! It may take up to 15 minutes to boot (for dex-opting, and encrypting if you were decrypted and decided to re-encrypt), so don't interrupt that first boot process, just let it go. It will also need to "Optimize" all installed apps, so that could take a long while as well.
agel1 said:
sorry dont understand
Im already rooted and with twrp installed
Click to expand...
Click to collapse
Bad reading by me. Sorry.
Nevertheless you can upgrade to 7.1.1 by flashing the lite ROM of Danvdh.
There is a possibility that dirty flashing will cause reboot issue. Backup first and update your bootloader and radio before flashing the ROM.
There's a thread with flashable zips with latest bootloader/radio.
https://forum.xda-developers.com/showthread.php?p=59728002/
Latest TWRP: https://eu.dl.twrp.me/shamu
Why is everyone recommending the difficult ways???
Just download the OTA image from google and sideload it from your PC.
You don't even need TWRP, unloaded bootloader or root access to do it and you won't loose any data or settings.
More info and OTA images at https://developers.google.com/android/ota
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
TeamRainless said:
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
Click to expand...
Click to collapse
Same here waiting for it as I hope it fixes the Android Auto connectivity issue .... wonder why it takes so long
Italy, XT1900-7 RETEU stuck on 8.0 August patch here, too.
I hope they're working hard on Pie!
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Same here
TeamRainless said:
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Click to expand...
Click to collapse
Same here ... just started the installation, but I doubt it will be an 8.1 update based on numbers it's "just" a security update ... will see what it fixes and what will be broken I would love to have Android Auto working without errors
the same **** here
Can I install thiw wia TWPR because i am rooted and I can not update?
vidra said:
Can I install thiw wia TWPR because i am rooted and I can not update?
Click to expand...
Click to collapse
No, only with stock recovery and all stock partitions.
Comby_sk said:
No, only with stock recovery and all stock partitions.
Click to expand...
Click to collapse
So if I restore /boot I should be able to do it?
vidra said:
So if I restore /boot I should be able to do it?
Click to expand...
Click to collapse
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Comby_sk said:
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Click to expand...
Click to collapse
I cannot seem to find it, can you please link it?
vidra said:
I cannot seem to find it, can you please link it?
Click to expand...
Click to collapse
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I don't have the permission to download the OTA.
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I keep getting E: failed to mount / if i use sideload and failed yo unmount / if I try to install from sdcard in official recovery.
How do I solve that?
Reboot to bootloader and check software status is official.
Comby_sk said:
Reboot to bootloader and check software status is official.
Click to expand...
Click to collapse
I have falsed everything back but it says modified. Did I miss something?
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Comby_sk said:
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Click to expand...
Click to collapse
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
vidra said:
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
Click to expand...
Click to collapse
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Abhishek Survase said:
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Click to expand...
Click to collapse
So how con I install the OTA?
I've read about updating to the latest OTA and keeping root from several places including from topjohnwu himself but still a little unclear about this and don't want to mess it up. So in the manager I click uninstall and then press restore images. Then apply the system update? I'm not understanding if I have to download the new boot.img to re-root? That's where I am confused.
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
Ok thank you. Unhiding magisk is not necessary?
qman66 said:
Ok thank you. Unhiding magisk is not necessary?
Click to expand...
Click to collapse
I don't think so
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
Is this pixel specific? Or do you think this would work on the 7T as well
In theory it should work with any phone that has A/B (dual partitions) support.
Pixeling said:
1. Uninstall and restore images
2. Install OTA (Do not reboot)
3. Install Magisk --> Install to inactive slot. This works because magisk is still running as root and can patch the flashed boot.img.
4. Reboot
Click to expand...
Click to collapse
One question. I have viper4android installed and I'm wondering when I uninstall and restore images, then update, will I lose viper and have to reinstall and redo all of my settings when I reinstall magisk?
rellomar said:
One question. I have viper4android installed and I'm wondering when I uninstall and restore images, then update, will I lose viper and have to reinstall and redo all of my settings when I reinstall magisk?
Click to expand...
Click to collapse
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Badger50 said:
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Click to expand...
Click to collapse
delete
Badger50 said:
I don't know what will happen via the OTA method, however, I can speak from experience that if you do your updates via fastboot and factory images, you will retain your V4A settings. I simply disable all of my modules, reboot, patch the updated boot.img, remove my face ID, fastboot the factory image with the -w removed, let it boot up, then fastboot the patched boot.img, boot up, enable my modules, reboot, and everything is as it was :good:
Click to expand...
Click to collapse
Could you possibly give me little more detailed instructions? I'm just coming back to Android after using an iPhone for a few years so I'm a little out of the loop with flashing. Mainly, I'm confused when you said fastboot flash the the factory image with the -w removed.
rellomar said:
Could you possibly give me little more detailed instructions? I'm just coming back to Android after using an iPhone for a few years so I'm a little out of the loop with flashing. Mainly, I'm confused when you said fastboot flash the the factory image with the -w removed.
Click to expand...
Click to collapse
After you download and extract the factory image, you will see a file named, flash-all.bat. Within that file, toward the end of the script, you'll see the -w flag which tells the script to wipe your device. By removing that flag, your are essentially updating your OS without loosing any internal data kinda like an OTA does :good:
with magisk installed how we can check whether we have update on the road, simply check in settings work?
Badger50 said:
After you download and extract the factory image, you will see a file named, flash-all.bat. Within that file, toward the end of the script, you'll see the -w flag which tells the script to wipe your device. By removing that flag, your are essentially updating your OS without loosing any internal data kinda like an OTA does :good:
Click to expand...
Click to collapse
That worked. Thanks for the advice....makes updating very easy :good:
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
NickEspo said:
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
Click to expand...
Click to collapse
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Tulsadiver said:
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Click to expand...
Click to collapse
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
NickEspo said:
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
Click to expand...
Click to collapse
Yes, though I normally fastboot the factory images rather than sideload an ota. That update process will lose root, then you patch the boot.img and fastboot it to regain root. I would recommend removing all modules prior to updating as they will survive the update process (unless you wipe) and if not compatible with your update, will bootloop you once you root again.