Database Info

[Q] Sorry, I'm new...

OK...I've read the Wiki and the Glossary, I've searched the forums, I've been obsessively reading this forum for a week, and I still have some very basic questions that I'm hoping someone can either point me to a link or just drop some info for me. I know many of you have been at this since the Dawn of Android, but sometimes I feel like I'm walking into my first day of med-school when everyone else has been here for 5 years. Assume for a moment that I am a tabula rasa where the rest of you are now writing in the margins of a dense technical manual. Because that's what it feels like for me.
First, some background info: I want to learn how to do all this stuff, but this phone was expensive! I don't want to break it. So I'm cautious. I'm not a programmer but I'm not technically inept. I am good at following directions. I don't panic when things go wrong. So I think I can root, flash, and all the fun stuff that comes with having an Android device. But I have some questions that are still unanswered. I'll try to be as concise as possible (too late, I know):
1) I have the SPH-D720 model. I see rooting guides for the I9020 but not the SPH-D720. Will those other guides work for my device? I've seen other people ask this same question get sent to BuglessPete's guide so I'm assuming so, but I want to be sure.
2) I know that GRJ90 and 2.3.5 just came out. My phone is updated to both. It looks like most of the root guides are still referring to 2.3.4 or 2.3.3. Should I wait until someone releases an updated 2.3.5 guide, or is the method still the same?
3) Backups...these are different than saved settings, yes? So when I root my phone (which apparently requires unlocking the bootloader now) I'm going to lose all of my apps/themes/settings, right?
4) Do any of the developers offer tech support?
I now throw myself to the mercy of the masses, prepared for flames, but hoping for help.

NoobyMcNoob said:
1) I have the SPH-D720 model. I see rooting guides for the I9020 but not the SPH-D720. Will those other guides work for my device? I've seen other people ask this same question get sent to BuglessPete's guide so I'm assuming so, but I want to be sure.
Click to expand...
Click to collapse
It's the same.
- fastboot oem unlock
- flash a custom recovery for your device (crespo4g) using fastboot
- boot into CWM, mount system and flash the su binary
NoobyMcNoob said:
2) I know that GRJ90 and 2.3.5 just came out. My phone is updated to both. It looks like most of the root guides are still referring to 2.3.4 or 2.3.3. Should I wait until someone releases an updated 2.3.5 guide, or is the method still the same?
Click to expand...
Click to collapse
No change unless you are trying to flash a modified boot.img for adb remount (this is not necessary if you merely want root access)
NoobyMcNoob said:
3) Backups...these are different than saved settings, yes? So when I root my phone (which apparently requires unlocking the bootloader now) I'm going to lose all of my apps/themes/settings, right?
Click to expand...
Click to collapse
Yes, fastboot oem unlock wipes everything, including the SD card.

Thanks. So a follow up question then:
Is it possible to back up all of my settings and whatnot, and then quickly put them back after rooting the phone? No biggie if not, and since all of my contact info is on Google that sync happens automatically.

Another question - when I'm installing the sdk, do I need all the other stuff that it automatically selects or can I dump all that and just download the USB driver package?

NoobyMcNoob said:
Another question - when I'm installing the sdk, do I need all the other stuff that it automatically selects or can I dump all that and just download the USB driver package?
Click to expand...
Click to collapse
You will need the usb driver and platform tools.
Sent from my Nexus S using XDA Premium App

NoobyMcNoob said:
Thanks. So a follow up question then:
Is it possible to back up all of my settings and whatnot, and then quickly put them back after rooting the phone? No biggie if not, and since all of my contact info is on Google that sync happens automatically.
Click to expand...
Click to collapse
You could use something like titanium backup, but watch what you restore as some things cause issues.
Sent from my Nexus S using XDA Premium App

Awesome. I'm taking the leap now! So far, nothing screwed up...

So...I can't get the correct driver installed. In all the guides it says I should have the Bootloader Interface listed as the driver. But that is not one of my options - Allgamer's guide says there should be 3 choices, but I only have 2:
Android ADB Interface
and
Android Composite ADB Interface
How do I choose the Bootloader Interface?

You need to be in the bootloader on the phone I believe. I am new to the nexus s so I am not 100 percent sure.

Didn't work from the bootloader either - still showing Android ADB Interface.
I guess I'll uninstall everything and start from scratch.

New Owners Of The OnePlus One..

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

New to Linux, wanting to root and or flash, Xperia Z5 Android 6.0.1

Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.

spynathan said:
Hello, this is my first post on XDA forums so take it easy on me. Recently I've started taking interest in rooting my Xperia Z5. However I don't really know much at all about Linux, and I've never rooted an android device before. I am actually a coder, in fact I'm using a laptop with a HEAVILY modded version of Win10, and with several apps of my own. I've only recently, about a few months ago, bought a decent android phone. I got the Xperia Z5 off eBay for a good price, brand new for a couple hundred bucks. I'm interested in slowly learning basic coding and hacking on android, so I figured I'd go with the first major step and getting it rooted so I can actually mod the thing. The operating system is nice, doesn't have much bloatware, but I'd like to flash a new ROM on it. I've dug around a bit, and I've seen a few root and flash methods, but I really don't have any idea which one is trusted, or which would be the most stable option. I figured my best option would be to signup here, and ask for some advice. I saw ROMX here on the forums, and it looked very promising. But since I'm new to all this, I thought it would be wise for me to ask for advice on where to start what what would be a good rom to flash. I have the E6603 Model, Android 6.0.1, with the April 1, 2016 security patch. And yes, I do fully understand the risks and dangers as well as security concerns of rooting, and flashing. But to be honest, I probably do far more dangerous things on a weekly basis. I thank you all for your time, any help is appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed

Envious_Data said:
http://forum.xda-developers.com/xperia-z5/general/guide-rooting-unlocking-bootloader-t3354307
there is this which i followed to root my Z5 but with marshamall you do have to have a unlocked bootloader so you can use systemless root, it isnt neccisary to downgrade and backup your DRM but it is advised since sony doesnt seemingly like wanting to repair phones with missing DRM
basic how to:
- Download flashtool and a FTF of your choice
- use flashtool the extract the kernel.sin using tools > sin extractor (you will have to open the FTF file in winrar or something like to copy it)
~ you should get a kernel.elf when extracted
you can then use rootkernel to repack the kernel with a recovery menu like twrp and also disable some system verification stuff that will prevent things from working or the phone booting
this is when you need a unlocked bootloader
- from there you can flash your kernel and boot the device and flash superSU systemless (from the recovery menu )unless you havent downloaded that already
~ you can get to the recovery menu by pressing volume up while the yellow LED shows up on the bootsplash
i may have missed some stuff but that guide I linked has everything i explained here ^ this above is how ive rooted my phone and re-rooted when needed
Click to expand...
Click to collapse
Awesome thanks! I'll try it first thing tomorrow after work.

Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.

spynathan said:
Ok so I've gotten everything done, backed up my drm unlocked the bootloader, and what not. Got to the last bit and I can't seem to get fastboot to work, it just says waiting for device. I've tried reinstalling all the drivers a few times, but nothing worked. Flashtool recognized the device, just couldn't get fastboot to recognize it. I'm running windows 10, I've made sure all the drivers are there but still no go. Any help would be greatly appreciated, I'm kinda stuck atm. EDIT, I found a fix for my case. Even though the drivers were installed, for some reason they weren't being read. Anyway all working now, thanks again.
Click to expand...
Click to collapse
atleast on windows 10 i found that i had to disable driver signature verifacation and sometimes i had to run command prompt in admin

How to Update to 7.1.1 on a Rooted, Unlocked Bootloader, Google Play Pixel?

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.

Just bought a P3A, do I update prior to rooting

I will take delivery of a new Pixel 3a later this week. I will thoroughly read through “How to root the Pixel 3a with or without twrp & take OTA updates once rooted” and “How to Root Your Pixel 3a and Install Magisk (on Pie & Q) with or without TWRP”. But before unlocking bootloader and rooting should I accept all updates first during the initial setup?

MrTooPhone said:
I will take delivery of a new Pixel 3a later this week. I will thoroughly read through “How to root the Pixel 3a with or without twrp & take OTA updates once rooted” and “How to Root Your Pixel 3a and Install Magisk (on Pie & Q) with or without TWRP”. But before unlocking bootloader and rooting should I accept all updates first during the initial setup?
Click to expand...
Click to collapse
Yes

bejunk said:
Yes
Click to expand...
Click to collapse
Thanks. The little reading I have done so far, it sounds like you can not flash or boot TWRP in Android 10. Won't all the updates take me to 10? I will want to back up my ROMs.

MrTooPhone said:
Thanks. The little reading I have done so far, it sounds like you can not flash or boot TWRP in Android 10. Won't all the updates take me to 10? I will want to back up my ROMs.
Click to expand...
Click to collapse
Oh, i forgot as i dont use TWRP anymore.
Yes TWRP only works on Android 9.
However you can't install it like in the past time. You can only boot it via fastboot. You need to do this everytime you want to use TWRP. However when i tried it in past times it did not work well afaik, a full backup did not work at all.
So yeah try it with Android 9 first.
But with all the google backups nowadays i dont have the need for a nandroid (twrp backup)...
Especially as you can just reflash the stock image with deleting /data.
Here is the main thread, i think it will be more helpfull than i am https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413

