yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] Archangel:
I was trying to update to TWRP RC1 from alpha 2 and I fastboot flashed the stock boot.img to both a and b then installed RC1, deleted the fstab-sailfish and then installed SU sr5 but it kept bootlooping back to recovery? Do you have to flash the flash-all right after fasbooting the stock boot image?
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
To update to RC1 from Alpha 2, you simply install RC1's EXE from within TWRP.

Flashing the stock boot.IMG's was an unecessary step unless you're missing something from your description of what you're doing.

I've never ever flashed the stock boot.img for any reason other than to un-fook something I fooked up.

The same goes for flashing it to A & B. Never once done that either.

Did you reboot back to TWRP after you installed it?

And then installed SR5 root?

Shouldn't really need to. But it doesn't make sense that you're bootlooping.
[Google Pixel XL Guides, News, & Discussion] Archangel:
Oh how I remember the good ol days of clockworkmod where things seemed so simple LOL. I read back in dee's troy explanation of TWRP and flashing the boot.img to both a and b partitions to avoid it booting back into recovery all the time. Well I had to restore a back up and thats exactly what happened. In RC1 I checked off system, data, boot, and vendor (all partitions no images) and the back up and restore went fine but it kept rebooting back into recovery? Now I am back on TWRP Alpha 2 cause RC1 is really wierd for me,,,I am trying to figure out what I am not doing that others are when they are saying they have backed up and restored so many times and I cant even get one to work?
[Google Pixel XL Guides, News, & Discussion] Nitemare3219:
I had a bootloop issue where my phone was going to stock recovery and showing "no command." I tried the flash-all.bat and it kept telling me the device had insufficient storage to transfer the .zip with all the main .img files (e.g. system, system_other) and would fail. I tried flashing the relevant .img's myself but failed that as well because there are no good instructions on what needs flashed (e.g. one website said to use "fastboot flash system system.img" when in reality the correct command seemed to be "fastboot flash system_a system.img").

At any rate, the ONLY thing that fixed my damn phone was reflashing the stock factory image with the Unified Toolkit. I think a guide on using that would be a lot easier than dealing with bull**** adb/fastboot issues by trying to do it yourself with those methods.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Hahah, CWM FTW.

I almost miss having to press the down arrow 50 times to get the option I wanted to select.

I felt so much in control. lol

That happened to me also on my first try. Which led to confusion about needing to back up the IMG's instead of partitions.

But after I restored to stock and then got RC1 running again, I tried the exact same backup and it restored/booted fine.

I'm not sure where you're at right now in your issues.

But it may be a good time to..

TWRP wipe the everythings!

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img (why not, can't hurt)

flash-all.bat the latest full factory image from Google

fastboot boot twrprc1.img

Install RC1 from within TWRP

Delete the fstab

Install RS5 superuser (or wait for RS6 to drop later today and not mess with fstab?)

Boot up & setup OS

TWRP nandroid your ish and back it up to PC.

TWRP nandroid your ish a second time and back it up to PC.

TWRP wipe the everythings.

Reboot to TWRP.

Restore one of the backups.

Test.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Just remembered something.

I think I had the bootloop back into TWRP on another occasion after screwing stuff up.

And then I flashed ElementalX kernel and suddenly I was booting into the OS again.

Not 100% sure. I break a lot of stuff on purpose.

I work from home and have a few minutes here and there to do what I want.
[Google Pixel XL Guides, News, & Discussion] cam30era:
Was your ADB and fastboot up to date?
[Google Pixel XL Guides, News, & Discussion] Nitemare3219:
Don't know and don't care. I've never had any notable issues because of ADB/fastboot versions since I've been flashing stuff since 2009. I've updated periodically for other reasons (like getting a new PC), but not because something wasn't working. I downloaded the latest minimal ADB/fastboot and that didn't fix anything either (was doing this at work, not at home where I know ADB was updated since I was trying to block Note7 packages). Point is, the Toolkit worked the 1st time with no issues. Half the instructions for things on the web are either dated/incorrect, or don't consider when **** goes wrong (like in my case of having insufficient storage for the flash-all.bat).
[Google Pixel XL Guides, News, & Discussion] jp712:
I too had the insufficient storage error when it was trying to update the image.

Turning off USB Debugging seems to have fixed it for me. Then just run the last step it failed on again.

fastboot update image-marlin-nmf26q.zip

Hope that helps...
[Google Pixel XL Guides, News, & Discussion] Nitemare3219:
I had a soft brick and even did a factory reset in the midst of all the issues. ADB/fastboot still never worked for flashing the entire 7.1.1 factory image.
[Google Pixel XL Guides, News, & Discussion] jp712:
Boot it back up and turn off USB Debugging, fixed the issue for me.
[Google Pixel XL Guides, News, & Discussion] MrMeek:
If you get in a soft brick like I was in,check Jcases PSA thread, you can run that to get out of it so you can actually get in your phone and turn on usb debugging to flash a stock rom.
[Google Pixel XL Guides, News, & Discussion] aholeinthewor1d:
Where is this thread idk why I don't see it

Edit: I'm retarded
[Google Pixel XL Guides, News, & Discussion] Paz9:
is it normal for fstab.marlin to appear again after installing supersu from zip?
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
yep
[Google Pixel XL Guides, News, & Discussion] Paz9:
:) thank you
[Google Pixel XL Guides, News, & Discussion] Paz9:
anyone know to to enter "service mode" on the pixel xl to view fast dormancy and to disable it. i remember my s6 had a dialler code.
[Google Pixel XL Guides, News, & Discussion] cam30era:
*#*#4636#*#*
[Google Pixel XL Guides, News, & Discussion] Paz9:
nothing about fast dormancy in there.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Updated OP for new SuperSU 2.79 and ElementalX 1.02 and also cleaned up the OP with

wraps.
Please let me know of any mistakes.
It's hard trying to keep such a long OP maintained without errors. :eek:

2.79 SuperSU does not require deleting fstab like 2.78 did.
Thanks, Chainfire & DeesTroy! :good:

Also added a link to download a modified flash-all.bat script with the "[B]-w[/B]" removed so it doesn't wipe your data.
http://www.filedropper.com/flash-all
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Updated OP for new superuser, kernel and January android image.

Cleaned a few things up.
[Google Pixel XL Guides, News, & Discussion] cam30era:
[MENTION=4274380]CZ Eddie[/MENTION],

Maybe update the OP with links to Google's ADB and fastboot instead of minimal?
[Google Pixel XL Guides, News, & Discussion] 557953:
Thanks for this guide, I just have a question, I have an EE Pixel XL so BL was unlockable originally (cheers Root Ninja) in the new Jan V update I downloaded (I'm in UK) when I unpacked "image-marlin-nmf26v.zip" I noticed there is a "bootloader-marlin-8996-012001-1611091517 .img" file which I don't see in the U update thats in the pictures of the guide, should I remove that before running the flash-all.bat? I don't wanna end up with a locked BL again, and if I remove it and need it I want a paperweight even less.

Thanks in advance people :)
[Google Pixel XL Guides, News, & Discussion] cam30era:
If your bootloader is already unlocked, it'll stay unlocked.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Will be adding the Google fastboot file download to the OP when I get a chance to verify it.

It is actually in the pics. Step 7B is where you'll see it.

Though the end of the filename got cut off.

I'll fix that for the February update pictures. :good:
[Google Pixel XL Guides, News, & Discussion] cam30era:
Here's a link to Google > https://plus.google.com/+ElliottHughes/posts/U3B6H3Sejvv
[Google Pixel XL Guides, News, & Discussion] old_fart:
Android Police ( 1/5/17 )

Google makes ADB, fastboot, and other platform tools available without full SDK or Android Studio download . . .

http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/

.

. .

. . .

Date stamp was newer . . . Well but, this version is the "same" version ( 1.0.36 ) as you point to in your OP . . . ;-p

Windows

Linux

Mac
[Google Pixel XL Guides, News, & Discussion] lupus2k:
My phone starts bootlooping and i not enabled the DEVELOPER SETTINGS (when the phone works). There is a way to use any fastboot command or i have a really expensive brick? :confused:

