Database Info

Bricked HTC ONE X AT&T

I checked all the other bricked threads and none have the same problem as me.
My HTC ONE X will not boot and or charge. I cannot get access to the bootloader or recovery.
My HTC ONE X had it's bootloader unlocked via the rogers htc-dev method. I also installed clockwork recovery. It is rooted also but you prob figured that already...
I pulled a bonehead move by flashing the MIUI rom the international one x by changing the update script to flash onto my phone. After it flashed it looked like it worked. When I left recovery and shut the phone off it would not turn back on.
I called AT&T they said they will switch it for me when they get a shipment but I want to keep this phone because the boatloader is unlocked and they might patch the rogers method.
Thanks in advanced.
P.S. I know how to use adb and other tools such as RUU and they did not work.

Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.

Ouch.... Another loss for htc sales
Sent from my HTC One X using xda premium

you cant get to hboot? 0.o

First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras

Reply
equlizer said:
Have you tried holding the power button for 10 seconds to reset it? You should see the 3 lights below flashing.
Click to expand...
Click to collapse
No nothing happens even with the charging adapter plugged in.
kevina90 said:
you cant get to hboot? 0.o
Click to expand...
Click to collapse
Nope

sassafras_ said:
First of all, you should be able to get to H-Boot by holding volume down when turning it on.
Second of all, this is why they lock the bootloader in the first place.
-sassafras
Click to expand...
Click to collapse
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.

jfn0802 said:
H-Boot key combo is not working.
I have been flashing roms since the samsung moment, I built and modified roms on my EVO and ported roms from other phones to the EVO. I always had recovery to fall back onto to get my phone booting again. Even when I had the Xperia Play that required a PC to boot recovery I was still able to get the phone to work. This phone is strange that is will not even turn onto H-boot/Bootloader.
Click to expand...
Click to collapse
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.

gunnyman said:
I like to play with my phones and this one is so finicky I'm scared to do too much.
I bricked one myself.
Click to expand...
Click to collapse
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.

And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2

jfn0802 said:
Im glad I have my iPhone to fall back on but it is really annoying that I cannot even get the bootloader to load. I only had it 3 days and already broke it.
Thank God the dude at AT&T cannot get into the bootloader also to see that is was tampered with so they are giving me a replacement.
Click to expand...
Click to collapse
Where do they have them in stock? I need to replace mine (screen issue) and can't find any around here.

powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+ 1
Sent from my HTC One X using xda premium

powerwagon said:
And people wonder why at&t locks their phones down. I'm guessing you just told them "my phone broke...I have no idea what happened". Just lovely.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
+2
Honestly, not trying to call you stupid or something, but did you really think it was going to run on this phone when it was meant for another one? The GPU and CPU are completely different...
Anyway, I'm glad AT&T is replacing it for you. Hopefully if someone else bricks the same way then they will be able to get a replacement as well.

so you are smart enough to use adb, an RUU, unlock your bootloader, root, flash roms.......but you aren't smart enough to see the hundreds of posts saying that the international roms don't work on our phones??

lol

Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?

Just pull the batte..... oh

jmattp said:
Just pull the batte..... oh
Click to expand...
Click to collapse
+1 for when I drowned my first one and it was stuck in a boot loop. I know it could have been saved if the battery would have been taken out.
Sent from my HTC One X

modest_mandroid said:
Coming from a phone that is virtually unbrickable (Captivate), I'm quite curious about how you managed to get it into this state. What exactly did you flash? Did the package contain both the system image and bootloaders for the tegra3 one x?
Click to expand...
Click to collapse
My EVO was unbrickable too, I flashed a rom that was designed for the international version. It only contained system and other basic rom stuff, nothing that was crazy.

No idea why you wouldn't be able to boot into recovery then. I hope all HTC handsets aren't like this..
Sent from my SGH-I897 using XDA

Well crap... I have a hard brick

Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!

Time to get your story straight.... "I just turned it off and it won't turn back on??? Maybe my chargers broken?"
Sent from my SCH-I535 using xda app-developers app

dushotgun said:
Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!
Click to expand...
Click to collapse
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out

Wait you tried to unzip the kernel in your pc? For what exactly? How did you flashed it back unzipped?
VERIZON GALAXY S 3

jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?

dushotgun said:
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?
Click to expand...
Click to collapse
You can try a USB Jig to force your phone into Download mode, but if it's truly hardbricked then JTAG or getting a replacement are your only options.

