Related
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
diamondx911 said:
Please help, my nexus was unlocked rooted with trinity kernel. When i pushed update, my tablet restarted with clockwokmod and failed to update
to 4.2. i believed it was because of custom kernel so i then flashed to stock factory, and re locked using nexus toolkit.
When i go to setting for update, it's showing me that my system is up to date 4.1.2. I don't understand. I thought flashing it back to stock factory will solve the problem.
Thanks a lot in advance for you hep
Click to expand...
Click to collapse
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
phonic said:
1) If you are using a custom kernel and/or custom recovery and/or removed/froze required system apks and/or modified build.prop and/or have a dozen other "custom" things, then the OTA update will NOT work. Period. You need to revert ALL of that. Stock kernel, recovery, system apks, build.prop, etc. Because if any of those aren't stock, the install will abort.
2) Having root is irrelevant. The update will remove suid access on the binary, so you will need to "re-root", but the binaries presence is irrelevant.
3) If it failed the OTA update, it won't download it again right away. Your best bet is to download the file and try to flash manually in a custom recovery (which will work as long as everything else is stock).
4) Did you say you relocked the tablet? If so, why? That was NOT required, and you just f*cked yourself, because you won't be able to flash a custom recovery back without unlocking the bootloader again, which will wipe your sdcard. There is NO reason to relock unless you are returning the device.
5) Again, this is why I hate toolkits. Learn to do things manually and you will be much better off.
At this point, assuming you relocked the bootloader, you will probably need to do a full factory reset and unlock it again. Then flash custom recovery and then flash the update. Or, since it would have been reset at that point, just download the full image from Google and flash that, then flash custom recovery.
Click to expand...
Click to collapse
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
diamondx911 said:
Haha, thanks for answering... the update came back by itself.
I was not aware of anything when i unlocked and rooted my nexus. please bare with me. I'm new to the android scene. but i'm very familiar with the hacking tool, i hacked and unlocked everything i own in my house, from 3 iphones, to my psp , xbox, ps3 and psp. when i first got my hand on the nexus i saw some dead black line of pixel that was appearing for half a second, after i read that a custom kernel can fix it,
I just did it fast and was not in a mood to start learning that sh*t from scratch. so now i'm on 4.2 , i know i lost everything. i will just have to unlock again and and root it....
Click to expand...
Click to collapse
Understood, and "hacking" android, especially Google devices, is pretty easy once you know what you are doing. The reason I dislike toolkits is that it prevents people from understanding the process, which really is fairly easy to understand, and can complicate troubleshooting steps.
The bootloader can easily be unlocked and locked. It takes one command and it's done. In order to flash anything with fastboot, you need it to be unlocked. The problem is, when you do this, it factory resets the device. So if you inadvertantly relock it, your going to need to reset it to unlock it again.
Even without the toolkit, going from unopened stock Nexus7 to fully rooted, updated and custom firmware Nexus7 only takes maybe 10 minutes, and 9 minutes of that is waiting for it to finish doing the various steps (flashing, rebooting, etc.). The most time consuming part is, unless you have good backups, restoring all your apps and settings. Titanium Backup is the best tool (IMHO) for that.
But yeah, in this case, you're going to need to unlock/wipe again. However, you CAN backup your "sdcard" to your computer and push the files back to it after the wipe. That can be very time consuming depending on how much you have.
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Thank you sir!
obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6
crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.
crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.
crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.
Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.
Forgive me if this has been asked before. I did search, but I couldn't seem to find an answer to this.
I have a dev edition model. I really want to root, but have been holding off because there are bugs with the current build of Lollipop and I'm kind of hoping Moto will release a 5.02 update soon to kill the memory leak and other issues. That being said, I have really been itching for root.
If I did root, what would I have to do to this phone to update it to the new version? Would I have to completely return to stock and wipe? Or could I ADB sideload? Seems like I was reading that you can't update at all when you're rooted, even if you disable root.
Without any idea how much longer it'll be before the next update, I'm finding it harder and harder to hold off on root, but I don't want to go through hell to get it back to stock and update it.
Thanks for any help and sorry if this has already been asked.
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
diggitydogg said:
From what I understand, root is fine. It is installing a custom recovery that will stop you from getting the OTA. You can very easily undo root. As a matter if fact, you can pretty easily reinstall the stock recovery also.
Click to expand...
Click to collapse
Thanks for the reply.
Most of the time, that's true. I have updated a lot of phones by simply unrooting, applying the update, and rooting again, or using ADB sideload and then just rooting. But from what I have been reading about the Moto X 2014, you have to completely restore it back to stock before doing anything, even if you just use the temp boot method to root.
Is that wrong? I can't seem to find any info that confirms either way.
I've installed custom recovery, how can I reverse it and install the original recovery for update?
One advantage of root is you'll have Titanium Backup, so even if you do have to do a full wipe before applying the update, you could just update it and restore everything back quickly using TiBu. With lollipop, apparently the update file checks for the entire system checksum as a whole instead of each file so any slight modification to the system will mostly require pure stock and this is the same even with the nexus. So yeah, you most likely have to wipe your device before updating. I'd say, wait till Xposed for Lollipop is out, its almost there, once it comes out go ahead and root it, it'll at least be worth the hassle then
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Steve-x said:
If you're rooted with lollipop and want to take an OTA update you can flash stock recovery and the stock system image. At that point you should still have all apps/data and be able to take a OTA update. The recovery and system files should be the exact version you already have and of course anytime you flash realize you could lose data!
Click to expand...
Click to collapse
Right. All you need to do is flash the stock /system partition and also the recovery if you replaced it. I don't know why everyone's talking about having to wipe the entire phone with the all the stock images.
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
ice_cold17 said:
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
Click to expand...
Click to collapse
If you're unlocked, rooted and have TWRP, why not just install custom ROM? Otherwise you can download factory image that you want, unzip and flash images individually via fastboot. Just don't flash user data and you won't loose data.
Just use the toolkit to 100% flash back go stock. It will unroot and reinstall stock recovery. Just remember to always keep USB debugging on and keep that boot loader unlocked. Once your back to the out box state you should be v able to receive ota. Or just use toolkit to flash the new stock image for your device. Ends with I.
Sent from my Nexus 6
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
ice_cold17 said:
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
ice_cold17 said:
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
Click to expand...
Click to collapse
I don`t erase and flash userdata usualy, its good to erase cache and then flash cache cache.img. A data factory reset after the procedure is adviced however for preventing fc`s and such.
So in the end is should wipe anyway? Oh well I was trying to avoid that only as a last resort. It wouldn't even let me unroot through the toolkit for some reason...
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
fubofo said:
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
Click to expand...
Click to collapse
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Evolution_Freak said:
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Click to expand...
Click to collapse
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
fubofo said:
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
Click to expand...
Click to collapse
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Evolution_Freak said:
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Click to expand...
Click to collapse
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
rootSU said:
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
Click to expand...
Click to collapse
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
OK, let me ask this, what is your current software? 5.0 or 5.0.1?
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
rootSU said:
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
Click to expand...
Click to collapse
Thank you sir for helping!
Evolution_Freak said:
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
Click to expand...
Click to collapse
Thanks @Evolution_Freak I'll give a shot at flashing just the stock recovery, unrooting and trying the OTA
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.