Database Info

[Q] NEXUS 5 BRICKED TRYING TO ROOT WITH CF AutoRoot. HELP!?

Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.

Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?

abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot

Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.

abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?

Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?

abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?

Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.

abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!

Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.

abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.

pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.

Would opening the command prompt window with administrative rights make a difference? Worth a shot.

Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.

Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.

It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.

Nexus 5 won't prompt for decrypt on boot / TWRP fails to decrypt

So I think I am screwed here but was wondering if anyone has run into similar issue. I was running SlimKat and had the data encrypted and I used BootUnlocker to relock the bootloader after I flashed TWRP a few months back. Been working fine for a couple weeks then yesterday I pull my phone out my pocket and it looks like it factory reset prompting to input all my info. So I reboot the phone thinking could be fluke and it doesnt prompt me for decyption password and again boots to setup screen. If you do login you cannot access the internal storage and there is no data connection. So I rebooted into TWRP and it prompts for decryption password only its not working. If I put in wrong password it comes back immediately that it failed. If I try correct password it tries for 30 - 45 seconds then comes back with failed. So tried downloading factory image and flash with fasboot but was complaining about bootloader locked. So I issued fastboot oem unlock and choose yes the screen switches to unlocked but doesnt wipe anything try to flash again and I get FAILED flash write failure. When I reboot to the bootloader it shows as locked again. I think my flash took a crap. Anyone have any ideas?

I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....

since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.

kj2112 said:
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.

simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.

what do you mean doesnt unlock it?

prestonr83 said:
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
Click to expand...
Click to collapse
very odd!
youre device is seen by fastboot(not adb)?

prestonr83 said:
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
Click to expand...
Click to collapse
That's a good point.
I'm afraid that if you cant flash the stock image, and you can't unlock the bootloader to try other methods....you may be at an impass.
You need to either get the stock image back on. Or unlock the bootloader, Then try my link. Not sure what else can be done here.
Sent from my cell phone telephone....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Oh....and again.....you may have driver issues on the pc, and that's why fastboot isn't seeing the phone. That is the first thing that needs to be corrected.
Sent from my cell phone telephone....

Zepius said:
what do you mean doesnt unlock it?
Click to expand...
Click to collapse
I mean i put it in fastboot issue fastboot oem unlock it prompts me on the phone to choose yes or no. I choose yes it then immediately goes back to fastboot screen and shows unlocked. However when trying to flash anything it fails and upon rebooting back into fastboot it again shows as locked.

Your emmc is dead. RMA it
Sent from my Nexus 5 using Tapatalk

simms22 said:
very odd!
youre device is seen by fastboot(not adb)?
Click to expand...
Click to collapse
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.

prestonr83 said:
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
Click to expand...
Click to collapse
have you tried flashing clockworkmod recovery and factory resetting it there?

simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Advice I would really have to disagree with as it is a built in security measure; telling people to avoid using proven security methods is sketchy in itself. I had my Nexus 4 encrypted for the last 4 months and had never had any issues. What issues are you talking about?

Encryption slows the device down... We all know that. Also, if by chance someone forgets their pw (yes... Seen it happen plenty) you lose al your stuff to get back in.
Anyway, to each their own... But I'm not important enough to worry about what's on my phone getting into the wrong hands. ?

VZN locked, Pixel stuck at bootloader, recovery mode fails -- what now?

Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK

TromboneKenny said:
Hi all,
I have an OG Verizon Pixel that's now stuck at the bootloader. I haven't done any unlocking or ROM modifications. It was stock 8.1 and it broke pretty close to the January update.
Recovery mode says "Failed to boot to recovery mode".
Starting from the bootloader just loads back into it, but the screen gets off-centered (I can attach pics if it helps).
When the phone was working, I'd never done any of the in-OS tools to start the bootloader unlocking process. I'm not really sure what I should be trying, but nothing I have tried from fastboot seems to work because it's locked. I feel if I could reimage it all, maybe it would work again, but it doesn't look like I have that kind of access.
Verizon's only option was $150 to replace it out of warranty (and then only provided a 90-day warranty). I declined that and got a Pixel 2, but now I have the old phone. Is there anything I can do with it? Or is it just junk?
Thanks,
TBK
Click to expand...
Click to collapse
Try reflashing the same factory image ur on

If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.

