Develop Bugs

I've bricked my flatmate's Desire? [FIXED, thanks]

NOTE: THIS ISSUE HAS BEEN FIXED, See this post #97 by "teppic74" for how I fixed the phone
My flatmate recently got a Desire from Vodafone, it's got their latest ROM on it with all their bloatware.
I told him I could debrand it, but the goldcard method didn't work because he had bootloader 0.83.
So I followed a thread to this site on how to downgrade the bootloader:
http://www.tolxdorff.net/tutorials/?step=2
So I did step 4... and then the screen went blank. I left it for a while, I thought it may be installing...
After a long time, I pulled the battery out and rebooted the phone ... I'm pretty nervous by this point LOL
Anyway, the phone reboots and I can hear the annoying HTC chime, which never happened on the Voda rom...
But I can't see anything. It appears that the phone is booting up, but the screen is not working.
Anyone got any advice on what I might do to fix this or am I toast? Grateful for any advice.

Have you try it again or download a original rom (maybe on vodafone...on my o2site it give a original rom and also here on xda)...or have you tried unrevoked...what say the h boot now..?????
with kind regards...Alex

Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea

mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
so you cant even get into recovery?

mmm_ok said:
Unforunately that's the problem... the phone is working and booting up, but the screen is blank... so I can't see anything.
I'll try to find and flash the voda rom, that's a good idea
Click to expand...
Click to collapse
you have no acsess to bootloader or recovery.....??
try vol down (hold it) and phone on (power)...

Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...

Two more people over at modaco at reporting the same issue, I think:
http://android.modaco.com/content/h...o-com/315329/ive-bricked-my-flatmates-desire/
http://android.modaco.com/content/htc-desire-desire-modaco-com/315332/borked-recovery-image/

Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.

mmm_ok said:
Well... I think I can get into recovery... it's just I can't tell because the screen is not showing anything...
if I was to make a noob guess at what's wrong, and this is unsubstantiated, it's that it's a new desire with SLCD screen and that it's get the driver for the AMOLED screen installed when I downgraded...
Click to expand...
Click to collapse
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone

georgemv said:
Test your theory.
Pull out the battery and put it back in.
Press and hold volume down and birefly press power on.
Keep volume down pressed for 5 seconds, then release it.
Count 20 seconds, then press the power key briefly once more.
You should now be in fastboot.
Connect your phone to the USB port and it should list it self when you execute fastboot devices.
If see it listed, you can restore the original ROM via the vodafone RUU file.
Click to expand...
Click to collapse
not bad...that is what i think too
edit: but better explained

mmm_ok said:
Two more people over at modaco at reporting the same issue, I think:
Click to expand...
Click to collapse
Correct that's me.
I tried a normal boot, unrevoked found the phone but got stuck waiting for boot loader.

I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen

mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
nothing in the list also not unknown...?

Alex-V said:
have you try phone on...wait 3-5 min and flash the original rom....or maybe a original ota with h boot 092...maybe windows recognizes the phone
Click to expand...
Click to collapse
Thanks I did try to flash an original ROM... but I get the same problem I had before when running the RUU (error 140)
If I find a .92 ROM, i'm not sure I can install it without seeing what's on the screen though...

Alex-V said:
nothing in the list also not unknown...?
Click to expand...
Click to collapse
Nah, it just says "List of devices attached" and then nothing

mmm_ok said:
I did follow the test you mentioned regarding fastboot.
Windows did make a bleep bleep sound when i plugged it in, but when I ran adb devices (is that what you meant when you asked "is it listed"?), there were no devices listed.
The phone does make the annoying htc sound on normal boot... just no screen
Click to expand...
Click to collapse
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)

I no longer even get the startup beep. Think I am totally screwed?

georgemv said:
ADB will not find your phone in fastboot. You need to download fastboot binary and run fastboot devices to list devices in fastboot mode. If you use windows, you also need to install the fastboot windows driver. (I think you can find that in the android SDK)
Click to expand...
Click to collapse
Thanks for your help. I'm working on it. Get back to ya soon.

SavageCore said:
I no longer even get the startup beep. Think I am totally screwed?
Click to expand...
Click to collapse
I'm getting the bleep bleep cause I tried to install the generic rom... you're probably not getting it because you only tried to root the existing rom, is that correct?

yeah i used this driver...open attached htm file (if you have download unrevoke...its also in) adb

Help phone stuck at boot screen

Hello. I just tried to unlock the bootloader on on Verizon Galaxy nexus. Now it's stuck at the bootscreen with the lock image. I did a search and couldn't find a exact answer for my issue. I hope I haven't bricked my phone. Anyway, any help would be appreciated.
I wasn't trying to root just unlock the bootloader. It appeared everything went ok but, now I'm stuck. I used the same method for unlocking the bootloader on my GSM G-nex and it worked.
I know I've done something wrong or this may be something simple. I just need help so I can use my phone.