Thanks
[Google Pixel XL Guides, News, & Discussion] skulldreamz:
Hold down power and volume down until your phone boots into the bootloader. Then you can use any fastboot command you want.
[Google Pixel XL Guides, News, & Discussion] lupus2k:
No...i have bootloader locked and the command "fastboot oem unlock" is disables because i didn't enabled the USB DEBUGGING option when the phone worked...
[Google Pixel XL Guides, News, & Discussion] skulldreamz:
Do you have Windows or Linux?
[Google Pixel XL Guides, News, & Discussion] lupus2k:
I have OSX and Windows... On both some commands works but every command that writes get me "(bootloader) Please unlock device to enable this command."

Thanks
[Google Pixel XL Guides, News, & Discussion] skulldreamz:
Type fastboot oem -h
[Google Pixel XL Guides, News, & Discussion] lupus2k:
I got the standard help page...
[Google Pixel XL Guides, News, & Discussion] skulldreamz:
You have stock recovery then right?
[Google Pixel XL Guides, News, & Discussion] lupus2k:
If i select RECOVERY MODE take me to bootloop again...
[Google Pixel XL Guides, News, & Discussion] skulldreamz:
I'm talking to someone right now trying to get you straitened out...
[Google Pixel XL Guides, News, & Discussion] lupus2k:
I'm crossing my fingers :highfive:
[Google Pixel XL Guides, News, & Discussion] skulldreamz:
Call 1-855-836-3987 and a Google rep will help you out.
[Google Pixel XL Guides, News, & Discussion] lupus2k:
Calling right now....i'll let you know if i fixed this!

---------- Post added at 09:10 AM ---------- Previous post was at 08:48 AM ----------

The same...SEND US THE PHONE :eek:
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
****OP updated for February Google Updates images, Google's ADB/Fastboot files and a newer SuperSU and newer ElementalX kernel.
[Google Pixel XL Guides, News, & Discussion] Pøîñtßlåñk:
Worked perfectly. :laugh:
[Google Pixel XL Guides, News, & Discussion] Xirix12:
So I have run into an issue. No matter what factory image I flash I am shown numbers and letters in the recovery when trying to flash TWRP. This is after many attempts to flash the factory images (January and February). Not exactly sure what the problem is. I can boot into the device and even bootloader. Just not able to do much after that. Any help is appreciated.

Some additional information: I was on Purenexus and was going to install the recent update. I was not asked a pattern or anything when accessing TWRP. I wiped, flashed rom and flashed TWRP again. I remembered that the vendor also needed updating so I flashed that too. I did however click something wrong and it may have flashed the vendor image to another one of the two options I believe they were system and radio. I flashed vendor to the correct one after that and rebooted system. It would not boot at all, so I decided to just download the factory image and start over. I get it to boot into bootloader and flash-all.bat. I then do not boot directly into system. Just stays in bootloader. I then just scroll to power and boot up. I go through the prompts and sign in. Once signed in and ready I go into bootloader to flash TWRP it shows all files in numbers and letters like it is encrypted. I have tried January and February factory images. Hope there is something I did wrong that can easily be fixed. Thanks
[Google Pixel XL Guides, News, & Discussion] BladeRunner:
I'm not new to flashing, but I don't see a recovery.img in the factory firmware. Also how does one get it to flash the boot, system and recovery using the flash-all.bat? All I get is "No boot.sig" etc. I'm trying to return to stock to take the 7.1.2 beta update. I run the flash all and the bootloader and modem flash ok, but nothing else flashes and I still have TWRP and am still rooted. I have a 128gb pixel on 7.1.1, rooted with the ElementalX kernel.
[Google Pixel XL Guides, News, & Discussion] mikaole:
Why do you want to take the ota?

Just flash the beta via fastboot.

