Anyone have the update patched for users with twrp/rooted with custom kernel?
Can't seem to find where to get it. I have the update from Google waiting..
no ota's for custom recovery, gotta either restore stock enough (system image and boot image backup in twrp before mounting system as read/write) to take the ota and reroot or download the big factory image and just flash the /system and boot parts and reroot. kinda sucks but chainfire is supposedly working on updating flashfire to apply these small ota's on modded software
StykerB said:
no ota's for custom recovery, gotta either restore stock enough (system image and boot image backup in twrp before mounting system as read/write) to take the ota and reroot or download the big factory image and just flash the /system and boot parts and reroot. kinda sucks but chainfire is supposedly working on updating flashfire to apply these small ota's on modded software
Click to expand...
Click to collapse
Ok. Thanks for the useful information. Maybe it is time to go back to a custom rom then..
I used Wugfresh's Toolkit to flash the security patch while keeping all my data. Just had to reroot when done. Took me no more than 1/2 hour. Super easy with Wugfresh.
Sent from my VS980 4G using Tapatalk
MightyT01 said:
I used Wugfresh's Toolkit to flash the security patch while keeping all my data. Just had to reroot when done. Took me no more than 1/2 hour. Super easy with Wugfresh.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I use the same toolkit. It is very complete and we'll made. I was under the impression it would not flash in any way if the system partition was touched.
I decided to go with another rom. Really like blissrom. Although I have used purenexus (great rom) and chromium in the past.
There's a great FAQ on Wug's site that held my hand. I'm running stock and rooted. You basically flash the latest patched version but get to keep all your apps and settings. I was stunned at how easy it was. It was my first try at updating this way and went perfectly.
Sent from my VS980 4G using Tapatalk
MightyT01 said:
There's a great FAQ on Wug's site that held my hand. I'm running stock and rooted. You basically flash the latest patched version but get to keep all your apps and settings. I was stunned at how easy it was. It was my first try at updating this way and went perfectly.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the info. I will check it out.
I just used Wugfresh's toolkit last night to update both my rooted stock Nexus 7 2013 and my rooted, stock Nexus 6. Just make sure you remember to check "no-wipe" mode when you unroot
Related
I'm reading the threads and seeing a consistent pattern (and experienced it myself). Referring at least to 4.1.2 -> 4.2 and 4.2 -> 4.2.1, it seems that you can do the OTA update if you if you have CWM but not TWRP. If you accept the OTA and have CWM, it will reboot into CWM, apply the update, ask if you want to preserve recovery and su, and reboot you into the new version.
If you have TWRP, though, it seems people get stuck at error 7 or similar.
When a larger version comes out in the future though I suspect we'll have to flash by hand as the OTA could blow away custom recovery; but for the two mentioned above at least, it wont kill CWM and installs fine with it in place.
I've loved TWRP in the past, but in this case it looks like CWM is handling the OTAs more gracefully. It's just a random chance that I have the latest CWM on my N7 instead of TWRP.
I have never used twrp, but I have done the last updates through cwm recovery and kept recovery and kept root. Definitely recommend cwm recovery.
I just got the OTA here, on TWRP 2.3.2.1, Nexus 7 no 3G. No errors, just worked.
Yeah just got the new update and I'm still rooted
-Google
iGoogleNexus said:
Yeah just got the new update and I'm still rooted
-Google
Click to expand...
Click to collapse
And you are using which recovery?
Both work. If they don't something else is going on.
Sent from Tapatalk XDA Premium
<><><><><><><><><><><><>
Nexus 7
Clean ROM 3.0 - Leankernel 0.8.x
jb0ne said:
And you are using which recovery?
Click to expand...
Click to collapse
CWM ...
-Google
Worked for me using TWRP
Sent from my SAMSUNG-SGH-T989 using xda premium
Just took the 4.2.1 update im still rooted using TWRP...
Status 7 is usually a security thing regarding the signature I think. If anything CWM has signature verification off by default.
Sent from my Nexus 7 using XDA Premium HD app
I really don't understand why people are having such a hard time understanding what is wrong when they receive an error message with the OTA update.
It's not complicated people. You don't need to be a friggin' brain surgeon or a senior level developer. The error message TELLS YOU what the issue is.
Verifying current system...assert failed: apply_patch_check("/system/SOMEFILE")
Guess what? Something is wrong with SOMEFILE. You either modified it, deleted it, "froze" it in TiBu, or did something else that is causing the update to break.
If you look at the updater-script, you can see everything thing the OTA does. It's just a long batch script basically.
The ONLY way this 4.2.1 OTA update is going to fail due to recovery is if you are using the wrong recovery for your device (ie: grouper on talapia, etc.).
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
jersonf said:
I hear what you are saying but....my N7 is stock, untouched, unlocked & rooted, yet I had problems with CWM & TWRP with the OTA and flashing the update manually.
I had to go back to stock recovery for both updates.
But I can see in this thread some have the OTA update working fine, one thing we all have in common is the N7, yet varied results.
Click to expand...
Click to collapse
Was your unit a 3G or Wi-Fi only model?
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What are you talking about?
XDA is in no way a site dedicated exclusively to "help people not use the stock software". It's a place where people can discuss their hardware/software including stock/custom/etc. usage and modifications. So not only is your comment 100% incorrect, but it's also contrary to this thread in particular. The thread title clear talks about using a CUSTOM recovery with an update to the stock software. So even if you were right (you aren't), your point is counter-intuitive.
There are many people here that are either mostly or completely stock. That's their personal preference and it's completely fine and acceptable. And it most certainly doesn't mean they don't deserve help or assistance here.
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Also, while OTA updates are written in such a way to remove suid root on the su binary and reinstall the stock recovery image, most new custom recoveries have a work around in place to prevent this. Not to mention it's trivial to restore them back after the update.
brizey said:
OTA?
I hate to be the hater, but why would anyone here take an OTA? The reason this site exists is specifically to help people to not use the stock software. If cwm survives OTAs it is probably an accident, lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
No accident ... I updated my N7 from 4.1 to 4.2 still rooted.. And I just updated again to 4.2.1 ... Don't know about you but I love these kind of updates
Also I like my devices stock, rooted and a few tweaks here and there along with rooted applications... I'm sure there are many of me out there.
-Google
I prefer to never actually flash the recoveries.. just adb boot them as required - that means my system is always stock for the updates and I can pick a recovery at random should I want them (although generally I only use them to get a root shell to install su when I get a new phone).
I am rooted stock with cwm touch and the ota fails staus 7. I'm pretty sure I didn't do anything to "break" the update for myself. It's kind of funny the clockwork stops and asks about flashing an untrusted rom and then doesn't allow it. I would rather sit out of this whole 4.2 bs anyway.
I was rooted and stupidly just clicked the update to 4.2.1 without thinking, it didn't even occur to me to take any measures to keep root or custom recovery. So I lost both. It only took a few minutes with Wugs' toolkit to fix though.
I've taken three OTAs with TWRP and had no problems with any of them.
Sent from my Nexus 7 using Tapatalk HD
I am already rooted with xposed installed on Verizon and got the notification for the Kitkat OTA update -- which thread do I follow to safely take the OTA KitKat update? Thanks.
libertao said:
I am already rooted with xposed installed on Verizon and got the notification for the Kitkat OTA update -- which thread do I follow to safely take the OTA KitKat update? Thanks.
Click to expand...
Click to collapse
You can just try to take it as long as you have stock recovery installed (TWRP/CWM/PhilZ will cause a soft-brick situation), but depending on what Xposed modules you use and the changes made it could likely fail.
The safest and best way would be to factory restore the firmware via this: http://forum.xda-developers.com/showthread.php?t=2448960, then take the OTA to 12B, followed by the OTA to 24A. The whole process is pretty painless, I did it going from an old CarbonROM build to the latest stock KitKat in about an hour and a half or so.
acejavelin said:
You can just try to take it as long as you have stock recovery installed (TWRP/CWM/PhilZ will cause a soft-brick situation), but depending on what Xposed modules you use and the changes made it could likely fail.
The safest and best way would be to factory restore the firmware via this: http://forum.xda-developers.com/showthread.php?t=2448960, then take the OTA to 12B, followed by the OTA to 24A. The whole process is pretty painless, I did it going from an old CarbonROM build to the latest stock KitKat in about an hour and a half or so.
Click to expand...
Click to collapse
To add, you can re-root with ioroot25 and if you need a recovery for any reason, use AutoRec to install the latest TWRP. You need to jump through a few hoops to install recovery on KK and it does them for you. If you plan on staying on the stock rom, I would leave the stock recovery.
mjones73 said:
To add, you can re-root with ioroot25 and if you need a recovery for any reason, use AutoRec to install the latest TWRP. You need to jump through a few hoops to install recovery on KK and it does them for you. If you plan on staying on the stock rom, I would leave the stock recovery.
Click to expand...
Click to collapse
In my opinion, ioroot25 only does a partial root, there is BusyBox installed with SuperSU... I would also recommend doing a manual BusyBox install (Play Store has several free installers) for a "full" root install.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
In my opinion, ioroot25 only does a partial root, there is BusyBox installed with SuperSU... I would also recommend doing a manual BusyBox install (Play Store has several free installers) for a "full" root install.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I forgot about that, I just used the app store BusyBox installer and it worked great.
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)
GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.
Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now
I have rooted my phone, but am not doing any custom ROMS or anything. I notice that I have an OTA update, and figure that it may be in my best interest to install it, and it would stop nagging me then too. I know if i un-root, I will loose everything. I use Titanium backup. So if I do a full backup, un-root, install update(s), re-root, I can re-install Titanium (I have the paid version) and recover everything right where I left off correct?
I am assuming that you unlocked the bootloader even though you are just rooting. That is how I roll. If so it would be far easier to download the latest image for your phone and flash it. Just skip flashing the user partition. That will save your apps, data and settings.
It is a 10 minute process and far less prone to errors. TI backups are great but can create lots of little gremlins when you restore them.
And with root there are so many other things you could have changed that might cause the update to fail that it just isn't worth the effort.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
I am assuming that you unlocked the bootloader even though you are just rooting. That is how I roll. If so it would be far easier to download the latest image for your phone and flash it. Just skip flashing the user partition. That will save your apps, data and settings.
It is a 10 minute process and far less prone to errors. TI backups are great but can create lots of little gremlins when you restore them.
And with root there are so many other things you could have changed that might cause the update to fail that it just isn't worth the effort.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
therealcrazy8 said:
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
Click to expand...
Click to collapse
Googling "nexus factory images" will get you where you need to go. But also I'd like to add that on the SuperSU forums there are posts about using the SuperSU app's built in "full unroot" feature with systemless root allows usage of ota's. It works by just restoring a backup of your boot image that the SuperSU.zip takes before rooting with the new systemless root method. The caveat to this is that when you install the zip via TWRP you need to select the "Leave /system read-only" option upon first install and also not mount /system as R/W at any time during your usage of root.
The way I've personally been doing ota's lately is just taking a "system-image" backup in TWRP before modding anything that way when the ota rolls around I just restore the backup, apply the ota update the backup reflash twrp and root. Doesn't really save any time versus using a factory image but 10mb ota vs 2gb image is easier for me with crummy data limited internets
StykerB said:
...The way I've personally been doing ota's lately is just taking a "system-image" backup in TWRP before modding anything that way when the ota rolls around I just restore the backup, apply the ota update the backup reflash twrp and root. Doesn't really save any time versus using a factory image but 10mb ota vs 2gb image is easier for me with crummy data limited internets
Click to expand...
Click to collapse
Interesting. As a rooted user though, why is flashing the entire (new) factory image an option, rather than just cherry-picking the files that you need (i.e boot.img, radio etc if altered)? I mean, I realize that you still have to download the whole image, but there are far fewer steps involved to getting a revised security update on your device than with resurrecting a stock Nandroid, applying the OTA, and then rooting again.
therealcrazy8 said:
Awesome! Good to know. I know how to use the search function, but what should I search for to find how to do what you've recommended?
Thanks again
Click to expand...
Click to collapse
At the top this sub forum is an FAQ that will get you going. Also in the development forum is a thread for Wugfresh NRT toolkit. It will do everything you need.
The option you are looking for in that is the 'no wipe' option to save your data.
But you should do it manually first, so you understand what is what if something goes wrong. And you should TI backup just in case.
If it bootloops or freaks out don't panic. It is fixable, as long as the bootloader is unlocked.
Sent from my Nexus 6 using XDA Labs
Not_A_Dev said:
Interesting. As a rooted user though, why is flashing the entire (new) factory image an option, rather than just cherry-picking the files that you need (i.e boot.img, radio etc if altered)? I mean, I realize that you still have to download the whole image, but there are far fewer steps involved to getting a revised security update on your device than with resurrecting a stock Nandroid, applying the OTA, and then rooting again.
Click to expand...
Click to collapse
It's only restoring the /system so data and apps remain but the main goal of mine is just saving data by not having to downloading a factory image. Regardless of how you do it you still have a PC in the mix at some point so I might as well save some of my data plan.
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
bluesrph said:
So far I've been running my OP3T with stock rom with TWRP recovery and SuperSU to have root. This was mostly because I wanted the Adaway and titanium backup to work. I undid everything so I could update to the latest OxygenOS version, and now I'm on the stock recovery too, but with bootloader still unlocked I believe. I no longer have root after doing the upgrade as far as I can tell, still a bit new to all this flashing, haha. The last time I did this was when the nexus 4 came out
What is the best option for maintaining root while still being able to upgrade smoothly? I'm not against using one of the custom ROMs if that will help, but I do kinda like the stock rom so far!
thanks!
Click to expand...
Click to collapse
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
saurabh40629 said:
This thread should answer all your questions and doubts
https://forums.oneplus.net/threads/...-or-custom-recovery-without-data-loss.479265/
Click to expand...
Click to collapse
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Click to expand...
Click to collapse
Dm-verity u can bypass but bootloader one, you can not. Look at the apps, mods section.
bluesrph said:
Thank you, I have seen that post. I'm guessing any route I go I'll have to flash updates then? I was hoping to find a way to be able to use OTA updates.
I've also never been able to get rid of the dm-verity error, even after going back to stock and locking the bootloader. Is there anything I need to worry about with that or is it just an annoyance?
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
You shouldn't try to flash the partial OTAs while you are rooted and have a custom recovery installed. The partial zip will try to make specific changes in the restricted partitions (/system, /boot, /recovery, etc.) related to the update and prior modifications to these files may cause the update to fail and the phone to brick. You can still use the "Update" tab in the Settings menu to download the update though as OOS will detect root and download the full zip of the update for you. Simply flash the full zip in TWRP, wipe cache/dalvik, then flash SuperSU and you're good to go the next time an update rolls out. Updating by this method (rooting immedately after flashing update) will also prevent OOS from replacing TWRP with the stock recovery again. When you download the update, you'll know if it's the full zip if the file is >1 GB (they're usually ~1.4 GB,, whereas the partial zips are a few hundred MB).
Unlocked bootloader warning screen is cannot be removed without relocked and fully resetting (wiping) the phone. DM-verity warning screen can be removed by following this guide. Make sure that you are flashing the correct firmware for you current version of OOS though, flashing the wrong version can brick you phone.