Related
I'm not a stupid person, but I am a slightly distracted widowed father of a three-year-old, and I've become so frustrated that I can't think straight!
I'm not a developer, but I've always easily rooted my devices by following the instructions. Until the Kindle came along.
I had all kind of trouble, wrong drivers, general mistakes, etc. Finally, everything appeared to be working, and then I had a hard drive crash during the root process. TWRP was installed, but, apparently, nothing else.
Took it to a second computer, downloaded KFU, installed drivers, ran. Partial success. TWRP appeared to be running smoothly. Downloaded ROM (Don't even remember which, Kindle has been thrown in drawer for weeks!) ROM appeared to install, but wouldn't boot. Here's where I got extra-stupid:
Obviously, something is already wrong with my Kindle, but at least I can see it in device manager. At least I can access it through KFU. For some insane reason, I began trying everything I could think to do, and eventually got TWRP into a recovery bootloop. Yay, me!
Now, I've screwed around on multiple computers, in Windows and Ubuntu. I'm completely confused as to which drivers are loaded where, Kindle shows up in Device Manager as a phone, but does not show up as a drive in Windows Explorer, and KFU, while it runs just fine, alternates between between telling me that it's "waiting for device," or "the system cannot find the drive specified."
Help on the Forums has been wonderful, but I am beyond that. My last post was answered with "Which drivers have you installed?" Well, crap! I don't know. I probably knew a month ago when the problem started, but I can't think rationally (where the Kindle is concerned, I seem to do OK in real life) anymore!
Now, I know that I've got so much crap going on, that most of you don't want to trash up the forum by trying to address my multiple issues. Please do not post "Have you tried the search tool?" Re-read my far too long post. I don't even know what the crap to search for anymore!
So, finally, here's my question? Anybody want to try their hand at fixing my F-'d up Kindle? It's not doing me a bit of good as is so, even if I mail it to someone and they just keep it I haven't really lost much!
All I want is a nice, stable (STABLE!) Gingerbread or ICS ROM that my little boy can watch Netflix on. I'll gladly pay anyone a reasonable amount to anyone willing to take this problem off my hands...
If you have TWRP installed can you mount the USB drive in it and then flash what you want?
When I mount usb storage in twrp, it does allow me to access the device on the computer, which is much better than I was getting. When I run KFU it still stated that it cannot find the device. If I run Kindle Unbrick, it open the command line, then just hangs up.
RobWoodall said:
When I mount usb storage in twrp, it does allow me to access the device on the computer, which is much better than I was getting. When I run KFU it still stated that it cannot find the device. If I run Kindle Unbrick, it open the command line, then just hangs up.
Click to expand...
Click to collapse
No need to run KFU... Just copy FFF to the Kindle and flash from TWRP. Then copy what rom you want and Flash from TWRP.
And, make sure you flash the FFF version (1.4a) in this thread:
http://forum.xda-developers.com/showthread.php?t=1632375
Your download should be named: fff-u-boot_v1.4a.zip.
You will see some notes in that thread about NOT flashing this file, but those are for an older zip. This is a flashable .zip ... I just installed (flashed) it last week from TWRP.
(P.S.) Your KF is not in as bad of shape as you might think. This is a quick fix with the right setup.
I had a similar problem. First you should download Kindle Fire Drivers(the one that came with KFU didn't work...) and install it. Then in TWRP mount the SD card. Update the drivers using that Kindle Fire Driver folder(I will upload it and give you the link). Then with KFU press 1(bootmode) and then 1 again(normal). I think this should get you out of bootloop. If that doesn't work, just flash the Kindle Fire Stock Rom.
Sent from my Kindle Fire using xda premium
When I said install Kindle Fire Drivers I meant download. Then manually install the drivers(My Computer, right click,
properties, hardware, and open up device manager. If you get android device or something, click on it. If you see Kindle with a ! then click on update drivers and select the kindle fire driver folder. If you don't see kindle, or if you see Android device, then uninstall. Then go to disk drives and find your kindle fire and uninstall. Close and re-open, and you should see Kindle! Then update the drivers. Open up KFU and change bootmode to normal. Do a 20 sec. hard reset and see if it boots. If your trying to install a Custom ROM(ICS or honeycomb) put the .zip file on you kindle fire. Then open up TWRP and choose Wipe, and Factory Reset. Then wipe Cache and Dalvik Cache. Then go to install and select the ROM. After install the boot may take awhile. You said you tried this but you got stuck in bootmode, so make sure you follow these instructions. Make a backup if you ever want to go back. Move the backup to your computer as it takes up almost 1.5gb of space. Please inform me if this doesn't help. Sorry if I'm not good at giving instructions,but I'm only 14.
Sent from my Kindle Fire using xda premium
Here is the Link for the folder. Just unzip and update your Kindle Fire with it: http://www.mediafire.com/download.php?lnx766ac84o7q1i
RobWoodall - hang in there, because a lot of us were exactly in your shoes. For the life of me I can't get most of the ubuntu stuff to work, and windows was a bit of a nightmare for drivers until sorted out. I bootlooped, thought I bricked, etc etc but all sorted out in the end.
The fact you can see it in device manager is good. What you need to do is to replace the drivers with the 'Android Composite ADB Interface' - this video may help you out
I'm sure folks here will try to help you out without taking your money
Thanks, but I don't seem to be able to find a current version of FFF. Probably because I'm not thinking clearly.
tedr108,
Thanks, but the link appears to be unavailable at this time. I'm not hopeful, as I have been quite able to install ROMs. For all I know they are running perfectly. My most immediate problem seems to be that I'm trapped in a bootloop, and no matter what I do, the Kindle always boots into TWRP. Apparently I'm in boot mode 5001, and I should be in mode 4000 or some such. KFU should be able to change the boot mode, but it only gives me "waiting for device."
RobWoodall said:
Thanks, but I don't seem to be able to find a current version of FFF. Probably because I'm not thinking clearly.
Click to expand...
Click to collapse
Here is the latest copy of FFF 1.4A that I have.
Dropbox link (while Rombot is down):
https://dl.dropbox.com/u/41149741/KFire-Android/fff-u-boot_v1.4a.zip
md5sum: 419c53b922c963082454b14b7de75a90
Edit: Tera Tike is on the ball! (Thanks I almost never ready this forum)
josepho1997,
Thanks. Downloaded and installed perfectly. Unfortunately, the Kindle will still only boot into TWRP recovery. Apparently I'm in boot mode 5001, and should be in 4000 or 4001 or something. It's really getting frustrating!
Use sudo command in ubuntu power it off type sudo fastboot getvar product plug your kindle in it should return kindle as a response your kindle then your kindle will be in fastboot then type sudo fastboot oem idme bootmode 4000 hit enter then type sudo fastboot reboot it should boot in normal mode
Nevermind, someone beat me to it...
RobWoodall said:
josepho1997,
Thanks. Downloaded and installed perfectly. Unfortunately, the Kindle will still only boot into TWRP recovery. Apparently I'm in boot mode 5001, and should be in 4000 or 4001 or something. It's really getting frustrating!
Click to expand...
Click to collapse
It seems that your system is bad.
Tera Tike,
Thanks! I think I love you! Worked perfectly. I'm now running CM7 Barebones, because that's the last ROM I had tried to flash. Now that I understand the process, I'll certainly experiment with other ROMs, but Bare Bones looks pretty darn good after staring at the TWRP menu for a month and a half!
P.S. Nope! My system wasn't bad, the operator was!!! LOL!
Thanks, Hashcode! I got the file from Tara Tike. Fantastic work! That simple option to reset bootmenu on the first page was all I needed all this time!
RobWoodall said:
Tera Tike,
Thanks! I think I love you! Worked perfectly. I'm now running CM7 Barebones, because that's the last ROM I had tried to flash. Now that I understand the process, I'll certainly experiment with other ROMs, but Bare Bones looks pretty darn good after staring at the TWRP menu for a month and a half!
P.S. Nope! My system wasn't bad, the operator was!!! LOL!
Click to expand...
Click to collapse
Great!!! Hashcode FFF is the best!! Now enjoy your hard work!
Thanks, Hashcode for all you have done for us Fire users!!
I really appreciate everyone's help! I've been sharing the nook with my three-year-old. He's a pretty smart kid but, once he learned how to change icons and wallpaper, install and uninstall apps, it's a completely different experience every time I turned it on. I bought the Kindle so I could have MY OWN tablet!
If anyone is still reading this thread, please give me some recommendations for ROMs. I typically only use Google Play Books, Contacts and Calendar, Aldiko Reader and Netflix. I'm not in the market for fastest or fanciest, but most stable. I don't care if it's Gingerbread or ICS (Heck, even Honeycomb if it's stopped sucking!) So what do you all say?
What's the most stable ROM out there for a person who needs Google compatibility on the Kindle Fire?
Hello! I get myself in a huge mess! and now I dont know what to do, I've been looking for a lot of solutions here but I cant fix my Kindle Fire...
I tried to rooted it but it didnt work and now it my pc says that the Device is not recognize, and the screen just show the Kindle Fire Logo...
It's been like that for a while... I'm ok with just the normal Kindle, without the rooting stuff v.v just need to make it work! please heeeelp
Help us help you...
What exactly did you do? (not just "tried to root and it didn't work") Did you install TWRP or FFF?
I don't see why your computer would say the device isn't recognized, when it shouldn't even show it at all (as it's stuck booting).
Sounds like your stuck in fast boot or something got erased or changed from the stock system.
Happened to me more than I care to admitted early on.
Try the app here: http://forum.xda-developers.com/showthread.php?t=1399889
It'll should be easier than using terminal. I haven't personally tried it.
It you have fastboot working > fastboot -i 0x1949 bootmode 4000 then fastboot reboot might get you on track quickly. If using Linux you need to be su, not sure if windows cmd needs administrative rights.
Good luck and report back.
Ok, the thing is that I unplug the Kindle probably before I should, I'm not quite sure :S! But the computer dont recognize the Kindle, though it does recognize it as ADB Android Phone sometimes...
I tried to install the driver manually but it didnt work, when I run the Utility is still offline... and I cant see the Kindle in "my PC" either...
I tried ti the thing with the Device manager, but it doesnt show anywhere the Kindle devices... so I'm pretty sure I'm doing something wrong! but the thing is I dont Have any Idea :'(
>.<!
Have a read here: http://forum.xda-developers.com/showthread.php?t=1552547
Fix the drivers as instructed in that thread (second post), and then post here your precise issue (or whatever it is you'd like to achieve), as detailed as possible.
For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
favaron88 said:
Ok, so let me preface this by apologizing if somehow the answer to my question is already lurking in the forums. I promise I have been looking for the better part of 3 hours and trying to figure this out on my own. My pride now hurts, and I have a headache. Please help me.
I was attempting to root my kindle fire, and put a custom rom onto it after getting jealous of my sister in law's samsung galaxy tab. I had previously done this back in april, but I decided to go back to the regular stock kindle fire (I think because netflix still wouldn't work otherwise at the time). I went to attempt and do basically exactly what I did in april with the newest version of KFU I could find here on xda, and attempted to install hash's jelly bean rom and gapps on it. I had made a back up restore point, but when I wiped stuff to get it all fresh, I must have wiped the restore. I couldn't get the jelly bean rom to work, it just stayed at the millions of triangles loading screen literally for like 30 minutes before I gave up. I decided to just go back to stock and forget about it. After putting the update.zip on the kindle and flashing it with TWRP, it boots up and just stays at the kindle fire logo, flashing every once in a while. When connected to KFU the ADB says online, but boot type says unknown. I tried to go into the boot type and tell it to go into different boot modes, and nothing changes. It just stays at the kindle fire loading screen, taunting me, laughing at me. I'm assuming that now my internal memory and SD card memory are both completely wiped and it's just got a bootloader or something and nothing else is there so it's in eternal start up mode with nothing to start up? I don't really know, and won't pretend to. I've taken a college level c++ intro to programming class (just finished it last week with an A-) and I've been a computer nerd for most of my life, so I'm not a toooootal noob, but I really have no experience with linux or anything other than playing around with ubuntu for like 4 days over the summer a few months ago. I'm currently downloading it and going to attempt to put it on a usb stick and boot into that so I can try and use soups application to see if that will help me, but I'm not even sure if that's what I need, and frankly I'm horrified to try and use linux for fear of screwing things up even more.
If my Kindle Fire is screwed, it's ok I suppose, but if there's a way I can fix it, I'd love to know.
Sorry for the wall of text, and thank you for any help that is offered. I'm almost to tears from the frustration and headache this has caused me, and you are much appreciated just for reading.
Cheers.
PS - I'm willing to give any screen shots, pictures, or anything else necessary to help diagnose the problem, just let me know.
Click to expand...
Click to collapse
Do you have a bootloader installed? Can you boot into recovery?
Eaffon said:
Do you have a bootloader installed? Can you boot into recovery?
Click to expand...
Click to collapse
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
favaron88 said:
Nope, I'm pretty sure it wiped out anything I had when I tried to restore it to factory. I can no longer access TWRS and I have no FFF installed it seems. I literally can turn the kindle on, watch it sit at the kindle fire screen, and turn it off once that starts pissing me off. no amount of holding the power button or pushing it different ways gets me into TWRS or anything.
Did I answer your question or was that not what you were asking?
Click to expand...
Click to collapse
Hmm... Does it show up in device manager?
Dont throw it.. give it to me. Haha
After my sem I will have plenty of time to do all this stuff..
Sent from my SGH-T999 using xda premium
Eaffon said:
Hmm... Does it show up in device manager?
Click to expand...
Click to collapse
I've uploaded a screen shot of my device manager and in "devices and printers"
as you can see, it shows up as a kindle in devices and printers, and as an android phone in the device manager.
I also uploaded "My Computer" so you can see there is no access to it from there.
Okay.
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Eaffon said:
See if you can issue fastboot or adb commands through command prompt. Navigate to your .android folder and type fastboot devices and adb devices and tell me what shows up.
Click to expand...
Click to collapse
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
favaron88 said:
I'll be honest, I'm not too good with command prompt... Is the .android folder going to be on the Kindle itself? once i get in that directory do I literally just type "fastboot devices" and "adb devies" or is there a command associated with that?
Click to expand...
Click to collapse
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Eaffon said:
should be in C:\Username\.android if its not there you can copy the files over from KFU. Its in the tools folder of KFU so you can just point command prompt there and then issue the command.
Click to expand...
Click to collapse
alright, I found it and tried those commands and this is what I got.
favaron88 said:
alright, I found it and tried those commands and this is what I got.
Click to expand...
Click to collapse
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Eaffon said:
I cant see the picture, but you need to cd to the files.
ex "cd C"\Users\Jimmy\Desktop\KFU\tools\" then issue the commands.
Click to expand...
Click to collapse
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
You could try my prefab ISO soupkit is already ran on it and it has teamviewer installed for assistance measures you can find it here post 7 http://forum.xda-developers.com/showthread.php?t=1413358 but what I think you will need is a factory cable found here ultimately post 9 http://forum.xda-developers.com/showthread.php?t=1392693 . The system is trying to run that's why it comes up android composite adb interface, its busy trying to handle the data that you failed to wipe prior to flashing jelly bean and then stock. You could also see if if will allow you to send twrp and fff back to the device with kfu then enter recovery wipe and reflash another ROM.
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
It's totally fixable.
Thepooch is right. My brother had the same problem with his son's. Just get into fastboot and flash a bootloader and twrp and youre set
Sent from my Amazon Kindle Fire using xda app-developers app
Thepooch said:
It's totally fixable.
Click to expand...
Click to collapse
Awesome
Also I didn't want you to think I ignored your post. I just finished making the usb drive with ubuntu on it and was going to attempt your solution in the other thread if whatever we were trying here doesn't work.
I appreciate y'alls help very much.
Eaffon said:
Okay we need to get it to boot into fastboot. Change the bootmode to fastboot in kfu so we can push recovery/fff
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Ok I loaded KFU and told went and told it to boot in fastboot, it said that it told the device to do it, but it still says Boot Status: Unknown.
Is this a problem or do we know that it's booting in fastmode now? I'm just not sure how to tell if it was successful since it's not giving me the code.
(Ps - I originally posted this before my previous post thanking you guys, but then came back to this window to see that I had screwed up the Captcha, but it wouldn't let me post for 5 more minutes since I'm a new user. Sorry for the wait.)
Its very common for the boot mode to be unknown in fast boot. Try to send twrp with kfu if it says waiting for device for a long time simply power it off while connected then back on it should then pick up and send twrp. If need be do the same thing with the bootloader just wait longer a failed bootloader flash is far worse than the situation your in.
favaron88 said:
Ok, nothing happened with I typed fastboot devices, but when I did adb devices it said
*daemon not running. starting it now*
*daemon started successfully*
List of devices attached
06B6002600000001 device.
image is attached. (Are you not able to see any of them/ is it not helping to upload screen captures? I'm just trying to be as easy to help as possible.)
Click to expand...
Click to collapse
ADB is connected, therefore you are not in fastboot. The Kindle Fire logo you see is actually the stock boot animation. The difference is whether or not it changes in brightness at any point (obviously it does).
You need access to recovery to fix your problem and you need the ability to change bootmodes to get into recovery. Without a working shell you need access to fastboot to change bootmodes.
Unfortunately, in many situations like yours, there is no working shell to change the bootmode. To confirm this, try to launch the shell by entering "adb shell", respectively.
If you receive an error, your only options are to get a factory cable (recommended) or open the device so you can put it in USBboot via the shorting trick and the use of Firekit (not so recommended).
With access to fastboot, you can change your bootmode to recovery or reinstall a custom recovery if necessary. In recovery, the "fix" is as simple as reinstalling a ROM.
"That's a special kind of stupid. The kind that makes me laugh."
I have scoured through pages and google searches for many related subjects and not one has been able to help me thus far.
I have a kindle fire that I rooted and put TWRP on it and android 4.1, a few months back.
The power port is damage so keeping it plugged in can be a challenge but it still works, anyways I digress.
I erased the entire SD apparently and that included my backups.
I can only boot into TWRP and normally that wouldn't be a problem except I can't connect my kindle through ADB commands and it doesn't show up on my computer. I have drivers installed and I have been trying so many different things so if you find something similar to what I'm talking about please let me know as I would love to have this kindle running again.
Many thanks in advance,
-TehRobot.
Mount the sdcard to USB in TWRP.
"That's a special kind of stupid. The kind that makes me laugh."
Ok I tried all the check boxes for mounting, of course mounting the SDcard... but the computer won't recognize the kindle to be even there.
I was running 4.1.0 on c9 and erased the SD card.. After that it wouldn't show up on my computer.
So TWRP is my savior except I can't put any files onto it to flash.. :
Edit****
Does anyone think I should buy a factory cable or breakout board, I think that's what it is called, to try and force the kindle into recovery, then perhaps it would show up on my laptop.
Because I figure if it showed up before, and after the accidental wipe it no longer did I would have to imagine it's the kindle itself.
I don't think that's it, if you're in TWRP you're already in recovery. Have you tried the Linux method in the soupkit sticky thread?
Sent from my Amazon Kindle Fire using xda app-developers app
Tehrobot said:
Ok I tried all the check boxes for mounting, of course mounting the SDcard... but the computer won't recognize the kindle to be even there.
I was running 4.1.0 on c9 and erased the SD card.. After that it wouldn't show up on my computer.
So TWRP is my savior except I can't put any files onto it to flash.. :
Edit****
Does anyone think I should buy a factory cable or breakout board, I think that's what it is called, to try and force the kindle into recovery, then perhaps it would show up on my laptop.
Because I figure if it showed up before, and after the accidental wipe it no longer did I would have to imagine it's the kindle itself.
Click to expand...
Click to collapse
SoupKit will fix your mounting issue OR look for a sticky in the KF General forum that explains how to do it manually.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
SoupKit will fix your mounting issue OR look for a sticky in the KF General forum that explains how to do it manually.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Thanks, going to put Mint 13 on my laptop and get started. I will report back after I get this kindle working again!
soupmagnet said:
SoupKit will fix your mounting issue OR look for a sticky in the KF General forum that explains how to do it manually.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Ok, so I have a partition on my HD with linux mint running on it with all the updates installed.
-DL soupkit.
read the readme.
It wont run in the terminal no matter what I do..
It does however show up in my Home/bin/soupkit.
I tried getting it to run in the terminal manually but to no avail.
I am only a breadth above novice with linux so bear with me please as I am trying to be as specific as possible with the problems I am encountering..
( I had it running in the terminal like normal but it kept asking for a sudo password that wasn't my password, but that was before I fully installed It, I thought I could make it work off the Demo version before full installation was completed.)
Tehrobot said:
Ok, so I have a partition on my HD with linux mint running on it with all the updates installed.
-DL soupkit.
read the readme.
It wont run in the terminal no matter what I do..
It does however show up in my Home/bin/soupkit.
I tried getting it to run in the terminal manually but to no avail.
I am only a breadth above novice with linux so bear with me please as I am trying to be as specific as possible with the problems I am encountering..
( I had it running in the terminal like normal but it kept asking for a sudo password that wasn't my password, but that was before I fully installed It, I thought I could make it work off the Demo version before full installation was completed.)
Click to expand...
Click to collapse
In terminal, are you entering "soupkit.sh" ?
Yes, I followed the instructions as closely as possible.
It wouldn't open, it would say it installed properly but wouldn't run.
Tehrobot said:
( I had it running in the terminal like normal but it kept asking for a sudo password that wasn't my password, but that was before I fully installed It, I thought I could make it work off the Demo version before full installation was completed.)
Click to expand...
Click to collapse
A couple things to note:
In demo (Live) mode, there is no sudo password, you just press enter. Also, in Live mode, nothing gets written to disc, especially if you are running Live from a CD.
If you want to run Live rather than actually installing Linux to your computer, you need to do so from a USB drive with "persistence" (Google it)
I understand this is new to you but all of this information is in the SoupKit thread. Pay close attention to the information you find there, and if there is something it that you don't understand, try to research it to the best of your abilities.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
A couple things to note:
In demo (Live) mode, there is no sudo password, you just press enter. Also, in Live mode, nothing gets written to disc, especially if you are running Live from a CD.
If you want to run Live rather than actually installing Linux to your computer, you need to do so from a USB drive with "persistence" (Google it)
I understand this is new to you but all of this information is in the SoupKit thread. Pay close attention to the information you find there, and if there is something it that you don't understand, try to research it to the best of your abilities.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
No I understand, I had it installed from the windows.exe it gives. You just finish installation whence you log into mint. Anyways,
I was trying to get around having to use a USB, that's all. I will get a bigger USB and try that, I did read the guide pretty closely and I'm sure I can do it, I was just trying to go without USB.
Thanks for all your help though its been a hell of a lot easier.
While attempting to unbrick my kindle using the Linux usbboot short trick and not getting anything detected in firekit and soupkit nor win7 for that matter, my little green power light now is always off. No power via battery and worse not even usb cable to pc even lightsup. Is this totally useless, now?
Probably not. What exactly were you doing when this happened? Please be as detailed as possible.
"That's a special kind of stupid. The kind that makes me laugh."
I had cm7 on for a long time with usb mass storage working and adb etc. Then I went with an early ver. of cm9 and found no usb connection or sd mount was possible. Months later i gave to my gf who wanted photos on it. But windows has not detected it. So I tried to update with cm10 and it was advised to update my twrp to 2.2.2.1. But upon using this new version of twrp I noticed I could only restore a backup I made. That worked. But the flashing of the cm10 rom did not, The touch screen was not responding at all, there.I rebooted into twrp and retried to flash the cm10 with still no screen response so I pressed reboot and saw "bootloader" and pressed it instead of reboot or sysem or plain shutdown. Thus my brick. I read much and guess i was stuck in fastboot mode and w/o any adb detection by windows 7 went with Linux usbboot shorting trick. Made the usb stick boot up to ubuntu and tried firekit and soupkit to no avail. Always showed Waiting for device!. Of course the back was off and pin shorted on mobo. Minutes later I notice all lights of kindle fire are out. No more Triangle or anything! Pc usb cable does not power it on nor does my battery charger in ac or solo w/battery. This is what I can recall from last 3 days.
Smmoph said:
I had cm7 on for a long time with usb mass storage working and adb etc. Then I went with an early ver. of cm9 and found no usb connection or sd mount was possible. Months later i gave to my gf who wanted photos on it. But windows has not detected it. So I tried to update with cm10 and it was advised to update my twrp to 2.2.2.1. But upon using this new version of twrp I noticed I could only restore a backup I made. That worked. But the flashing of the cm10 rom did not, The touch screen was not responding at all, there.I rebooted into twrp and retried to flash the cm10 with still no screen response so I pressed reboot and saw "bootloader" and pressed it instead of reboot or sysem or plain shutdown. Thus my brick. I read much and guess i was stuck in fastboot mode and w/o any adb detection by windows 7 went with Linux usbboot shorting trick. Made the usb stick boot up to ubuntu and tried firekit and soupkit to no avail. Of course the back was off and pin shorted on mobo. Minutes later I notice all lights of kindle fire are out. No more Triangle or anything! Pc usb cable does not power it on nor does my battery charger in ac or solo w/battery. This is what I can recall from last 3 days.
Click to expand...
Click to collapse
Ok, the reason I ask...
Your device is either in USBboot or you didn't install a bootloader properly. At first glance it seems it's the latter. In Firekit, select "usb_install_fff_twrp". If it just sits at "waiting for OMAP4 device" you'll need to use the shorting trick to detect the device and get the bootloader installed properly. Afterwards, if I were you, I would use recovery to install the latest version of FFF before rebooting.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
Ok, the reason I ask...
Your device is either in USBboot or you didn't install a bootloader properly. At first glance it seems it's the latter. In Firekit, select "usb_install_fff_twrp". If it just sits at "waiting for OMAP4 device" you'll need to use the shorting trick to detect the device and get the bootloader installed properly. Afterwards, if I were you, I would use recovery to install the latest version of FFF before rebooting.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
I will try when the Kindle fire turns on. Rather, if it ever powers up. Thanks for your time and response.
Smmoph said:
I will try when the Kindle fire turns on. Rather, if it ever powers up. Thanks for your time and response.
Click to expand...
Click to collapse
No, you misunderstood. The device already powers up (even though it doesn't seem like it), it just doesn't have a working bootloader. Without a working bootloader, the only way you can communicate with the device is to put it in USBboot.
There's a possibility it is already in USBboot (unlikely) and Firekit will send commands anyway. Otherwise, you need to use the shorting trick to temporarily put it in USBboot long enough for Firekit to work.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
No, you misunderstood. The device already powers up (even though it doesn't seem like it), it just doesn't have a working bootloader. Without a working bootloader, the only way you can communicate with the device is to put it in USBboot.
There's a possibility it is already in USBboot (unlikely) and Firekit will send commands anyway. Otherwise, you need to use the shorting trick to temporarily put it in USBboot long enough for Firekit to work.
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
Alright I will give it a go. It will have to wait till tmmrrw, tho.
Thanks
On another route, What if I buy a new KF 1st Gen. from a retail store and put this bricked one in the new box with cords, papers etc. and return it within the full refund time would I stand a chance at getting refunded? Also since it won't light up could I claim it is simply bad hardware section of the unit? Plus would it eventually get torn down ,Amazon..where they might see it was rooted and registered by me?
I have a better idea. Why don't you take some personal responsibility for a problem YOU created and either fix it yourself, send it to someone who can, or suck it up and cut your losses?
I could go on all day about the moral, let alone the practical, implications of how such a decision will impact the community as a whole, but we both know that would be a complete waste of my time.
Do as previously suggested or not, but don't complain when it becomes increasingly harder to make a device, one that you've spent your hard earned money on, your own.
"That's a special kind of stupid. The kind that makes me laugh."