Related
Problem with the ROM"Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras"
Hello, this is the first topic i write on XDA. I have a huge problem with the ROM called "Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras" uploaded by kibmcz
I have made a mistake, i forgot to install the file for root and now i do not have root, i can not connect my nexus s with the computer and i can not get on my Clockworkmod recovery to change ROM. I don't know what to do. Please help me to change this ROM!
You should still be able to boot into the bootloader (vol up + pwr). You can then flash CWM again via fastboot.
chronophase1 said:
You should still be able to boot into the bootloader (vol up + pwr). You can then flash CWM again via fastboot.
Click to expand...
Click to collapse
How can i flash CWM via fastboot? Can you give me directions please?
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.[/QUOTE]
Thanks a lot my friend, i hope that i won't have any problem to connect my nexus s with the PC because now i have due to this ROM..
Its not the roms fault. The point of a stock unmodified ROM is simple. To be a stock ROM unmodified ROM
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.[/QUOTE]
My friend i still can not connect my phone with the computer. So i can't follow these directions.
albundy2010 said:
Its not the roms fault. The point of a stock unmodified ROM is simple. To be a stock ROM unmodified ROM
Click to expand...
Click to collapse
But now unfortunately i can not connect my phone with the computer and flash recovery
error?
ironia. said:
error?
Click to expand...
Click to collapse
Yes..
christoscy said:
Yes..
Click to expand...
Click to collapse
And what error? That would be handy to know... if it's the lack of drivers just install PDAnet and follow the instructions, it will install the drivers for the Nexus S.
DeuXGod said:
And what error? That would be handy to know... if it's the lack of drivers just install PDAnet and follow the instructions, it will install the drivers for the Nexus S.
Click to expand...
Click to collapse
I have installed them but it still does not recognise my Nexus S. And it doesn't show me Android ADB Interface in device manager.
christoscy said:
I have installed them but it still does not recognise my Nexus S. And it doesn't show me Android ADB Interface in device manager.
Click to expand...
Click to collapse
With your phone up and running normally and android debugging on, go to cmd. type adb devices does it show? Just wondering.
jayjay3333 said:
With your phone up and running normally and android debugging on, go to cmd. type adb devices does it show? Just wondering.
Click to expand...
Click to collapse
No it doesn't show..
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
devcager said:
Hi guys,
I run rooted unlocked Nexus 5 with CM11. I wanted to update the ROM but it failed - I read a bit and found out that it is due to old bootloader version. I would like to update it but I'm not a friend with ADB and stuff.... It would be great to use the most easiest way. I got OTA update notification but have no idea what it does - will it unroot the phone? will I lose CM11 ROM? Just trying to figure out what backups and steps shall I do to update my ROM. How shall I continue from here?
Thanks a bunch!
Click to expand...
Click to collapse
Attempting to take the OTA will fail.
Download the factory image and extract bootloader-hammerhead-hhz11k.img
Boot your device into bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
vin4yak said:
You have a custom recovery installed, right? Flash the bootloader zip via recovery. However, you need to get familiar with adb/fastboot as you're gonna need them if you ever find yourself in a tight situation to fix your device.
Open the "must read" thread linked in my signature and find the thread which has all the info about adb and fastboot.
Click to expand...
Click to collapse
Thank you! I get it about ADB, I had to solve one my problem in the past via ADB. Anyway, I just need to find the 4.4.4 bootloader in ZIP (or probalby .img will work too?) and flash it? That's it? Does it wipe my phone or something?
You just need to flash the IMG via fastboot, no wiping required!
EddyOS said:
You just need to flash the IMG via fastboot, no wiping required!
Click to expand...
Click to collapse
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
You don't need to. Just boot into fastboot, connect to PC, fastboot flash bootloader name_of_file.img, reboot, done
it's easy you must become familiar with fastboot and add the second you aren't it will come back to haunt you
Sent from my Nexus 5 using Tapatalk
devcager said:
Alright. One more thing. Is it possible to convert the IMG file I have into zip to be able to flash it in TWRP?
EDIT: I found that Nexus Toolbox for my 5 has the option to flash the bootloader image so I will try this variant.
Click to expand...
Click to collapse
so you learned nothing. awesome.
Zepius said:
so you learned nothing. awesome.
Click to expand...
Click to collapse
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
Brick waiting to happen.
Add to ignore list
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
I'm still waiting for someone to make a thread saying their device is "bricked because flashed fastboot to adb using bootloader while in recovery with x toolkit"
I have searched and can't find out anything about this, but for some reason I can flash recovery-clockwork-6.0.4.5-hammerhead.img through fastboot and then get into CM recovery. However, if I leave recovery and try to boot into it again, I get the dead droid picture. I can flash CM again and it'll work, but again, for a single use. I've never had this problem before on any Droid I've owned and I can't seem to find anyone dealing with it in this forum. Any help would be greatly appreciated.
No this phone is not rooted. I have unsuccessfully attempted this with CM (upon exiting recovery mode, you are prompted to root your phone if it hasn't been rooted).
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
You should also search the rules and list in he correct forum. This is not for questions only development
Sent from my Nexus 5 using XDA Free mobile app
also, clockwork mod recovery is long discontinued and provides no support anymore.
EddyOS said:
It sounds like you're using 'fastboot boot recovery.img' as opposed to 'fastboot flash recovery recovery.img'
Click to expand...
Click to collapse
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
strakajagr said:
First of all, sorry about the wrong forum. My bad.
Secondly, I used flash recovery as my fastboot command. I've done it a few times now. It just won't stick.
Click to expand...
Click to collapse
In any case, I can flash something else since CM is no longer supported. Thanks.
strakajagr said:
In any case, I can flash something else since CM is no longer supported. Thanks.
Click to expand...
Click to collapse
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try locking the bootloader and rebooting. Does it stay locked? Or is it still unlocked? You may have a bad eMMC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
How do I go about locking the bootloader after it's unlocked?
strakajagr said:
How do I go about locking the bootloader after it's unlocked?
Click to expand...
Click to collapse
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
BirchBarlow said:
First of all dump CWM. As another poster said, it's outdated and no longer supported. Get TWRP.
Second, don't use auto-root, it can be problematic. If you want to root, do so by flashing the latest SuperSU binary in TWRP.
Click to expand...
Click to collapse
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
strakajagr said:
Fair enough. I actually installed CM instead of TWRP on the advice of a friend. I use TWRP on my tablet. I installed the latest SuperSU via CM and it accomplished nothing. That said I can go ahead and put TWRP on it and give it another shot.
Is there a TWRP img that I can use for flash recovery? Also, can I flash a recovery over another?
Click to expand...
Click to collapse
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
simms22 said:
twrp for the n5 http://teamw.in/project/twrp2/205 and yes, you can flash another recovery right over.
Click to expand...
Click to collapse
Word. Thanks.
Next order of business is figuring why there is so much lag when I text/gchat in 5.0. This is the whole reason I got into this mess. I couldn't wait 3 more weeks. Sadly, when I type, the keyboard freezes constantly. I figure I'll install a recovery mode correctly and then try to tackle that problem.
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/