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
Related
Whe I try to install CM7, I installed recovery successful by change boot mode to "idme bootmode 0x5001", maybe I made some mastake when I copy log file, I can't update to CM7, now it's always come into recovery mode when I restart KF, I don't know how to exit recovery mode.
How can I change to normal mode? Thank you!
Is there any method to exit recovery mode?
yuhao51000 said:
Is there any method to exit recovery mode?
Click to expand...
Click to collapse
try:
fastboot oem idme bootmode 4000
fastboot reboot
That command will put it back to OS boot mode, not recovery mode. That worked for me when I flashed TWRP today.
If your stuck in clockwork, adb should work and you can type
adb shell
su
idme bootmode 4000
exit
exit
adb reboot
fastboot commands won't work while your in recovery, only while your in fastboot.
It works, now I installed CM7 successful, great thanks!
could this work on another device like the tf700?
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
Not quite sure what i did 0_o. I used the kindle fire utility to install permanent root. It rebooted and allwas well. Then i used the program to tell it to boot into fastboot mode. when I did this now it just loops between the Triangle and TWRP. Im guessing not screwed...i just dont know what to do next to fix it lol. I tried the brick fixer program. it just reboots the kindle fire and then it does the same thing over and over.
Try hooting into TWRP and telling it to reboot in normal mode.. using KFU of course lol.
I'm in the same boat...however, I figured out how to get it to stop and stay at the Triangle (fastboot mode)
I typed "fastboot -i 0x1949 getvar product" into the Command Prompt Window on my computer. It then said <waiting for device>
I forced the Kindle off with the 20-sec press, then unplugged and re-plugged it into the computer.
Now I just have to figure out how to get the fastboot mode to give me access to the USB, or to get ADB working on this sucker. I'm trying to get a ROM over to the Kindle's internal memory so I can save it's life!
Hopefully this will give you a launching place, too. Oh, and using the Kindle Fire Utility will then work as long as it's in the triangle screen, but every step I've used with it so far just puts me back into the FireFireFire / TWRP loop.
Hey guys thanks for the response. shortly after I posted this I went into the kindlefire irc channel and they helped me out. somehow the stock rom i was on corrupted itself and even when i did
adb shell
su
idme bootmode 4000
reboot
It still wasnt fixed. So the solution was to flash that modaco rom thats here and then run the adb command again. Viola. Working Kindle Fire . Now if i can just figure out how to make the stupid wallpapers stop auto cycling lol.
New_Guy777 said:
I'm in the same boat...however, I figured out how to get it to stop and stay at the Triangle (fastboot mode)
I typed "fastboot -i 0x1949 getvar product" into the Command Prompt Window on my computer. It then said <waiting for device>
I forced the Kindle off with the 20-sec press, then unplugged and re-plugged it into the computer.
Now I just have to figure out how to get the fastboot mode to give me access to the USB, or to get ADB working on this sucker. I'm trying to get a ROM over to the Kindle's internal memory so I can save it's life!
Hopefully this will give you a launching place, too. Oh, and using the Kindle Fire Utility will then work as long as it's in the triangle screen, but every step I've used with it so far just puts me back into the FireFireFire / TWRP loop.
Click to expand...
Click to collapse
would try to boot to twrp, tap the mount button and mount sdcard
now you should be able to copy a rom to sdcard and install it
to force it to boot to recovery issue: "fastboot -i 0x1949 oem idme bootmode 5001" and "fastboot -i 0x1949 reboot"
if it says <waiting for device> just cold restart the kf - the command should be picked up and finished
don't forget to switch back to normal boot after installation: "adb shell idme bootmode 4000" and "adb reboot"
maybe this could also help you:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell 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
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
hillbillyhotrod said:
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
Click to expand...
Click to collapse
Sounds like you're still in Fastboot mode.
Try these ADB commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Thanks
Sorry it took me so long to respond but I had a login problem. From what I have read ADB doest go al that well using ubuntu, that and I'm not really all that good using command line and terminal. Any other ideas?
So my friend tried setting it up remotely last night but it didn't go well, anything I can't do from inside TWRP to make it work?
Sent from my SGH-T959V using XDA App
hey
hey man, in twrp, trying doing mount, then on your computer, put on a stock rom to the drive, then in twrp, run the stock rom
I'm pretty sure that is what I have been doing but I will try again
Ok, tried again and no luck, I have tried cm7 cm9 and a few others with the same result.
semms like the kf is in bootmode 5001 (recovery)
would try to use kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
but use the corrected run.sh from here:
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use option 1 - bootmode normal
an other option is firekit:
http://forum.xda-developers.com/showthread.php?t=1430038
It's alive
Brought it to my friends house yesterday who has windows and that command worked perfectly. Now I have energy ICS installed and cant log in to gapps, lucky me.
Now should I be able to put on a different rom from Ubuntu computer without that happening again?
Sent from my SGH-T959V using XDA
to switch it accidentially to a wrong bootmode can allways happen, but it's no problem:
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell 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
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
Way over my head, plus im not able to do the adb from my computer I have to have my friend do it from his windows machine.
just flashed a gapps for a different rom but still not letting me sign in to google. Driving me nuts.
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
b63 said:
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
Click to expand...
Click to collapse
I will have to check that out
Gapps
Any clue how to get my gapps working?
the energy rom should have it allready built in:
http://forum.xda-developers.com/showpost.php?p=23255224&postcount=75
It does but I couldn't sign it so I tried a different one, still cant get in.
sorry - don't know the energy rom - would try to ask NRGZ28 in his thread
Thanks for the help
It is stuck at the picture of yellow fire icon, with a phase press power button for recovery at the bottom...... but no matter how many times i press the power button, it does not respond..............helphelphelp.....
Try holding the power button for about 20 seconds, that should reset it. You can also try this: http://forum.xda-developers.com/showthread.php?t=1356257
Did you install a recovery yet? if so, try spam pressing the power button to get into it. From there you should be able to mount usb and install a rom
The kindle fire has several boot modes, one being a fastboot mode where it will stay at the bootloader until fastboot issues a command to change the boot mode. The command would be...
fastboot oem idme bootmode 4000 && fastboot reboot
not trying to be an ass but i wish people would learn some of the basics before jumping in head first into things they don't really understand then posting basic questions in the development section of forums
But my PC now cannot recognize my fire which is recognized as unknown device. Every time I tried to use adb shell, it said device is not found.....oh my god.....
And I have tried to hold the power button for more than 20s but it doesn't seem work.....
In fact I have installed TWRP once. However, when I am accidentally installing the TWRP twice, the fire is then stuck at the yellow triangle "FIRE" logo...and with a phase press power button for recovery at the bottom.
OH MY GOD....the Fire is my mum's ..... she is going to kill me
I didn't say anything about adb shell
foxdog66 said:
I didn't say anything about adb shell
Click to expand...
Click to collapse
not using adb shell??!! then how can I use the command????
You might also need to use the -i switch. So the command would look something like...
fastboot -I 0x1949 oem idme bootmode 4000
not to be "that guy" but this is in the wrong section. it should go in general.
--sent from my glacier.
I had the same problem ... my computer recognized my fire for 20 sec and BAM! everything just got frozen... just triangle for ever... then I connected to computer ... I had the TWPR installer already open... and before freezing I tried to re install the recovery mod and it worked!
some basics:
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell 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
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse
b63 said:
some basics:
Click to expand...
Click to collapse
MY fire relights its fire!!!!! so many thanks!!!!!!!!!!!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
I solved it! it very easy:
1- plug your device to your PC while it is on fire icon
2- open "Kindle Fire Utility" and then press 5
3- done!
I was so scared that I had lost my kindle. I write this for others so hopefully will be helpful for them.