And your problem should likely be out of date adb and fastboot driver.
[Google Pixel XL Guides, News, & Discussion] BladeRunner:
I don't have a problem flashing with fastboot, just that pixel has way more stuff than I am used to, and, like I said I don't even see a recovery file in there so Im not entirely clear on WHAT to flash.
[Google Pixel XL Guides, News, & Discussion] BladeRunner:
Got it. I don't think I was patient enough. I tried again and let it run and it flashed fine. I'm still curious if the there is a way to flash just the stock recovery partition though?

---------- Post added at 12:15 PM ---------- Previous post was at 12:12 PM ----------

OK, got that figured out too. Recovery is now part of the boot.img. Mind.Blown
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
TWRP is unable to decrypt.

I get this once in awhile.

Especially when I 100% wipe both A & B partitions or screw around too much.

Once I restore to stock and then flash TWRP and it fails to decrypt, I just end up restoring to stock again (and make sure I leave the -w in the script).

Then try TWRP again.

I've never had to do it more than twice to get it to decrypt properly.

Sometimes just rebooting to recovery a couple times works too.

You might also try flashing boot.img to A & B partitions, then reflash TWRP again.

Correct, there is no recovery.img for Pixels.
[Google Pixel XL Guides, News, & Discussion] Xirix12:
So for my issue, I tried about 10 times (no exaggeration). I just gave up and locked the bootloader. I tried all the things I could find and everything ended up with TWRP unable to decrypt. I figured I'd lock and attempt to quickly relock (I knew going with that could and most likely would result in not being able to unlock it again.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Weird.

Did you try a different version of TWRP?

Like start with fastbooting an older one.

Then if it works, flash the newest one?

Either way, you might want to post about it in the TWRP thread to get up to date info, especially since you're on Verizon and IDK anything about Verizon and its lock situation.
[Google Pixel XL Guides, News, & Discussion] Xirix12:
I tried using Alpha 2, which was the other one I has used previously too, and then permanently changed it to RC1. Either one would not decrypt. Yea, as far as I know I am "screwed" there is no way to get Depixl8 to work with 7.1.1. I will look though. Thanks.
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
You have a Verizon phone on 7.1.1? Yea, you can not unlock.
[Google Pixel XL Guides, News, & Discussion] Xirix12:
I didn't say I could. In the post I replied to he said to look. He might be talking about something else since he said TWRP. I am not too concerned at this point. I just wish I could findout what went wrong and how that can be remedied in the state I was in. Most of the posts I visited had the same issue the TWRP not decrypting data and then they got it to work. That was not the case for me, unfortunately.
[Google Pixel XL Guides, News, & Discussion] djRamage:
sticky this!
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
OP Updated for March 2017 Google Security updates images.
[Google Pixel XL Guides, News, & Discussion] stm8:
Edit: Sorry, I must have a reading disability!

Thanks again for the guide and keeping it updated.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Thank you, I did forget to add the March -w modded flash-all.bat.

It's updated now. :good:
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
I wouldn't be surprised if both flash all's were identical though.
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Different. The line for the bootloader changes with each bootloader change, and the radio.....
[Google Pixel XL Guides, News, & Discussion] Reitaz:
Sorry im kinda new into this. Do I need to wipe both slot A and B before flashing the stock image if I want it to be completely stock? or maybe flash-all.bat already does the job?
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Flashall will take care of everything for you
[Google Pixel XL Guides, News, & Discussion] ffchampmt:
It appears​ the flash all script is written for the March "C" release which I thought was Rodgers specific?
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
I thought I uploaded the "B" but just in case I didn't, I have now re-uploaded "B". :good:
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
It is not necessary but I do exactly this in TWRP. :good:

I wipe dalvik, system, data and internal SD on A & B.

It's completely overkill/unnecessary though.

I like overkill myself. :laugh:
[Google Pixel XL Guides, News, & Discussion] mikaole:
That the same with me still going the 3 times Wipe that you needed in the first days of cm recovery :)

Better too much than one step too little
[Google Pixel XL Guides, News, & Discussion] djforbes7:
Elemental X

Do I have to do the Elemental X to successfully root? The only reason I want to root is to activate hotspot.
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
You can root with any kernel. Boot to twrp and install SU.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Nope, kernal is optional. Don't need kernel at all for root to work.
[Google Pixel XL Guides, News, & Discussion] djRamage:
Thanks for the guide! Using it to update since the OTA won't work with the SafetyNet modded kernel.

