yeah, I wasnt gonna go right to 7.1.1. anyways.
weird that my current firmware doesn't show up on any lists of existing firmware for the Marlin
weird that my current firmware doesn't show up on any lists of existing firmware for the Marlin
Yeah. Because it was a test device it had a version somewhere in-between the first officially released images. Probably why you also didn't receive any automatic updates. Or the setting was unchecked in dev settings. Either way I bet once you are on the official image you will start to be updated automatically.yeah, I wasnt gonna go right to 7.1.1. anyways.
weird that my current firmware doesn't show up on any lists of existing firmware for the Marlin
When i search in google for "android factory images pixel" it comes up right away. Download packages and instructions. Flashing a factory image does wipe your data, unless you edit the factory image flashing script ( .bat file for Windows, .sh for Mac/Linux) and take out the "-w" tag. "W" is for WIPE.I am coming from long term usage of Samsung phones, so have no idea really, and I don't like OTA methods, I always flash full firmware, after a full wipe. So is there a repository for these releases, from where I can download the full firmware and flash via ADB or something?
Just use a factory image. If you don't want to lose data remove -w flag from flash script. Locking bootloader wipes the device though. So I suppose data doesn't matter if you are re locking.Will adb sideloading Ota restore my phone to stock? And I'm able to relock bootloader after that?
Really? No other way to update while keeping both root and data?You must lose root but you can preserve data. One method is running flash-all script of the 7.1.1 factory image, with -w removed from the script or bat. Removing -w prevents data from wiping.
You can reroot afterward.
Sent from my sailfish using XDA Labs
It takes 2 minutes to boot into twrp install SuperSU sr4 or sr5. Really there is no other way than that...Really? No other way to update while keeping both root and data?
Here are excellent directions for you written by @micmarsJust out of curiosity can you flash the newest version of twrp without adb? I'm unlocked bootloader on Verizon and I've been keeping up with the twrp thread but I'm not familiar at all with adb. It took me awhile just to get unlocked. Mainly just getting adb installed and everything in the right place.
Get a phone that runs Gingerbread.. awwis there anyway or a mod to get menu button for navbar or long press recents for menu? this is driving me nuts lol. thx in advance
I actuly have had a physical menu button on Nov bar wit using cyanide rom and mostly broken rom. I'm still using broken rom on my nexus 6p and nexus 6. just not on pixel xl. I miss it lolGet a phone that runs Gingerbread.. aww
I get your gripe, but persistent menu button is no longer standard design. Even on 6.0.1 ROMs on Nexus 5, persistent menu button mods didn't always work. It would either not work or open the menu from another place, the default place..because it isn't design.
Instead of menu button, look for 3 dots. Long press something. Press and swipe.
I used to miss it. I agree if the app needs a menu, it should be easy to use.
Sent from my sailfish using XDA Labs
I would try doing the opposite.. updating your SDK and uninstall minimal.. I'm not sure it's been updated for 7.1.1. It's also been the most common issue with folks trying to use it.Lovely. Just got my PXL 128GB yesterday and I have been screwing around just to check it out before I unlock the bootloader and root it. I downloaded everything I that I would need (which isn't much) and attempted to use dePixel8 which kept failing. I noticed that the screen would shut off before it would attempt to boot into the bootloader. Perhaps it's some Verizon attempt at sabotaging the process. Idk but by manually booting into the bootloader at the right time I was able to get it to work.
Okay. Success. I then was looking at downloading the latest image file when it dawned on me that I should be able to take the OTA that's waiting in my notifications. Again, success and now time for rooting. Need I say more? I used Chainfire's Root for Pixel (XL)/SuperSU v2.78 SR2 from October 29yh. Smfh ? Now it won't boot up and even when I try to flash the factory image NMF260 it fails.
How stupid is that? I should have known better but I was somewhat preoccupied with binge watching some shows at the same time. My SDK was pretty outdated (I think v1.16) so I completely uninstalled it and installed Minimal ADB & Fastboot but flashing the factory image still fails.
The PXL acts like it wants to start but it's stuck at the boot animation and never makes it into the OS. Anyone have any ideas??
![]()
Sent from my SM-G935V using Tapatalk
With the new partition layout it's taking some time to make tools like TWRP and SuperSU work as intended. Once all the kinks are ironed out and ROM zips can be flashed easily, development will take off I'm sure. I know beanstown has a Pixel so we may see some pure nexus love eventually.I wasn't sure where to ask this, so I figured this thread would be a safe start. What's up with ROM development? There's only one custom ROM as far as I can tell, which I find very surprising. Is the phone still too new?