Database Info

Contacts Recovery. No Screen (smashed), No Root and no USB Debug enabled

Hi, I have a friend who has just smashed their Desire S whilst out on Sat.
Unfortunately, as the title says, they have no screen (touch doesnt appear to work either but no real way of telling!), not root, no USB debug and I have already checked and they didnt have their contacts set to sync with their google account but with the phone! :-/
Can anyone give any suggestions other than a screen replacement? They have already got an S3 on the way today so just want to be able to restore their contacts.
Cheers and thanks in advance!

I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?

Aquous said:
I think this is definitely possible, but it may get very complicated.
Do you have adb in recovery (you'll have to boot into fastboot and blindly navigate to the recovery option)? Is the bootloader unlocked?
Click to expand...
Click to collapse
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,

It is unlikely indeed that you will be able to recover the data as the phone is. If you're in the UK (possible as the phone is on Orange) and fancy posting it then I can stick my LCD and touch panel on it for you so I can recover the data.

Also if u r in the uk, try a phone repair shop that has jtag, they should be able to pull any data off the phone.

radeonorama said:
Thanks for replying Aquous!
I have just been given the phone today from a friend to try and help them out so im not sure on either? Do you have a desire s and would be able to tell me the button sequence to get into recovery to find out? As for the bootloader being unlocked, i very much doubt it as the phone was running a stock orange rom.
Any ideas?
Cheers,
Click to expand...
Click to collapse
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.

Aquous said:
Then you probably don't have adb in recovery either.
We can try the easy way first: from the Google Play website (on your computer), download TalkBack to your phone and see if you can launch it blind. From there on, your phone will read to you what's on the screen
If you can't manage to do that, I have another option in mind but it's complicated and you may not be able to recover your contacts:
Unlock the bootloader via htcdev. This will wipe your data, but if you don't allow the rom to boot after the unlocking, this is OK.
Immediately after issuing the fastboot oem unlock command, HOLD DOWN THAT VOLUME - BUTTON. If the ROM is allowed to load, your data will be significantly harder, if not impossible, to recover.
If you held Vol - correctly after the unlock, you'll be in fastboot (if the phone vibrated, quickly pull the battery before the rom starts writing to the data partition).
From fastboot, boot a custom recovery ('fastboot boot recovery.img')
In this custom recovery, you have adb. Pull the data partition and run file recovery software to try to reconstruct the data that was on it but was wiped by the unlock process.
Purposefully not giving any clearer instructions than this, because if you don't know what you're doing the chances are very high that you're going to do it wrong and won't be able to recover the data.
Click to expand...
Click to collapse
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!

radeonorama said:
Bloody legend!
Using the above coupled with Droid explorer i managed to pull everything she needed! Thanks so much for taking the time to help me out!
All the best!
Click to expand...
Click to collapse
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications

Aquous said:
Holy ****, you actually did this? And it WORKED? You, sir, have some serious balls! Gratz!
By the way, this has HUGE privacy implications
Click to expand...
Click to collapse
Yup, everything i needed off it worked.
I left it for a while as a last resort because of the risk of total data loss and bought a replacement screen which was DOA!
So you plan came into play and it really worked. It wasnt so hard as the steps you gave just helped me get the order right in my head rather than trying something and mucking it up even more!
Thanks again good sir! She was very pleased!

Bricked after unlocking bootloader

Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...

Did you have all the drivers?
Can you get to bootloader?

pert_S said:
Did you have all the drivers?
Click to expand...
Click to collapse
Up to my knowledge, no driver is required on a mac.
pert_S said:
Can you get to bootloader?
Click to expand...
Click to collapse
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.

sylar12 said:
Up to my knowledge, no driver is required on a mac.
No, and that's what makes me think my Nexus is dead. The device does not respond to the power button at all.
Click to expand...
Click to collapse
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?

Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.

pert_S said:
Oh I see. I've never used a Mac for these things before but have you asked for help in the CF thread?
Click to expand...
Click to collapse
Yep. No response so far, but the problem appears a few hours ago only.
I'm pretty sure my bootloader is corrupted. But does that prevent the device to power on?

Any other idea?

sylar12 said:
Any other idea?
Click to expand...
Click to collapse
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.

abaaaabbbb63 said:
If you can't do anything to it, then RMA. Google won't know you did something to it, because they won't be able to boot it too.
Click to expand...
Click to collapse
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem

sylar12 said:
Hi all,
Just having right now a BIG problem with my all new N5. I have received it a few hours ago.
I have just turned it on one time: the phone downloaded and installed an update, and I have configured my google account. After that, and before installing any app, I decided to unlock my bootloader.
Here is exactly what I have done se far:
- downloaded the ZIP archive by chainfire (CF-Auto-root tool) from this thread
- unzipped it,
- I just ran then: sudo chmod +x tools/fastboot-mac
- Then, I boot the N5 in fastboot mode
- And finally: sudo tools/fastboot-mac oem unlock
So, here, my phone asked me (on the screen) if I was sure to unlock the bootloader. I clicked on yes, and then :
- the screen turned off,
- I got on the shell:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Since, my phone does not respond to anything, the power button has no effect. It just seems off, and I can not turn it on.
So, any idea on what has just happened? I was just unlocking the bootloader through fastboot, so no heavy tweaking here...
Any help would be buch appreciated, but I have the feeling that my N5 is now a (pretty) brick...
Click to expand...
Click to collapse
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.

sylar12 said:
I have contacted google, RMA should be OK.
But I would like to understant what happened: is this because I tried to unlock from a mac? A what is the meaning of:
... ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
Just in case it could allow people to not have the same problem
Click to expand...
Click to collapse
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.

Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.

gee2012 said:
Have you created a path for adb (in for windows) system/system variables/path/ commands to be recognized on your Mac (if this is needed off course)? I`am not xperienced with Macs but i guess they also need a path for passing on commands.
Click to expand...
Click to collapse
This is not "directly" required on mac. And the fastboot binay has been recognized by the shell, since the unlocking procedure started (my phone asked me if it was ok for unlocking the bootloader).
abaaaabbbb63 said:
Wait. Try this:
Press and hold the power button + BOTH volume buttons AT THE SAME TIME for about 15 seconds, then try booting.
It seems that the USB connection got interrupted, but that wouldn't normally brick your phone, nor corrupt the bootloader. Maybe it just got stuck.
Click to expand...
Click to collapse
I already tried this: nothing happens... I guess the phone is really bricked.
eddie_gordo said:
Please keep us updated if you find out why this happened. I am waiting for my Nexus 5 to arrive on Monday and I was planning on doing exactly what you did.. Boot it up, configure Google account to check if everything is fine and then unlock the bootloader on a Mac. I've never used fastboot before on a mac as I only have one recently, but from what I remember of using fastboot in a windows machine, as long as we could run "fastboot devices" and got a response, everything should be fine. Isn't this the same in Macs?
Cheers.
Click to expand...
Click to collapse
It should be the same, yes. Fastboot is very easy to use usually, it's the first time I have such a problem. And I have no idea why the unlocking has got wrong. 2 solutions imho:
- a phone harware problem which only reveals during the unlocking process;
- a fastboot problem/mac related problem.
Just trying to figure out which one is the correct answer.

El Daddy said:
Do you see the battery icon when you plug your phone in? Try it a few times and see if the icon will show up.
Click to expand...
Click to collapse
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.

sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.

sylar12 said:
Sorry, just noticed your post right now.
No, nothing happens when I plug the phone in.
Click to expand...
Click to collapse
I think you got really unlucky. Possibly a bad cable or USB port but some connection got lost while you were flashing. RMA is your best option right now. Sorry bro

abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their phone.
Click to expand...
Click to collapse
Yessssss, I did it!
...
:crying:
abaaaabbbb63 said:
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).

sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't they will).
Click to expand...
Click to collapse
You'll be fine on the rma. Been there done that on another device

sylar12 said:
Yessssss, I did it!
...
:crying:
It should be OK I think. I just hope they will not notice I tried to unlock the phone (but if the N5 is really dead, I don't think they will).
Click to expand...
Click to collapse
Maybe the XDA award for the1st N5 bricker is a new Nexus 5 32GB

abaaaabbbb63 said:
Congrats!
You have managed to be the first xda user to really brick their Nexus 5.
I'm sorry, but you'll have to rma.
Click to expand...
Click to collapse
Sorry to disappointed you but I was the first one. Last week I bricked mine

[SOLVED] I think my I may have bricked my tablet

I had the Katkiss 5.1.1 ROM and decided to go with the KatKiss 6.0 ROM. I did a backup to an external card using TWPR. Since I was going from 5.1 to 6.0, I decided to format/data before flashing the ROM. I left the room and came back to see that my daughter reset the tablet. Now it seems to have been stuck in a boot loop similar to what happened in this thread:
https://forum.xda-developers.com/transformer-tf300t/help/softbricked-tf300t-trying-to-flash-to-t3508565
But I can't even get into the recovery. It'll get to the TEAMWIN screen and restart and it won't stop. I can't even shut it off to stop it. I've been searching for a solution and found this link:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated

the_KEV said:
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated
Click to expand...
Click to collapse
Really bad luck!
Hopefully you can reach fastboot. Then follow step by step the instruction in post #2 in the first link of your post to get back on stock rom JB 4.2. Good luck!

Am I supposed to be on a certain screen in order for me to use fastboot?

the_KEV said:
Am I supposed to be on a certain screen in order for me to use fastboot?
Click to expand...
Click to collapse
I don't know what is your knowledge in general, but the post I recommended above gives you all what you need. All erasing steps are based on "Buster99" and have been used several times successfully.
Minimal ADB & Fastboot allows your PC to communicate with your device via a DOS window on your PC. Therefore the USB driver must be installed. USB Debugging on your device must be activated. Hopefully you can start the "Fastboot USB download protocol" via "Power on"/ "Vol down" in the left corner above of the device display.

I'm sorry, I might not have been clear enough... I saw your post with the instructions, I was asking if the tablet should be on a certain screen because the only screen I can get to is where it asks if you want to boot to recovery, android or wipe data. I was wondering if this where I should be on the tablet when attempting this fix. Thanks

OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!

the_KEV said:
OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!
Click to expand...
Click to collapse
Congratulations! You are welcome!

Please halp! Phone possibly bricked

flashed a rom earlier today, and magisk wasnt passing the safteynet check for some reason, so i flashed Huawei-Prop-Fix-v1.1_2017082601.zip and now my phone wont boot at all. nothing even comes up on screen. it just keeps vibrating and resetting with a black screen and lit backlight. idk what to do, kinda freaking out ! please someone halp :'( :crying::crying::crying::crying::crying:
--UPDATE-- SOMEHOW I GOT IT IN FASTBOOT MODE, PLEZ SOMEONE TELL ME WHAT I CAN DO

if you in fastboot.. install TWRP via ADB.. download and flash stock firmware back..
think the chinese version is safest, then just rebrand device and load new firmware

none24 said:
flashed a rom earlier today, and magisk wasnt passing the safteynet check for some reason, so i flashed Huawei-Prop-Fix-v1.1_2017082601.zip and now my phone wont boot at all. nothing even comes up on screen. it just keeps vibrating and resetting with a black screen and lit backlight. idk what to do, kinda freaking out ! please someone halp :'( :crying::crying::crying::crying::crying:
--UPDATE-- SOMEHOW I GOT IT IN FASTBOOT MODE, PLEZ SOMEONE TELL ME WHAT I CAN DO
Click to expand...
Click to collapse
If you can get into fastboot follow this post https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996. Take your time and read it carefully then follow the steps.

vijer said:
If you can get into fastboot follow this post https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996. Take your time and read it carefully then follow the steps.
Click to expand...
Click to collapse
follow which instructions? and im in fastboot mode but my screen is still black

redhotneo said:
if you in fastboot.. install TWRP via ADB.. download and flash stock firmware back..
think the chinese version is safest, then just rebrand device and load new firmware
Click to expand...
Click to collapse
im in fastboot but my screen is still black. i can install twrp but when i reboot i cant get to it. the phone stays black screened and keeps rebooting

none24 said:
follow which instructions? and im in fastboot mode but my screen is still black
Click to expand...
Click to collapse
The link I provided has a lot of information about flashing stock firmware. At this point you probably want a short answer but it would be best if you read the whole post. That way you will have more knowledge about what you are doing.
You need the firmware for your device.
You need TWRP
You need to know how to use ADB
I could try to explain all of this here but it is already explained in the post I linked to. So try reading it carefully, and then ask questions about the parts you don't understand.

vijer said:
The link I provided has a lot of information about flashing stock firmware. At this point you probably want a short answer but it would be best if you read the whole post. That way you will have more knowledge about what you are doing.
You need the firmware for your device.
You need TWRP
You need to know how to use ADB
I could try to explain all of this here but it is already explained in the post I linked to. So try reading it carefully, and then ask questions about the parts you don't understand.
Click to expand...
Click to collapse
no lol a short answer is the last thing i need right now, i need details. its not that i dont understand it, my screen is black so i cannot see anything <---- thats the main issue.
I cant access ADB i can only get into fastboot because again my screen isnt showing anything at all. no bootlogo no nothing. i cant get into twrp only fastboot. i know how to use those things but if i cant get into recovery then what else can i do? my only available access is fastboot

none24 said:
no lol a short answer is the last thing i need right now, i need details. its not that i dont understand it, my screen is black so i cannot see anything <---- thats the main issue.
I cant access ADB i can only get into fastboot because again my screen isnt showing anything at all. no bootlogo no nothing. i cant get into twrp only fastboot. i know how to use those things but if i cant get into recovery then what else can i do? my only available access is fastboot
Click to expand...
Click to collapse
I guess I'm confused, if you can get to fastboot you should be able to issue ADB commands.

vijer said:
I guess I'm confused, if you can get to fastboot you should be able to issue ADB commands.
Click to expand...
Click to collapse
adb commands arent available in fastboot.. its only fastboot commands. adb is only available when the phone is booted into the OS

none24 said:
adb commands arent available in fastboot.. its only fastboot commands. adb is only available when the phone is booted into the OS
Click to expand...
Click to collapse
Well in theory you should be able to issue ADB commands in fastboot. But if you can't, then try using Huawei's Hisuite to recover the phone.

vijer said:
Well in theory you should be able to issue ADB commands in fastboot. But if you can't, then try using Huawei's Hisuite to recover the phone.
Click to expand...
Click to collapse
in theory yes, but sadly it doesnt work like that. ive tried. also HiSuite says its not compatible and the compatibility list only has 2 devices that i think are tablets.
guess its time to return to samsung i loved this phone, but note8 here i come.... its been real guys o/

none24 said:
in theory yes, but sadly it doesnt work like that. ive tried. also HiSuite says its not compatible and the compatibility list only has 2 devices that i think are tablets.
guess its time to return to samsung i loved this phone, but note8 here i come.... its been real guys o/
Click to expand...
Click to collapse
return for warranty.. they will sort out... maybe ur screen is dead or hardware issue..
also get the phone in off state.. think its volume up + power...
then hold down both volume buttons + power and wait for boot.. should take you to recovery screen.. if your screen is active then u have some hope

vijer said:
Well in theory you should be able to issue ADB commands in fastboot. But if you can't, then try using Huawei's Hisuite to recover the phone.
Click to expand...
Click to collapse
in fastboot mode you can only issue fastboot commands.
adb commands are used in recovery/booted system.
@none24 let the phone stay on until it dies then plug in usb and see if it boots after that.

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