Database Info

Moto g bricked

Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me

Joomlar said:
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Click to expand...
Click to collapse
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.

smohanv said:
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
Click to expand...
Click to collapse
Or he can ask for replacement
Sent from Samsung Chat

jaspreet997 said:
Or he can ask for replacement
Sent from Samsung Chat
Click to expand...
Click to collapse
I would not wait for two weeks for replacement when we can bring the phone to life within 30min.
I agree a risk element in it. If the phone is basically faulty, then it is not worth trying the way I suggested. Has this worked before you started mess around?
Good luck..

smohanv said:
I would not wait for two weeks for replacement when we can bring the phone to life within 30min.
I agree a risk element in it. If the phone is basically faulty, then it is not worth trying the way I suggested. Has this worked before you started mess around?
Good luck..
Click to expand...
Click to collapse
If the phone is basically faulty (a potential hardware issue) the last thing one should do is unlock the bootloader and lose the warranty.
Sent from my Nexus 5

If you have ordered from flipkart Just call them and pretend that its not turning on at all.....and they will give you a hand to hand replacement!

I can return phone but it cost more then 60 EUR via DHL and i must wait long time...
Today i will try to unlock bootloader and flash firmware. Thanks you all, have you more suggestions?
I dont know what happened. This is strange problem because telephone work fine 5 hours and after power off, i see only Motorola Logo. I hope that i will not miss guarranty when i unlock bootloader.

Unlock device is finished. Can you give me tutorial for flashing stock firmware? I am noob
U used this tutorial: http://www.theandroidsoul.com/install-moto-g-uk-generic-firmwarestock-rom/
but after flashing i have the same problem
Is there any solution? If not, how i can lock bootloader because now i lose guarranty

Joomlar said:
Hello,
I was bought moto g 8 GB and i used it one day.
My phone does not work
I made factory reset and after that phone works but after 2 hours when i turn on phone, i see only Moto logo, after that he appeared black screen. I will record video tomorrow if you need it.
When i hold power down and power button i can see fastboot flash mode. I can see normally options in flash mode but also i see "Device is LOCKED". http://postimg.org/image/oa3blyd2n/
http://postimg.org/image/9pm8r4i3z/
When i click on recovery mode phone has restart and i see moto logo and black screen...
I wait 7 hours but nothing happened.
Please help me
Click to expand...
Click to collapse
I had exactly the same issue, after I unlocked the bootloader this happened to me, don't worry is not bricked just a software issue with some providers firmwares, what did I do? The good about this is, you should be able to put it in fastboot.
Read all before try it please
* I unlocked the bootloader (seems like you already did it)
* I flashed CWM http://forum.xda-developers.com/showthread.php?t=2563599
Here the next issue was I needed to flash a ROM but I wasn't able to put any file in my device even mouting the USB in CWM or adb push, so: sideload
* I downloaded this rom http://forum.xda-developers.com/showthread.php?t=2606943 (you could use other but that worked for me)
* I Put the zip file in the fastboot directory
* I turned on my device in recovery mode (CWM, you can do it by the fastboot, select recovery, use vol up to enter, vol down to move, power button doesn't work here).
* Wipe factory, cache and dalvik (just in case I think factory wipe is enough)
* I went to the option flash from zip file, flash from sideload (or similar not sure about the name but it says sideload)
adb sideload myromfile.zip
once the adb finish, CWM will notify you and you can flash your rom regularly. It will finish, then you should reboot, It should take about 5 minutes for the first boot. Then my phone worked again.
Sorry if I said something wrong, first time I talk here and I felt identified with your issue and wanted to help you.

Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone

sounds like the phone might be faulty if it happened and you didnt do anything to cause it ,
anyway another option for you is to try a external reset,you have attempted too flash other firmwares so not 100% sure it will work but give it a try through fastboot recovery.
click the link below and halfway down the page follow the instruction for "external reset"
https://motorola-global-portal.cust..._detail/a_id/97329/p/30,6720,9050/action/auth

This is my steps:
-Flash this falcon_retgb_user_4.3_14.10.0Q3.X-76-LGG-8_54_release-keys-cid7-Retail_GB via this tutorial http://www.theandroidsoul.com/install-moto-g-uk-generic-firmwarestock-rom/
-flash CWM V3 or V2
Do i need to flash some other stock ROM before i do external reset? EDIT; external reset does not work becase i can not enter to recovery and wipe data/cache...

smohanv said:
The good thing about development phone like Moto G are that you can never brick your phone. It is very much recoverable. Try unlocking bootloader and then flash official firmware from this link http://sbf.droid-developers.org/phone.php?device=14
Use this link to unlock bootloader,
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
You can bring your phone back to life.
Hope it helps.
Click to expand...
Click to collapse
Except it isn't a development phone and of course you can brick it. Try erasing the bootloader and recovery and see how you get on then. Im pretty sure it'd be bricked??
To OP - you should have returned phone especially as you are a noob, no offence but a noob trying to recover a phone which has 'broken' by itself is not going to end well especially as its impossible to tell if its hardware or software issue in the first place.
I wish you luck though.

Joomlar said:
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
Click to expand...
Click to collapse
To get into CWM after flash it, go to fastboot mode, then in the menu, use ONLY vol down and move to the recovery option, once in the recovery option push vol up.
It also could be you phone has a fault from factory.

scott_doyland said:
Except it isn't a development phone and of course you can brick it. Try erasing the bootloader and recovery and see how you get on then. Im pretty sure it'd be bricked??
To OP - you should have returned phone especially as you are a noob, no offence but a noob trying to recover a phone which has 'broken' by itself is not going to end well especially as its impossible to tell if its hardware or software issue in the first place.
I wish you luck though.
Click to expand...
Click to collapse
You can perfeclty recover an erased or corrupt bootloader, and from there flash anything you want, including recovery. Yeah, it's an unbrickable phone.
http://forum.xda-developers.com/showthread.php?t=2623587

Joomlar said:
Thank you. I flashed CWM but i can not enter to it. When i hold volume down + power button i enter in fastboot flash mode. How i can enter to recovery cwm? When i enter to recovery trough fastboot mode nothing happened. Phone has restart and appeared moto logo. When i flash it i got ".mismatched partition size".
Is there any tutorial for me ? I am very frustrated with this phone
Click to expand...
Click to collapse
i got the same error, but i just kept flashing cwm like five times in a row then vol down then up and it loaded cwm.
try it.

Yes, it can be bricked depending on the version... Mine can't have the bootloader unlocked...
Sent from my XT1032 using xda app-developers app

I must return phone. My bootloader is unlocked, i hope that manufacturer will give me new phone.
IF you have any solution respond me please.

Maybe you could try this way http://forum.xda-developers.com/showthread.php?t=2542219 !?

Joomlar said:
I must return phone. My bootloader is unlocked, i hope that manufacturer will give me new phone.
IF you have any solution respond me please.
Click to expand...
Click to collapse
Your phone seems to be fine. the only option worth a try is to flash official firmware that should go ok with a locked bootloader forget about custom recovery and rooms
and in any case do not unlock the bootloader until you some how solve this and in the picture you posted the phone already is in flash mode just make your PC to recognize your phone by installing the necessary drivers and flash
Find everything you need in the post above mine

Black screen and nothing else...

Lets make a long story short, i just got my OPO, as an advanced android user i desided to put
ParanoidAndroid 4.6, but before I installed custom bootloader (TWRP) and rooted it. Since i am installing new ROM i did a backup and then i needed to wipe my device, by accident i wiped everything from my phone, including backup and new ROM. I was left with TWRP (It is my 1st android phone without sdcard so i started to panick), then i started it in fastboot mode, to check if I can copy ROM again from my pc, but it didnt work. Then i went to restart options in TWRP and choose restart in recovery mode, then my phone turned off. Apperently it did restart but now my screen is just black and I cant do anything with it. I was holding power button, then with volume up, then with volume down, no result. When i connect it to my PC i hear sound that phone is connected but still nothing is happening. Please help me what should I do. My guess is when i pressed to restart in recovery mode, it wasn't meant to be the custom one, so it tried to open one that dosen't exist. My phone was charged 40% when i was doing that.
Note1: Unknown USB Device (Device Descriptor Request Failed), this is what i get when I check Device Manager.
Many suggestions were made so far none of them help. Hope someone will help me here!

First, TWRP isn't a custom bootloader, it's a custom recovery. The phone can't 'open a recovery that doesn't exist', it opens whatever recovery you have installed at the time. Make sure the phone is powered off (hold power for about 10-15 seconds), then try booting into recovery again (hold power + volume down).
Transmitted via Bacon

Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.

There is another problem
bigballa said:
Looks like you're using windows from the looks of you writing Device Manger so if you can boot back into fastboot then you're still okay!
Download this then just use the Flash CM11S option and it should bring you back to life.
Tool kits are amazing bro. Even as an advanced user myself they are still my favorite tools to use.
Click to expand...
Click to collapse
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.

Only 1 thing
I just need to fix how to find device in adb and then it will be very easy.

Mod Edit: quoted post removed.
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
[/COLOR]
Gapkobob said:
I tried all of the toolkits and fastboot, the problem is that i cant even see device when I type adb devices in cmd.
Click to expand...
Click to collapse
Gapkobob said:
I just need to fix how to find device in adb and then it will be very easy.
Click to expand...
Click to collapse
My friend you're in a bit more trouble than I think you realise you're in. Your device is showing up as QHSUSB_BULK in Windows, which means it's technically bricked. I believed you can save it though, have a look in this thread, you're gonna need to read through it all to find the solution you need. Let me know how you go.
Transmitted via Bacon

Simple driver issue.
The following steps will solve your problem: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/

Solved !!!
Solved thx to everybody. http://forum.xda-developers.com/one...een-fastboot-adb-t2835696/page16#post55129486 this helped

Great news.
Transmitted via Bacon

MATE 7 L-09 bricked and dead

Hello
I have a Mate 7 L-09 and I am in the same situation of Sassan_Payehdar described in the his thread
Hi everyone,
I have a Huawei Mate 7 LT-09 16 gig, and I recently did these works:
1. The installed rom was android 6 B513.
2. I read a post in this forum (that is closed now) and updated it to B553 KingVIP Chinese through restoring nandroid TWRP backup.
3. After install I saw lots of bugs, so I wipe all partitions through advanced wipe in TWRP.
4. Then install marshmallow stock recovery using mobopx tool.
after that nothing works.
The USB drive just show hisuite CD-Rom and device not recognize for ADB Options in windows 7,8,8.1 and 10.
There is no recovery,
There is no option using combinations of the buttons vol+,Vol- and power.
I tried installing stock ROM through .app file and dload folder and still nothing works.
I tried Jtag and after lots of work, fastboot screen appears and reinstalling all versions of different recoveries and looks like the software is installing nowhere in neverland!, there is nothing!
I take my device to a technician and he said there is maybe no way to re-run the device. I really need help.
Apologize for poor English and thanks in advance help.
Click to expand...
Click to collapse
No bootloader, no recovery, no option using combinations of the buttons vol+,Vol- and power, no recognition by ADB on PC only huawei logo.
He tried Jtag to appear fastboot, but I never read anything about Jtag. Where can I find it and how to use it?
Sorry for my English.
Can somebody help me?
Thank you so much!!
Al

What happens when you enable your phone (after shutdown) with pressing power + volume up?
Also, what happens when you do the same but with power + volume down?
I would say that if it loads the logo you should be able to enter fastboot/recovery.
Focus on this first and what is your experience with using custom roms to give us an idea of what could be overlooked etc.
If you can load to fastboot and/or recovery let us know and we start from there.

Mother_Teresa said:
What happens when you enable your phone (after shutdown) with pressing power + volume up?
Also, what happens when you do the same but with power + volume down?
I would say that if it loads the logo you should be able to enter fastboot/recovery.
Focus on this first and what is your experience with using custom roms to give us an idea of what could be overlooked etc.
If you can load to fastboot and/or recovery let us know and we start from there.
Click to expand...
Click to collapse
Thank you very much for the answer......
Ok...
I can' t swich off the phone. When I press power off button it reboot and after a few seconds appears huawei logo and then nothing more happens.
When I try to press VOL- and power or VOL+ and power or any other combination of buttons it happens the same think written above: the phone reboot and after a few seconds appears huawei logo and stop.
I brought the phone to the huawei customer center and they told me it need to change motherboard to fix it but it is out of production. I brought it to two famous Chinese stores to fix phones here in Milano, but they couldn't do anything (so they said).
I would just like to retrieve the use of the phone. I saved all the data.
Thanks again for the help.
Al

verdiverdi said:
Thank you very much for the answer......
Ok...
I can' t swich off the phone. When I press power off button it reboot and after a few seconds appears huawei logo and then nothing more happens.
When I try to press VOL- and power or VOL+ and power or any other combination of buttons it happens the same think written above: the phone reboot and after a few seconds appears huawei logo and stop.
I brought the phone to the huawei customer center and they told me it need to change motherboard to fix it but it is out of production. I brought it to two famous Chinese stores to fix phones here in Milano, but they couldn't do anything (so they said).
I would just like to retrieve the use of the phone. I saved all the data.
Thanks again for the help.
Al
Click to expand...
Click to collapse
Not being able to to overcome the logo boot is unknown to me. Maybe the phone should still be able to be flashed!
I lack the knowledge, but to help out I share a link to someone having a similar issue. I will share the link at the end of this post.
If you are unable to connect to your phone and/or make it enter fastboot or recovery I have no idea if that means your phone is bricked.
For now, make sure you understand how to flash,boot,reset etc your phone, only to be sure you have tried all approaches.
Let us know if you did not succeed also so others can learn from this thread in the future
similar topic link -> https://forum.xda-developers.com/mate-7/help/mate-7-booting-t3585079

Mother_Teresa said:
Not being able to to overcome the logo boot is unknown to me. Maybe the phone should still be able to be flashed!
I lack the knowledge, but to help out I share a link to someone having a similar issue. I will share the link at the end of this post.
If you are unable to connect to your phone and/or make it enter fastboot or recovery I have no idea if that means your phone is bricked.
For now, make sure you understand how to flash,boot,reset etc your phone, only to be sure you have tried all approaches.
Let us know if you did not succeed also so others can learn from this thread in the future
similar topic link -> https://forum.xda-developers.com/mate-7/help/mate-7-booting-t3585079
Click to expand...
Click to collapse
Ok
that's unbelievable I was be able to access in fastboot&rescue mode....
I connected the device to my pc but ADB doesn't recognized it.
Now how can I do?
Many thanks
Al

I have same problem as u before, i managed to go to fastboot and then i installed a recovery but the probleme, i bring it into a repair store and the dude literally broke my sd card slot so now I'm really upset.
After that i wanted to make a restore to proposed backups in the firmware forum but nothing happend

Foxar26 said:
I have same problem as u before, i managed to go to fastboot and then i installed a recovery but the probleme, i bring it into a repair store and the dude literally broke my sd card slot so now I'm really upset.
After that i wanted to make a restore to proposed backups in the firmware forum but nothing happend
Click to expand...
Click to collapse
Good
now I am in this situation: I was able to install TWRP recovery for Marshmallow 3.0.2-0 Mate 7 by Mobopx v.2.1.
I chose this recovery beecause my last firmware was EMUI 4.0 (Marshmallow).
After I tried to apply this method: http://ministryofsolutions.com/2016...09tl10-bootloop-after-marshmallow-update.html, but it didn't work. After flashing I power on the phone and it try to boot (some times the animation start too for a bit) but then nothing. The phone reboot in recovery mode (this is a change compared to before).
Somebody has some ideas??
Thanks
Al

verdiverdi said:
Good
now I am in this situation: I was able to install TWRP recovery for Marshmallow 3.0.2-0 Mate 7 by Mobopx v.2.1.
I chose this recovery beecause my last firmware was EMUI 4.0 (Marshmallow).
After I tried to apply this method: http://ministryofsolutions.com/2016...09tl10-bootloop-after-marshmallow-update.html, but it didn't work. After flashing I power on the phone and it try to boot (some times the animation start too for a bit) but then nothing. The phone reboot in recovery mode (this is a change compared to before).
Somebody has some ideas??
Thanks
Al
Click to expand...
Click to collapse
Wonderful!!!!!!
I solved my problem!!!!!
I flashed a TWRP backup get from this forum and now my phone is working.
Thank you to everybody...
Al

I'm very happy for u, can u give me which one you choose for the backup

Foxar26 said:
I'm very happy for u, can u give me which one you choose for the backup
Click to expand...
Click to collapse
Go here
https://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
and choose the appropriate TWRP backp. Flash it by TWRP recovery. It were very simple!!!.
Obviously you have have a working TWRP recovery.....
Hi

Help me fix a bricked OPO :(

Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?

try charging the phone for a few hours

se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.

sounds like u need a new battery

ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.

@bmark240
help please

se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.

bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.

kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.

Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.

THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os

THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out

FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.

i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.

Another brick?

Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!

stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
happened to my walleye too , and managed to bring it back to life . check this thread for a possible solution. https://forum.xda-developers.com/pixel-2/help/december-factory-image-to-broken-t3875213

Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!

stanelie said:
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
Click to expand...
Click to collapse
Just as a reference for anyone else who needs the fix and can't be bothered opening another thread.
SOLUTION: At the menu where it is stuck and saying device fail etc, plug in your usb cable to the mobile, press and hold the POWER button for 10 seconds, it will now recognise your phone under fastboot.
Once that is cleared, it's pretty much straightforward flashing latest pixel 2 image via fastboot and problem solved.
sidenote: Issue came with anyone who tried to flash december security updates and above as of what I heard.

I will try that, thanks.

So, several things :
Holding down the power button had no effect other than restarting the boot menu, but Fastboot never became available.
Opening up the phone and disconnecting the battery and reconnecting it made Fastboot available again. This would be in line with other users that let the phone battery discharge completely before regaining fastboot access.
Sidenote : opening up this phone is not for the faint of heart. I managed to damage something on the motherboard doing so (probably a static electricity discharge), the screen ended up displaying gibberish. I was able to salvage my phone by replacing the motherboard. I had ordered a replacement motherboard when I thought all was lost with no fastboot, and I had it on hand. Expensive little sucker...

stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me except I never even tried to root. Just pulled the phone out of my pocket, and the little Android dude was belly up. It's showing device locked - and although I had it in Dev. mode from weeks back (thought USB Debugging was enabled) it fails to respond to adb commands, boot-loader mode, etc.
...Looks like Google laid an egg with this one.

Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.

ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!

Save my day! I just keep pressing power button and fastboot response finally!

Can this be done if the device is locked?

_Kalyan said:
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Click to expand...
Click to collapse
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
Works on bootloader state locked or not?

SoKa1993 said:
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
Works on bootloader state locked or not?
Click to expand...
Click to collapse
If the boot loader is locked look for a script for unlocking the bootloader from recovery or bootloader state. I did find it but cannot remember. My bootloader was unlocked so I did not have to use it.

ashokabs said:
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I have same problem. I use Pixel 2 and Fedora. My question is, what i exactly should do? I mean the steps. I didn't get that beep from my laptop. But I got the vibration when I hold the power button when it's not connected to USB. Please Help me.
Sorry my english isn't that good.