Hi,
apologies if this has been asked before. I have received messages to update to marshmallow OTA, but my phone has an unlocked bootloader and is rooted. From what I understand the bootloader is not a problem, but the rooted phone is. I have also seen references to TCRW recovery, but I'm not sure if I have that (I forget now how I rooted the phone...)
So what steps should I take in order to update? Is it easier to just download and flash the MM firmware directly, or should I unroot the phone and then do it OTA? Easy instructions for either approach would be much appreciated!
Thanks.
eelgc said:
Hi,
apologies if this has been asked before. I have received messages to update to marshmallow OTA, but my phone has an unlocked bootloader and is rooted. From what I understand the bootloader is not a problem, but the rooted phone is. I have also seen references to TCRW recovery, but I'm not sure if I have that (I forget now how I rooted the phone...)
So what steps should I take in order to update? Is it easier to just download and flash the MM firmware directly, or should I unroot the phone and then do it OTA? Easy instructions for either approach would be much appreciated!
Thanks.
Click to expand...
Click to collapse
You need stock recovery and an unrooted phone to apply the update. You can flash stock MM firmware and then get the OTA. WAIT FOR SOMETIME.
Hi, thanks for the reply. Is there any way of unrooting without relocking the bootloader? It would make it easier to reroot once I upgrade to MM I imagine, but all the instructions I can find online do both - any links to a reliable set of instructions would also be appreciated!
eelgc said:
Hi, thanks for the reply. Is there any way of unrooting without relocking the bootloader? It would make it easier to reroot once I upgrade to MM I imagine, but all the instructions I can find online do both - any links to a reliable set of instructions would also be appreciated!
Click to expand...
Click to collapse
You do not, actually can not, relock the bootloader. You just need stock recovery, meaning no TWRP, and remove root and any significant changes made to the system with root.
There are no real instructions needed and it kind in some ways depends what you have done with root... if you have done heavy modifications to /system then you might as well just reflash the factory image. If you have done only a handful things, you MIGHT be able to take the OTA if you undo them, such as remove Xposed and it's modules, use the SuperSU app to do a full unroot (it's an option in the menu, just look for it), and you have to find the stock recovery for you device and flash it with fastboot.
There is no step-by-step tutorial because every situation is different, everyone does different things to their phone... If you are unsure you can do it, perhaps just flashing the factory image will do what you need? It will wipe everything, but nothing you can do will lock/relock your bootloader.
Thanks for the explanation, that makes sense. Some of the links I found implied that you could relock the bootloader (with 'fastboot oem lock begin'), but in any case, I think that step can be skipped anyway, and everything else seems straightforward.
I actually haven't done anything with root except install adaway (from what I remember! nothing fancy in any case), and am still on stock firmware, so will just do as you suggest and unroot with supersu and flash the stock firmware..
Cheers!
acejavelin said:
You do not, actually can not, relock the bootloader. You just need stock recovery, meaning no TWRP, and remove root and any significant changes made to the system with root.
There are no real instructions needed and it kind in some ways depends what you have done with root... if you have done heavy modifications to /system then you might as well just reflash the factory image. If you have done only a handful things, you MIGHT be able to take the OTA if you undo them, such as remove Xposed and it's modules, use the SuperSU app to do a full unroot (it's an option in the menu, just look for it), and you have to find the stock recovery for you device and flash it with fastboot.
There is no step-by-step tutorial because every situation is different, everyone does different things to their phone... If you are unsure you can do it, perhaps just flashing the factory image will do what you need? It will wipe everything, but nothing you can do will lock/relock your bootloader.
Click to expand...
Click to collapse
eelgc said:
Thanks for the explanation, that makes sense. Some of the links I found implied that you could relock the bootloader (with 'fastboot oem lock begin'), but in any case, I think that step can be skipped anyway, and everything else seems straightforward.
I actually haven't done anything with root except install adaway (from what I remember! nothing fancy in any case), and am still on stock firmware, so will just do as you suggest and unroot with supersu and flash the stock firmware..
Cheers!
Click to expand...
Click to collapse
Relocking the bootloader was possible with some older Moto G models, but I believe everyone with the 3rd Gen that has tried it has failed. Make sure any tutorials or guides you use are for the Moto G 3rd Generation or 2015 model, although previous models are similar there are definite differences.
I just ordered Moto G Turbo (which is probably the same as the normal Moto G 2015 phone.)
Quick question: I would like to keep it as stock, since it is for my parents' use. If I update it to the latest OTA (6.x), will I lose ability to unlock the BL?
Coming from the Droid's background, unlocking the BL is a complicated affair. But I hear things are simpler with the 'normal' Motos.
Related
Long story short, I rooted my phone a long time ago (with the intention of installing a root-access wifi app). Foxfi started to work, so I never went any further than unlocking the bootloader, installing root, and installing superuser.
Since then, I got the OTA update to 4.1. I tried to uninstall the superuser app, but I'm not able to uninstall it. At this point, I would like to simply uninstall super user and maybe re-lock the bootloader.
I've looked around online and found some instructions, but they are generally for ICS or gingerbread. So my first question is if that matters. Secondly, all the instructions refer to flashing a stock ROM, and wiping data. I already have the stock ROM, so I don't know if I just skip certain steps in the process, or what.
My questions are probably pretty basic, I just want to make sure I don't brick anything, or totally reset my phone (if it isn't necessary).
Thanks!
dorklord said:
Long story short, I rooted my phone a long time ago (with the intention of installing a root-access wifi app). Foxfi started to work, so I never went any further than unlocking the bootloader, installing root, and installing superuser.
Since then, I got the OTA update to 4.1. I tried to uninstall the superuser app, but I'm not able to uninstall it. At this point, I would like to simply uninstall super user and maybe re-lock the bootloader.
I've looked around online and found some instructions, but they are generally for ICS or gingerbread. So my first question is if that matters. Secondly, all the instructions refer to flashing a stock ROM, and wiping data. I already have the stock ROM, so I don't know if I just skip certain steps in the process, or what.
My questions are probably pretty basic, I just want to make sure I don't brick anything, or totally reset my phone (if it isn't necessary).
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1572307
You are stock rooted so flash factory and this will clear your phone to pure stock. To relock bootloader at the end just fastboot oem lock. Your phone will be like it is out of the box. If you choose to unlock again remember that does wipe your SD. There really is no need to lock bootloader unless shipping for warranty reasons.
jayjay3333 said:
http://forum.xda-developers.com/showthread.php?t=1572307
You are stock rooted so flash factory and this will clear your phone to pure stock. To relock bootloader at the end just fastboot oem lock. Your phone will be like it is out of the box. If you choose to unlock again remember that does wipe your SD. There really is no need to lock bootloader unless shipping for warranty reasons.
Click to expand...
Click to collapse
I'm still a little confused, do I need to download a ROM from that thread? I've never installed a different ROM, so don't I already have a factory ROM?
Also, as a note, I've got a Nexus S 4G from sprint.
Try this. http://forum.xda-developers.com/showthread.php?p=15628028
Sent from my Nexus S 4G using xda app-developers app
dorklord said:
I'm still a little confused, do I need to download a ROM from that thread? I've never installed a different ROM, so don't I already have a factory ROM?
Also, as a note, I've got a Nexus S 4G from sprint.
Click to expand...
Click to collapse
You said you "would like to simply uninstall super user and maybe re-lock the bootloader." You have factory but rooted (superuser)
So flash factory which will remove SU and make it as if "out-of-box"
This may make help you more.
http://forum.xda-developers.com/showthread.php?t=1785672
Go here https://developers.google.com/android/nexus/images
- get the Factory Images "sojus" for Nexus S 4G (d720) -- >Android 4.1.1 (JRO03R)
Follow the instructions to a T and all will be fine. Need Android SDK working for your phone for fastboot http://developer.android.com/sdk/index.html
Google guides to set it up if you don't have it already. You should if your rooted, but it sounds like you don't flash so maybe not.
Old sticky here http://forum.xda-developers.com/showthread.php?t=895545 to help get SDK in part 1. Part 2 to lock fastboot oem lock
Give it a go. Ask for help and I or others will help you out.
Cheers
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
tuffluck said:
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
Click to expand...
Click to collapse
As long as you're familiar with adb/fastboot run the following:
Code:
[U]From Bootloader[/U]
fastboot oem unlock
fastboot flash recovery [URL="https://dl.twrp.me/hammerhead/twrp-2.8.6.1-hammerhead.img"]twrp-2.8.6.1-hammerhead.img[/URL]
Boot into recovery....
[U]From Recovery[/U]
adb sideload [URL="https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1"]UPDATE-SuperSU-v2.46.zip[/URL]
tuffluck said:
I've read a lot of guides both on this forum and using google. Some are saying to wipe the phone completely and flash SuperSU through TWRP, some are saying there is a chainfire auto-root method. Why am I like the only one confused? I just received my Nexus 5 (I know I'm late in the game), and updated to 5.1. I would like to root, but don't really know what the best way is. Should I just wait on a new, easier way that is currently in the development process?
Also I am reading I'd have to go back to stock to get any new OTA updates, and I read that can be kind of a PITA. So do you think root is still worth it? Honestly I just want viper4android, Adaway, and Greenify. That's it.
Thanks for the help and sorry for probably a very redundant question.
Click to expand...
Click to collapse
Both are right. There is a manual way (flashing SuperSU through TWRP) and there is an "automated" way (the chainfire auto-root). Pick your poison.
The manual way will most likely wipe your device because the "unlock" step does that. I'm honestly not sure about the auto-root method, but I'm going to guess it probably also wipes.
As for OTA, yes, you need a stock recovery to get OTA, because.... well... the OTA uses the stock recovery to update. Most people are of the mind that if you're the type of person who flashes a custom recovery like TWRP, you're also the type of person who doesn't care about OTAs (the .zip is typically posted here within hours of the OTA going live anyway).
There are risks and drawbacks to any kind of hacking of your phone. Risks obviously include bricking, but the drawbacks usually include having to wipe and reinstall things once in a while, and also the lack of OTAs. Pick your poison.
fosser2 said:
As long as you're familiar with adb/fastboot run the following:
Code:
[U]From Bootloader[/U]
fastboot oem unlock
fastboot flash recovery [URL="https://dl.twrp.me/hammerhead/twrp-2.8.6.1-hammerhead.img"]twrp-2.8.6.1-hammerhead.img[/URL]
Boot into recovery....
[U]From Recovery[/U]
adb sideload [URL="https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1"]UPDATE-SuperSU-v2.46.zip[/URL]
Click to expand...
Click to collapse
Being a Nexus device this process is pretty straightforward and does not need all of the utilities to obtain root
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.
Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!
PhantomSoul said:
Hello,
I've been out of the rooting scene for a while now (last phone had a damn permalocked bootloader!) and wanted to be clear on a few things before rooting this phone.
1. I am aware that doing any sorts of modifications to the system will disable OTA updates and those have to be done manually, the question is when I restore my phone (removing root, going back to stock recovery, etc) will automatic OTA updates be re-enabled? Is the stock recovery image even available, or is this even possible? because...
2. When I am looking to sell the phone in the future, I want to be sure that the phone doesn't show any signs of tampering. I am wondering this because the last phone I rooted was the Motorola z2 force, which was the first phone I've ever seen with that "unlocked bootloader" warning when powering on. And with that phone even after all the images were returned to stock, there was still a "your device has loaded a different os" warning, even if it was the stock image. The CTS system functioned similarly to Samsung's knoxs system, where once it was tripped, there was no going back and I wasn't aware of this...
TL;DR: If I ever wish to sell the phone to completely stock (relocked bootloader, stock recovery img, etc), will the phone be permanently tainted with a message like with the image attached? thanks!
Click to expand...
Click to collapse
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk
In your image it's because it's a Motorola, not a good manufacturer with bootloader (but not the worst).
There is 3 big ways with bootloader:
#1 (the best) : The unlock method is 100% in the "code" and you can unlock and relock it yourself (Google with Nexus and Pixel)
#2 (good but not the best) : The unlock method is in the code BUT the manufacturer has a part of the method (an unique code) and you can't do it without register your IMEI on the website, so the manufacturer know it, you lose the warranty... (Motorola, Sony).
#3 (the worst) : You just can't because the manufacturer doesn't want. (Nokia)
jmtjr278 said:
If you flash stock image and relock bootloader no one will ever know.
As far as otas while rooted, this device will allow you to accept, it will just overwrite root.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
Yes, sir. I'm not sure what method you used other than flashing the rooted boot.img but if am update comes out either patch the new kernel or wait for pbanj to post the modified img. That's it. Easy peasy
Sent from my Pixel 3a using Tapatalk
alliance1975 said:
@jmtjr278
Thank you for your informative post. I just got my 3a and am very happy with it. I rooted via pbanj's recommended procedure and changed out some apps. Except for loading his patched image that allows Magisk I have made no changes to the basic pie room.
Your reply suggests I can install an ota, lose root, but I can reinstall root via panbj's procedure.
Click to expand...
Click to collapse
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.
googlephoneFKLenAsh said:
You can't install ota on rooted phone. It will fail in recovery.
The steps you need to do is as follows:
1. boot to bootloader, use fast boot to flash stock boot.img
2. go to recovery, apply ota.zip using adb sideload
3. boot back to bootloader, flash the patched boot.img with root
4. reboot and enjoy with root and all your apps/data intact.
Click to expand...
Click to collapse
Wow a slightly different procedure. So it would appear I need the stock boot image when I want to do an OTA. Thanks.
There have been lots of issues with Google pay and securehub (if you work at a big company and want company email on your phone) and unlocked bootloader. Yes, magisk does eventually find workarounds, just depends on how much time you want to spend screwing around knowing it'll break relatively often. Also, we don't have many developers on board yet, so as far as custom roms and kernels go, it's slim pickings.
All that being said, rooted stock is great as long as you don't mind resetting everything to unlock the bootloader.
As you have noted, if you unlock the bootloader you will get the warning when booting. However, unlike your previous phone, you can reflash to stock and relock your bootloader very easily.
Obtaining root and then accepting OTA updates is also much easier with the Pixel phones (and really any phone that is now using A/B partitions). Here is a to some magisk tutorials that show you how easy it is to take an OTA update. https://topjohnwu.github.io/Magisk/tutorials.html
Also as noted previously, it can be tricky to get Google Pay set up with a rooted device. It is possible, but it takes some effort. Personally I don't use Google Pay, so it's no loss to me and I haven't bothered trying to get it to work. Otherwise root is very important to me. I use several mods/apps that are very important to me. Viper4Android, Advanced Charging Control, Ad blocking, Youtube Vanced, and Active Edge Mod (a unique mod for Pixel devices with the active edge gesture) as well as root explorer, tasker (and related apps like secure settings) and titanium backup.
To me, having access to those mods and apps are well worth seeing the warning message and having to manually accept a OTA update and having an extra step or two in the update process.
Could someone help me? I'm currently rooted on OOS, with TWRP and a custom kernel installed. I'd like to unroot and go back to fully stock (in light of the recent development of SafetyNet and CTS; see TopJohnWu's tweets, cause I am by no means an expert, but he makes it clear this is the end of rooting permanently now). I need help on how to do it without bricking my device, and also a method of transferring as much of my current data as possible (obviously Titanium/Swift Backup is out of the question cause I won't have root access). Thank you very much in advance!
pratzyushd said:
Could someone help me? I'm currently rooted on OOS, with TWRP and a custom kernel installed. I'd like to unroot and go back to fully stock (in light of the recent development of SafetyNet and CTS; see TopJohnWu's tweets, cause I am by no means an expert, but he makes it clear this is the end of rooting permanently now). I need help on how to do it without bricking my device, and also a method of transferring as much of my current data as possible (obviously Titanium/Swift Backup is out of the question cause I won't have root access). Thank you very much in advance!
Click to expand...
Click to collapse
I think you con relock the bootloader/unroot with the msm tool. Dont hold me to that I may be wrong
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
This would be a good place to start.
I have done this many times, firstly, install the lastest version using the full package from OP page, this will get rid of the TWRP for you, then restart in fastboot, in fastboot, run "fastboot oem lock" (or would be relock?), confirm in your mobile, reboot, reinstall the last full package and be happy.
Something like it, I don´t remember exactly, but this is the idea.
Tks and good luck!