Database Develop

[Q] Phone and recovery doesn't work, odin doesn't flash on dl mode

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?

Fastboot-Drivers-HELP!

So I need help XDA fams. I am currently trying to update my N6 to 5.0.1. The issue i'm having is that my pc wont connect to my N6 while in bootloader. When in bootloader the usb seems to work fine, im assuming, since im getting "transfer mode: usb connected" on the very bottom of the phone screen. But when i adb and check to see if its connected, under "list of devices attached", nothing shows up.
When the N6 is booted up normally it works perfectly fine. I'm able to adb into my phone and it shows up under "list of devices attached".
Ive read around and know windows 8.1 and usb 3.0 drivers might be an issue. So I tried both usb google drivers and the universal naked drivers. I've uninstalled and reinstalled a crap load of times and nothing.
This thing is pissing me off. CAN ANYONE HELP OUT!

Adb is for Android. When you are in the boot loader, you use fastboot.
Try "fastboot devices"

El Daddy said:
Adb is for Android. When you are in the boot loader, you use fastboot.
Try "fastboot devices"
Click to expand...
Click to collapse
Wow lol. I feel stupid. Thanks man. Didnt know that.
But im still having an issue with it being recognized. I go into recovery mode and select the "apply update from adb". When trying to sideload the zip file i keep getting "error: device not found".
Any ideas?

jrforlife said:
Wow lol. I feel stupid. Thanks man. Didnt know that.
But im still having an issue with it being recognized. I go into recovery mode and select the "apply update from adb". When trying to sideload the zip file i keep getting "error: device not found".
Any ideas?
Click to expand...
Click to collapse
Check your device manager in Windows. Make sure it says "ADB Composite Interface" or something similar. If not, you'll have to install the drivers again.
Also, make sure you have the latest ADB package from the SDK.

Device not found in adb sideload or recovery trying to install 5.1 otc

So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......

Gage_Hero said:
So i downloaded the sdk.... plugged in the phone windows installed the adb composite driver I open command prompt in the platform tools folder run adb devices yes it is there reboot the phone into recovery.... many times.... do adb devices... nothing shows up apply from adb no device.... I'm on windows 7 64 I'm pretty sure its a driver issue but I can't get it to recognize the phone in recovery.... everything is stock on the phone bootloader still locked ( wouldn't be able to do that either since yeah no adb action.... using the cable that came with the phone tried multiple ports..... maybe someone can explain how to install the driver so it works? right now in device manager it shows up as Android device then below that adb composite driver..... this part I understand sort of... was expecting to see nexus 6 but how would I know...... if anyone has the actual driver that works I would appreciate it
Installed motorola device manager for windows.. no difference..... edited the inf file from sdk .... no difference..... I'd try another computer but probably end up installing the same driver so no point there....
edit edit also removed every hint of the old samsung drivers since I came from s4 to nexus......
Click to expand...
Click to collapse
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I will try wugfish to install the drivers and then see if I can use ADB after that.... I definitely did not have the device show up as nexus 6 in device manager other than the mtp part... pretty hard for that not to show up..... I'll give it a shot on Sunday unless the ota drops to the phone first.

A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app

Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.

tvtodd said:
Had the same problem on a Win7 machine that I have used for several phones. Would see the device in ADB when full booted, see it in fastboot, but when in ADB sideload, could not see it. Turns out it was trying to use the Samsung ADB vs. Google/N6 driver for ADB. Had to do a lot of hoop jumping, deleting/changing drivers, but worked great after.
Click to expand...
Click to collapse
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.

z28 justin said:
Can you explain exactly what you did? This is exactly what my N6 is doing. When the phone is on, under "Device Manager" it says "Samsung Android Phone - Android Composite ADB Interface". When in Bootloader it says it is a a "Samsung Android Phone - Android Bootloader Interface" and I keep deleting the driver and trying to reinstall the default drivers from the SDK Manager but it just keeps loading as the damn Samsung.
Click to expand...
Click to collapse
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....

Gage_Hero said:
I successfully installed the correct drivers.... Download wugfish for n6, at the top when its installed, there is a button in the middle to setup drivers, follow the instructions exactly and it will work. Of course before someone jumps on me, I do plan to sideload through command prompt....
Click to expand...
Click to collapse
I followed those instructions as well and it still registered as a Samsung Device. However, I did finally get it to work by going through my "Uninstall or change a program list" and removing a "Samsung Driver Installation" program I had installed for my wife's S4. Then I ran back through Wugfish's driver directions and sure enough, it finally registered as a standard Android device and not a damn Samsung.

I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!

Mephisto_POA said:
I've tried on my Nexus 6, every time it goes to recovery mode it doesn't show up in device manager.
I've already unistalled all drivers, used the nexus root tool to reinstall the drivers, it doesn't matter. It works fine the first part when you need to use ADB to restart the device in bootloader mode, then you select recovery and nothing happens the device never shows up, so I can't install/uninstall any drivers because it simply doesn't display anywhere, wtf!
Click to expand...
Click to collapse
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app

I don't know if this will solve your issues. When I was side loading the 5.1 update I couldn't get tmy win 7 machine to see the device after rebooting from adb to sideload.
I ended up finding a thread somewhere that suggested a newer version of adb. Once I downloaded the most recent version it installed fine.
I also rebooted into fastboot through adb, went to device manager and found my nexus, manually updated the driver. After all that everything worked fine.
Don't know if that helps or not....

I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.

Intub8 said:
Did you try to disconnect and reconnect the USB while the phone was in recovery?
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
I found the problem
each mode has a unique hardware ID
when phone is in normal mode with USB debug, when it is at bootloader and then afterwards when it is in recovery mode
the last mode, hardware ID VID_18D1&PID_D001 didn't get any dirvers installed, evne downloading official drivers from google and other parties.
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
lukesdiesel said:
I can't get my computer to show my N6 as a phone. All it shows is Unknown Device. I've loaded the Google Drivers yet it doesn't list them when trying to load them manually.
Click to expand...
Click to collapse
https://www.reddit.com/r/nexus6/comments/2yyfri/nexus_6_not_getting_detected_during/
check this

got it to work
I got it to work by unplugging and plugging back in once I had hit the adb sideload option in recovery. When I was just in recovery it had no effect.
rkshack

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
thanks. this worked

Mephisto_POA said:
I had to manually edit the android_winusb.inf file and add the hardware ID %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001 under ;Google Nexus (generic)
Click to expand...
Click to collapse
My device needed %CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002.

This happened to me too, I just ended up using a different computer: https://plus.google.com/+LoganJonesJ/posts/hrDRAnyrotf

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Click to expand...
Click to collapse
Worked for me as well, thanks!

Intub8 said:
This is what I did.
When you get to the phone into recovery mode unplug the USB plug and then plug it back in again. Windows should search for the driver. When windows finishes open device manager. Look for the nexus 6 with the yellow icon. Follow the steps attached in the picture. Credit for the driver steps goes to wugfresh, steps obtained from his toolkit.
Sent from my Nexus 6 using XDA Premium HD app
Click to expand...
Click to collapse
Worked like a charm. Thanks!

A2CKilla said:
A simple unplug and replug in fixes the issue...when you get to the adb point on the phone and you make sure the driver is installed on the computer correctly, simply unplug from the computer, replug in and continue
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks so much for this! I had tried EVERYTHING trying to get my 6P to connect with no success. This simple fix was exactly what I needed.

Side Loading OTA Update help

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!

Stuck at Fastboot while Rooting

Hi All,
I installed all the drivers for ADB (do I need some for Fastboot?). While rooting my fire does not want to wake up after going into fastboot mode. I can manually turn it off and on back again, but cannot finish rooting as the command shell is waiting for the device to boot and it never boots up.
Also, I cannot hear the device plug in sound in windows while my fire goes into fastboot mode (while I can clearly hear one when watching YT video regarding rooting instructions)... That may be a clue?
Thanks for any help. And Big thanks for all the developers!
Also, I tried to update the drivers one more time to see if they were the problem. And after uninstalling device and pluging it back in, Windows allows me to choose MTP USB device only... When I point the right path to .inf file it gives me an error of:
---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
---------------------------
OK
---------------------------
Any ideas?

Ok, I managed to install the drivers by turning off the mtp connection in developer settings. But that did not help... Still getting stuck in fastboot mode.

rybaryba33 said:
Ok, I managed to install the drivers by turning off the mtp connection in developer settings. But that did not help... Still getting stuck in fastboot mode.
Click to expand...
Click to collapse
just root with Supersu.zip in twrp
[CUSTOM RECOVERY] TWRP Recovery
Sent from my KFFOWI using Tapatalk

I managed to root using root.bat
I somehow installed fastboot drives and I did it, when I pressed vol up and power button. I acted fast to install the drivers. Then I just followed instructions and gained full root.
Thanks again developers! I shall donate so you can have a few drinks on me