Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Adb in recovery

OP Keithn

21st August 2014, 07:12 PM   |  #1  
OP Senior Member
Thanks Meter: 139
 
546 posts
Join Date:Joined: Feb 2011
More
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.

Sent from my One M8
22nd August 2014, 01:10 AM   |  #2  
OP Senior Member
Thanks Meter: 139
 
546 posts
Join Date:Joined: Feb 2011
More
Quote:
Originally Posted by Keithn

Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.

Sent from my One M8

Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
22nd August 2014, 07:44 AM   |  #3  
Unjustified Dev's Avatar
Recognized Developer
Flag Memphis , TN
Thanks Meter: 5,251
 
5,035 posts
Join Date:Joined: Oct 2012
Donate to Me
More
Quote:
Originally Posted by Keithn

Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.

Could you send me stock recovery so I can take a look inside the init.rc
22nd August 2014, 03:00 PM   |  #4  
OP Senior Member
Thanks Meter: 139
 
546 posts
Join Date:Joined: Feb 2011
More
Yeah, I'll do that today

Sent from my One M8
22nd August 2014, 05:13 PM   |  #5  
Unjustified Dev's Avatar
Recognized Developer
Flag Memphis , TN
Thanks Meter: 5,251
 
5,035 posts
Join Date:Joined: Oct 2012
Donate to Me
More
Quote:
Originally Posted by Keithn

Yeah, I'll do that today

Sent from my One M8

I found it inside the stock nvidia images for testing on the k1 board thanks.

This appeared to be the issue https://github.com/cm-ardbeg/android...very.ardbeg.rc
The Following 2 Users Say Thank You to Unjustified Dev For This Useful Post: [ View ]
22nd August 2014, 08:10 PM   |  #6  
OP Senior Member
Thanks Meter: 139
 
546 posts
Join Date:Joined: Feb 2011
More
Quote:
Originally Posted by Unjustified Dev

I found it inside the stock nvidia images for testing on the k1 board thanks.

This appeared to be the issue https://github.com/cm-ardbeg/android...very.ardbeg.rc

If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
23rd August 2014, 02:10 AM   |  #7  
Unjustified Dev's Avatar
Recognized Developer
Flag Memphis , TN
Thanks Meter: 5,251
 
5,035 posts
Join Date:Joined: Oct 2012
Donate to Me
More
Quote:
Originally Posted by Keithn

If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.

I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Attached Files
File Type: img recovery.img - [Click for QR Code] (9.49 MB, 11 views)
Last edited by Unjustified Dev; 23rd August 2014 at 02:12 AM.
23rd August 2014, 02:23 AM   |  #8  
OP Senior Member
Thanks Meter: 139
 
546 posts
Join Date:Joined: Feb 2011
More
Quote:
Originally Posted by Unjustified Dev

I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working

Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)

A request for the USB configuration descriptor failed.
for device status.

I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________

Nothing in Ubuntu either, even lsusb doesn't list it.
Last edited by Keithn; 23rd August 2014 at 02:52 AM.
The Following User Says Thank You to Keithn For This Useful Post: [ View ]
23rd August 2014, 02:57 AM   |  #9  
Unjustified Dev's Avatar
Recognized Developer
Flag Memphis , TN
Thanks Meter: 5,251
 
5,035 posts
Join Date:Joined: Oct 2012
Donate to Me
More
Quote:
Originally Posted by Keithn

Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me

Code:
Windows has stopped this device because it has reported problems. (Code 43)

A request for the USB configuration descriptor failed.
for device status.

I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________

Nothing in Ubuntu either, even lsusb doesn't list it.

This is crazy does adb work in the recovery you compile from their git?
Last edited by Unjustified Dev; 23rd August 2014 at 03:17 AM.
23rd August 2014, 03:35 AM   |  #10  
OP Senior Member
Thanks Meter: 139
 
546 posts
Join Date:Joined: Feb 2011
More
Quote:
Originally Posted by Unjustified Dev

This is crazy does adb work in the recovery you compile from their git?

I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.

The Following User Says Thank You to Keithn For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes