Related
Dear all,
Please be patient with me on this.
I have tried using Kindle Fire Utility 0.9.6 to run Option 2 (Install Permanent Root with Superuser)
After installing for a short while, my KF was on TWRP boot screen.
[/LIST]So I thought it was done without checking the DOS Command I disconnected the device and reconnected and tried to mount and wipe factory reset and stuff to install a new ROM
(As I was composing this, I recall that there was that has something to do with Root Checker Please Wait ... )
[/LIST]Right now, no matter what how many times I wipe or clear, whenever I install a ROM, my boot screen will be the blue KF logo and it will automatically boot into TWRP.
I was wondering if someone please lend me a helping hand in resolving this issue.
Regards
MrKD
have you installed firefirefire? That has saved me tons of trouble.
Josepho1997 said:
Did you try:
Code:
adb shell idme bootmode 4000
Click to expand...
Click to collapse
Hi Josepho1997,
Yes, I have tried to boot in 4000, 4002 and 5001 but to no avail.
Whenever I try to boot it, it tells me that the drive cannot be located (Exact word - All my ADB USB interface drivers are all working as my ADB status is Online but my Boot Status is Unknown)
montypy323 said:
have you installed firefirefire? That has saved me tons of trouble.
Click to expand...
Click to collapse
Hi Montypy,
I will probably try to install FireFireFire later when I am home and provide a feedback to you if it works.
Thanks for the tip!
You need to forget about KFU and use FFF1.4 (blue Kindle Fire logo) for what it was designed. Hold the power button until "Reset bootmode" is hi-lighted at the bottom of the screen and release. Just don't hold it too long or you will shut it off.
soupmagnet said:
You need to forget about KFU and use FFF1.4 (blue Kindle Fire logo) for what it was designed. Hold the power button until "Reset bootmode" is hi-lighted at the bottom of the screen and release. Just don't hold it too long or you will shut it off.
Click to expand...
Click to collapse
Hi SoupMagnet,
I realized what was the problem: Whenever I see the blue KF logo, the next thing it does is to boot to TWRP
So after you have enlightened me, I have managed to boot into the ACTUAL ROM instead of the TWRP interface.
That was because it was set to default boot into Recovery (For some reason)
I never realized that only such small move can fix my nightmare (Literally I could not stop worrying before I went to bed last night.
Kudos to you, you deserve my most heartfelt thanks.
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
lob455 said:
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.
KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).
I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.
The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.
Thanks,
lob455
Click to expand...
Click to collapse
Does it show up in Device manager? as kindle, android phone, or something else...?
sd_shadow said:
Does it show up in Device manager? as kindle, android phone, or something else...?
Click to expand...
Click to collapse
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
lob455 said:
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).
On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
Click to expand...
Click to collapse
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Thepooch said:
Fairly certain your battery is dead http://forum.xda-developers.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
Click to expand...
Click to collapse
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
lob455 said:
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.
Okay. Here is where the weird part starts.....
After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.
So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.
However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.
Please let me know if you have any recommendations.
Thanks again.
Click to expand...
Click to collapse
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Thepooch said:
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.
Code:
adb push rom.zip/sdcard/
shift plus right click on kfu's tool folder select open command window here. Type
Code:
adb devices
you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.
Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. @sd_shadow 's Rom would be perfect for first flash.
Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
Click to expand...
Click to collapse
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
lob455 said:
Thanks @Thepooch for the detailed reply.
I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:
1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.
2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).
I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.
Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
Click to expand...
Click to collapse
Android adb interface alone is a detection of fastboot composite is normal boot. This could be due to a partially broken shell try while the device is in recovery not at the bootloader your bootmode is iffy.
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x http://techerrata.com/browse/twrp2/blaze
sd_shadow said:
What is current Twrp versiom? 2.7.1.0?
If the problem is Kindle software, a could try a couple of things
adb commands should not work in bootloader mode
fastboot commands should work in bootloader mode
try
fastboot devices
if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x ..................
Click to expand...
Click to collapse
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
lob455 said:
Thanks @sd_shadow for the reply.
In recovery mode, TWRP reports that it is version 2.6.3.1
I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.
If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
Click to expand...
Click to collapse
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.
sd_shadow said:
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.
the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)
or try the reboot command
fastboot reboot
Click to expand...
Click to collapse
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Just place a Rom on your Sdcard and flash it.
lob455 said:
@sd_shadow -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.
My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
Click to expand...
Click to collapse
Try the mount option in twrp again
sd_shadow said:
Try the mount option in twrp again
Click to expand...
Click to collapse
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck
lob455 said:
@sd_shadow @Thepooch
Thanks both of you for your help. But not all stories have a happy ending.
Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.
I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.
At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
Click to expand...
Click to collapse
I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.
I have the firetv rooted with xposed running and the xbmc launcher running. I tried to upgrade to beta xbmc 14 nightly but it did not work. So I then tried to uninstall xbmc fully with adb. Now my firetv will boot to the firetv animation screen and then go to black screen with the error: Acitivy org.xbmc.xbmc splash screen not found. I have tried to reinstall xbmc 13.1 for adb but it will not go thru. I've tried killing xbmclauncher (se.blunden.xbmclauncher.apk) with no luck. Tried to uninstall Xposed with no luck. I can connect to my firetv thru adb and can create a su adb shell, but can't get anything to work through adb. Please help this fool!
apazrjon said:
I have the firetv rooted with xposed running and the xbmc launcher running. I tried to upgrade to beta xbmc 14 nightly but it did not work. So I then tried to uninstall xbmc fully with adb. Now my firetv will boot to the firetv animation screen and then go to black screen with the error: Acitivy org.xbmc.xbmc splash screen not found. I have tried to reinstall xbmc 13.1 for adb but it will not go thru. I've tried killing xbmclauncher (se.blunden.xbmclauncher.apk) with no luck. Tried to uninstall Xposed with no luck. I can connect to my firetv thru adb and can create a su adb shell, but can't get anything to work through adb. Please help this fool!
Click to expand...
Click to collapse
i recommend a factory reset
If you have got to the point of desperation and no other help is forthcoming. I ran through this guide when I had an issue and it restored my AFTV.
It won't let me post the link. So have a look on firetvnews .com and you should see a way to restore the AFTV. Or read below, I just copied it:
If you’ve managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV’s operating system.
To do this you will need a USB keyboard with a “Print Screen” or “SysRq” key. Mac keyboards generally do not have this key so will not work. Before you get started, plug the USB keyboard into the Fire TV and unplug the Fire TV’s power. Now plug the power in and while the Fire TV is booting, you need to press the following 3 keys simultaneously: Alt + Print Screen + i
Pressing those 3 keys sends a “kill all tasks” command to the Fire TV. If you kill all tasks during boot up enough times, the Fire TV will enter Recovery Mode. So after pressing Alt + Print Screen + i, the Fire TV will flicker and restart the boot up process. While it’s trying to boot up a second time, press Alt + Print Screen + i again. Repeat this process several times until the Fire TV displays the message “The System Update was not successful.” When you see this message, you are now in Recovery Mode.
If you are having trouble getting into Recovery Mode, a good time to press Alt + Print Screen + i is as soon as you see the colorful boot animation. Pressing Alt + Print Screen + i should cause the screen to go black and the boot animation to restart. Press Alt + Print Screen + i every time the boot animation restarts. After 4 or 5 restarts, you should see a white Amazon logo followed by the “Update was not successful” screen. You can also try holding Alt + Print Screen + i through out the entire initial boot up process.
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Yeah I've seen that factory reset method. I am almost at that point! I have a wireless k400, but it doesn't seem to work. I just need to get my hands on a wired keyboard. I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
apazrjon said:
Yeah I've seen that factory reset method. I am almost at that point! I have a wireless k400, but it doesn't seem to work. I just need to get my hands on a wired keyboard. I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
Click to expand...
Click to collapse
I would use command "adb shell pm list packages -f" that way you can see what apps are installed on the Fire TV and exact package name.....
Next uninstall with "adb uninstall com.amazon.app.name" (no directory or .apk specification needed)
I was playing with some Xposed mods yesterday and locked the fire TV up as well, uninstalling mod fixed it. (Xposed Additions Module)
apazrjon said:
I was hoping there may be some better adb commands to accomplish removing xposed and xbmc launcher, but I guess probably not. Time to get a wired keyboard! Thanks for the quick responses! Cheers!
Click to expand...
Click to collapse
Only thing I can think of is to try an adb install of xbmc with the -r flag set, then an uninstall of Xposed before uninstalling XBMC. The -r should force a reinstall and get you back to a useable interface but otherwise, yep, sounds like a reset'll be required.
roustabout said:
Only thing I can think of is to try an adb install of xbmc with the -r flag set, then an uninstall of Xposed before uninstalling XBMC. The -r should force a reinstall and get you back to a useable interface but otherwise, yep, sounds like a reset'll be required.
Click to expand...
Click to collapse
If adb is working, adb reboot recovery should get you into recovery so you can do the factory reset.
reboot recovery does get me into the update download page but no buttons on my remote or my wireless k400 seem to get me to recovery for factory reset. Any thoughts?
apazrjon said:
reboot recovery does get me into the update download page but no buttons on my remote or my wireless k400 seem to get me to recovery for factory reset. Any thoughts?
Click to expand...
Click to collapse
Did you already uninstall all Xposed modules and the Xposed framework ?
trying that next. It seems that adb will only work right after I reboot for some reason. Going to try again right now.
Just went ahead and got a $10 usb keyboard from walmart. Still couldn't get the home button to work for getting my into recovery. Then i decided to press shift + home and it worked. I don't know if it was the key combo or just good timing with the home button. Who knows. Back to factory now! Time to rebuild. Everything was set up perfect! Just couldn't leave well enough alone, lol! Thanks for all the help. My adb would only work for one time at a time and wouldn't uninstal anything. Cheers!
deleted content ..
sorry ., didn't notice I would have been duplicating what others already posted ....
rbox said:
If adb is working, adb reboot recovery should get you into recovery so you can do the factory reset.
Click to expand...
Click to collapse
Sorry, meant "only command flag in ADB you might try before going for a full restore"
I thought the OPs core problem was that xposed was telling his system to use a nonexistent app as the launcher, and he wasn't able to get the app back in even for long enough to uninstall Xposed, reboot, and then uninstall XBMC.
Smithy71 said:
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Click to expand...
Click to collapse
I've got a gray screen and can't get rid of it. I'm rooted and have elmerohueso's Launcher installed. All has been working perfect until the other night when I got a "low memory" pop up with a request to uninstall some apps. After that, the screen grayed and that was that. I've gotten to the“Update was not successful” screen but cannot get the menu to show up. I'm using a usb keyboard and have tried home, shift + home, and every other combo I can think of but the menu will not show up.
Anyone have another suggestion?
When you are on the update unsuccessful screen, press alt + sys rq + i to reboot back to the update screen again and then press home to bring up recovery menu. That's what I did on my keyboard
Smithy71 said:
If you have got to the point of desperation and no other help is forthcoming. I ran through this guide when I had an issue and it restored my AFTV.
It won't let me post the link. So have a look on firetvnews .com and you should see a way to restore the AFTV. Or read below, I just copied it:
If you’ve managed to brick your Fire TV or for whatever reason are unable to get to the settings menu to perform a factory reset, here is how to enter recovery mode without fully booting into the Fire TV’s operating system.
To do this you will need a USB keyboard with a “Print Screen” or “SysRq” key. Mac keyboards generally do not have this key so will not work. Before you get started, plug the USB keyboard into the Fire TV and unplug the Fire TV’s power. Now plug the power in and while the Fire TV is booting, you need to press the following 3 keys simultaneously: Alt + Print Screen + i
Pressing those 3 keys sends a “kill all tasks” command to the Fire TV. If you kill all tasks during boot up enough times, the Fire TV will enter Recovery Mode. So after pressing Alt + Print Screen + i, the Fire TV will flicker and restart the boot up process. While it’s trying to boot up a second time, press Alt + Print Screen + i again. Repeat this process several times until the Fire TV displays the message “The System Update was not successful.” When you see this message, you are now in Recovery Mode.
If you are having trouble getting into Recovery Mode, a good time to press Alt + Print Screen + i is as soon as you see the colorful boot animation. Pressing Alt + Print Screen + i should cause the screen to go black and the boot animation to restart. Press Alt + Print Screen + i every time the boot animation restarts. After 4 or 5 restarts, you should see a white Amazon logo followed by the “Update was not successful” screen. You can also try holding Alt + Print Screen + i through out the entire initial boot up process.
Once on the “Update was not successful” screen, press the Home key on your keyboard. This should bring up a menu in the upper left corner. Use the arrow keys to highlight the factory reset option and hit enter.
Click to expand...
Click to collapse
how to connect usb keyboard same time usb power? fire tv have no usb port
roy0175 said:
how to connect usb keyboard same time usb power? fire tv have no usb port
Click to expand...
Click to collapse
OTG Y Cable! It's an OTG cable that can also deliver power to the FireTV while you are using it with a mouse, keyboard, etc...
Hi,
I think I have bricked my Fire TV stick in a weird way.
I tried to root it using this tutorial:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
I managed to get root and su command working (used the chinese PC version of KingRoot, worked on the 3rd attempt). Next, on step 10, "Install TWRP custom recovery by running the command:sh /data/media/0/montoya_recovery_v1.zip" I stopped, because the adb shell showed the message "device read only or busy" or something similar.
I decided to eject the device and reboot it to try again. After this, the device boots into a splashscreen (Teamwin Recovery Project 3.0.0.7) where I have the choice to press left to boot normally and right to launch recovery. There also is a timer that after 5 seconds will boot into the selected choice.
The problem is that the remote left or right are not working and I cannot choose anything. After 5 seconds (the default choice is boot normally so it should work ok) the device boots into an amazon splashscreen and remains this way.
When I connect it to the computer via usb cable and start adb it recognizes the device, but only on the period that the 5 second timer runs. And some weird characters appear, SU is not working. The reboot command works in adb, but not much use. Also, if I list the adb devices, the serial number appears followed by "Recovery".
I tried plugging it into a normal charger (i do not have the genuine amazon one anymore) and no luck.
I have attached pictures of what appears on the tv with the connected device and on the command prompt console.
Thank you in advance!
b3cks89 said:
Hi,
I think I have bricked my Fire TV stick in a weird way.
I tried to root it using this tutorial:
http://www.aftvnews.com/how-to-inst...d-an-initial-rom-on-a-rooted-fire-tv-stick-1/
I managed to get root and su command working (used the chinese PC version of KingRoot, worked on the 3rd attempt). Next, on step 10, "Install TWRP custom recovery by running the command:sh /data/media/0/montoya_recovery_v1.zip" I stopped, because the adb shell showed the message "device read only or busy" or something similar.
I decided to eject the device and reboot it to try again. After this, the device boots into a splashscreen (Teamwin Recovery Project 3.0.0.7) where I have the choice to press left to boot normally and right to launch recovery. There also is a timer that after 5 seconds will boot into the selected choice.
The problem is that the remote left or right are not working and I cannot choose anything. After 5 seconds (the default choice is boot normally so it should work ok) the device boots into an amazon splashscreen and remains this way.
When I connect it to the computer via usb cable and start adb it recognizes the device, but only on the period that the 5 second timer runs. And some weird characters appear, SU is not working. The reboot command works in adb, but not much use. Also, if I list the adb devices, the serial number appears followed by "Recovery".
I tried plugging it into a normal charger (i do not have the genuine amazon one anymore) and no luck.
I have attached pictures of what appears on the tv with the connected device and on the command prompt console.
Thank you in advance!
Click to expand...
Click to collapse
While the stick is plugged into your computer and it boots to the TWRP selection screen in your ADB / command terminal (with the weird character's you see) using your keyboard type in mouse.
Then use press d then enter. This will highlight recovery and allow you to boot into recovery. You use key presses on your keyboard to navigate in TWRP.
While your in recovery and if you have not pushed the previous rooted zip over do this now.
Make sure you read exactly what your next steps are very close on how to proceed with flashing a pre rooted rom.
If you make a mistake doing this you will brick your stick.
What he said. Welcome to rooting FTV sticks...
Michajin said:
What he said. Welcome to rooting FTV sticks...
Click to expand...
Click to collapse
It worked, my stick is now up and going. Thank you very much, you are a genius!
:highfive:
Hey I got a question. Which fireOS version was on your stick while rooting it? Because I can't wait for a rooting method for 5.2.1.1
Pottkopp said:
Hey I got a question. Which fireOS version was on your stick while rooting it? Because I can't wait for a rooting method for 5.2.1.1
Click to expand...
Click to collapse
I think many of us updated to 5.0.5 and stayed there when news of root methods hit.
Yep. I missed that point and looked for any progress on rooting when my stick already updated itself to 5.2.1.1... But now I won't let it update anymore. Hopefully someone will find a new method soon.
Sorry for the late reply. 5.0.5. is my version
Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
you need a usb keyboard and then you need to press a combination shown on youtube: , Don't be afraid it is very hard to do it but i can confirm it works 100% for sure!! The timing for holding the key press is all that matters to be successfully...
Try different timings if it's not working on the first run but you need then to hold the buttons for very long time until your fingers feel dead....
..im not sure if adb is working in "safe mode" you need to test that. If yes - you could use "adb reboot recovery".
2. you need to reflash Magisk in core mode.
Aq
dougie175 said:
Sorry if this is posted in the wrong section, I am never quite sure where these sort of queries should go
To cut a long story short I unlocked and rooted 1 of my FTV 4K sticks, I was struggling with an issue on 1 and ended up installing a Magisk update. I know there are warning all over the forum about this please put it down to a lack of experience.
On reboot it just comes up with the black screen and the white amazon logo, it stays on this for about 2 minutes then restarts to the same black screen. i.e. its caught in a boot loop. It never gets to the white amazon screen.
I bought myself an OTG cable thinking this would get me to twrp so I could go into recovery and wipe it and start again or something, but even with the OTG cable plugged in it still does exactly the same thing. I have tried the same OTG cable and entertainment keyboard setup on another FTV 4K stick and it gives me the 5 second boot menu to get into recovery.
I am guessing I have killed it beyond repair? Is there anything else I can try to do?
Thanks
Click to expand...
Click to collapse
You haven't killed your stick, install fastboot drivers and app.
Connect your stick to your pc via usb.
Enter
Code:
fastboot devices
when you see black screen with amazon logo, it should be inside fastboot mode
(If somehow you flashed update to boot.img as written in the guide)
If you see the stick in fastboot mode,
Pull twrp from kamakiri.zip
Place it in fastboot folder
Enter
Code:
fastboot flash boot boot.img
(boot.img or whatever the name of your twrp image)
Code:
fastboot reboot recovery
It should work, if not you can use shorting method again.
Thanks very much both, I will have a play around this evening when I get home from work and the kids are in bed, hopefully with the info above I can get back to recovery again.
Thanks for the help gents, in the end I had to do the shorting method to get the stick to do anything. It took about 6 attempts before kamakiri script even registered it as anything being plugged in, it just kept saying wait for boot.
Once it realised the stick was present and shorted I was away though, I have ended up having to factory reset and wipe everything so will need to start again with it but I am just pleased I don’t need to shell out again for a new stick.
Thanks again for your help