So, my Google Edition Pixel XL arrives tomorrow, and I've been digging around in preparation (I've previously owned the OG Droid and Galaxy Nexus, so consider myself marginally competent as a consumer of non-OEM firmware). Anyway, I'm super intrigued by the firmware slots I've heard mentioned, but was hoping for some clarification on how they work.
-Do they run from the same Data partition, so you can run one Kernal/ROM one day, and the other on another day, back and forth, forever...
-Or are they more like a nandroid backup?
Thanks for helping me understand this new feature,
Christian
Same data.
So remember what they were built for. They were built to run the same OS and provide seamless updates. They were not built for dual boot.
You can do a little trickery. Like same Rom with one rooted and one not pretty easily. Beyond that it is very tricky, there are a couple of folks here that seem to habe a handle on it.
Hopefully they will be along shortly.
The slots on the Pixel XL seem to trip up a lot of people who try to install TWRP, a custom Rom or root the phone. The really frustrating thing is that I did my research too and came across completely contradictory information regarding how they relate to custom flashing and should be handled. Even worse, the custom flashing guide on XDA for this phone is terrible. If you read through all the pages at various points it tells you to do something different than at the beginning of the thread and it doesn't deal with the dual slots at all. Google also seems to keep breaking root on the Pixel XL where SU programmers have to come up with updates and new flashing procedures to keep root working. The Pixel XL is the only phone I have ever owned that I am afraid to flash on, but if you are braver than me then I certainly wish you luck.
Related
I'll try to keep it short, but;
I bought a Google edition Pixel XL from swappa because I saw a really good deal on it and couldn't pass it up. Though even though it's a google bought phone (I checked the IMEI and unlocked the bootloader with no problems, so it basically has to be), I'm on the Verizon build of NDE63X instead of NDE63V, which is the "regular" build. I'm not sure if this could pose any problems in the future, but I thought I'd try to get on the regular build in case.
I tried sideloading the normal OTA image, but it denied by saying it was out of date as compared the build I'm on now? It was downloaded straight from the Google developers page, so that doesn't seem to make sense to me. Eventually I toyed around and ended up flashing the phone with the google edition of the OTA, and everything seemed to be in order. All of this was a pretty long and painstaking process because I've known barely anything about the intricacies of Android before like 2 days ago and have just been learning it all from scratch. However, when I finally was in the V build over the X build, I saw my phone had an update; I went ahead and installed it just thinking that it was standard and maybe the OTA I flashed in was lacking the November security patch or something. When this update went through, it put me back on the X build. Needless to say I was a little frustrated, I kinda felt like I just wasted a royally large amount of time.
So I guess that leaves the question of; why/how exactly did this happen? Is it an issue?
My bootloader is unlocked now after that whole fiasco; should I relock it? Is it any kind of significant security issue? I've heard that relocking the bootloader can brick the phone entirely, and lord knows I don't want that.
If I keep the bootloader unlocked, what exactly can I do with it? I know it allows to install custom kernals/roms, but I'm not exactly sure what that's like or what it's exactly capable of. I know, this is a very general question that I could google. But I'd also just like to hear people's inputs about it.
Will my phone get regular updates with the bootloader unlocked, or would it unable/cause some kind of error?
Thanks in advance for any replies! Like I said, I'm still really new to this whole thing, so if you could kind of explain answers and/or instructions in kind of a black-and-white way that would help me a lot. All of this is kind of intimidating, but it's also been a lot of fun, I like learning about it all.
@cam30era
This is what I did, I actually had it on the V build, for all of about 20 minutes. Then it pushed an update through and the update changed it back to the X. I'm not sure if I screwed something up along the way or exactly how it happened, but it seemed like a kind of unique thing.
Actually, if you'd like to downgrade, make sure your bootloader is unlocked. Flash the boot image from the factory image zip. After that you can sideload the V ota.
Sent from my Pixel XL
So what exactly is your problem with the build that you have other than being the "Verizon" version? The phone isn't going to function any different and there are probably little to no differences in the software other than a letter on the build number.
Sent from my Pixel XL
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
That would only affect models sourced from Verizon...
Sent from my Pixel XL
imnuts said:
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
Click to expand...
Click to collapse
Agreed. AS long as you keep your bootloader unlocked you can flash what you want. If you see something amiss flash another version.
Flashing the verizon firmware on a Non verizon phone should be fine. @imnuts said, same questions and answers with the Nexus 6. I flashed all sorts of builds just to see how they would perform... IN the end there were all the same.
After nearly three years with my trusty Sony Xperia Z5 Compact, I feel it's time to move on. Got my eyes on this phone since like forever and now that OP6 is releasing I'm hoping for some nice price drops. Anyway, I've read some threads on getting started modding the phone, but I still have a few questions.
With my phone I'm used to having one (usable) ROM, recovery and kernel combo. However, OP5t seems to have quite a few. Which ones are recommended? Do I need to patch the kernel to be able to boot with a modded system partition and to modify it while Android is running? (dm-verity and Sony RIC on my Z5C, respectively.)
Which is the go-to Windows app for flashing ROMs? (Like Flashtool for Sony?)
Do I have to back up a partition so that the camera keeps working and to still be able to play DRM-protected content after bootloader unlock? Which partition do I need to restore to completely lock the bootloader in case I change my mind (and need warranty again)? (So it shows "locked" instead of "relocked".) (On Sony I had to do these with the TA partition.)
Thanks a lot for reading through, I know I wrote a rather huge wall of text.
QWERTYsystems said:
After nearly three years with my trusty Sony Xperia Z5 Compact, I feel it's time to move on. Got my eyes on this phone since like forever and now that OP6 is releasing I'm hoping for some nice price drops. Anyway, I've read some threads on getting started modding the phone, but I still have a few questions.
With my phone I'm used to having one (usable) ROM, recovery and kernel combo. However, OP5t seems to have quite a few. Which ones are recommended? Do I need to patch the kernel to be able to boot with a modded system partition and to modify it while Android is running? (dm-verity and Sony RIC on my Z5C, respectively.)
Which is the go-to Windows app for flashing ROMs? (Like Flashtool for Sony?)
Do I have to back up a partition so that the camera keeps working and to still be able to play DRM-protected content after bootloader unlock? Which partition do I need to restore to completely lock the bootloader in case I change my mind (and need warranty again)? (So it shows "locked" instead of "relocked".) (On Sony I had to do these with the TA partition.)
Thanks a lot for reading through, I know I wrote a rather huge wall of text.
Click to expand...
Click to collapse
You're entering into Oneplus country, options rule the roost. You are going to have to read about all the roms and kernals and make a decision on what best meets your needs.
I wouldn't start there though, OOS is pretty good in it's own right so the smart money is on taking it for a spin before you move on to the roms. Many who do will stay there and many of those who leave for the roms come back to it. It really is that solid. To that end I would start by either simply updating the phone to the latest stock and rooting/recovery or go to the open beta with rooting/recovery. The latter have been by and large very stable as a whole so you are usually safe using them in daily driver duties. In either case useful upgrades to stock android that came on the phone along with some tuning via magisk will get a lot of users where they want to go with stock reliability and functionality.
To install you're going to use fastboot so you'll need to set that up, there are several tutorials available if you're unfamiliar with it. Some people just don't want to take the time to get fastboot 101 capable, if you're of that mind you can use several tools which are available in the development section.
You didn't ask but I'm going to throw something out there for your consideration. The 6 is going to be here soon, I get the impression you hang onto your phones a long time making it perhaps a better choice. You'll wait a bit more than a month but gain a half a year in "newness" to start that long journey.
QWERTYsystems said:
After nearly three years with my trusty Sony Xperia Z5 Compact, I feel it's time to move on. Got my eyes on this phone since like forever and now that OP6 is releasing I'm hoping for some nice price drops. Anyway, I've read some threads on getting started modding the phone, but I still have a few questions.
With my phone I'm used to having one (usable) ROM, recovery and kernel combo. However, OP5t seems to have quite a few. Which ones are recommended? Do I need to patch the kernel to be able to boot with a modded system partition and to modify it while Android is running? (dm-verity and Sony RIC on my Z5C, respectively.)
Which is the go-to Windows app for flashing ROMs? (Like Flashtool for Sony?)
Do I have to back up a partition so that the camera keeps working and to still be able to play DRM-protected content after bootloader unlock? Which partition do I need to restore to completely lock the bootloader in case I change my mind (and need warranty again)? (So it shows "locked" instead of "relocked".) (On Sony I had to do these with the TA partition.)
Thanks a lot for reading through, I know I wrote a huge wall of text.
Click to expand...
Click to collapse
Came from the Xperia Z2 after about 4 years and just recently bought the OP5T.
AFAIK, there's no Flashtool like application for OnePlus devices so you just have to rely on TWRP and there's no such thing as that stupid TA-Partition on the OP5T (or any OnePlus device). You won't lose anything when you unlock your OnePlus device, not even your warranty.
I don't have a recommended custom kernel or rom since I'm very pleased with OxygenOS but the main reason why I'm not switching to a custom ROM is that of Portrait Mode and Face Unlock which aren't available on custom ROMs.
There is Skipsoft and another, the name escapes me but it's there in the development section. Face unlock (Google) and portrait are available depending on the rom but are problematic on most. It is a good point because the google face unlock is not as good as the OP implementation. There are also the nav gestures which most seem to like and I'm among them.
Thanks everyone! Already learned so much! (But I still have some more.) You said OOS is stable (I heard it has some RAM management issues), should I go for the open beta? Do the new features outweigh the bugs? How is Magisk and themeing on OOS (does the former have bugs/random reboots, is latter even possible (Andromeda on Oreo, maybe))? Is there a way I could preserve my data between ROMs? Are there some must have apps/mods I should totally try out? (such as stereo sound mod and Google Camera) Speaking of, is there a recommended Google Camera port for this phone? And lastly, how is the audio quality?
EDIT: Oh and can this phone be easily bricked? I remember no matter what I did with my Z5C I could always reflash it in flashmode.
OOS is stable as can be, even the beta is pretty darn stable, more so than some stable releases. Realistically if the beta isn't offering something you want there is no reason not to go with the official release. You can read about the beta and it's various changes over on that thread.
The only issue either OOS or it's beta in terms of RAM management is that it makes engineers over at Samsung envious, this wont be a problem for most of us.
I'm not a theme guy of I've nothing to offer there. Magisk has been fully functional and has worked without a hitch in my use. As with any device the more modules you load the more you increase your odds of having a conflict in much the same way as you run into with exposed. I'm using the stereo mod, modded youtube, volume steps, and Sony framework with their player. I've had Viper on and it worked without problems but I've since broke down and purchased high(ish) end headphones and don't use it now. You'll have to try your faves and see how it goes but if their mainstream and you don't go overboard with the modules I'd expect them to work.
I use a combination of Ti and nandroids and do a clean flash with every new rom, normally I'll backup and then just dirty flash when going to the next iteration of the same rom. The phone is difficult to brick as long as you follow instructions and pay attention to what your doing, That would apply to almost any modern android phone though, they aren't easy to brick and typically even when you think you've bricked it you haven't, you just don't now how to get out of it. As good fortune would have it a lot of people here have already stubbed their toe on almost any problem you can have and between them and the guru's you will seldom be left with an actual honest to God brick. Pay attention and you shouldn't have to encounter a day of "oh crap" while you wait for others to help you.
I'd rate the audio on speaker as just OK, the in-call quality up at the ear has enough volume and is clear but not special. That puts it right about the same place as I rate most flagship phones.
For now don't overthink all this stuff, the 5T is an excellent value as most will say but more it's in many respects a better day to day phone than my Note 8 was which I've since given to one of my kids. You don't have to make excuses for this phone, outside of a camera which is behind the flagship curve it's solid.
Hey folks. Had the Pixel XL and was running Magisk, but wanted to get peoples impressions of root vs magisk on the Pixel 2.
Primary things I want it for: Adblocking, Viper audio, debloating, I can't even remember what the hell else I do.. (have been on a Samsung S9 temporarily after smashing my XL, didnt want to root for resale purposes)
Also, I know Pie just dropped, and the development here seems fairly active, so what is an estimated timeframe for 9.0 roms to drop? Not looking for ETA, so much as a general (1 month, 2 month, 3 years). On a similar note, is it possible to root/magisk the stock 9.0 rom? I see custom kernels, so methinks it is, but I want to be sure before I take the dive..
And finally, aside from warranty issues (which I don't qualify for anyways as my P2XL is second hand, and no invoice...stupid Australia), why WOULDNT I want to root?
Thanks
jewnersey said:
Hey folks. Had the Pixel XL and was running Magisk, but wanted to get peoples impressions of root vs magisk on the Pixel 2.
Primary things I want it for: Adblocking, Viper audio, debloating, I can't even remember what the hell else I do.. (have been on a Samsung S9 temporarily after smashing my XL, didnt want to root for resale purposes)
Also, I know Pie just dropped, and the development here seems fairly active, so what is an estimated timeframe for 9.0 roms to drop? Not looking for ETA, so much as a general (1 month, 2 month, 3 years). On a similar note, is it possible to root/magisk the stock 9.0 rom? I see custom kernels, so methinks it is, but I want to be sure before I take the dive..
And finally, aside from warranty issues (which I don't qualify for anyways as my P2XL is second hand, and no invoice...stupid Australia), why WOULDNT I want to root?
Thanks
Click to expand...
Click to collapse
No reason to not to root lol
Custom roms will come but slow
You can root pie as well with no problems
Cheers ?
Sent from my Google Pixel 2 XL using XDA Labs
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
AwkwardUberHero said:
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
Click to expand...
Click to collapse
Use this unofficial version of Magisk (1674) as opposed to the official (1671). https://forum.xda-developers.com/showpost.php?p=77240449&postcount=2832
Why? Some users are experiencing boot issues with the official. This fixes it
Thanks for that. I am going to bite the bullet and do it today.
AwkwardUberHero said:
I'm debating on taking the root plunge as well on my 2XL. Cannot decide either way. Not super familiar with ADB, but can read directions. Bricked my G2 back years ago, and had to reflash and such back to stock..Scary, but eventually got it to work.
Click to expand...
Click to collapse
Just did mine (took 5 minutes). I am pretty comfortable with this stuff so let me know if you need any help.
jewnersey said:
Just did mine (took 5 minutes). I am pretty comfortable with this stuff so let me know if you need any help.
Click to expand...
Click to collapse
Did you just follow the steps one by one and it worked? I'll be doing this on Mac. Could install a VM with Windows if it makes it any easier.
I'm on windows, but you should be fine on Mac after installing ADB. Mac instruction for doing that are in the first post.
After that just follow directions to unlock and then install TWRP (my preference) .
Save everything important to your PC because it will get wiped.
So for the last year and a half ever since my Galaxy S7 was stolen on the train I've been using an iPhone. Well that stopped working and I just bought a Pixel XL. So it's been a while.
Anyway the one nice thing about the Galaxy S7 was that it was virtually brickproof. No matter how bad you ****ed up flashing the wrong image or whatever you could always just fish the stock ROM and be ok.
Is the Google pixel the same? Or should I be extra careful when rooting and installing ROMs ?
Thanks
I don't know how reliable it is, but I've been able to un-fudge everything I've done to the pixel XL so far
You might look through the questions and answers section over the last week before deciding on a purchase. There are quite a few of us suffering from bootloops due to, apparently, hardware issues..
Well I ended up buying one but turned out to be retail and thus a Verizon version. Which wouldn't even matter if I could get the damn thing to connect to fastboot
I've recently rooted my phone and now I am questioning why I did it. The first phone I rooted was my Nexus One and I've been a member of this site since the release of the Galaxy S2 so I am no novice. It used to be a necessity to root for the increased control it gave, but now all I seem to be doing is finding solutions to get back functionality that I've lost through tripping Knox. Please, can anyone give me a reason or list the advantages of rooting the current generation of phones because I'm struggling to justify keeping the bootloader unlocked and not going back to stock?
No. I wouldn't... for you though the cat's already out of the bag.
If running on Pie I definitely wouldn't update to 10 or worse 11.
mckeowngoo said:
I've recently rooted my phone and now I am questioning why I did it. The first phone I rooted was my Nexus One and I've been a member of this site since the release of the Galaxy S2 so I am no novice. It used to be a necessity to root for the increased control it gave, but now all I seem to be doing is finding solutions to get back functionality that I've lost through tripping Knox. Please, can anyone give me a reason or list the advantages of rooting the current generation of phones because I'm struggling to justify keeping the bootloader unlocked and not going back to stock?
Click to expand...
Click to collapse
Like you, I've been rooting since my HTC-Hero way back in the early days of Android. It was necessary for better kernels, better battery life, better RAM and CPU management, better file systems (Early days of ARM and EXT4) and of course those cool themes and apps that only work with Root (Titanium Backup, Gosh I miss you!!). Not to mention what was my favorite, MIUI!
The last phone I rooted was the Nexus 6. It was a powerhouse! I still have it in a drawer full of old devices in my desk and miss it! Someone once told me when checking out my N6, "Your phone is like a muscle car!"
I miss rooting and I hate that carriers have locked the Bootloaders down. Android was founded on and was expanded by the Amateur Development community. Look up Cyanogen for details!.
I just bought my daughter this device outright - first, one I've ever bought that wasn't through my carrier and I'll be doing the same with the Pixel 6 for myself later this year which means I can finally go back to rooting and hopefully back to what earned me the RC title, but I also wonder, do I really NEED to root these??
My daughter isn't a power user. She's probably happy with whatever native settings and Samsung themes she can find on her own. My Pixel 4 XL has been great as is. so I applaud your question because I also wonder if rooting is still necessary or is it just a way to feel rebellious and outside the fray?
I also own a Pixel 4, bought to scratch an itch when I wanted to try out GrapheneOS.
I think I will go back to stock, which is sad as I enjoyed the process of modifying the phones software. If there was a net gain or increased functionality to keep the phone rooted, I would but unfortunately there isn't a compelling reason to keep the bootloader unlocked.
Am I wrong? Is the scene, at least for Samsung phones, dead and this forum obsolete?
Root is a must for me. Just being able to debloat. Either way I bought a unlock token
I understand the debloat of carriers useless apps, but since I found that ADB can basicly remove the programs I don't need root for that. But I still like root for change hosts files and such.