att lg g6 recovery - LG G6 Questions and Answers

so i was just playing around and used adb to and my PC was able to find adb devices and i was run some simple commands but when i try to reboot to boot loader it looks like its trying to as i hear plugged in sound after phone booting but immediatly disconnect sound and it boots normally and i tried rebooting to recovery and it booted to a screen with robot with a red exclmation mark and no command on the bottom and i tried some key combinations but nothing worked except holding vol down and power boots it back, does this mean att or lg have not installed recovery or is it blocked, i am aware bootloader is locked but it should still boot to recovery as it did in the g2 days that i can remember, any ideas, thank you.

update and few questions,
in the lg g 2 days on att non rooted phone the button sequence would take you to factory erase screen and if one accepts it it erases and then boots into stock recovery but now on lg g6 it does not , it erases and boots normally, and i tried adb reboot bootloader and it wont work and i tried adb reboot recovery resulting in flat robot with red exclamation mark and NO COMMAND on the bottom, i am just trying to understand, is it that secure boot in nougat is locking me out or is it att that disabled recovery and fastboot, any thoughts appreciated.

Related

[Q] Problem when attempting to flash TWRP

Hello,
I rooted my phone with no issues. Then when preparing to get TWRP on my phone I was setting up ADB via this tutorial
http://www.youtube.com/watch?v=XslKnEE4Qo8
and got the phone to be recognized as device in the cmd window, but when doing the adb reboot bootloader step, the phone just reboots to vzw logo and then the home screen. After being stuck at that step I tried this method http://androidfannetwork.com/2013/09/18/twrp-recovery-available-for-lg-g2-att-and-verizon/ using flashify but after flashing and hitting the reboot button my phone wouldn't turn on and thought I bricked it until I waited a few and then had to hold the power button down for 15 seconds and it turned on. But now I can't get to the white screen reset menu (Stock recovery menu?) using the power+vol down method. Is my stock recovery borked? Any tips on how to get twrp on my phone, hoping it installs over the broken stock recovery. Thanks in advance for reading this.

a6000 shut down during MIUI flash, won't boot into recovery

Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.

no recovery, locked boot loader, fastboot only, qualcom recovery not working

was on CM13/TWRP, suddenly my phone rebooted while i was talking, i looked at it and it had a linux logo on it....waited a bit, didn't go away, so i held power until it turned off.....then it wouldn't turn on.....so i tried recovery, nope. tried fast boot, that worked.. tried to reflash TWRP from fastboot command, failed because device is not unlocked.
can't run oem unlock because i can't get in the OS to developer mode to enable it.....
so i've been trying to do the qualcom recovery, windows 10 laptop, tried all the versions of the qualcom recovery/drivers i can find...... the recovery tool keeps giving me a red error on line 4. either that or it flat out crashes the whole program.
whats my next step? i'm attempting to run it on a windows 7 computer now thinking that may make a difference.
anyone have any thoughts?

lg k20 plus won't boot into twrp

So im trying to root my lg k20 plus. I flash the twrp recovery image and it says everything is successful. Then reboot to the factory reset screen by holding volume down and power then releasing power when i see the lg logo and pressing again. I guess the k20 plus doesnt have a regular recovery screen all it is is a factory reset anyways select yes twice to reset and it should boot into twrp recovery. only mine won't.. it goes to the screen with a yellow exclamation point that says "your device software cannot be checked for corruption. lock bootloader", and then will flash the lg logo and go straight back to the other screen and just cycle over and over forever. i can just press power and it will boot up like normal but i can't get to twrp recovery. I;ve tried recovery images from two other sources but nothing still any help would be appreciated
Randallray2711 said:
So im trying to root my lg k20 plus. I flash the twrp recovery image and it says everything is successful. Then reboot to the factory reset screen by holding volume down and power then releasing power when i see the lg logo and pressing again. I guess the k20 plus doesnt have a regular recovery screen all it is is a factory reset anyways select yes twice to reset and it should boot into twrp recovery. only mine won't.. it goes to the screen with a yellow exclamation point that says "your device software cannot be checked for corruption. lock bootloader", and then will flash the lg logo and go straight back to the other screen and just cycle over and over forever. i can just press power and it will boot up like normal but i can't get to twrp recovery. I;ve tried recovery images from two other sources but nothing still any help would be appreciated
Click to expand...
Click to collapse
Try this thread.....
https://forum.xda-developers.com/android/development/recovery-twrp-v3-lg-k20-plus-t3616248
Did you save the twrp "recovery.img" as a different name? At first i named it something else and had the same problem. I just renamed it "recovery" and all was well.
Randallray2711 said:
So im trying to root my lg k20 plus. I flash the twrp recovery image and it says everything is successful. Then reboot to the factory reset screen by holding volume down and power then releasing power when i see the lg logo and pressing again. I guess the k20 plus doesnt have a regular recovery screen all it is is a factory reset anyways select yes twice to reset and it should boot into twrp recovery. only mine won't.. it goes to the screen with a yellow exclamation point that says "your device software cannot be checked for corruption. lock bootloader", and then will flash the lg logo and go straight back to the other screen and just cycle over and over forever. i can just press power and it will boot up like normal but i can't get to twrp recovery. I;ve tried recovery images from two other sources but nothing still any help would be appreciated
Click to expand...
Click to collapse
Did you find a solution? 3 yrs later.

