Hey all, I think i screwed myself on this one.
So i just got my kindle 6.2.1. After working through the root tuts, i would update my kindle driver and i would get an error. Along the lines of the driver is not recognized on windows x64. so it would not let me update my kindle driver for root.
However after furthering myself to fix the solution.
my kindle all together will not connect to my pc. It will go into usb mode, then loops between the connecting circle and disconnect. My computer only recognizes it as "J" drive and not as kindle altogether.
Im stumped.
So after reading and trying how others on here fixed that very same problem I deiced its time to make a post and ask for help because those other methods did not work.
Ok I did something stupid and I went ahead and did a factory reset to my kindle. Yes I know it was a complete noob thing to do and I should have known better seeing that I have rooted and flashed ROMs on all my other android devices and never once did something that dumb but I did it this time. Now I do have a back up made and had it safely stored on my PC.
Problem is that I can't get into recovery it stuck on the FFF logo and holding down the button only brings it back up. When the device restarts windows recognizes it as an unknown usb device and won't connect and Adb also wont recognize the device or show that it is connected. So now I need to ask someone who is more knowledgeable then me on what to do next. Any help will be appreciated
Ok update: Was able to solve my own problem using the Kindle fire utility and by uninstalling the drive for the kindle through the device manager, then using the drive install_drivers.bat in the KFU folder to reinstall the drivers. I next unplugged my kindle from the pc, turned it off by holding the button on the kindle in and then restarted it with the usb plugged into the pc. My Pc recognized my kindle and I was then able to use KFUs Bootmode menu and once in there used option 1. to boot it in normal mode. Hope this helps anyone who was stuck like I was. My memory of which adb commands to use was a bit rusty but using the KFU helped with that part.
I have flashed Kindle Fire with CM9(version 2/9) . It was running great first day. But the next day, it could not connect to WiFi(Mecurcy wireless router, WPA/WPA2), just frequently tried to connect but be refused. But it was OK on the first day after I flashed CM9.
When I tried to login the router from PC to set the wireless channel, the router refused the login name/password(it is admin/admin, used to be OK). It is so funny and confused.
About the sdcard problem: I plugged Kindle Fire usb cable into PC as usb driver. After i plugged out the cable, Kindle Fire cannot recognize the sdcard. I have to restart the machine. Is there any solution for finding sdcard without restart?
There is another little problem. It cannot recognize the file name with international language but show ??? instead. How to fix it?
I am very appreciate for your help. Thanks.
Hemmed go into TWRP and make sure that SDcard is mounted... Or you could try factory reset.
When I plug my nook into my laptop it 'briefly' enters USB mode, and then drops it and the drives. It then tries to go back into USB mode, and basically does this repeatedly until it gives up The nook is basically unusable during this and keeps flashing with the usb mode and normal home screen. After this happens, both the Nook internal storage and SD card are greyed out in settings, reading "unavailable", and the SD card cannot be accessed and is not detected in any way. What gives?
Is this a windows problem, a nook software problem, or a hardware problem? I'm not sure if this happened before I rooted, since I basically just took a backup and rooted as soon as I had it out of the christmas wrapping.
jun127 said:
When I plug my nook into my laptop, the it goes into USB mode, and then drops it, and then tries to go back into USB mode, and basically does this repeatedly until it gives up. After this happens, both the Nook internal storage and SD card are greyed out in settings, and the SD card cannot be accessed and is not detected in any way. What gives? Is this a windows problem, a nook software problem, or a hardware problem? I'm not sure if this happened before I rooted, since I basically just took a backup and rooted as soon as I had it out of the christmas wrapping.
Click to expand...
Click to collapse
Can you please try to connect it to the pc without the sd-card inserted?
Have you tried reloading the original firmware?
J_Palito said:
Can you please try to connect it to the pc without the sd-card inserted?
Have you tried reloading the original firmware?
Click to expand...
Click to collapse
The same thing happens when connecting without the SD card. I haven't tried reloading the original firmware yet but I first really noticed it happening after I did a full backup with NookManager on 1.0.1. That was when I could not get it to stay in usb mode long enough to copy the 1.1 update zip into the directory. The only way I was able to get it in was I 'tried' doing the 6 hard resets where I tried holding down shut down 6 times in a row (but nothing special happened so I thought nothing happened). And then I restarted windows and it seemed to work, for a while anyway, until I rooted. I wonder if that had to do with restarting windows or restarting the nook a couple dozen times. lol
The changes I've made so far to my nook ST:
1.0.1 backup with noogy
1.0.1 backup with nookmanager
1.1 manually update
1.1 root with touchnooter
I rooted 3 times in a row because the first time none of the apps worked
multi touch kernal with CWM
then I switched to
OC kernel with fast mode
lots of software additions and tweaks like legacy launcher, wallpaper changer, ES file explorer, adb wifi
Static IMEI mod
Whatsapp verification/install
So besides the USB problem it's kicking ass at this point . I really hope I don't have to restore to original firmware or return it for hard ware problems. So I can confirm this is not a usual occurrence? Let me test it on some other computers to see if it's my laptop...
UPDATE: I started windows in safe mode and it had no problems whatsoever connecting to the nook as it should, and the nook didn't go nuclear either. So I suspect it's some drivers or software relating to virtual disks that is conflicting with the nook, or something else enigmatic. What a pain..
Thought it was worth mentioning. Yesterday I had a bit of scare having flashed system, data and SD card in my Kindle and not able to adb to it. Thought I had a fairly solid brick. Had drivers reinstalled and tweaked and PC rebooted to no avail. Turned out, the problem was with my USB hub. connected Kindle directly to the PC the adb went online just fine.