shagbag913 said:
If the bootloader isn't unlocked it is probably bricked. With an unlocked bootloader you could reflash a factory image and get it working but you cant do that with a locked bootloader.
Click to expand...
Click to collapse
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA

KittyRgnarok said:
I could be wrong but I think u might be able to sideload like an Oreo preview build without bl unlock, idr though but yeah tl:;dw: your device is likely as bricked as a house so you should attempt to request and RMA
Click to expand...
Click to collapse
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
Yeah that's what I'm thinking. OP test this and if anything breaks report back

That's pretty odd that it would just break like that. If he hasn't messed with anything software related it could be a hardware issue

shagbag913 said:
You can sideload ota updates in the stock recovery, but I'm pretty sure that's it. He could try sideloading this months update and see. I could be wrong
Click to expand...
Click to collapse
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?

TromboneKenny said:
I can't even get into recovery mode. It errors (see OP for the message). Would it be different if I initiated recovery mode from fastboot or adb?
Click to expand...
Click to collapse
I don't think it would be different. This sounds like a hardware issue, not software.

Is this my fault or a hardware issue? (ERROR: Slot Unbootable: Load Error)

Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.

u found any way to unbrick your phone?

yuva_cool said:
u found any way to unbrick your phone?
Click to expand...
Click to collapse
Nope. The RMA was approved and I'm using a new (refurbished) device.

U had an unlocked bootloader and yet your RMA was approved? @computerslayer

yuva_cool said:
U had an unlocked bootloader and yet your RMA was approved? @computerslayer
Click to expand...
Click to collapse
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.

computerslayer said:
The error showed up when I relocked the bootloader, so it was locked when I submitted the RMA. They approved it (and didn't demand a payment when they received the RMA'd phone), so I suppose they accepted that it was a warrantied issue.
Click to expand...
Click to collapse
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.

robocuff said:
Did you flash the stock boot image before you relocked? If not, Magisk was still installed and that's where you went wrong. You need to be completely stock when you relock the phone.
If you ever relock the phone you have now, to be on the safe side, I'd flash the factory image and leave the -w in the flashall batch file. Your phone will get wiped when you relock it anyway so you won't be out anything if you do so.
Click to expand...
Click to collapse
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.

computerslayer said:
I am abashed to have to report that I did not flash the stock boot image. I wondered if Magisk was the cause, but assumed that the wipe caused by relocking would take care of that too.
Click to expand...
Click to collapse
If that's the case, it's a certainty that that's the cause of your problem. You have to be completely stock when you relock it. Flashing the factory boot image should take care of that if all you have done is installed Magisk. That said, I'd still flash the factory image and let it do the wipe, just to be sure.

computerslayer said:
Okay, so my phone is bricked and there's no recovering it. RMA is already ordered and on it's way. Essentially I'm in the same situation as this poor soul (and many others, from the results of searching for this error in the forums).
What I want to know is if I did this or if this was something I couldn't have foreseen. The phone had an unlocked boot loader with the latest OS (Pie) & security updates (November). No custom ROM or kernel - stock everything, though I did have Magisk installed. Today I decided to re-lock my bootloader. While the device was in fastboot mode I issued the command "fastboot flashing lock" and followed the phone's on-screen directions. When it finished and tried to reboot, it would only go the fastboot mode with the message "ERROR: Slot Unbootable: Load Error".
I recognize that locking the bootloader may have been the last straw for some present flaw - like a weak engine finally giving out after long service. Is that the case here or is there some step I missed that would have prevented this from happening? I ask because I don't want to repeat a mistake in the future.
Click to expand...
Click to collapse
I have this issue and now my pixel 2 cant boot. It stuck. Cant enter fastboot. This is my last experience with pixel series devices. Its expensive phone, but its too sensitive to brick. I dont know why, an update or a flashing stock rom can make your phone totally unuseable. I just cant accept it

I had exactly the same issue. just keep holding the power button with or without the vol- for a good 30~ seconds or so (it will restart several times) but keep holding.
and make sure you are connected to the PC until you hear the ding that the phone got recognized, then the phone will accept fastboot commands.
This worked for me before I was going to throw the phone in the garbage!

Pixel bricked with locked bootloader

Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).

You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.

post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'

This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905

junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.

Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs

junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?

aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.

Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?

post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.

Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks

HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.

Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks