Develop Bugs

Question on root and unlock bootloader

I am new to the nexus 7.
Can I root without unlocking the broader?
What is the side effect of unlocking the boot loader?
Is there existing method to root without installing customer recovery?
Thanks

macaumen said:
I am new to the nexus 7.
Can I root without unlocking the broader?
What is the side effect of unlocking the boot loader?
Is there existing method to root without installing customer recovery?
Thanks
Click to expand...
Click to collapse
There is currently no known way to root without unlocking the bootloader and using a custom recovery.
Unlocking the bootloader allows you more control over the tablet. Specifically to install custom recovery, ROMs, etc. Most of the benefits from an unlocked bootloader are things you do from a custom recovery, not through the bootloader itself. The only real negative 'side effects' are that you lose some of the safety benefits, since you can do dangerous things if you don't know what you are doing, and that it may void your warranty.

So, if want to root, I must unlock bootloader?
Well I still get ota with bootloader unlocked?

macaumen said:
So, if want to root, I must unlock bootloader?
Well I still get ota with bootloader unlocked?
Click to expand...
Click to collapse
1. Yes
2. Technically you can, but not recommend; just wait for the rooted stock and flash that.

teh roxxorz said:
1. Yes
2. Technically you can, but not recommend; just wait for the rooted stock and flash that.
Click to expand...
Click to collapse
Regarding your #2, there is no reason not to unlock the bootloader to get OTA updates. The only thing that breaks OTA is custom recovery.

phonic said:
Regarding your #2, there is no reason not to unlock the bootloader to get OTA updates. The only thing that breaks OTA is custom recovery.
Click to expand...
Click to collapse
Completely correct. I just said not to do it, cause he seems less experienced, and from my experience, they get freaked out afterwards trying to put it back on. So trying to save him a headache, lol.

I recommend staying stock unless you absolutely need a specific root required app.
Right now there isn't a reason for root access except titanium backup.
I do recommend, however, to go ahead and unlock. It will wipe your device including personal data, so might as well get that out of the way now before you risk losing something important.
You can easily flash a custom recovery and root anytime after that, but I would wait until knowledgeable devs figure out the device a little more first.
Sent from Nexus 7 FHD from XDA Premium HD

player911 said:
I recommend staying stock unless you absolutely need a specific root required app.
Right now there isn't a reason for root access except titanium backup.
I do recommend, however, to go ahead and unlock. It will wipe your device including personal data, so might as well get that out of the way now before you risk losing something important.
You can easily flash a custom recovery and root anytime after that, but I would wait until knowledgeable devs figure out the device a little more first.
Sent from Nexus 7 FHD from XDA Premium HD
Click to expand...
Click to collapse
I'm not sure why you would suggest people not to root now. You mentioned a very good reason to do so - Titanium Backup. Not only is it useful for backups in general, but it's also a lifesaver for copying apps and their data from one device, like someone's old N7, to their new N7.
While I would certainly agree that people should wait before flashing custom ROMs, kernels, hacks, etc., nothing is going to change with rooting your N7 today versus a week or month from now. All the pros and cons will still be the same.

phonic said:
I'm not sure why you would suggest people not to root now.
Click to expand...
Click to collapse
They guy doesn't need root. He also doesn't understand root. So his chances of softbricking are good, and then, instead of us trying to talk him out of rooting, we now have to talk him through how to fix it.... .. Can we count on you to provide this support since your are so OK with him rooting now?

tweaked said:
They guy doesn't need root. He also doesn't understand root. So his chances of softbricking are good, and then, instead of us trying to talk him out of rooting, we now have to talk him through how to fix it.... .. Can we count on your to provide this support since your are so OK with him rooting now?
Click to expand...
Click to collapse
Neither you nor I have any idea what he needs or doesn't. He hasn't said anything other than asking some basic questions about the process. There are numerous guides on here that walk people through rooting step by step. There are also a handful of people who have soft bricked their device and asked for and received help. And yes, I have assisted people with similar issues in the past. Everyone on this board has at one point in their lives screwed something up - that's how we learn.
In any case, my point was that there is no clear reason for him not to do it if he wants to. The device is pretty forgiving unless he kills the bootloader.

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<

first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.

redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted

esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.

redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?

I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.

Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.

hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.

esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".

I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?

esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

Debating on rooting my Pixel 2XL, looking for seasoned android user's advice.

Hi all,
I am possibly interested in rooting my device. I have been rooting/rom'ing since back on my HTC Hero forever ago. Made a brief trip to iOS, and got into jailbreaking, but always missed the Android atmosphere. I am having issues with the battery on my device, and have debated factory resetting the device, and came across the forums about rooting.
I would just run a stock rom, with root, to be able to use Gravity box and Xposed. I am not super familiar with terminal/command line, so that part worries me a bit.
Anyone that is rooted, how does your device's battery last? Any major issues you notice? I use my camera for pictures of my family everyday, and don't want to risk anything that could compromise this feature.
Thanks in advance

Rooting doesn't hinder or damage or affect your battery directly
If you have enough reasons to root just root
I have plenty reasons to root that's why i did
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs

I've had lots of Android phones and tablets over the years, and every one was rooted at some point. Imo, rooting is not as critical as it used to be. Back in the early days of Android, rooting was the only way to get certain features that were later incorporated into Android. As Android matured, rooting became less important unless you needed a specific function or app. Rooting is still required for stuff like Titanium Backup, AdAway, Viper4Android, etc, because those need access to system-level files, which is impossible without root permissions.
Ask yourself what do you plan to do with root access? If you have a specific need for root, then go for it. Obviously you are not new to the game, and the procedure for rooting Pixel 2 is brain-dead simple compared to what you did for HTC Hero. However, if you don't have a specific need or plan, then it is not worth messing with imo. The Pixel 2 is an absolute beast out of the box. Root tweaks won't get you significantly better performance. I am rooted and use Sysconfig patcher (a Magisk module) to allow doze for Google Play Services for a very small gain in battery life. But I wouldn't root just for that. Monthly updates are a little more hassle if you are rooted, but if you get that far then you should be able to flash updates too.

AwkwardUberHero said:
Hi all,
I am possibly interested in rooting my device. I have been rooting/rom'ing since back on my HTC Hero forever ago. Made a brief trip to iOS, and got into jailbreaking, but always missed the Android atmosphere. I am having issues with the battery on my device, and have debated factory resetting the device, and came across the forums about rooting.
I would just run a stock rom, with root, to be able to use Gravity box and Xposed. I am not super familiar with terminal/command line, so that part worries me a bit.
Anyone that is rooted, how does your device's battery last? Any major issues you notice? I use my camera for pictures of my family everyday, and don't want to risk anything that could compromise this feature.
Thanks in advance
Click to expand...
Click to collapse
I too am a stock rom + root user. My battery life is outstanding for my usage patterns, usually 8-12 hours of SOT. As far as rooting, only you can answer that. Personally, I love it!! I like using dark themes, AdAway, TiBu, and the ability to use custom kernel tweaks. Having said all that, I haven't noticed any decrease in performance with day to day usage that you would likely use. So, if you ask me....root that sucker! ????

Badger50 said:
I too am a stock rom + root user. My battery life is outstanding for my usage patterns, usually 8-12 hours of SOT. As far as rooting, only you can answer that. Personally, I love it!! I like using dark themes, AdAway, TiBu, and the ability to use custom kernel tweaks. Having said all that, I haven't noticed any decrease in performance with day to day usage that you would likely use. So, if you ask me....root that sucker!
Click to expand...
Click to collapse
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?

AwkwardUberHero said:
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
Click to expand...
Click to collapse
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:

Here's some more info for you to read as well :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Badger50 said:
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Click to expand...
Click to collapse
Do you really need to remove the lock screen password? I flashed the OTA (using this method: https://forum.xda-developers.com/pixel-2-xl/how-to/how-to-applying-monthly-security-t3750234), and I had no issue entering the PIN from within TWRP (twrp-3.2.1-2).

And don't forget that rooting is a XDA rush!

uofirob said:
Do you really need to remove the lock screen password? I flashed the OTA (using this method: https://forum.xda-developers.com/pixel-2-xl/how-to/how-to-applying-monthly-security-t3750234), and I had no issue entering the PIN from within TWRP (twrp-3.2.1-2).
Click to expand...
Click to collapse
Just my personal preference really. I just don't take chances with twrp if I don't have to :good:

sublimaze said:
rooting Pixel 2 is brain-dead simple compared to what you did for HTC Hero.
Click to expand...
Click to collapse
I never rooted my Hero but did completely unlock my HTC 4G LTE(S-off???). Dear lord was that a nightmare. I think back then it actually required a tool(Dirty Racoon???), only certain ROM's would boot on certain bootloaders, etc. I don't miss those days lol.

AndrasLOHF said:
I never rooted my Hero but did completely unlock my HTC 4G LTE(S-off???). Dear lord was that a nightmare. I think back then it actually required a tool(Dirty Racoon???). I don't miss those days.
Click to expand...
Click to collapse
I did root the HTC Hermes (win5) which was a trip!

AwkwardUberHero said:
Seeing your input on this, Badger, makes me want to do it. Granted, not having rooted in over four years or so, I feel like I am missing a wealth of knowledge on this subject. I may give it a shot later today and see what happens. The only thing that worries me is installing the updates that come out each month. Do you do those monthly?
Click to expand...
Click to collapse
While the 2 XL is a great phone even without root, I think there is just too much fun, experimenting, and customization to miss if not rooted. But this is a personal choice and you have to decide if you really want a specific battery icon, or any other custom feature.
You been given links to some steps and guides which are very good references. Since you said it's been four years since you rooted, I'm throwing in my guide as well
I am not a technical kinda guy, and sometimes the little details are what trip me up, so I crafted this initially for myself needing to be reminded of each step.
It is very detailed, step by step with tips and links and everything needed in one place. It certainly isn't the final authority for sure, but I've used it dozen and dozens of times with no issues. You can always default to the guide or other references if something isn't clear.
Take the plunge, I think you'll be very glad you did. In my opinion, root makes a great device an excellent device

@Az Biker @Badger50 I will be trying this on a Mac. Anyone happen to have steps for a Mac?
Thanks again for everything!

Mac instructions are in the op of the thread badger posted#7

galaxys said:
Mac instructions are in the op of the thread badger posted#7
Click to expand...
Click to collapse
Thanks! Totally overlooked that.

Badger50 said:
Oh I absolutely do the monthly updates using fastboot to install the factory images. It's actually very easy once you get the hang of it. You can look over my personal guide if you'd like so you have an idea of what to do :good:
Click to expand...
Click to collapse
Hey badger, thanks for these steps. Debating on trying this tomorrow. Do you have the actual rooting directions as well for a Mac? Tried looking in YouTube but could only find windows.
Thanks again in advance.

AwkwardUberHero said:
Hey badger, thanks for these steps. Debating on trying this tomorrow. Do you have the actual rooting directions as well for a Mac? Tried looking in YouTube but could only find windows.
Thanks again in advance.
Click to expand...
Click to collapse
First you'll need to enable developer options by tapping on the build number 7 times in settings/system/about phone. Then enable OEM unlocking and USB debugging. You'll need adb/sdk installed on your Mac, then you'll need to unlock your bootloader with the follow fastboot commands..
fastboot flashing unlock....
And
fastboot flashing unlock_critical...
You have to have magisk 16.3 and the twrp installer zip in your internal storage.
Then you'll need to fastboot the twrp.img with the Mac specific prefix command (which I don't know), but the command is...fastboot boot twrpxxxx.img
That'll boot you into twrp, then hit install, and navigate to where your twrp installer and magisk zips are. Flash twrp, followed by magisk, reboot, and you should be rooted.

Badger50 said:
First you'll need to enable developer options by tapping on the build number 7 times in settings/system/about phone. Then enable OEM unlocking and USB debugging. You'll need adb/sdk installed on your Mac, then you'll need to unlock your bootloader with the follow fastboot commands..
fastboot flashing unlock....
And
fastboot flashing unlock_critical...
You have to have magisk 16.3 and the twrp installer zip in your internal storage.
Then you'll need to fastboot the twrp.img with the Mac specific prefix command (which I don't know), but the command is...fastboot boot twrpxxxx.img
That'll boot you into twrp, then hit install, and navigate to where your twrp installer and magisk zips are. Flash twrp, followed by magisk, reboot, and you should be rooted.
Click to expand...
Click to collapse
Awesome. Thank you. I was messing with adb a bit today, enabling immersive mode and what not. I think that I can follow these steps.

Need some help

I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.

Download latest factory image. Extract the boot.img from it and save to your phone. Open magisk manager and patch that boot.img. Save /download/magisk_patched.img to your computer. Disable or remove any magisk modules that you might have running. In bootloader run the flash-all.bat, after editing to remove -w, and boot into system. Reboot to bootloader and run "fastboot flash boot --slot all magisk_patched.img" and you should be good to go. Make sure to back everything up before hand just in case something does wrong. I use a mix of titanium backup, sms backup/restore, export contacts, and manually saving files. There are other ways, but this is what I am comfortable with.

