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

Used WugFresh to relock and return to stock...have no idea WTF happened

the whole process went through fine. then at the end it says your device will take 5-10 minutes to reboot. its been 20 minutes and im still stuck at the recovery screen (whatever the screen is called where the droid's stomach is open)
i tried booting into the phone and i can but im still not stock so this obviously isn't working for whatever reason.
any thoughts?

I don't know but the toolkit forum would be the place to ask or read the FAQ on the toolkit.

Next time, don't use a toolkit. Use fastboot.
Sent from a juiced Galaxy Nexus

fux0r99 said:
I don't know but the toolkit forum would be the place to ask or read the FAQ on the toolkit.
Click to expand...
Click to collapse
thanks ill give that a shot...

DroidOnRoids said:
Next time, don't use a toolkit. Use fastboot.
Sent from a juiced Galaxy Nexus
Click to expand...
Click to collapse
I'm continually amazed that so many people will literally waste more time trying to get a toolkit to work than it would take for them to learn how to use adb/fastboot, and punch in the commands.
I looked at a toolkit once to see what all the hubub was about. It took longer to read the options on screen than it did to learn all adb commands.
Sent from my Galaxy Nexus

Chances I messed something up? Where do I go from here? Uninstall drivers?
Need some hand holding because I really need it back to stock by weekend end

theboywonder said:
Chances I messed something up? Where do I go from here? Uninstall drivers?
Need some hand holding because I really need it back to stock by weekend end
Click to expand...
Click to collapse
we dont know, you used a toolkit. it tells you nothing really.
learn fastboot, there is a thread about the whole return to stock with detailed instructions.

If you can, get into the stock recovery and wipe cache and data. I've gotten stuck at the Google screen once before when I relocked and flashed stock images. Oh and the three posts above are all correct, this is a Nexus, no need for tool kits.

Did system gave you error or something when flashin....i dont know, it is a toolkit!
Did you flash userdata....i dont know, it is a toolkit!
........................ !
any way boot into recovery and wipe data and cache, reboot
How can i put my Gnex in fastboot/recovery mode?
Turn off your phone, press and hold down Volume Up and Down keys + Power button at the same time until fastboot (bootloader) mode (image of an Android with Start) appears then release the keys. Press volume up or down and select recovery by pressing power button. (For stock recovery, when you see an android logo with exclamation mark, press power + volume up to see the recovery menu).
Click to expand...
Click to collapse
if it didnt work, flash stock images manually with fastboot commands

[Q] [Bad Update] Nexus 7 came in today, tried to root...

Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
UPDATE: So it wasn't bricked it, as I was able to return to the home screen. After a day of using it though, with the Nexus being buggy (freezing and crashing), it just died. I can't boot it or anything. It's plugged in, but nothing's happening.

Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Download factory image and do a factory restore:
https://developers.google.com/android/nexus/images#razorjss15q
I personally don't like toolkit. Recommend to root it yourself step by step.

I, being very technically unsavvy, have no idea what to do with the images.

Alright, here's the good news. You haven't bricked your nexus. You can and will fix this yourself, without a tool kit.
Read this thread:
http://forum.xda-developers.com/showthread.php?t=2379797
Then read it again and again until you understand the steps to fix your tablet. I was in your shoes once, years before toolkits were available and I learned how to fix worse problems then you have currently. Take your time.

Desperate User said:
I, being very technically unsavvy, have no idea what to do with the images.
Click to expand...
Click to collapse
Great user name given what you just posted

Desperate User said:
Well, as the title suggests, I just got my new Nexus 7 in the mail. Played around with it, definitely liked it. I wanted to get it rooted and used this guide on the website to try to root it. I installed the drivers, enabled debugging and developer mode and USB debugging, saw the serial as it said, and then I unlocked the bootloader and tried to root my tablet. Things started to get wonky. The toolkit said that it was completed, but my tablet stuck on the loading 4-colored X screen. It's been about 30 minutes and I'm thinking that my device is bricked. Then I tried to restore the device but the toolkit isn't recognizing the tablet. How do I restore my tablet, or do anything with it?
Please help, as I don't want to waste $220 on 4 hours of having a working Nexus 7.
Click to expand...
Click to collapse
Same thing happened to me a month ago. Most important thing, don't freak out. Hold power for 20sec to hard reboot, then as soon as google logo appears hold down volume button to enter bootloader screen. From there you can do anything

http://forum.xda-developers.com/showthread.php?t=2391301

Did you boot into the phone after you unlocked the bootloader but before you tried to root? Do you have a custom recovery installed?

doe you have a custom recovery?
if so check if you still have your internal storage, i had the same problem as you but there is a bug going around when u unlock your bootloader your internal memory is wiped see this threat for feather explaining: http://forum.xda-developers.com/showthread.php?t=2380913
In my case i booted to fastboot and did the command fastboot -w and then it created new user partitions and then i could flash the stock image and then it worked again
Hope i helped u

No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't

hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app

HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't know, maybe you should make your own thread rather than hijack mine.

Desperate User said:
No custom recovery, but I have an update:
So after using the vol- and power buttons, I was able to bring the Nexus back to its home screen for a day (so it wasn't bricked), but it was really buggy- freezing on my and shutting down. Now though, I think it's bricked; I can't power it up, can't do anything. So I can't turn it on now :/. Probably gonna take it to see a repair store sometime soon.
@bananagranola: no I didn't
Click to expand...
Click to collapse
owh, does it al least charger when u plug it in?

silvan g said:
owh, does it al least charger when u plug it in?
Click to expand...
Click to collapse
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.

Desperate User said:
I can't tell. The damn thing doesn't respond to anything.
Click to expand...
Click to collapse
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down

HuxenShah said:
hey my nexus 7 flo came with jwr66n ... i have experience no issue in this build but... i am receiving a notification to update..... should i update even if have no issue on jwr66n ...?? or will it be a risk...
Click to expand...
Click to collapse
If you're not rooted, it's just a stock update. There isn't any more risk than there is for any stock version, and you shouldn't lose data. If you buy a Nexus 7 2013 a few months down the line, after current stock with JWR66N is sold out, I believe it'll come with that update out of the box.
Desperate User said:
I don't know, maybe you should make your own thread rather than hijack mine.
Click to expand...
Click to collapse
I understand you're frustrated, but that was a little rude...he's just trying to get help, just like you.
Desperate User said:
I can't tell. The damn thing doesn't respond to anything. It's plugged into the wall right now and not doing anything. My PC doesn't recognize that it's plugged in.
Click to expand...
Click to collapse
Unrecognized in ADB or fastboot? Can you get into bootloader (boot while holding power and volume-down)? If you haven't tried fastboot while the phone is in the bootloader, and you can get into bootloader, try "fastboot devices." If you can do that, download a custom recovery and flash it from fastboot. Then format data and reboot.

silvan g said:
Try plugin it in the charger and wait 5 min and then try to boot it with power+volume down
Click to expand...
Click to collapse
Done and nothing

Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img for the LTE or fastboot boot openrecovery-twrp-2.6.0.0-flo.img for the WiFi version.
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.

Guhrasoh said:
Download the platform tools: http://www.androidfilehost.com/?fid=9390355257214632011 and
TWRP for the WiFi: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.0.0-flo.img or LTE version: http://techerrata.com/file/twrp2/deb/openrecovery-twrp-2.6.0.0-deb.img
Unpack the platform tools zip into a folder, copy the openrecovery-twrp-2.6.0.0-deb.img file into the same folder and open a command prompt into this folder (hold shift while right clicking on the folder and the option should be there).
Try to turn the nexus off by holding the power button for 30 secs, connect it via USB to your PC and wait till the screen shows the white charging information. Now press the volume down button on the nexus and keep holding it while you press the power button. After a moment you should see the green android with the open belly and some device information on the screen.
Now go to the command prompt you opened and enter: fastboot boot openrecovery-twrp-2.6.0.0-deb.img
After a few seconds you should see the recovery screen, if it asks you for a password just hit cancel, there choose "Wipe" and then "Format Data" and confirm that you want to format data. After it has done its stuff go back to the main menu and choose reboot and let it boot into system. Now it should work again.
Click to expand...
Click to collapse
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.

Desperate User said:
That would be great, but when I plug in the tablet to the PC the screen doesn't show any information. That and I can't turn on my Nexus in any way, including the volume down and power method.
Click to expand...
Click to collapse
How long has it been charging? I'd give it a couple hours, then try the bootloader again.

[q] help ! Nexus wont go in recovery mode or boot at all !

Hi all, I am fairly new to the world that is custom ROMS and custom recovery. I am not very experienced with either of these things but right now have an issue to deal with.
I have a samsung galaxy nexus i9250gt that was sold to me from a friend. He claimed that the phone was in a constant reboot cycle and no matter what he tried he was not able to get out of it. I decided to take on the challenge and have so far been unsuccesfull.
So, what I have done so far is download a galaxy nexus tool kit v11.0 and try flashing the stock google rom on to it. Did not work.
Also tried using odin to flash a stock rom on to it. Still the same issue.
The screen I seem to get is a Google logo with a unlocked lock near the bottom. The phone vibrates and then shows this screen before repetitively doing so till the battery dies.
I can sometimes get in to fastboot mode and CANNOT get in to recovery mode. The phone will sometimes just restart when i select recovery mode or it will show a dead android with a red triangle and an exclamation mark. I do not really know what to do from here
REPEAT: PHONE WILL NOT GO IN TO RECOVERY MODE SUCCESSFULLY, WILL GO IN TO FASTBOOT MODE SOMETIMES.
I would really appreciate a step by step guide on how to get out of this.
Thank you.

Try another toolkit
wmalik81 said:
Hi all, I am fairly new to the world that is custom ROMS and custom recovery. I am not very experienced with either of these things but right now have an issue to deal with.
I have a samsung galaxy nexus i9250gt that was sold to me from a friend. He claimed that the phone was in a constant reboot cycle and no matter what he tried he was not able to get out of it. I decided to take on the challenge and have so far been unsuccesfull.
So, what I have done so far is download a galaxy nexus tool kit v11.0 and try flashing the stock google rom on to it. Did not work.
Also tried using odin to flash a stock rom on to it. Still the same issue.
The screen I seem to get is a Google logo with a unlocked lock near the bottom. The phone vibrates and then shows this screen before repetitively doing so till the battery dies.
I can sometimes get in to fastboot mode and CANNOT get in to recovery mode. The phone will sometimes just restart when i select recovery mode or it will show a dead android with a red triangle and an exclamation mark. I do not really know what to do from here
REPEAT: PHONE WILL NOT GO IN TO RECOVERY MODE SUCCESSFULLY, WILL GO IN TO FASTBOOT MODE SOMETIMES.
I would really appreciate a step by step guide on how to get out of this.
Thank you.
Click to expand...
Click to collapse
Download and install Nexus Root Toolkit v1.7.2 by WugFresh. Follow all instructions to configure your drivers correctly. Flash Factory Image using the fastboot method: On the toolkit startup window select Current Status: "Softbrick/Bootloop" then click "flash stock + unroot" follow the instructions....

when you see this dead android with exclamation mark, press power + volume up to see the recovery menu.
i suggest to read stickies in general section and take a look at gnex tips and tricks thread (see my signature) to know your phone better.
and dont forget to use SEARCH BUTTON.

imethodZ said:
Download and install Nexus Root Toolkit v1.7.2 by WugFresh. Follow all instructions to configure your drivers correctly. Flash Factory Image using the fastboot method: On the toolkit startup window select Current Status: "Softbrick/Bootloop" then click "flash stock + unroot" follow the instructions....
Click to expand...
Click to collapse
Did this and have the same result as before. I even waited the 10 minutes it told me too. The phone turned off and when i booted it back on it stayed in a boot loop.
Not sure what to do now as im still getting the same google logo with the unlock sign underneath.

samersh72 said:
when you see this dead android with exclamation mark, press power + volume up to see the recovery menu.
i suggest to read stickies in general section and take a look at gnex tips and tricks thread (see my signature) to know your phone better.
and dont forget to use SEARCH BUTTON.
Click to expand...
Click to collapse
The device does show the exclamation marked android but when i press the power button and volume + i get no response.

wmalik81 said:
The device does show the exclamation marked android but when i press the power button and volume + i get no response.
Click to expand...
Click to collapse
use fastboot to flash full stock images (see sticky in general section)
if it didnt work, i guess it is a hardware issue

Maybe the partition table is screwed, when flashing with ODIN, did you use a .pit file?
Maybe the bootloader is borked, have you tried using OMAPflash to try and restore it?

beekay201 said:
Maybe the partition table is screwed, when flashing with ODIN, did you use a .pit file?
Maybe the bootloader is borked, have you tried using OMAPflash to try and restore it?
Click to expand...
Click to collapse
did use a .pit file when using ODIN
I am going to try OMAPflash and see if i can work something out. if not i fear that I am screwed

Stuck in boot loop when rooting device with magisk

Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?

Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.

Larzzzz82 said:
Try rebooting into recovery. When you see the Android laying down and I believe it says no command, press the up button. This should bring you to another menu where ADB sideload is an option. you could then download the appropriate OTA from Google and sideload it to the phone.
Click to expand...
Click to collapse
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...

helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....

simplepinoi177 said:
when in Bootloader mode (where it shows your "baseband version" and such), you actually use the volume button to change around the different options to boot, and then the "on/off" button to select.
But it looks like you get it to show the red "recovery mode" and, I imagine, you intuitively pressed the "on/off button" to select it, but in the unlikelihood that that is the case, make sure you are not holding or pressing or "....clicking volume up" button while it's booting; that's probably where you're going wrong....
only once you're in the stock recovery mode -- with the android lying down, dead, and a red exclamation point coming out of it -- is where you press the "volume up" and power button together to see the options...
good luck and hope this helps....
Click to expand...
Click to collapse
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.

helpless_user said:
I tried this and I never get to the dead android screen. I just get to a screen that says that my bootloader is unlocked and then the Google logo is showing.
Click to expand...
Click to collapse
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .

helpless_user said:
Thanks for your reply. I pressed "On/off" button + volume down and got into menu with recovery mode. But selecting recovery mode with "on/off" button and then clicking volume up just brings me to a view with the google logo showing and then the phone turns off. I can't seem to access menu with ADB sideload unfortunately...
Click to expand...
Click to collapse
In fastboot you can boot to a recovery.img; fastboot boot twrp.img
Download TWRP .img here.
(that recovery menu allows adb mode also).
Here you can(re)flash zip/image etc.
Format /data to ensure it is not encrypted.
For example, flash the extracted images of the OTA images from Google.

simplepinoi177 said:
Hmmmm...it sounds like something's wrong with your boot partition, then -- that's where the recovery resides. I suggest re-downloading the latest Full Factory image (from Google's developers site), editing flash-all to remove the "-w" and "exit" at the end, then running the flash-all once again on your device.
....after reading your OP, one key thing to keep in mind is that, in Bootloader Mode, you use "fastboot" commands while you use "adb" commands when within the OS or recovery....
And, for future reference, it would be better (most likely) if you wish to root the taimen for you to follow THIS GUIDE: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 .
Click to expand...
Click to collapse
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.

helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!

Not able to figure out the exact fix
helpless_user said:
Thank you very much!! Running fastboot helped me do a factory reset and now my phone is working again! Thought my phone was bricked so this is a relief.
Click to expand...
Click to collapse
@OP, I am still stuck with the exact same issue. How did you exactly fix it? After running the solution given, I'm back at the infinite logo screen again.
Edit: It worked, thank you so much! This is a life saver.

simplepinoi177 said:
I'm real happy you got it back up and running!
Yeah, I'm not agreeing with all of what Google's doing now (in concerns with the Pixel 4 [i.e. removing unlimited original quality storage]), but they really did well with the whole "Bootloader Mode" where you can feel a bit more secure and confident that, as long as you have access to Bootloader Mode and can successfully connect your device, you're not too far gone and definitely bricked beyond hope! It's not so hopeless as with devices before and what the term "bricking" truly applies to....
Happy to have helped!
Click to expand...
Click to collapse
Hi i have the same issue with different device lenovo tab m10 tbx605L and i cant boot the recovery.img it throws me this error.Can u give me any ideas?

helpless_user said:
Hi,
I followed this guide on how to root the pixel 2: "androidcentral.com/how-root-google-pixel-2" and finished all the steps. But when running step 11 it got stuck in a boot loop due to some software issues with the patched image I assume.
I've tried opening the phone in fastboot mode and then connecting with ADB, but it seems I cannot find my device since USB-debugging is not turned on.
Any ideas of how this can be solved? Or am I screwed?
Click to expand...
Click to collapse
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
EDIT: Quoted the wrong poster. My reply is an answer to the quoted poster instead of the poster who revived a dead thread with a question for a totally different device.

Strephon Alkhalikoi said:
Did you install TWRP before rooting? If you did, that is the source of the bootloop. Our root guides here are much simpler than the one you provided the address to. The article in question is also out of date. Current versions of TWRP and Magisk don't play nice together. You need to BOOT TWRP using fastboot instead of installing it.
Copying the latest Magisk package to your internal storage, then renaming it to uninstall.zip and flashing it through TWRP should remove Magisk and resolve the bootloop. If that doesn't work, flashing the last stock package should.
Click to expand...
Click to collapse
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??

safaan0313 said:
unfortunately there is not an exact version of twrp recovery available for my device lenovo (tbx605L) even when i try to boot the stock recovery.img , it says FAILED (remote : unknown command) do you know what is causing this error??
Click to expand...
Click to collapse
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.

Strephon Alkhalikoi said:
I didn't realize you had replied to a thread that was two years old AND for the wrong device. Ask in the Lenovo section. This is the Pixel 2 XL section and advice given here is not applicable to you.
Click to expand...
Click to collapse
Hmm well thanks for your indirect F**k off

safaan0313 said:
Hmm well thanks for your indirect F**k off
Click to expand...
Click to collapse
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.

Strephon Alkhalikoi said:
I'm not sure you're aware of this, but not all devices are the same. Case in point: Samsung. How do you use fastboot commands on a Samsung device? Answer: You can't as Samsung doesn't support fastboot.
But thank you for making your expectations clear. Apparently, according to you, I should be able to figure out your problem despite not owning your device. It doesn't work that way. The only reason I know the answer to the question I posted in the previous paragraph is because I own a Samsung device.
Seriously, you getting bent out of shape at me because of your own screw-up is laughable.
Click to expand...
Click to collapse
Right I knew that.I am sorry.I was so damn angry at my own mistake.I AM S O R R Y.But off the record I just repaired my tab