My Samsung Galaxy Nexus is stuck in this boot loop, where it first boots normally and then after about 10 seconds shuts down and reboots. I have tried installing a stockrom using adb sideload, but it returns "E: signature verification failed". I researched the problem and apparently verification can be disable using RomManager. I tried to flash the app using adb install, but this returns "error: closed". The device is displayed as a sideload device when i type in "adb devices", but the Nexus Root Toolkit does not detect any adb fastboot devices, although it does detect that a phone is connected.
Model Type according to Nexus Root Toolkit:
Galaxy Nexus
GSM/HSPA+
Android *.*.* Any
I am frankly at a loss, as i have no prior experience with rooting etc., so i would be grateful for any advice.
The same problem started, too. I've tried every method, but the problem is not solved. What should we do ?
Try adb reboot bootloader or adb reboot recovery. If adb doesn't accept any reboot commands, try going to the bootloader and get into recovery from there (or, install or boot a custom recovery) and install a different ROM.
Related
Just a moment ago I pushed my own custom framework-res to the phone. I had only edited some picture files inside it. After rebooting it worked correctly so I edited some more images, booted into clockworkmod recovery and tried to push in a new framework. But this time my adb just gave me an error "error: device offline".
After rebooting into revoked recovery I tried using adb again but with the same result. I also noticed that my computer suddenly installed all of the Android related drivers again, there were four different drivers it installed.
I thought it was because of my custom framework so I decided to flash my custom rom again. I didn't do a full wipe and after rebooting I got stuck in a bootloop.
So currently the only way I can access the phone is in fastboot. My computer recognizes the phone when it's in recovery but I can't use any adb commands. When I type adb devices it lists my devices but says it's offline. I tried doing the first step of the rooting process and it worked fine but after booting into recovery I tried doing the step2 but the device was still offline.
Is this because of my Windows drivers or did I screw up the Android system somehow?
You should have made a backup using nandroid. I though think you need to wipe.
Sent from something using the internet.
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
solved
I used another laptop with a fresh skipnote nexus toolkit and everything worked just fine.
shakrooph said:
Hi,
First of all I'd like to say I tried to look this up in the forum but since my problem is kind of a combination of several problems, I failed to find a proper solution.
I have a rooted galaxy nexus running 4.3 deodexed. I downloaded a Mod to flash in CWM Recovery. Did a flash and factory reset and as I tried to flash it, it gave an error and aborted the installation and since then I can't get the phone out of bootloader. I can enter recovery mod from there however, I can't boot the phone.
Unfortunately I don't have a stock rom or any other zip/img/tar etc file on my sdcard.
When I plug my phone on bootloader I get the error message FASTBOOT fail command
I downloaded adb drivers but when I try to use adb push command I get an error message saying "ADB is not a recognized as an internal or external command etc." I'm doing this on the folder where extracted adb files.
I used to skipnote nexus toolkit. But even though I can get it to recognize my phone on either fastboot or adb mode, I fail to flash / push or install anything on my phone. If I try ADB, it waits forever on waiting for ADB phase. If I use fastboot however, it gives an error message and aborts the operation.
Downloaded & installed kies on the computer. I tried ODIN to push files but I failed at that too. Seems like Odin doesn't recognize the device.
As a result, I can't use my phone right now. I'm open for any suggestions for installing a stock rom and unrooting or rooting and installing a custom rom.
Thank you all very much in advance,
Click to expand...
Click to collapse
Ok, my nexus 7 this morning had just randomly started to not respond to any touch. I restarted the device by turning it off and on again with the power button, and it stuck at Google logo. I can go into bootloader, but not recovery. If I try to go in to recovery, it gets stuck at Google logo again.
The device is stock, didn't even unlock it. Fastboot devices returns the serial number, fastboot oem unlock pops up the screen if I want to proceed, at which point I click no because I don't want to wipe the drive yet. I've tried Nexus Root Toolkit to boot into temporary custom recovery to make a back up, but doesn't work. NRT live log is as follows
-----------------------------------------------------------------------------------------------------------
Information: Rebooting your device into bootloader mode...
fastboot reboot-bootloader
Information: Rebooting your device into bootloader mode...
adb reboot bootloader
Information: Checking Fastboot Status
fastboot devices
Information: Retrying.. Checking Fastboot Status
fastboot devices
05864603 fastboot
Fastboot Status: Device Connected
Information: Booting modified boot.img to enable running privileged commands...
fastboot boot "D:\Android Development\Nexus Root Toolkit 1.7.2\data\Modified_Boot\modified_boot_razor_5.0.1_Information: Waiting for your device...
adb wait-for-device
LRX22C.img"
-------------------------------------------------------------------------------------------------------------
and then times out.
Since i couldn't connect it with my computer with USB debugging on, the drivers might not have installed correctly, although I did try installing the drivers with NRT. Currently my laptop doesn't recognize the device. It does make sound when I connect the device, but it doesn't show up in device manager at all.
Any pointers please?
Hi all.
After OTA upgrade to android 6 of unlocked unrooted nexus 7 2013 WiFi i decided to unlock and install twrp.
I used adb and fastboot to flash version 2.8.7.
It went smooth but after reboot to recovery, twrp shell returns "can't mount *" for all partitions. And the device is bootlooping into this state (unless I boot into bootloader).
The worst part is that my pc wont recognise the tablet when connected. Adb devices returns an empty list. So i cant even flash stock recovery or do anything uing adb/fastboot.
HELP!!!!
[solved] falshed factory image manually using fastboot
It seems fastboot recognized the device while adb/pc couldn't.
I downloaded Android 6 factory image from google and flashed-all that.
Just updating in case some other noob who doesn't fully understand adb/fastboot relations.
Hi, I have a Nexus 5X Android 8.1.0 with TWRP on it. I'm trying to root my phone. I'm using Nexus Root Toolkit. It's unlocked and ready for NRT. When I click "Root" (with or without Custom Recovery), I get an error "ADB Recovery device was not found." It asks me to select drivers on my computer (Android Device > Android ADB Interface.) I have 3 "Standard MTP Device" Drivers. The Live Log shows "Checking ADB Recovery Connectivity" and then fails. I get the error. So how do I root with NRT and get past the "ADB Recovery device was not found"? Has anyone heard of this problem? What drivers do I need? Everything else works fine. Also, Will rooting with Toolkit install Super SU and BusyBox? I've never successfully rooted using NRT. So how do I fix the Recovery Connectivity? Please reply. Thanks
Hi, I'm back. Does anyone know what "Recovery Connectivity" means? My phone is plugged in. I used Magisk once but I'd like to try Nexus Root Toolkit. I'll check back later.
I'm back. I found that Recovery Connectivity means TWRP isn't working. When I try the bootloader and hit Recovery, I get a screen saying "no command." Then it reboots to the system. I tried reinstalling TWRP using "adb reboot bootloader", when I try "fastboot flash recovery twrp-2.8.x.x-xxx.img", it completes but when I reboot and try Recovery from bootloader, I get the same "no command" error. I tried from C:/...NexusRootToolkit/data/Root_Files and "C:\AIO" which is a second file I downloaded. Both have Bullhead img files in them. They say flashing recovery is successful, but when I reboot and try Recovery, I get the above error. Does anyone know how I can flash the TWRP Recovery?
I installed TWRP. I can boot into it whenever I want. When I click "Root" and check "Custom Recovery" (on NRT) it completes and says rooting was successful. That's good. It also says I need SuperSU and Busybox. I tried flashing them (the zips) in TWRP and it says it completes. When I open my root checker or BusyBox it says "no Root." So my root was incorrect. I think I need SuperSU to root in NRT. I flashed it but it doesn't show up. I can't find it in Google Play. The live log says SuperSU flashed successfully. Still no Root. So where do I download SuperSU? NRT has it. Not working. BusyBox shows up on my phone but says it needs root. Does anyone know where I can download SuperSU? And how to Root? Please reply. Thanks
Hi, I'm going to try Magisk. It doesn't use System and I can update. Instead of using SuperSU. Now my Nexus 5X won't show up in Windows Explorer. I need to move Magisk on my phone. Can't do that. It shows up in Device Manager. I've been trying a lot of Drivers. Not connecting just MTP Device. I found a few drivers but I get an error "This device cannot start. code 10." So what driver do I need for MTP Device? It used to say Nexus 5X in Windows Explorer and Device Manager. For screenshots try this question on Microsoft Community... https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/need-android-mtp-drivers-for-nexus-5x/d59c47c4-df80-410c-b2de-45a7869604a6?tm=1574728076937
I got it working. I downloaded Magisk on my phone. Then rebooted to TWRP and installed the zip from my Downloads folder. Then I restarted to the system and my App showed up there. I now have my phone rooted with Magisk.