I have previously installed TWRP which has run without any problem, helping me to install the rooted version of KF 6.2.1 firmware posted here in xda a month or so earlier. It has been running fine until yesterday.
For some reason, when I ran Market, it asked for secure login with a "Retry" button which did not work. When I checked it was still registered with my GMail account for Google. Then the wifi started to go on and off for no reason.
I realized something went wrong so I decided to re-install the rooted 6.2.1 using TWRP.
The installation process completed successfully. I pressed "Reboot" button then choose "Power off". However when I restarted the KF by pressing the on/off button, it booted into TWRP by itself (meaning when the yellow triangle came up, I DID NOT press and hold the on/off button to boot into TWRP; the light went orange by itself and booted into TWRP). I switched on and off several times, but it booted into TWRP by itself all the times.
I decided to wipe everything before re-installing the firmware. I got back into TWRP and wiped cache, Dalvik, System, Factory reset and SDcard. When I press "Install" button, the copy of firmware is no longer on the KF because of complete wiping. I press "Mount" -> "Mount USB storage" and hook up the KF to my PC, so that I can transfer the copy of the firmware to the KF.
I repeated the process (firmware installation was again successful), but I still got the automatic booting into TWRP instead of normal boot.
Then I tried using KF Utility 0.9.2 to update TWRP (I originally installed TWRP using the TWRP Installer). However, I could not get it into fastboot mode (the Utility says "fastboot mode: no"). The instruction from the Utility said if installation did not work, try reinstalling the drivers - I ran "install-drivers.bat" and reinstalled the drivers, but did not get into fastboot mode to do anything.
Then I tried to install CM7 instead of the original firmware. I copied CM7 onto KF and used TWRP to install the zip. Again I wiped everything before installation. Unfortunately this time, the installation process did not complete. I rebooted the KF and again it auto-boot into TWRP (probably because there is no OS on the KF now).
I can still boot into TWRP without problem. The nightmare now is that:
When I try to mount USB device so as to connect to the PC to transfer files, my PC does not detect it as a drive.
Before the screw-up, it shows in Windows Explorer as "Kindle" (or "Amazon Kindle device"). Now when I go to device manager and click "Disk Drives", only the HD of the PC shows.
The "Android Phone" ("Android ADB interface") still shows in Device manager when I hook up the KF, therefore I guess I can still use ADB.
So these are my two questions:
(1) How do I get out of the "reboot loop" and stop the automatic reboot into TWRP so that I can boot normally into Android (this is presuming I install the firmware successfully)
(2) What can I do now that "USB Mount" in TWRP does not work? Can I fix it or can I reinstall TWRP?
Thanks.
Desperately yours
ST
If in Device Manager it shows up as "Android Phone" that means you have the ADB drivers installed and it will not mount as a drive. Simply delete the device from Device Manager and replug the kindle to your computer, or just use a different computer.
Sent from my Kindle Fire using Tapatalk
DesDr0id said:
If in Device Manager it shows up as "Android Phone" that means you have the ADB drivers installed and it will not mount as a drive. Simply delete the device from Device Manager and replug the kindle to your computer, or just use a different computer.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
ALL PROBLEMS SOLVED
Thanks. I uninstalled ADB then reconnect KF, and it reinstalled ADB. When I press "Mount USB storage", my PC detects KF as a drive ("Kindle") again.
Actually I also solved the problem of TWRP bootloop:
http://forum.xda-developers.com/showthread.php?t=1390773
I used ADB to issue "idme bootmode 4000". This took my KF out of the TWRP bootloop back to normal boot. I am surprised to see that CM7 installation is successful, despite it seemed that in TWRP this was cut off in the middle, without the usual "installation successful" message that came after original firmware installation.
Can you see it in adb by doing an "adb devices"?
just for the future - the commands to set bootmode to normal depending on the current bootmode and version of fff:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
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
please mark the subject of the topic (edit first post) to [Solved]
Link to original thread: http://forum.xda-developers.com/showthread.php?t=1452651
This is a specific guide to restoring your Kindle Fire from boot loop caused by changes in the /system/ directory permissions.
The problem:
After rooting my Kindle Fire, I tried to install the Android Market app and while doing so, messed up my read/write permissions of /system/app/
After rebooting my Kindle, the logo animation started looping endlessly, indicating there was a serious issue taking place.
The specs:
Device: Kindle Fire
Firmware: 6.2.1
Desktop: Mac Mini
OS: OS X Lion
The tools:
You will need,
1. The KindleFireRoot Kit from here (It has tools for all OSs)
2. TWRP 2.0 from here
3. The fbmode file found here to be able to stock fastboot in 6.2.1
The steps:
1. Move all the contents from both the downloaded KindleFireRoot Kit and TWRP into a single directory for convenience.
2. Assuming you were able to root your Kindle in the first place, it's likely you already have drivers installed (Windows). Check by opening a Terminal, navigating to the dir with all the tools and doing this on Windows:
Code:
adb kill-server
adb devices
on Mac:
Code:
sudo ./adb kill-server
./adb devices
Your device should be listed. If it is skip to the next step.
If it's not, install the drivers found in the usb_driver directory (Win only). In this directory you can find the adb_usb.ini file which you need to move to the .android directory that's inside /Users/[your_name]/
3. We will now use the fbmode to fastboot to stock 6.2.1 as explained in this thread.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
4. Now that we can fastboot, we will install TWRP 2.0.
Just run this command:
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
...and reboot. The Kindle should boot into a screen with a yellow triangle and TRWP will install itself.
5. What you need to do now is tap the reboot button onscreen. As it reboots, hold down the Power Button until the light turns orange. You will then boot into TWRP. You will see a Menu with a bunch of Buttons.
6. Now it's time to boot up your Kindle as a USB Drive to repair the permissions.
Touch the Mount button and select the checkbox that says System. After that tap on Mount USB
All you have to do after that is type this in the Terminal and voila:
Code:
adb shell chmod 755 /systme/app
7. Reboot your device and enjoy.
Thanks to everyone who helped me figure that out in the original thread and the threads that I've linked. I might be missing a step. PM if you get stuck or just Reply on this thread.
/system/app kindle fire
Hi,
Thanks for the instructions. I got to the point where the yellow triangle shows up on my kindle fire after doing the fastboot command and touching the reboot button on the kindle screen. However, it just locks up after that and I never get to the subsequent menu. All I see is the yellow triangle on the screen with the instructions to press the power button for recovery. I have reset the power many times and all I get is the yellow fire triangle now. Any ideas how to get out of this loop? Thanks.
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
if you'r done you may have to reset the boot mode to normal (when you are in twrp):
adb shell idme bootmode 4000
adb reboot
Windows doesn't seem to be recognizing my device anymore. I get an unknown usb device when I plug it in. When I run the fastboot commands I get a <waiting for device> from which it never returns. I tried to reinstall my android_winusb.ini file to the kindle, but windows says it is up to date. Windows gives me this error in the device manager: " Windows has stopped this device because it has reported problems. (Code 43)" Help!
you have to update the driver manually:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
Thanks, that did it! I also had plugged it into another computer that recognized it as a kindle. I'm not sure if that mattered or not.
This seems to be great. Unfortunately I've got to a different thread and I think I totally bricked my Kindle. I was able to install and run TRWP. However I tried to do a recovery from Amazon Stock img. Then rebooted the kindle. After that the kindle rebooted and got stuck again. I tried to re-run TRWP but this time I got a different error message when tried to run adb shell to go into fastboot. The error message said the system shell could not be found. Adb shell is not accessible and if I do a fastboot command it says waiting for device.
If I do adb devices I can see the actual device # not anymore in recover mode but listed as device. But not able to run the adb shell. I am really frustrated!
that happend many others by trying to flash the original amazon rom
the original rom deletes fff, twrp and root
with a messed up system shell you have no possibility to get to fastboot mode
the only solution is to use a factory cable - you can build or buy one:
http://forum.xda-developers.com/showthread.php?t=1392693
the factory cable forces the kf to fastboot mode
restore with factory cable:
http://forum.xda-developers.com/showpost.php?p=21391952&postcount=38
handling:
http://forum.xda-developers.com/showpost.php?p=21708081&postcount=157
or in short:
You must insert cable, then switch off kindle by pressing button about 20sec and press once again, kindle will be in fastboot.
test with "fastboot getvar product"
After kindle will be in fastboot, with Kindle Fire Utility install TWRP recovery and with recovery install prerooted stock or CM7 firmware.
Rom: Stock
Rooted with KFU 0.9.5
TWRP 2.1
fff 1.4a
The problem I'm having is that when I boot my KF up it goes to fff. I get 3 options to boot from (this is whenever I power down the KF). When I choose to boot to recovery, the power light turns orange for two secs and then it boots; but back to the fff screen. I did this about four times in a row and it still boots back to the ffa screen.
If I choose ~normal boot~, It boots up fine. When I try to use KFU to boot to recovery or fast boot, it says that it is waiting for device. I tried this several times but no luck.
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
I'm not very advanced in this stuff. Please be patient with me. Thank you for all your help.
what command are you using to install recovery?
ok
download twrp 2.1.1.img onto pc
turn off kindle (20 second hold) with the usb cable unplugged from the kindle
open terminal where you have fastboot located.
type the following:
fastboot flash recovery </enter/path/to/recovery.img/here>
press enter
you should see waiting for device
then plug in your usb to kindle
this should power up the kindle and fastboot flash a new recovery.
then type
fastboot reboot
note:
(there is a space between recovery & /
i also find it easier to put a space after "recovery" then drag & drop recovery.img into terminal)
ok...
I did everything you said and the cmd console was still <waiting for device> after I plugged in the KF.
I checked in device manager and that's ok for the adb (it says: android composite adb interface).
Still looking to get into twrp recovery.
IndianaBond said:
I want to get into recovery. That's my goal. I'm guessing that the KF is not booting in fastboot for it to go into recovery. I tried to reinstall TWRP 2.1 with KFU and it gets to the point where it's waiting for the device and nothing happens.
Click to expand...
Click to collapse
There's probably something wrong in KFU's process. Could you at least show us its log or a screenshot?
reflash twrp using smirkit. than try to get into recovery again
Sent from my Galaxy Nexus using xda premium
if its waiting for device your pc is issuing fastboot command. so as you say its your kindle.
one of the above methods should work.
imho smikis's smirkit is nice to use
edit: can you copy and paste your commands after you try to flash new recovery
Let me know if this post belongs somewhere else.
My Mi A1 is stuck in a bootloop as a result of trying to install magisk 14.4. At the moment I can boot it into fastboot mode, but not into recovery mode. In fastboot I can execute the command
fastboot devices
that returns the hex number followed by "fastboot." However, it does not respond to any other fastboot commands, e.g.
fastboot reboot
fastboot oem device-info
I have been attempting to flash the stock rom without success as follows:
in win10 32-bit environment:
fastboot responds as above. I cannot install the MiFlash-2017-7-20 version. Windows complains. I conclude that version must be a w10 64-bit app, although it doesn't say so.
win10 64-bit
MiFlash-2017-7-20 installs and runs, but does not see the device. Apparently, the adb drivers are at fault. I have turned off signature enforcement and tried installing various versions of the adb drivers. The device manager shows them as installed, but reports that they cannot start.
Centos 7 linux
Adb drivers install. "Fastboot devices" reports correctly. All other fastboot commands fail, i.e. they hang. I tried installing the tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image using the linux shell script provided, but that just hung also.
Is this phone well and truly bricked at this point? Is there any other recovery available?
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
GalihBK said:
Maybe you should boot to other partition (A or B)
Just fastboot then try boot to other partition, hope it works
Click to expand...
Click to collapse
As he said, he can't execute fastboot commands so that isn't a option.
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Edwin Hamal said:
I think it is not hard bricked by any means. Try booting into the Quallcomm EDL and try flashing the fastboot rom with MiFlash too. You can setup a virtual environment in which the flash tool can run and the drivers can install properly.
Click to expand...
Click to collapse
1. I tried this method to boot into EDL with no luck. Is there any other way?
C:\Downloads\xiaomi mi a1 root>adb reboot edl
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
2. On my win10 32-bit installation I am able to run MiFlash-2017045. It reports the device. I attempted to flash this image:
tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794
It completed and reported "success" however it did so in only 7 seconds, so it must not actually have succeeded. In any case the phone still will not boot.
3. However, I distrust MiFlash 20170425 because it comes from an androidmtk.com site and the processor is Qualcomm, not Mediatek. So I attempted to install MiFlash2017-07-20. However, that program will not install on my win10 32-bit installation. There is a Windows msg saying it cannot be installed, but does not give a reason. I suspect it is a 64-bit program. So, I installed MiFlash2017-7-20 in a win 10 64-bit installation. The program does run, but it does not see the device. I suspect that the adb drivers do not install correctly. I did turn off signature enforcement and the drivers appear to install, but the device manager reports that the drive cannot start.
The tissot images include bourne shell scripts to install, so I installed the adb drivers on my Centos box. Fastboot reports the device, but just as in win10 no other fastboot commands work. So, even though I did try to execute the install_all.sh script, it just hung on the first "fastboot getvar product" command.
So, I do not have a way to flash the stock rom.
_mysiak_ said:
@yuoip
1. You say that "fastboot devices" works, but "fastboot reboot" not. What error do you receive? Could you paste full log?
2. Sometimes drivers in Windows must be installed manually - open device manager, find unknown device, choose from list and find and choose "android fastboot" or "android adb" device depending on the mode you're in. If you have installed fastboot device before, you should be good to go. Otherwise you'll need to download minimal adb package (https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/), or Google development kit (much larger).
3. stock recovery mode is started by pressing "power button + volume up", once "no command" screen appears, press shortly "power button + volume up" to show the menu.
4. please post full log of command "adb devices" as well
Click to expand...
Click to collapse
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
dhewaghost said:
Hola guys. I got mostly the same issue here. While I still can use adb comand while on fastboot. But i can't flash stock rom using mi flash.. i mean after the done notice my phone still stuck and wont reboot. Like the flash doesnt apply to the phone. I wonder what was wrong
Click to expand...
Click to collapse
Use fastboot commands manually. Mi flash tool is very buggy. Many time it doesn't work.
_mysiak_ said:
Unpack ROM image, extract directory, open cmd, run "flash_all_except_storage.bat" (you might want to remove command "fastboot %* oem lock" from the end of bat first), check/show log.
Click to expand...
Click to collapse
Did the command:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot getvar product 2>&1 | findstr /r /c:"^product: *tissot" ||
"Missmatching image and device"
So this is a little interesting. However, I don't think that the image is actually the wrong one, but that the script cannot get the device info since both "fastboot getvar product" and "fastboot oem device-info" fail on a timeout.
zazzy24 said:
The easiest thing that worked for me in a similar situation is going into stock recovery and factory resetting the device. I had tried pretty much everything before this and my device was still dead for 1 and a half days before i hit upon this idea without any guides and it worked!!
Do this to get into recovery mode:
1. Power off your phone
2. Press power button and volume up button at the same time
3. You will get "No command" Screen with Android robot with exclamation mark
4. Press power button (don't release) then press volume up button..
5. You will enter into recovery...
The phone may just reboot normally the 1st time you try it as it requires some practice to get it right, but keep trying..
Hope this helps
Click to expand...
Click to collapse
When I do that it just keeps going back to the "no command" screen. I think the recovery image is either damaged or gone.
yuoip said:
1. All fastboot commands, other than "fastboot devices" just hang on "<waiting for device>" with no error message in the linux environment. In the win10 environment they timeout after a few seconds with a message like this:
C:\Downloads\xiaomi mi a1 root\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794\tissot_images_7.8.23_7.1>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 7.000s
2. I had already installed adb-setup-1.43.exe, but I ran it again anyway. Same result.
3. The device will not boot into recovery mode. Pressing power and volume up brings it the "no command" screen with the supine robot image.
4. C:\Downloads\xiaomi mi a1 root>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No other output.
Click to expand...
Click to collapse
1. & 2. It sounds like you don't have installed fastboot drivers (install them manually via device manager) or phone isn't connected in fastboot mode (make sure there is a picture with fastboot written on the phone).
3. this IS the recovery mode, just press power + volume up again to show the menu
4. you won't see ADB devices in fastboot or recovery mode, unless you enable ADB sideload from recovery
Device Manager shows:
Android Phone
yuoip said:
Device Manager shows:
Android Phone
Click to expand...
Click to collapse
Wrong drivers then, it should say Android bootloader interface. Reinstall them correctly.
1. I did the manual install, but I don't see anything labeled "fastboot driver."
Device manager now reports:
Android Phone
Android ADB Interface
Android Bootloader Interface
Android Bootloader Interface
Android Composite ADB Interface
However, all these entries have a warning symbol on them. The Device status for each is:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Is one of these the fastboot driver? Apparently not, since the behavior of the fastboot command hasn't changed.
When I try using the fastboot command the A1 shows "Fastboot" with the rabbit character and the sick robot.
I should mention that in the Centos environment I have installed the android-tools package, which include adb and fastboot drivers and tools. The behavior of the fastboot command there is the same.
So, this leads me to believe that the problem is the A1, not the windows or linux environment, but I don't know enough to know for sure. Also, I would assume that if the fastboot drivers were not installed, the command "fastboot devices" would fail, but it doesn't.
3. At the "no command screen" if I do press and hold the power button and then the vol. up button it boots right back into the "no command" screen. There is no menu.
4. With no recovery menu I can't set any options.
Uninstall/remove everything with android name in it, disconnect phone, reconnect phone in fastboot mode. Make sure that there is only one item under Android Phone - Android Bootloader Interface. You should not see 4 devices - do you have Android emulator running or anything else connected?
When in recovery, do not hold power + volume up, just press it briefly. Sometimes it takes few tries to show the menu, but I can assure you that it's there.
Yes! You're right. The recovery menu is indeed there. I didn't know that it had to be a short press to bring it up. Thanks.
Device manager now shows only one "Android Bootloader Interface" entry. I am not running any emulator.
So now what do I do? Do I need to flash the tissot... image? The fastboot command still behaves as before.
Quick Google search suggests to avoid using USB 3.0 ports. So..maybe try another ports on your PC..?
Hi,
I have an HD 10 that's stuck on the fire screen.
I can boot into recovery but ADB won't recognise the device and it doesn't show up in device manager.
If I reboot into bootloader the fire appears in device manager, loads the drivers and I can use fastboot and see the device.
Is there a way to push the update.bin file to the device using fastboot so i can try and restore or is there a way to get ADB working that I've missed out?
Thanks
Nick
OK, ignore me. I had to choose 'apply from adb' so the device appeared in device manager and then manually select the drivers. All good now!