are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.

same thing here... I posted a request for a LTE boot.img since can still get into the bootloader

Goat_For_Sale said:
are you able to boot into the bootloader? if so you should be able to recover and can't worry a little less.
Click to expand...
Click to collapse
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"

Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
qnet said:
No I don't believe I can. When I type fastboot it just says "waiting on device" I can hold the volume down & power buttons and get to the screen were it says "start" at the top and below that "downloding"
Click to expand...
Click to collapse
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot

Goat_For_Sale said:
Yea, that was what I was eluding too, The device just came out and google released the GSM image. I am sure that it will appear online in the near future.
if you are able to get into the bootloader does it say that its unlocked ? is your google splash screen showing the unlocked padlock ? you could also try fastboot flash recovery to get cwm on there and provide additional potential solutions.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
That is download mode used for odin.
hold BOTH volumn buttons and power to get into the bootloader/fastboot
Click to expand...
Click to collapse
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.

qnet said:
Yeah, when I did the procedure it said that it was unlocked. Everything looked ok , it booted show the unlock symbol under Google. It then went to the colorful animation and was stuck there. At that time I pulled the battery and, it's been stuck at the screen showing google and the unlock image.
Click to expand...
Click to collapse
you should have let the animation run for like 10 minutes the phone has to rebuild the first boot can take like 15 minutes sometimes.
try booting into the bootloader see if that works still

Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.

qnet said:
Sorry I wasn't paying attention and didn't read the part were you told me how to get to the fastboot screen. I'm there now. Can I just relock or fix the bootloader from problem there? It shows it unlocked at the fastboot screen.
Click to expand...
Click to collapse
you could try fastboot oem lock and see if that works but if the phone wasn't booting i don't know if that will fix it but worth a shot.
try it out and see. it shouldn't do any harm to try

I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.

GirLuvsDroid said:
I had the issue with the failure to boot up after doing the fastboot oem unlock (I had to use the pda net drivers to get my device recognized to get even that far). I did a lot of things like pulling the battery, locking again and then unlocking and nothing worked until I went here http://rootzwiki.com/topic/11732-galaxy-nexus-root-procedure-adb-method/, then downloaded the files following their directions and doing the fastboot boot boot.img command. It took a LONG time to boot up, but it did boot finally.
Click to expand...
Click to collapse
Thank you, I'll try that.

I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?

qnet said:
I have another question. One of the selections on the fastboot screen is recovery mode. Can I try that or is this something were you have to have a rom stored on a sd-card?
Click to expand...
Click to collapse
you could download the recovery image from
http://forum.xda-developers.com/showthread.php?t=1392336
then when connected in fast boot flash it with
fastboot flash recovery recovery.img
(rename the file from the linked thread to recovery.img)
this should write your custom recovery partition.
once you have that though you are still not going to be able to boot but it would allow you to flash a nandroid backup if someone made one for you or a LTE based rom
EDIT: you could also try a factory data reset and wipe dalvk cache from withing cwm. that may fix your boot problem

I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen. All of the files I'd put on my internal storage were wiped (during the oem unlock, I assume) but I'm in the stock rom but Superuser was installed and I have root access.
Hope it helps.
EDIT: looks like this is the same thing Goat_For_Sale posted above, but his command flashes CWM where mine temporarily boots into it. Since most of us will be installing CWM anyway I'd recommend using his command instead.

mixedlemon said:
I had this problem, too.
I downloaded Clockwork Recovery and used 'fastboot boot LTErecovery_cwr.img' to boot into it, I wiped data and cache / factory reset and then rebooted. It rebooted twice, but after ten minutes or so I was back to the ICS Welcome screen.
Hope it helps.
Click to expand...
Click to collapse
where did you get the lterecovery_cwr.img ? could you link to it please

I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg

mixedlemon said:
I linked to the thread in my post, but here's a link to the mediafire upload from that thread: http://www.mediafire.com/?mdf0mtacskob5yg
Click to expand...
Click to collapse
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.

Goat_For_Sale said:
Thanks, my bad I didn't realize you were refering to the recovery image, thought it was the boot image for the LTE device.
Click to expand...
Click to collapse
Ahh no problem.
I got pretty worried for a second that I'd already broke my shiny new Nexus, so I'm really hoping I can help out someone else that had the same problem.

Solved
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.

qnet said:
I believe it's fixed now. I use the method that GirLuvsDroid posted from the Rootzwiki forum. Once it rebooted, I stopped there and didn't root the phone. I was just happy to get it booted.
It's downloading all my apps and settings now. Thanks to everyone who tried to help me, I really appreciate. This was a good learning experience for me.
Click to expand...
Click to collapse
So you were just able to go through the Rootzwiki method? Were you stuck at "Downloading...Do not turn off target !!" screen when you went to boot screen originally? My device still can't be detected :/

Bricked Watch -- Help!!

