Related
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Dan Again said:
I recently followed this guide to root my XT1095. All I did was unlock my bootloader and boot the image...I did not (intentionally) alter my recovery, nor did I install a custom ROM. Will I still receive OTA update notifications and, if so, are they safe to apply?
Click to expand...
Click to collapse
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
grneyez said:
If you are running a custom recovery TWRP for example, I doubt that you will get OTA updates. I believe you need the stock recovery to be able to install OTA updates.
Click to expand...
Click to collapse
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Dan Again said:
I'm a little confused by your response. As I said in my original question, I did not (intentionally) alter my recovery. Did the method that I used achieve root alter my recovery for me?
Click to expand...
Click to collapse
As long as you don't make any changes to /system, you *should* be good to go for updates. If you didn't intentionally flash a custom recovery then you still have the stock one.
If you're rooted OTAs won't work. In KitKat and lower they just performed checksums on each file before updating, so the altered root files were left untouched and the update installed. In Lollipop and up (at least for Nexus devices), it does a total checksum and if /system has been altered in any way (including for root) OTA's won't install.
grneyez said:
If you did not install a custom recovery than you should be able to get OTA updates. Check to see what recovery you have.
Click to expand...
Click to collapse
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Dan Again said:
Thanks for all the responses, guys. I booted into recovery and saw this, so I think my recovery is still stock. One quick question: when I boot into fastboot and select "Recovery", I get a dead Android and a "No Command" prompt - I had to follow these steps to actually get there. Why is that?
I'd like to try out Xposed now that it's available for my device, and I see that requires a custom recovery. If I install a custom recovery (TWRP, for instance) and use it to flash Xposed, can I then revert back to stock recovery and continue to receive OTA updates?
Click to expand...
Click to collapse
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Dan Again said:
Fair enough. So let's say that I install a custom recovery and then Xposed. Will there be a way that I can manually upgrade to new stock OS versions as they come out for my phone?
Click to expand...
Click to collapse
You can always flash a ROM or custom ROM via fast boot, but you will loss all your settings, apps etc because you are flashing an entire new system... The OTA only patches
The only way back is to flash your stock ROM if you can get a hold of it.
floepie said:
The only way back is to flash your stock ROM if you can get a hold of it.
Click to expand...
Click to collapse
So, funny story - this weekend I accidentally wiped my OS and had to flash stock ROM to get back up and running. See: here. Good resource for others who might be looking for Moto X 2014 stock Lollipop firmware...definitely saved that on my computer
juliospinoza said:
If you modified your system with Xposed you won't be able to install OTA updates. Even if you return yo stock recovery.
To install an OTA you need three things. 1. Unaltered system, 2.no root and 3. stock recovery
Click to expand...
Click to collapse
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
yurkennis said:
Isn't there any way to uninstall Xposed, revert back to original recovery and remove root--all in order to install OTA without completely loosing user data and apps installed?
Click to expand...
Click to collapse
yes
just flash via fastboot
1. recovery (stock)
2. system
if your phone is 5.0 xt1095 and you didn't flash modems you should be able to receive OTA.
Repeat of Question
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
jhworth8 said:
I'm not sure I completely understand what I need to do to get updated to 5.1. I have an XT1095 that I only rooted, no custom recovery. I downloaded the OTA for 5.1 last night and tried to update. Got an error and it did not update. A quick google search seems to state, as well as earlier in this thread, that I can not update if I am rooted. I would prefer not completely start over on my phone (wipe) and would like to just apply the update. Can I just "unroot" my phone and apply the update or do I have to go back to the beginning (with a stock recovery) before the update will take?
I know enough about all this to have followed the directions to accomplish the root about 7 months ago. Since then not played with any system files! The only reason I rooted was so I could use the full capabilities of Greenify. Any opinions on that would be appreciated as well. Thanks!
Click to expand...
Click to collapse
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
AGISCI said:
Try reading, the post literally before yours tells you what to do, lol.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
summit15 said:
I take it that flashing the recovery and the system.img files to the phone will not erase all the apps, photos, music, etc.?
Click to expand...
Click to collapse
Correct, it won't erase those things.
Sent from my XT1095 using Tapatalk
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
yamahakid said:
so if i am just rooted, and custom recovery, could I unroot (via supersu app) and flash stock recovery and be good to go? or am i missing something?
Click to expand...
Click to collapse
It's more difficult with Lollipop: updates now "look for" a completely stock unmodified unrooted system. So you'll have to flash a stock image of the current build and then take the OTA.
So I've read a couple threads on this, but I'm still confused.
I want to update through OTA, but not encrypt my phone, ultimately.
Is this how it's done?
Flash Stock system, boot, bootloader, recovery (5.0.1)
Boot to stock recovery, adb sideload OTA
Reboot to bootloader
Flash custom boot w/o forced encryption
Reboot?
I think when I unencrypted back then, I had to make a full wipe? I want to avoid this.
George_Mn said:
So I've read a couple threads on this, but I'm still confused.
I want to update through OTA, but not encrypt my phone, ultimately.
Is this how it's done?
Flash Stock system, boot, bootloader, recovery (5.0.1)
Boot to stock recovery, adb sideload OTA
Reboot to bootloader
Flash custom boot w/o forced encryption
Reboot?
I think when I unencrypted back then, I had to make a full wipe? I want to avoid this.
Click to expand...
Click to collapse
It would be best to wait for a 5.1 no-force boot.img to be released first. And also, wait until the 5.1 systemn.img is available. Then flash 5.1 system.img and the nboot.img of your choice.
rootSU said:
It would be best to wait for a 5.1 no-force boot.img to be released first. And also, wait until the 5.1 systemn.img is available. Then flash 5.1 system.img and the nboot.img of your choice.
Click to expand...
Click to collapse
Didn't Google want to ditch force encryption with 5.1?
George_Mn said:
Didn't Google want to ditch force encryption with 5.1?
Click to expand...
Click to collapse
The only change we're expecting is that they may move from software to hardware encryption.
Though you could test it if you believe that to be the case.
rootSU said:
The only change we're expecting is that they may move from software to hardware encryption.
Though you could test it if you believe that to be the case.
Click to expand...
Click to collapse
I just read a post of someone saying 5.1 does not add an option to unencrypt.
rootSU said:
It would be best to wait for a 5.1 no-force boot.img to be released first. And also, wait until the 5.1 systemn.img is available. Then flash 5.1 system.img and the nboot.img of your choice.
Click to expand...
Click to collapse
is there no way to create a 5.1 no force boot.img from the 5.1 OTA or from the system files on the phone after the 5.1 OTA was applied?
thafngame24 said:
is there no way to create a 5.1 no force boot.img from the 5.1 OTA or from the system files on the phone after the 5.1 OTA was applied?
Click to expand...
Click to collapse
I don't know enough about unpacking boot,imgs to answer that.
I am also looking for the same thing. Sideload the OTA zip file and keep it unencrypted.
I am currently on FK and I was thinking to do this:
Flash stock 5.0.1 boot.img
Sideload the OTA
Flash unencrypted 5.1 boot.img
Of course no reboots in between to avoid the encryption.
Any thoughts?
Ladduro said:
I am also looking for the same thing. Sideload the OTA zip file and keep it unencrypted.
I am currently on FK and I was thinking to do this:
Flash stock 5.0.1 boot.img
Sideload the OTA
Flash unencrypted 5.1 boot.img
Of course no reboots in between to avoid the encryption.
Any thoughts?
Click to expand...
Click to collapse
We got the factory images now, so you don't have to flash 5.0.1 first.
5.1.0 Shamu
Is there an unencrypted 5.1 boot yet?
George_Mn said:
We got the factory images now, so you don't have to flash 5.0.1 first.
5.1.0 Shamu
Is there an unencrypted 5.1 boot yet?
Click to expand...
Click to collapse
Yes, here http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Ladduro said:
Yes, here http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
Click to expand...
Click to collapse
I messed it up. Flashed everything (but the custom boot.img) and then tried to root (Cause I wanted to flash a mod through twrp) which lead into a boot which I didn't interupt quick enough.
It now just says "Encryption unsuccessful" and that I have to reset it. I even tried flashing everything again (including new unencrypted boot.img) Oh well.. Most stuff was backed up so whatever..
George_Mn said:
I messed it up. Flashed everything (but the custom boot.img) and then tried to root (Cause I wanted to flash a mod through twrp) which lead into a boot which I didn't interupt quick enough.
It now just says "Encryption unsuccessful" and that I have to reset it. I even tried flashing everything again (including new unencrypted boot.img) Oh well.. Most stuff was backed up so whatever..
Click to expand...
Click to collapse
Sorry about that...
Ladduro said:
Sorry about that...
Click to expand...
Click to collapse
Happens! I literally got everything backed up but Whatsapp so at least I got a fresh phone now lol. And it's unencrypted!
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
bovineyard said:
Many of you have heard by now that 5.1.1 is out, and we should receive an update soon on our stock rom Nexus 6. I just bought a Nexus 6 64gb, XT1103, and it is running the stock rom, rooted, and un-encrypted. I'm wondering if we'll lose root and un-encrypt if we take the update, and loose data if we re-unencrypt. What have your experiences been on the stock rom 5.1 update?
Click to expand...
Click to collapse
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
cam30era said:
While the update will download, it will not install with root and an unencrypted kernel.
IF you want to take the OTA, then you will need to fastboot flash the boot.img and system.img from the factory image. Boot.img will encrypt your kernel, but you will not loose data (but you will have to factory reset, again, if you want to unencrypt, which will wipe data). Flashing the system.img will remove root and flash stock recovery.
Click to expand...
Click to collapse
i think with root but encrypted will do the update
HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
cam30era said:
Nope, not on Lollipop. Kitkat and before, yes. Not anymore.
Click to expand...
Click to collapse
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
5.1.1 is NOT officially out for the nexus 6. it is in aosp though. thats two differing things. stock is on 5.1.
HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
The OTA package only looks at system.img and boot.img. Of course you need stock recovery to install it. And the "unroot" option inside SuperSU is insufficient. It leaves some traces around that will prevent the OTA from loading. Flash the stock system.img.
And afterwards, when unencrypting, you'll have to fastboot format userdata. Which will wipe your SDcard again.
HitNrun_ said:
so unroot and encypted will do the trick? what about the bootloader, will it work with unlocked or should it be relocked too?
Click to expand...
Click to collapse
Bootloader status has no effect on the OTA.
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
ibraheeemz said:
I have rooted, but encrypted 5.1, and got OTA5 5.1.1, I am on custom recovery,
should I flash stock recovery before flashing? plus, after installing, I will need to regain root access right? my data/apps will stay intact right?
Click to expand...
Click to collapse
As it says above, you cannot FLASH the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
danarama said:
As it says above, you cannot receive the update if you are rooted, even with a stock recovery.
You will have to flash the system.img and boot.img of the Stock factory image. IF the full factory image of the version you want is available here: https://developers.google.com/android/nexus/images
...download it, extract the system and boot.img and fastboot flash them. Job done. If the version you need is only available in an OTA file, you'll need to flash the system and boot of the expected version (i.e. the one you're on now) AND flash the recovery to accept the OTA
Click to expand...
Click to collapse
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
ibraheeemz said:
I am using a custom recovery, on a rooted but STOCK 5.1, and I already got OTA, I downloaded it as well, but needed to make sure before upgrading, that it doesn't cause data lose if I move to stock recovery, and want to regain root after flashing 5.1.1,
anyway, i flashed stock recovery, then proceeded with the update, it tried flashing but showed "error" at the android screen, so, I don't whats missing, as I was using stock 5.1, just unlocked it, rooted it, and flashed customer recovery,
Click to expand...
Click to collapse
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
danarama said:
When I said receive, I meant flash. You cannot FLASH the update if you are rooted. Period. Read my post again but substitute the word receive for flash.
Click to expand...
Click to collapse
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
ibraheeemz said:
got it, but still looking for the answer, will I loose data after flashing system.img? or while regaining root after 5.1.1 update?
Click to expand...
Click to collapse
No. Only factory reset or unlocking the bootloader loses data. System.img is the rom, flashing to /system. Boot.img is the kernel, flashing to /boot. if you flash these separately, userdata.img is not flashed to /data, so your /data partition remains in tact.
root doesn't touch /data either. Just /system
HitNrun_ said:
i think with root but encrypted will do the update
Click to expand...
Click to collapse
How do you get root while leaving it encrypted?
Arfyness said:
How do you get root while leaving it encrypted?
Click to expand...
Click to collapse
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Evolution_Tech said:
No OTA update will flash with any mods to system, boot, or recovery. No way, no how.
Click to expand...
Click to collapse
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Arfyness said:
Yeahhh I get that now. It's got to verify that what's already there matches what it's supposed to be updating.
I'm looking here because I'm on Fi now, and there are more implications there than I realized before. Not that those matter too much, I do want stock. Just trying to see how I can stay current, be rooted, and not break Fi. Thankfully it's a Nexus device so it's not throwing up insane device restrictions blocking root access.
I want to be able to update system and boot, as they come available, with a recovery like TWRP or CWM. Then reapply SuperSU flash after that. What I'm not sure of is whether I can even do that. I'm fuzzy on the whole " encrypted device" thing. Does that apply to the images at https://developers.google.com/android/nexus/images#shamu
Would I be hosed if I took the system and boot images and flash those to update from one version to the next?
Click to expand...
Click to collapse
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
edit - this was a duplicate. i can't delete it.
Evolution_Tech said:
You absolutely can, it's just that if you wish to decrypt, you'll have to format data. I've had this device, since launch and I'm still encrypted. Not an issue for me. But you can just flash, individually, everything but userdata and keep your data intact, each time a new image becomes available. Then just flash TWRP and then SuoerSu from TWRP. If you've unencrypted, OTA won't flash. You can always update manually.
Click to expand...
Click to collapse
Oohhh, wait, so flash from fastboot, except flash SuperSU from TWRP? (update.zip style?) Is only the data partition encrypted then? If that's the case why are folks decrypting? Unlocking the bootloader requires it, but what is that required for?
And thank you loads BTW! I'm so far behind! I'm coming off 3 years of rooted, stable SGS3 stock, last updated to 4.1.2. There were no further stock updates that I wanted, (too many bugs) and everything was working so I left well enough alone.
(I probably would have messed about with CM and other roms, if I had not initially bricked the thing trying to put TWRP on... and had to send it for somebody to JTAG reprogram it. Thought about it several times, but never wanted to chance it again.)
Thanks again!
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Evolution_Tech said:
Hi, no modifications to system (including recovery) or boot can be present for OTA to flash. Look here:
http://forum.xda-developers.com/showthread.php?t=2992919
Click to expand...
Click to collapse
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
greycobalt said:
Well that's a bummer! Thanks for the link. It looks like sideloading will still work, is that correct? If so, is it possible to sideload an update without wiping my data or factory resetting?
Click to expand...
Click to collapse
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
greycobalt said:
I've been receiving the prompt to update my N6 to 5.1.1 for the past few days, but whenever I attempt to install it, it says it's rebooting and does nothing. Is this because I'm rooted? Besides being rooted, there's no modifications to the system (well, except for Franco Kernel and MCR I suppose...). Is it even possible to update this way? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Hi hi. Made me smile. Thanks for that.
Evolution_Tech said:
If your bootloader is unlocked, just do this:
Download the factory image for the new build you want.
Extract twice to end up with the bootloader, radio, boot, system, recovery, userdata, and cache images.
Flash each image individually with fastboot except for userdata.
You will be updated and won't lose data. Then, just flash TWRP again and then from TWRP, flash the superSU zip. You will be stock rooted, with TWRP recovery. All your data will remain.
If you try to flash official OTA via sideload, it will still fail because of root and custom recovery.
Click to expand...
Click to collapse
I will definitely do this! Thanks. They haven't posted the Verizon 5.1.1 to the image site yet, so I'll have to wait a bit I guess. :-/ Thanks!
Didgeridoohan said:
Hi hi. Made me smile. Thanks for that.
Click to expand...
Click to collapse
Can someone explain this to me as to why https://android.googleapis.com/pack...amu-ota-LMY48I-from-LMY47Z-superblock-fix.zip gives me the following error shown in the attach picture?
Looks like it should match correctly but sideload is errorring out saying otherwise
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>adb shell getprop ro.build.fingerprint
google/shamu/shamu:5.1.1/LMY47Z/1860966:user/release-keys
C:\Users\Double\AppData\Local\Android\android-sdk\platform-tools>
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
david279 said:
Do it from stock recovery. It's kinda broken in twrp because twrp was build with a build.prop with old user keys so it won't let you flash it. All the Ota zip will see is those old user keys and kill it every time. Stock recovery will work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
Install the stock recovery in fastboot, you can download it from the factory images or just search for it
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
I'm having the same problem with TWRP and the TMO LYZ28J update. How do I get back to stock recovery? Is it just a matter of uninstalling TWRP and reinstalling it when I'm done?
Click to expand...
Click to collapse
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
danarama said:
If you have TWRP, chances are your rom would be modified in some way so the OTA Won't work anyway.
Click to expand...
Click to collapse
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
JimSmith94 said:
I'm stock rooted, are you saying that won't work? What's the proper way to install this update without losing data?
I'm used to flashing updates from recovery, so this whole sideload thing is new to me.
Click to expand...
Click to collapse
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
danarama said:
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
Click to expand...
Click to collapse
There is an LYZ28J factory image available, here > https://developers.google.com/android/nexus/images
danarama said:
Correct, root is a modification. An OTA will not flash unless the rom and kernel are 100% as expected.. This is regardless of whether the OTA zip is flahsed in adb sideload or as an OTA natively.
If there is a J factory image available, fastboot flash the system.img and boot.img and you're updated.
If there is not, do the above but with the version the OTA expects. .. Then flash the OTA
Click to expand...
Click to collapse
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
JimSmith94 said:
Thanks for the info! Since Google says they will release these updates monthly, I'm hoping to find a simple, painless, and repeatable method to do these updates. Will flashing your suggestions lose root or data?
Click to expand...
Click to collapse
It will lose root, but you just flash supersu from recovery
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
doublejz said:
I had to flash the stock recovery back on and then did the OTA update. :-/ I really like my full system backups that TWRP does though..
Click to expand...
Click to collapse
Just flash the system.img then