Related
Hi. I just got a Kindle Fire 6.3 that I rooted recently through instructions from this site. Worked like a charm. I then installed CM7 and decided that I didn't like it, so I removed it. I restored to the backup I made before installing CM7. It worked fine after that. To save space, I went into the root and deleted the backup and rom files that I didn't think I needed anymore. I called Amazon because I was having trouble streaming videos from the amazon video store. So... they told me to do a factory reset. Now it keeps booting into the TWRP menu and won't go any further. After this, my Windows PC also no longer recognizes my Kindle, ever after reinstalling drivers from the Kindle Fire utility. I have the Kindle 6.3 update, but I can transfer it to my Kindle's root since my PC can't see the Kindle. My PC makes the noise when I connect and disconnect the Kindle, but I can't access it. Any ideas? PLEASE HELP!!!
jespiritu said:
Hi. I just got a Kindle Fire 6.3 that I rooted recently through instructions from this site. Worked like a charm. I then installed CM7 and decided that I didn't like it, so I removed it. I restored to the backup I made before installing CM7. It worked fine after that. To save space, I went into the root and deleted the backup and rom files that I didn't think I needed anymore. I called Amazon because I was having trouble streaming videos from the amazon video store. So... they told me to do a factory reset. Now it keeps booting into the TWRP menu and won't go any further. After this, my Windows PC also no longer recognizes my Kindle, ever after reinstalling drivers from the Kindle Fire utility. I have the Kindle 6.3 update, but I can transfer it to my Kindle's root since my PC can't see the Kindle. My PC makes the noise when I connect and disconnect the Kindle, but I can't access it. Any ideas? PLEASE HELP!!!
Click to expand...
Click to collapse
Its in a fast boot boot loop go into kfu and hook it up the press normal boot it will say waiting for devices then turn off the kindle wile connected by holding the power button then turn it on and it will connect during boot up
Sent from my LG G2x using Tapatalk 2
DJLamontagneIII said:
Its in a fast boot boot loop go into kfu and hook it up the press normal boot it will say waiting for devices then turn off the kindle wile connected by holding the power button then turn it on and it will connect during boot up
Sent from my LG G2x using Tapatalk 2
Click to expand...
Click to collapse
Even if the PC won't recognize the Kindle?
jespiritu said:
Even if the PC won't recognize the Kindle?
Click to expand...
Click to collapse
Try it if not uninstall the drivers in device manager then reinstall
Sent from my LG G2x using Tapatalk 2
Try going to where fast boot drivers are located ie. Sdk/tools etc. Open command print there and type "fastboot devices" (no speach marks).
See what you get.
Sent from my Amazon Kindle Fire using xda premium
you need to mount your device as usb storage. its not in fastboot, its in recovery lol
adb devices should make it pop up. than adb idme bootmode 4000.
twrp is your issue, and will continue to cause issues like this for you and others!
Sent from my HTC Glacier using xda premium
How do I mount the device as USB storage? Device is online with kfu, but the boot menu says "The system cannot find the drive specified." I've also uninstalled and reinstalled the drivers and nothing. Even when trying to reinstall twrp, it's stuck on activating fast boot (4002).
jespiritu said:
How do I mount the device as USB storage? Device is online with kfu, but the boot menu says "The system cannot find the drive specified." I've also uninstalled and reinstalled the drivers and nothing. Even when trying to reinstall twrp, it's stuck on activating fast boot (4002).
Click to expand...
Click to collapse
In twrp there is an option to mount storage
Sent from my LG G2x using Tapatalk 2
Thanks, all! Mounting to storage worked. I just copied the kindle 6.3 zip update to the root and installed. Everything works fine now! Thanks again!
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."
Hey guys. I have my kindle fire over a year now and recently it started sticking a lot and certain things i would press would open something else. I decided to basically format it by using Kindle Fire Utility. I got into TWRP Recovery and made a backup; wiped Cache and Davlik and so on, then I tried installing an update from the update.zip I uploaded and from there, I have had this boot screen. I cannot get into the device, but when I plug it into the computer, it tells me the device is Online but the Status is unknown. Please help me out!
Thanks a Million!
silentarts said:
Hey guys. I have my kindle fire over a year now and recently it started sticking a lot and certain things i would press would open something else. I decided to basically format it by using Kindle Fire Utility. I got into TWRP Recovery and made a backup; wiped Cache and Davlik and so on, then I tried installing an update from the update.zip I uploaded and from there, I have had this boot screen. I cannot get into the device, but when I plug it into the computer, it tells me the device is Online but the Status is unknown. Please help me out!
Thanks a Million!
Click to expand...
Click to collapse
This is from not doing a "factory reset" in recovery before flashing the update.zip.
In testing the new version of SoupKit, I attempted to break the shell intentionally by installing the update.zip without doing a factory reset in the hopes that I would receive the typical "- exec '/system/bin/sh' failed: No such file or directory (2)" error that is usually accompanied with trying to change the bootmode over a missing or corrupted shell. After several attempts to intentionally put myself in that situation, I could never actually make it happen. However, after leaving the KF alone for a minute or two while it tried to boot and sat at the Kindle Fire log, it would usually boot into the Kindle Fire stock recovery and give me the option to factory reset.
You could try that out to see if it works for you, but there's still a good chance that you'll need to acquire a factory cable to get into fastboot so you can reinstall FireFireFire and custom recovery to fix the problem.
Thanks!
Ok. My question now is. When I launch KFU, I press 1 and then what do I press 2 or 3? then leave it let to do it's thing?
My main issue though is this message:
- exec '/system/bin/sh' failed: No such file or directory (2) -
is there no way to fix permissions?
Stress
I tried what you told me on all boot modes, but I keep getting this error.
Anyways. I tried pushing a file to the system via adb and this is what it shows...
adb push zergRush /
failed to copy 'zergRush' to '/zergRush': Read-only file system
Is there any way to push a folder with the correct permissions?
Please help me...
Got something
Hey. I am running through some adb commands and I tried
adb pull / /fadil
Click to expand...
Click to collapse
It actually copied some files...
I am not sure if it is possible, but can you delete folders or push folders through adb?
I also did adb root and it told me that adbd cannot run as root in production builds
Thanks!
Yeah, that error means your shell actually is screwed and you need a factory cable.
This is a cross-post, sorry but I need the help...
Hello Forum Lords, I hope that I found the proper thread for my problem.
I was simply trying to get Jelly Bean onto my wife's replacement KF1 after the first KF1 suffered some sore of hardware malfunction and would no longer take a charge. Somehow, somewhere I went horribly wrong this time around. I got stuck at the KF1 logo and eventually I got it to boot, but only to recovery (TWRP).
My predicament is this: My KF1 is stuck booting into TWRP. Device manager on Win Vista recognizes the KF1 as Android Composite ADB Interface. When I try to use the KFU to boot the device into Normal Mode it says "cannot find the drive specified".
At the KFU starting menu, it says ADB Status: Online, Boot Status: 0x5003.
My ultimate goal is to get this thing running with Jelly Bean (like I accomplished with the first one before it broke) again. I am painfully noob at all of this. Please speak as you would to an escaped chimp who will not let go of the keyboard and mouse.
Thank you, anybody?
Do you see the blue kindle fire logo when it boots?
No. Normal Boot logo
Can anyone help me out? Please?
silentarts said:
Can anyone help me out? Please?
Click to expand...
Click to collapse
Can anybody else help me out?
Can anybody else help me out?
silentarts said:
Can anybody else help me out?
Click to expand...
Click to collapse
Pay attention to the instructions given to you. Get a factory cable.
Don't live in America.... I'm from Trinidad and Tobago
silentarts said:
Don't live in America.... I'm from Trinidad and Tobago
Click to expand...
Click to collapse
You have two options. You can make or acquire a factory cable or you can usbboot. The factory cable is the easiest and safest option for you. If you decide to usbbot, you'll need Linux, Firekit, good eyes, and a steady hand. It will require you to open the device and short a point that is slightly larger than a grain of sand. It's significantly more difficult than using a factory cable and puts you at risk of doing permanent damage to your device's hardware.
Thanks a lot... Will see what happens....
Okay... so I did something stupid.
I rooted my new Kindle Fire HD 8.9" ...and every worked perfectly. But then I installed Nova Launcher and encountered a number of bugs--the worst of which was that trying to move icons would result in the screen flipping upside down. So here's the stupid thing: I tried to unroot it without looking online.
So, first, from the Kindle Launcher I restored the system to factory defaults. That god rid of a lot of the stuff I'd added, but the system was still rooted.
So then I looked online and tried a few things to no avail. Then I finally tried the "correct" method to unroot--b4nary's binary utility--but was unable to do so. I looked online further, found nothing remotely helpful, and then decided to re-run the binary utility under the assumption it'd be like reinstalling software... (yeah, guess that's not the case).
So, anyway, that's what I did.
I ran the .bat, chose restore my data, and then the Kindle rebooted in it's super-sluggish form.
And that's where I'm stuck.
After the unlock screen I get a "complete action using" window for Home (default launcher) and Nova, and an error message on top of it saying "Process system is not responding. Would you like to close it?"
If I choose Home to launch, for example, I get another error window saying "Activity System is not responding. Would you like to close it?"
And I can still access all of the directories on my Kindle via My Computer.
...
So, I've heard that so long as your Kindle is at-all responsive, it's not bricked... but at the same time, I can't seem to find anyone else in the entirety of the Internet to have had the same problem. I was stupid, I know that... but does anyone have any ideas on how I might go about resolving this problem?
Personally I would try reflashing the system partition, because I don't know exactly what broke, never seen the system process crashing. Might be fixable using a different method, but unless someone else knows exactly what happened I would reboot in fastboot and use the kfhd restore utility in the 8.9 inch kf android development the section. It will be pre-rooted though and without the alternate launchers installed, but you can always put those back on.
You have rebooted the kindle right?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Okay... I've made some progress. I was able to boot up Nova without getting any non-responsive errors, and from there--slowly, haltingly--was able to wind my way to the settings menu and select "reset to factory defaults." So that whole process went through and I now (finally) have a responsive Kindle.
I can boot into either Nova or Home.
The problem is, I'm missing many of the programs/applications that were part of the rooting process.
At this point I think, since I can't get b4nary's tool to unroot, I'm best off just trying to re-install everything (all that Google stuff post-rooting) and try to make the best of things. It doesn't look I'll be able to unroot without buying a special cable.
Is there any way to... I don't know, run like a diagnostic of the OS to verify that everything is functioning properly?
Okay, so I installed the various Google utilities needed as a prereq. for Google's Play Store... but quickly found I couldn't use ES File Manager fully.
As far as I can determine, the chief problem I am facing now is that the Super User application--the one that's installed on a properly-rooted Fire--is no longer on my machine... and AFAIK the only way to put it on there is to use the .bat utilitity that was the cause of all these problems in the first place.
EDIT:
Messing with the Kindle further, there's some weird stuff going on. In addition to not being able to fully use ES File Explorer, I cannot uninstall the Nova Launcher... which will not function in the first place without rooting... almost like it's only half-rooted.
U can't uninstall it because its on the system partition, and has to be for the kindle to let you use it. The system partition mounts in read only mode by default and needs root to remount in read/write mode so you can delete it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
So... what do I do now? I've been able to install Chrome, but can't install Google Play Store w/out being able to use ESFE to move stuff around inside the partition explorer, and I can't use the batch file to unroot the Kindle because it's only half-rooted and doesn't have the necessary SuperUser program (and d/ling Super User and Super SU .apks hasn't helped anything)--and, of course, trying to re-root via batch half-bricks the thing.
So... would reflashing the system partition effect anything, and if so, how exactly would I go about doing that?
Well let's put It this way, reflashing the system partition isn't going to wipe many of then apps installed or their settings or the contents of the sdcard, all it does is reflash the system partition to stock rooted, no launchers and I think it also doesn't come with Google play and its framework, so make sure to install kindle free before you do this, makes life easier after you flash it to get Google play back up and running. Since I believe the kfhd doesn't work with a fastboot cable simply plug the kindle in with USB debugging turned on, and run the command from an command prompt that's cd'd into the same folder as an adb command, like the folder binary's root comes in, and run the command in step 2 of the kfhd8.9 system restore utility. On another note, when the kindle boots into fastboot, if your PC doesn't find many drivers compatible with the device, download the drivers from my signature, and go to the device manager and there would be a device with a triangle or something on it, tell it to update driver and point it to my drivers. The rest of the instructions are in the thread the utility comes from lemme get a link to it for you.
Edit: um ignore some of my instructions as i thought the 8.9" version of this tool's page was a clone of the 7" models page with a 8.9" set of images and I was wrong, its even more straightforward than i thought. Just shut the device off and when u launch the tool hit enable fastboot, then in plug you device in. Tell it to restore the kindle, and it even has the option to install the Google play store and framework for you. Here's link: http://forum.xda-developers.com/showthread.php?t=2011126
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hm... that seems very promising, but no luck so far.
I run the batch and get stuck with it "waiting for device," even long after the Kindle shows up in My Computer. Guess I'll try re-installing the drivers and retrying the batch file a few more times.
EDIT: Well, re-installed drivers and rebooted. Now My Computer isn't recognizing the Kindle at all, and the tablet is displaying a USB Compatibility error and informing me that some computers require third-party software to interact with Kindles.... it's almost funny how every single thing seems to be going wrong for me.
EDIT2: After playing around with it some more, it seems that the PC will -ONLY- recognize the Kindle (and the Kindle will ONLY not give me the USB compatibility message) when I have the drivers that auto-install from the Kindle Fire itself... using the ADB drivers results in the opposite, and SR Tool does not recognize the Kindle in either case.
Okay, several installations and reboots later and I got the drivers working properly and was able to run the SR Tool.bat utility. I was able to run 1, 3 and 4 no problem, then hit 5 and during the reboot got stuck on the loading screen.
Did it again and just did 1 and then 2 and then ended with 6.
*BTW. the options were:
1. Enable Fastboot
2. Restore-su/Supersu.apk only
3. Restore-su/Supersu.apk, Apex Launcher, phonesky.apk/vending.apk
4. Erase cache and userdata
5. Install GoogleServicesFramework.apk
6. Reboot Normally
0. Exit
Once again, rebooting takes me to the loading screen and I stay there. It's quite frozen.
Since this utility is able to do fastboot, is there any way to just clear the whole system out--get rid of all the rooting stuff and return the Fire to its original unrooted form?
EDIT: the terminology I keep see used with the SRT is "flash the system," but what does that even mean? Which of those 5 options flashes the system?
Odd maybe this isn't the right utility, it was labled the same in the android developments all about the kindle fire HD 8.9" page, lemme see if I can find the right utility.
Edit: on second thought just use kffa, its more universal, and it does what you need. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
My kindle fire 2 rooted was working fine until I launched this program called GOLauncher. I didn't like it and tried to uninstall it, but the darn thing wouldn't remove and the the next time I turned on my kindle, all I would get was a flashing loading screen. Nothing else. I soon thereafter discovered (when the 1-step program I had previous successfully used about 10 times before) would go no further that daemon starting. I noticed that instead of a Kindle in my device manager, there was now only a Portable Device with E: showing as active.
I've tried every solution I could find from here, but 90% of them assume you have the whole driver .exe to install or some other such stuff. Every driver that doesn't, doesn't work for my computer, and won't put the kindle device back on my computer. So now, I have no way to communicate between my kindle and my computer, which I need to do frequently.
I've uninstalled each adb between installs, I've tried all the drivers I can find, I've deleted hidden devices (there were no kindles there either)
Plus, I can't get these apps I installed on the third party sites (which I miss) to uninstall. All they say is "move to favorites" in both my app folder and in the cloud. I am assuming it's because I no longer am able to access those sites.
Could someone please help me? I'm pretty computer literate, except where it comes to DOS commands. Sigh, the one thing I didn't learn in high school.
I promise I've been spent the last 5 days and nights (and even restored my device to factory settings just to get it to work) searching through so many pages of this site that I'm starting to get confused. Will someone please help me?
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
This is what happened. I installed a program from the Google Play store, wasn't happy with it, and botched the uninstallation. I was messing around on my computer to see how I could fix the problem (after just rooting hubby's kindle fire 2nd generation and discovering I had not ADB drivers and my device manager wasn't recognizing my requests). I notice that once again the kindle is missing on device manager when plugged in to the computer. What is showing up is a Portable Device labeled E:. So I go looking for answers here.
One of the things I noticed I could do with the broken kindle was that about 1 out of 5 times it was on, I could swipe the top of the screen and have the settings menu come up. And out 1 out of those 5 times, I could actually get a setting to appear by pressing on it. So I literally spent 17 hours trying to time the swipe, press, press to get the restore to factory settings program to work. And when it finished, I had a useable device, but all the kindle programs were gone (they were still on my cloud) and I could run all the programs installed from other android stores (but I can't uninstall them). And, of course, I can't get my computer to recognize the device. But I do have program called file manager that allows me access to shared files on my family's three computers so I can transfer files over the LAN if I need to.
I hope that helps. Thanks for taking the time to help me.
I am running an Intel i5 with 64-bit Windows 7 Home Premium Service Pack 1. It has all Microsoft updates and it is my pristine baby that I bought 18 months ago (my last computer was 9 years old that I built with an AMD processor and an 17 and 20 GB hard drives that were donated to me. It was a real POS, but it's still running to this day as a backup.
I know the feeling, before i got my new laptop from a friend a few weeks ago i had a pc with a pentium 4 and 2gb of ram, and like 3 hard drives. Anyways I'm assuming at this point you want to try restoring the system partition? Have you tried the drivers in my signature for adb access? If you can reboot into fastboot you could restore the system image from kindle fire first aid, should fix any problems with the os. It all depends on if USB debugging is turned on on your kindle, and if you can get the PC to detect it as such, usually I would just uninstall the MTP device and try searching for drivers on the new device detected and point it to my drivers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Have you tried a factory reset?
--》Sent from my mind to your screen
mindmajick said:
Have you tried a factory reset?
--》Sent from my mind to your screen
Click to expand...
Click to collapse
Thanks for both of your information. I did get the ADB drivers to show up - in the most stupid of ways. I changed from by brand new monster gold plated cable to a Wal-Mart special. Suddenly, everything worked perfectly! I use KFFirstAide to restore the device to the #1 setting, and then rooted it using the #23 setting. I also installed the Google Play store (though I installed the wrong, more complicated, version of if the first time.
Now I have a problem I can't see to fix. Ever since I got everything set up, there are certain programs on my kindle (cloud and device) that I can't get rid of. They are No Lock, Talk, News & Weather, Majic Locker, Google Voice, and Gl Launcher HD. I've tried downloading both ES Task and File Manager and deleting or startup disabling these apps, and while they say they are deleted, they reappear back on the active list as soon as I turn on my device (yes, I've rebooted), but I can't get them off my kindle Apps pages. And Go Launcher starts up every single time I turn on my device, and I hate this program, because it is not what I was looking for. Now I always have to look at it.
These .apk's are all in the system/apps folder. That's why I've tried to use the above file apps to get rid of them.
Also, my Silk browser doesn't work (I can open it and it immediately closes), and while I know I can download dolphin browser or firefox, I want the browser built for tablet speed and efficiency. Plus, when I had multiple browsers before, I always got the popup asking me which app I wanted to use to perform that function. But I can't find an apk for silk anywhere, and my device won't uninstall Silk.
Can anyone help? I feel so stupid about the cable issue. You wouldn't think a 3 day old cable would not properly transfer data.
OK to fix your launcher, go into the setting>apps and find go launcher and clear its defaults. That's kinda unspecific but I haven't been on amazon os for a while. To get rid of system apps, use es file explorer, enable root access, if on the older version, mount the system, if you have a panel on the left its the new version. Anyways from there you can simply hold down on the app and hit delete. Not too sure why silk isn't on the list. Though I though I might say consider this, you have no way of using flash with silk, so other browsers are kinda useful because you can. Then again I like flash. Kinda sounds like silk got deleted.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Not entirely true
stunts513 said:
OK lemme get this straight, you are stuck in a boot loop at the kindle logo and want adb access but nothing is showing up( except maybe a portable device)? If its showing up as a portable device during a boot loop that strikes me as odd, usually you don't have adb access during a bootloop , much less and mtp connection. If it's stuck in a boot loop you will typically need a fastboot cable to get out of it. Also what os are you running? I might be of more assistance after I get a better idea of what your kindle is doing exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have gotten several tablets to respond to ABD commands while soft bricked or not booting all the way. This is actually how I became an authorized MID repair facility. I have repaired a few kindle's that would only boot the to logo. If the device is loading as portable device, go to device manager, update driver for portable device, manually update the driver to whatever ADB driver you have extracted and it should at least respond to adb wipe command. once done you should be able to use the KFU to restore the tablet to factory state.
At least this is the process that has worked for me several times.