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
Related
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Update just failed for me too, which having read up, looked like it might have been because of having an alternate recovery installed.
So I removed the recovery .................UPDATE FAILED
Removed root.....................................UPDATE FAILED
Locked Bootloader..............................UPDATE FAILED
Full system wipe.................................UPDATE FAILED
You can force a retry by going to App,------All-------Google Services Framework and stopping the process and wiping the data
Then checking for update manually.
Some folks say you can have problems with Play and push notification after the framework wipe, but as I had gone the route of restoring to default, I wasn't bothered as I will just do the same again.
I wonder if there is a deeper issue however, than just my tablet.
Phil
jonchill said:
I had the notification for 4.2 update yesterday morning and after pondering for the day I decided to initiate the upgrade which for some reason or another the update failed.
Is there anyway of finding out why the update failed and since the failure I've had no further notifications of the update so how can I try the update again?
Thanks
Jon
Click to expand...
Click to collapse
did you guys did anything or change anything from system, like change the proxyprovider.apk for flash support? Mine failed through OTA and even via manual update but then I changed back the those apks and things went well and now I am on 4.2. Just sharing my experience and hope it can help you guys. somewhat.
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
My tablet updated just fine and it is both rooted and unlocked. My galaxy nexus which is the same (both rooted and unlocked) for some reason fails on the 4.2 update.
I had the exact same problem over the past two days, I don't have a custom recovery, just unlocked bootloaded and root.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
OOOOOH! I froze then deleted the KOREAN IME app, because why the heck do I need a Korean app on my tablet? Hmm, so what are my options? Can I just redownload the Korean IME off the play store and OTA will work then?
Was there any other forced IME like Chinese that's 'baked in' to the Google ROM? I forgot if I may have deleted any others, but I think it was only Korean.
just lou said:
If you guys replaced the stock recovery, deleted or froze any stock apps,or modified any system configuration files, OTA is going to fail.
Click to expand...
Click to collapse
That explains it then I've deleted and frozen stock apps.
Thanks
I'm the same, i deleted system apps.
Is the only way to fix this to use a pc and adb the 4.1.2 zip and gapps?
Is there any way to fix it from the device itself?
(I've tried flashing the 4.1, 4.1.2 and 4.2 via CWM)
Would reflashing the 4.1 gapps help?
Sent from my Nexus 7 using xda premium
I had the same problem. Used titanium backup and the "integrate system apps updates into ROM" option and then couldn't update to 4.2.
Tried several things I read in this forum but nothing worked.
Had to erase everything and flash the stock ROM I downloaded from Google. They have a 4.2 stock ROM too so didn't need to update afterwards.
Then restore all your apps from backup and you are set.
Sent from my Nexus 7 using Tapatalk 2
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Chocoburger said:
Wow, all because a damn Korean IME app? Geez, what a pain, Google. :|
Click to expand...
Click to collapse
The alternative is that you restore your system folder to its original state (i.e. get hold of that Korean IME app, stick it back in /system/app and set the correct permissions). I had to do this with Google Wallet but it can be done if you know exactly what you've changed and avoids flashing a factory image and setting your device up again (albeit that Titanium makes this relatively painless now).
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
Me too. Also a 32gb N7. I owned it less than a week. Multiple factory resets didn't correct the issue either. I returned it to the store for a refund. Didn't want to keep a device that would never install updates.
I have 32 gigabyte Nexus 7 and it came with Android 4.2 out of the box so I guess no problems with the updates
Sent from my Nexus 7 using XDA Premium HD app
CFRTim said:
Have a brand new 32 GB N7, and having the same update fail, right out of the box, like wtf
Click to expand...
Click to collapse
So your saying you opened it, turned it on, signed in.....then your status bar should show system update available, click it, accept, let it do its thing and it just failed?
Sent from my Nexus 7 using Tapatalk HD
If you search the forums this has been addressed and solved. You need to reflash the os - you don't need root. Use wugs toolkit. Its a problem on googles end where the nexus was formatted incorrectly, and a reflash fixes it.
Sent from my Nexus 7 using Tapatalk HD
Yep. Got the Android robot on his back, with the triangle/exclamation point on top of him, after downloading, restarting and almost complete install. I've tried multiple times and miserably failed each time, at the same point. Eventually, I was able to manually update it using Wug's Nexus Toolkit, since all other methods failed. Thank you Wug
Sent from my Nexus 7 using Tapatalk 2
So finally Android 4.3 has arrived and our Beloved Nexus 7 is Upgradable Now.....
here is the link to the download of factory Image:
https://developers.google.com/android/nexus/images#nakasijwr66v
Follow this Method and flash the New Android OS...
[GUIDE] Flashing a Factory Image with fastboot / return to stock Thanks @comminus for a great Guide...
Report Back with screenShots and new featuers as well as Bugs because new pudates bring New Bugs.....
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
hassam_tariq2003 said:
The update brought a new bootloader version...android 4.2.2 had 4.18 and 4.3 has 4.23.....
Click to expand...
Click to collapse
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
tbonezx11 said:
Did you lose boot loader unlock or root when you installed 4.3? I'm assuming you used fastboot to install not OTA? Just curious...I'll be playing tonight when I get home.
Click to expand...
Click to collapse
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
mhl12 said:
You lose root but your bootloader remains unlocked.
Has anyone been able to root 4.3? Tried to root and flash custom recovery with the Nexus 7 toolkit, but I don't think it's working.
Click to expand...
Click to collapse
haven't tried it (I'm yet to receive the update) but someone referenced this link: https://plus.google.com/u/0/+Chainfire/posts/WqS2E9kkN1L
he is right.....You loose root but bootloader remains unlocked...
i have heard people say that you do not loose root if you use the OTA Method and your bootloader also remains unlocked....So its your choice its either Fastboot or OTA...
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Yeah OTA wont work for most people, seeing as they probably have a modified ROM. In any sense, chainfire has a root method that works. I can confirm it working, because I installed it using TWRP
khaytsus said:
Just use OTA Rootkeeper, you'll be fine.
Just remember kids.
You cannot use an OTA if your ROM is modified in ANY WAY.
Click to expand...
Click to collapse
When 4.2.2 came out I had problems updating because my ROM was modified. But someone modified OTA not to check for changes in ROM and it worked.
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
I am running 4.3 unlocked but I did the one click method for root using nexus tool kit and for some reason it did not work, I have to try again tonight.
Want a single click ADB setup? Go to my thread I've made a Tool for that. No need to download the whole SDK it's just 2MB
http://forum.xda-developers.com/showthread.php?t=2374071
What to know how to easily pull ota link with ADB follow my thread.
http://forum.xda-developers.com/showthread.php?t=2270429
For official nexus 7 windows 7 - 8 driver download them from ASUS site. No trickery needed.
Sent from my SPH-L710 using Tapatalk HD
Team SXTP
So, I played around a bit,
First of all, I did a "clean, unrooted and even locked bootloader install".
So I'm 1000% stock, just to avoid stuff like "maybe root caused it"..
(I locked it because I wanted to go 100% stock, just FYI, I know it's normally not necessary...)
The welcome screen was a bit weird... I got asked 2 times to tick or untick boxes for saving passwords and all that stuff.. (I think they mixed up the new and the old "first boot setup"?)
The Apps and widgets in the drawer were kinda confused, took 2 reboots for them to settle... (Icons disappeared and reappeared.. The widget tab in the drawer threw some widgets in and out, and the previews were mixed up, so dots and a weird sign was the result (as a preview of the widget)...
The initial setup was pretty laggy, but after setting stuff up, until now, yes I can say the performance of the nexus 7 is improved..
First I was like "OH HELL NO" but after the setup and the reboot everything was smooth...
Oh, and the back button was destroyed 1 time, blinked up but didn't go back... I pressed the home button and it worked then.
Edit: And sadly, no new wallpapers in stock... ):
Sent from my Nexus 7 using xda premium
I booted it up, restored my Google Play stuff (flashed a factory image, completely wiped everything from it, so it's clean, I think).
It lagged a lot, so I rebooted it and it still isn't 4.2.2 smooth. Maybe it's just me, I'll see.
Is it just me, or does it feel like the only thing that changed for us is the number in settings menu besides Google Apps?
OpenGL ES as it was already said, doesn't appear to be here for us, not to mention the fact that Miracast had never actually worked on N7 until recently when someone had it ported over.
Has anyone managed to find the link for the OTA yet?
SO I flashed the stock 4.3 kernel on a 4.2.2 rom and discovered that the stock android 4.3 kernel breaks wifi and gps on 4.2.2...
Eregoth said:
Has anyone managed to find the link for the OTA yet?
Click to expand...
Click to collapse
I have literally hours working on that.
Flashed the stock image using fastboot, took like 2 minutes to do, flashed the chainfire root patch and rebooted and restored apps, so far everything is pretty smooth no disappearing apps or icons or buttons, the kernel seems to be quicker, opening websites was quite a bit quicker, one thing I noticed while trying out different browsers was ads opening up new tabs automatically, that's something that's never happened before.
ffaiz.m said:
no OpenGL ES 3.0 for us?
according to http://developer.android.com/:
"OpenGL ES 3.0 is an optional feature that depends on underlying graphics hardware. Support is already available on Nexus 7 (2013), Nexus 4, and Nexus 10 devices."
Click to expand...
Click to collapse
Tegra 3 does not support GLES3. Even Tegra 4 won't, because nvidia are still using their old gpu architecture.
What's the performance like? Better than 4.2 or 4.1?
Sent from my GT-I9300 using xda premium
December 17, 2014 OTA 5.1 arrive at my Google Nexus 5 running stock, no root.
You are a little lost. Is 5.0.1 not 5.1. Be carefull with your writing.
just downloaded and installed.... only to get ...
"error"
plus a picture of an android lying on its back
phone unresponsive
a few minutes later it rebooted, still in 5.0
Yep, 5.01 OTA came to me about 1 hr. ago and installed with no issues!
EDIT: Sorry, should have stated my N5 is completely stock.
Yep. Got my update about an hour ago also. No issues.
Sent from my Nexus 5 using Tapatalk
Where any of you guys rooted before you updated and did it stay rooted?
wilbur said:
just downloaded and installed.... only to get ...
"error"
plus a picture of an android lying on its back
phone unresponsive
a few minutes later it rebooted, still in 5.0
Click to expand...
Click to collapse
same here, and can't redownload the update
Xanathoscl said:
same here, and can't redownload the update
Click to expand...
Click to collapse
so are any of you all rooted. im rooted NOT running a custom rom. can i do the OTA with out any issues? let me know please
ron608 said:
so are any of you all rooted. im rooted NOT running a custom rom. can i do the OTA with out any issues? let me know please
Click to expand...
Click to collapse
in the last time and had OTA update rom and root stock, now at 5.0 root stock and the error I get
it should be noted that both had the bootloader unlocked
Xanathoscl said:
in the last time and had OTA update rom and root stock, now at 5.0 root stock and the error I get
it should be noted that both had the bootloader unlocked
Click to expand...
Click to collapse
my nexus is unlocked and rooted. but im running the stock rom. i rooted my phone just to tether my wifi. so i havent really changed anything. so i need to know if i DO the ota update, will it do something to my phone. i didnt quite understand what you meant in what you said.
was saying that the last time I did not have a problem KK to L, now to update 5.0.1 if you gave me error, taking the stock and root
Xanathoscl said:
same here, and can't redownload the update
Click to expand...
Click to collapse
after about 10 minutes, the "update available" option returns
rebooted again, same outcome - "error"
i don't have much space on the device (500mb) so i'm going to free up some space and try again...
I'm pretty sure you need to revert to stock, unrooted and locked for the ota to work without issues...
Sent from my Nexus 5 using Tapatalk
CPNowell said:
I'm pretty sure you need to revert to stock, unrooted and locked for the ota to work without issues...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I've never rooted my Nexus 5 (embarrassed to say)... first device that I didn't feel the need to
I've now got tons of spare space... 3rd attempt... downloads, starts to update, wait 20 seconds, then a nice picture of an Android on its back and an "Error!"...
You could try wiping your cache partition before trying again?
Sent from my Nexus 5 using Tapatalk
---------- Post added at 11:01 PM ---------- Previous post was at 10:51 PM ----------
(btw, I'm completely stock and unrooted also...)
Sent from my Nexus 5 using Tapatalk
---------- Post added at 11:19 PM ---------- Previous post was at 11:01 PM ----------
wilbur said:
I've never rooted my Nexus 5 (embarrassed to say)... first device that I didn't feel the need to
Click to expand...
Click to collapse
Don't be embarrassed! Like you, I never felt the need to with my Nexus 5... my previous HTC Desire and HTC Desire S however were another story... I just hate HTC Sense with a passion after using the Nexus!
Tried 2 sideload OTA (adb reboot bootloader, then (when my Nexus 5 is in recovery mode and after tellin him "apply update from ADB") adb sideload 785a2f7af3718dba7e569decde8b6c4dc476a309.signed-hammerhead-LRX22C-from-LRX21O.785a2f7a.zip) , Error !
Unroot usin supersu unroot, Error !
Google sent me OTA by air (3 times), Error !
In order 2 wash without data loss, I tried Skipsoft Android Toolkit washin, then I put out android Avast (then sideload again), Error !
I wiped cache...
Then Google sent me OTA (4th), Error !
Do U know some right way (except factory reset) ?
Got mine a few hours ago and installed without issue. its tough to say if it fixed anything since I wasn't having any real issues outside of Chromes performance being terrible and the occasional screen redraw. Seems faster but that might be placebo or just that my caches were cleared with the update.
Worse is I kwow where is the bug : reading /cache/recovery/last_log.x tells that :
.../...
Verifying current system...
failed to stat "/system/bin/install-recovery.sh" : No such file or directory
etc...
(Somebody stole file before...)
As far as I know you must not have custom kernel, custom recovery or be rooted for the OTA to be applied correctly
Got mine this afternoon, in BC Canada only 13.3 mb downloaded and installed with no issues, stock, no root, unlocked boot loader. I always wait a bit after a major update before doing anything to my phone since you know the bug fix is always coming shortly after.
Sent from my Nexus 5 using XDA Free mobile app
I have a note 3 with at&t that's never been rooted but I would like to. Can sometimes point me in the right direction to get started?
Sent from my SAMSUNG-SM-N900A using XDA-Developers mobile app
Anyone can point us to the right direction for rooting?
Sent from my Nexus 10 using Tapatalk
zubero said:
Anyone can point us to the right direction for rooting?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
+1 for OC2, I mean all, I, am, seeing is Downgrade options to 4.4 KitKat then towel root then Safestrap then flash slotted Updated Lollipop Rom? All, I want is to remove bloat and use exposed, is there a root for OC2? Without downgrading thanks
Here's the video for downgrading and rooting. Then after that you can use any of the builds available. I'm using Alliance v12. Works like a charm,I almost gave up on my phone and was about to buy a new one. After downgrading to NC2,rooted and the pushing in Alliance 12 it's back. Thank you community.
https://youtu.be/QL6V7Y8vNms
Sent from my Nexus 10 using Tapatalk
zubero said:
Here's the video for downgrading and rooting. Then after that you can use any of the builds available. I'm using Alliance v12. Works like a charm,I almost gave up on my phone and was about to buy a new one. After downgrading to NC2,rooted and the pushing in Alliance 12 it's back. Thank you community.
https://youtu.be/QL6V7Y8vNms
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
So you downgraded to NC2 which I'm assuming is 4.4.2 becuase Im on NJ5, downgraded to NC2 or Jellybean I think and rooted with towel root and installed safestrap via the instructions, but when I try to reboot into Safestrap after installing and it installs, I grant it Superuser, and click Reboot to Recovery and nothing happens, any ideas? Becuase I need Safestrap, so I can flash Alliance, or Backup or anything else, but there are SO MANY conflicting OP's, regaurding Safestrap "it abandoned", "it only works on 4.2.2", "there's a work around for Safestrap on 4.4.4, by flashing Kitcat Kernal" "or Safestrap will work on on OC1 also with correct kernel"
All I want is to be on the "LATEST FIRMWARE FOR THIS PHONE, THAT WILL ALLOW ME TO EFFECTIVELY USE SAFESTRAP, TO BACK UP, FLASH, AND RUN ALLIANCE ETC..."
IF that means being someone a beer, I'm cool with that, been around here for awhile and had many Samsung phone Notes One, Two, S3, S4, but never had to deal with this bootloader crap, just so frustrated at this point[emoji726]
Sent from my SAMSUNG-SM-N900A
Did you install busybox before installing safestrap?
Sent from my DROID Turbo using XDA-Developers mobile app
Yeah I'm pretty sure I did I mean I have Busy box installed of course, and Safestrap, and I'm not sure in what order, however if Busy box was causing the issue, then Safestrap would not install at all, right? But yes now that I remember, when I got this phone it was already updated to OC1 (at that time the latest build) after try to sift through all the different out dated tutorials, I finally just did what I mentioned above, but Safestrap "Installs fine", "Allows me to grant SU", then "allows me to (click)" reboot to recovery" then FAIL.... nothing happens, on NJ5, I know Safestrap ended development at some point, and don't you also have to flash a certain kernel in order for SS to work on KK? So Confused
Sent from my SAMSUNG-SM-N900A
You need to install Busybox, then open busybox and tell it to install it into the system
Then open safestrap and do likewise.
I did this on nc2 no idea how it'll work on an older version.
Sent from my DROID Turbo using XDA-Developers mobile app
mrkhigh said:
You need to install Busybox, then open busybox and tell it to install it into the system
Then open safestrap and do likewise.
I did this on nc2 no idea how it'll work on an older version.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
so mrkhigh, thank you by the way first! off, to your response, so as far as you know "Safestrap" did not require any additional steps, to work on 4.3, like an updated kernel, which I know makes no sense to me eithier, other than the permission changes that occured at the true root level on NJ5 Update, and SafeStrap itself not being a true recovery, in the word of true TWRP, per this pain in my @$$ bootloader, which I have already made knowen in this community, AND others, is simply a loophole, to the "right to modify" ruling by the FTC some years back, if you will to the carriers, at&fee included among others
Sent from my SAMSUNG-SM-N900A
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.