Related
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Rey0 said:
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Click to expand...
Click to collapse
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
jagreci said:
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
Click to expand...
Click to collapse
Sounds cool then. Thanks
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
crucialcolin said:
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
Click to expand...
Click to collapse
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
beekay201 said:
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
Click to expand...
Click to collapse
I've actually been spoiled by nandroid on the HP TouchPad with CM. Really nice to have a complete backup image. Wish I would have thought about unlocking and rooting before I got a bunch of stuff on my Nexus setup the way I like it. Sort of stuck since you have to unlock the boot loader for a custom recovery. Thus is life though.
I haven't tried it yet but it looks like Adb can do it on a stock device.
ex: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
I'm actually extremely torn on the OTA thing. I find it just so damn convenient with the admission I've gotten lazy of late Otherwise I have a tendency to never update.
I just recently received my oneplus one a week ago,if they're any new oneplus one owners out there.. Did you already or are thinking about unlocking bootloader,root and flashing a ROM? I'm eager to do it but would like to wait for an official ota lollipop update. I've read that it might be next month? Hopefully that's true..or am I waiting on nothing and should just custom mod it already.
If you want to wait for official update, then wait for a couple of weeks.
if we dont have official update by then, you can unlock bootloader, root and flash nightlies or custom ROMs
msri3here said:
If you want to wait for official update, then wait for a couple of weeks.
if we dont have official update by then, you can unlock bootloader, root and flash nightlies or custom ROMs
Click to expand...
Click to collapse
Thanks I'm probably gonna wait if we do get anything in the next few weeks. Hope we do
Unlock your bootloader now. It must be done when you first get the phone because it wipes the entire device. If you wait you'll lose all your apps and settings. You don't need to do anything else like install a recovery or flash a ROM yet but you really should unlock the bootloader straight away.
Transmitted via Bacon
I got my device during the January 20 sale. Already flashed CM12 temasek build and AK kernel!
I got my OnePlus 4 days ago, that's the all beauty its already smooth and fast with Cyanogen and everything you put as a costume rom now will arrive later to your device, so unless your unsatisfied with your current device situation, keep it that way. and i was a flashaholic on my last 2 devices [ galaxy nexus, transformer prime] , on my nexus i flashed a different rom/nightly every 4-7 days
vitalero said:
...so unless your unsatisfied with your current device situation, keep it that way...
Click to expand...
Click to collapse
Bad advice, if he ever wants to flash a custom ROM or have root he must unlock the bootloader straight away.
Transmitted via Bacon
Like Timmaaa said Unlock it now before you have a full list of contacts and all your apps installed, since the Unlock will wipe your phone totally, there is no going around it. After that Yes wait for the Official CM update, don't be like the dozens or more users that flash everything they can see with a CM12 attached to it , and come crying after that they bricked their phone....
Follow Timmaaa's guides ( in his signature ) and all will be good.
Contacts are being synced to your Google account or sim. Videos and pictures can sync directly to a cloud [ google drive,dropbox] , apps also can be saved in that backup app fforgot her name, or just write them down on a paper or go to Google Play and add all your wanted apps to Watch List, then after a reset you can just press Install on your PC and it will automaticly give you a fresh installation of all the Aps on your mobile. the only reason im saying all this is because its already Cyanogen based.[more of an AOKP fan but tested their bacon version on another phone and didnt like it that much]
I am on day 3 of my OPO and loving it. Huge upgrade from my N4.
I have unlocked bootloader, installed a custom recovery, and rooted.
My main question is...does this ruin my chance of receiving OTA updates? Or will I get system updates and the ultimate lollipop upgrade with stock rom (just rooted and custom recovery). Do I need to go back to stock recovery?
I want to make sure I have the latest setup...and have played with the idea of updating to CM12 nightlies...but I am just hoping OPO will make the jump shortly.
worst case you will flash in your costume recovery the stock image of the official CM lollipop
vitalero said:
Contacts are being synced to your Google account or sim. Videos and pictures can sync directly to a cloud [ google drive,dropbox] , apps also can be saved in that backup app fforgot her name, or just write them down on a paper or go to Google Play and add all your wanted apps to Watch List, then after a reset you can just press Install on your PC and it will automaticly give you a fresh installation of all the Aps on your mobile. the only reason im saying all this is because its already Cyanogen based.[more of an AOKP fan but tested their bacon version on another phone and didnt like it that much]
Click to expand...
Click to collapse
vitalero said:
worst case you will flash in your costume recovery the stock image of the official CM lollipop
Click to expand...
Click to collapse
You're missing the point, which is that it's better to unlock the bootloader when you first get the device, because it saves you from having to do all that. Especially when it comes to apps and games that have saved data which will be completely lost.
you are correct timmaaa, dont hate me, but this is just my opinion, for me a fresh rom or huge update is a fresh start, so other than installing apps all over, i can just pick the apps i really used , with this process i droped from over 75 apps to 10 after reducing few every single flash, sometimes when you get something NEW you dont want your old garbage there.
and my other sentence that you quoted was for the other guy that asked something abit diffrent
vitalero said:
you are correct timmaaa, dont hate me, but this is just my opinion, for me a fresh rom or huge update is a fresh start, so other than installing apps all over, i can just pick the apps i really used , with this process i droped from over 75 apps to 10 after reducing few every single flash, sometimes when you get something NEW you dont want your old garbage there.
and my other sentence that you quoted was for the other guy that asked something abit diffrent
Click to expand...
Click to collapse
I understand what you're saying, and there's definitely no hate here, but I don't think you're seeing my point still. Forget about ROMs or updates for the moment, all I'm talking about is the fact that unlocking the bootloader is best done when the device is first received. Anything else can happen at a later stage because they have no major effect, but the bootloader is a different story.
Transmitted via Bacon
y0bailey said:
I am on day 3 of my OPO and loving it. Huge upgrade from my N4.
I have unlocked bootloader, installed a custom recovery, and rooted.
My main question is...does this ruin my chance of receiving OTA updates? Or will I get system updates and the ultimate lollipop upgrade with stock rom (just rooted and custom recovery). Do I need to go back to stock recovery?
I want to make sure I have the latest setup...and have played with the idea of updating to CM12 nightlies...but I am just hoping OPO will make the jump shortly.
Click to expand...
Click to collapse
No you will get OTA if you don't touch systems files
IMHO, playing with Nightlies is asking for trouble, it's all good if you are a Dev or a someone that really knows his/her way around Android, but not for a novice... Look around the forum , 99% of the threads about bricked , non-responding, dead phones, come from people trying out Nightlies and having no clue what they are and what they are doing. Not saying it's your case here. This is just my opinion.
Cholerabob said:
Look around the forum , 99% of the threads about bricked , non-responding, dead phones, come from people trying out Nightlies and having no clue what they are and what they are doing. Not saying it's your case here. This is just my opinion.
Click to expand...
Click to collapse
I agree with this statement. Phones are not very easy to brick if you actually know what you're doing. It's amazing how many "I did something, I have no idea what I did, but it bricked my phone" posts there are in this device section.
timmaaa said:
Unlock your bootloader now. It must be done when you first get the phone because it wipes the entire device. If you wait you'll lose all your apps and settings. You don't need to do anything else like install a recovery or flash a ROM yet but you really should unlock the bootloader straight away.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, but i do not understand it.
Today i have got my new OnePluse One. I want to wait a little bit and use the original ROM CM11s for ca. a few days/weeks. What should I do now? Install my favorite Apps and use the Phone with CM11s and unlock the bootloader in a few days/weeks when i will flash a custom-rom?`
Or should I unlock the bootloader now and install then my favorite Apps and use the orignal CM11s?
I do not understand why you recommend to unlock the bootloader now? When i unlock the bootloader now and flash a new custom-rom in a few weeks then i also have to wipe data etc.(factory reset), isn't?
hallohallo222 said:
Sorry, but i do not understand it.
Today i have got my new OnePluse One. I want to wait a little bit and use the original ROM CM11s for ca. a few days/weeks. What should I do now? Install my favorite Apps and use the Phone with CM11s and unlock the bootloader in a few days/weeks when i will flash a custom-rom?`
Or should I unlock the bootloader now and install then my favorite Apps and use the orignal CM11s?
I do not understand why you recommend to unlock the bootloader now? When i unlock the bootloader now and flash a new custom-rom in a few weeks then i also have to wipe data etc.(factory reset), isn't?
Click to expand...
Click to collapse
Unlock your bootloader now. I've explained why pretty thoroughly this thread. It wipes the whole device, including your user data during the process. Yes you will have to wipe when you try a custom ROM in a few weeks, but if your bootloader is already unlocked you can backup your apps because you'll be able to root your stock ROM, plus you won't need to worry about copying all of your personal data to your PC and then copying it back again.
Transmitted via Bacon
Assuming that I install my apps now(Social Media, Music etc.) and do some data at my internal storage. And in few weeks I will flash a custom-rom. Before I flash it, I save my data(music, images etc.) in my PC and use "Appbak" for backupping my apps. My Google-Account stores my contacts etc.
Where is the problem now? Can I use Appback only with a rooted and unlocked device?
hallohallo222 said:
Assuming that I install my apps now(Social Media, Music etc.) and do some data at my internal storage. And in few weeks I will flash a custom-rom. Before I flash it, I save my data(music, images etc.) in my PC and use "Appbak" for backupping my apps. My Google-Account stores my contacts etc.
Where is the problem now? Can I use Appback only with a rooted and unlocked device?
Click to expand...
Click to collapse
Never heard of Appback so I can't answer that. In my experience though non-root backup apps are completely useless. Titanium and Backup+ are the only two that work well. I've given reasons why the bootloader should be unlocked (it saves a lot of hassle, plus if something goes wrong with your phone you're completely screwed with a locked bootloader), if those reasons aren't good enough then don't do it. Do whatever you want to do, clearly you know better so I'm not going to argue with you about this.
Transmitted via Bacon
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.
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
cmivxx said:
So I finally got a pixel after lurking around for a while and ended up with a Verizon version. Luckily the dePixel8 fix got the BootLoader unlocked as it wasn't updated yet. Now that I've got the bootloader unlocked, I haven't done anything with it yet. I used to root all of my android phones (Nexus 5, 6, 5x...) and do all kinds of cool things, but as of the 5X, everything I used to root to do is now baked into the Pixel, so I haven't touched anything on it. The one thing I would love to use is Android-Pay... DOH
So, I am verizon phone (on t-mobile), bone-stock OS with an unlocked bootloader and no Android Pay due to failing safety-net. The question is, if I re-lock the bootloader, will I ever be able to unlock it again? Like I want to try a ROM etc? Or is my best bet to get the Kernel that patches the Safety-Net process?
My original thought process drug me to the kernel patch, but since I really haven't had a need to mess with my pixel, the whole process seemed far more involved than the simple desire to use Android-Pay... Which led me to thinking about just re-locking the bootloader... So, please help!
TIA!
Click to expand...
Click to collapse
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
mac796 said:
I believe most of kernels have that safety net patch. Really painless to flash. You can just boot TWRP and flash kernel I believe
Click to expand...
Click to collapse
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
cmivxx said:
Ok, I'll bite... Is there a "preferred" kernel at this point? Digging through some of the threads on the different kernels is about a bunch of people having problems... I just want the safety-net patch, probably won't use the other features.
Click to expand...
Click to collapse
I usually just use the kernel that comes with the rom im on. And I use magisk. I have used ex kernel. I really like the ex manager app. And I do believe it still passes safety net with just unlocked bootloader. At least it used to. Google updated safety net this month so I don't know if that changes things.
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
cmivxx said:
Alright, I did it... TWRP RC2 + Elemental X sorted out my safety-net issues... Just concerned about legit updates to the phone. Guess I'll fgure that out when the time comes.
Thanks for the help!
Click to expand...
Click to collapse
You will probably be able to take the OTA with just a unlocked Bootloader, you will just have to boot TWRP and Flash that kernel every month. There also is a stock kernel someone builds for what you're trying to do
You can flash google's factory-image.
Then you can re-lock your bootloader and you can unlock it too.
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.