Develop Bugs

i think the froyo update bricked my phone

this is what i got after the update (image).
what does that mean and what should i do now?

Is your phone rooted?

Hold up volumne and hit the power button and the same time.
Then when the menu appears, hit the power button while "reboot" is highlighted.
Nothing much to it usually

Nit3m4re said:
Is your phone rooted?
Click to expand...
Click to collapse
no it's not, i didn't do any kind of manipulation to it.
To prevent spam to the forums, new users must wait five minutes between posts. All new user accounts will be verified by moderators before this restriction is removed.
Click to expand...
Click to collapse
im already mad but this is just....ggggggrrraaasdfasd....

shotten99 said:
Hold up volumne and hit the power button and the same time.
Then when the menu appears, hit the power button while "reboot" is highlighted.
Nothing much to it usually
Click to expand...
Click to collapse
do you mean the bootloader menu? i get 4 options:
fastboot
recovery
clear storage
simlock
i selected recovery, then i got the reboot option.
the phone just hanged on startup (white background, green HTC logo).
selecting recovery gives me the same error i described in my first post.

is your phone debranded?
Anyway, you should probably run 1.21 RUU from fastboot to return to previous rom

djoni1980 said:
is your phone debranded?
Anyway, you should probably run 1.21 RUU from fastboot to return to previous rom
Click to expand...
Click to collapse
nope, it's an unbranded phone. what's 1.21 RUU?

shotten99 said:
Hold up volumne and hit the power button and the same time.
Then when the menu appears, hit the power button while "reboot" is highlighted.
Nothing much to it usually
Click to expand...
Click to collapse
whoops, now i got it...
i did that but it didn't help.
that menu also gives me the option to apply the update again (sdcard:update.zip) but it says it can't find the zip:
'E:failed to open /sdcard/update.zip (No such file or directory)'
'E:signature verification failed'
'Installation aborted'

preller said:
nope, it's an unbranded phone. what's 1.21 RUU?
Click to expand...
Click to collapse
download http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126984_signed.exe to your pc
turn phone on in fastboot mode (back+power)
connect phone to pc via usb
run ruu from pc
hopefully that will lead you to safety of 1.21 rom

djoni1980 said:
download http://shipped-roms.com/shipped/Bra...00.28U_4.06.00.02_2_release_126984_signed.exe to your pc
turn phone on in fastboot mode (back+power)
connect phone to pc via usb
run ruu from pc
hopefully that will lead you to safety of 1.21 rom
Click to expand...
Click to collapse
this would break my guarantee, right?
i'm going to try to update it again, i found the official froyo update here:
http://liveimage.htc.com/OTA_Bravo_Froyo_HTC_WWE_2.09.405.8-1.21.405.2_release4dua3bcrut4wrv30.zip
edit:
that helped. my phone is alive again...

djoni1980, I just need to say..
Youre my hero!! My stock phone displayed the same problem. Tried your solution and now i am back in business! thank you VERY much!!!

I suggest to both of you to root phones using unrevoked, and then flash radio and rooted froyo when it arrives (later today ).
It is actually much safer - you can backup everything with titanium, do nandroid backup from recovery, wipe everything before you flash (which could be the cause of boot loop), and restore everything after successfull installation with titanium

djoni: kako to uraditi, može na PM?

preller said:
this would break my guarantee, right?
i'm going to try to update it again, i found the official froyo update here:
http://liveimage.htc.com/OTA_Bravo_Froyo_HTC_WWE_2.09.405.8-1.21.405.2_release4dua3bcrut4wrv30.zip
edit:
that helped. my phone is alive again...
Click to expand...
Click to collapse
I may sound a bit dim here, but how did you update with this file?
I have the same problems as you btw.
I have renamed it to update.zip as i've read elsewhere, but when i select reboot from the bootloader menu i just get returned to the same situation.

SkinBobUk said:
I may sound a bit dim here, but how did you update with this file?
I have the same problems as you btw.
I have renamed it to update.zip as i've read elsewhere, but when i select reboot from the bootloader menu i just get returned to the same situation.
Click to expand...
Click to collapse
go into the bootloader menu and click on recovery. now you should see this error-image i've posted. press volume up and power button. a new menu should appear wear you can choose to apply the update manually.

my Lg pad wont boot up. pls help see Image

after I tried unsuccesfull to Install a custom rom I got this msg and my lg pad wont start anymore...
can any1 help me pls? see Image at attachments.

No attachment. Do you get LG logo and bootloop? If so, don't worry mate.

CuraeL said:
No attachment. Do you get LG logo and bootloop? If so, don't worry mate.
Click to expand...
Click to collapse
there Is now. pls help me mate

Aha, did you use the wrong recovery? I'm gonna take a blind-shot and think that you did. ;/ So maybe you cannot flash CM on it. It is common mistake. - What you are seeing right now is the stock LG charging pre-system. I think you have wiped the image from the system, so it shows you the RAW data instead.
Well, let it charge to 20-25%
Then do this:
1. Unplug the tablet from charger and let it turn fully off.
2. Press and HOLD Volume Down + Power Button.
3. On LG Logo appear, ONLY release Power key, still holding Volume Down. Then quickly press and hold Power and Volume UP also. So now you hold all three buttons. So you need three fingers.
This should take you to "Factory Reset", but when you have custom recovery, you can press Power and you will come to custom recovery. I think you can mount the external SD card and then flash a new recovery. Go find PhilZ recovery in the Original Android Development sub-forum here. You just flash the Zip inside of TWRP. When that is done, reboot and repeat the steps on the top of this post, then flash CM.
Keep on trying the key combo, it is a bit tricky, but it works. While you try and get to recovery, download PhilZ CWM touch and prepare the SD card on your computer, if you have the option.
Good luck.

CuraeL said:
Aha, did you use the wrong recovery? I'm gonna take a blind-shot and think that you did. ;/ So maybe you cannot flash CM on it. It is common mistake. - What you are seeing right now is the stock LG charging pre-system. I think you have wiped the image from the system, so it shows you the RAW data instead.
Well, let it charge to 20-25%
Then do this:
1. Unplug the tablet from charger and let it turn fully off.
2. Press and HOLD Volume Down + Power Button.
3. On LG Logo appear, ONLY release Power key, still holding Volume Down. Then quickly press and hold Power and Volume UP also. So now you hold all three buttons. So you need three fingers.
This should take you to "Factory Reset", but when you have custom recovery, you can press Power and you will come to custom recovery. I think you can mount the external SD card and then flash a new recovery. Go find PhilZ recovery in the Original Android Development sub-forum here. You just flash the Zip inside of TWRP. When that is done, reboot and repeat the steps on the top of this post, then flash CM.
Keep on trying the key combo, it is a bit tricky, but it works. While you try and get to recovery, download PhilZ CWM touch and prepare the SD card on your computer, if you have the option.
Good luck.
Click to expand...
Click to collapse
thanks for your reply.
yes I did use the wrong recovery, as a matter of fact I didnt know which one to use so I choose one randomly
the bad thing I did what u said. and nothing happened .. still stuck at the lg logo and Is not charging anymore...

Keep on trying the key combo. Hold power + volume down, when logo comes, release power, still hold volume down, then also hold power and volume up, so you hold all 3 buttons. But never release volume down.

CuraeL said:
Keep on trying the key combo. Hold power + volume down, when logo comes, release power, still hold volume down, then also hold power and volume up, so you hold all 3 buttons. But never release volume down.
Click to expand...
Click to collapse
hey man thanks for ur post.
I did what u said and It appears a factory reset mode and then I hit power to do a factory reset and then reset with the lg logo being stuck again :/ any luck?
thanks

ANTRIK said:
hey man thanks for ur post.
I did what u said and It appears a factory reset mode and then I hit power to do a factory reset and then reset with the lg logo being stuck again :/ any luck?
thanks
Click to expand...
Click to collapse
No custom recovery. Hn, we must do another thing then, wait a second. I must find a text and copy it to you from another post, brb. We must go to download mode instead when no recovery.

I did what u said and It appears a factory reset mode and then I hit power to do a factory reset and THEN A TEAM RECOVERY STARTS AGAIN AND LG LOGO STUCK AGAIN

ANTRIK said:
hey man thanks for ur post.
I did what u said and It appears a factory reset mode and then I hit power to do a factory reset and then reset with the lg logo being stuck again :/ any luck?
thanks
Click to expand...
Click to collapse
Here is quote from someone else I found in another place but shutdown the thread without thinking.
I use the download mode to install the original official rom.
1. Download the LG MOBILE SUPPORT TOOL by this link:http://www.lg.com/us/support-mobile/lg-V500-White
2. install the software in computer, Plug in USB cable with computer, Open the software LG MOBILE SUPPORT TOOL.
3. Turn off Pad and unplug.
4. press hold both volume up and volume down, Then plug in usb cable, And then pad is in downlaod mode
5. USB driver will be insatlled automatically
6. In LG MOBILE SUPPORT TOOL, click option---.country and language-OK, then click option--upgrade recovery
7. It will installe original official rom automatically.
8. After about 1.5 hours, The pad will be installed the last official room.
^ This is a quote and now I shut down the thread, sorry, don't know who said it, just got stoked when I saw it.
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
ANTRIK said:
I did what u said and It appears a factory reset mode and then I hit power to do a factory reset and THEN A TEAM RECOVERY STARTS AGAIN AND LG LOGO STUCK AGAIN
Click to expand...
Click to collapse
What? You got recovery booted but it restarted itself again to LG screen? If you can, just stay in recovery.

CuraeL said:
No custom recovery. Hn, we must do another thing then, wait a second. I must find a text and copy it to you from another post, brb. We must go to download mode instead when no recovery.
Click to expand...
Click to collapse
lol I was there
download mode please do not uplug...
but I turned It off
dont know how do I get there ;p

ANTRIK said:
lol I was there
download mode please do not uplug...
but I turned It off
dont know how do I get there ;p
Click to expand...
Click to collapse
Click on PC SYNC and download the only file, PC Suite, it has program in it. Then follow guide.
http://imgur.com/kzHc2sa

CuraeL said:
Click on PC SYNC and download the only file, PC Suite, it has program in it. Then follow guide.
http://imgur.com/kzHc2sa
Click to expand...
Click to collapse
thank you so much man you saved my life
I did everything u said and Its working again .
In order to Install cm11 which recovery should I use? I used this one before twrp 2.6.3.0.img awifi

ANTRIK said:
thank you so much man you saved my life
I did everything u said and Its working again .
In order to Install cm11 which recovery should I use? I used this one before twrp 2.6.3.0.img awifi
Click to expand...
Click to collapse
Go into http://forum.xda-developers.com/showthread.php?t=2551499 and scroll down to downloads.
You are on stock ROM, meaning you wanna go and check in your system settings - about tablet for the software information. Choose one of the three: V50010a, V50010c or V500e. Download the right one for your device. Then a few lines lower, download "Loki" from the link.
Enable developer settings in your Tablet and follow the adb instructions in the thread. This is the TWRP you need to flash a KitKat rom. The older versions will fck up your device. - Remember to root before you begin!

CuraeL said:
Go into http://forum.xda-developers.com/showthread.php?t=2551499 and scroll down to downloads.
You are on stock ROM, meaning you wanna go and check in your system settings - about tablet for the software information. Choose one of the three: V50010a, V50010c or V500e. Download the right one for your device. Then a few lines lower, download "Loki" from the link.
Enable developer settings in your Tablet and follow the adb instructions in the thread. This is the TWRP you need to flash a KitKat rom. The older versions will fck up your device. - Remember to root before you begin!
Click to expand...
Click to collapse
hey man thanks for ur reply.
so far we are In the same page
I downloaded v50010a which Is my devIce then loki zip
but I have no Idea what Is cdm and adb I tried to open cmd and run thoose commands but I getting eroor adb not support something like that.
although I download adb.exe and fastbook and Installed It.
Is It any way to flash recovery though my tablet like goo apps or rom manager ?
thanks.

Go here, http://forum.xda-developers.com/showthread.php?t=2553192
Read first post, donwload and enable developer options on Tablet.
Then download and run the .bat file. Then you get root.
Then you go download the V50010a.lok file and you rename the file to V50010a.img instead.
Then you go to market on phone and search for "Flashify", and you flash the .img in there. (I don't use it, but many people does.)
I recommend you study a bit on adb and fastboot for another time, since if anything crashes, adb is the way to go. Not Flashify. But for now Flashify GUI should be fine. Just remember the root first.
This is the last question I will help you with since all of your questions has been in other threads and you should be able to find them in the forums.

CuraeL said:
Go here, http://forum.xda-developers.com/showthread.php?t=2553192
Read first post, donwload and enable developer options on Tablet.
Then download and run the .bat file. Then you get root.
Then you go download the V50010a.lok file and you rename the file to V50010a.img instead.
Then you go to market on phone and search for "Flashify", and you flash the .img in there. (I don't use it, but many people does.)
I recommend you study a bit on adb and fastboot for another time, since if anything crashes, adb is the way to go. Not Flashify. But for now Flashify GUI should be fine. Just remember the root first.
This is the last question I will help you with since all of your questions has been in other threads and you should be able to find them in the forums.
Click to expand...
Click to collapse
YES! YES! YES!
I did It Installed cm11
thanks man for your time!
u know good things happen to good people. and u re a good guy
god will reward you!
thanks.

ANTRIK said:
YES! YES! YES!
I did It Installed cm11
thanks man for your time!
u know good things happen to good people. and u re a good guy
god will reward you!
thanks.
Click to expand...
Click to collapse
Happy to help, see you on the forums.

Can someone please help me

I was trying to update my phone and something most likely went wrong. Then the update installed and screwed up my phone. When I turned it on it stayed on the startup for so long. I tried to clear cache through the bootloader, but now it shows the android screen of death except it flashes. This occurs even outside the bootloader.
I am rooted with stock os.
Thanks in advance to whoever helps

Flash it with the original firmware

anfalanl said:
Flash it with the original firmware
Click to expand...
Click to collapse
Yup, same thing happened to me, I had to reflash it to stock firmware.

How would i flash
Magister54 said:
Yup, same thing happened to me, I had to reflash it to stock firmware.
Click to expand...
Click to collapse
Hey, thanks for the response.
Could you please elaborate on how I would do this. Because I do not understand how to do this if the bootloader doesn't work.
Thanks, your response and input means alot

Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"

Magister54 said:
Take the firmware from Asus website, for me I took UL-Z00A-WW-2.19.40.22-user.zip
Boot the phone in bootloader and try to go in the recovery screen, it took me a lot of tries to get in it!!!
From here you can select "insall update from ADB"
From your PC you do a "adb sideload UL-Z00A-WW-2.19.40.22-user.zip"
Click to expand...
Click to collapse
When i try to do this, i see the error sign but it is flashing

hudasameer450 said:
When i try to do this, i see the error sign but it is flashing
Click to expand...
Click to collapse
That's normal. When you get the error sign when booting into stock recovery, hold power down and press volume up and quickly release both buttons at the same time. If done correctly recovery menu will pop up and then you can start actually flashing.

Flashing
does this still work if the screen is flashing, because I tried before and it did not work, maybe I pressed it wrong or there is some other issue.
Thanks

Help about Pixel C !!

Hello,
This is the third time I've asked you for help. This time it is, it always concerns google pixel C. Everything worked so well. But today, by simply taking a picture, the device turns off and on again on the google logo. Then the android robot with a red alert appears. the word "No command" just below. I can navigate the recovery. But impossible to go into "android recovery" with the menus to apply sideload ota.... I sincerely think it is brick and I'm really very afraid that I won't be able to use the guarantee despite having locked the bootloader before. I was on the official Android 7.1.2 software. The adb and fastboot commands detect the tablet. But I can't unlock the bootloader or flash... I have no idea what to do, I could use your help please!!!!!!!!

Hawkeye5 said:
Hello,
This is the third time I've asked you for help. This time it is, it always concerns google pixel C. Everything worked so well. But today, by simply taking a picture, the device turns off and on again on the google logo. Then the android robot with a red alert appears. the word "No command" just below. I can navigate the recovery. But impossible to go into "android recovery" with the menus to apply sideload ota.... I sincerely think it is brick and I'm really very afraid that I won't be able to use the guarantee despite having locked the bootloader before. I was on the official Android 7.1.2 software. The adb and fastboot commands detect the tablet. But I can't unlock the bootloader or flash... I have no idea what to do, I could use your help please!!!!!!!!
Click to expand...
Click to collapse
Have you tried this?
"Turn off GOOGLE PIXEL C. Press and hold together : Power Button + Volume Down until Logo appear at LCD screen. If we see the menu at LCD screen, choose Wipe Data/Factory Reset with Volume Button to select and use Power Button to ok or enter."

Are you sure I can do that? Because I had downgraded Android from version 8.1.0 to 7.1.2 because I had a problem with 8.1.0. Therefore I had unlocked the bootloader etc.... So the data had been erased! If I do a wipe data/Factory reset will it work at least at 90/95% ? Despite having only installed the Factory image (without OTA) can it work without doing a bootloop or other...?

braunie said:
Have you tried this?
"Turn off GOOGLE PIXEL C. Press and hold together : Power Button + Volume Down until Logo appear at LCD screen. If we see the menu at LCD screen, choose Wipe Data/Factory Reset with Volume Button to select and use Power Button to ok or enter."
Click to expand...
Click to collapse
Well, I tried and I always fall back on the page with the robot and the inscription "no command" just below. I'm sad ?

If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).

braunie said:
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
Click to expand...
Click to collapse
The bootloader is locked. This is the end. Is there any advice I can try to send it to the after-sales service?

braunie said:
If the bootloader is unlocked you maybe have a chance by install TWRP and then install LineageOS 15.1 (wich is much better than stock).
Click to expand...
Click to collapse
Tell me, the OTA file is used to apply an update, right? Because I tried to do this manipulation but by downloading Exactly the same software and it didn't work. So if I try with a more recent version of Android, it should work, right?

Hawkeye5 said:
Tell me, the OTA file is used to apply an update, right? Because I tried to do this manipulation but by downloading Exactly the same software and it didn't work. So if I try with a more recent version of Android, it should work, right?
Click to expand...
Click to collapse
Sorry, but I don't know this. If the bootloader is locked I have no further idea.
Maybe somebody else has an idea???

braunie said:
Sorry, but I don't know this. If the bootloader is locked I have no further idea.
Maybe somebody else has an idea???
Click to expand...
Click to collapse
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!

Perfect!
---------- Post added at 03:20 PM ---------- Previous post was at 03:20 PM ----------
Hawkeye5 said:
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Click to expand...
Click to collapse
So I may ask you for help if I have the same problem

Hawkeye5 said:
Okay, I found the solution. The OTA image had to be installed. I am happy. Everything seems to be working for now. And yes, the ota image can be installed without unlocking the bootloader!
Click to expand...
Click to collapse
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks

Jmash79 said:
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Click to expand...
Click to collapse
Hi, if your device is a C pixel, you can try to check it out here: https://developers.google.com/android/ota
To sum up, my problem was the following: suddenly, my tablet could no longer boot on android but on the page where the robot was displayed with a red panel and the indication "no command".
And the solution was the following: being on Android 7.1.2 I had to download Android 8.1.0 for the "update" to work. So I followed all the steps indicated by the site I provided you. That is, having Fastboot and adb working, then putting the.Zip file of your android in the same folder as adb and Fastboot. Then you follow the different steps shown on the site to download the ota image. My explanation is not great so if you have a question about something specific let me know. And if you can send screenshots of your worries it will help.
Good luck with that!

Jmash79 said:
How did you fix it
I had the same exact same fault in December and couldn't work out how to fix. I thought my tablet was just a paperweight now but would be so happy if i could fix it.
do you have a link to the method you used or can you provide more details on how to fix?
what do you mean by the OTA image had to be installed?
Each time I tried to copy the image from my computer to the tablet it failed.
would be grateful for any help.
thanks
Click to expand...
Click to collapse
Hi, if your device is a C pixel, you can try to check it out here: https://developers.google.com/android/ota
To sum up, my problem was the following: suddenly, my tablet could no longer boot on android but on the page where the robot was displayed with a red panel and the indication "no command".
And the solution was the following: being on Android 7.1.2 I had to download Android 8.1.0 for the "update" to work. So I followed all the steps indicated by the site I provided you. That is, having Fastboot and adb working, then putting the.Zip file of your android in the same folder as adb and Fastboot. Then you follow the different steps shown on the site to download the ota image. My explanation is not great so if you have a question about something specific let me know. And if you can send screenshots of your worries it will help.
Good luck with that!
Translated with www.DeepL.com/Translator

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