Stuck at "Google" screen after TWRP wipe

Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
goister said:
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
Click to expand...
Click to collapse
So since everything was checked, that means you wiped the system partition. The device will not boot if you do that unless you flash a factory image via fastboot or new ROM via TWRP
OK, I thought wiping /system would just bring it back to factory state. 2 questions now
1. How do I get to recovery when it's always stuck at the Google screen with no adb access? Would I have to wait for the battery to run out (hence turn off), charge it for a while, then use the buttons to boot to recovery, or is there a faster way?
2. I am actually trying to revert to stock ROM (downloaded at https://developers.google.com/android/images#angler) by following step 10 of the Heisenburg guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) which advises me to use fastboot to flash the individual images. In my case, how do I boot to fastboot?
OK, so I managed to boot to the bootloader and run the following commands as per the Heisenberg guide (using the stock MTC20L firmware)
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Everything was successful, and I did a fastboot reboot after that.
However, my device still doesn't boot up. This time. It's boot loops for a few times before turning off.
I tried booting up to bootloader with power/vol-. Curiously, I can now only do this when cable is connected. If cable is disconnected, the orange LED just blinks once when power button is pressed, and nothing happens. Once cable is connected, then I'm able to boot up to bootloader with the button combination. I then retried the flash process again, but still no go. I noticed after fastboot reboot that the orange LED blinked a few times before rebooting and boot looping.
Kinda stuck now, any ideas?
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Face_Plant said:
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Click to expand...
Click to collapse
Thanks. Booting into stock recovery shows an exclamation sign with "no command", since I don't have TWRP anymore. Would I need to first flash TWRP before I can do a factory reset?
I just tried flashing to the same sock firmware as before the problem happened (7.1.2 N2G47W) but still same problem. I notice that after the Google logo disappears and the screen goes blank, the orange LED blinks 10 times before rebooting.
Edit: Tried factory resetting in stock recovery (by holding down power button and pressing vol+), the rebooting after factory reset. Still getting a boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
goister said:
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
Click to expand...
Click to collapse
brother help me! i am facing same issue
first little info abt my device.
my device was running on android nougat with twrp recovery installed but the device was not rooted.
so get back to stock and install oreo I followed every step given on http://www.androidexplained.com/nexus-6p-revert-stock/ but somehow my phone is stuck at bootloop with no recovery installed.
Please help me here.
As per the Heisenberg guide, if you don't install root (SuperSU or Magisk), TWRP won't stick, so you'll go back to stock recovery.
For me, simply unplugging the USB cable after rebooting after a flash solved my problem. For some reason, if the cable is connected during reboot, it would boot loop.
brother, somehow I managed to install twrp. but everytime I touch it 2-3 times the phone gets switched off.
then it keeps rebooting to 'Google' logo.
can you tell me what should I do now?
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
tommast said:
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
Click to expand...
Click to collapse
hi, did youmanage to solve this problem? I am aving the exct same problem. Disconnecting the ucb isnt working for me

Categories

Resources