I rooted the watch successfully and then attempted to revert to stock using the instructions here: http://forum.xda-developers.com/huawei-watch/development/guide-return-to-stock-huawei-watch-t3219596
. Midway through the restore of the system.img, my computer crashed and now the watch is stuck at the Huwaei logo. I can no longer connect to the watch over adb - attemps to do so show that the watch is "offline." Is all hope lost or is there anything I can try?

No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Edit...if it shows connected but offline, just try unplugging it and plugging it back in again.
Sent from my Nexus 6 using Tapatalk

brizey said:
No one has figured out a way to boot directly to the boot loader yet...there has to be a way, just need to find it.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.

davpel said:
Okay. I'll keep checking back. BTW, I looked back at the terminal window which reopened when my computer restarted and the last thing posted there was "restored" so it may not have been my computer restarting which caused the issue. For this reason, I would strongly caution anyone who is thinking about using the system restore files in the linked thread. Better safe than sorry.
Click to expand...
Click to collapse
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.

brizey said:
Hey man, try unplugging and plugging it back in, then quickly doing an adb reboot bootloader. I have found that adb goes offline when in ambient mode, so you may get a brief chance to get it to the bootloader.
Edit:
Ah hah! You have to adb root to get it to work in ambient mode.
Man, we need a mechanical way to boot to bootloader.
Click to expand...
Click to collapse
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!

If you can get into the bootloader, maybe try restoring these instead? http://forum.xda-developers.com/huawei-watch/general/huawei-watch-stock-rooted-images-t3224930

davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.

brizey said:
I have my TWRP backup if you need it. I looked at it and it looks OK...typical image with the folders and SELinux context files. But...it is a rooted image.
Click to expand...
Click to collapse
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?

davpel said:
Yeah, I think I'm screwed. When I do adb devices, my computer sees the watch and gives back the serial number but shows its offline. I've tried some of the tricks to get into the LG Watch and 360 bootloaders, but they don't work with the H watch. Also, my watch never really shuts off. It is stuck at the logo. If I hold down the power button, it will eventually turn to black for about a 1/2 second, then boot immediately back into the log and give two vibrations. But never the bootloader. Ugh!
Click to expand...
Click to collapse
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.

davpel said:
Thanks, but unless/until I can get into the bootloader, I'm stuck. Right?
Click to expand...
Click to collapse
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.

1/4 Life said:
If if's anything like the Moto 360, you should be able to power the watch off, and then hold the power button for ~30 seconds to achieve boot to bootloader.
Click to expand...
Click to collapse
Tried that. I get the double vibration, but no bootloader.

FWIW, I just looked at a few of the 5.1 OTAs for other watches. I think the OTAs will work even if rooted. I looked at skin1980's init autoroot script, and I don't think it really touches any of the base system files...it only adds in the binaries. The updater script does a hash on all of the files that it is going to patch, then patches them if the hashes are OK. Given that we are not really touching the system files by flashing a custom ROM, I think we can make the OTA zips work. The kernel will likely not flash, but we can always build a new one from source if needed.

brizey said:
Hmmm...just noticed that tiny's and skin's system images are not the same. Different sizes.
Click to expand...
Click to collapse
And i dont know why. I dd them like i said and they are completely stock.

davpel said:
Tried that. I get the double vibration, but no bootloader.
Click to expand...
Click to collapse
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)

1/4 Life said:
http://forum.xda-developers.com/g-watch-r/development/fastboot-mode-lg-g-watch-r-t2946955 (?)
Click to expand...
Click to collapse
Thanks, but tried the LG method as well (both the swipe and the tap) and had the same results -- or lack thereof.

Has anyone else tried restoring to stock with success from Skin's files?

myke66 said:
Has anyone else tried restoring to stock with success from Skin's files?
Click to expand...
Click to collapse
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.

Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!

Skin1980 said:
@davpel watch has been successfully restored with the system.img i posted. BTW the fastboot flash system system.img doesn't work properly, i will update my thread with the new HOWTO.
Click to expand...
Click to collapse
davpel said:
Yes, my watch is working great, thanks to Skin1980. This community is very lucky to have him!
Click to expand...
Click to collapse
Agree 100%. I am returning my first watch, and flashed it back to stock and relocked the bootloader with no issues using the revised instructions. Going to keep my new one stock I think...got to cut down on the toys (Nexus 6, Nexus 7, iPhone 5s, custom PC, G37, surveillance system, house LED lighting conversion, etc. etc. Momma ain't happy, and I really want to spend more time with the kiddos.)

Who the hell needs to ROOT a damn smart watch?! I could see when it was 2 years ago with the first Samsung smart watch to sideload Android apps but this.... This is just stupid. Congrats
Sent from my SM-N910T using Tapatalk

Bricked?!?

Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.

Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again

And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.

if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all

Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.

warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.

So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?

Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked

If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!