Hallo Everybody,
I'm new to flashing/rooting/etc. on mobile android devices, but since my Motorola RAZR I is stuck at the red Motorola logo, it is time to gather some experiance.
As said, the phone stucks at the Motorola logo, propably a bootloop. Fastboot access is possible, it is also possible to get into the recovery menu. But when I try to connect adb via the recovery menu option "apply update via usb" my PC (Win7) gets an "Unknown Device" in the Device Manager under USB-Controller.
I used adb before for playing a little bit around, so all Motorola drivers for the normal debug mode work, but I don't find a driver for the "Unknown Device" (recovery mode adb).
I already tried different USB cables and restarted my PC serveral times, but still no driver for the "Unknown Device". I also tried the Intel Driver update for android devices and forced to install the Motorola drivers for this "Unknown Device" but nothing helps.
I wanted to try to download/backup some files from the internal storage. Afterwards, I want to flash a lineageOS.
I also searched a day in the internet and in this forum but I didn't find a solution. Sorry if I didn't find the Solution-Thread.
Has somebody an Idea?
Many Thanks in advance.
Related
I just recently got into modding my N1 a few weeks ago and finally hit my first snag:
Original root was through superoneclick, so bootloader is still locked. I flashed over to stock GRI40 OTA without realizing (stupidly) that flashing
it would also flash over my RA recovery and unroot my phone. Now, superoneclick is incompatible with GRI40, so I can't re-root through that, and I'm having trouble
with unlocking the bootloader through fastboot.
I get no response from ADB or fastboot in windows cmd prompt when I boot phone to FASTBOOT.
the command "fastboot devices" gives me a repeat of the same prompt with no error. (I can't get fastboot to work in normal debugging mode either, and I don't know if it usually will, because this is the first time I've used it.)
the command "adb devices" gives me response-- "list of devices attached" with nothing below (ADB works fine in debugging mode though).
I thought it might be a driver problem, but "Android bootloader Interface" driver is on the device manager list while phone is in fastboot, and seems to be properly
installed; I can't seem to find another suitable driver to update it to anyways.
Beyond that, there don't seem to be any other drivers running in the device manager either.
It's to the point where I'm considering taking the long way around and re-rooting through passimg, but that may not work anyways from what I've been reading, and that still won't fix my fastboot issue.
Any ideas on why I can't get fastboot to work?
my devise manager lists it as 'Android 1.0' when connected with fast boot..
if the drivers were installed on their own, then uninstal them.. and manually update the drivers (download them yourself)
that might help.. idk..
Sent from my nexus one
I think that may be part of the problem because I'm not seeing Android 1.0 on the device manager list. I do have an unknown device on there, but I can't update the driver with any of the Google USB drivers. Also, I'm pretty sure it's not my N1 because I'll unplug the N1, delete the unknown device, and scan for hardware changes and it will pop up again, so I don't think it has anything to do with my phone.
Put your phone in to fast boot, plug the phone in to a different port on your computer. If you have been plugging it in to the front, plug it in to the back. If you have been plugging it in to the back, plug it in to the front.
This should force windows to re-detect your device and it will hopefully install the missing drivers you're needing...
That was a good idea, but I had no luck with that one either. Thanks though.
Alright, shreyas said device is "Android 1.0" from windows device manager when the phone is in fastboot. Why does mine say "Android Bootloader Interface" and is this the case for everyone else?
Even more interestingly, I'll uninstall it, manually install whatever driver I chose for it, and that installation will fail. Then, I'll uninstall it again and have 'puter automatically scan for hardware, "android 1.0" pops up as one of the unknown devices but then gets reassigned as "android Bootloader Interface" after automatically installing drivers.
Oh yeah, I'm running Windows 7 64.
The drivers mentioned here didn't help either
http://forum.xda-developers.com/showthread.php?t=702927
stratmn5105571 said:
Oh yeah, I'm running Windows 7 64.
Click to expand...
Click to collapse
i am on win7 32!
btw umm try this link
http://android.modaco.com/content/z...com/319156/winxp-7-zte-blade-drivers-and-adb/
another umm stupid thing mayb, did you try out adb wireless..?
Have you tried using the PDANet drivers? Those are the ones that I've had the best luck with on my Win7 x64 laptop.
EDIT: Seems you have...
I'd recommed using an application called USBDeView (I think?) to manually uninstall all USB drivers for Android/HTC/ADB/NexusOne/etc, and THEN installing the PDANet drivers.
Thanks for your help. I ended up downloading "superboot," which has fastboot on it, and it works just fine. I don't know what the deal is with the fastboot that came with the SDK but my computer just doesn't seem to like it. I checked and rechecked all commands and file directories, and I just don't get it...oh well, I hope this helps others.
Thanks again.
Hi there !
Until now I have successfully installed any version from 6 to 11, using SAMSUNG USB Driver for Mobile Phones.
Today I flashed Build 12 and Google Apps (v7.1). Then I made WIPE (wipe data/factory reset + wipe cache partition) and my GT-I9000 stuck at the boot screen... It is impossible to get into Recovery Mode. I can get into Donwload Mode ! But when I connect my phone via USB and via Odin - my PC cannot recognise the "unknown device". OK, new drivers.
I tried Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe - unsuccessfully - my PC cannot recognise the "unknown device" again.
I installed "Google USB Driver for Windows" (revision 4) with Android SDK and AVD Manager. But my computer's
"Device Manager" cannot "Update Driver Software" - it displays an error : "Code 10" (The device cannot start).
Please, help! Thanks in advance!
A simple solution
Fortunately, after couple hours of reading on SGS forums,
I found simple solution of the problem:
At first, I installed again regular "Samsung Galaxy S USB Driver": (drivers.softpedia.com/progDownload/Samsung-Galaxy-S-USB-Driver-for-Windows-x86-Download-96692.html) and did not used the Google USB driver (for my GT-I9000)!
Second, after changing the USB port on my computer, I did what I read here, in a post from "westy": "...Remove USB cable. Put phone into download mode. Plug USB into phone and then into computer and hopefully Odin picks it up as it did with mine."
(samsunggalaxysforums.com/showthread.php/2530-USB-connection-not-recognized-by-computer/page2)
It works !
Thank you, i have similar situation
Hi,
Im using a stock v30a rom and windows 7.
Yesterday i tried to root my phone with the latest version of AIO tool.
I followed instructions to the letter but while rooting the screen remained blank
AIO tool displayed a message "nvflash started" and went idle.
Rooting older versions was a matter off seconds so after a while i figured nothing
is going to happen and unplugged the usb cable.
The AIO tool then displayed a "usb write error"
The phone is working fine now but when i connect it to my pc in mass storage mode
It disconnects and reconnects all the time as if i was taking the cable in and out.
I did a hard reset , reinstalled LG united phone driver but that did not help.
Update: I connected the phone to a pc at work and mass storage works fine.
Can someone please help me uninstall the nvflash driver?
Looks like the presence of both drivers confused windows.
Figured i post the solution just in case someone has
the same problem.
Remove battery plug usb cable with volume up and down pressed,
Windows recognise "Nvidia usb device" go to device manager and
uninstall its driver.
If next time you connect the phone you get "cdc serial device not
connected" error reinstall lg driver and you re done.
Hello all..
I'm sorry if this is the wrong section, but I can't connect my problem to anything similar..
I've been removing system apps on my phone and, unfortunately I selected Lg Home in a group, and without noticing I deleted it.
I did restart it after it.. and the problems started.
I was able to select the custom Home by LG somehow, but I'm enable to go into settings (getting "Unfortunately, Settings has stopped.")
After that, I noticed that I cannot do really anything on the phone.. my PC no longer recognize my device, usb debugging is disabled.
In addition, I cannot get into fastboot (boot loop, when I'm holding the keys),
I cannot go into recovery too.
I could only get to the LG hard reset page, did reset the phone.. with no success at getting anything back.
I have terminal emulator and SuperSU on my phone (it's rooted).
Is there anything I can do with the terminal? Like send LG drivers to my PC, or restarting in fastboot/recovery?
I even tried to flash the original ROM with LG Flesh Tool.
With that program I cannot get phone information, and when I try to flash I get a message saying that Upgrade stopped due to an error.
It asked me to restart and bla bla.. still same
I did try it from download mode, but my phone did not got recognized on the PC again, so nothing there too.
Whenever I connect the device to the PC, windows is searching for drivers for MTP Usb Driver (and fails everytime). Note: I did have those installed before I messed up the phone.
I have ADB and I'm working with cordova, so I tried to install another andorid on my pc, and it got recognized right away (every driver was installed without doing anything, and I can shell it).
Any advice?
Thanks.
Sorry for spamming..
But, nothing really??
Greetings,
Yesterday i tried to flash twrp + havoc os, like on my previous phone, but i got stuck right on the begining when ADB says the device wasn't found, I have the phone unlocked, usb debugging allowed, and i can access phones internal storage from windows just fine, entered fastboot and still nothing.
Weird thing is after i entered fastboot the Device Manager changed the name of phone to just "Android"
and driver failed to install, then i tried to search the driver with windows built in driver search, and driver was sucesfully installed, but the phone still can't be found by ADB. Really don't know which can be the cause. I have win 7 by the way. Hope somebody can help me with my problem, i appreciate any tips.
Thanks and have a great weekend
ElectroYume said:
Greetings,
Yesterday i tried to flash twrp + havoc os, like on my previous phone, but i got stuck right on the begining when ADB says the device wasn't found, I have the phone unlocked, usb debugging allowed, and i can access phones internal storage from windows just fine, entered fastboot and still nothing.
Weird thing is after i entered fastboot the Device Manager changed the name of phone to just "Android"
and driver failed to install, then i tried to search the driver with windows built in driver search, and driver was sucesfully installed, but the phone still can't be found by ADB. Really don't know which can be the cause. I have win 7 by the way. Hope somebody can help me with my problem, i appreciate any tips.
Thanks and have a great weekend
Click to expand...
Click to collapse
Sounds like the fastboot drivers are missing. I'm sure you can find the drivers if you google it or just download the mi flash tool and install the drivers from there. Test the type c as well maybe the cable has the problem (try to use the official one), test it from a different usb, or an other PC or laptop if you have any.
I had similar issues before using mi flash tool, I tried on my other laptop and was working fine.
Thank you for your advice, it was due to drivers, but now im struggling with some very weird problem, i managed to flash twrp, and installed havoc (later tried lineage) succesfully, but when i boot the phone, it boots into fastboot instead of android for some reason, i tried installing the rom several times, everytime succesfully, deleted dalvik cache and so on.. Its just booting to fastboot for some reason.