I have rooted a few phones and even two kindle fires but I messed up my fathers.. Rooting went fine, I was able to install the google framework and vending.apk.
On reboot kindle fire logo kept repeating.
Where I think I went wrong wrong was changing the permissions on vending.apk I might have changed permission on system/apps.. I ran the unbrick application but didn't know what the right issue so I ended up going a little hog wild trying "stuck at logo", "recovery" and "modded system/application"
now it only boots to press power for recovery page.
It is correct that I need to get adb shell working to have a shot here? I decided (a little to late) to slow it down but the shell didn't seem to be working at the point I stopped..
the kf is in fastboot mode - adb ist'n working in this mode
what tells your device manager? it should be "android adb interface" under "android phones" - if not update your drivers
then you can issue:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
if it says <waiting for device> to the first command let the command open and power off the kf by holding pwr button ~20sec - power on again - the command should be picked up and finished - pwr off/on again
Thanks... Will try this in a few hours when I get home
Thanks... After that I was able to get the ADB shell and find the issue with my permissions...
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Related
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Do you have fastboot access? Try running the following...
fastboot -i 0x1949 oem idme bootmode 4000
Try this: http://forum.xda-developers.com/showthread.php?t=1422832
Thanks guys, ill try those and post back w the results.
so i tried fastboot -i 0x1949 oem idme bootmode 4000
and it seems to have been successful, in that it is now back to its original boot loop state. however, it is still not booting fully.
it seems that adb commands are now working, i can do adb shell, and navigate root folders (system etc).
zombie, i havent had much luck with that route, i had tried that earlier.
I've seen people mentioning that the cause for their brick had something to do with permissions, so i did ls -l in the adb shell, here are the permissions for some of the relevant folders. if there are any others that might be helpful, let me know.
root -> drwx------
system -> drwxr-xr-x
sdcard -> lrwxrwxrwx
oh and framework-res.apk -> -rw-r--r-- (same as all other files in that directory)
i did modify the framework-res to change the background image. it successfully booted at least once after the modification - i used metamorph, i loaded the file, then rebooted for it to take effect. this was successful, but i believe it was the next reboot which did my kindle in, so possibly related.
i rambled a bit, but maybe if i replaced the current framework-res.apk with the stock framework-res.apk, that might be worth trying? are all stock framework-res.apk files the same at stock? because i don't have a copy of the original that came with my kindle.
i would go back into fastboot and then flash over TWRP... and then reinstall your os from scratch. it would probably be easier than trying to root around fixing it from the inside.
Thanks xrishox, I might do that. Is there a thread detailing how to do that?
When I tried doing fastboot I lost the ability to use adb commands so I'm not sure how to go about flashing twrp.
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
jackofaiitrades said:
Hello all,
I've got a bricked droid, and haven't been able to find a fix that worked in other threads here.
I rooted my droid successfully, and installed GO Launcher EX, along with the android market, and a number of apps from there.
Among those, busybox, metamorph (which i then used to change the wallpaper), titanium backup, etc. I had successfully rebooted after all these installations and after changing the wallpaper.
I was getting on a plane the other day and turned off the KF, and havent been able to get it to boot since.
Originally it was in a boot loop, getting to the kindle fire icon and rebooting every 3 seconds.
I tried using the KFU, but it was unsuccessful at changing the boot mode (drivers were successfully installed).
Failing at that, i tried following the instructions in http://forum.xda-developers.com/showthread.php?t=1414832
After the reboot, it is now just stuck in the kindle fire screen, and i cant run any adb commands, device not found.
Am I straight up screwed now? or anything I might be able to do at this point.
Much appreciated, thanks for any advice.
Click to expand...
Click to collapse
Howdy!
I recently just dealt with this same issue. My KF was stuck in boot loop and wouldn't be recognized by my computer. I left it in bootloop until it ran out of battery. Once it was completely drained, I connected it to my computer and my computer recognized it, I then reinstalled the drivers. Right after that I used KFU to change bootmode to normal boot and let it fully charge! Good to go! Hope this helps someone.
from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and here is a note from vashypooh - the op of kfu
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
maybe it helps someone ...
Thanks guys, I won't be near a computer until tonight but will try these out as soon as I get back
lmntone said:
Download the fbmode binary and TWRP image. Then run the following.
Code:
adb push fbmode /data/local/temp
adb shell /data/local/tmp/fbmode
arbiter reboot
Your device should reboot and be stuck on the Kindle bootscreen. You are currently in fastboot mode. Now run the following...
Code:
fastboot -i 0x1949 poem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.image
Your device will reboot after that last command. It will boot into the TWRP installer. When it completes, tap "Reboot". Then boot into TWRP recovery and install the factory update, or a custom image that won't replace FireFireFire and TWRP.
Click to expand...
Click to collapse
Tone you're a life saver, thanks. I'm up and good to go.
good that it's working again !
have you seen this one in the dev section - could save a lot of handwork:
http://forum.xda-developers.com/showthread.php?t=1428428
Also, when I get back to my computer again, ill update my OP to include the solution so that others might benefit. its like a 20 minute fix but took me days to resolve it (largely due to lack of comp access but that's beside the point).
I just overall screwed up big time with this thing. I rooted 6.2.1, then uninstalled/froze a bunch of the stock apps (including the default Kindle launcher, as I had Go Launcher installed).
I then decided I wanted to restore to the factory default settings, as I wanted to use Amazon prime, among other things. I went into settings and hit the "restore to factory defaults button" (which was stupid, I know). Unsurprisingly, this resulted in Kindle Fire bootloops.
Trying to fix this, I used the KindleFireTool to install the most recent TWRP...which didn't work at all. It would just stay on the yellow triangle screen. Now, things have gotten even worse, though I don't know why. Whenever I plug the fire into the computer, it goes into TWRP bootloops!
For the brief few seconds that the Fire is on when plugged into my computer, the driver isn't recognized at all (shows up as "kindle" with a triangle next to it in device manager).
I know what I did was dumb, but even so, any help would be hugely appreciated.
YES YES YES!!!! OK HERES HOW I DID IT TO FIX THE BOOTLOOP OF TWRP
First you must download Kindle Fire Utility and extract it to your desktop
then go to command prompt or cmd then type in the location of the folder heres mine for example: C:\Users\Madaran\Desktop\Kindle Fire Utility\tools
then type in fastboot -i 0x1949 oem idme bootmode 4000
For me it said waiting for device all I did is rebooted the device and it worked
as the device reboot it will still go back to TWRP now type this in the command prompt
fastboot -i 0x1949 oem idme bootmode 4000
then it should reboot again and ITS FIXED
----------------------------------
I used this thread to fix it.
http://forum.xda-developers.com/showthread.php?t=1428715
Thank you so much! I'll post results when I get the opportunity.
Well it didn't work...the thing isn't connecting to the computer properly. I think it's a goner.
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
skippwhy said:
I did all of that up until step 6. My device won't allow me to reboot. When it's plugged in via USB, it boots up, dies within 20 seconds, then boots again. I can't break the cycle, and it just says waiting for device on and on...
Click to expand...
Click to collapse
It maybe your battery its low. Try to charge it and connect it again.
Definitely worth a shot
You were right! It was a battery issue
sirmavs said:
Mine didn't connect also but it still worked. You don't need the device to be connected just plug it in and put it in the TWRP recover mode. Then do the steps again.
1.Download Kindle Fire Utility
2.Extract it to desktop.
3.You can't connect it while its in FastBoot mode so open up CMD or Command Prompt.
4.Again locate the folder and type it in the CMD for example I typed:
"cd C:\Users\Madaran\Desktop\Kindle Fire Utility\tools"
5.Then type this in "fastboot -i 0x1949 oem idme bootmode 4000"
6.It should say waiting for device. Go to TWRP and hit reboot system.
7.It should work now and while waiting for your Kindle to boot up, the power button should be orange.
8.When it turned orange I immediately typed this in the CMD or Command Prompt
"fastboot -i 0x1949 oem idme bootmode 4000" so it wouldn't boot to the TWRP recovery menu.
9.It should reboot again and load up your CyanogenMod 7
10. If it work hit the thanks button please.
Click to expand...
Click to collapse
Hey guys... I kinda bricked my Kindle... I tried all the steps mentioned above. My Kindle boots but it freezes on the Kindle Fire Boot Screen. It does not load the home screen of Kindle with Shelf.
Please help
http://forum.xda-developers.com/showthread.php?t=1428428
As a disclaimer, I've searched for this question, but have only found when the question is asked as a much broader topic and goes unanswered.
That being said, I can't seem to get TWRP 2.0 installed through using "fastboot boot", the Kindle Fire Utility, or the technique using dd to rewrite the contents of the parttitions.
The closest I've come is getting FIREFIREFIRE to start up using the "dd" technique, but TWRP still will not start when I hit the power button for recovery. And yes, I did use "dd" on the TWRP image file as well.
Also, I even tried using fastboot to flash u-boot.bin onto the bootloader partition, and twrp onto the recovery partition. Still, I can get to the yellow, but no further into starting TWRP.
Any help would be appreciated. At current time, I have the stock bootloader and recovery partitions on the Fire and it is rooted.
Thanks.
maybe your in fastboot mode and hopefully your drivers are installed correctly you can use:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot
this should bring you to normal bootmode
I've tried that in case there was an issue. In fact, if I don't press the power button during the yellow triangle, the Kindle Fire OS will start as normal after 10-15 seconds. So, it looks like the bootloader is working right and I'm in the correct bootmode. But, if I hold down the power on the yellow triangle (which is supposed to start TWRP), I just get stuck and nothing starts.
That being said, I think I'm in the correct bootmode.
if i don't remember wrong there is an issue with installing twrp with dd
i think you could retry the installation or simply use KFU (but don't use the drivers of kfu if you have working ones)
Thanks.. I'll give it another shot tonight, and then.
when the device starts and the Triangle appears, are you just pressing the power button once? or are you pressing it until it turns orange?
I have to press it a few times before it changes color to orange and then just let it alone. A long press doesn't work for me.
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
not possible - had the same - rooted with superoneclick on 6.2 then updated
i think your twrp install failed - would retry
I finally figured out my problem. For whatever reason (which is still unknown to me), the Kindle Fire Utility was not able to properly download the twrp.img. The file that was downloaded was 8K (which I'm guessing was some sort of error web page). Anyway, I went straight to teamw.in and downloaded the latest version that clocked in at around 10MB, installed it via the "fastboot -i 0x1949 boot twrp.img" command and all is well now.
If anybody is having similar problems, you might want to check the size of the twrp.img file. 10M = good, 8K = bad.
vaporofnuance said:
I can get it to turn orange. I think the long press worked for me on that one. Though, I do know I did the multiple presses as well and didn't get any further.
Is it possible that it might be goofed up because I used SuperOneClick for the original root on 6.2 instead of KFU?
Click to expand...
Click to collapse
It turns orange the second it starts booting recovery. That's when you should let go. Holding the power button for ~30 seconds for any reason is a hard signal to the PMIC chip to power off.
good that it works again ...
please mark the subject of the topic (edit first post) to [Solved]
I just did a restore setting in the CM7 option after that I cannot boot into the CM7 but only the TWRP...
Can anyone tell me how to reinstall the TWRP...
I tried to use the kindle fire utility to re-install it, however it doesn't connect...
always shows offline..
please help
thanks
Did you restore bootloader, recovery and system from your backup using TWRP? If so you should have TWRP installed.
Please provide detail info what you have done to give further help.
You may need to update your USB diver to get adb working and to be able to install recovery software.
Sent from my Amazon Kindle Fire using Tapatalk
i think you said boot to recovery in cm7 - now you'r in a recovery bootloop - means it boots allways to recovery by itself - right ?
if so (if it is booted to twrp) use kfu option1 - bootmode normal
or issue manually:
adb shell idme bootmode 4000
adb reboot
an other method is to use fastboot commands:
fastboot oem idme bootmode 4000
fastboot reboot
in the case it says <waiting for device> power it off by holding the pwr button for ~20sec till it turns of - pwr on again - the command should resume and finish
a second pwr off/on will bring you back to normal
if commands don't work check your drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Can anyone tell me what the befits are to running cm7 vs a lunched like adw ion the fire?
I tried to root my kindle through, http://forum.xda-developers.com/showthread.php?p=24128777 , but I got half way and got stuck at the fastboot mode. I don't have recovery or anything because it was a stock 6.3 kindle fire. Does anybody know how to get out of this? The adb isn't recognizing my device right now and I've tried hard resetting.
Any help would be appreciated!
Edit: Is the only way out of this is through a factory cable?
what means got half way ?
you switch to fastboot at a point - then adb commands are not recognized
only fastboot commands are recognized in fastboot mode
would try to issue:
fastboot -i 0x1949 getvar product - it should return "kindle"
if not check your drivers
if you got the drivers working resume with the above manual
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Oh. Is that it? . So is it normal for the cmd command "adb devices" to not show the kindle device?
If so, that's a pretty big relief! And all I need to do is type that cmd?
you have a great manual here explaining how the kf works:
http://forum.xda-developers.com/showthread.php?t=1552547
furthermore this one could help you to understand how drivers/bootmode/commands correlate:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
I'm having a similar problem. I can boot into fastmode but when I try to reboot, it just seems to hang with a <waiting for device> message. I get the same <waiting for device> message if I do the fastboot -i 0x1949 getvar product command.
I am stuck in TWRP and if I hit reboot, the command prompt does return the info.
OK, it appears that the KF didn't update. It was just stuck in some weird boot loop or something. Maybe it was trying to update and couldn't for some reason? I am keeping all this info bookmarked in case something does happen though.