Related
I flashed the 6.3 update from TWRP and after reboot it gets stuck on kindle fire logo. I have tried Kindle Fire Unbrick Utility with no success. Whenever I choose an option on there, it says waiting for device. When I plug my kindle fire into my computer it makes the connecting noise. In kindle fire utility it shows that adb is online, but the boot status is shown as unknown. When i try to have it reboot into normal mode from kindle fire utility, I get exec '/system/bin/sh; failed : no such file or directory. Then the kindle fire resets itself and im back at square one.
I've uploaded a screenshot of what I get when I use kfu and try to get into fastboot
u were supposed to wipe data after flashing but before rebooting. what rom were you on before you flashed it? usbboot or factory cable.
Sent from my HTC Glacier using xda premium
I was rooted stock. Do you think I should order a factory cable?
yes. unless your comfortable removing the back cover.
Sent from my Kindle Fire using xda premium
If you type "adb devices do you see your kindle?
sent from my ever evolving kindle fire
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
chris_m128 said:
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
Click to expand...
Click to collapse
Personally I don't think it will show up in adb devices.but you don't need android sdk for adb.if you downloaded kfu then you have it.first look in kfu folder till you find adb.exe. then use the cd command and move into the folder with adb.then you can do adb devices.good luck bro.I've bricked 2 kindle fires and I still don't have enough money for a third.
Sent from my Droid using XDA
chris_m128 said:
when i type adb devices under command prompt I get that it's not a recognized command. I think that's because I never downloaded and installed the Android SDK. I've always just used kfu to root and install recovery.
Click to expand...
Click to collapse
like he said, but u can also navigate to the folder and do shift+control+right click and open cmd prompt. from there do adb devices
Sent from my Kindle Fire using xda premium
thank you!
when i type in adb devices after following your instructions I get a bunch of numbers, then they are followed by "device" I can post a screenshot if it will help
You said your computer makes a noise when u plug it in.. its not bricked. What does it show in device manager.
Sent from my Kindle Fire using Tapatalk
it shows android phone
chris_m128 said:
it shows android phone
Click to expand...
Click to collapse
Delete those drivers and run the driver pack from kfu. Then manually select the driver device manager. You have to choose adbcomposite device
You are not to bricked you only have the wrong driver
Sent from my ADR6425LVW using XDA
that's what's keeping my device from booting up?
chris_m128 said:
that's what's keeping my device from booting up?
Click to expand...
Click to collapse
No it is what is preventing you from fixing it
Sent from my ADR6425LVW using XDA
they are all wrong.
when u do adb devices and it shows numbers your golden.
do it again
then do
adb idme bootmode 4000
adb reboot
Sent from my HTC Glacier using xda premium
smirkis said:
they are all wrong.
when u do adb devices and it shows numbers your golden.
do it again
then do
adb idme bootmode 4000
adb reboot
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Well, I don't want to argue. I just know that for the 2 kindles that had the same problem as the OP, any adb command I sent just sat "waiting for device" It was not until I got the right driver (adb composite) that it started taking adb commands again.
if he can push a 4000 reboot without the driver, great. But if he is getting "waiting for device", as he stated in OP, then my suggestion is to get the right driver installed in there.
most soft bricks happen when the fire gets stuck in fastboot mode and loses connection via driver issues and fails to take adb commands.
chris_m128 said:
when i type in adb devices after following your instructions I get a bunch of numbers, then they are followed by "device" I can post a screenshot if it will help
Click to expand...
Click to collapse
but, this.
so, I don't wanna argue either. fastboot is one thing, but adb is another.
his waiting for devices in the op is from kfu, and if you know how it works, it chains a fastboot command and pings it at waiting for devices awaiting reboot. his adb works fine.
Sent from my Kindle Fire using xda premium
Sorry for hijacking your thread bro but im having the same problem. ADB is online but boot status is unknown. On top of that, its stuck at the kindle logo. Any help?
Ok, so im using KFU to root my Kindle.
I get it rooted, I get twrp and firefirefire installed, but when it trys to "Attempt to remove root checker"
It says:
mv: can't rena,e '/system/bin/check_rooted': No such file or directory
Then it trys to install Superuser.apk and I get this error: "Error: Could not access the package Manager. Is the system running?"
But I have root? Any ideas?
Download a file manager that lets you see system files like root explorer and see if the root check file is removed
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
You should also look in devices on windows and see what is showing up
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
yeah i know how to use adb, ive used it before for my Sprint Evo.
when i do adb devices, it shows a bunch of numbers
but in dev manager, it just shows it as a portable device.
Did you try to remove the file with adb
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
what would the command be?
and do i manually need to push the .apk?
Kfu says adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
I would do
adb shell. If this doesn't work your drivers might be messed up
mv /system/bin/check_rooted /system/bin/check_rooted.bak
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
Hmm, it kicked back a # sign. But I was able to install gapps? Weird.
# means the adb shell command worked now try the mv command
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
yeah i got it to work, and installed a rom, now it doesnt even show up on my computer anymore. It makes the sound when something connects, but nothing pops up.. Damn it.
Edit: Fixed it. Thx for the help.
Glad I could help
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
I'm using Kindle Fire HD 8.9 - 8.4.6 software version
I have looked at a few fixes like the stunt wallpaper fix 2.1
It seems like the file "/system/framework/framework-res.apk" has changed.
I extracted that file but can't find the same paths in it.
Anyone have some current info?
Thanks In Advance!
If you are trying to figure out how to manually fix it, the boolean path isn't viewable normally, u have to actually decompile the apk to see that file, not simply unzip it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
boolean path
stunts513 said:
If you are trying to figure out how to manually fix it, the boolean path isn't viewable normally, u have to actually decompile the apk to see that file, not simply unzip it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OK I decompiled It using Java
java -jar "apktool.jar" d framework-res.apk edit_source
And I now see the path
/edit_source/res/values/
Can I just edit "bools.xml" using a text editer
<bool name="disable_system_wallpapers">false</bool>
Pretty much, then u have to recompile the file and pull the resource.arsc file out of the new framework-res.apk, and stick in in the old one to update it while maintaining the signature in the file. My wallpaper fix does all this for you, but if you need some hints and want to do it manually, feel free to look through the batch file, I'm sure you would recognize the important parts as long as you have some basic command line knowledge.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
looped
stunts513 said:
Pretty much, then u have to recompile the file and pull the resource.arsc file out of the new framework-res.apk, and stick in in the old one to update it while maintaining the signature in the file. My wallpaper fix does all this for you, but if you need some hints and want to do it manually, feel free to look through the batch file, I'm sure you would recognize the important parts as long as you have some basic command line knowledge.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I you are in a loop at the red triangle screen
Is there a way to at least power the unit off?
Um hold down power? If you got into a red triangle screen, you will need a fastboot cable to restore the system in kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Factory Cable:
stunts513 said:
Um hold down power? If you got into a red triangle screen, you will need a fastboot cable to restore the system in kffa.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Where can I buy that cable? And what can you do with it that you can't do with the regular cable that came with the device?
Also If your device was set to have ADB disabled will you still be able to do anything using that cable?
My bad, disregard that last statement I forgot I am in the 8.9" forum. Its a lot more simple since your an 8.9" user, just turn kindle off, open a command prompt and CD into the directory where you have a copy of fastboot. Now type "fastboot -i 0x1949 getvar product", once it says waiting for device, plug you kindle in while its off, it should boot into fastboot, you will know from the screen saying fastboot in yellow letters. If that doesn't doesn't do many thing and it just hangs on waiting form device, then you need to install the drivers for the jem device that will show up in the device manager for a few seconds after the kindle turns on, use the drivers in my signature for this. Once the drivers are working try the process again and it should work. Sorry about the fastboot cable confusion, I suck at multitasking and was in between rounds of halo reach when I answered, and didn't notice that I was in the 8.9" section. Hope I posted this before you found them online and got one, because they are useless on the 8.9" models.
Another note, adb has nothing to do with fastboot mode, so it has no effect, on that note remember adb commands don't work in fastboot, you have to use fastboot commands.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Jem Device
stunts513 said:
My bad, disregard that last statement I forgot I am in the 8.9" forum. Its a lot more simple since your an 8.9" user, just turn kindle off, open a command prompt and CD into the directory where you have a copy of fastboot. Now type "fastboot -i 0x1949 getvar product", once it says waiting for device, plug you kindle in while its off, it should boot into fastboot, you will know from the screen saying fastboot in yellow letters. If that doesn't doesn't do many thing and it just hangs on waiting form device, then you need to install the drivers for the jem device that will show up in the device manager for a few seconds after the kindle turns on, use the drivers in my signature for this. Once the drivers are working try the process again and it should work. Sorry about the fastboot cable confusion, I suck at multitasking and was in between rounds of halo reach when I answered, and didn't notice that I was in the 8.9" section. Hope I posted this before you found them online and got one, because they are useless on the 8.9" models.
Another note, adb has nothing to do with fastboot mode, so it has no effect, on that note remember adb commands don't work in fastboot, you have to use fastboot commands.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Where can I find the right Jem Driver
It's in my signature...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Drivers:
stunts513 said:
It's in my signature...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
These will work for fastboot even if ADB isn't enabled on the device?
Yes, fastboot uses the same drivers as adb, just not the same command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Fastboot:
stunts513 said:
It's in my signature...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ok I got fastboot going using KFFirstAide64 loaded the alternative adb driver from that
after starting KFFirstAide I choice 9 which is fast boot status
and now am in fastboot
product: Jem-PVT-Prod-04
finished. total time: 0.003s
7EE400003C002FFF fastboot
What do I do now?
Tell it to restore your system, I don't know the exact choice number or what it says since I have never used it, but it should have an option somewhere to restore the system partition, I think I heard you can even choose which version, if you can I suggest one of the newest one available from the list.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
recovery images:
stunts513 said:
Tell it to restore your system, I don't know the exact choice number or what it says since I have never used it, but it should have an option somewhere to restore the system partition, I think I heard you can even choose which version, if you can I suggest one of the newest one available from the list.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Would you happen to have some 8.4.6 images?
KFFirstAide the latest version has 8.1.4
No I don't have the 8.9" model, but you could just let it update via ota after you restore it, or just restore it and follow the instructions on Amazon's website to manually update it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
After Update:
stunts513 said:
No I don't have the 8.9" model, but you could just let it update via ota after you restore it, or just restore it and follow the instructions on Amazon's website to manually update it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
OK after enabling OTA updates and then updating to the latest firmware version 8.4.6
I have lost super user access however in es explorer I can still access /
and /system and all that do I have to root it over again or just load superuser?
You need to root it again, u only have read only access to /system at the moment, and you have to have root to change that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to root it again, u only have read only access to /system at the moment, and you have to have root to change that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------------------------------------------
OK thanks rooted again all good and I am back
Now after all that do I attempt a wallpaper fix?
hahahahahaha
Wallpaper fix:
Lamere said:
-----------------------------------------------------------------------------------------------------------------------------------------------------
OK thanks rooted again all good and I am back
Now after all that do I attempt a wallpaper fix?
hahahahahaha
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------
OK wallpaper fix done and all is well
Now how do I find the actual images? and whats the best way to add a few of my own to the lock screen images?
Thanks in advance
I've really messed my KF2 up somehow. The Kindle Fire Utility reports that it's ADB Rooted, but my su binary is missing.
When I open Superuser, it reports that it needs to update the Su binary, but it fails.
127|[email protected]:/ # su
su
/system/bin/sh: su: not found​
Once the KF2 is rooted, I'm stuck on the sluggish blinking slow screen. I've fixed this a couple of times using "adb shell rm /data/local.prop", but once I try to re-root it the sluggish blinking screen comes back. I think this is a side effect of the missing su.
I believe I can hack this back together using a valid su binary. At this point, I'll be happy to get it back to a known good state so I can install the latest cyanogenmod. I need to fix the root so I can install TWRP, right?
Any suggestions would be helpful!
Doug
If your shell says root then u should be able to put su on your sdcard then cup it over to xbins and set its permissions with chmod. BTW be careful of kfu on a kf2, it will hard brick it if you use it to install a boot loader.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
If your shell says root then u should be able to put su on your sdcard then cup it over to xbins and set its permissions with chmod. BTW be careful of kfu on a kf2, it will hard brick it if you use it to install a boot loader.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I'm unsure where I should get the su binary from, I'm sure that once I have it, I can push it up using adb.
Doug
I think the file is included in binary's root.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I think the file is included in binary's root.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I appreciate your help, but I don't quite understand.
I've looked in the Superuser.apk file, and used find in the adb shell and do not see it anywhere.
Doug
DougWare said:
I appreciate your help, but I don't quite understand.
I've looked in the Superuser.apk file, and used find in the adb shell and do not see it anywhere.
Doug
Click to expand...
Click to collapse
I found it, now I'll try to fix my Kindle.
Thanks!
Doug
Hey All!
I had a nice post written up, but XDA decided that it didn't like me and signed me out while I was writing so it's gone now... in any case....
My problem is this: I have set up my linux machine to do adb/fastboot and I'm fairly certain that there's nothing wrong with it on that front. I have no problem with adb, I use shell and then change the bootmode to 4002 and then quickly send a fastboot command to attempt to catch it before it loads FFF. I have FFFv.1.4a which I believe is still the newest version but I want to flash a newer version of TWRP (currently on 2.1.1). I tried using the flashable zip on HashCode's CM11 thread, but it doesn't seem to be making any change (if there's a special way to flash a recovery via recovery I would appreciate any advice) but at this point I'm stuck because I don't remember needing the factory cable to get to the point that I'm at but I don't know of any other way to enable fastboot mode. Is there a way that I can do this without the factory cable? I have one at home, but not with me at school
Thanks in advance,
Sparkplug
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It appears that even though I'm running MoDaCo, I'm no longer rooted. Very odd.... Perhaps that has something to do with my weird situation. I'll try rooting and report back!
stunts513 said:
In twrp hit reboot then hit boot loader, or use and adb shell or mobile terminal and run "su -c 'reboot bootloader'", those are some of the alternate ways to enter fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I should have been more clear. I have no trouble getting to FFF and having it stay there as though it is waiting for commands, but my computer just continues to say <waiting for device>
Does that mean that I'm doing something wrong or do I just need to use the factory cable and that's the beginning and the end of it?
I'm mainly from the 2nd gen kindles and was a little bored so I ventured into the 1st gen forums... But if you are saying that its going into fastboot mode, but you PC can't issue commands then I would guess it's a driver problem, last I checked my drivers in my signature also work with 1st gen kindles. I thought fastboot had its own screen outside of FFF, but if it doesn't then check your device manager for a device with a triangle next to it, I'm guessing it will say otter, like I said though 1st gen kindles aren't my forte but they are similar in certain aspects.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I'm mainly from the 2nd gen kindles and was a little bored so I ventured into the 1st gen forums... But if you are saying that its going into fastboot mode, but you PC can't issue commands then I would guess it's a driver problem, last I checked my drivers in my signature also work with 1st gen kindles. I thought fastboot had its own screen outside of FFF, but if it doesn't then check your device manager for a device with a triangle next to it, I'm guessing it will say otter, like I said though 1st gen kindles aren't my forte but they are similar in certain aspects.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I think that it is supposed to have a separate screen but I wound up doing what I forgot existed because I'm so used to doing everything manually; using ROM Installer by JRummy to flash the image after I had rerooted. I appreciate the help either way!