Kindle looks and acts rooted but i can't install TWRP with KFU.
When it ask the kindle to reboot in fastboot the kindle stays idel in usb mode.
EDIt got it rooted by installing android phone drivers then i rolled them back now it reads as a usb composite device or something, doesn't say kindle with the flag like it did at first.
What commands did you use?
what commands??? i used 5 on KFU it did its thing so far then it said waiting for device after it told the kindle to reboot in fastboot.
I just got this today with stock 6.2.2 and got it rooted finally but i want recovery and other roms >.> THe kindle just doesn't reboot when its told by KFU during TWRP installation.
I think KFU isn't working for 6.2.2 at the moment.
Are you comfortable with running commands from the command prompt? If yes, do you have ADB running properly?
if i have a set of instructions I can use the command line. but not intuitivelly, i got this thing rooted even after installing the drivers gfailed so i did pretty good so far
,
Disregard this post. See my next post.
I has to be root first right, cause i was mistaken and it didn't take. when i run the command line to enable root it gets this message
adbd cannot run as root is in production build.
i even tried the instruction on this link by they are very vague for 6.2.2 and it doesn't tell you were to place files which i assume got to C;\kindleADBhttp://rootzwiki.com/topic/13027-universal-all-firmware-one-click-root-including-262/
Disregard my last post. Do the following.
Download BurritoRoot2.bin from this thread and TWRP from here. Place BurritoRoot2.bin and the TWRP image in the same folder as adb.exe and fastboot.exe (you can use the ones from KFU).
Now run the following...
Code:
adb push BurritoRoot2.bin /data/local/tmp/
adb shell chmod 777 /data/local/tmp/BurritoRoot2.bin
adb shell /data/local/tmp/BurritoRoot2.bin
adb root
adb shell idme bootmode 4002
adb reboot
You were given root access for the adb shell with BurritoRoot2 and that allowed you to change the bootmode. The last command will rebooted the KF into fastboot mode.
When you see a solid "Kindle Fire" logo, you can continue with the following commands...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
The device will reboot and install FFF and TWRP.
I.will be attempting this a lil bit later today have Tiber optics installed and they are due any min.
Thankyou for your help.
Do you guys know why when I command Adb root it tells me its in.production build? This confused me.last night and I am expecting to ru. Into it mater when I attempt to do this root and twrp fix
It's because it isn't rooted. I don't think KFU has implemented BurritoRoot2 yet.
I tried downloading the 6.2.2 update and manually update but when it reboots TWRP 2 says Can't mount /mnt/sdcard/kindleupdates/update-kindle-6.2.2_D01E_3205220.bin
then TWRP gets stuck in a loop only loading into TWRP until I do "idme bootmode 4000"
Anyway, since it seems pretty safe at this point to update to 6.2.2 I want to get it over with now, but am having trouble, is the problem TWRP 2.0?
if you use the original amazon update you will loose fff, twrp and root
take a look at this update method:
http://forum.xda-developers.com/showthread.php?t=1452082
works like a charme
Related
i am now in 6.2.1 rooted by Jcase's method.
i can enter the adb correctly but when i type "adb remount"
it resulted back "operation not permitted"
the more important part is that:
when i type in "idme bootmode 0x4002" in the adb shell
it said "<idme>invalid permission"
i have put superuser.apk and su in the correct places.
is there any solution for my situation?
i want to get into fastboot mode becoz i want to try the oc kernel
I have the same problem. is there a solution?
Edit: i found a solution: type su after adb shell, then continue with idme bootmode 4002
after that i was able to install TWRP
Yea you need to su in to be able to do whatever you want.
Sent from my Kindle Fire using Tapatalk
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).
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.
Hi Guys! I need your Help!
My Kindle fire is stuck on the booting logo, it looks a bit sharper and brighter than usual.
I was running a perfect running stock 6.2.2 firmware with root access.
Those are the steps i did:
went to http://forum.xda-developers.com/showthread.php?t=1410223 and did:
Code:
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Reboot normaly with no boot manager, so:
Did the first part of the thread BurritoRoot3 and tried to perform the "To install the CWR recovery by DoomLord after gaining root:" procedure.
Again it did boot normal.
Went to http://forum.xda-developers.com/showthread.php?t=1414832 and did:
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
it went good, i did reboot the device and now its stuck with kindle fire logo and no adb connection
Any advice please Next i will try this http://forum.xda-developers.com/showthread.php?t=1430038
Hopefully someone can assist.
I was at the same place, stock rom, 6.2.2 with root access via burritoroot2. To add TWRP I used KFU edited to support burritoroot2.
Haha puh, i think i fixed it.
this thread help.
http://forum.xda-developers.com/showthread.php?t=1407254&page=2
You have to look at the kindle fire logo. when its static. you are in fastboot mode.
to boot normal you can just do:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
This should work with 4002 as parameter to re enable fastboot mode.
Soo. question solved
But has anybody an idea how to get to CMW installed in fastboot mode?
//ps. i added vendor id (0x18d1) to adb_usb.ini on windows 7
it is described at the op of cwm under [how to test]:
http://forum.xda-developers.com/showthread.php?t=1454241
Did that process b63 link mentions last night without issue on a KF that has TWRP.
miro101 said:
Haha puh, i think i fixed it.
this thread help.
http://forum.xda-developers.com/showthread.php?t=1407254&page=2
You have to look at the kindle fire logo. when its static. you are in fastboot mode.
to boot normal you can just do:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
This should work with 4002 as parameter to re enable fastboot mode.
Soo. question solved
But has anybody an idea how to get to CMW installed in fastboot mode?
//ps. i added vendor id (0x18d1) to adb_usb.ini on windows 7
Click to expand...
Click to collapse
put cwm in ur fastboot folder
fastboot flash recovery cwm.img
u might needto do fastboot -I 0x1949 flash recovery
make sure u have firefirefire already installed, or flash that at the same time. fastboot flash bootloader u-boot.bin
Sent from my HTC Glacier using xda premium
Hey guys,
I'm sorry I couldn't figure out what to do next simply by searching your forum, so I will try to be both as brief and as descriptive as possible.
I started here (http://forum.xda-developers.com/showthread.php?t=1568340) trying to root my fiancee's KF 6.3. I didn't feel comfortable using KFU or similar because those programs are built for Windows and I am using Linux. The Kindle Fire seems to be stuck in a recovery loop. When plugged into USB (using the cable that's actually for my LG Optimus phone), it boots to FireFireFire (yellow triangle) then reboots constantly. At no point is it accessible via adb devices or fastboot, and it doesn't show up under lsusb, which would be the equivalent to not showing up in Device Manager in Windows. (The driver should be fine because all of this was working fine originally when I started the process.)
So I guess my question is what now? I've read a few things about needing a "factory cable" which may set it back into fastboot mode, and I'm pretty sure I could get going again from there. Is that what I need to do? TIA for any help.
PS - I've successfully rooted my LG Optimus S and flashed custom ROMs, so I'm not totally inexperienced. I use Arch Linux and I'm comfortable on the command line. If you have a solution for Windows, I *might* be able to translate it into Linux speak, so don't hold back. Same goes for Ubuntu/Debian - those are totally different than Arch Linux, but I might "get it" enough to translate it.
PPS - I have intentionally omitted information relating to what I was doing when I caused this for brevity, but I would be happy to discuss what steps I took in following the above linked thread if some guru believes it's relevant or someone wants to know.
A factory cable is a last resort kind of thing so I wouldn't jump the gun quite yet, although it doesn't hurt to have one in the first place.
It would be helpful to know which step in the rooting process things went awry. The constant rebooting/restarting isn't typical. Did you make sure you had enough battery before trying to root?
FIREFIREFIRE loads in a temporary fastboot and with the version you are using it lasts for about ten seconds (before the green light goes dim). You can issue fastboot commands during this time without the need of a factory cable.
See if you can get...
fastboot devices
...to be recognized during this time.
Sent from my Amazon Kindle Fire using xda premium
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
It would be helpful to know which step in the rooting process things went awry.
Click to expand...
Click to collapse
OK, let's start with that.
From the thread I linked in the first post:
Your device will now boot into twrp recovery, and flash the firefirefire bootlaoder. When done it will prompt you to reboot. Upon reboot you will get stuck on the "yellow triangle" screen of firefire fire.
Click to expand...
Click to collapse
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
Howto flash by hand
Get into fastboot mode somehow. Having and older FFF from the TWRP installer is a good start. Currently KFU or fbmode is the easiest
flash with "fastboot -i 0x1949 flash bootloader u-boot.bin" (take out "-i 0x1949" if FFF is already installed)
disable fastboot: "fastboot -i 0x1949 oem idme bootmode 4000"
reboot: "fastboot -i 0x1949 reboot"
Click to expand...
Click to collapse
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
pbailey212 said:
If you get stuck at a screen with a yellow triangle, run: fastboot -i 0x1949 oem idme bootmode 4000 If your device is always booting TWRP run: adb shell "idme bootmode 4000" If you still can't get out of booting TWRP, first run: adb shell "idme bootmode 4002" reboot your device, then run: adb shell "idme bootmode 4000" reboot again and you should be out of your bootloop.
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I think the problem here is the he can't get past the bootloader and stuck in an ACTUAL bootloop. In which case, adb commands are useless.
One thing that could be causing problems is the USB cable being used. If the device only experiences these symptoms when plugged in then I would say that's most likely the case.
Sent from my Amazon Kindle Fire using xda premium
I suggest you build a firekit USB for Linux. Search for firekit for Linux thread in the development section.
Sent from my Amazon Kindle Fire using Tapatalk 2
palintropos said:
OK, let's start with that.
From the thread I linked in the first post:
That was not my experience. My device loaded TWRP but just sat there on its home screen without prompting me to reboot. I used adb reboot recovery to see if it had indeed flashed FFF but was simply not prompting me to reboot, and it had not. So I used instructions from elsewhere (http://forum.xda-developers.com/showthread.php?t=1369405) to flash FFF at this point myself:
There were a couple of weird issues with this but the process seemed to go smoothly. However, when I rebooted (the last command) is when I discovered I was stuck in a recovery loop, and the last time I was able to see the device normally via adb devices/lsusb/dmesg.
I guess it may have been the battery because I've since let it fully charge (this is the first time I've looked at it in days) and now it's not in a recovery loop but stably sitting at the "yellow triangle". There is also now an entry for it in lsusb:
Code:
Bus 002 Device 008: ID 18d1:0100 Google Inc.
fastboot devices gives me something like "no permissions fastboot" but I have no idea what that means because I've never seen its normal output.
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/showthread.php?t=1475740
Installing TWRP 2.0.0 is different than installing TWRP 2.1.0. I think the instructions on the TWRP site is for the old version, but they link the new one.
http://forum.xda-developers.com/showpost.php?p=24732291&postcount=1298
Your OP sounds suspiciously like a dead battery, but you say you've corrected that. You might want to connect to your OEM charger for a while anyway and see if that helps
Also, in my experience, fastboot on linux required elevated privileges. Try running it as root.
Make sure your linux environment is set up correctly.
http://forum.xda-developers.com/show....php?t=1475740
Click to expand...
Click to collapse
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
palintropos said:
EDIT: I should note that I do notice the device ID now seems to register as 0x18d1 rather than 0x1949, but I'm not entirely sure what to do about that. I copied my udev rules but changed '1949' to '18d1' and 'Lab126' to 'Google Inc' but I don't even know if that was a sensible move because I've never really done much with udev rules.
Click to expand...
Click to collapse
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
palintropos said:
I've done the Arch Linux equivalents of all of that, and I'm set up with udev rules per our wiki here: https://wiki.archlinux.org/index.php/Android#Adding_udev_Rules
I'm pretty sure the USB cable I'm using might actually be the issue because it was fine straight off the OEM charger, and I even momentarily got a correct reading with fastboot devices (as root), but now I'm back to almost like earlier. The yellow triangle screen is still "stuck"/stable, but I can't find it on adb/fastboot devices or lsusb.
Click to expand...
Click to collapse
Have you tried setting the bootmode to normal and rebooting?
fastboot oem idme bootmode 4000
fastboot reboot
Like I said before, it would probably be best for you to try this as root.
EDIT: It's also possible your system is broken and the KF can't complete its boot process. When you start up the device, the boot logo will first come up. Does the display go black after that and come back with a dimmer yellow triangle logo? Because if it's doing that, it's not in fastboot any more.
kinfauns said:
This is fine. It just indicates you are running the FFF bootloader... pokey9000 changed the VID to a value fastboot recognizes by default instead of the custom vendor ID (1949) that Amazon uses in the stock bootloader. With the FFF bootloader, you can drop the "-i 0x1949" part of the fastboot command.
Click to expand...
Click to collapse
Ditto. If you can get the device to be recognized even for a second, it's still enough time to issue...
fastboot -i 0x1949 oem idme bootmode 4000
Just keep trying
[Edit:] or what he said
Sent from my Amazon Kindle Fire using xda premium
Yay! I played around and got my udev rules working, and I got a reading on (sudo) fastboot devices, so I was finally able to set the bootmode to 4000 and reboot. Everything seems to be back to normal now. The Kindle appears to be working fine though not rooted.
Please let me know:
if there is anything else I should know to make sure the KF is normal
if there is any additional info I should post to benefit other users who might have this same problem
or if I should mark this thread SOLVED/RESOLVED or equivalent and how to do so.
if your fastboot ever stucks in waiting for device mode and you are on linux
try once with either root user or using sudo command.
thats one of the thing people forget most of the time and get stuck there.
http://forum.xda-developers.com/showthread.php?t=1576675
Try the above with the kindle switched off you should see waiting for devic, then press power once ( fast boot should kick in when you power on)
Sent from my Amazon Kindle Fire using xda premium