Firstly, i have not rooted yet. Wont get a chance to until i get home later. That VZW notice keeps popping up asking me to update.
So.... if i let it update are the current root methods still compatible after the update is applied?
rooted fine.. got mine home, ran the 4.0.2 then unlocked/rooted..
unlocked bootloader and rooted mine after the update, no problems.
Ah, so an OTA update will re-lock the bootloader?
Hefe88 said:
Ah, so an OTA update will re-lock the bootloader?
Click to expand...
Click to collapse
No, but you will loose root privileges - the su file and apk will still be there but the permissions on the files will have been changed and you won't have access to them.
If you used one click method to root you'll need to rerun it.
If you used a manual method you'll need to redo the chmod part.
(afaik the only way to relock the bootloader is for you to run
fastboot oem lock )
Related
My phone said a new update was available (Android 2.3.3), and after it installed and rebooted, a prompt comes up saying "Software Could Not Be Updated". Any idea what could be causing this? My phone is rooted if that makes any difference.
[email protected] said:
My phone said a new update was available (Android 2.3.3), and after it installed and rebooted, a prompt comes up saying "Software Could Not Be Updated". Any idea what could be causing this? My phone is rooted if that makes any difference.
Click to expand...
Click to collapse
Is your bootloader unlocked?
DId you remove any bloatware? Or anyting else? If so the update won't work, you need to replace teh displaced files. A couple of threads on this subject
batman_112 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Nah I didn't unlock the bootloader.
As Cholerabob said, did you remove any files after you rooted your phone? If that's the case, an OTA update will not work for you until and unless you either reflash or replace the files which you've removed.
If you've just frozen apps with Titanium Backup, you might want to undo that before trying to update.
Cheers! Hope this helps.
If u have rooted and remove some bloatwares, u will have to flash a default 2.3.2, root it, then do the OTA update to have a rooted 2.3.3
Sent from my LT15i
Hi All,
I have rooted Samsung Galaxy Nexus with Android 4.0.2 in it.
The phone come from Japan so I did a temporary unlock with ****docom v1.1.
These days I got notification to update to 4.0.4.
Is it safe to update? Will it lock my phone again?
Thank you,
dynamikus
It will not lock your bootloader, but it will remove root permissions. All you have to is root again by installing the SU apk.
Will it have signal back?
hurley1718 said:
It will not lock your bootloader, but it will remove root permissions. All you have to is root again by installing the SU apk.
Click to expand...
Click to collapse
I am new to the rooting stuff my phone was rooted before I got it.Any link how can I root my phone agin?
I know it can't be done right now but all I want is the stock rom with superuser installed. When the one-click comes out do you guys think it will have the option?
Sent from my Nexus 7 using Tapatalk 4 Beta
Why not just unlock? You can always lock it again if you want to return to factory.
^^ This, plus if you don't want to replace the recovery you can always use ADB to boot do a different recovery like TWRP to flash the SuperSU :good:
Will an unlocked bootloader still be able to accept OTA updates?
If not, will it accept OTA updates after relocking the bootloader?
Thanks.
Godswrath said:
Will an unlocked bootloader still be able to accept OTA updates?
Click to expand...
Click to collapse
Yes.
Unlocking your tablet doesn't really make changes to your system. It sets a flag that allows you to modify partitions which were previous read-only and also allows you to boot unsigned kernels/recoveries.
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
sfhub said:
Whether you can accept OTAs or not depends on whether you have modified or removed any OS files. Adding files (like you would to add root) will not affect your ability to get OTAs. However with root capabilities, you will sometimes be tempted to modify or remove OS files. That could prevent you from a successful OTA update.
Click to expand...
Click to collapse
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
sfhub said:
So I mentioned above that root wouldn't affect your ability to get OTAs.
I actually went through the process of flashing JWR66N, rooting, then applying the JSS15J OTA.
What I found is that SuperSU actually does cause the OTA to fail somewhere near the end when it is setting permissions. All the files are patched successfully but there is a failure when the OTA tries to unpack the new recovery. This is due to SuperSU install marking a file immutable to support its "survive" OTA feature. If you undo this attribute change on the one file, the OTA works fine.
If you do not undo the change, effectively you'll have all the files for the JSS15J ROM, except your build fingerprint will still say JWR66N.
Click to expand...
Click to collapse
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Godswrath said:
Great, thank you so much for the info sfhub! May I ask how you undo the attribute change on the file? I'll really want root, but for the moment I don't want to stick with OTAs, I spend enough time messing around with ROMs on my phone, (EG4T).
Click to expand...
Click to collapse
you just do
chattr -i /system/etc/install-recovery.sh
I attached an UPDATE-SuperSU-ota.zip install file you can run from TWRP to do it for you. You just run it after UPDATE-SuperSU-v1.51.zip and it will set you up to receive OTAs successfully (you'll need to re-install the two files after the OTA to put root back on)
So basically you do this
adb reboot bootloader
fastboot boot twrp.img
within TWRP
install UPDATE-SuperSU-v1.51.zip
install UPDATE-SuperSU-ota.zip
You can even "chain" install them, just select UPDATE-SuperSU-v1.51.zip first.
Aria807 said:
Why not just learn android some more? It's a nexus device. It's meant to be easily unlocked / rooted / returned to stock / relocked. If anything, there are tons of resources in this forum to help you return your device to stock if you mess things up so you can return the tablet or get warranty done.
Click to expand...
Click to collapse
IMO you can actually learn a lot trying to understand out why things fail
Hello all,
Long time lurker, though first time poster. I have a Verizon Pixel XL that I have unlocked the bootloader and rooted the phone on Android 7.0. I am now getting a system notification that I can update to Android 7.1. I'm unsure truly if I should proceed with it or not.
Don't want to lock my phone out as I am afraid of the repercussions.
Summary: Unlocked bootloader on Verizon Pixel XL with root trying to see if it is possible to update over system update to 7.1
Thank you in advance! ?
DreyX said:
Hello all,
Long time lurker, though first time poster. I have a Verizon Pixel XL that I have unlocked the bootloader and rooted the phone on Android 7.0. I am now getting a system notification that I can update to Android 7.1. I'm unsure truly if I should proceed with it or not.
Don't want to lock my phone out as I am afraid of the repercussions.
Summary: Unlocked bootloader on Verizon Pixel XL with root trying to see if it is possible to update over system update to 7.1
Thank you in advance! ?
Click to expand...
Click to collapse
It would fail if you try since you're rooted. You'll need to sideload the OTA via recovery, then root again via fastboot before first the boot.
krypto1300 said:
It would fail if you try since you're rooted. You'll need to sideload the OTA via recovery, then root again via fastboot before first the boot.
Click to expand...
Click to collapse
Thank you. Will give it a shot.
DreyX said:
Hello all,
Long time lurker, though first time poster. I have a Verizon Pixel XL that I have unlocked the bootloader and rooted the phone on Android 7.0. I am now getting a system notification that I can update to Android 7.1. I'm unsure truly if I should proceed with it or not.
Don't want to lock my phone out as I am afraid of the repercussions.
Summary: Unlocked bootloader on Verizon Pixel XL with root trying to see if it is possible to update over system update to 7.1
Thank you in advance!
Click to expand...
Click to collapse
Same situation as you,
Got a question for ya, I just unlocked bootloader also yet its still gray. Is yours?
I expected it to fail as I have UL bootloader and am rooted, I tried it anyway and it worked. I was surprised. I got updated to V firmware (I'm in the UK, EE network, previously had H firmware). Bootloader remained unlocked but lost root. I rerooted after update without issues. Hope this helps.
nbhadusia said:
I expected it to fail as I have UL bootloader and am rooted, I tried it anyway and it worked. I was surprised. I got updated to V firmware (I'm in the UK, EE network, previously had H firmware). Bootloader remained unlocked but lost root. I rerooted after update without issues. Hope this helps.
Click to expand...
Click to collapse
I want to install the update but don't want to lose root is there a guide somewhere on how to side load it with adb?
canemaxx said:
I want to install the update but don't want to lose root is there a guide somewhere on how to side load it with adb?
Click to expand...
Click to collapse
I'm pretty sure that can't be done. If you update, you'll lose root but it only takes two minutes to re root.
nbhadusia said:
I expected it to fail as I have UL bootloader and am rooted, I tried it anyway and it worked. I was surprised. I got updated to V firmware (I'm in the UK, EE network, previously had H firmware). Bootloader remained unlocked but lost root. I rerooted after update without issues. Hope this helps.
Click to expand...
Click to collapse
So you took the OTA or side loaded the OTA? If you took the OTA and it succeeded while being rooted, that would be great news.
nbhadusia said:
I'm pretty sure that can't be done. If you update, you'll lose root but it only takes two minutes to re root.
Click to expand...
Click to collapse
lyall29 said:
So you took the OTA or side loaded the OTA? If you took the OTA and it succeeded while being rooted, that would be great news.
Click to expand...
Click to collapse
Sideload the OTA then boot to bootloader and redo root before fully rebooting to android. Worked for me.
Sideloading OTA with custom kernel
Is the process for sideloading an OTA different if you have a custom kernel? I'd imagine simply sideloading it wouldn't work.
nbhadusia said:
I'm pretty sure that can't be done. If you update, you'll lose root but it only takes two minutes to re root.
Click to expand...
Click to collapse
Pretty much the same process to root it again after the update? Same root method?
Sent from my Pixel XL using Tapatalk
So should we anticipate having to sideload every OTA update from this point forward as well? Along with having to root the phone again? Or do we expect OTA updates to work on rooted Verizon phones with the bootloader unlocked in the future?
Forgive the ignorance but the last few phones have been developer edition or have had simpler root methods.
le0.br4zuc4 said:
Pretty much the same process to root it again after the update? Same root method?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup. Same method.
I'm having a hard time finding an answer to this. I am going to unlock my bootloader but wait until the beta is over to root. Can I still get OTA updates with an unlocked bootloader and no root? I've rooted all my Android devices in the past and some of them could receive updates when unlocked and some couldn't. This is my first Pixel.
sparkeymat said:
I'm having a hard time finding an answer to this. I am going to unlock my bootloader but wait until the beta is over to root. Can I still get OTA updates with an unlocked bootloader and no root? I've rooted all my Android devices in the past and some of them could receive updates when unlocked and some couldn't. This is my first Pixel.
Click to expand...
Click to collapse
What's the point of unlocking if you're not going to root or install a custom rom?
Why not go ahead and root? This guide is all you need:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
jsbeagle said:
What's the point of unlocking if you're not going to root or install a custom rom?
Why not go ahead and root? This guide is all you need:
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117
Click to expand...
Click to collapse
It turns out I was one of the lucky ones that got OEM unlock on a locked device with the beta. So, I was going to unlock invade the next update locked it back and just run out the beta. When it was over I was going to root. But I may as well do it now.
OTA is tricky with root but I have pulled it off the last few months. The key is to pull the update before it does so automatically. Google now checks for root on download and stops if you are rooted. It only does it once, if it finds root it won't check again until next month.
So the process is like this.
First Monday of the month in the morning hit Magisk Manager and unroot....restore images.
Do NOT reboot. You will remain rooted until you reboot and this is important.
Spam the check update button. Mid afternoon you will get the uodate. Let it install. But do NOT reboot.
After the update hit Magisk Manager again and install root....but select the option to install to the other slot. The update installed there...you want to root that slot.
Now you can reboot.
If you are not rooted, just unlocked it will update just like normal.
sparkeymat said:
Can I still get OTA updates with an unlocked bootloader and no roo?
Click to expand...
Click to collapse
Yes without root you can definitely get OTA updates with an unlocked bootloader.