Database Info

[Q] deleted htc framework file and phone doesnot start

deleted htc framework file and phone doesnot start.
After rooted my htc One X. In the process of removing at&t crap ware I accidentally deleted something that said htc frame work.
From then on my phone would not start. I unlocked my phone as well. How ever I didnot have any custom ROM installed or didnot have any back up done.
When I tried to reboot my phone after deleting the htc frame work file, it would not start. HTC icon would show up and it would not go further.
These are the things I did.
1. I flashed CWM.
2.I flashed TWRP.
3.I finally flashed CWM. 5.8.3
Then I went to fastboot mode and
removed Dalvik Cache, Erased the sd card
and tried to 'mount usb storage' but it would say
"unable to open ums lunfile(no such file or directory)SD card space free:10169MB"
My phone though shows as a removable disk , when i click on the icon it would say " Please insert disk into removable disk." I tried to save a custom ROM on my memory card and flash it but my system doesnot detect my phone.
Can some one please help me?
Thank you.

HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.

Lock bootloader run ruu start over. Next time the very first thing you do is make a nandroid back up.

redpoint73 said:
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Thanks for the quick reply.
When I tried to mount my phone as usb it would not. I mentioned that as well.
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online. Without installing a custom ROM and run RUU , do you think my phone works
Adding a note to it. my phone is s-on and did not have android sdk installed on my machine. i tried all this using fastboot files and twrp img.
Thank You

in00b said:
When I tried to mount my phone as usb it would not.
Click to expand...
Click to collapse
You mentioned you tried to mount USB using fastboot (I've never mounted USB using fastboot, so I can't comment on that). Try mounting USB within TWRP, and see if that works. FYI, the USB mount feature in CWM does not work, and CWM does not really support our device, and has major issues. That's why its strongly recommended you use TWRP and not CWM.
in00b said:
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online.
Click to expand...
Click to collapse
Website seems to be too busy now. As long as its not 2.20, it should be okay. Normally, I would caution against randomly searching around the internet for things and flashing them, and instead getting them here instead. But briefmobile is Kenneth Penn's website, and he is a known developer on XDA.
in00b said:
Without installing a custom ROM and run RUU , do you think my phone works
Click to expand...
Click to collapse
You deleted part of the OS, so I'd say no. It doesn't boot does it? Then it doesn't work.
Also, please click "Thanks" to the post that help you.

the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?

in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
No, you can only have one recovery. Flash one, you overwrite whatever you had before.

in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
I'd stay away from CWM. I know it used to cause problems, but I don't know if it does anymore.
Most everybody here (in the One XL forums) prefer TWRP anyways.

Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You

in00b said:
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
Click to expand...
Click to collapse
Did you lock your bootloader before running the RUU?

Butters619 said:
Did you lock your bootloader before running the RUU?
Click to expand...
Click to collapse
nope my phone was boot loader unlocked and s-on.

in00b said:
nope my phone was boot loader unlocked and s-on.
Click to expand...
Click to collapse
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.

Butters619 said:
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Click to expand...
Click to collapse
thanks i will try unlocking my phone and get back to you.

in00b said:
how do i relock my phone.that doesnt turn on at all. all i see is htc screen and it wouldnt go any further.
Click to expand...
Click to collapse
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.

Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....

qwertyaas said:
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
Click to expand...
Click to collapse
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
But in almost every thread things have to be said 2-3 times which is ridiculous

Butters619 said:
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Click to expand...
Click to collapse
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.

in00b said:
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
Click to expand...
Click to collapse
See that thanks button. Go through this entire thread and press it for everyone who helped you (aka everyone). Especially gunny.

And remember, things that sound important (framework, build., etc...) typically are important random assassinations typically get the shooter in trouble

18th.abn said:
random assassinations typically get the shooter in trouble
Click to expand...
Click to collapse
lol
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Butters619 said:
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
Click to expand...
Click to collapse
Maybe he's more a fan of the Butters cartoon character than he is Totoro?

[Q] Please Help! Phone Bricked (Noob Problems)

Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!

Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app

luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.

Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!

fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.

Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!

fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.

Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?

fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.

Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again

fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?

Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.

fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.

Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?

fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?

Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!

fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.

Hard bricked OPO?

Hey,
i just re-rooted my One after updating to 38r some days ago, and as it booted up, i got the "audiofx has stopped" bug and the "CM Lockscreen has stopped" bug at the same time. i tried to reset with twrp, reflash the rom and whatnot. I also cant flash roms with toolkits as i can not unlock my Bootloader. Today i finally managed to install a modified 38r via USB Otg after some other rom installations failed (also with USB Otg). I'm all like "Hell Yeah, fvck yeah OnePlus support!" (I wrote to them some days ago but they have not replied). I euphorically booted up my device and waited until the cyanogenmod logo pops up. i waited all the time. And its in a Bootloop now. I tried resetting my device and reflashing the ROM but none works. Can anyone help me please?
Sorry for the typos, i got not much time right now so i had to type fast.
thanks in advance

Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon

as i can not unlock my Bootloader
Click to expand...
Click to collapse
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
also cant flash roms with toolkits
Click to expand...
Click to collapse
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.

d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Transmitted via Bacon

timmaaa said:
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Click to expand...
Click to collapse
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".

d4fseeker said:
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
Click to expand...
Click to collapse
Fair enough, although for someone who's inexperienced I think using the flashable version will be an easier and quicker solution.
Transmitted via Bacon

timmaaa said:
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
Click to expand...
Click to collapse
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.

try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15

Crime_Monkey said:
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
Click to expand...
Click to collapse
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.

d4fseeker said:
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
Click to expand...
Click to collapse
I installed twrp with the toolkit by @manudroid19 when my phone was still functionable.
And the toolkit says that my bootloader is locked and i cannot unlock it. Every time i try to unlock it with the toolkit when in fastboot mode, the phone just boots up to twrp.

Have you tried the instructions in this thread:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

r0ni3 said:
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I can not find the folder, with and without an OS installed.

Crime_Monkey said:
I can not find the folder, with and without an OS installed.
Click to expand...
Click to collapse
no folder ..
you just have to write that command

r0ni3 said:
no folder ..
you just have to write that command
Click to expand...
Click to collapse
I can't find this option in twrp either.

Crime_Monkey said:
I can't find this option in twrp either.
Click to expand...
Click to collapse
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15

r0ni3 said:
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.

Crime_Monkey said:
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Click to expand...
Click to collapse
installa a nightly...
and gapps

you can adb push roms in twrp, so you dont have to resort to otg.

Issues booting into recovery after trying to update to M

I was following this guide and after flashing the recovery, I seem to be unable to boot into the recovery mode. I can still boot into fastboot fine. I tried both TWRP 3.0.0 and the 20151227 experimental build mentioned in the guide.
I'm not sure what step I screwed up because none seemed to report an error while following that guide.
I ran into this thread where the OP seemed to maybe having the same issue and I waited at the logo for quite a while as suggested there.

search for the experimental twrp... you will find it here. only this one works with MM
http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229

el3c said:
search for the experimental twrp... you will find it here. only this one works with MM
http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
Click to expand...
Click to collapse
I tried that before posting but in case I missed something, I tried that again with no progress.
At this point I'd be happy just going back to android 5.x but I'm not sure where to start in terms of removing the mm blobs from the guide I linked and getting a recovery that will actually work.

RagingRoosevelt said:
I tried that before posting but in case I missed something, I tried that again with no progress.
At this point I'd be happy just going back to android 5.x but I'm not sure where to start in terms of removing the mm blobs from the guide I linked and getting a recovery that will actually work.
Click to expand...
Click to collapse
Have you unlocked your bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
then
fastboot flash recovery twrp-20151227-EXPERIMENTAL-shieldtablet-m.img
Click to expand...
Click to collapse
you find it here: http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
This is must work! I ve done this several times.
It is better to take this Guide...but use the TWRP from the link before: http://forum.xda-developers.com/shield-tablet/general/complete-guide-shield-tablet-k1-root-t3315965

el3c said:
Have you unlocked your bootloader?
then
you find it here: http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
This is must work! I ve done this several times.
It is better to take this Guide...but use the TWRP from the link before: http://forum.xda-developers.com/shield-tablet/general/complete-guide-shield-tablet-k1-root-t3315965
Click to expand...
Click to collapse
Yup, did both of those steps. What sort of output does fastboot give you when you flashed stuff? My working theory is that the fastboot client on the shield isn't performing the flash even though fastboot on my PC says that everything went OK.

el3c said:
Have you unlocked your bootloader?
then
you find it here: http://forum.xda-developers.com/showpost.php?p=64520513&postcount=229
This is must work! I ve done this several times.
It is better to take this Guide...but use the TWRP from the link before: http://forum.xda-developers.com/shield-tablet/general/complete-guide-shield-tablet-k1-root-t3315965
Click to expand...
Click to collapse
I ended up getting it fixed. It seems like it was an issue with the USB ports I tried. I plugged it into a different one and it seems to be working.

[Solution/Solved] Pixel Bootloop After Rooting Chainfire/Flashing boot-to-root.img

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/