Database Info

Partially Bricked Nexus 5

I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this

I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal

snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.

Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data

I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop

do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.

Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above

rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links

snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..

rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..

snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.

rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.

snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers

rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?

snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading

jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.

rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.

theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight

Softbricked my nexus 5? Any help?

So i'm not super competent in adb and what not, but just competent to use wuggs toolkit. I went to google's website to download lollipop 5.0 for my nexus 5. Then i set the phone back to stock, flash 5.0 and its running well. Then i go back in to settings, developer options, and to root my nexus 5 and install TWRP on it through wuggs. Now it has twrp, but will not boot up past the google name with the unlock. I only have the fastboot page and TWRP. The big kicker here is that my pc says does not recognize device and it flickers back and forth with connection every two seconds to my PC. When i go into device manager it shows android device though. So well hey i figure since i have a softbricked nexus i'll just click the button for it and reset. Well it wont do it, it pulls up fastboot.exe goes through a few commands, some saying it failed then it stops and windows tells me to close fastboot.exe
Any help from the very respected XDA?

oh, gawd.. fastbooting a factory img would have been so much faster. sorry, toolkit, i cant help you with it.

hayden55 said:
So i'm not super competent in adb
Click to expand...
Click to collapse
There's your answer right there. That's how ppl like Op brick their devices everyday

Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.

jayRokk said:
Do some research, read read and lastly Read
If you can adb the factory image you can adb a recovery. Google how to. Its literally one comand line.
Stop tossing the word bricked around, a brick is a phone that doesn't turn on and don't blame other things if you don't know how to use them.
Google is your best friend. No one is going to hold your hand.
Click to expand...
Click to collapse
aww but i really wanted a hand hold.

hayden55 said:
aww but i really wanted a hand hold.
Click to expand...
Click to collapse
here is an extra long :highfive: for your hand holding

chapelfreak said:
here is an extra long :highfive: for your hand holding
Click to expand...
Click to collapse
Hey thanks bud! Problem was it couldnt connect to the computer for more than 5 seconds...
SOO.... i messed with mounting an OTG jump drive and it had my old TWRP back with android 4.4.4. IT Worked!
p.s. i tried just mounting system data etc... the turn on mtp connection button and it Would show up better than just plugging in but couldnt download anything big. and no adb connection

dicecuber said:
There's your answer right there. That's how ppl like Op brick their devices everyday
Click to expand...
Click to collapse
i do not need your input if you aren't going to contribute to the problem just antagonize the op

Current problem at hand: phone now will only connect to pc for 5 seconds at a time. What could do this and how do I reflash to normal?

Still using toolkits?

hayden55 said:
i do not need your input if you aren't going to contribute to the problem just antagonize the op
Click to expand...
Click to collapse
It's a suggestion

Disclaimer: I use OS X/Terminal to fix these things normally and honestly found that after the initial learning curve, it's easier than using Windows or Wugfresh. I'm not a developer, just a hobbyist user.
Make sure you're using an OEM cable to connect to the computer if you're getting dropouts. Also, attempt to uninstall and reinstall OEM drivers (I believe Wugfresh has instructions on how to do this) for Windows.
If you have confirmed that you have TWRP 2.8.1.0 installed, try to boot to TWRP --> ADB Sideload. Connect phone to computer, open Terminal/Console and type the command 'adb devices' (without the apostrophes. I haven't used Windows since I stop using Wugfresh, so the command probably differs). If the device can be seen through this, you should be able to return to the bootloader and start issuing fastboot commands to flash the image.
Let me know how I can help!

[Q] Nexus 5 stuck on boot loop

Hello everyone:
This is the first time I ask for help on the Nexus 5. I read the couple of post about boot loop, but they could not help me. What happened was that I was checking some link on the browser and all of the sudden the phone restarted, I saw the google logo then the four color dots and it stayed there for ever. I check for info on how to deal with the problem and tried the power button plus the volume down (-) to get into the loader. After I was on the loader I tried unsuccessfully all the different menus that come with it, i.e., Start, Reboot, Restore, Power off. The only one that produces any result is the power off with which I can just turn the device off. I have had the phone since November 2013 and it is untouched, original google phone. It updated to os 5 a few months ago and there was no problem with it. I wanted to restore it to factory settings but as mentioned before the phone will not let me in. Is there any other way I could try to access it to restore? Thanks for your help.

Do a search for nexus factory images. You'll have to unlock your boot loader and then follow the instructions on that page.
Sent from my Nexus 5 using Tapatalk

Thanks but...
ldubs said:
Do a search for nexus factory images. You'll have to unlock your boot loader and then follow the instructions on that page.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you Idubs for the help, I am still reading and got stuck on the following:
I got an HP Envy 17 with windows 8.1 and I am trying to follow this instructions to get the Universal Naked Drivers install put can get this to appear:
To Install on Windows 8, you must additionally disable driver enforcement
- From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the - -- pop-out bar to appear, then click the Gear icon).
- Click ‘More PC Settings’.
- Click ‘General’.
- Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
- Wait a bit.
- Click ‘Troubleshoot’.
- Click ‘Advanced Options’
- Click ‘Windows Startup Settings’
- Click Restart.
All that is on bold can't be access. The closest I get is to Restart and the laptop restarts, which makes me loose everything and no driver can get installed.
Any suggestions?

Using Win 7 computer
After hours of no go with Win 8.1, I finally tried my old Win 7 pc. I got android sdk installed per instructions on this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I can get to the point where I type fastboot oem unlock, and the phone shows it's unlocked, then I am supposed to type fastboot reboot. The phone reboots and stays on the permanent boot loop. I waited 30 minutes and nothing. Is it something I am doing wrong or the phone is toasted? I will like to know before I send it to Google for repairs as it is not in warranty any more and they will probably charge me what the phone was worth in the begining. Any ideas?

Put it back in fastboot mode and flash the factory images using the instructions from the page where you downloaded them.
Sent from my Nexus 5 using Tapatalk

@abyss1957 what happens when you flash a kitkat rom?

Frustrated
Hi:
I did a flash-all per instructions and the phone will not accept it. I unlock the phone, at least it says so on the display, when I give it the command the first thing it does is it reboots the loader and gets locked again. From there on the whole operation fails because it says it can not write to a lock device. I am using the adb program with the windows 7 command line. I think I will let google play with it if is not to costly, anyway I have to call them tomorrow to find out what happened with the shipping labels and instructions they were going to send.

abyss1957 said:
Hi:
I did a flash-all per instructions and the phone will not accept it. I unlock the phone, at least it says so on the display, when I give it the command the first thing it does is it reboots the loader and gets locked again. From there on the whole operation fails because it says it can not write to a lock device. I am using the adb program with the windows 7 command line. I think I will let google play with it if is not to costly, anyway I have to call them tomorrow to find out what happened with the shipping labels and instructions they were going to send.
Click to expand...
Click to collapse
If the bootloader is re-locking itself it's a classic sign of an emmc failure. Sorry man you've done all you can. See if Google will still warranty it. Keep asking to talk to a higher level of costumer service if they say no. Sometimes they can be really generous about out of warranty phones.

Thanks all
I tried today to revive the phone again by doing it per bitdomo thread:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
After it got to about 6% is failed and the message was: userdata erase failed, and from there nothing happened. I guess it is really toasted. Thanks anyway for all the help all I can say is that I know today more than I did yesterday thanks to the great site. You all have a nice day. :laugh:

abyss1957 said:
I tried today to revive the phone again by doing it per bitdomo thread:
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
After it got to about 6% is failed and the message was: userdata erase failed, and from there nothing happened. I guess it is really toasted. Thanks anyway for all the help all I can say is that I know today more than I did yesterday thanks to the great site. You all have a nice day. :laugh:
Click to expand...
Click to collapse
Don't give up yet..... Look at my post http://forum.xda-developers.com/goo...p-lollipop-t3098632/post60491129#post60491129
I was in a similar situation and managed to fix my phone. Give it a try :good:

Thanks a lot eross
Thanks for the post, unfortunately I tried to flash it a couple of times after I posted my last and nothing happened. Always stuck at 6%, so I finally send it to LG for repairs. It should be back next week. Mine never allowed me to write anything to it, maybe a component bad. They send me an email with the charges for the repair but never said what was really bad with it, except that it was on a start up loop (like I didn't knew that). Anyways thanks to all for the help it was a real learning experience. :good:

Don't give up yet read a post above
LG is a waste of money

Oneplus 6 stuck in fastboot mode

Hello everybody,
I was glad to receive my OnePlus 6 3 days ago. But this morning, the phone rebooted itself and I am now stuck into fastboot mode.
So just to be clear, I already tried the following things :
- Rebooting into system by pressing "Power" while fastboot mode is selected on "START"
- Rebooting into system by using fastboot.exe utility "fastboot.exe reboot"
- Rebooting into recovery by selecting the option in fastboot menu and pressing "Power"
- Trying to unlock the bootloader by using fastboot.exe utility "fastboot.exe oem unlock" (Can't do it since I didn't turn on the option in Developer Settings)
At this point, my phone is just a brick rebooting into fastboot and I'm thinking about sending the device back to OP. Would someone have an idea what could I do to boot the phone or at least access the recovery ?
Thanks.

Is it still stock? Have you done anything to it? If you haven't unlocked it, I don't think the unbrick tools will work for you, and you should contact OP.
You might give this a try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

iElvis said:
Is it still stock? Have you done anything to it? If you haven't unlocked it, I don't think the unbrick tools will work for you, and you should contact OP.
You might give this a try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Hi, Thanks for your reply. I didn't do anything to the phone. It was 100% stock. I'm now trying some tools I can found on xda but with no luck :/
I'm gonna try the tool you linked right now. Will keep updated.

Gr8man001 said:
Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That tool requires an unlocked bootloader, which the OP does not have.

Gr8man001 said:
Have you looked into this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Thanks for your reply.
Yes I tried it like 15 min ago, and I get an error because my bootloader is locked ... I can't unlock because it has to be done in the system.

So, if you don't mind losing your personal data on the internal storage, you might try unlocking the bootloader. This will wipe the internal storage. I had an issue where I was caught in a bootloop and I locked and then unlocked the bootloader and it got me out of the bootloop.
If you are stuck in fastboot, you should be able to unlock the bootloader via adb cmd line from your computer. I believe it's "fastboot oem unlock".

azsl1326 said:
So, if you don't mind losing your personal data on the internal storage, you might try unlocking the bootloader. This will wipe the internal storage. I had an issue where I was caught in a bootloop and I locked and then unlocked the bootloader and it got me out of the bootloop.
If you are stuck in fastboot, you should be able to unlock the bootloader via adb cmd line from your computer. I believe it's "fastboot oem unlock".
Click to expand...
Click to collapse
Thanks for you reply.
Unfortunately, the bootloader can't be unlocked. I have to check "OEM UNLOCK" in developer settings and since and I can't boot into the system ...

Krysou said:
Thanks for you reply.
Unfortunately, the bootloader can't be unlocked. I have to check "OEM UNLOCK" in developer settings and since and I can't boot into the system ...
Click to expand...
Click to collapse
Forgot about that setting...sorry. You might try and give OP Support a call. I have heard that they can remote into your phone and resolve issues like this one.

I am NOT an expert and there are smarter folks on this site who can explain. I had a similar issue with one of my previous phones and someone had suggested to turn off the phone (if you can otherwise just try it in fastboot mode) and hold BOTH volume up and down buttons while pressing the power button (keep it pressed for a good minute or so) and I was able to boot into "limited" OS (I think it's called safe mode or something). Not saying that it will fix the issue but may be worth the try. Just trying to help. Good luck.

Gr8man001 said:
I am NOT an expert and there are smarter folks on this site who can explain. I had a similar issue with one of my previous phones and someone had suggested to turn off the phone (if you can otherwise just try it in fastboot mode) and hold BOTH volume up and down buttons while pressing the power button (keep it pressed for a good minute or so) and I was able to boot into "limited" OS (I think it's called safe mode or something). Not saying that it will fix the issue but may be worth the try. Just trying to help. Good luck.
Click to expand...
Click to collapse
Thanks for your suggestion. Unfortunately, the device reboots into fast boot each time again and again.

time to call OnePlus and have them do a remote session to restore ur phone, get a keylogger and get the passcode for the zip for us lol

Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
https://www.******.com/unbrick-oneplus-6-using-msmdownload-tool/
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.

Krysou said:
Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
https://www.******.com/unbrick-oneplus-6-using-msmdownload-tool/
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.
Click to expand...
Click to collapse
can you give a download link of that tool and some simple instruction, please.

jkyoho said:
can you give a download link of that tool and some simple instruction, please.
Click to expand...
Click to collapse
Hello,
https://www[.]berga-tech[.]com/2018/05/how-to-guide-unbrick-oneplus-6-using.html?m=1
You will find all instructions and download link there.

Return
Krysou said:
Thanks for your reply.
Yes I tried it like 15 min ago, and I get an error because my bootloader is locked ... I can't unlock because it has to be done in the system.
Click to expand...
Click to collapse
Unfortunately sounds like you may have to return the phone. (that sucks)

https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
try the OOS5.1.5 MDMtool from link above. It works for me.
And if you unable to go to qualcomm 9008 mode from fastboot, try connect to pc with cable ,and press and hold power& vol_up, and wait for the connect sound from computer

Krysou said:
Ok guys, good news. I succesfully reseted the phone thanks to MsmDownload Tool.
The link provided by iElvis helped me identify which tool should I search. After downloading the .rar file from the link, I got an error when launching the program. I then searched another version of it and found :
This one worked perfectly. I am really happy it works again. I would like to understand what happend but whatever, let's hope it does not happen again.
Thank you all for your suggestions.
Click to expand...
Click to collapse
I'm experiencing the exact same issue than you Krysou. Thanks a lot for the solution which gives me a hope ! Could you please tell me if you were able to recover your data (photos / videos) after the unbricking procedure ? I'd like to know it before I run the MsmDownload Tool.
Thanks for your reply

groggy8888 said:
I'm experiencing the exact same issue than you Krysou. Thanks a lot for the solution which gives me a hope ! Could you please tell me if you were able to recover your data (photos / videos) after the unbricking procedure ? I'd like to know it before I run the MsmDownload Tool.
Thanks for your reply
Click to expand...
Click to collapse
OOps men, I'm sorry to answer that late to your question, doing it for the others searching for a solution.
So : You won't recover anything after running MsmDownloadTool. You get a pretty much completely stock phone, like when you got it after unboxing

Krysou said:
Thanks for your suggestion. Unfortunately, the device reboots into fast boot each time again and again.
Click to expand...
Click to collapse
try this metod https://forum.highonandroid.com/t/how-to-unroot-oneplus-6-using-fastboot/33

Google update bricked phone

Afternoon all.
This morning I had one of the usual messages on my pixel 2 about having to restart the phone to install the update. I did so but now I can't boot the phone. I'm in the bootloader, with the following options and consequences
start > causes phone to restart instantly
restart bootloader > restart instantly
download mode > restart instantly with "ERROR: Operation Denied"
recovery mode> restart instantly with "ERROR: LoadImageAndAuth Failed: Device Error"
Barcode > works
power off > works
I've not tinckered with the phone in any way and have only installed official updates when prompted. I'm trying to get up to date with everything again, and have downloaded adb. "adb devices" doesn't show anything, however "fastboot devices" will display my device. I've tried the unlock "fastboot flashing unlock" command but get "FAILED (remote: 'Flashing Unlock is not allowed')"
Is my phone bricked? It's a few weeks out of warranty.... any help is greatly appreciated.

Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?

junglism93 said:
Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?
Click to expand...
Click to collapse
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.

thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse

junglism93 said:
thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse

thermomonkey said:
junglism93 said:
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse

junglism93 said:
thermomonkey said:
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse
Thanks again. Has this happened to anyone else before? i.e. just restarting when told to by the normal google updates and the phone is suddenly bricked?? Seems silly and it's totally put me off buying another pixel device!
Click to expand...
Click to collapse

If you search loadimageandauth error in XDA search you'll find a few threads on it, was just doing that myself. Seems to point at a bootloader issue from what I've skimmed over so far which would tie in with that link I posted.
I'm not put off the pixels by these things, in the grand scale of things it's a very low average of devices it happens on so I guess you've just been unlucky. This is my 2nd pixel device ( had the pixel prior to this pixel 2) and most likely won't be my last pixel device.
Good luck with having another crack at the warranty