Specifics first -
Device: VS980 (VZW LG G2)
Recovery: TWRP 2.6.3.2
ROM: CM 10.2 12/6 Nightly
I had a random reboot while trying to answer a phone call today. Its happened before. So I figured I would reflash the nightly to see if it would correct itself. I entered recovery from the power button menu. I tried to flash the nightly from the CyanDelta folder (tinkering around earlier, downloaded it, detected rom, and deleted from cmupdater file). For some reason I decided to wipe cache and dalvik after installing. The phone never rebooted after that. I proceeded to try and power up only to be faced with a constant CM boot screen (I knew something was wrong when I notice how long it took to get to the CM screen). I was able to get back into recovery to try and flash the 11/30 nightly, which I hadn't touched. After flashing, I noticed the "Unable to mount /cache". So instead of trying to fight with my phone to get back into recovery, I flashed a backup. It also displayed the "Unable to mount /cache". My phone was in recovery where I performed a factory reset. ADB was recognizing it and receiving commands. I unplugged it to see if I could get into download mode. Now I cant get it back into recovery. When I do "adb devices" it shows up as "unauthorized". Where do I go from here? I have very limited adb experience.
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.
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
Help me!
I run AOSP 7.3 and TWRP 3.4.0.0 (or 3.3.0.0, i don't remember)
I flashed orangefox 11 following this: https://techrrival.com/flash-recovery-adb-fastboot/
after last step: (Reboot the Device Type the following command to reboot your device “fastboot reboot”), phone stuck loading AOSP.
I then managed to re flash TWRP 3.4.0.0 trying to solve the problem but still stuck loading AOSP...
The problem is that when i run ADB commands it responds: error: no device\emulators found,
I managed to solve it the first time by killing adb and exiting usb device, then running again, but now this doesnt work anymore.
Please Help as this is my main and only phone...
By pressing and holding both volume buttons and power button for 15 seconds, After vibration signal released the power button, while keep holding both volume buttons I’ve successfully booted into TWRP recovery.
By choosing reboot to system it still stuck loading AOSP.
What should i do now?
I wiped cache and everything went back to normal.
Hello everyone,
I flashed teamwin today and afterwards lineagos. All worked like a charm. However, I tried getting root access using this tutorial (
), but there was an error message when I installed the "no-verity" zip. I rebooted it, all went normal and after another restart it now is stuck at the teamwin page.
I can go into download modus, but flashing teamwin again, does not result in any changes. Teamwin version is 3.6.2_9-0.
What can I do?
Thanks
Since I can't turn it of (I have to either go into download mode or get stuck at the twrp screen), I would really appreciate fast help
E: Fastboot and adb unfortunatelly don't seem to work, because the phone is not listed when I type "adb devices".
E2: I downloaded the "latest" Firmware from Sammobile, Flashed (only) the AP file (2,6 GB), choose "Auto-reboot" in Odin and after the reboot I managed to get into the normal bootloader -> Wipe cache and factory reset.
After restart Android 8 started to get set up.
If you encounter this: Be careful and make sure your battery is charged! Because when stuck in bootload it gets hot and apperently drains the battery quite fast.