FYI, I almost found out the hard way but very glad I checked, the modded flashall file you have linked DOES STILL include the -w so it will wipe the phone.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Ugh, dangit.

Re-uploaded again and verified -w removed and it's the B.
[Google Pixel XL Guides, News, & Discussion] Pøîñtßlåñk:
Notice a problem using -w in the flash all. When i boot for the first time all my apps start crashing. I let it settle and tried to update them via google store but most of my apps would not open or crash. Forced me to start from fresh.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
You used the unmodified flash-all, correct? And apps started crashing on the first boot?

Sounds like a system wipe didn't go through properly or the flash was bad?
[Google Pixel XL Guides, News, & Discussion] burnface:
[Solved] Nevermind, I followed this, and then went back to bootloader and did a fastboot flashing lock, and all is good.

So I'm on Verizon, rooted and unlocked bootloader, but no TWRP, Kernels, or ROMs.. if I want to go all the way back to stock, can I safely follow this still?

Thanks!

[edit] I'd like to relock my bootloader as well (trading for a normal Pixel), what do I have to do in addition to these steps?
[Google Pixel XL Guides, News, & Discussion] ThePieMonster:
So no wiping dalvik cache during the TWRP process?
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
For what, installing SuperSU or the kernel?

Sure, it doesn't hurt to wipe cache.

Most of those zips will wipe it on their own too.

It's not critical either way.
[Google Pixel XL Guides, News, & Discussion] ThePieMonster:
True. I ended up just doing it once when I was done installing everything. Works either way I guess.
[Google Pixel XL Guides, News, & Discussion] nikpoth:
Fantastic guide. would lock and unlock bootloader in the first post?

Thank you!
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
I could add that but I don't want to stretch this thread more than it is and there are already other threads out there about locking/unlocking.

It would be rude for me to duplicate those threads.

IMO.
[Google Pixel XL Guides, News, & Discussion] jreink01:
In the OP, is that modified allflashbat already without the -w? I need to use that but I don't want to wipe my data? This is my first time flashing a bat file so sorry for not knowing this.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
yes
[Google Pixel XL Guides, News, & Discussion] jreink01:
I have been following that step by step guide and am ready to go into fastboot to try this. Now, will this take me to the state it was in before all this happened, but with my settings, data, and apps, right?

When this is done, I will have to reroot and install twrp again??

I would like to install to install pure nexus, which vendor image will I need then??

and is the procedure:

do a wipe

flash pure nexus and twrp again

install vendor image, what file that may be

reboot

Ok, its back to factory, I was hoping to avoid doing this as I lost all my data, settings, root, etc.

Thanks for the help though. Is there anyway I can restore my stock backup without going through all this hassle again?

---------- Post added at 11:55 PM ---------- Previous post was at 11:27 PM ----------

Doing your guide and using your flash all bat, Was that suppose to erase everything I had on my internal storage??? Because it erased everything!! All my songs, ringtones, my backup, all the data in titanimum backup!!! Everything I didn't want it to do, it did!!! I am not happy!!

---------- Post added 25th March 2017 at 12:02 AM ---------- Previous post was 24th March 2017 at 11:55 PM ----------

I thought using your bat and the procedure you outlined was supposed to keep data, apps, settings, and ESPECIALLY the files on the internal???
[Google Pixel XL Guides, News, & Discussion] TonikJDK:
Sorry for what happened to you but I just checked the file that CZ posted and the flashall bat file is absolutely correct. He removed the -w exactly as he should have. His bat file did not wipe your data.

I would bet you accidentally used the flashall bat file that you got when you downloaded the full image.
[Google Pixel XL Guides, News, & Discussion] CZ Eddie:
Sorry to hear you had some troubles.

Yes, if you follow my directions step by step and substitute the stock flash-all with the modded flash-all, then you are not supposed to lose any data.

I suspect you used the wrong flash-all or something else went wonky.

Did you save the flash-all command line output so we can analyze to see what happened?