My phones stuck in a no command loop i can access recovery and bootloader mode this happened while following a guide to root my device after applying an update from my sd card(june 2018 ota) this happened no matter what i do i cannot seem to get fastboot to detect my device so i can unlock the bootloader (adb detects it when in apply update from adb) can anyone help with this?
Update
Update: it is now stuck on the powered by andriod screen. after running out of battery i think
Related
hello
so I wanted to get my nexus 4 to complete stock mode and failed in the process.
I followed a guide that was posted on here and
1. locked the bootloader
2. put 3 files (rom, recovery, boot animation?) into the phone and went to flash them
3. rom installation failed but I went and installed recovery and boot
now the phone is stuck at google booting screen and wont go past it. bootloader gives me dead android with triangle and I can't get into adb because it says device is offline.
can anyone tell me a way to fix this?
Unlock the bootloader and flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app
i have same issue with you
only boot into google logo..
i can reboot my into fastboot mode and recovery mode...and try to install some usb driver from the forum
but still can not adb and fastboot my phone...
in command prompt say device offline.....device not found...
my phone can not connect my computer...........
So my Nexus6p randomly restarted once (I had been on 7.0 since release date with no issues) and since then is stuck in bootloop on the Google Logo.
Holding the Power+Volume Down boots into bootloader. From there I can't get to recovery or even tried the factory reset from there and it always gets stuck on the Google Logo.
I have downloaded the SDK and while fastboot works, adb doesn't.
I can't flash anything through fastboot because boot loader is locked. I can't unlock the booatloader because remote oem unlock is disabled. I have never had the need to root or unlock bootloader, so never had USB debugging or allowing unlock checked under debugging tools.
Can't sideload OTAs since adb doesn't work.
Do I have any options to recover the device and make it work again?
kumarshah said:
So my Nexus6p randomly restarted once (I had been on 7.0 since release date with no issues) and since then is stuck in bootloop on the Google Logo.
Holding the Power+Volume Down boots into bootloader. From there I can't get to recovery or even tried the factory reset from there and it always gets stuck on the Google Logo.
I have downloaded the SDK and while fastboot works, adb doesn't.
I can't flash anything through fastboot because boot loader is locked. I can't unlock the booatloader because remote oem unlock is disabled. I have never had the need to root or unlock bootloader, so never had USB debugging or allowing unlock checked under debugging tools.
Can't sideload OTAs since adb doesn't work.
Do I have any options to recover the device and make it work again?
Click to expand...
Click to collapse
Do you just have stock recovery? If so, can you boot directly into it with power + vol up. If so, maybe try hitting stock recovery menu to side load ADB or factory reset? Otherwise, sounds pretty borked unfortunately.
Sent from my Nexus 6P using Tapatalk
Hello
As menitoned, my phone won't boot into TWRP, it does boot into Android 7.0 EMUI 5.0, can boot into revolutionary recovery, but no, not TWRP... Bootloader is unlocked! Please help
Are you certain it's not booting into TWRP? The reason I ask is I thought I couldn't boot into the custom recovery programme either: it kept loading EMUI, using the phone's buttons. In my case, ver.4.1.1
Have you tried booting via ADB commands? I had reloaded a stock update, then unlocked the bootloader for a second time, only find the same scenario. It wasn't until I tried rebooting with ADB that it actually loaded TWRP.
In case you aren't familiar with the commands. Install ADB Tools, then open a command window from the correct folder location, where ADB tools are installed. To check the PC recognises the device, use:
adb Devices
it should show the device's serial number {I think}. Then:
adb reboot recovery
it should reboot into recovery mode. If TWRP has been installed correctly, it should load into it. Otherwise...I don't have a clue what the issue is. All the best.
Please help!!!
I tried to update my rooted Nexus 6P to 8.0.0 (OPR5.170623.011, Nov 2017) using the Flashfire app and something went wrong!!! The phone is now stuck in bootloop and will not get past the 4 google coloured dots. I can boot the phone into the bootloader and then get into TWRP recovery from there but thats pretty much it.
I hoped I would be able to fix it by flashing the system image, bootloader etc using adb and fastboot but have had no luck. I have tried on both a PC and a Mac and neither seem to recognize the device. When using the commands "adb devices" or "fastboot devices" nothing shows up and when I try to flash anything it says "waiting for any device" yet when the phone is off it signals that it is charging from the laptop.
I have updated my rooted 6P multiple times before using both Flashfire and adb/fastboot from both a PC and a Mac and have never had problems before this. I have run out of ideas to try so any help would be greatly appreciated but I fear I might have bricked my beloved Nexus 6P.
MilkyOolong said:
Please help!!!
Click to expand...
Click to collapse
Weird. You should at least have fastboot when in bootloader mode, and MTP with TWRP. In bootloader mode, plug the device into your PC. The device is not detected at all? Have you tried wiping cache/dalvik? MTP not working in TWRP?
If you can boot into recovery then your device is not bricked. Make sure the adb and fastboot binaries on your computer are completely up to date. I'm pretty sure Google updated them for Oreo. You will need to flash the full stock image with flash-all.bat command when you get your computer to recognize your phone. Updating from Nougat to Oreo using Flashfire or Flashify is a bad idea because you are dealing with something way more extensive than an OTA update.
I just bought this phone and it is on nougat with a security patch level of December 2016.
First of all I unlocked the bootloader and afterwards it displayed a white screen with 30 unlock attempts remaining, I then figured out how to erase it and it showed a white circle with the text erasing.
It finally erased and I booted into android and set it up.
I reenabled USB debugging and tried to get TWRP installed, and the dirtycow exploits were successful and it became stuck on the tmobile logo ( I think systemui crashed). Then I followed the instructions to run "adb logcat -s recowvery" but in the terminal it outputted nothing.
I am clueless as to how I can install a custom recovery so that I can get a custom rom installed.
Any help would be appreciated in getting a custom recovery installed onto this device.
Thank you!
Do you have a link to the dirty cow procedure you used?