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.
I have a Samsung Galaxy Ace (S5830), a week ago when i woke up i released that it was not working. Before that i tried to change my imei, and i couldn't. But it worked after my fail at changing imei, than after a few hours it stopped working. When i try to power on, backlight turns on and off, sometimes it happens twice or thrice or till it's battery is over. Just turns on light and off. It goes on download mode, and ramdump mode. Recovery mode doesn't work. When i try to flash a rom via Odin, pc identifies my phone, odin starts but after Odin says "close serial port...", it tries to reboot but it cannot again, turns on and off the backlight again.
So, i think something is wrong with booting section, do you have an idea about this problem?
Thanks for reading.
Do you have all the USB drivers for the ace?
Does your Odin show the yellow box when you connect your phone?
If you can reach dl mode, you have a greater chance of unbricking! But I fear you will lose your imei and you wont be able to call..
Sent from my Ex-Hard bricked Galaxy Ace!
galaxyace152 said:
Do you have all the USB drivers for the ace?
Does your Odin show the yellow box when you connect your phone?
If you can reach dl mode, you have a greater chance of unbricking! But I fear you will lose your imei and you wont be able to call..
Sent from my Ex-Hard bricked Galaxy Ace!
Click to expand...
Click to collapse
Yes odin shows the yellow box, and i can reach dl mode. But as i said, via Odin or Power button when my ace tries to reboot, it just turns light on and off. I cannot do anything.
you tried adb for recovery? Connect phone in download mode and use adb to go to recovery mode.
Xr01d_GT said:
you tried adb for recovery? Connect phone in download mode and use adb to go to recovery mode.
Click to expand...
Click to collapse
i've never heard about it, i'm trying right now! Hope it works, thanks a lot.
edizkralll said:
i've never heard about it, i'm trying right now! Hope it works, thanks a lot.
Click to expand...
Click to collapse
sorry about flooding, but how can i use it to get to the recovery mode? can you explain it? Thanks.
edizkralll said:
sorry about flooding, but how can i use it to get to the recovery mode? can you explain it? Thanks.
Click to expand...
Click to collapse
When i try "cd c:\android-sdk\platform-tools" and "adb -d reboot recovery" i get an "device not found" error. I use win77x64, i have "Samsung USB Composite Device" under my device manager/usb devices list. I've installed google drivers via sdk manager but it doesn't seem on my device manager. what should i do ?
edit: as i understand, it is necessary to be checked "usb debugging mode" for my pc to see my phone as an adb device. my phone is closed and i cannot power it on, can i do this ? i think adb works for my problem, but i couldn't use it. it always says "device not found".
edizkralll said:
When i try "cd c:\android-sdk\platform-tools" and "adb -d reboot recovery" i get an "device not found" error. I use win77x64, i have "Samsung USB Composite Device" under my device manager/usb devices list. I've installed google drivers via sdk manager but it doesn't seem on my device manager. what should i do ?
edit: as i understand, it is necessary to be checked "usb debugging mode" for my pc to see my phone as an adb device. my phone is closed and i cannot power it on, can i do this ? i think adb works for my problem, but i couldn't use it. it always says "device not found".
Click to expand...
Click to collapse
OK..try these things..
Code:
adb start-server *to start adb*
adb get-state *it'll show whether device is connected or not*
adb reboot recovery *to go into recovery mode*
Correct Me if I'm wrong, but usually USB debugging is enabled by default I think.
BTW, when you plug in your device, does it light up or shows any activity?
I've installed google drivers via sdk manager but it doesn't seem on my device manager.
Click to expand...
Click to collapse
Google drivers as in? Samsung USB Composite Device should be there when You connect your phone, that's your phone drivers.
P.S:I'm attaching My ADB (I don't use the whole SDK) if you think you need them, copy them to any folder and open command prompt from there (shift+right-click combo),and run the adb daemon from there.
Xr01d_GT said:
OK..try these things..
Code:
adb start-server *to start adb*
adb get-state *it'll show whether device is connected or not*
adb reboot recovery *to go into recovery mode*
Correct Me if I'm wrong, but usually USB debugging is enabled by default I think.
BTW, when you plug in your device, does it light up or shows any activity?
Google drivers as in? Samsung USB Composite Device should be there when You connect your phone, that's your phone drivers.
P.S:I'm attaching My ADB (I don't use the whole SDK) if you think you need them, copy them to any folder and open command prompt from there (shift+right-click combo),and run the adb daemon from there.
Click to expand...
Click to collapse
When i connect my phone there seems "samsung usb composite device" it's ok.
when i write on cmd;
"cd c:\android-sdk\platform-tools\"
"adb start-server"
it says "daemon started succesfully"
and when i write "adb get-state"
it says "unknown".
i'm checking google now, hope find something about it. can you help me with it?do you have an idea?
edit: i've searched a lot on google, but i couldn't find anything. i think i must edit an adb_usb.ini file but i don't know what to do. my problem is adb doesn't see my phone, i don't know if it works after adb sees my phone but i want to try it. i cannot use my phone for 2 weeks and i'm really tired about it.
edizkralll said:
When i connect my phone there seems "samsung usb composite device" it's ok.
when i write on cmd;
"cd c:\android-sdk\platform-tools\"
"adb start-server"
it says "daemon started succesfully"
and when i write "adb get-state"
it says "unknown".
i'm checking google now, hope find something about it. can you help me with it?do you have an idea?
Click to expand...
Click to collapse
unknown it means your device is not detected..did you connect device to PC when in download mode??!
Xr01d_GT said:
unknown it means your device is not detected..did you connect device to PC when in download mode??!
Click to expand...
Click to collapse
Of course, yes.
Has anybody actually tried the adb reboot recovery? It doesn't work, you need to use the button combination.
Type 'adb devices' to see if your phone is recognized.
Sent from my GALAXY Ace.
tomb20 said:
Has anybody actually tried the adb reboot recovery? It doesn't work, you need to use the button combination.
Type 'adb devices' to see if your phone is recognized.
Sent from my GALAXY Ace.
Click to expand...
Click to collapse
Thanks for answer but i've already tried that command "adb devices", nothing listed.
tomb20 said:
Has anybody actually tried the adb reboot recovery? It doesn't work, you need to use the button combination.
Type 'adb devices' to see if your phone is recognized.
Sent from my GALAXY Ace.
Click to expand...
Click to collapse
Who said it doesn't work? I always use that, kind of never get the buttons combo
---------- Post added at 10:12 PM ---------- Previous post was at 09:59 PM ----------
edizkralll said:
Of course, yes.
Click to expand...
Click to collapse
OK. Then this is the last resort. Uninstall all the phone drivers and re-install them. Win 7 automatically downloads from the internet if the windows update is on.Then via adb try for recovery.
Xr01d_GT said:
Who said it doesn't work? I always use that, kind of never get the buttons combo
---------- Post added at 10:12 PM ---------- Previous post was at 09:59 PM ----------
OK. Then this is the last resort. Uninstall all the phone drivers and re-install them. Win 7 automatically downloads from the internet if the windows update is on.Then via adb try for recovery.
Click to expand...
Click to collapse
i tried it thrice, uninstalled everything and re-installed. tried on another pc, but it didn't see my phone again. should i change something in adb_usb.ini ?
any more ideas ?
I' ve purchased a "usb jig", but when i plugged it to my phone it started to turn light on and off action again. i'm really bored about it, what else can i do?
I’m a noob when it comes to android adb but I'm an IT guy so what the hell I want 5.1.
I am following some directions on line on how to side load the OTA update seems easy, just a few commands and it should work. Here is what I'm doing and where I'm getting stuck any help?
Loaded Android SDK
Enabled Dev options, USB Debugging and OEM Unlock.
adb Devices - shows my device
adb reboot bootloader – restarts into the bootloader.
Select Recover Mode
Hold Power button, then press once the Volume Up button. To get Recovery Mode
This is where I get stuck, I'm reading I need to send the command “adb sideload <filename of update.zip>” but at this point ADB no longer sees my nexus 6? Nothing happens when I run this command and nothing is reported when I run ADB Devices?
Now I'm thinking drivers but I loaded the drivers? Can someone point me in the right direction?
I'm trying on a Windows 8 PC
Also when I'm looking at the device manager everything shows up fine until i enter the recover. At this point nothing shows up in device manager and when i resead the USB cable nothing happens no sound like im disconnecting something and reconnecting it, not device manager refresh, weird.
update! got it working.
So it turns out the device manager dose not show anything until you get into adb sideload options then the wrong driver is loaded and i had to manual pick Android adb driver. once i did this i was able to side load the ota update and now on 5.1.
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
tom1226 said:
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
Click to expand...
Click to collapse
Thanks you are right you have to be in the adb sideload options for the phone to show up in device manager and at this point it was not seeing the right driver, once i picked android adb driver i was able to update Thanks!
Awesome, glad it worked out for you!
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?
I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse
Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** device
Then I can do "adb reboot bootloader"
Phone shuts down and get on fastboot with this "waiting for device" I got stuck there.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Sent from my SM-A800F using XDA-Developers mobile app
Yeah I'm experiencing this too as well! I just recently updated to 20p and I am trying to root again. I was able to use fastboot to install twrp before. Don't know why this is happening.
This is what I did
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Bootloader unrecognized
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
wish0 said:
In fatsboot I saw in device manager my phone was "rats I don't remember-something bootloader device" I chose update driver and browse my filkes and chose the marshal one. after that everything worked fine. Sry I'm an anxious person. Hopes this helps and if not or I could help more ask me more and hopefully I'll be more mellow lol.
Click to expand...
Click to collapse
[email protected] said:
I used the app shared above and used it to locate the driver and ended up having to roll back to a previous driver and it worked in my case.
Click to expand...
Click to collapse
Can one of you share a link to the driver you used?
MaRz0o said:
Can one of you share a link to the driver you used?
Click to expand...
Click to collapse
I'm at work won't get off for another 13 hours but like the post maybe two above here it was Marshall something. Go to device manager look for the boot loader adb interface can't remember exactly what it's called and double click it and use the menu option to rollback not update the driver and you should be good. I tried everything else including the one touch and only the rollback worked.
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
chromiumfan said:
For my computer, it shown up as something like "Kedacom USB Device" in the Device Manager, but I rolled back that driver from 11 to 9 and it worked beautifully!
Click to expand...
Click to collapse
Do you have the driver? I have none to roll back to.
Okay...
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
wish0 said:
Okay so yeah it says kedacom usb device, that gives me the waiting for device error...in device manager when im in fastboot mode find kedacom device and click on it to see android bootloader interface. Right click on the android bootloader interface and choose update driver, browse my computer for driver software, then let me pick from a list of device drivers on my computer. From there I choose marshal London bootloader interface. From there everything works... don't have to restart computer of phone, everything works together perfect. Either it came with my computer or its from this install of adb... the 15 sec adb installer http://forum.xda-developers.com/showthread.php?t=2588979. Try my steps see if it works!
Click to expand...
Click to collapse
I am having the "waiting for device" issue. But I dont have the "Marshal London" drivers. I have adb 15 sec drivers installed. Any idea where I could get them?
okay another try..
Okay have you tried, while the waiting for device prompt is up, instead of telling your computer you want to select from the list of drivers, to choose automatic: search online for the driver?