I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?

Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
we're only human if i had this phone and saw this unlocked bootloader i would get excited about it as well lol i feel for the man/woman

Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.

dushotgun said:
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.
Click to expand...
Click to collapse
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help

jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Sucks, OP.
And don't even bother writing Adam. I don't know him, but I read his threads. He just had a major accomplishment (with help) and he will probably not even respond. Let him have his day/peace. He earned it. You admit that you jumped the gun.
Sent from my SCH-I535 using Tapatalk 2

Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Ohhh..c'monnnn- he/she was a Droid X user. As a fellow X2 encrypted bootloader ****ing never unlocked I was excited as **** about it being cracked too.
I'm not ****ing with my kernel or nothing.. but.. I couldn't resist. Been on lock down for 2 years- pre ordered the phone and come to find out they locked this ****er too.
Don't be so hard on the guy/gal.. :angel:

Coderedpl said:
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help
Click to expand...
Click to collapse
I sent him a message but no response yet. I tried that and I still get nothing thanks though. I've read every page of the bootloader research by adam I saw this on his original post:
"op5= aboot
This block is signed by Samsung, we will not be able to modify it
This block contains HTML information. It would appear that it is possible to put the device into a mode where it will provide a webserver which displays state information.
This block appears to be a complete operating system
This block contains the Loke Daemon which communicates with Odin3."
I take this to mean there is no way for me to communicate with odin now and jig wouldn't be able to force it into odin either since I overwrote the 0p5 block. I guess thats it since I don't have a jtag set up.

Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest

You flashed the kernel to the aboot partition, most likely meaning no booty booty to get into a state (download mode) where you can ODIN to stock. That being said, looks like you'll be JTAGing in your near future. Curious about prices, if you do it!

ooofest said:
Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest
Click to expand...
Click to collapse
It's $60
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

ooofest said:
Have you considered inquiring about JTAG rates from these folks?
- ooofest
Click to expand...
Click to collapse
Thanks for the link, it looks like thats my only option for getting it fixed.

This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.

JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
It will and it will ENJOY it.

JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
dd = disk destroyer :laugh:

So did I just brick my phone?

Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):

XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone

That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.

XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.

Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?

XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader

Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.

XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped

I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..

Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash

It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here

Glad to hear its working

Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.

mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2

mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.

superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"

please
how did you fix your phone i almost have same problem

He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks

Pixel XL Verizon bricking problems.

I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Edit- I'm on stock Android 7.1.1 and not rooted.

Timtube said:
I'm currently on my 4th replacement from Verizon. Everytime the phone has either went into an endless bootloader loop where clicking start takes me back to the bootloader and when going to recovery it says "failed to boot to recovery" or turned off and wouldn't turn back on and essentially becomes a bricked phone. Is there anyone else with this problem?
Click to expand...
Click to collapse
Did it work in the Verizon store? I've perhaps seen this once or twice but a replacement device usually worked. But 4 devices? That just doesn't seem real. Not that you're making it up but you need to explain what you are doing before the device goes into a boot loop. Worst case scenario, go to a store and make sure the phone works before you leave.

Weird sounds like you are trying to use depixel8 on an unsupported firmware? And you are bootlooping the phone ?

happened to me on my first device, partly why i havent SU or TWRP yet....just unlocked for future fun...
Mine bricked inbetween twrp and SU....but im sure i messed up somewhere. TWRP worked but as soon as i did SU, it all went wrong for me.....Figured id wait to more stable stuff is out, before messing around again.
mine did the same thing as what your describing...
peace
byte

I did not unlock the bootloader. I am not rooted. I am using stock Verizon Pixel XL 7.1.1.

well that changes everything, sounds like just bad luck dude

bytethegroove said:
well that changes everything, sounds like just bad luck dude
Click to expand...
Click to collapse
I know it sucks. I really like the phone when it works.

I think i killed my device

So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?

