Hello,
My nexus 5 is rooted, rom custom (great terminus) and kernel code blue.
I have recently to try change my kernel for Stock Kernel [L-preview r3] [LPX13D] : I take the kernel stock on this page : http://forum.xda-developers.com/google-nexus-5/general/kernel-t2518816
I have just reboot my device on recovery (TWRP) and flash the kernel and reeboot. No wipe. Nothing else. But my phone doesn't start : Now after bootanimation, I have "update of app 14 on 95.." and at the end of this loading
phone reboot and "update of app" again.. endlessly.
So I try reinstall a factory ROM, bootloader, radio, kernel. All. The problem is my phone is not found on adb command :
HOWEVER USB debugging is activated.
On windows, the device is recognized on device Manager "android device" "android bootloader interface".
I have the latest version of fastboot tools of android sdk installed.
My phone is boot on bootloader and plug in USB
The following command :
adb devices
list of devices attached
adb usb
error device not found
I also tried on my macbook pro. Same problem, all seem work fine but device not found.
Have you an idea to force the recognition of the device ?
If you're in the bootloader its fastboot not adb
Fastboot devices
Sent from my Nexus 5 using Tapatalk
Yes, was that^^ Thanks !
So my boot is stuck at the Cyanogen logo. I believe this happened because I flashed an incorrect zip file of a previous Xposed version (74 instead of 75).
I need to push either the Xposed Uninstaller, or the correct v75 version, to the phone's sdcard storage without being able to boot.
My phone is a rooted OnePlus One, with the latest Sultan's Unofficial CyanogenMod and TWRP Custom Recovery installed.
Booting into Fastboot Mode, the cmd command [fastboot devices] gives me back my device ID, but [adb devices] does not.
The [adb push] command does not seem to be working; I keep getting the [error: device '(null)' not found] message.
I tried USB mounting using the MOUNT menu in TWRP, but I keep hearing the Windows sound for *device unplugged*, and my storage never appears to allow me to explore it (I'm on Windows 8.1).
Any idea what's going on? Any help would be appreciated, thanks!
Moto G XT1032
Hello,
I hope that you understand my English. I am kind of a layman concerning Android, but still wanted to install Cyanogenmod 13. I followed these instructions (can't post them apparently since I am new). Official instructions on the CM website. (Bootloader was already unlocked because I already installed Cyanogenmod 12, went back to Stock ROM and now tried to install CM13). Like alwas there were some minor errors during the first steps, but I handled them alright, I think.
The real problem started when I tried to install the zip-file of CM13 ("Installing CyanogenMod from recovery", step 8). I followed the instructions (wipe etc.), but the installation stopped at "Patching system image unconditionally" and it said something like "missing md5-file" although the file I downloaded on the TWRP website was right next to the recovery .img.
After trying and trying I started to go through the options in TWRP recovery (which was a fault, I know) and wiped some things that probably should not have been wiped. Next error message was: "unable to mount /system". New problem.
Then I thought, I might try the recovery that was right next to the downloadlink of the CM13 firmware. Installed it succesfully and tried again some things, now I have a bootloop and can't shut off the phone. When I shut it off, 1 second later the Google-screen with the open lock appears again". The only help was to manually shut it off with recovery.
I can't even start Android anymore, which means I can't activate USB-debugging, the installation files of CM13 are missing and the main problem: my PC only recognizes the phone in fast boot mode - I can't move files to the phone, it just says in the task bar: "Fastboot falcon S".
As soon as I enter recovery mode, the USB-sign on Windows vanishes.
Tried to move the files to the devices by "adb push cm-13.0-20160703-NIGHTLY-falcon.zip /scard", but it says "* daemon not running. starting it now on port 5037 *
* daemon startet successfully *
adb: error: connect failed: no devices/emulators found"
The device is not recognized by "fastboot devices" in cmd.
I hope that you understood everything. Already tried to get help in German forums, but nobody answered there.
And yeah, I definitely stopped trying to solve it by myself because I might just destroy it more.
Thanks for your help!
seems like we are on the same trolley.
I wanted to have a 100% clean system so I wiped everything.
I reinstall SDK, google drivers, motorola drivers, but no success. In fastboot mode it's written: USB connected, on the computer eject "Fastboot falcon S". I create file adb_usb.ini with id in it, restarted system, killed adb and so on. Tried different USB port, different cables.
Aendroit, if you find a way share.
I'm on W10 if that matters.
Ok. So I managed to go through the problem.
First, I was able to reinstall TWRP with fastboot (fastboot root twrp.....), so fastboot worked for me. Then it seems that on the main screen, where you choose options with volume buttons, fastboot works, but not adb.
I went into recovery and "adb shell" worked, so did "adb devices".
I used push command and so on.
I'm glad you got the solution now. Unfortunately I can't follow the instructions. Could you please take me through it step by step ("fastboot root twrp", I never used a command like this before). Thanks!
Because when I go in recovery and type in "adb shell" or "adb shell" on my computer, it says "no devices/emulators found".
Update: Got it. I can enter TWRP now, but in the installation log it said "Mismatched partition size (recovery)" at the end. If someone knows what that means ...
I meant: fastboot flash recovery twrp-3.0.0.0_2-falcon.img
Mismatched size is just an information, nothing to worry about. Now, when you are in TWRP try to check the device "adb devices", should work.
Thank you, my computer recognizes the device again! I was able to copy the files to my phone. Unfortunately I still can't install a custom rom. I tried Mokee instead of CM13 now and i always get the same messages:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 146758281
Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and so on.
I don't know what that is supposed to mean ...
Well, I'm not very good oriented in all this stuff, so I don't know why you got those problems, far from being a dev.
I copied ressurection ROM + open gapps nano (thou I always used banks, but this time wanted to save more free space) and installed it via TWRP without any issues.
Thank you for the answer. Mokee works now! I'm not happy that I can't use CM13, but I got Mokee working after a while and I'm glad about it.
I'm in way over my head guys, so here's my situation:
I have no OS installed, for some reason I can't get into TWRP anymore (it goes to eRecovery instead).
I CAN get to bootloader screen (bootloader is unlocked).
adb does not recognize my device on device list command (it worked before, but now I can't get into the OS to turn on USB debugging and such...).
please help! I don't know what else to do!
liran96 said:
I'm in way over my head guys, so here's my situation:
I have no OS installed, for some reason I can't get into TWRP anymore (it goes to eRecovery instead).
I CAN get to bootloader screen (bootloader is unlocked).
adb does not recognize my device on device list command (it worked before, but now I can't get into the OS to turn on USB debugging and such...).
please help! I don't know what else to do!
Click to expand...
Click to collapse
I think the first step to fixing my phone is to get it recognized in the list of devices attached in adb.
how do I go about doing that?
In device manager I got it to recognize my phone as Android Phone > Android ADB Interface.
so I believe the drivers are updated, what else can I do to get my phone recognized in cmd adb?
If I need to provide any more details then please say, I am getting hopeless
Edit: I managed to get into TWRP. still no clue how to continue from here as I can't transfer any files from PC
I found a update.zip file on my phone's SD card, I can't remember which ROM version it holds, but when I try to flash it I get a few errors:
check_write_data_to_partition,write data error
E:unknown command [errno]
Update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip files '/external_sd/update.zip'
I think I managed to screw my phone up even more, I can no longer get into TWRP...
:crying:
I initially had installed oxygenOS 12, then rollbacked to oxygenOS 11 without ADB, using the system update method. Then I unlocked the bootloader and enabled USB debugging. Then rebooted into fastboot mode and according to the guide here, I used the command "fastboot update aospa-sapphire-2-oneplus8-alpha-20220118-image.zip" to try to flash Paranoid Android in my phone...and here's where the problem occurs: it gets stuck at "<waiting for device>" till I reboot the phone into fastboot again and when I do it throws the error: "fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable." (I have also attached the error message in this post), and ultimately my phone gets bricked. I am able to unbrick it into OxygenOS again but this error keeps happening again when I tried it for the second time. Please help.