pside15 said:
I have been into the Android scene since the original Samsung Galaxy S. I couldn't even tell you how many phones I had since then but I was always big into rooting and flashing more ROMs than healthy. I lost the ability to get endless company phones and ended up with locked bootloader phones for a few years. One day I saw a friend with the Pixel 2 and I got the itch again. I got the Pixel 3XL and unlocked the bootloader and rooted it immediately. At the time I didn't realize how much different the process was as far as updating and installing ROMs than it used to be on my older phones like my beloved Nexus phones. Basically I'm paranoid about doing anything because the process sounds extremely complicated to me. Maybe I'm just getting older. I build server and storage solutions every day but this is foreign to me. Sorry for all the rambling. Basically I'm rooted and still on the November 2019 build. I'm starting to get OTA update prompts a lot but I just ignore them. I just really want to update the easiest way and hopefully be able to do more going forward. Thanks for any help anyone can provide.
Click to expand...
Click to collapse
Here ya go... https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117

Google offers their own flashing update tool. You can find it here, https://pixelrepair.withgoogle.com/carrier_selection.

Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.

pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You will need to wipe data on the upgrade to 10.
You will need to root again after the update. Bootloader will remain unlocked.
Once you have rooted, there is a method to take an OTA, and stay rooted. A description of the procedure is in the forums somewhere.
Again, I would recommend to follow the guide posted by Homeboy76. It will comprehensibly explain all the steps you need to achieve root,update etc. With links to downloads.
Gone are the days of flashing with just your phone. My first rooting experience was with an HTC Amaze. Then an S4 Samsung.
Good luck..
Edit: I stand corrected on data wipe when going to 10. I perhaps was overly cautious, and followed other recommendations.

pside15 said:
Thanks for all the replies guys. Will all these methods keep by bootloader unlocked and phone rooted? I definitely want those as they are now. Going to look a lot closer into the kernel and ROM situation. Also, is it safe to go from 9 to 10 without wiping? I'd obviously rather not wipe but if it might cause issues then I'd go with the wipe.
I know it's an old phone but I miss my old HTC Desire HD. So much awesome development for that phone. Released with Froyo and eventually got functioning Marshmallow builds. That phone and my Nexus 4 are probably my favorites of the countless phones I've had over the years. Anyway, thanks again for the replies. Gonna get this thing updated tomorrow.
Click to expand...
Click to collapse
You do not need to wipe data to update to 10. It is perfectly safe, we all did it. And so did all the people with locked bootloaders. You only have to wipe going down. Up is fine.
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
And here is the link to take an ota without losing root.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).

Anyone tried Google's flashing update tool?

Homeboy76 said:
Anyone tried this?
Click to expand...
Click to collapse
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection

sliding_billy said:
Just a heads up, your link is broken. Looks like the period at the end of the sentence accidentally got included in the hyperlink. The one in spotmark's post works. https://pixelrepair.withgoogle.com/carrier_selection
Click to expand...
Click to collapse
It's working now

Homeboy76 said:
The link is in spotmark's quote: How can it be my link?
When I click it it works.
Click to expand...
Click to collapse
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.

sliding_billy said:
It's only if you click the link from your post. You copied the . into the link. It comes up with 'Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.
Look closely at the hyperlink highlighting, and you'll see the . at the end.
Click to expand...
Click to collapse
It's working now

Homeboy76 said:
Read the edited post above yours.
Click to expand...
Click to collapse
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.

sliding_billy said:
Not kidding, it is still not clicking without the . included. When you look at spotmark's post, the dot is black. Yours is blue and part of the hyperlink. I tried it in two browsers.
Click to expand...
Click to collapse
@sliding_billy
It's working now

Homeboy76 said:
@sliding_billy
It's working now
Click to expand...
Click to collapse
Winner, winner. Even better when you can't see the link.

Just got a Pixel 3XL

I just received a Pixel 3XL as a free hand me down and need some assistance. I know it's a couple of years old but still seems to be a solid phone. I basically need to wipe this thing completely clean. The problem is that it's rooted with an unlocked bootloader with TWRP. While that might not be a huge issue it's also on a older Android version 9. I've been reading but I'm not exactly sure where to start in regards to what to do first. I know my share of rooting and flashing ROMs but my knowledge is back with the Nexus and older HTC phones. Any help would be greatly appreciated.

rootbox15 said:
I just received a Pixel 3XL as a free hand me down and need some assistance. I know it's a couple of years old but still seems to be a solid phone. I basically need to wipe this thing completely clean. The problem is that it's rooted with an unlocked bootloader with TWRP. While that might not be a huge issue it's also on a older Android version 9. I've been reading but I'm not exactly sure where to start in regards to what to do first. I know my share of rooting and flashing ROMs but my knowledge is back with the Nexus and older HTC phones. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi,
Pretty much everything you need to know is here: https://forum.xda-developers.com/t/guide-root-pixel-3-xl-android-11-r.4160447/
You can go ahead and just flash whatever factory image you want from here, (mostly) just like a Nexus device:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just use the flash-all script, don't flash one partition at a time...
It will remove root and wipe your phone clean. Root on Pixels doesn't work how it used to back in the Nexux days, as TWRP is not fully supported on 10 or 11 yet.
Just be sure the previous owner Google account has been properly removed before you proceed, otherwise you won't be able to log in with yours: FRP (Factory Reset Protection).
Post in the thread i linked you or here if you need further assistance.
Cheers...
Sébastien.

