Related
first of all thanks for the excellent rom.since im just trying out this new rom,im intending to change my rom back to modaco gr8 after trying out for some time.
But here's the trouble here.i always can't seem to access twrp through my kf.Each time what i did was i connect my device with USB to the pc and use kfu to reflash twrp to gain access.
But now with this gederom,my pc can't seems to detect my kf and it keeps saying driver is needed.
So what can i do now to once again gain access to twrp??
please please help me im really panic now.
chaukeng said:
first of all thanks for the excellent rom.since im just trying out this new rom,im intending to change my rom back to modaco gr8 after trying out for some time.
But here's the trouble here.i always can't seem to access twrp through my kf.Each time what i did was i connect my device with USB to the pc and use kfu to reflash twrp to gain access.
But now with this gederom,my pc can't seems to detect my kf and it keeps saying driver is needed.
So what can i do now to once again gain access to twrp??
please please help me im really panic now.
Click to expand...
Click to collapse
I had to read this post a couple of times just to make sure I'm not going crazy. So you have been using the KFU to REFLASH recovery every time you want access to it?!
I'm not going to be nice and not say what I really want to say. But do yourself (and everyone here) a huge favor and thouroghly read this thread...
http://forum.xda-developers.com/showthread.php?p=23747567
...before you do anything else on your Kindle and potentially do damage to your device. HINT: the problem isn't the rom
[Edit:] When you're done reading the above posted thread, read this one for good measure:
http://forum.xda-developers.com/showthread.php?p=19837228
Sent from my Amazon Kindle Fire using xda premium
the link is broken.any way to read that?
i Doesn't know what im doing is wrong since no one replies to me in my local forum.
and also i flashed modaco gr8,uses it for around 1 month and its been working great.
But now i realise my mistakes now and any way to change this?
just want to reflash this to my modaco.thanks!
XDA Won't let me copy the full link for some reason.. Go to the General forum under stickies and select Kindle Fire for Beginners.
[Edit:] fixed try again
Sent from my Amazon Kindle Fire using xda premium
sorry first one still can't open.
I know once i reboot my kf i have to either long press or press twice to get my switch into orange colour to get into recovery mode.
But since mine is not the fire triangle anymore (its an android doll on top of the 'kindle fire' logo.i doesn't know why mine is this version but i've read alot with this also ). i couldn't access recovery through the aforementioned method anymore.i tried to ask many people even natmile on facebook and i've got no confirmation from them until now.
i did do some readings including the one for the beginners and i do search for my problem on why i can't access to my recovery.But i just can't find an answer.really need your help.
chaukeng said:
sorry first one still can't open.
I know once i reboot my kf i have to either long press or press twice to get my switch into orange colour to get into recovery mode.
But since mine is not the fire triangle anymore (its an android doll on top of the 'kindle fire' logo.i doesn't know why mine is this version but i've read alot with this also ). i couldn't access recovery through the aforementioned method anymore.i tried to ask many people even natmile on facebook and i've got no confirmation from them until now.
i did do some readings including the one for the beginners and i do search for my problem on why i can't access to my recovery.But i just can't find an answer.really need your help.
Click to expand...
Click to collapse
The "yellow triangle" logo is the FireFireFire bootloader (version 1.2). The "kindle fire" logo with android is also the FireFireFire bootloader (version 1.3). Recovery selection for both versions is the same, only the time span given for you to make the selection has been reduced in v1.3. My guess is that you are not pressing the power button at the right time to make the selection.
This is the thread for FFF v1.3...
http://forum.xda-developers.com/showthread.php?t=1541043
In the first post, it gives you directions on how to make the recovery selection...
Recovery Selection - As the Kindle Fire boots up, the power button LED will change from bright green to a dim green. Once it changes to a dim green, press the power button again and release (repeat a few times to be sure). The LED will then change to an orange color indicating recovery selection and boot into recovery.
Personally, I keep my fingernail on the button and as soon as the reflection goes dim, I press/release several times. If you want to be absolutely sure, keep pressing/releasing until the LED goes orange. This always works for me without fail. If the LED goes orange and it doesn't get to recovery, something is wrong with your recovery.
As far as gedeROM goes, look in the notification area and make sure it says "Android debugging enabled" when you have it hooked up to your computer. If you still can't send it adb commands, then it's likely a device driver issue. Read the second post of the first link soupmagnet gave you.
chaukeng said:
But since mine is not the fire triangle anymore (its an android doll on top of the 'kindle fire' logo.i doesn't know why mine is this version but i've read alot with this also ). i couldn't access recovery through the aforementioned method anymore.
Click to expand...
Click to collapse
That is a very important piece of information that would have been useful from the beginning. There is no reason for the new version of FireFireFire (Kindle fire logo w/android) to work any differently from the old one (yellow triangle) in regards to entering recovery.
Try reinstalling FireFireFire to see if that fixes the problem.
Sent from my Amazon Kindle Fire using xda premium
sorry...i was too nervous and missed this...thanks for both of your help.i will try the above method and see whether it works.
and i can't reinstall firefirefire since my pc won't detect my kindle fire.and it now detects it as p1000 (samsung galaxy tab).
chaukeng said:
sorry...i was too nervous and missed this...thanks for both of your help.i will try the above method and see whether it works.
and i can't reinstall firefirefire since my pc won't detect my kindle fire.and it now detects it as p1000 (samsung galaxy tab).
Click to expand...
Click to collapse
Try fastboot mode in KFU. Option 1, when it show <waiting for device> then connect the KF, hold down the power button untill it shut down, and hold button again to turn it on.
If you can somehow get to fastboot, try flash TWRP again.
Sine you can get in to FFF, I strongly believe that it's still alive.
Gửi từ Kindle Lửa của tôi qua Tapatalk 2
reinstall drivers
chaukeng said:
sorry...i was too nervous and missed this...thanks for both of your help.i will try the above method and see whether it works.
and i can't reinstall firefirefire since my pc won't detect my kindle fire.and it now detects it as p1000 (samsung galaxy tab).
Click to expand...
Click to collapse
I think you need to go in to device manager and uninstall the drivers and reinstall the drivers . Try it out
i tried using kfu and use fastboot.but can't detect.
since gedeROM design to change our kf into galaxy tab,can i manually change and allows the pc to detect my kf as a kindle fire?Then probably i would have access to kfu.
btw i tried pressing the button but still couldn't access twrp through device.
You're in a pretty tricky spot. Apparently, the way GedeROM was set up, it is causing problems with adb connecting. But it all boils down to a driver issue. You need to somehow get into twrp to flash a different rom and see if it is the rom causing your original problem. But without access to recovery or USB debugging, I can't think of anything that will help you.
Try uninstalling and reinstalling your device drivers until you can get a connection long enough to change your bootmode to 5001 in order to get back into recovery.
You need to be able to get a solid connection with adb and fastboot to further troubleshoot your problem and it looks like you can't do that with the rom you're using.
Sent from my Amazon Kindle Fire using xda premium
I have the same problem, loaded GedeROM got in fatboot, and now I am stuck.
okay.somehow i've managed to get USB mass storage working.But KFU still shows offline.
But then i found out if i ask the kfu to help me boot to recovery it may still works.But can i do this and get to recovery and flash back my modaco?
Or should i manually flash my twrp again?
Flash MoDaCo to see if that helps. If not, reflash twrp. If not still, reflash firefirefire.
very nervous...i flash twrp again and i get to boot into recovery.omg....now im restoring into my modaco backup...hope it works.
Btw my kfu status is now 'online'
thanks so much soupmagnet!
But what if my kf still can't access twrp,should i do everything from the start manually?
power butoon
chaukeng said:
first of all thanks for the excellent rom.since im just trying out this new rom,im intending to change my rom back to modaco gr8 after trying out for some time.
But here's the trouble here.i always can't seem to access twrp through my kf.Each time what i did was i connect my device with USB to the pc and use kfu to reflash twrp to gain access.
But now with this gederom,my pc can't seems to detect my kf and it keeps saying driver is needed.
So what can i do now to once again gain access to twrp??
please please help me im really panic now.
Click to expand...
Click to collapse
start by powering your of, no need to connect anything ( USB) just make sure the from is in your of SD card wait for the yellow triangle any press several times with 3 sec intervals, until twrp shows up...hope this helps you...
ADB Not Working After GedeROM
I've been using the 28-04-2012 GedeROM all weekend, and it works fine, but I still haven't been able to get ADB working. I checked Android Debugging under Developer Options. On my PC, the KF only shows up in my Device Manager as a Disk Drive with the designation "Am", not as an ADB device, and the ADB Devices command doesn't show any devices attached. My computer thinks its an empty disk drive (no data). I have a regular Windows x86 PC. I try and try but I can't re-install any other driver to get the PC to recognize it.
Funny thing-- I tried recovering my stock system and data from TWRP (after factory wiping GedeROM), and it didn't work, I just get a dim lit screen on reboot. GedeROM re-installed ok, so I'm not too upset, just wondering why I can't go back.
I searched around on the lists but didn't see any idea that worked. Any suggestions would be greatly appreciated.
Thanks- Roger
Roger Dives said:
I've been using the 28-04-2012 GedeROM all weekend, and it works fine, but I still haven't been able to get ADB working. I checked Android Debugging under Developer Options. On my PC, the KF only shows up in my Device Manager as a Disk Drive with the designation "Am", not as an ADB device, and the ADB Devices command doesn't show any devices attached. My computer thinks its an empty disk drive (no data). I have a regular Windows x86 PC. I try and try but I can't re-install any other driver to get the PC to recognize it.
Funny thing-- I tried recovering my stock system and data from TWRP (after factory wiping GedeROM), and it didn't work, I just get a dim lit screen on reboot. GedeROM re-installed ok, so I'm not too upset, just wondering why I can't go back.
I searched around on the lists but didn't see any idea that worked. Any suggestions would be greatly appreciated.
Thanks- Roger
Click to expand...
Click to collapse
You need to reinstall the drivers. Long explanation at this link...
http://forum.xda-developers.com/showthread.php?t=1625356
ADB on GedeROM
Thanks for the advice Kinfauns, I'll read your article and try to reinstall the drivers again tonight. I did try over the weekend, checked the drivers, made sure they didn't change somehow, but the system wouldn't accept the drivers-- either "not better than what is already installed", or "can't find any drivers". My PC seems to recognize the KF as a disk drive, not as an ADB or Android device, so it's like the PC isn't even looking for my driver to be a suitable driver for the "Am" disk drive.
Thanks for your help!
Roger
I initially bricked my kindle with the KFU somehow so the static logo showed, but that was a relatively quick fix. I then got clockworkmod working, and flashed a ROM. Now it will show the standard kindle bootloader for a second, then the screen will flash white, and then I get a blank screen. ADB works, but neither KFU nor the Fire Unbrick Utility will recognize it, I just get waiting for device. This has left me really scratching my head. Any advice would be greatly appreciated.
Typically, this is caused by a bad download (failure to check MD5) or not " wiping" correctly. In your case, I'm willing to bet Clockwork is the culprit. Use fastboot to manually install TWRP to see if that fixes the problem, or try a different rom. Personally, and based on what I've seen in the recent past, I think Clockwork is not a safe bet in regards to custom recovery at the moment.
soupmagnet said:
Typically, this is caused by a bad download (failure to check MD5) or not " wiping" correctly. In your case, I'm willing to bet Clockwork is the culprit. Use fastboot to manually install TWRP to see if that fixes the problem, or try a different rom. Personally, and based on what I've seen in the recent past, I think Clockwork is not a safe bet in regards to custom recovery at the moment.
Click to expand...
Click to collapse
Thank you for replying. The problem is I can't get it into fastboot. When I turn on the KFU, it states that ADB is online but boot status is unknown. I can force it to reboot but I can't get it to fastboot. Whenever I try to install anything or repair it with the Kindle Fire Unbrick Utility, I either get waiting for device forever or exec '/system/bin/sh' failed. The default kindle bootloader is still installed, I think, and I can't get into clockworkmod at all.
daimyo777 said:
Thank you for replying. The problem is I can't get it into fastboot. When I turn on the KFU, it states that ADB is online but boot status is unknown. I can force it to reboot but I can't get it to fastboot. Whenever I try to install anything or repair it with the Kindle Fire Unbrick Utility, I either get waiting for device forever or exec '/system/bin/sh' failed. The default kindle bootloader is still installed, I think, and I can't get into clockworkmod at all.
Click to expand...
Click to collapse
See, this is why it's important to be extremely detailed with the issues you are experiencing, including all error messages.
Code:
exec '/system/bin/sh' failed
That indicates your shell has been damaged or corrupted. The only fix for this so far, is with a factory cable. Get a factory cable to put your device in fastboot.
heres where to find a cable http://forum.xda-developers.com/showthread.php?t=1392693
Thepooch said:
heres where to find a cable http://forum.xda-developers.com/showthread.php?t=1392693
Click to expand...
Click to collapse
Thank you. I just bought one. Just one question, when it arrives, how do I use it? Do I just use the KFU to install Firefirefire? Or do I have to use firekit? And do I just plug in the cable once to force fastboot then use a normal cable to flash a new recovery and bootloader? Sorry, I'm kind of new at this.
By plugging the cable into your usb port first, then to your device that has been powered off, the device will power on automatically into fastboot. After that it can be used to send commands and transfer data as a normal cable. Using it in a way other than I described will not enable fastboot automatically.
So, I tried searching for days on how to fix my problem.
A little while ago I rooted my Kindle Fire, and it was great. Then I did something. Not sure exactly what. But It ended up just doing nothing. When I boot up the Kindle it shows the blue and white Kindle Fire logo. Nothing else past that (unless I go to recovery.) Now, my computer doesnt recognize it anymore, even after doing most of the driver updates that people on here have said to do.
I need help, basically, getting it back to normal, so I can give rooting a try again. Now that I know what exactly I am dealing with, I can do this and not screw everything up.
First, the computer says the driver is installed, yet it doesnt recognize it.
Second, (before the driver mishap) KFU said it was connected but the adb was unknown.
Third, I have CWM and I tried to flash the normal Amazon update to bring it back, and it says"it cant open it (bad)".
Now, I would really like some help with this. I'm just at a complete lost.
Now should I put that into command prompt in the adb part? because it just says fastboot is not recognized.
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Now its just not connecting to the computer. I installed Android sdk and everything and its just not working. It says the driver is installed but there was an error because a problem had occurred. Any help? :crying:
As soon as you get tired messing with drivers you can move on to something that works http://forum.xda-developers.com/showthread.php?t=1850038
ManofFishFry said:
Yes, It wont do that, it just says error: device not found. also says 'fastboot' is not recognized.
Click to expand...
Click to collapse
I hope u r on windows PC..
first after u set up adb, make sure u install adb drivers that came with kindle fire utility with ur kindle fire unplugged..if u had plugged in kindle fire while doing that, go to device manager and uninstall that device and its driver software and start up from beginning..
keep kf unplugged and install driver..u dont get usb debugging option in stock kf rom..its enabled if u have installed the drivers properly..ur kindle fire appears as android phone in device manager if everything u hav done is correct..
then boot up ur kf..that blue and white kf logo is of firefirefire bootloader..i hope its v1.4a and u see it on right top of the screen..if its stuck there then open command prompt as administrator on ur pc..connect ur kf to pc..type in to cmd
Code:
fastboot devices
if u see something under list of devices attached that will be ur kindle fire(unless some other android device is connected in fastboot mode lol)
Because kindle fire, as far as i know, can only boot into 3 bootmodes(normal, recovery, fastboot) unless u have altered the partition table to install different roms and multiboot ur kindle fire..
if fastboot command is not recognized, try setting the path to where fastboot.exe is present in KFU folder
alternatively u can go to folder where fastboot.exe is located and right click while holding shift and selecting 'open command window here' and fastboot needs to firefirefire bootloader to be installed on ur kindle fire..
also u can try this..
JUST GO TO RECOVERY..twrp has always been a better recovery software than cwm based thing available for kindle fire at least for me..if u go to recovery, ur kf will definitely show up as an adb device..u can change the bootmode using this..just type in:
Code:
adb devices
if ur kf is seen as in recovery then type this in cmd
Code:
idme bootmode 4000
reboot
just report if this worked..
okay well, I deleted all the drivers and started from the beginning. Yet, after running the install_driver.bat I plugged my Kindle in and it still says device not recognized. Now, you how can get adb working? It is coming up as unknown device. Its just seeming like theres something wrong on the kindle part. But hey, what do I know. haha
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
But doesn't that require linux? I have windows 7. Is there something like that for windows?
Thepooch said:
lol try what will work http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
This is what I get when I try to install the driver....
To run soupkit all you need is at least a 2 gig usb flash drive ubuntu 12.04 32 bit and universal usb creator. By the way your problem with the driver is you (or how you`re going about it), You would trip if I got on your computer and got it to work or could at least tell you why its not working. that`s why I suggested soupkit if you would of actually read the information I gave you, I wouldn`t have had to tell you twice and you would know that to use it it`s not required to be installed on your computer. But hey catch me online I can either help you fight through windows crappy drivers or help you set up soupkit I`m always game for a challenge When updating the driver you need to point it to the 32 bit version of the driver for instance on my computer it`s located here C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers. After it`s ran unplug and replug device if that doesn`t work power off and power on while connected this generally does the trick when windows finally catches on it will install android adb interface, this is the fastboot driver (if you`re stuck in fastboot). Then select option 1 in KFU for changing bootmodes, then option 1 for normal if it does nothing power off and power on while connected it should then detect the kindle and reset the bootmode to normal. Pm me later I will be online all evening and most every evening I will help you sort it out.
Josepho1997 said:
Whoops! Somehow my post was posted twice. I didn't even get to see your reply. Sorry!
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
this is what I get when I try this... (btw im working with firefirefire. its got the blue and white kindle fire.)
Why don't you let me take a look?
Dark__king said:
Hi i have the same problem but the only thing is that my device is actually verified by the coputer and can connect via usb mount but when i try to install a ROM it says unable to mount and cannot install rom but i see there is something for fixing mounting problems there in soupkit so i'll give it a try.
Click to expand...
Click to collapse
Yes soupkit can fix mounting problems.
This is a very interesting issue with this Kindle windows detects it as unknown usb device, drivers are installed properly from what I can see. Ubuntu with soupkit ran on it fails to detect it in recovery or fastboot. multiple cables tried, lsusb doesn`t show the device connected. I really think this one the computer is the problem, because it`s the only unchanged variable.
Firekit may be the only option if Linux won't detect the device. Before doing that, make sure a USB 3.0 port isn't being used and try a fresh install of Linux to be safe. Otherwise, it seems putting it in USBboot is the only option for getting Linux to detect.
I'm not exactly sure what causes the unknown device error, but it almost always means there is something wrong with the bootloader, and it seems as though Windows might be the main culprit. Not sure why exactly, but it may be similar to the problem soulweeper51 had. Possibly a hardware issue involving the computer's USB port or the motherboard itself.
@ManoFishFry has doomlords cwm recovery and he flashed JB at first I thought it was an issue with cwm not being detected but the fact that it`s not detected in fastboot raised my eyebrows. The bootloader appears to be functional but I cannot rule out any minor state of being broken in another fashion when lsusb returns null. The computer doing the work had never been used prior to the incident so driver install didn`t take place till after the fact. The usb ports are all either 1.0 or 2.0 no 3.0 ports are being used. An alternate computer would be nice to rule out the computer itself @ManoFishFry only has a dinosour of an xp machine as alternate use of is not possible yet, not that it would even be possible to install drivers because of the typical unsigned driver failure of xp and booting ubuntu isn`t happening at the moment on this machine.
I'm willing to bet it is the bootloader.
Just USBboot and get it over with.
We did try usb boot once but it didn`t work will keep trying.
I apologize ahead but I have not been able to find a thread that addresses my problem.
Kindle Fire (1st gen)
Rooted with KFU, installed FFF, TWRP, Go Launcher and Gaaps. Worked perfectly.
Attempted to flash hashcode's JB ROM with Goo manager and made a mistake.
Attempted to boot to system and all that will show is the Rolling Triangles splash screen
continuously.
I can boot to TWRP.. I want to start over and flash the Amazon update 6.3.1 but my
Windows 7 PC cannot connect to the Kindle over usb. Fastboot seems to connect
(returns "Kindle" on fastboot getvar product) ADB does not show any devices attached.
I have deleted and reinstalled drivers - Windows does not recognize the Kindle.
Will a factory cable allow my PC to recognize my stuck Kindle?
Which version of twrp are you using?
Sent from my Amazon Kindle Fire using xda app-developers app
A factory cable will only put your device in fastboot. If you plug the kindle in while in recovery it should install the correct drivers. Try connecting to your computer and selecting mount and hit the big button to access your sdcard contents, where you can transfer a new rom zip to it. I wouldn`t attempt to flash stock unless you research prior many brick their devices and then a factory cable is needed. Did you wipe before flashing? If so how and what?
Also, do you have FireFireFire installed?
Thank you for your replies!
I have FFF installed
TWRP is 2.3
I did do a cache wipe and factory reset within TWRP
I did see this morning manofFishfry posting "[Q] I need help bad"
and it seems he was having a nearly identical problem with USB
connection.
I will attempt thepooch's recommendation:
http://forum.xda-developers.com/show....php?t=1850038
I will post any progress I make.
Many thanks
M
TWRP 2.3 is your issue if you do get ubuntu setup with Soupkit simply replace 2.3 with 2.2.2.1 and rewipe and reflash another rom.
Thepooch said:
TWRP 2.3 is your issue if you do get ubuntu setup with Soupkit simply replace 2.3 with 2.2.2.1 and rewipe and reflash another rom.
Click to expand...
Click to collapse
Looks like I'm still stuck then - I've only got Win7 on my PC - unbuntu is WAY out of my league.
I'll try Zombiepiratez unbrick utility
M
It`s not that far out of your league. Use universal usb creator to make a live usb with persistent run soupkit on it reboot the usb Your in like flin If you want help I can help you at some point to get this done.
Thepooch said:
It`s not that far out of your league. Use universal usb creator to make a live usb with persistent run soupkit on it reboot the usb Your in like flin If you want help I can help you at some point to get this done.
Click to expand...
Click to collapse
I removed the Kindle drivers from my Laptop PC and then connected my son's unrooted stock KF1. It was recognized, the drivers loaded, and I loaded the KFU drivers and updated them no problem. I ran KFU and got 4000 on the code.
I then plugged in my "stuck in TWRP/FFF/JB Splash Screen" rooted KF1 and the PC sees it as a removable memory device. It prompts me to load it with media when I double click on it. KFU can't find it. ADB can't find it. Fastboot can get "Kindle" from getvar product, but nothing else.
What can I do next?
Thanks!
Update
Micah461 said:
I removed the Kindle drivers from my Laptop PC and then connected my son's unrooted stock KF1. It was recognized, the drivers loaded, and I loaded the KFU drivers and updated them no problem. I ran KFU and got 4000 on the code.
I then plugged in my "stuck in TWRP/FFF/JB Splash Screen" rooted KF1 and the PC sees it as a removable memory device. It prompts me to load it with media when I double click on it. KFU can't find it. ADB can't find it. Fastboot can get "Kindle" from getvar product, but nothing else.
What can I do next?
Thanks!
Click to expand...
Click to collapse
One new thing: I mounted the SD card using TWRP, then my Win 7 Laptop could connect to my Kindle via usb as an external drive. Win 7
then siad the drive needed reformatting. KFU still would not connect.
would the soupkit help in this situation? I had the same problem but figured out the whole mounting from TWRP and it worked for me
Micah461 said:
One new thing: I mounted the SD card using TWRP, then my Win 7 Laptop could connect to my Kindle via usb as an external drive. Win 7
then siad the drive needed reformatting. KFU still would not connect.
Click to expand...
Click to collapse
Your sdcard issue and ADB issue are two completely unrelated things. The ADB issue is due to the way Windows handles drivers. Fix the driver problem or use SoupKit/Linux.
The sdcard issue is due to your sdcard losing its formatting somehow. You'll have to reformat (quick format, block size 4096) in order to use it again. You will lose all data on the sdcard BTW.
"That's a special kind of stupid. The kind that makes me laugh"
Huzzah! Success in spite of myself!
Many thanks to each of the experts that each gave me nuggets of info that eventually
unbricked my KF1.
I last posted that Win 7 would see my Kindle when I used TWRP to mount the SD card.
It prompted for me to "format the device" and feeling I had nothing to lose - selected
default settings and quick format.
This then opened a File Manager window giving me access to the SDcard folder on the KF1.
I had downloaded the Stock update from Amazon update-kindle-6.3.1_D01E_4107720.bin
On another thread - Soupmagnet had said to rename this BIN file to a ZIP - which I did.
I shortened the file name to update-kindle-6.3.1.zip.
I de-mounted the SDcard folder in TWRP.
I wiped the Dalvic and did a factory reset.
I navigated to the Install screen and it found the update file and installed it.
UNBRICKED!
Thanks again for the tireless help you guys give.
Micah461
I have a kindle fire which wasn't doesn't connect to the computer. I get an error message such as "USB device not recognized". I had rooted the kindle fire and I thought that this problem could have been because of the rom or some kind of kernal error so I installed the stock rom thinking that I will just re-root if however the connection problem still was still there. So now I have kindle fire which is not rooted so doesn't have google market and I want to root it however cannot find a way to get it connected. I have tried 3 different computers and many different cables however still no success. I have also tried reinstalling the drivers, turning off and on the kindle fire with the cable plugged in. Could the port on the kindle fire be broken even though it charges fine. Also, would a factory cable help because I don't want to order it if it doesn't work. What other options do I have? I live in UK and this kindle fire is the 1st gen which was only available in US so cannot send it to amazon for checking.
Your help will be appreciated :good:
Do you have TWRP installed? If so, try connecting it to the computer using the USB mount via TWRP...
I have 3 Kindle Fire tablets that I installed a JB ROM on for some friends, and one will not connect to the computer (except via TWRP). I never did figure out why, but I could copy a ROM and Gapps to it while in TWRP. I set them all up the same, and that one still doesn't connect.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
http://forum.xda-developers.com/showthread.php?t=2179748
No root therefore no twrp
larryf said:
Do you have TWRP installed? If so, try connecting it to the computer using the USB mount via TWRP...
I have 3 Kindle Fire tablets that I installed a JB ROM on for some friends, and one will not connect to the computer (except via TWRP). I never did figure out why, but I could copy a ROM and Gapps to it while in TWRP. I set them all up the same, and that one still doesn't connect.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
Click to expand...
Click to collapse
Sorry for the late reply but no i do not have twrp as went back to stock as I thought that root cause some problem. So now I'm stuck without root and therefore without play store and I cannot root
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
Thanks I will try this and get back to you
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=2179748
Click to expand...
Click to collapse
I tried following the guide however I cannot do the hardware ID bit because in device manager it doesn't show the hardware id. It just shows unknown device
shlokpatel said:
I tried following the guide however I cannot do the hardware ID bit because in device manager it doesn't show the hardware id. It just shows unknown device
Click to expand...
Click to collapse
Plug the device in and manually uninstall the unknown device that shows up in Device Manager. Then Find the directory where the 'android_winusb.inf' is stored (somewhere in your WINDOWS directory), delete it, and start over.
soupmagnet said:
Plug the device in and manually uninstall the unknown device that shows up in Device Manager. Then Find the directory where the 'android_winusb.inf' is stored (somewhere in your WINDOWS directory), delete it, and start over.
Click to expand...
Click to collapse
Tried but still not working
Could it be possible that the port on the kindle fire is broken as I have tried connecting in on many computers and in none it has worked. Also I dont know if this is relevant but when I connect the kindle fire to the computer, the device is connected screen doesn't come up, it just charges and thats it no other change
shlokpatel said:
Tried but still not working
Could it be possible that the port on the kindle fire is broken as I have tried connecting in on many computers and in none it has worked. Also I dont know if this is relevant but when I connect the kindle fire to the computer, the device is connected screen doesn't come up, it just charges and thats it no other change
Click to expand...
Click to collapse
If this is the stock OS, then I would say that is definitely a problem. You may have some system files missing for detecting USB devices plugged in as UMS. Are you able to access any flash drives?
soupmagnet said:
If this is the stock OS, then I would say that is definitely a problem. You may have some system files missing for detecting USB devices plugged in as UMS. Are you able to access any flash drives?
Click to expand...
Click to collapse
Yes, my computer detects my galaxy s2 and other flash drives perfectly. Is there any way of rooting the kindle fire without connecting it to the computer? Because all i want is to have the play store on my device
The new version of KFU seems to have a much more effective driver install. You should try looking into that.
soupmagnet said:
The new version of KFU seems to have a much more effective driver install. You should try looking into that.
Click to expand...
Click to collapse
Still doesn't work Any method of rooting without computer connection ?
EDIT:
Also tried the soupkit on Linuxmint and still no luck
Hi there,
I'm having the same problem with a kindle fire.
- Stuck at logo
- Driver is installed but device is not recognized, so does hardware id.
Hope some one have a solution
bangsnntk said:
Hi there,
I'm having the same problem with a kindle fire.
- Stuck at logo
- Driver is installed but device is not recognized, so does hardware id.
Hope some one have a solution
Click to expand...
Click to collapse
Windows version?
Listed as what in Device manager?
Sent from my XT894 using Tapatalk
I am having the same issue with my KF2. USB Comms disappeared in terms of the device being recognised by XP but strangely fastboot worked and I was able to load CM11 on the device after downloading it via wifi and installing TWRP via fastboot. Still no USB on CM11 but its briefly recognised for a split second when it first boots. Monting the volume via TWRP has not effect either.
Have tried a variety of cables and have tried connecting the Kindle to an XP netbook, downloading fresh drivers etc etc etc.
Any ideas out there?
Shotaway said:
I am having the same issue with my KF2. USB Comms disappeared in terms of the device being recognised by XP but strangely fastboot worked and I was able to load CM11 on the device after downloading it via wifi and installing TWRP via fastboot. Still no USB on CM11 but its briefly recognised for a split second when it first boots. Monting the volume via TWRP has not effect either.
Have tried a variety of cables and have tried connecting the Kindle to an XP netbook, downloading fresh drivers etc etc etc.
Any ideas out there?
Click to expand...
Click to collapse
I Think you would get better help in one of the Kindle Fire 2 / KF HD Q&A forums
Sent from my XT912 using Tapatalk
sd_shadow said:
Windows version?
Listed as what in Device manager?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Same problem.
Problem:
-stuck @ logo screen
-usb not recognize by computer (windows 7 OS)
I already tried using different sets of cable, reboot both kindle and pc, tried to insert on different usb ports, tried to install adb and adb drivers. still not recognize.
Please help, any suggestion is very much appreciated.