Related
Hi All,
Not sure if this is the right place to post this but i'm going to try anyway:
I've just recently downloaded adbWireless on my x10 mini but on the load screen of the app i've only got half the page - the part that i actually need is hidden and i can't scroll down... obviously because of the screen size... is there any other way to show the rest?
Surely i can't be the only experiencing this?
Thx.
Nvm, i see they released an update which fixed it.
Has anybody got this to work on the Mini?
I´ve tried the app yesterday, but no success. Display issues commented earlier are fixed, but i can´t connect with the device. Tried to restart the tcpip 5555 port through adb shell when usb connected, but no luck (it always returns an error).
Exactly the same thing happening to me - although every now and then i get a widget popping up in the status bar saying that's it's been enabled.
Still can't connect to it though...
Hi mates,
since this evening, my Galaxy S2 (unbranded, unrooted, with stock firmware) was connecting fine with my PC in the "kies mode". I could use kies flawlessy, and I could regularly see my phone in my windows 7 (x86) explorer, and use explorer to read and write files from and to its memory.
Then, this evening, I got a notification, from kies, that an update (of kies) was available (2.0.2.11071.182.2), and I gave my consent to the updater. It did all its dirty job but after the installation of the new version, despite the phone connects via USB, every time I try to access the phone's memory from the PC, the connection drops. It restores backafer one second or two, but then again, if I try to access the phone's memory, it drops agains. The problem appears indifferently when accessing phone's memory from kies, and when doing it from windows' explorer, and this makes me suspect of the drivers, that the new version of kies brought along.
The phone connects correctly to the PC in the direct USB mode, and I can access its memory with no problem, and this also suggests that the problem should be the drivers.
So I uninstalled everything (new kies and drivers), and rebooted the PC, then I dowloaded what I believe is the previous version of kies: 2.0.1.11053.99.3, and launched its installation. After the end of the process, I rebooted the PC, just to be safe. According to the list of the installed software in my PC (in "Control Panel > Uninstall a program"), the drivers have rolled back, as expected, to version 1.3.2410.0 (before they were 1.4.something).
At the first connection of the phone to the PC after the reboot, I got notification from windows that the device installed correctly and it is ready to use (all the tree drivers are indeed reported as installed correctly)...
The point is that all this did not solve the problem at all, and USB connection still behaves exactly as badly as before.
I tried again uninstalling and reinstalling everything, also adding a manual clean up of the windows' registry from any entry related to "samsung", checking that the phone was not set in "USB debugging" mode, and disabling the antivirus, but despite everything appears to be fine, the phone regularly keeps on refusing to maintain USB connection alive everytime I try to access its memory.
What drives me mad is the fact that until this evening, everything was working flawlessly!
What else can I try????
I've just made a test on another PC running windows XP, with latest Kies 2.0.2.11071_128 installed. It's my office PC, and although I'm not 100% sure, I seem to remember that, until yesterday, my phone was connecting fine with it, and with that version of kies. But now, all of a sudden, I have the same problem also with this PC...
So, likely, it is a problem of the phone... the MTP application restarts everytime I try to access the phone from the PC, so... what can I try on the phone, to see if I can fix this annoying issue? I DON'T WANT TO FACTORY RESET MY PHONE, PLEASE!!!!
If any of you has any suggestion, I would be more than grateful...
JuniorGG said:
If any of you has any suggestion, I would be more than grateful...
Click to expand...
Click to collapse
I had the same problem the other day and I could not find a way to fix it, in the end I did a factory reset from Settings/Privacy and its ok now, just wiping cache did not fix it, factory reset was needed.
Dear Odia, thank you very much for replying and giving me a clue.
So... it appears that there's nothing else to do, is there? Buhahhaa!!! I want to cry!!!! I haven't made a backup and resetting the phone will be really painful... I'm already starting to feel the pain in my ass!!!
By chance, do you happen to know if I will have to buy again the apps I have already bought from the market? I have always kept both "Backup personal data" and "Automatic restore" ticked in "Settings>Privacy"... Could this be of any help?
JuniorGG said:
Dear Odia, thank you very much for replying and giving me a clue.
So... it appears that there's nothing else to do, is there? Buhahhaa!!! I want to cry!!!! I haven't made a backup and resetting the phone will be really painful... I'm already starting to feel the pain in my ass!!!
By chance, do you happen to know if I will have to buy again the apps I have already bought from the market? I have always kept both "Backup personal data" and "Automatic restore" ticked in "Settings>Privacy"... Could this be of any help?
Click to expand...
Click to collapse
You can always make a backup now before the reset and you will not have to buy paid apps again.
Yes but how can I backup my phone if kies will loose the connection with the phone as soon as it tries to access its memory?
Oh wait a moment, Perhaps I could use Kies air? Deos it allow to backup the phone? 'cause I can't test it now in my office, there's no wifi here...
From what I can tell, its the amount of the power that is supplied to the USB port itself that is the issue. I have the same problem when I put my i9100 on certain computers. Same thing happens to my WD MyPassport. Certain computers it works fine, and some it will power it for a bit, but once the device starts to draw too much current, it just disconnects.
This is why I try to do all my modding and flashing on a laptop, since, for me, they seem to be the most reliable in keeping devices powered up properly.
This is certainly a good point, but in my particular case, USB connection used to work up until yesterday with all the PCs I have (2 laptops and a desktop PC), whereas since yesterday, it works with none (with and without using the same USB ports). In addition if I use straight USB connection (hence not through the MTP app used by kies), it works fine.
Anyway what you have just mentioned is actually what scares me, because it would mean a hardware fault. But I'm crossing my fingers, hopefully it's (just) a software related issue and a factory reset will solve it. After all, straight connection works, so it would be really surprising if it were a hardware fault.
I will try resetting everything when I get home. Another "nice" busy evening to account to Samsung!
I guess if all samsung customers were honestly paid for every hour spent mending/fixing the issues of samsung products, the company would declare bankrupt in a matter of a few days!
Ok, I solved the issue with a drastic factory reset.
Thanks Odia for helping.
I spent 8 hours backing up and restoring everything included all the settings and personalisations. I went to bed at 3 am, eating only a quick sandwich in front of the bloody phone.
THANK YOU SAMSUNG, I wish to electrocute all your ****ing managers.
I hate when something in a device screws up all of a sudden and noboby knows why. It could happen again any time, and again I would have to spend hours mending a stupid phone instead of enjoying my life.
By the way, does anybody knows exactly what data is automatically backed up and restored on google servers by these functions?
"Settings>Privacy>Backup of personal data"
"Settings>Privacy>Automatic restore"
I always had both tiched, and I noticed that almost all the applications downloaded from the market that were installed on the phone, were automatically re-downloaded and restored on the phone at first boot after reset, but I'm not too shure I have understood what else was automatically restored.
I just read this thread for the first time, and was sympathetic to your issue when I started reading. I could see that there had been problems, but suggestions had been made and you seemed to be making good progress.
I was getting ready for offering advice and wishing you well with your problem.
Then suddenly you start to wish physical harm on Samsung employees.
Bye.
JuniorGG said:
Yes but how can I backup my phone if kies will loose the connection with the phone as soon as it tries to access its memory?
Oh wait a moment, Perhaps I could use Kies air? Deos it allow to backup the phone? 'cause I can't test it now in my office, there's no wifi here...
Click to expand...
Click to collapse
This is a simple solution try it and it will work for you the next time you face it most of the time it is a hardware issue i have been facing the same issue and nothing helped neither the factory reset nor the *#7284# procedure.
Take a pointy object like a pin or a paper and then clean your usb slot of the phone properly cuz most of the times usb pin points gets connected with each other due to the atmosphere and metal reaction. After that it will work like a charm for you. Before commenting anything negative i would appreciate if those who are facing this issue for a long time try this and then comment
Had the same problem, solved it by upgrading the phone software.
Setting > About Phone > Software update.
No need to afraid losing files. Hope that helps.
i faced the same problem on the GalaxyS sometime back. i did factory reset too. I got the same problem again. but i remembered it working on my LG TV so i did not go for factory reset. I went for re-install of samsung's USB driver for Windows. now it is working fine.
I fully agree that Samsung needs to be more responsible and responsive in resolving the such problems without causing data losses.
[email protected] said:
i faced the same problem on the GalaxyS sometime back. i did factory reset too. I got the same problem again. but i remembered it working on my LG TV so i did not go for factory reset. I went for re-install of samsung's USB driver for Windows. now it is working fine.
I fully agree that Samsung needs to be more responsible and responsive in resolving the such problems without causing data losses.
Click to expand...
Click to collapse
You could have saved a lot of hassle by installing a custom Rom and Kernel. I hate MTP mode! Mass storage mode is much better, I never had any problems with that....
Workaround - Power Management
This may be fixed, for now. However, in the future, there is a small workaround that you can use so that you're not required to wipe your phone every time this happens.
Here's what I do:
Since the device's connection is severed after the use of a certain amount of power, we can control the power management of the port that the device is connected to.
On WinXP:
Enter "Control Panel" > "System"
Click on "Hardware"
Click on "Device Manager"
Find the "Universal Serial Bus Controllers" section
Click the "+" next to that, and find the "USB Root Hub" that the device is connected to.
Right-click on the Hub, then select "Properties"
Click on the "Power Management" tab
Then, UNcheck the box that says "Allow the computer to turn off this device to save power."
This will prevent the connection from resetting. It's a quick workaround that works pretty well for me.
However, I ought to note that the changes should be undone after you're done with syncing the device, ESPECIALLY if you're on a laptop. Otherwise, you could risk a lot of battery/power usage within a short time, even if there is no device connected to that port.
Good luck, I hope this helps.
Cheers!
-Robbie (Zecred)
Moderator please help others as this is a community problem
Archer said:
I just read this thread for the first time, and was sympathetic to your issue when I started reading. I could see that there had been problems, but suggestions had been made and you seemed to be making good progress.
I was getting ready for offering advice and wishing you well with your problem.
Then suddenly you start to wish physical harm on Samsung employees.
Bye.
Click to expand...
Click to collapse
Please don't bail out because of that comment, i have been having this issue for a month and AT&T almost sold me another phone telling me it was the USB PORT.
I changed my phone setup dialing *#7284# and changed the UART to : PDA from Modem and same for USB (to PDA) modes. This helped get connected as before it would not even recognize the phone (computer would not do so).
I was am not sure if it is not the battery or charging circuitry, as others also reported, but my charging circuit is working fine and my battery charges 100% and last all day as normal. I can connect to the USB port and see my phone for a short while but it will suddenly disconnect.
But same as before it suddenly disconnects and will reconnect cycling continuously. I also believe it is the charge circuit because when it is charging, i hear the phone constanlty beeping from turning the schreen on/off. Same as when it is plugged into the usb port on computer.
Am tempted to buy a battery, but is can run the phone on the USB port without a battery in the phone. Problem continues without a battery...disconnecting and connecting to the computer.
Zecred said:
This may be fixed, for now. However, in the future, there is a small workaround that you can use so that you're not required to wipe your phone every time this happens.
Here's what I do:
Since the device's connection is severed after the use of a certain amount of power, we can control the power management of the port that the device is connected to.
On WinXP:
Enter "Control Panel" > "System"
Click on "Hardware"
Click on "Device Manager"
Find the "Universal Serial Bus Controllers" section
Click the "+" next to that, and find the "USB Root Hub" that the device is connected to.
Right-click on the Hub, then select "Properties"
Click on the "Power Management" tab
Then, UNcheck the box that says "Allow the computer to turn off this device to save power."
This will prevent the connection from resetting. It's a quick workaround that works pretty well for me.
However, I ought to note that the changes should be undone after you're done with syncing the device, ESPECIALLY if you're on a laptop. Otherwise, you could risk a lot of battery/power usage within a short time, even if there is no device connected to that port.
Good luck, I hope this helps.
Cheers!
-Robbie (Zecred)
Click to expand...
Click to collapse
I was plagued with this same problem, until I tried the above fix, and it works brilliantly! No more disconnects, great stuff.
It's pretty old topic but maybe someone has same issue and doesn't want to loose data. I had similar problem (couldn't connect to device, also couldn't install/uninstall any stuff because of no-space-available error).
I managed to download all pictures/documents via adb - worked pretty well. A sample command to retrieve all camera pictures:
adb pull /mnt/sdcard/DCIM
Hello everyone! I scanned a few pages and search a bit but couldn't find my exact problem already listed;
When I plug in my USB cable to my laptop (Windows 7) the phone goes into 'installer mode' and sits there for about 10-15 seconds then switches to 'media device' mode. That's cool because I want it to be in media device mode normally, installer mode is useless. The problem is, if I open dev options and select USB Debugging mode, it only stays for 10-15 seconds then pops back into media device mode -- for the 10-15 seconds I can connect from my PC and start pushing my app over but then it fouls up when it comes out of dev mode.
My phone is rooted but I have very few apps on it yet, the only rooted app I have is a wifi tether app which I haven't used yet, and NoBloat which I used to disable some verizon crud. It will still flip out of usb debug mode even if I don't try to push any data to it... GRRR! I also have a problem where I can't sign into Samsung Account ("Samsung Account has stopped working")... but that's another story >=(
SonyUSA said:
Hello everyone! I scanned a few pages and search a bit but couldn't find my exact problem already listed;
When I plug in my USB cable to my laptop (Windows 7) the phone goes into 'installer mode' and sits there for about 10-15 seconds then switches to 'media device' mode. That's cool because I want it to be in media device mode normally, installer mode is useless. The problem is, if I open dev options and select USB Debugging mode, it only stays for 10-15 seconds then pops back into media device mode -- for the 10-15 seconds I can connect from my PC and start pushing my app over but then it fouls up when it comes out of dev mode.
My phone is rooted but I have very few apps on it yet, the only rooted app I have is a wifi tether app which I haven't used yet, and NoBloat which I used to disable some verizon crud. It will still flip out of usb debug mode even if I don't try to push any data to it... GRRR! I also have a problem where I can't sign into Samsung Account ("Samsung Account has stopped working")... but that's another story >=(
Click to expand...
Click to collapse
Sounds like your wonderful "Debloat" app uninstalled something you needed. That's why these apps are useless. One persons soultion isn't for everyone.
DarkMenace said:
Sounds like your wonderful "Debloat" app uninstalled something you needed. That's why these apps are useless. One persons soultion isn't for everyone.
Click to expand...
Click to collapse
As a matter of fact, I completely re enabled everything I had frozen before posting and it still doesn't work.could it be a flaw in the root process?
To be clear, I never "un-installed" anything with NoBloat, I only "Disabled" or froze some apps (mostly amazon and the verizon nfl center, nothing system-wise).
SonyUSA said:
As a matter of fact, I completely re enabled everything I had frozen before posting and it still doesn't work.could it be a flaw in the root process?
To be clear, I never "un-installed" anything with NoBloat, I only "Disabled" or froze some apps (mostly amazon and the verizon nfl center, nothing system-wise).
Click to expand...
Click to collapse
Well if you want to do a system restore send me a PM and I'll give you instructions to do so. I'll only be up for about another hour or so.
DarkMenace said:
Well if you want to do a system restore send me a PM and I'll give you instructions to do so. I'll only be up for about another hour or so.
Click to expand...
Click to collapse
For those waiting with bated breath, a full restore did not help the issue of it not staying in USB Debug mode. In fact, a total reflash of the stock ROM and kernel still had the exact same problem, which I re-created right after I performed the initial setup... so this bug exists in the normal stock ROM it seems...
SonyUSA said:
For those waiting with bated breath, a full restore did not help the issue of it not staying in USB Debug mode. In fact, a total reflash of the stock ROM and kernel still had the exact same problem, which I re-created right after I performed the initial setup... so this bug exists in the normal stock ROM it seems...
Click to expand...
Click to collapse
Your phone might be defective if it never worked from the day you got it. If that's the case you should go to Verizon.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Nah, I'm almost 100% it's just a software problem because if I uncheck Debug mode then check it again, I can use the phone in dev mode for like 15-20 seconds and everything works perfectly... I can push my APK to test and it works great, but after it flips back to media mode it just kind of dies...
Edit: Can you plug your phone into your PC and tell me what mode it starts in, then wait 20 seconds and see if it changes modes? My phone immediately goes into "Installer Mode" then 20 seconds later changes to Media Mode (MTP). Maybe it's a problem with the drivers I have installed causing the phone to flip out of dev mode...
SonyUSA said:
Nah, I'm almost 100% it's just a software problem because if I uncheck Debug mode then check it again, I can use the phone in dev mode for like 15-20 seconds and everything works perfectly... I can push my APK to test and it works great, but after it flips back to media mode it just kind of dies...
Click to expand...
Click to collapse
Might try contacting Verizonnthen n havimg them connect you to Samsung if they can't fix the issue.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
The chumps at Verizon don't know how to do anything besides make phone calls and Samsung support is always closed by the time I get home...
Figured it out! Went into device manager and updated the "CDC Serial" with the driver from the Kies application from Samsung website, that cleared it up!
SonyUSA said:
The chumps at Verizon don't know how to do anything besides make phone calls and Samsung support is always closed by the time I get home...
Figured it out! Went into device manager and updated the "CDC Serial" with the driver from the Kies application from Samsung website, that cleared it up!
Click to expand...
Click to collapse
Good now if you ever need to restore you'll be fine with the USB debugging.
Sent from my Rooted Verizon Samsung Galaxy S4 using xda premium
Hi guys, hoping for some SuperUser help...
Using the GPS Time application to try and get my Omate TrueSmart to update the time after the battery dies (I can't believe the device can't hold enough power to maintain its internal clock, that's a terrible design flaw in a watch, but anyway)
The problem is that the GPS Time app pops up the SuperUser dialogue asking me to give it permissions--but the dialogue is too big for the screen and there's no OK button visible! How do you handle this on the TrueSmart?
metaphor_ said:
Hi guys, hoping for some SuperUser help...
Using the GPS Time application to try and get my Omate TrueSmart to update the time after the battery dies (I can't believe the device can't hold enough power to maintain its internal clock, that's a terrible design flaw in a watch, but anyway)
The problem is that the GPS Time app pops up the SuperUser dialogue asking me to give it permissions--but the dialogue is too big for the screen and there's no OK button visible! How do you handle this on the TrueSmart?
Click to expand...
Click to collapse
I use xposed for apps that spill over the edges. Start here...then move to xda
repo.xposed.info/module/de.robv.android.xposed.mods.appsettings
Sent from my HTC One using Tapatalk
Set Device Settings -> Display -> Font Size to Small and the SuperSU screen will fit on screen
fg said:
Set Device Settings -> Display -> Font Size to Small and the SuperSU screen will fit on screen
Click to expand...
Click to collapse
Thanks to both of you!
Open SuperSU and look on the first tab 'Application', Touch the #
Change 'Acces' to Allow
then save
False move on SU, now TS won't complete booting
I have a TrueSmart 1/8, US version, developers edition, with most up to date rom and with Loki's patch.
I wish I had read this thread a few minutes sooner. I was trying to install the gestures app GMD gestures I think it was and kept running into the same superuser problem. So went into settings for superuser and hit yes to have it installed I think in the system. I can't really tell you now because I can't get back into the watch at all.. I know it said to reboot immediately after and that if SU did not show up to go to the Google play store to reinstall or to open it from there or something...I'm not sure what. In any event, after SU did its thing, I powered off and on powering back on, it will not get past the Omate TrueSmart screen. Nor can I turn it off. Can anybody help me? For now I have it in the cradle so it doesn't lose power, since I cannot turn it off.
I know I can take the battery out, but I wanted to consult before I do anything more.
Tom19146 said:
... I powered off and on powering back on, it will not get past the Omate TrueSmart screen. Nor can I turn it off. Can anybody help me? For now I have it in the cradle so it doesn't lose power, since I cannot turn it off.
I know I can take the battery out, but I wanted to consult before I do anything more.
Click to expand...
Click to collapse
If you had ADB enabled, try plugging into your computer and see if you can launch an adb shell which will give you more restoration options. You may be able to undo your changes from the command line, or at the least reboot into recovery mode.
Without ADB, your options are to pull the battery or wait till it drains naturally.
fg said:
If you had ADB enabled, try plugging into your computer and see if you can launch an adb shell which will give you more restoration options. You may be able to undo your changes from the command line, or at the least reboot into recovery mode.
Without ADB, your options are to pull the battery or wait till it drains naturally.
Click to expand...
Click to collapse
What program should I have open on my PC before connecting watch (or is that a sensible question)?
New patch coming out this weekend to address that.
Tom19146 said:
What program should I have open on my PC before connecting watch (or is that a sensible question)?
Click to expand...
Click to collapse
Just a follow-up to the above, in case anyone lands in the same place, I did take the back off, remove the battery for just a moment, and then put the back back on. (I doubted, since it was frozen, that connecting to my PC would help, so i didn't try that. ) To my delight, everything was as I had left it, save that the gestures GMD app now loaded. (I made my font small, as recommended above, and was able to ok super user this time.) I had expected after removing the battery, to have to rebuild/reload everything from scratch,but that didn't happen.
Thanks to all for your help.
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
horgenblorg said:
I have a Windows 10 PC and a Kindle Fire HDX 8.9 that I purchased about 2 years ago. Up until the past few days I was a very basic user. Just spotify, web browsing and some games. The most advanced things I did on it were install some apk files from the internet and make it so the screen was always on in the secret developer options menu. Up until Monday I had no intentions of rooting my tablet or doing any high level tech wizardry with it.
But the past few weeks I have been noticing significant performance decreases in my kindle. Apps crashing, screen freezing, slow performance. I didn't think much of it, I figured I just had too many terrible games on it. On Friday morning it crashed while I was using it and attempted to boot back up but with the [fastboot] text under the word amazon. It got stuck on this screen, restarting it just brought it back to this, attempting to hold the power button and the volume up button didn't appear to do anything either. Eventually after restarting it about 20 times it booted normal for whatever reason. After this it worked normal for another day and then it crashed again and booted with the [fastboot] text. I read up more on fastboot and various kindle fire issues and jammed restarts until it randomly worked again.
This time I when it was working I tried restoring it to factory default in case something I had done or added was the cause of these boot loops or whatever. I also went into developer options and turned on usb debugging since my reading made it seem like that was pretty necessary.
It crashed and restarted again Monday morning but it didn't get stuck in fastboot this time, it just got stuck on the word amazon. So I installed the various tools and drivers I have read about on here and I have been doing my best to try and make it work again. But as someone with zero experience with this sort of thing I have hit a wall.
When I first hooked it up last night I set the driver to the "adb interface driver", I got adb to see the device and I was able to execute some commands to it. I made it reboot just to see if I could, it still stopped at the word amazon, and then I went to sleep. Today I turned on my computer and adb will not find the device. Apparently something changed overnight and windows will now only see the device as a standard mtp usb device. I have attempted to force it to change with the "update drivers -> browse my computer -> let me pick from a list -> Have disk " line. But when I choose the kindle drivers or the adb drivers it tells me they are incompatible. Unplugging and plugging back in doesn't do anything. Restarting doesn't do anything. Attempting to uninstall the drivers doesn't do anything. I don't know what is left or how to fix this so I can proceed. And honestly even after I get through this road block I have no idea what I should do to try and make my tablet operational again. So I am in need of some guidance. Is there anyone out there that can show me the way or at least get adb to see my device again?
Click to expand...
Click to collapse
The symptoms you describe suggest a hardware vs software problem. Guessing bad memory (or controller) given the random boot behavior. Unfortunately, there is little you can do to rectify the problem, even if software based, on an unrooted 4th gen HDX. ADB will not allow privileged access unless the device rooted.
Look on eBay for another motherboard. Might also want to grab a daughterboard as well.
Watch some teardown videos on YouTube. Everything applies to the 4th gen as it does from the 3rd gen as far as taking it apart.
In total you can fix it for around $65. That's with buying both boards which you possibly only need the motherboard.
Sent from my KFSAWI using Tapatalk