5.1 said:
Hi,
Pretty much everything you need to know is here: https://forum.xda-developers.com/t/guide-root-pixel-3-xl-android-11-r.4160447/
You can go ahead and just flash whatever factory image you want from here, (mostly) just like a Nexus device:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Just use the flash-all script, don't flash one partition at a time...
It will remove root and wipe your phone clean. Root on Pixels doesn't work how it used to back in the Nexux days, as TWRP is not fully supported on 10 or 11 yet.
Just be sure the previous owner Google account has been properly removed before you proceed, otherwise you won't be able to log in with yours: FRP (Factory Reset Protection).
Post in the thread i linked you or here if you need further assistance.
Cheers...
Sébastien.
Click to expand...
Click to collapse
Thanks for the reply, much appreciated. His account is completely gone and mine is the current one. I basically want to update it but I do want to keep root for a few things. I was mainly concerned since it's on an old version of 9 and I know there were some bootloader changes which is what really had me concerned.

rootbox15 said:
Thanks for the reply, much appreciated. His account is completely gone and mine is the current one. I basically want to update it but I do want to keep root for a few things. I was mainly concerned since it's on an old version of 9 and I know there were some bootloader changes which is what really had me concerned.
Click to expand...
Click to collapse
Hi,
You said you have read, but don't know where to start... If you state your goal, it would be easier to help you!
Keep root with stock firmware? What Android version?
Cheers,
Sébastien.

5.1 said:
Hi,
You said you have read, but don't know where to start... If you state your goal, it would be easier to help you!
Keep root with stock firmware? What Android version?
Cheers,
Sébastien.
Click to expand...
Click to collapse
Good point. I'd like to get updated to the most stable android version and keep root with the ability to flash custom kernels. I've been using this for a bit on 9 and it's definitely showing it's need to be updated. The option to flash ROMs would be nice but definitely not necessary. I'm not opposed to doing a complete wipe but if I could keep my data that would obviously be optimal even though I highly doubt that will be possible. Thanks again for the reply.

rootbox15 said:
Good point. I'd like to get updated to the most stable android version and keep root with the ability to flash custom kernels. I've been using this for a bit on 9 and it's definitely showing it's need to be updated. The option to flash ROMs would be nice but definitely not necessary. I'm not opposed to doing a complete wipe but if I could keep my data that would obviously be optimal even though I highly doubt that will be possible. Thanks again for the reply.
Click to expand...
Click to collapse
You should be able to update and save data.
Flash the factory image as mentioned above, however before you run the flash-all bat file edit it with notepad. Near the end of the file remove the -w and save it. Then run the flash all. That will update you and save data.
Then you reroot following one of the rooting guides. Copy boot.img from the factory image to your phone,. Install Magisk Manager and patch the boot.img. Copy that back to your computer and flash it.

TonikJDK said:
You should be able to update and save data.
Flash the factory image as mentioned above, however before you run the flash-all bat file edit it with notepad. Near the end of the file remove the -w and save it. Then run the flash all. That will update you and save data.
Then you reroot following one of the rooting guides. Copy boot.img from the factory image to your phone,. Install Magisk Manager and patch the boot.img. Copy that back to your computer and flash it.
Click to expand...
Click to collapse
Thanks for the reply. I read about doing that but just wasn't sure if that would all work properly since the bootloader was unlocked and TWRP was installed. I'm guessing the factory image flash will get rid of TWRP. It also doesn't matter going to say 11 straight from 9? Sorry for all the dumb questions but this is way different than it used to be when I started back with the original Galaxy S, HTC DesireHD, and Nexus 4.

rootbox15 said:
Thanks for the reply. I read about doing that but just wasn't sure if that would all work properly since the bootloader was unlocked and TWRP was installed. I'm guessing the factory image flash will get rid of TWRP. It also doesn't matter going to say 11 straight from 9? Sorry for all the dumb questions but this is way different than it used to be when I started back with the original Galaxy S, HTC DesireHD, and Nexus 4.
Click to expand...
Click to collapse
Correct, this flash will remove twrp. You are done with twrp it is not working on pixels 10 and up.
9 to 11 should be fine, there is always a risk upgrading a full version. That risk is not any greater because you are jumping two versions.