Related
*disclaimer: I am posting here because for all of my searching, I don't see help for unbricking on a Mac when you're already rooted...
********UPDATE: I SOLVED THE ISSUE! I WILL POST A HOW-TO FOR MAC USERS VERY SOON!********
My problem:
I can't use the usual steps in this forum to get past the boot animation because I can't see my device on my Mac anymore since this whole boot loop started. How do I get into adb if my kindle is in boot limbo..?
Note: My Kindle is rooted, I have adb on my Mac and everything was fine until I updated my GoEx Launcher. Help!
Thanks in advance, and I'll donate/buy beers for whoever can help!!!
Am I seriously the only one in this forum who uses a Mac to access adb??
I heard issues, so I dual booted into windows to run the commands.
Sent from my HTC Glacier using xda premium
smirkis said:
I heard issues, so I dual booted into windows to run the commands.
Click to expand...
Click to collapse
Ok. I guess I'm just gonna have to bite the bullet and find a PC. Still, I don't understand how being on a PC or a Mac will make a difference if the kindle is stuck at the boot animation, how will the PC ever get to communicate with it..? I'm mean if it's looping then it never gets to initialize enough for adb to access it... right?
Ok, so for some unexplainable reason, I got my iMac to recognize that my kindle is attached (unlike my Macbook, which never sees it while it's boot looping). Yes, I am still in boot loop though. I think my problem is I never make it into fastboot mode.
When I am in adb, I can see that my kindle is rooted (the permissions pop up in the Terminal) but when I get to the fastboot part, it always returns "permission denied" for any command I enter.
If I've gotten this kindle to talk to adb via Terminal (on Mac) while it's in boot loop mode, there HAS to be a way to push it even further and get it to wipe the system and back to stock... right?
Help!!!!
***UPDATE***
I've somehow gotten into fastboot mode (i think) because the logo is no longer flashing. But of course now that it's in fastboot, Terminal says:
error: device not found
I downloaded fastboot.exe (but what folder should it be in???) and run the fastboot commands, starting with: cd /system/bin
...but it just says: No such file or directory
I feel like I'm really close here lol.. someone, throw me a bone!
im not really familure with macs I know that it is unix based but how do the drivers work? is it like PC or more like linux?
***UPDATE***
PROGRESS!!!
I was able to enter the fastboot commands to erase user data, told it to boot into bootmode 4000, and then I entered the command to reboot...
...that's where it ends. lol
Apparently the Terminal is stuck at: "rebooting..."
I'm gonna stare at it as long as I can, hopefully it reboots because if it does, I can post a new thread for all the Mac users who got stuck like me...
**cross your fingers!***
wtphoto said:
im not really familure with macs I know that it is unix based but how do the drivers work? is it like PC or more like linux?
Click to expand...
Click to collapse
...more like Linux!
OMG OMG OMG OMG!!!! I DID IT!!!!
LOL AWESOME!!!!!!!!!!!!!!!!
Ok! So I'm gonna post my steps for Mac users.. unfortunately, not tonight because I'll be up trying to get CM7 on this bad boy! lol
...and yeah, I know what you're sayin. 'Why hack it some more after you just got it back up and running?!"
Well, that's the life of a geek lol. Not to mention that now I know how to get it back if I crash it again, so.. yeah. Here's to being a geek baby!
Thanks for NOT helping guys... I guess trial and error IS the best teacher!
I know when I was having an issue getting fastboot to recognize I had to add 51-android.rules to my /etc/udev/rules.d directory
**edit** NM looks like you got it, sorry I came in late
wtphoto said:
I know when I was having an issue getting fastboot to recognize I had to add 51-android.rules to my /etc/udev/rules.d directory
**edit** NM looks like you got it, sorry I came in late
Click to expand...
Click to collapse
Hey, thanks! Yeah I already had it in the bag by the time you posted, but thanks for trying to help...
I am in the process of organizing a new post with the steps I went through to get unbricked on my mac. I will be posting soon!
webmastertroi said:
Hey, thanks! Yeah I already had it in the bag by the time you posted, but thanks for trying to help...
I am in the process of organizing a new post with the steps I went through to get unbricked on my mac. I will be posting soon!
Click to expand...
Click to collapse
Thanks so much man!!!!! <3 you (no homo) ur a life saver!!!! can't wait for this guide epic thanks to you!
LOL!!! Glad to know someone else can use it! I have been busy working and now I'm in airport to fly out for the holidays, but I'm working to post it hopefully tomorrow or Friday... I'm on it!
Sent from my Kindle Fire using xda premium
Well, I'm now in the same boat and also on a mac...stuck at boot and can't seem to get it to be recognized by adb... If someone could post the steps, I'd be very grateful...
bikeracer4487 said:
Well, I'm now in the same boat and also on a mac...stuck at boot and can't seem to get it to be recognized by adb... If someone could post the steps, I'd be very grateful...
Click to expand...
Click to collapse
I apologize for the wait. I'm traveling for the holiday and simply haven't had the time. I will try to work on it asap. It's a pretty lengthy post with a lot of steps and I will have to organize it all lol. I will soon though...
Merry Christmas in the meantime..
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
lchanmanl said:
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
HOLY CRAP!! That just fixed my kindle that has been bricked for 2 weeks. THANKS!
HELP!
Troi:
I am in the same boat as you. Can you post the steps you used to unbrick your Fire on a Mac?
Thanks,
David
lchanmanl said:
Here is the fix that should work on Windows/Mac/Linux:
1. first have your kindle plugged in and off
2. in the command prompt, browse to the android platform tools, where fastboot is.
3. type in fastboot -i 0x1949 oem idme bootmode 4000
4. It should show < waiting for device >
5. Turn on your Kindle
If its still sitting at the yellow triangle, then type fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
I'm still stuck at the triangle after step 5. So I tried the fastboot -i 0x1949 reboot and I get this message
ERROR: usb_read failed with status e00002ed
any thoughts?
EDIT: the error now says
ERROR: could not get pipe properties
I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over.
So I followed this guide: http://forum.xda-developers.com/showthread.php?t=1399072
Now I'm stuck at the "Kindle Fire" splash screen, been sitting here stuck for 10 minutes now and still going. Anyone to get out of this? Oh and while I'm sitting here stuck at the splash screen, my power button is still orange, if that means anything to anyone?
I also still see "android phone" in device manager and it says my drivers for it are installed correctly.
EDIT: I have KF connected to my PC, when I type in "adb shell" I get this now:
c:\>cd android
c:\Android>adb shell
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
c:\Android>
Click to expand...
Click to collapse
I also tried following this:
I have also heard of the problem with some people getting caught in a boot loop and see a constant Kindle Fire boot screen. To fix this you must open up your cmd and type:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
But when I type in "fastboot -i 0x1949 oem idme bootmode 4000" I just get this, doesn't do anything?
c:\Android>fastboot -i 0x1949 oem idme bootmode 4000
< waiting for device >
Click to expand...
Click to collapse
I also tried reinstalling my drivers. I removed them, restarted my PC and followed these directions again: http://forum.xda-developers.com/showthread.php?t=1431785&page=2
I tried typing in "fastboot -i 0x1949 oem idme bootmode 4000" but still just sits at "waiting for device".
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
bal1985 said:
I was rooted, just stock though, use BurritoRoot. Also had TWRP working fine. I tried several times to install MoDaCo Custom ROM for the Kindle Fire but it would just throw me into a bootloop at the Kindle Fire splash screen, couldn't get it to work. Someone suggested that I unrooted back to stock and started over...
Click to expand...
Click to collapse
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.
Refot_Sirk said:
We are in the same boat my friend. I think we're gonna have to get/make a factory cable.
Click to expand...
Click to collapse
so you tried everything that is listed above and nothing worked? by the way what is a factory cable, what does it do and how do you get one?
theres gotta be a way to get out of this bootloop...someone has to know.
b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
ive tried all of those.
for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode
b63 said:
to flash the stock stock rom was probably not the best idea because you'r loosing root,fff and twrp
the prerooted secure stock rom from here http://forum.xda-developers.com/showthread.php?t=1402440 is the better choice cause it don't touch fff & twrp
anyway - allthrough i'm pretty shure you allready tried:
http://forum.xda-developers.com/showthread.php?t=1442529
maybe using the unbrick utility can help you:
http://forum.xda-developers.com/showthread.php?t=1428428
or try to start over manually:
http://forum.xda-developers.com/showthread.php?t=1414832
if this all does'nt work:
http://forum.xda-developers.com/showpost.php?p=21062347&postcount=19
Click to expand...
Click to collapse
- the first one didn't work.
- the second, the unbrick utility didn't do anything. everything just sits at "waiting for device".
the third, [fastboot] stock 6.2.1 wont work for me. this is what i get when i try that option:
C:\Android>adb push fbmode /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
2457 KB/s (510876 bytes in 0.203s)
C:\Android>adb shell chmod 755 /data/local/tmp/fbmode
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Android>
Click to expand...
Click to collapse
b63 said:
for making a factory cable look here:
http://forum.xda-developers.com/showthread.php?t=1392693
it puts the kf in fastboot mode
Click to expand...
Click to collapse
yeah im not soldering anything, ill just make things worse. if i could buy one that would be great. my only option is to get my kindle replaced again. no choice. hopefully someone here can help or knows something before i call amazon.
this is the other option - you have to open it:
http://forum.xda-developers.com/showthread.php?p=20565446
would buy a factory cable - there are at least 2 guys selling them here in the forum - one of them is SkOrPn
make a search for factory cable or SkOrPn
it's also good to have one for the future ...
EDIT:
here you can order one:
http://forum.xda-developers.com/showpost.php?p=21309629&postcount=123
u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium
smirkis said:
u need to slow down and read more carefully.
buy a cable from skorpn, fastboot flash twrp than new fff1.2
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.
Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App
bal1985 said:
i read very carefully, but before i start throwing money around, i dont know how much he charges, but maybe someone else can get my through this little issue.
i did message him a bit ago, just waiting for his reply.
Click to expand...
Click to collapse
i think i have read he charges ~ $15 with shipping
G1ForFun said:
Make sure your computer is set up properly to read your kindle...the easiest thing to do is download Kindle Fire Utility, extract it to your desktop, navigate to the tools folder within the Kindle Fire Utility folder, hold shift while right clicking and select open command prompt here. Once the window opens up, try the commands over again where you push the fastboot file and then change the permissions.
Adb shell (press enter)
Su (press enter, if already showing # sign than you are already in su)
Chmod blah blah (press enter)
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
im not rooted so adb wont work properly...
i did what you said:
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>su
'su' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Brett\Desktop\Kindle Fire Utility\tools>
Click to expand...
Click to collapse
b63 said:
to flash the stock stock rom was probably not the best idea....
Click to expand...
Click to collapse
So are threads like this:
http://forum.xda-developers.com/showthread.php?t=1399072
just bad advice? Or is there some inherent risk in flashing or removing any recovery?
bad advice ? don't know - it is written in the title what happens
i think this is for people who want to return the kf to amazon and mostly it works.
if i want to keep my kf and have a working recovery system i would NEVER EVER flash the original stock rom from amazon
there are prerooted stock images available as i mentioned earlier
also a pure update version to 6.2.1 is available (i used it from 6.2 to 6.2.1 - very fine)
There sending me a knew one, I learned my lesson. I'll get more info before flashing. Well at least people know not to use that thread above. He should put a little warning in his thread so no one else gets my promblem.
Sent from my HTC Rezound using XDA Premium
Hi all, I have the same problem, while I was using TWRP I don't know how but I have bricked my kindle, now it is in "kindle fire screen boot loop", when I attach the kindle at computer it is seen, kindle fire utility say:
ADB status: online
Boot status: unknown
I tried to change boot mode from kindle fire utility and it reboot my kindle but in the same situation, so I try to make a factory cable, I connect the red wire with the connector that have not any wire (on the rear), as I read in some threads, but when I reboot kindle pressing power button for 20 sec, with this modified usb insert, and power up kindle....never happens and it still say "kindle fire"
sorry for my english and please help me
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before. Honestly though, I feel like I'm at end. I've scoured Google & xda-dev for 5+ hours now and I can't find a single answer that works. So here's my "special" problem:
Info: Windows 7 Home Premium 32-bit
Kindle Fire (previously) temp rooted with BurritoRoot. Installed TWRP 2.0, firefirefire, google-framework.apk, and the rest of the lot, then de-rooted.
Yesterday, I realized that the Music tab on my KF was crashing. I was literally unable to look at my music. About half an hour later, I was unable to read books as well. Thinking about it now, I'm pretty sure that it was because I had forgotten to uncheck "update automatically" for the stock kindle apps in the Android Market/Play Store, making it unusable in the stock Kindle OS. Oh well, at least the source of the problems was found.
Of course, being the happy little idiot I am, I thought I should just restore the firmware via stock OS. I could just re-root and reinstall all of my apps, right? Huge mistake. After buzzing around for thirty seconds, Kindle rebooted. Instead of launching into the stock OS for initial config though, it dropped itself into TWRP 2.0 without me even pressing the power button. TWRP, of course, kindly informs me that the entire device is blank.
I fretted for a little bit, then connected my Kindle to my computer. I already have the adb drivers installed, but Windows shows it as Unknown Device.. It also helpfully insists that it has malfunctioned and tells me to buy a new one.
I turned to Vashypoo's KFU. A bunch of threads said it was stuck in fastboot and KFU could could put it back into regular (4000) boot. However, KFU's bootmode menu is unable to find the device, which is in the TWRP menu.
I tried using command prompt to gain access.
Code:
adb shell
then
Code:
fastboot -i 0x1949 idme bootmode 4000
gives me "/sbin/sh: fastboot not found" which is really scaring me.
Back to KFU, I tried reinstalling stock firmware from there. It apparently installed fine (how?). I doubt that it did, but TWRP is showing some signs of an OS in the device (not sure if its the full OS or not). Bootmode 1 now giving me no response (!)
Since all I really need is access to the SD storage to upload the OS, I tried to reinstall the drivers. Windows implores that its "Unknown Device" driver is the correct one. Trying to choose the "Android Phone" driver sens me back to "Unknown Device" for some reason.
I went back to basics. Used the mount function in TWRP to mount USB storage. AS you can probably guess, absolutely no response from PC.
Dearest XDA-devs i reach out to you. I'm at end. I don't know what else to do. If any of you can help me, I'll be grateful. While I'm not a complete noob (know my way around computer root, experienced jailbreaker/rooter, know basic command line) I'm utterly lost at what to do know. At the risk of sounding like a pretentious prude, I'll make a list of accomplishments to help anyone else who happens to have strangely fallen down the same path I have. As always, if you ever need more details, just ask.
nxtfari
-----------------------------------------------------------------------------
[X] Reason for stock app crashes (Play Store auto-updated stock Kindle apps)
[X] Reason for boot loop (I'm an idiot/Restore via stock OS)
If you can able to get to adb shell, you won't be able to run fastboot commands from there. Fastboot commands can only be issued to the KF when the KF is in fastboot mode... adb commands can only be issued when the KF is in recovery or booted to the OS. Also, the fastboot command is on your computer (probably in the same directory as adb). If you are in adb shell, it's going to run executables stored on your KF, so you are essentially looking in the wrong place for fastboot. That's why it's telling you that the command can't be found.
If you can get into adb shell while booted into TWRP, you should just be able to just run 'idme bootmode 4000' to get the bootmode back to normal and reboot. Hopefully, your system is intact and is able to boot up. Otherwise, you need to get back to TWRP and you can probably just 'adb push' the stock software onto your /sdcard partiton and use TWRP to install it.
Thank you so much
Thank you so much,
i have the same problem, and with this on a cmd:
#adb shell
#idme bootmode 4000
#reboot
now I have again a kindle fire ^_^
Thanks again
nxtfari said:
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before.
Click to expand...
Click to collapse
I think I speak for most of the people here when I say, your valid attempt at thoroughly explaining your problem, how you arrived at your problem, and the steps you took to resolve your problem is greatly appreciated and goes a LONG way towards getting the help you need in a timely and orderly fashion.
If everyone addressed their problems this way, our forums wouldn't be constantly inundated with threads that require twenty replies to fix a simple problem when it should only take a couple at best.
Wishful thinking
Sent from my Amazon Kindle Fire using xda premium
Hello, my kindle fire is stuck on the kindle fire logo, i have tried to hold the power button to do a reset, but it just stays on the logo after the reset. I don't have TWRP installed. I have attached an image to the post that shows the driver. I have tried to use the kindle fire utility, but my kindle appears offline. I will be very grateful to anyone that can help.
Thanks In Advance,
Zachary.
kinfauns said:
Read this...
http://forum.xda-developers.com/showthread.php?t=1552547
with emphasis on device drivers.
"Android ADB Device" typically means the device is in fastboot mode and you cannot use adb while in fastboot mode.... you must use fastboot.
With your KF off and disconnected from your work computer, run this command...
Code:
fastboot -i 0x1949 getvar product
and then connect it to the computer. The KF will turn on automatically. The computer will say "<waiting for device>" for a bit, but if the command works, it will eventually return "product: kindle" as output. If that works, you can actually flash TWRP from there, but if you are anxious for it to do something again...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
should get it booting normally again. If it doesn't, look at the link I gave you and focus on getting your drivers fixed. You won't be able to execute any commands (fastboot or adb) through Windows if the device drivers don't work. You might want to go back to Firekit if drivers remain problematic for you.
Everything you need to know to fix your KF is in that link at the beginning of my post, including the commands you need to run. At the bottom of post #3 is also another link to a how-to root/install ROMs page.
Click to expand...
Click to collapse
Try this. Originally posted by kinfauns.
Next time you have an issue search the forum before making a thread.
Sent from a thingymajig that sends things.
Can you please walk me through the whole process? Are you talking about cmd???
When i type it in there it says fastboot is not recognized as an internal or external command .
As mentioned your answers are in the kinfaux "beginners guide".
Sent from my Galaxy Nexus using xda premium
veeman said:
Try this. Originally posted by kinfauns.
Next time you have an issue search the forum before making a thread.
Sent from a thingymajig that sends things.
Click to expand...
Click to collapse
What did you do to the KF to end up with it in it's current position? Prior to the current issues have you ever used ADB or the Kindle Fire Utility to connect to your KF? If not, or even if so, you need to read the entire Kindle Fire for Beginners. The entire second post will take you through installing the Kindle Fire Utility and verify you can connect to your KF. When that is done you can use it as josepho1997 suggested.
I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!
shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.
I have a problem
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.
dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.
Just uninstall the kindle driver and replace it with the generic fastboot one
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.
there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?
hw = hardware?
MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.
Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?
uhg
Facepalm
just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608
I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?
I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.