Attempted to ask this here, but I don't have privileges to post there. I just installed MIUI on my Kindle Fire (which I received today), and its working great, other than a few issues.
1. I can no longer access the Kindle from my computer (even though USB debugging is connected), but this hasn't been listed as a known issue. Is there a way to fix this?
2. My Gmail and File Browser apps seem to have disappeared, though I can still access them via Manage Applications - is there a way to get them back on the home screen?
And big thanks to all you devs for the awesome work!
Any ideas?
I've a similar prob. w/usb in ics. Hear pc sound but nothing on kf. I have to mount usb in TWRP. Anyone a clue MIUI and/or ICS?
I have questions about MIUI also. Mine seems to be partly in Japanese. Is there a way to have the labels in English? Also there is no disconnect button for removing it from the usb cable . I have been ejecting it at the pc and hoping that is alright.
Thanks,
BBC0
Related
I am very impressed with my Galaxy Tab 10.1, but I'm having a glaring problem: my PC won't detect it as a storage device. This is the one that came with 3.1 out of the box, and I assumed that it would connect to my PC and play perfectly with it. I guess I've been spoiled by how my HTC Evo always connected perfectly to my PC with no issues or no drivers for me to hunt down and install, because it didn't work.
Okay, no sweat, I just need to download the drivers and install them, right? I did just that as well. I connect the tablet to the PC (which runs Windows 7 64-bit), and the PC gives me notifications saying my device is ready to use, but I can't find it as a storage device at all under My Computer. I do find it in my "Devices and Printers" list, but it doesn't show up with the rest of my devices at the top (it shows up with unspecified devices or something at the bottom of the list with a generic-looking icon representing it).
Okay, I probably need to just uninstall the drivers and maybe reinstall them and try again, right? Did just that, no dice. The exact same thing happens. On the tablet, I also probably need to point out that the only thing I get is the "USB Debugging Detected" notification or whatever it says while Windows 7 doesn't pick it up.
So now I ask what everybody else did to get theirs recognized. And I already tried switching USB ports and checking for updates. No dice there, either.
Wow, I feel like an idiot after solving this problem, but just so I can spare anybody else who has the same issue the trouble of going through this, I'll post what the solution was for me.
Unplug the tablet and disable USB debugging on the tablet first, then plug it back in and it'll be picked up as a generic cell phone by My Computer. Hope this helps somebody in the future. Heh...
Honestly, I really didn't think that would solve the problem, and I did search beforehand and found nothing of the sort telling me that doing just that would have fixed the problem.
I have searched the Q&A and General forums and found no one with my question.
Some time ago I noticed that my NC is no longer recognized when I plug it in to my PC via the stock USB cable. I am now on n147 and the problem persists.
By "not recognized" I mean that the PC doesn't see it in any capacity. No ADB Composite Interface, no generic Composite USB interface... Nothing. I can plug it in, pull it out, all with no recognition whatsoever.
I have ADB and the USB drivers installed. As I said, this used to work flawlessly.
Can anyone offer any solutions or suggestions for how I can figure out where the problem is?
When you plugged the NC in, did you see any "removable drive" on PC?
No.
No removable drives, with or without drive letters and no new devices listed in the Device Manager.
I don't know if the nb148 causing this problem or not but have you installed Nook Color Tweak lately?
nb148? Not sure what that is.
I installed NC Tweaks as soon as it came out and have had it installed since then.
I suppose I could try uninstalling it and seeing if that fixes things, but I don't think it will since the changes are already in the kernel and Tweaks is there simply to make modifications of variables.
night-build 148 that is
Anyway, if you have Nook Tweak installed, then make sure to CHECK OFF the Host USB option.
votinh said:
I don't know if the nb148 causing this problem or not but have you installed Nook Color Tweak lately?
Click to expand...
Click to collapse
Since Nightly 147 is the latest at this point in time... 148 cannot be causing the problem.
Thanks Dizzy.
I don't have USB Host on.
How's about now?
Given that this has been a problem since the sub-n130 releases, I doubt n148 will make a difference.
n148 makes no difference and I've now lost deep sleep.
I guess there's nothing to be done. It's too bad too, since I like using the internal storage.
I have no problem at all running with Win7 x64 OS
I didn't use to either... Until I did.
@mr_fosi: Did you go in and disable usb debugging mode?
If you have done that and still have the problem... you may need to go through device manager, on view menu check show hidden device, delete all B&N devices in any group they show in (most likely only in Disk drives) and all devices in Universal Serial Bus controllers that have device ID's beginning with VID_2080.
Hi again Dizzy.
Yes, I tried disabling USB Debugging but it didn't do anything.
I also tried your other suggestion and I see no applicable devices once I show hidden devices. No USB devices with that VID and no disk drives.
I found that the stock Nook Color cable will NOT work.
BUT I can use just about any other cable and it connects fine.
I run Win 7 64 bit.
Try a different cable and see if that helps.
Thanks for the suggestion, framitz.
I'll give it a go and see what happens.
mr_fosi said:
Thanks for the suggestion, framitz.
I'll give it a go and see what happens.
Click to expand...
Click to collapse
If you don't get it going... pm me... I'll write a program to scour the registry looking for known NC devices and remove them... should make reinstalling drivers easier.
You may want to hook the NC up and look for any "unknown" devices in device manager and add info to the winusb.inf file for installing drivers... I've added a couple that some older rom's reported the device as.
Hi guys!
I've had a problem over the day with my beloved HD2, and I've started to fear that it might actually be the hardware starting to decay. About a day or two ago, when inserting my phone to the MicroUSB cable, it recognized the HD2 just fine, had access too USB mount, ADB and all of that. Transfered some music to the SD-card (Trancent 16gigs Class 4, btw - still very well recognized by the phone to the time at writing this), but now, some time later I get nothing out of connecting the phone to either my laptop or rig.
I know it's not the drivers or the cable, since I've tried with others cables and a few other computers. The message is the same old "The device could not be recognized". But the funny thing is, somehow the device must know that its connected to a computer anyway, 'cause it instantly enables debugging and the option to enable mount. I, as of now, has had no luck getting into the SD card, sadly. Not even been able to pull logcats or anything, setting up wireless ADB hasn't been sucessful either - so where I stand now, I'm kinda in need for a helping hand.
Has anyone else ever had this problem too, or am I left out in the cold?
By the way, even managed to put on an older nightly CM9 build, as it was stored on my SD. No luck there either. MAGLDR mount / recovery mount doesn't function either. Same error.
The ROM I first had the problem on was PARANOIDANDROID v0.6. Then a nightly CM9 from sometime last week. Both immensely close to stock and ICS based. LEO512, by the way.
Please, give me a hand!
TL;DR: USB broken, still charging, help.
Your usb is getting loose (usb data connection becomes irratic and then stops working, continued use results in USB port ripped from mainboard), try to not use it while plugged in and see if the repair shop can fix it for you without breaking usb data. You can use the SwiFTP app in playstore to transfer files in the mean time.
You may also want to use a cradle charger to minimize USB port being used.
Maybe I'm searching for the wrong thing but I'm just finding people having the same problem but not what to do about it. After the 7.1.1 update whenever I connect a USB cable to the PC it just goes into charging mode and I haven't had time to mess with it until now.
I've tried several different cables (that always worked until now) and 2 different windows 10 PCs, but even with the different options in the developers options section (MTP, charging only, etc) I never get that option in the notifications section under power, what do you want to do with this? etc.
I'm trying to unlock the bootloader but even in recovery it just says to connect a USB cable and nothing shows up PC side like it used to before the update.
Anyone know what to do about this or point me to a thread I missed with a solution?
Thanks
edit: or even if its possible to revert to whatever stock version it came with?
edit2: Tried a xubuntu livecd, same deal. Kind of rules out OS. Wonderful, going to have to do some ass backwards way to get music on here.
Hello.
I've got my mother's Samsung A20. And i need to recover data, but the screen doesn't work.
When power button is pressed, display flashes the lock screen (wallpaper, current time and so on). And then it turns black (backlight stays on for 30 seconds, and then turns off). Pressing the button doesn't guarantee flashing the display, sometimes it goes black immediately. Touch screen gives no input as far as i know (can't hear anything when trying to type pin). Problem still occurs during and after reboots.
I managed to connect a mouse and keyboard with USB OTG, and i was able to unlock. But the phone has no MHL support, so i can't get any image through USB. I'd try pressing the power button repeatedly to get some image and inch my way through the interface, but the lockscreen interferes.
The USB port is set to Charging Only mode, so i can't copy files to my computer. USB Debugging is disabled, bootloader is locked.
Does anybody have a clue, how to get image? Some way to get data? Maybe some keyboard shortcuts, so i can disable lockscreen and make my way easier? And maybe disable 20 alarms in the morning?
damiandbcz said:
I'd try pressing the power button repeatedly to get some image and inch my way through the interface, but the lockscreen interferes.
Click to expand...
Click to collapse
I like to be helpful so I'll try to give you some suggestions but I hope others pitch in who know far more than I do.
I never use the USB cable anymore to operate my phone from my PC (but my screen isn't broken so your situation will be much harder).
I connect to my phone from Windows over Wi-Fi without USB all the time, and I can unlock my screen from the PC, and I can mount my entire Android device as a drive letter on Windows over Wi-Fi, etc., so "maybe" (just maybe though), you can consider using either a WebDav server on Android to access your files and/or adb to bring up and manipulate activities on Android....
damiandbcz said:
The USB port is set to Charging Only mode, so i can't copy files to my computer. USB Debugging is disabled, bootloader is locked.
Click to expand...
Click to collapse
However, I don't know if adb will work for you if you can't turn on USB debugging in the first place... but as of Android 12, adb now works completely over Wi-Fi (see screenshots below) without needing the USB cable to establish the initial connection like it used to be prior to Android 12.
damiandbcz said:
Does anybody have a clue, how to get image? Some way to get data? Maybe some keyboard shortcuts, so i can disable lockscreen and make my way easier? And maybe disable 20 alarms in the morning?
Click to expand...
Click to collapse
If the screen problem is "just" hardware and not software, and if you can turn on Wireless Debugging, you might be able to display your phone over scrcpy or vysor (both of which use adb over Wi-Fi) as shown in the screenshots below on my phone - which never needs the USB cable connection.
Hope this helps, but you seem to need folks who know more than I do as adb/vysor/scrcpy all work for me because I can set up USB Debugging & Wireless Debugging as shown below.
Note that you might have an FTP server or a WebDav Server on your Android phone, and if you do, you might be able to at least transfer important files since they each can mount your entire Android phone as a drive letter on Windows over Wi-Fi (without needing the USB cable).
GalaxyA325G said:
I like to be helpful so I'll try to give you some suggestions but I hope others pitch in who know far more than I do.
I never use the USB cable anymore to operate my phone from my PC (but my screen isn't broken so your situation will be much harder).
I connect to my phone from Windows over Wi-Fi without USB all the time, and I can unlock my screen from the PC, and I can mount my entire Android device as a drive letter on Windows over Wi-Fi, etc., so "maybe" (just maybe though), you can consider using either a WebDav server on Android to access your files and/or adb to bring up and manipulate activities on Android....
However, I don't know if adb will work for you if you can't turn on USB debugging in the first place... but as of Android 12, adb now works completely over Wi-Fi (see screenshots below) without needing the USB cable to establish the initial connection like it used to be prior to Android 12.
If the screen problem is "just" hardware and not software, and if you can turn on Wireless Debugging, you might be able to display your phone over scrcpy or vysor (both of which use adb over Wi-Fi) as shown in the screenshots below on my phone - which never needs the USB cable connection.
Hope this helps, but you seem to need folks who know more than I do as adb/vysor/scrcpy all work for me because I can set up USB Debugging & Wireless Debugging as shown below.
Note that you might have an FTP server or a WebDav Server on your Android phone, and if you do, you might be able to at least transfer important files since they each can mount your entire Android phone as a drive letter on Windows over Wi-Fi (without needing the USB cable).
Click to expand...
Click to collapse
A20 can have only Android 9, 10 or 11, but thanks for ideas anyway.
I didn't even know adb can work over WiFi, I'll look into it. Hopefully this version can do it too.
Now trying blindly to turn on the screen reader…
damiandbcz said:
A20 can have only Android 9, 10 or 11, but thanks for ideas anyway.
I didn't even know adb can work over WiFi, I'll look into it. Hopefully this version can do it too.
Click to expand...
Click to collapse
Ooops. My bad. I apologize. You'll need the USB cable in Android 11 for a moment to establish the connection first. Then you can switch over to Wi-Fi after that (or you can stay on USB).
damiandbcz said:
Now trying blindly to turn on the screen reader…
Click to expand...
Click to collapse
I feel for you. I really do. It hurts me when people can't access their phone remotely to get their data back. I am searching all over the XDA site for a solution for you, where I just moments ago opened this thread to help (I'm still searching for you though).
What is the best XDA solution to control Android on the PC & recover data over Wi-Fi when the user suddenly has an unresponsive broken screen?