Database Users

Nexus s stuck on "Google" icon when i start the phone

hi, my phone has stuck on the "google" icon when i start it. I have tried the "bootmode" you know when you hold volume and on/off button. There i tried to push on "reboot", "recovery", nothing is happening same thing. The only thing i have managed so far is installing driver usb for android phone in my computer, but i cant find the phonefolder in "My computer" to put reboot/update files to make the phone work.
How can i make the phone work? please help me im not so good at this.

please someone???

distortedloop said:
Everything you need should be in these two threads:
http://forum.xda-developers.com/showthread.php?t=878786
http://forum.xda-developers.com/showthread.php?t=895545
The second one has pictures and is very easy to follow.
Click to expand...
Click to collapse
Try this, thanks go to DistortedLoop

Check the links kenvan posted above.
You don't want to see the phone mounted as USB, you need to see it with the fastboot command from your DOS or unix terminal.
Then push ClockWork recovery to the phone.
From CW recovery you should be able to use it's tools to get you running again, or at least adb should work so you can mount storage and push files to it via adb.

I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
somii87 said:
hi, my phone has stuck on the "google" icon when i start it. I have tried the "bootmode" you know when you hold volume and on/off button. There i tried to push on "reboot", "recovery", nothing is happening same thing. The only thing i have managed so far is installing driver usb for android phone in my computer, but i cant find the phonefolder in "My computer" to put reboot/update files to make the phone work.
How can i make the phone work? please help me im not so good at this.
Click to expand...
Click to collapse

i have tryed this one : http://forum.xda-developers.com/showthread.php?t=895545
once i get to the phase where i select recovery in bootloader it just goes to the screen with the google logo and the unlocked padlock icon and it sticks there, any suggestions? i have tried to entering the recovery command again in the command prompt, still same problem =(

dinan said:
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
Click to expand...
Click to collapse
nothing the phone started to hang/freeze and then vibrating for about 40 seconds, i took out the battery the it was stucked in on the google icon.

dinan said:
I'd love to help you but I need a little more background... did you just buy the phone and this is happening? Or did you try rooting it and this is happening? Or did you just flash a different rom and this is happening?
Click to expand...
Click to collapse
kenvan19 said:
Try this, thanks go to DistortedLoop
Click to expand...
Click to collapse
i have tryed this one : http://forum.xda-developers.com/showthread.php?t=895545
once i get to the phase where i select recovery in bootloader it just goes to the screen with the google logo and the unlocked padlock icon and it sticks there, any suggestions? i have tried to entering the recovery command again in the command prompt, still same problem =(

Ok since you say you have a padlock on the boot screen, I assume you know how you unlocked the bootloader.
Turn the phone on into fastboot (hold power and volume up), then connect the phone to the computer via USB. Flash clockwork recovery (3.0.0.5 preferred) and then you should be able to enter clockwork recovery assuming you did it correctly. Push this rom (http://forum.xda-developers.com/showthread.php?t=884093) to your card and flash it in recovery.

dinan said:
Ok since you say you have a padlock on the boot screen, I assume you know how you unlocked the bootloader.
Turn the phone on into fastboot (hold power and volume up), then connect the phone to the computer via USB. Flash clockwork recovery (3.0.0.5 preferred) and then you should be able to enter clockwork recovery assuming you did it correctly. Push this rom (http://forum.xda-developers.com/showthread.php?t=884093) to your card and flash it in recovery.
Click to expand...
Click to collapse
Yes i know, can you be more specific`? step by step? im noob sorry for bothering you., how do i push to my card?

I have fixed my phone, my phone was liquid damaged. So i putted the hole mainboard in 100% alcohol and after 20 min i took it out and let it dry. And then it worked fine!

It just happened to me an hour ago. I tried for a few time to remove the battery and start it up (even with a new one). I also thought it might happen since the battery was drained so i let it recharge for a while with no success.
Eventually i attached the device to the computer's usb, waited and started it. and it worked.
Don't know if that was what solving it - but it back working.

[Q] Stock Nexus 4 bad install of 4.3 OTA

Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!

Jesmuris said:
Hello, I tried searching for this but came up empty. I have a completely stock Nexus 4, received the OTA push for 4.3. Phone has never been rooted. After going through the install process it showed the android on it's back with a red triangle and said error. After a restart the phone just sits at the Google screen!!! I'm I boned or is there a fix for this? Any info would be greatly appreciated! Thank you!
Click to expand...
Click to collapse
Try going into fastboot and flashing the stock rom from google.

gmaxpwnage said:
Try going into fastboot and flashing the stock rom from google.
Click to expand...
Click to collapse
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall

Jesmuris said:
Not sure what mode I entered, Held vlm down + power. Says Fastboot Mode in red with a big green Start at the top. Options it gives me is Start, restart bootloader, recovery mode, and power off. If I try to enter Recovery mode it says no command. Don't see anything that allows me to reinstall
Click to expand...
Click to collapse
Ok, found out on the no command screen I can hold power and hit vlm up and it brings me to system recovery with these options. Reboot system, apply update from ADB, wipe data/factory reset, wipe cache partition.
Not sure what to do sadly

Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot

Johnsonyc said:
Try following step:
1. Press Vol up and down and powerbutton same time to get to the fastboot mode as you mention.
2. Choice Recovery Mode and press power button. If you got luck you will see an android guy with red mark on the screen.
3. Press Vol Up and Power button same time for while don't let go it will pop up a list of option clean the cache and do factory reset, then reboot system.
If this method not working. Then hard method is flash your Nexus 4 with fastboot. Search the forum there few people already post how to flash 4.3 ROM with fastboot
Click to expand...
Click to collapse
Ok thank you, trying this now will update:good:

Didn't work Will try other method

Jesmuris said:
Didn't work Will try other method
Click to expand...
Click to collapse
Sorry to hear this bad news Hope the other method work for you!

Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I had a similar experience (kind of). I had issues side-loading 4.2.2 -> 4.3 on my N4. After it finished update and rebooted I got a black screen and nothing more. I ran through it and tried to update to 4.3 again, and then it worked.
Even though it worked I've been noticing issues with it. For example, I now can no longer uninstall anything. When I attempt to uninstall any app, the phone reboots. I'm backing up now with Titanium and am about to flash. I was hoping there would be a quick fix here, but such is life. Viva la impatience.

I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .

oneguy77 said:
I have same problem my stock 4.2.2 stuck x boot load , did vol up+dwn +power now stuck in "Download Mode" do not unplug the device until the process is complete .
Click to expand...
Click to collapse
This is what I eventually followed to get mine working. I just did scenario 2 and that worked perfectly for me, so far no issues, just having to get things back to where I had them before. The second link is actually more detailed. Just make sure you follow step by step. I guess i could have not done step D10 but wanted to make sure this route worked for me. Thank you again for those who pointed me in the right direction
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1

Jesmuris said:
Well, first try, couldn't get my PC to recognize fastboot in adb. Was getting frustrated beyond hell and had to walk away for a bit. Came back about an hour later and for some reason it finally recognized it... Back to the start screen like when I first bought the phone. So far working ok, except for being able to log into my google account... 2-step verification giving me issues now lol. Thank you again for your assistance. Very much appreciated!!:good::good:
Click to expand...
Click to collapse
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...

FYI if you flash to stock android 4.3 and you have the 16 GB Nexus 4, make sure that after you re-flash you have the full 16 GB and not 8 GB (unless you want to re-setup your phone twice like me). If you get this problem you can wipe cache and data from recovery and voila, all of your free space is back.
---------- Post added at 10:52 PM ---------- Previous post was at 10:44 PM ----------
zpilot said:
I have the exact same problem but not sure how to get my PC to recognize fastboot in adb mode...
Click to expand...
Click to collapse
If this is what I think it is, I was having the same problem. If I went into Control Panel on my PC and it would say that the driver is failing to load. To fix this I uninstalled the driver, rebooted, reinstalled Google USB Driver from the Android SDK Manager, restarted, and all was well after that.
I really have no explanation for why this fixed it, or it didn't work before, because other than fastboot, everything was working flawlessly with getting my phone to communicate with my PC.

Can't boot, tried flashtool, not going well, help

So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?

I think it's getting a model information check fail in lg flashtool, ugh this sucks.

bova80 said:
So heres my issue, ATT G2. Installed clean rom xe 1.1 then was dumb and used titanium to restore my app data, not system, just app. but someone that caused a system ui to keep crashing, so I got into recovery mode by holding down and power button (white screen that asks to reset to factory). Did that and it booted to TWRP ran a script and then went back to LG screen and then blank screen with flashing led and that's where it stayed, won't go any further.
I've put it in download mode now and am using LG flash tool but when I plug the phone in the box for COM41 in the flash tool just says waiting for connection and thats it. then when I unplug it it says failed, obviously. Is my phone a brick or can it be saved?
Click to expand...
Click to collapse
LOL, i just went through the same thing. I'll be posting a fix tonight I worked out with Scott.
"There is a "back door" method. This is why they updated TWRP by the way...
Download this: https://dl.dropboxusercontent.com/u/...with cmd.zip
Extract it to desktop. open the command.bat file.
Type "adb reboot recovery" then press enter. You need to keep doing this during the factory reset.
This assumes you have drivers installed. If you have no drivers installed for recovery mode then just select generic Google Nexus ADB drivers.
You kinda have to hammer the reboot recovery command. Its all timing... To hammer it... press the up arrow in the dos prompt and that will repeat the line. then press enter.
Keep doing it until you see it reboot to twrp and you should be able to sideload or load from storage.
It may take 10 or 15 minutes to get the exact right timing so dont give up.
And of course, this is all dependent upon you having the drivers already installed."
- Scott
For timing, you'll need to wait right when TWRP starts writing the script and start hammering it out. Timing is everything so when you see the TWRP screen starting hitting the up cursor and enter. It should load recovery. Don't bother using the tool, it won't work as it thinks your device is a D802 and won't be compatible with the dll. This will get you back to normal and from here you can just wipe and reinstall the rom again fresh with out losing media/data on the your drive.

I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated

MkV05 said:
I tried to download the file since I am in the same boat, but the dropbox is giving errors... Could you please repost the link to get the file? It would be greatly appreciated
Click to expand...
Click to collapse
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.

SamsungGalaxyStig said:
When I get home to my personal desktop I'll be able to upload the link again. It's not my drop box but I have the files to upload to drop box and repost.
Click to expand...
Click to collapse
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?

ccmbr002 said:
Awesome, been waiting for this! Just to confirm, will the same file work for someone with a Verizon G2 who's having the same problem?
Click to expand...
Click to collapse
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip

so I got it right when it said teamwin to reboot but everytime it reboot it tried to run the script and would never actually go into twrp. att is sending me a new phone but I'm worried when I send this one back they'll get me for being rooted.

SamsungGalaxyStig said:
I haven't tested it on VZW unfortunately. Check with scrosler. However, I assume it should be similar if not the same, but don't quote me on that.
Updated Link guys: https://www.dropbox.com/s/qsjwguwtlyczwdh/adb with cmd.zip
Click to expand...
Click to collapse
I just messaged him to double check - I don't have access to my phone for a few days (out of town) but if he hasn't responded by the time I get home I'll just go ahead and try it and post here if it works or not. Thanks again for sharing this file!

Got the file... and MANY THANKS!!! It allowed me to un-softbrick my G2 finally

this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
updating partition details
Running boot script....
Finished running bootscript,
Processing AOSP recovery commands....
----Wiping Data Partition----
Wiping data without data/media...
Done.
Removing all files under '/cache'
---- data partition wipe complete!
Done processing script file
Click to expand...
Click to collapse

bova80 said:
this just isn't working for me, so hard to get it to get that command and when I do it still just reboots to the wiping partition script and reboots again. Think I'm screwed. Anything I can do in download mode or any other commands I can send? @SamsungGalaxyStig
video clip of what is happening
http://youtu.be/8U_mgYYxIpQ
here is what the script says
Click to expand...
Click to collapse
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?

SamsungGalaxyStig said:
The minute you see the twrp screen pop up start hammering away at the adb command listed before. after you type it once, you can keep pressing the up cursor and it will just replicate the previous command. You are opening up the cmd in the adb folder right?
Click to expand...
Click to collapse
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?

bova80 said:
yeah just tried it again and as soon as I hit it it starts rebooting again goes to TeamWin screen and then runs the same script I posted before and when it is done it reboots and then goes to blank screen. I had just put the latest twrp on the day before too so I don't understand why it isn't booting to it.
My biggest thing is will ATT freak and send the phone back once they get it and go to download mode and see it says rooted or if they try the hard reset and see it goes to a TeamWin screen.
side note, if I can type adb shell and get it to prompt me there, is there anything I can try and type quickly to have it do anything else?
Click to expand...
Click to collapse
Are you constantly doing the adb recovery reboot? or once or twice?

SamsungGalaxyStig said:
Are you constantly doing the adb recovery reboot? or once or twice?
Click to expand...
Click to collapse
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?

bova80 said:
I did it a bunch of times continuously and it would just keep rebooting. Am I supposed to just keep doing that for 10-15min straight? How will I know if it gets into recovery if it just keeps rebooting when ever I keep doing that?
Click to expand...
Click to collapse
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.

SamsungGalaxyStig said:
Keep doing it, watch your phone as it will eventually boot into recovery itself without running script.
Click to expand...
Click to collapse
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?

bova80 said:
when I'm sending that command though it never actually runs the script, it just reboots.
I'll try this out when I get home, hopefully my fingers don't get tired, lol. How long did it take you?
Click to expand...
Click to collapse
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?

SamsungGalaxyStig said:
like 5-10 min at most. it's literally timing. and based on what i saw on the youtube video you were having the exact same problem. btw, you have your drivers installed correctly right? you can check that under device manager. BTW, are you using a PC or mac?
Click to expand...
Click to collapse
on a pc. when i go under device manager I think it says something like lg modem, I'll know for sure when I get home.

omg it finally worked! thanks, I eventually just gave up with the command prompt and it went in.

Hi guys my T-mobile LG V20 is in a bootloop help...

I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help

jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole proccess step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
same problem here and cant find solution ...

I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should

Flash the latest su and your fine.

ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
did that but my adb says no devices or emulators?

jo4mvp24 said:
did that but my adb says no devices or emulators?
Click to expand...
Click to collapse
Make sure your on charging mode and you have adb debug enabled

send the adb reboot recovery command as soon as the twrp connects to the computer. as soon as you hear it connect to the computer it should work if your drivers are working.

charlieb620 said:
Make sure your on charging mode and you have adb debug enabled
Click to expand...
Click to collapse
how do i do that when phone stuck on encryption unsuccessful screen?

exactly my issue
ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:

This method WORKS!!!! Same situation happened to me. THANK YOU 500x!! you saved my brick!

ErickF said:
I had the same issue. when you press to reset button when the phone boots it should reboot and for a short time go to recovery and try to write some commands, right? if it does like mine did then what i did to fix it was boot up the phone and wait for the page saying encryption unsuccesful to popup and on the computer have the adb reboot recovery ready to go so when you press the reset button and the recovery menu pops up press enter on the computer before it goes away and it should send you to the regular recovery menu. from there you should go back to wipe and press the format data button where you have to type yes to erase everything. let me know how it went.
you will have to reflash the supersu but it should now be working like it should
Click to expand...
Click to collapse
This works 100% thank you so much. Just have patience as it has to be at the right time....WORKS WORKS WORKS!!!!!

Help
Can someone explain the commands and how to do this please thanks in advance

I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery

epr2175 said:
I did the data reset and im still in the bootloop. Worst thing is now i cant seem to get into recovery
Click to expand...
Click to collapse
What screen are you stuck in? Do you have adb up and running?

Same as before Encryption unsuccessful. I was able to do the trick, got into two and wiped data. Then rebooted to system and it went right back to that screen. I've tried 100 times or so to get back into twrp with no luck. I hear the computer recognize the device when it goes into twrp for 2 seconds after you click reset. Not sure if that means add is up and running or not.

jessiemougeot said:
Ya that is exactly what happend give me a few minutes ill try it out and let you know....THANKS...THANKS....THANKS...It worked, i got it on my first try. Your right ...you have to be quick. thank u so much you saved me along night of downloads! :victory:
Click to expand...
Click to collapse
Well it booted then got stuck on the lg boot screen again. Adb does not recognize my device, can only boot into Fastboot. Fastboot does see my device, tried lgup, lg bridge, and lg update none see my device, tried relocking bootloader after oem lock bootloader rebooted said my device was corrupted and shut itself off went back into Fastboot unlocked bootloader again and back to the same lg screen help?

This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
---------- Post added at 02:06 PM ---------- Previous post was at 01:11 PM ----------
crazyc78 said:
This did not work for me, my phone reboots back into TWRP whenever I install a system image it still gives me the encryption message.
Click to expand...
Click to collapse
Now I don't even have the encryption screen it just reboots back to TWRP very frustrating!!

fixed!
jessiemougeot said:
I got the new T-mobile LG V20 I went thru the the whole process step by step of how to root and install twrp on my device the last step of having to encrypt it failed now its stuck in a bootloop. screen pops up saying encryption is unsuccessful,then resets to twrp and flashes back to the previous screen. over and over. Please help
Click to expand...
Click to collapse
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.

This option works!
SyHusky said:
Had the same problem and could not for the life of me do the adb thing. Someone here stated something that I thought I'd try: Press volume down while plugging in the phone to get into fastboot. In a command window issue "fastboot oem lock" (this will relock the boot) > Let the phone reset and you'll see the "Phone corrupt message" > Plug the phone in again to do a fastboot and issue "fastboot oem unlock" > Take the battery out let the phone boot and BAM-E WHAM success!
btw. I followed the steps here to do the whole root thing with Android . how (google "how to root the v20")
I think the "data" wipe did this and according to this site it's not a necessary step so skip it.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!

jay_h_jacob said:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I go my T-mobile LG V20 H918 on 11/23/16 and sure enough, I followed the same thread as listed above where it added the step of "data wipe" crap. I was caught in a bootloop, where phone kept bootlooping back to the "reset to factory." The other method of entering the adb command at the right time was more frustrating than anything. (I never got it to work). I spent all day yesterday trying to get this phone working. I re-read (x30) the above thread and on the first attempt it worked. I did not get the "Phone Corrupt Message," but I went ahead and entered the "fastboot oem unlock" and the F#$king phone finally reboot to the setup initial screen. It wiped everything, but having a phone working rather than a nice $800 paperweight, I wanted to kiss SkyHusky for sharing this simple method. YOU ARE AWESOME!!!!
By the way, since I am a glutton for punishment, I followed the steps to root again. After flashing the SuperUser, I rebooted to System. I was at the initial setup screen. My phone is rooted, has TWRP, and SuperUser! As soon as I got the phone working, I went back to TWRP and made a BACKUP!!!!
It is amazing that every time I f-up a phone, I can always come to XDA and get a solution. THANKS GUYS!
Click to expand...
Click to collapse
No problem!! Also I forgot to add I only rooted afterward and didn't try to install a ROM or anything. I would think you risk danger with some ROMs without that decryption thing turned off. So maybe in the short future there will be better fixes.

Nexus 6P Bootloop, fastboot devices works, but no other fastboot commands work

Hello,
My wife's 6P is stuck in a bootloop. Here's what I've tried so far:
adb devices -> no result
fastboot devices -> device info is displayed
Any other fastboot command -> "FAILED (command write failed(No error))"
I unlocked her bootloader when we got the phone, but I can't flash anything. I just keep getting that error.
Any ideas? Thanks in advance for your help.

Did you update ADB and fastboot ?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/

coremania said:
Did you update ADB and fastboot ?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Click to expand...
Click to collapse
Yep, I'm able to see my 6P and N7 2012 via ADB, just my wife's 6P that I can't seem to get to work.

Not sure what happened, but I am now able to execute fastboot commands without getting that error. So now I'm waiting for the battery to die down enough to be able to boot recovery per this post. Hopefully this will fix it.

FlyOnTheWall43 said:
Yep, I'm able to see my 6P and N7 2012 via ADB, just my wife's 6P that I can't seem to get to work.
Click to expand...
Click to collapse
You're not able to boot to stock recovery ?
---------- Post added at 14:40 ---------- Previous post was at 14:21 ----------
What happens if you put a working twrp.img into your fastboot folder and try to boot it without flashing.
fastboot boot twrp.img
or
fastboot boot recovery twrp.img

coremania said:
You're not able to boot to stock recovery ?
---------- Post added at 14:40 ---------- Previous post was at 14:21 ----------
What happens if you put a working twrp.img into your fastboot folder and try to boot it without flashing.
fastboot boot twrp.img
or
fastboot boot recovery twrp.img
Click to expand...
Click to collapse
correct, I cannot boot to stock recovery, flash a custom recovery, or boot to a custom recovery directly (without flashing).

FlyOnTheWall43 said:
correct, I cannot boot to stock recovery, flash a custom recovery, or boot to a custom recovery directly (without flashing).
Click to expand...
Click to collapse
Just read the thread you linked, did you try the freezer, like the guy from the last post ???

coremania said:
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
Click to expand...
Click to collapse
no, I just found that thread and I'm at work... going to try the freezer trick tonight.

coremania said:
Just read the thread you linked, did you try the freezer, like the guy from the last post ???
Click to expand...
Click to collapse
FlyOnTheWall43 said:
no, I just found that thread and I'm at work... going to try the freezer trick tonight.
Click to expand...
Click to collapse
Shoot, didn't help. Still continued to bootloop.

FlyOnTheWall43 said:
Shoot, didn't help. Still continued to bootloop.
Click to expand...
Click to collapse
Yes, actually the thing with the freezer i never heard that before, but if i remember right someone uses heat to make the phone bootable for a short time. May you carefully try this
with a hairdryer ??? And then try the 4 core modified boot.img

coremania said:
Yes, actually the thing with the freezer i never heard that before, but if i remember right someone uses heat to make the phone bootable for a short time. May you carefully try this
with a hairdryer ??? And then try the 4 core modified boot.img
Click to expand...
Click to collapse
ok, I can give this a try today after work and report back... thanks

The freezer trick did not work. But what helped me was to let the phones battery run out then plug it into the charger and let it boot loop for about 20 mins or so. The phone should boot at that point. I'm thinking the phone has to at least have a minimal charge to boot. Once the phone boots take it off the charger and make sure that "usb debugging" is on as well as allow "oem unlock" option. Once those settings are set go back to fast boot and attempt to flash the four core fix. It really works ????. If you leave the charger on it will go back to boot looping after it reaches 10 percent or so. Hope this helps.

pacoe said:
The freezer trick did not work. But what helped me was to let the phones battery run out then plug it into the charger and let it boot loop for about 20 mins or so. The phone should boot at that point. I'm thinking the phone has to at least have a minimal charge to boot. Once the phone boots take it off the charger and make sure that "usb debugging" is on as well as allow "oem unlock" option. Once those settings are set go back to fast boot and attempt to flash the four core fix. It really works . If you leave the charger on it will go back to boot looping after it reaches 10 percent or so. Hope this helps.
Click to expand...
Click to collapse
My bootloader is already unlocked, but I can't flash or boot the four core fix.

I know this question sounds redundant, but does your phone show your bootloader to be unlocked? Seems quite strange that it would not run the fastboot commands. What is the command that you are typing in to install the four core fix.

pacoe said:
I know this question sounds redundant, but does your phone show your bootloader to be unlocked? Seems quite strange that it would not run the fastboot commands. What is the command that you are typing in to install the four core fix.
Click to expand...
Click to collapse
no worries, I appreciate the attention/suggestions this thread is getting.... yeah, the bootloader is showing as unlocked. Also as of post #4, I am able to execute all fastboot commands now... I'm not 100% sure why it started working.

Always glad to help. Have you been able to fix the phone?

Sorry to disturb you, after I unlocked my device, I tried to flash both normal fix and 4 -core fix img > flash TWRP recovery, but I still cannot get into recovery mode, is my procedure wrong?
1) Flash 4 core fix boot img.
2) Flash TWRP recovery.
3) Boot to recovery.
4) Bootloop.
Thank you.

pacoe said:
Always glad to help. Have you been able to fix the phone?
Click to expand...
Click to collapse
No, but our Pixel 2's just showed up, so this isn't as urgent for me as it originally was. I'm hoping I can still get her old Nexus 6P and use it as our home phone with Google Voice. But, first I have to get this fix to work...
I'm able to flash the modified boot images without any errors, but I still can't get it to boot... I'm thinking it might be because my wife had to keep her phone 3-6 months behind the most current factory image (due to a poorly supported app she HAS to have for work) so I'm thinking the boot images on this thread won't work for her phone because he's on an older factory image. Am I correct in thinking this might be the problem?
I've requested that the OP of that thread either created modified boot images for the older versions of the factory images or explain how he made them so I can try to make them myself. Hopefully he's able to help me out.