tried to install TWRP using these instrucitons
http://forum.xda-developers.com/showthread.php?t=1399023
tried everything i could find but im stuck in the kindlefire flash screen and cant go back or anything...is there anyway i can force the tablet to reboot into the OS? It doesnt connect to adb or anything
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
smirkis said:
u are in fastboot. open a cmd prompt in the same directory your adb is in, and run fastboot commands. since twrp isn't installed, u will need to include -i 0x1949 device code or whatever it is, sorry I'm on my device so I can't type is specifically.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i tried doing that..i looked for all of the fast boot commands and it always says fastboot not a valid command etc etc....i tried an adb shell but that didnt work either..i even tried doing a restore with a thread thats in the general forums
Have you verified that fastboot is in fact on your machine? It should reside in the same folder as adb. Also, have you you either A) added the adb/fastboot folder in your Path or B) CDed into the folder where adb/fastboot resides to run the commands?
yay i got it to work...all i did was put in this
fastboot -i 0x1949 oem idme bootmode 4000
then this
fastboot -i 0x1949 reboot
which i got from here
http://forum.xda-developers.com/showthread.php?t=1398728&page=3
looks like all i had to do was add fastboot to the directory i was using so thanks =)
now i just have to wait for a full charge and i can try the twrp again
I also try to install CM7, but it's dead in recovery, I can't exit recovery now. For I have changed boot mode to "idme bootmode 0x5001", How can I change to normal mode ? When I reboot now, it goes to recovery mode directly.
Related
Got the triangle screen and following instructions in guides are not fixing it. Heres my scenario. I got my kindle with 6.2 on it. Got it rooted, installed market and go launcher and was great. Then the update of course came thru and broke root. Still been able to download market apps and use go launcher. So I followed this guide
http://forum.xda-developers.com/showthread.php?t=1417284
to regain root and install twrp. It says root is successful, but superuser force closes everytime trying to open or use it. I can open my tibu and root explorer and everything still gave me root access. Went and changed the MarketIntentProxy.apk to MarketIntentProxy.apk.bak so market links go to market by default. That worked. Noticed that all amazon apps downloaded have a default amazon icon. Thought nothing of it. Went to install twrp anyway. Stuck at triangle now. Followed all instructions to fix and the KFU keeps flashing error device not found constantly and boot status unknown. Not showing up in my devices but I can eject via the safely remove hardware program. What happened? Did everything as guide states and watched the videos as I was doing each step.
you have to update the drivers by right click in device manager (some have to this up to 4 times)
to change the bootmode you can use kfu or do it manually:
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
this is also sometimes helpful:
power down kf by longpress the powerbutton then replug it without powering on before - will do it by itself
then i would suggest to reroot with kfu but take care - if you allready have burritoroot on your device you have to delete it before retrying
b63 said:
you have to update the drivers by right click in device manager (some have to this up to 4 times)
to change the bootmode you can use kfu or do it manually:
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
this is also sometimes helpful:
power down kf by longpress the powerbutton then replug it without powering on before - will do it by itself
then i would suggest to reroot with kfu but take care - if you allready have burritoroot on your device you have to delete it before retrying
Click to expand...
Click to collapse
I can't update driver any longer because it doesn't show in my devices. I will try the adb method since I can't install fastboot.
Sent from my MB860 using XDA App
pre4speed said:
I can't update driver any longer because it doesn't show in my devices. I will try the adb method since I can't install fastboot.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
maybe this helps:
power down kf (long press pwr) disconnect
http://support.microsoft.com/kb/315539/en-us
remove all regarding adb & kindle & restart comp
then reconnect without powering on - will do itself
b63 said:
maybe this helps:
power down kf (long press pwr) disconnect
http://support.microsoft.com/kb/315539/en-us
remove all regarding adb & kindle & restart comp
then reconnect without powering on - will do itself
Click to expand...
Click to collapse
No that did not work either. I have let my tech geek who has a linux based system try to unbrick it. Hopefully he can get his system to talk to the kindle since my windows cant. Thanks for trying to help.
Sent from my MB860 using XDA App
pre4speed said:
No that did not work either. I have let my tech geek who has a linux based system try to unbrick it. Hopefully he can get his system to talk to the kindle since my windows cant. Thanks for trying to help.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=1428428
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
I think I accidentally bricked my kf when I was attempting to root it, wheni turn it on it gets stuck on the flame triangle then freezes after a few minues, I can also boot into recover but I can't seem to mount the usb storage into the computer, it doesn't show anything on my cmputer or anythin so I can't copy the rom over to the storage inside. Is there any way to push a file throug fastboot? Sorry I'm a newb at all this
go into twrp and tap mount - mount sdcard - it will show up on your computer
if not check your drivers
I believe you can adb push files to your device if it booted into recovery (check your device is recognized by adb devices; if not it might be a driver issue), however TWRP also can mount your "sdcard" and have it show up on your PC like any other mounted device; look for the "mount" button.
Good luck!
So its a possibility I can access it through adb while its in recovery? Ill try as soon as I get home
Sent from my SPH-D700 using XDA App
Open adb shell and type
idme bootmode 4000
reboot
I assume that you are able to communicate to your KF.
Regards
Sent from my GT-S5830 using XDA App
i can't seem to access it through adb but i can through fastboot
well i made little progress
i took a random custom rom > took the system file > then packed into a zip file > flash with "fastboot flash system ect."
but now it goes through a boot loop into recovery (boots into the kindo logo for about 1/2 a second and then reboots into recovery automatically)
issue:
adb shell idme bootmode 4000
adb reboot
Or, if you can't get there through adb but can with fastboot
fastboot -i 0x1949 oem idme bootmode 4000
fastboot reboot
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
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Anything?
oliverm91 said:
Hi,I just installed android 4.4.3 from 4.4.2 rooted with kernel mat1x v13.5 with the following steps:
adb reboot bootloader
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.02.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Then installed CWM by:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-touch-6.0.4.7.img
fastboot reboot-bootloader
and then I tried to go to recovery mode with:
Code:
fastboot reboot-bootloader
but the command line says:
Code:
<waiting for device>
. If I write:
Code:
fastboot devices
, nothing happens, but if I write:
Code:
adb devices
it does recognizes my phone.
Anyway I went to recovery mode with volume buttons (CWM is properly installed), went to sideload options, USB connected and typed:
Code:
adb sideload UPDATE-SuperSU-v1.99r3.zip
but it says:
Code:
error: device not found
While I'm in Recovery mode (in CWM) adb devices can't find any device.
SDK tools and platform-tools are just updated and PC is just rebooted.
EXTRA INFO: when i go out of CWM it says:
Code:
Root access is missing. Root device? THIS CANNOT BE UNDONE.
and options are
-no
-Yes - Root device (/system/xbin/su)
When I choose Yes it just starts with no problems.
Click to expand...
Click to collapse
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
taodan said:
Try reboot the phone and then reboot to recovery and see if that works. If not, try TWRP recovery.
Click to expand...
Click to collapse
You mean turn off the phone and turn on to recovery? Because I've already done that as I mentioned in the first post.
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
audit13 said:
Not sure but aren't recovery mode and fastboot mode different?
Can you manually boot into fastboot mode on your phone rather than using adb commands?
Click to expand...
Click to collapse
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
oliverm91 said:
I just used fastboot to go into recovery with my pc because i'm lazy, I can do it with the mobile, but when i tried I discovered the <waiting for device> error. And I need to use adb coomands to sideload SuperSU. I think i can flash it from the phone, but it still bothers me the fact that there is something wrong, because I use my phone to test personals apks.
Click to expand...
Click to collapse
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
audit13 said:
Are you using a Windows PC? If you are, boot into task mamager and kill all ADB services. Relaunch the command prompt and try it.
Click to expand...
Click to collapse
I am, Windows 8. But this problems happens even after rebooting my PC.
oliverm91 said:
I am, Windows 8. But this problems happens even after rebooting my PC.
Click to expand...
Click to collapse
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
audit13 said:
I assume the drivers load the first time you connect your phone. Does running the command prompt as an admin make a difference?
Click to expand...
Click to collapse
I use PowerShell as admin
No clue?
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
karthi89 said:
Revoke USB debugging authorizations for all the devices from the developer options and try again..
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Did this, but ADB still doesn't recognize my phone while in recovery.
jd1639 said:
Adb and fastboot are two different things. Use adb commands when you're booted into recovery or normally booted. Use fastboot commands when you boot into the bootloader
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok, but ADB won't recognize my device when it's on CWM (CWM v6.0.4.7)
I realised that in "device manager" of Windows a yellow triangle appears on "Other devices" -> Nexus 4 (when im in Recovery)
and when I normally boot my phone it appears normally under "Android device" -> android composite adb interface
No clue?