[Q] ADB not finding device? - Moto G Q&A, Help & Troubleshooting

Quick note: I'm very new to all this so I don't really know entirely what's going on.
Alright, basically I'm trying to install the Paranoid Android ROM and I've run into a bit of an issue. I've unlocked the bootloader and flashed the ClockworkMod Recovery. The problem I've ran into is that when I go into the CWM recovery and attempt to do anything with ADB it comes up with "error: device not found"
What am I doing wrong?
Sidenote: ADB can find my phone if it's booted up normally, it's only when I boot to the CWM custom recovery that it can't find it...

I think you are doing it wrong way buddy..
Boot in to Bootloader mode not in CWM Recovery, then try with fastboot and check again..

I did boot into bootloader, then went to CWM and tried to push the ROM using ADB but it wasn't recognising my phone.
Doesn't matter now anyway. I got around it by literally just drag and dropping the zip files onto my phone's internal memory when it was booted up normally and connected to my PC. Then I rebooted into the bootloader, flashed CWM and installed from ZIP. That method was far easier than messing around with ADB etc.

Related

[Q] HELP stuck on google screen after trying to root with superboot

I tried using superboot to root my nexus s, but ended up with having a stuck google screen upon reboot.
Is there anyway I can recover my phone to the original state. I can get into the boot screen by pressing up volume and the power button and I have downloaded an original rom; however, I don't know how to upload this rom
into the phone.
I unlocked the bootloader, and have the android SDK installed. I do have a response when I use the command "fastboot devices"
Is there any possible way to save my phone? Please help, Thanks in advance
is there a recovery image saved under the recovery option?
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
ri ch said:
Hey I'm having the exact same problem as the OP.
I don't have a recovery image saved in recovery, so I tried to flash the latest CWM recovery image through adb, but the device isn't found.
My phone was rooted, then upgraded to 2.3.4, then got 2.3.6 OTA, but lost root. Tried to root with Superboot and now my phone's stuck.
How can I get my phone to work again?
Click to expand...
Click to collapse
You have to flash CWM using fastboot, not adb.
fastboot flash recovery recovery.img
Once you have the custom recovery flashed you can flash superuser in CWM to get root back or just flash one of the custom ROMs that include superuser.
Yes, I did exactly that.
I really have no idea what I'm doing so I'm extremely grateful for people who do.
Thanks
I am in the same boat as these other chaps. After installing the 2.3.6 OTA update I tried to root with Superboot and now my Nexus S just sits on the Google screen with the open padlock.
I've tried installing CWM recovery, as well as the boot.recovery.img that comes with Superboot, and it seems to install successfully. After rebooting my phone still sits on the Google screen, however.
Am I doing something wrong here (I'd previously rooted with few problems)?
EDIT: I should mention that after flashing the .img I'm trying to boot into recovery - at this point it just sits on the Google screen.
EDIT 2: Never mind, I sorted it. I tried using a different recovery.img (from this thread) and I was then able to get into recovery and restore a backup.

[Q] Botched TWRP upgrade, now lost root access

While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Tunameltsalad said:
While attempting to switch to CM11 I tried upgrading TWRP from 2.4.4 to the newest 2.6+ and it messed up my recovery. Then, while trying to re-flash an older TWRP, I accidentally installed SuperSU over an existing install, and lost root. Tried re-rooting the device using motochopper and it gets to the last part, "rooting device" and it says "failed". Device the reboots, I try to open SuperSU and it says "no SU binary installed". All I'm trying to do is put back TWRP 4.2.2 so I can restore my device. Please help
EDIT: Tried using fastboot to install image, everything looks good, then my tablet freezes up. I do a power cycle, it reboots, and the recovery didn't flash.
UPDATE: Recovery flashed and wiped EVERYTHING. I am back on recovery 4.2.2.0 but nothing is mounted and I can't mount anything, I can't make backups or restore images, and ADB Sideload does not work. Any help would be really, really awesome. I have SDK Manager, and I can currently use ADB on my computer, I just don't know what commands, blobs, or images to use.
Click to expand...
Click to collapse
Can you use fastboot to reflash the stock ROM?

[Q] Stuck in recovery some time after flashing cwm

Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...
If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Sideload worked perfectly! Thank you so much!
cm11 working only TWRP here , with cwm appears same error
mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse

Flash recovery not working!

Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
angrygamer1023 said:
Backstory: I tried to load Cyanogenmod on my phone; but first I had to load TWRP recovery in order to get to load it. This is where the issue came; I decided to go the easy route and attempted to install it through Flashify (an app on the Google Play store); upon restarting my phone; it was bricked. I went into EVERYTHING, when I tried to go into recovery it would just send me through the bootloop and then send me to AP Fastboot.
Confused, I called Motorola; and was notified and Flashify had removed my prevoius recovery and failed to but TWRP resulting in this.
Issue: So what I did is I got the CWM recovery specific for my phone (XT926) and went into ADB fastboot and typed "fastboot flash cwm.img", from my ADB folder of course. Then when I booted into recovery, nothing happened; it would just send me through the bootloop again. Please help.
Click to expand...
Click to collapse
Try another recovery / another version. Did the trick for me and you have nothing to lose
I have 2 XT925s. I bricked one to the point that I could boot to fastboot but could not even get into stock recovery. I was running stock 4.4.2.
I did the following.
I got the DROID_RAZR_HD_Utility_1.41. I used the TWRP 2.7.1.0 in that utility specifically for XT925.
I used fastboot to manually flash TWRP into the recovery partition.
DO NOT reboot past boot menu. Right after flashing, boot into recovery. That should give you TWRP.
I used TWRP to Install CM11 snapshot. I had to manually flash into the modem partition, the modem file also obtained from the above utility. You will need to flash in gapps for 4.4.2.
That recovered the bricked phone.
Of note, I was able to flash TWRP in the other phone. Backed it up. Transfered the backed up OEM ROM into the phone running CM. And get it to run stock ROM.
I now have one running CM11, and one running stock 4.4.2. I'm just comparing battery life. I've noticed CM11 has a smaller memory footprint than stock 4.4.2.
Cheers
did not work for me anywhere to be found stock 4.4.2 recovery img for 926?

XZP Wont Boot after Flashing Standard Rom

Hi All,
I've been trying to install TWRP, Root etc on my XZP since yesterday. I've done something wrong at some point, and now my phone will not boot at all.
I had no troubles unlocking bootloader, installing TWRP etc initially. I then tried to install a custom rom from these forums and that's where things spiraled downwards for me.
As part of that procedure, I needed to flash the latest sony firmware first. That went fine.
However, now TWRP is not able to decrypt storage, so I'm not able to flash anything else. Perhaps this is because I booted into the new sony firmware and forgot change the pattern/fingerprint to pin/fingerprint.
So I'm not able to unlock the storage via TWRP by entering a password.
I tried to reflash the same firmware again using newflasher. But the phone won't boot at all. It turns off immediately after the Unlocked bootloader warning. It's not going into a boot loop. Just turns off.
I then tried to flash the TWRP recovery image using adb fastboot command, and the flash seemed to execute properly, but I still can not boot into recovery.
Is it possible the main storage is still encrypted, so nothing can flash to it? Bricked? If so, how do I proceed?
I read something about reformatting partitions? But I'm not able to get into TWRP recovery menu to do this.
*EDIT: I reflashed trwp recovery image, and am not able to boot into recovery. I still can not unlock (unencrypt) the main storage though.
*2nd EDIT: I followed the instructions here:https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
I was then able to flash the stock ROM back onto my device, and I'm able to boot my phone up. I'll look at installing a custom ROM at a later date.
Thread closed at OP request

Categories

Resources