-MightyMouse- said:
So its been a while since I've been to xda so I hope I'm posting this in the right section.
Just so you know, I realize that what I did I will probably never be able to fix, I just want to make sure before I go before google on my knees and beg for mercy. I'm also aware that what I did is so stupid and unforgivable that I should never be allowed to root a device ever again. With that out of the way, here is my problem.
I just had my pixel replaced after my previous one had hardware problems, that are irreverent to this topic. I was setting it up to be my daily driver again, so I unlocked the bootloader, rooted it, loaded a few systemUI mods and the elementalx kernel. I had it working really well, but one thing was bugging me. That stupid notification that you get every time you boot up with the bootloader unlocked. I hated it. I got to thinking about it today, and I thought "Could it be possible to relock the bootloader with the changes that I made and have it still work?" I was thinking that once the mods were put in, it shouldn't matter whether or not the bootloader was unlocked or not cause the changes were already made. So I did the unthinkable and relocked my bootloader after I did all the stuff listed above.
So yes I major bricked my device by doing this, and yes I'm a major idiot for thinking that locking the bootloader was an OK thing to do. I can still get into fastboot mode, but thats it. When I try to boot into the system, it flashes the splash screen for about .5 seconds then goes black for 2 seconds then repeats. It does the same thing in recovery mode so adb side loading firmware is out of the question. I can't use fastboot boot whatever.img cause the bootloader is locked. I can't fastboot wipe userdata or mess with the system in any way via fastboot. And to top it all off, I cant reunlock the bootloader because it requires that an option be checked in the system that I now can't boot into.
This is a last ditch effort to see if I can fix this device myself, or if I need to go to google and pray they let me rma my device a second time
Any Ideas?
Click to expand...
Click to collapse
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.

-MightyMouse- said:
Any Ideas?
Click to expand...
Click to collapse
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?

quinejh said:
Well I'm not sure of this, but can't you unlock your bootloader through adb? If so then just flash the stock image.. I also saw a post somewhere about restoring your phone with a locked bootloader. Again this is just a suggestion but worth looking into.
Click to expand...
Click to collapse
Thanks for answering. I had looked into this, but the only way that you could do that is adb sideloading an ota from google. That can only be done by the recovery which is now borked.
bobby janow said:
I'll not chastise you for what you did, I've locked the bl after making changes too although I never did care about the splash screen. I just don't look at it after a reboot, hold it until it vibrates and then log in. But I understand you not liking is since I've seen other posts about trying to get rid of it. But... your only mistake was flipping the OEM unlock switch. You could have relocked the bl with that switch still enabled and not have the splash screen any longer.
So at this point you have to beg for a replacement. I don't think they'll give you a hard time about it if you're honest as you were here. You might get some suggestions from others so good luck. You did try to factory reset in recovery right? Oh just looked and you can't get into recovery. What happens when you try from bl menu? You don't even see the android little guy saying "no command"?
Click to expand...
Click to collapse
What makes me really mad is that I never disabled OEM unlock. That being said, I did see that is was disabled in settings and didn't think anything of it. I can't get into recovery at all, even through the bootloader. My guess is I borked the image that the recovery was put on as well as the system and probably a couple others. Something I know I could fix if the boot loader wasn't locked. Well I think I will get the ball rolling on an RMA then.

@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.

bobby janow said:
@-MightyMouse- When you have bootloader unlocked the option is grayed out and thereby disabled. But it does say bootloader is already unlocked so no action is needed. If you didn't switch it back over then there really is no reason that it should be disabled in the settings. When did you see it disabled if you can't get into the system? And what happens when you type the unlock command from bootloader menu? I'm locked but I think it's something like fastboot oem unlock or maybe it's changed. What does the screen say? I'm sure you tried it but I'm just curious.
Click to expand...
Click to collapse
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.

-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
Ok cool. Good luck.
Sent from my Pixel using XDA-Developers Legacy app

-MightyMouse- said:
That was the first thing I tried. I forget what it said, but I do remember that it wouldn't let me. No matter, I already got it RMA'ed but have to wait till Monday to ship it off.
Click to expand...
Click to collapse
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.

NoobInToto said:
So, what error shows up when you try - fastboot flashing unlock ?
After you somehow manage to unlock BL, you could try using the flash-all.bat script to quickly begin to push the images....
Edit: nvm. I see you have gone through a RMA again.
Click to expand...
Click to collapse
The error was something like option unavailable. Went through the RMA process which was surprisingly good. Every time I've gone through it, they never ask more than one or two questions before they ask for my imei and tell me that my device could be replaced, which is great, because if I can't fix it, it just needs to be replaced anyways. In other news I got my third pixel just a couple hours ago so hopefully this one lasts me longer than a day.