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 looked through A LOT of bricked KF threads but I can't fix the issue that I'm having. Before I found this forum and the very useful looking tools that it provides (KFU, etc) I managed to root my KF by using adb and pushing / installing burritoroot by the command prompt. Everything looked OK, I installed su and got root access to work in the adb shell as well as for apps.
I attempted, without much success, to get the Android Market working on my KF but it always crashed. I messed with some permissions like for /system/app, but I changed that one back to match the other folders in /system.
I may have deleted an apk out of /system/app that wasn't the Android Market, but I'm not sure...
Anyway, I tried to reboot my KF and it got stuck in a boot logo loop. It reports a boot mode of 4000 (normal).
I tried the fastboot recovery method and also KFU, but there are some issues:
Root access seems to have disappeared (access through adb shell cannot be elevated)
Burritoroot will not install anymore through KFU (I get the message "Error: Could not access the Package Manager. Is the system running?"
The above message also occurs when I try to use the adb install command
Fastboot never recognizes the device. It sits on <Waiting for Device> forever.
I've tried rebooting the KF while connected and reconnecting the USB.
I made a Factory Cable, but the Fastboot condition is the same.
I uninstalled my Windows drivers until it showed up as "Kindle" in the Device Manager and installed the files that came with KFU.
I tried the KF Unbrick utility, but that didn't seem to do anything that I missed.
Additionally, when I connect with adb shell I have limited file system access. I can is through /system and some other folders, but I can't access /sdcard and I can't seem to mount the sd card
After writing all this and thinking it through, I decided to compare the /system/app directory on my KF with one in an update.zip file that I downloaded.
It looks like I deleted the file ApplicationsProvider.apk from /system/app
That seems to be the only thing missing.
Is this a Try-to-return-your-KF important file? Is my KF hosed?
fonetik said:
Is this a Try-to-return-your-KF important file? Is my KF hosed?
Click to expand...
Click to collapse
Nope, if you can get fastboot working it doesn't matter how broken /system is. Try this to sidestep the Windows driver problems I think you're having:
http://forum.xda-developers.com/showthread.php?t=1430038
Once you get TWRP installed you can restore from the stock update which will wipe and replace /system.
Thanks I'll give this a shot. I had some issues with Windows when trying to install Cyanogen on my Droid X and a Linux Live-CD got me back on track. Hopefully this will do the trick. I'll report back.
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
I had a similar problem and it was my usb driver set up:
/etc/udev/rules.d/##-android.rules
the ## for Meerkat is 70
SUBSYSTEM==”usb”, ATTR{idVendor}==”0bb4″, MODE=”0666″
Vendorid is 1949 for KF
link that got me going: http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
sorry if you already know this.
I'm new to this so thanks. I'll try it tomorrow when I get a chance.
fonetik said:
Well, I'm in Ubuntu and I got the firekit stuff up, but it does the same thing. It refuses to connect with fastboot. It just sits at < Waiting for Device >.
Click to expand...
Click to collapse
Are you sure you're in fastboot at that point? Are you using your factory cable? Try doing this to get into fastboot mode and use a different USB cable to connect with fastboot. If that doesn't work, do the same but use Firekit in case the fastboot drivers are messed up.
I'm probably not in fastboot. I'll give this a shot. Thanks again.
Edit:
That seems to have gotten me into Fastboot! I'll see if I can get TWRP installed.
There's a faint pulse =)
Edit 2: TWRP installed OK and I used it to try and install the stock update.zip. It rebooted and then got stuck at the logo again, but I'm going to keep working on it. At least I have a tool I can use.
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP. I cleared all my caches and did a factory reset. Then I installed a pre-rooted version of 6.2.1. It did a little reboot dance for a while and then came up into the OS!
Thanks a ton pokey9000. I'm happy to send a couple $$ your way.
fonetik said:
Edit3: I seemed to be stuck at the TWRP yellow triangle, I think I managed to install FireFireFire, and managed to get back into TWRP.
Click to expand...
Click to collapse
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
krelvinaz said:
Just in case someone else reads this... The Yellow Triangle is not TWRP... it is FireFireFire... TWRP by default is the blue themed screens you get after the FireFireFire icon and will start out saying TEAMWIN in Landscape mode.
BTW, good to hear you fixed the problem. You should edit the original post and change the Subject adding [SOLVED]
Click to expand...
Click to collapse
Sorry about the confusion. It was the FFF triangle, but the KF wasn't going into recovery when I held the power button down. I reinstalled with FFF using adb and it worked. Original post subject updated.
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
So I JUST got this thing today, and was trying to get android marketplace.
here is the list of things that have happened so far:
1. after moving vending.apk to apps folder, main GUI crashes and hitting the home button only switches through apps
2. decide to reboot since it is the next step for installing marketplace anyway
3. stuck in boot loop with shiny animations
4. manage to get TWRP installing
5. post says I need to hit 'reboot' on my kindle. I do.
6. stuck on yellow triangle, with all the drivers no longer working no matter what I do.
known fixes I've tried:
-uninstalling and reinstalling drivers
-rebooting computer and kindle multiple times
-selecting 'android driver' or whatever
-pressing the home button right after startup to try and get back into recovery mode
when looking in the device manager, it used to come up as 'kindle' with the yellow exclamation mark. now it only shows up as 'unknown device'
I JUST got this thing, and it wasn't from an official seller, so im basically on my own... anyone know what I should do?
EDIT: now the device manager IS saying 'android composite ADB interface' but it still wont how up in the kindle fire utility...
EDIT2: I was able to get it into restore mode, and get TWRP to pop up. I then have it clear the cache, and restored back to factory defaults. when I told it to reboot, it rebooted back to recovery mode. I then used the Kindle Fire Utility to set it to normal boot mode.
NOW, the problem im having is that it is stuck in a boot look with the animated 'kindle fire' logo.
Click to expand...
Click to collapse
Its working now! turns out that originally, all I needed to do was change the system permissions back to 755.
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
ra0ultortugas said:
Do you have TWRP installed?
If so this link may be helpful to you. I've read a lot of jayceooi's stuff; he may be able to help you.
http://forum.xda-developers.com/showthread.php?t=1430446&highlight=jayceooi
Click to expand...
Click to collapse
Yes, I have twrp 2.0 installed. It had worked fine until yesterday.
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
b63 said:
have a .android folder in your home dir ?
should have adb_usb.ini in it with this entry: 0x1949 and 0x18D1 - if not add it
then it should show up in kfu
to test manually:
cd with an (elevated) command promt to the tools folder of kfu and do:
adb devices - should return serialnumber and bootmode
Click to expand...
Click to collapse
When I went thru this procedure it says "list of devices attached"
and empty line (So no devices found).
I think my problem is drivers. Since my pc recognizes kf for several seconds only.
During those several seconds nothing really I can do.
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
wigsey said:
Use the liux method. Worked for me.
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
thanks. will give it a try.
Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...
When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.
linuxsociety said:
When you first try to power on the device and the amazon logo is still being displayed have you tried to get adb shell rooted or set it to recovery mode boot? Without the firefirefire bootloader it is going to be difficult to use adb unless you can at some point get adb to connect. Just out of curiosity, why didn't you also flash the boot loader instead of just flashing twrp? All I know to try is either kfu and keep hitting 0 to recheck device status and maybe you will get an Online+Rooted read out at some point before the system attempts to load & crashes.
Click to expand...
Click to collapse
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?
I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?
superbomb17 said:
I try to get into recovery mode, I'm not sure why i didn't use FireFireFire, this is my first tinker with an android device, I tried KFU from the instant i pressed power button to the black screen and its just unknown device. Is it broke for good?
Click to expand...
Click to collapse
So KFU is reporting unknown device? Sounds like you need to install the kindle fire USB drivers again. Is this on linux or on windows? unknown device means that it is recognizing a device, just doesn't know what device it is.. You need the correct drivers installed for the Kindle Fire, be sure to re-install those and try again.
When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.
Hausschuh said:
When I was stuck on Fastboot I just reinstalled the Drives and then changed the boot over KFU.
Click to expand...
Click to collapse
Did you try plugging it into another PC to see if that PC detects it?
superbomb17 said:
Hello,
I know there are many similar threads but i have a slightly different issue: I was editing /system/build.prop and did a reboot and i got stuck, right after the Kindle Fire logo pops up it goes black at the time the animation is supposed to start, computer reads it fine but ADB nor Fastboot will pick it up.KWRP also doesn't work, Any help?
IMPORTANT:
I have a backup of a TESTED and WORKING build.prop, if i can mount the Kindle in windows i will be able to apply the backup and fix it that way.
FYI:
I don't exactly care about keeping my data anymore, I just want it to turn on and be usable...
Click to expand...
Click to collapse
The fact that it goes black right after the kindle fire logo makes me think it's not stuck in fastboot (would be unlikely in a build prop edit) which is why you can't get fastboot to recognize; at the same time depending on where it's failing during the boot init adb won't load either.
superbomb17 said:
I have a crazy idea and i have no idea if it will work, but it's worth a shot:
After reading the Kindle Fire breakdown, I think i can take the kindle apart and get access to it's internal SD, my questions is this: can I somehow plug it into a computer?
Click to expand...
Click to collapse
First off; I seriously doubt you would be able to mount the sd from your PC properly. Rather than cracking the device I would try booting it from a factory cable, it should hopefully force fastboot mode at which point you should be able to resolve your issues.