The very first thing to do is minimal setup so you can enable developer settings and allow bootloader unlocking. That's a sticky setting, so then you can update, factory reset, etc. before actually unlocking the bootloader and rooting. Especially important if you're US/Verizon (don't put your SIM in until bootloader unlocking is enabled).

mike.s said:
The very first thing to do is minimal setup so you can enable developer settings and allow bootloader unlocking. That's a sticky setting, so then you can update, factory reset, etc. before actually unlocking the bootloader and rooting. Especially important if you're US/Verizon (don't put your SIM in until bootloader unlocking is enabled).
Click to expand...
Click to collapse
Thanks. So I read the two rooting threads I referenced above. I have always used TWRP in the past, but seeing it not supported in Android 10, I am considering skipping that. Do you think TWRP will support Android 10 in the future? I am a little nervous making changes without a backup. My plan would be to stick with a rooted stock at first than consider migrating to a custom ROM. Any recommendations are appreciated. Phone will be delivered tomorrow.

bejunk said:
But with all the google backups nowadays i dont have the need for a nandroid (twrp backup)...
Click to expand...
Click to collapse
I am not sure what you mean by "google backups nowadays". Is it the availability of stock ROMs?

MrTooPhone said:
I am not sure what you mean by "google backups nowadays". Is it the availability of stock ROMs?
Click to expand...
Click to collapse
No , I think most people use a TWRP backup because it restores you to a specifiic point with all your apps, user settings and your data in those apps.
Thats why i used it in the past times. Setiing up a phone in the past could be really time consuming and frustrating.
But nowadays, if you use the google backup (in Settings > System > Backup) (and the whatsapp one for messages - thtas the only messenger i use, but every other popular messager has a backup feature now) setting up the phone takes maybe 10 mins when i flash the factory image, it even gets my homescreen layout and my wallpaper back, also my settings. Apps which support that also keep their settings.
In the past i allways had a custom rom, because stock rom sucked. But with the Pixel theres no reason for me to use a custom rom anymore.
About root, i rooted my phone since i first used android, ca. 2010. But now I really dont need it anymore, so i just keep things stock.
---------- Post added at 16:03 ---------- Previous post was at 15:50 ----------
MrTooPhone said:
Thanks. So I read the two rooting threads I referenced above. I have always used TWRP in the past, but seeing it not supported in Android 10, I am considering skipping that. Do you think TWRP will support Android 10 in the future? I am a little nervous making changes without a backup. My plan would be to stick with a rooted stock at first than consider migrating to a custom ROM. Any recommendations are appreciated. Phone will be delivered tomorrow.
Click to expand...
Click to collapse
I dont think TWRP will be supported in the futur on A10. Google locked up /system and some other partitions the TWRP team needs to find new solutions but there id not much hope.
Did you buy your phone unlocked? If yes, the worst part you should be worried about is losing you app data from some apps. You cant really brick your phone. In the worst case you just need to flash a factory image.
You should know that rooting your phone will probably break google pay and banking apps. May i ask what did you want use root for?
I dunno, I really like Lineage OS, but it just feels like a downgraded stock rom.. (I used it before all the time on all phones before getting a pixel).
Also, for every update (monthly) you need to patch your boot.img, flash it, and the apply the update. Its some work which i dont think is worth it anymore.

bejunk said:
May i ask what did you want use root for?
Click to expand...
Click to collapse
Thanks for the detailed reply. I am coming from a MotoG3 (rooted stock), a 2015 era phone. So a lot has changed. I really have not seen a mid range phone I really liked, so I jumped on the P3a when I heard the news they were being discontinued.
I use root mainly for Adfree, SD-Maid, and Titanium Backup. I used to use Cerberus until the developer reneged on a lifetime subscription. I don't mess with the system apps much, but I do keep a few apps frozen except for the times when I seldom need them.

Magisk is the best way to root your phone as it still passes the SafetyNet check and google pay and banking apps continue to work. There is an excellent thread here on how to do it.
[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted
Every month, I "uninstall" magisk (which really just restores the original boot files) and sideload the latest update, then I install the magisk-patched boot.img and my phone is rooted again.
To be honest, I don't miss twrp at all. adb and fastboot are all that's needed. The backup in android 10 is perfectly sufficient.
This phone is practically impossible to brick. I love my Pixel 3a, except for the one problem I had when the bottom speaker died and I had to have it repaired under warranty at the local ubreakifix in less than an hour.

MrTooPhone said:
Thanks for the detailed reply. I am coming from a MotoG3 (rooted stock), a 2015 era phone. So a lot has changed. I really have not seen a mid range phone I really liked, so I jumped on the P3a when I heard the news they were being discontinued.
I use root mainly for Adfree, SD-Maid, and Titanium Backup. I used to use Cerberus until the developer reneged on a lifetime subscription. I don't mess with the system apps much, but I do keep a few apps frozen except for the times when I seldom need them.
Click to expand...
Click to collapse
Yeah, I had that phone too It was pretty good for its time. I even replaced the screen once, but its really complicated on that phone... To your needs:
Adfree: you can setup a custom DNS server (i think it was adguards one) in the settings menu which will block all ads, so no real need anymore for adaway or root for this. Just google a bit.
Titanium backup: I does not work so well is what i heard and like said nowadays most apps backup over Google backup. With Android11 it will get even harder as /data partition is even more protected now. Not really worth it imho.
Froze system apps: Pixel Android is really barebones. The few apps which i dont need (like Google Music/Video PixelBuds app etc) you can just disable them in the settings. This will freeze them, its like uninstalling them, they wont show up at all.
SD Maid is great but only rooting it for using it, is not worth it. You can clear the cache of the apps which hoard a lot of data by yourself. Also, when you uninatll an app, it asks you if you want to delete your userdata as well. The phone takes care of the rest.
Cerberus: If you keep your bootloader locked, when your phone gets stolen, nobody can access your phone. Even if they reflash it, on first boot it will ask to login to the gmail last time set up. Theres no workaroud. Google aslo has a find my device thingy, wher you can track or delete your device remotly.
I would suggest to use your phone unrooted for some time, and if you really need to root it for something, you can still do it.
Welcome to team Pixel, mate!
(sorry my grammer im to lazy to double check it...)

@bejunk Just a not to say thanks again. I took your advice and did not root. However, I did flash with GrapheneOS and then re-locked the bootloader. Time will tell if I like it.