Hi
I rooted my KF using kindle fire utility 0.9.5 -successfully.
After flashing gede ROM, KF is boot looping (there is a CM9 logo with the android guy flashing on the screen)---rebooting KF brings me back to the same screen
I have absolutely no access to the device. Kindle unbrick v.1--does not do anything, it gives: waiting for device
kindle fire utility gives: device offline
adb device gives: error: device not found
however, when i plug in the KF into my computer, under Device Manager--the KF is listed as "Galaxy" with a yellow triangle. No longer listed as kindle.
Please help! Thanks
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
soupmagnet said:
Does this sound like it may apply to you?
http://forum.xda-developers.com/showthread.php?p=25400963
&
http://forum.xda-developers.com/showthread.php?p=20317299
Click to expand...
Click to collapse
Thank you for your response. the KF is fully charged so power is not an issue. The biggest issue is I have no access to the device in order to do anything. Device cannot be recognized and it reads as a Galaxy in device manager
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
soupmagnet said:
Oh, that problem...
OK, read these
Driver information:
http://forum.xda-developers.com/showthread.php?p=23747671
Hardware ID information and reply from gedemis w/fix:
http://forum.xda-developers.com/showthread.php?p=25444709
Click to expand...
Click to collapse
Thanks soupmagnet. However still no progress. my device is still bootlooping.
How can I get into recovery while it is still bootlooping.
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
soupmagnet said:
I am quite (100%) certain the issue you are describing is a dead battery. It is the only issue known that causes the boot logo to flash like that. Your battery most likely died while asleep as some roms don't sleep or shut down properly.
I'm willing to bet if you pay attention and follow the steps from the links I originally gave you, you'll be able to fix your device.
Click to expand...
Click to collapse
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
mrslax said:
Qem is saying that as soon as the ROM was flashed and went into boot mode, the kindle kept bootlooping the ROM intro over and over.
Turning the KF on and off does nothing as the KF is trying to boot into the ROM but never gets past the intro screen (blue-ish android cartoon, CM9 type intro).
Because of the bootlop, there is no way to get into recovery physically and when connected to the computer, the kindle is being shown as a galaxy unit with no drivers, probably due to the flashed ROM.
Click to expand...
Click to collapse
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Qem can't post links so I posted her response instead.
"Again, thanks for your response. Yes I have clockwork Mod.
At first the KF kept bootlooping to the KF intro screen followed by a small portion of the ROM intro.
After multiple resets the intro just continues forever.
Here is a link to what it looks like. Its been like this even after powering off and on.
http://www.youtube.com/watch?v=npx9HIbF5Po"
Any ideas for bootloop
soupmagnet said:
My apologies. Apparently I misunderstood that portion of the first post and it's likely I'm just getting threads confused. So again, I apologize.
Based on this newly discovered information, I'm willing to bet you have Clockwork Mod recovery installed as opposed to TWRP. Yes? or No?
Click to expand...
Click to collapse
Please do you have any ideas re:bootloop. I am stuck.
Qem said:
Please do you have any ideas re:bootloop. I am stuck.
Click to expand...
Click to collapse
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
no way to mount TWRP
soupmagnet said:
Yes. I'll try to explain it in a way that you'll understand.
You have Clockwork Mod
You need TWRP
Click to expand...
Click to collapse
Thanks.
However did you see the you-tube link in chat #9?
I do not have any access to the device (in order to install TWRP) because no application (KF utility, Kindle unbrick, cmd prompt) can find the device: "ERROR: device not found".
The only place in which the device is found is in device manager but it lists the KF as "Galaxy".
May be I might be missing something...
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
I am having the same issue.
The problem is we flashed CWM, then a CM9 rom. Now just runs the aminamtion.zip boot screen and does nothing. it is unable to get into fastboot or CWM. inorder to flash another rom to install TWRP
KF has internal sdcard... cant mount TWRP
soupmagnet said:
You need to flash a different rom, like cm7, older version of cm9, or MoDaCo, just long enough to install TWRP. CWM will not install later versions of cm9.
You can mount your sdcard in TWRP, or if your drivers are working properly, you can use the "push" command in adb to transfer another rom.
Click to expand...
Click to collapse
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Qem said:
Thanks. I appreciate your help.
Pardon me I am desperate to get my KF in a working condition.
However the KF does not have an external SD card. Therefore to mount TWRP on the sdcard, I need access to the device. This access is what i dont have... The sdcard on the KF is internal and I cannot open any folders in the KF due to the bootloop
Click to expand...
Click to collapse
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
soupmagnet said:
No, you're misunderstanding me.
If you want to install the TWRP from inside the rom (i.e. using gscript or smirkit), you have to access recovery (in your case, CWM) to mount your sdcard. It will mount to your computer as an external drive, like a thumb drive. While mounted, transfer a rom that will work with CWM from your computer to your sdcard, then flash it in recovery to have a working rom to install TWRP.
Otherwise, if you want to use the command line method to install TWRP...
fastboot flash recovery /path/to/twrp2.1.img
...but considering KFU says "offline", that is out of the question unless you can get your drivers working.
Click to expand...
Click to collapse
So I was able to find drivers for the "Galaxy" (http://pastebin.com/nhbaaWMu) and installed it. This enabled KFU to recognize my device as "online".
However there are two issues (1) there is no access to the drive. it mounts like an external drive, but does not open/explore. like an external drive or USB would.
(2) when i try to go into recovery mode via KFU, KFU gets stuck.
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Qem said:
When you say fastboot flash recovery /path/to/twrp2.1.img, does the "path/to/twrp2."1-- mean the actual file path to where TWRP is located on my computer or is the "path/to" part of the cmd line input
Click to expand...
Click to collapse
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
still boot looping affter fastboot+twrp2
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
Thank you for your help thus fat, I appreciate it. However I still have not fixed the issue...
I tried it (actual path to file), it still said "waiting for device".
after a while, I held held power button to manually reboot, still nothing.
I also uninstalled and re installed the drivers... nothing
using KFU to boot into normal mode still returns "system cannot find the drive specified."
at wits end...
Pardon the typo..
soupmagnet said:
Actual path to file.
[Edit:] I've heard one of the roms here won't mount the sdcard in TWRP but I'm not sure which one. It may be gedeRom.
Click to expand...
Click to collapse
In prev post, I meant thanks for your help thus "far" and not "fat"
sorry for the typo
Related
Has anyone else experienced this problem:
I rooted my Kindle Fire using KFU 0.9.5. it came stock with kindle 6.3 software. The rooting process was a cinch, and I installed GO Launcher EX and the Google Play store and many other applications that work great. I haven't installed anything in the past few days. It's been working fine since I rooted about 3 weeks ago. Now, all of a sudden, I go to open my fire and there's an android guy with an "!" Icon. I reboot. Get the yellow splash screen, and it goes to rebooting options. I select normal reboot. Goes to yellow screen, Goes to Kindle fire splash screen, goes to lock screen. I unlock with my PW and the device immediately turns off. So I try again, this time using recovery. Same scenario. Third time I chose fastboot. Now it sticks on the yellow triangle screen and does nothing. How do I get it to boot up? Please help.
Thank you,
Kyle.
There was a new update from Amazon causing problems. You can flash a different rom or get the new update from the Amazon website and flash it, which will make everything 100% stock again without root.
soupmagnet said:
There was a new update from Amazon causing problems. You can flash a different rom or get the new update from the Amazon website and flash it, which will make everything 100% stock again without root.
Click to expand...
Click to collapse
Ok. I got it to boot into recovery mode. when I go to reboot system now, it goes to the yellow triangle splash, then kindle fire splash (orange fire lettering, not blue), then it brightens up, and goes to the lock screen. then immediately powers off. reboots into the yellow triangle splash, then an android robot with a loading bar that fills about 25%, to a mini android robot with an orange ! triangle.
If I have to flash a new ROM, which would you suggest?
Thank you,
Kyle.
Also, in the CWM recovery, there's a factory data reset. Will that undo the root? Or will it just wipe the memory?
???
Please advise. Currently my Kindle is stuck and I'd like to have it operational again. Even if that means re-rooting it. Does CWM Factory Reset wipe the root or just delete the memory on the device. Is that even the correct route to go? Is there an easier way to get out of this boot loop? KFU won't recognize the device because it won't power up all the way.
Thank you.
Factory reset will only wipe your user data.
To break root and restore to factory original you have to flash the latest update from Amazon.
Google "Kindle Fire software update", it will be on the Amazon website.
Change the file extension from ".bin" to ".zip" and put it on your sdcard.
Flash the new update.zip in CWM
soupmagnet said:
Factory reset will only wipe your user data.
To break root and restore to factory original you have to flash the latest update from Amazon.
Google "Kindle Fire software update", it will be on the Amazon website.
Change the file extension from ".bin" to ".zip" and put it on your sdcard.
Flash the new update.zip in CWM
Click to expand...
Click to collapse
Ok, but I still cannot add anything to my device because it will not start up in any mode, so my computer isn't recognizing the device. How do I get the computer to see the Kindle while it's "off"
I've read http://forum.xda-developers.com/showthread.php?t=1552547 and it's not very helpful in that regard.
Can you boot into recovery? If you can, you're halfway there.
soupmagnet said:
Can you boot into recovery? If you can, you're halfway there.
Click to expand...
Click to collapse
Soupmag, Sorry it took so long to reply; I had to pick my kid up from his mom's after work, and feed, bathe, and bed him, which is exhausting. I was at work earlier.
I can boot the device into recovery mode. The screen looks like this:
CWM-based Recovery v5. 0. 2 .7 FULL (By DooMLoRD)
Amazon Kindle Fire: v01-FINAL: Touch ed. by TUTRCHAOS
-reboot options
-Install zip from sdcard
-apply /sdcard/update.zip
-Wipe cache
-Backup and Rest.
-Mount & Strg
-advanced
-Power off
-Go Back
Build info...
-----------------------------------------------------------------------------
I don't know how to get a new .zip on the /sdcard. The PC doesn't see the device, so I can't transfer. It won't boot normally from this (reboot options are norm., fast, recov.) so I'm left with trying to reinstall the .zip, but I don't know if I need to wipe b4 I try that. Or, factory reset and hope it starts in Kindle launcher. What happens next. Sorry this is so long. I just don't want to screw it up even worse or possibly brick it.
Thanks for your help and patience.
-Kyle
soupmagnet said:
Factory reset will only wipe your user data.
To break root and restore to factory original you have to flash the latest update from Amazon.
Google "Kindle Fire software update", it will be on the Amazon website.
Change the file extension from ".bin" to ".zip" and put it on your sdcard.
Flash the new update.zip in CWM
Click to expand...
Click to collapse
BTW: I'd rather not factory resotre and re-root, but if I have to, than I will.
Thanks again.
Kyle
For some reason, the update will not install with CWM. I found that if you install TWRP, the update will install. I have used the commands on this page http://forum.xda-developers.com/showthread.php?t=1568340 to successfully install TWRP and then the update installs. After that, you will have to re-root.
When it says in those instructions:
adb push fbmode /data/local/fbmode
is that a command prompt window in the kindle dir? Or a KFU Option?
adb push fbmode /data/local/fbmode
Something completely different?
Please elaborate.
Thank you.
-Kyle
There's no need to reroot. I assume you're using Windows, right? Fix your drivers so you can use adb to push a new rom to your sdcard OR mount your sdcard in TWRP and transfer it like that.
Ok Awesome. Soupmag, awesome. I don't want to un-root. How do I update my Drivers? I had the adb drivers working fine yesterday. I didn't change anything. I'm using the KindleADB drivers and when it worked. I plugged it into the PC (windows vista) it would show under ADB devices on device manager.
Thank you,
Kyle
Well first, see if you can get into recovery and mount your sdcard (Kindle plugged into the computer of course)
Ok, I'm on recovery CWN-based Recovery v5.0.2.7 FULL
There's an Android Composite ADB interface under Android Phones in Device Manager
USB plugged in of course
Edit: When I shut the device down the Android Phone>Android Composite ADB Interface is removed from devices in device manager, so it has to be seeing the device, right?
kylebenton said:
When it says in those instructions:
adb push fbmode /data/local/fbmode
is that a command prompt window in the kindle dir? Or a KFU Option?
adb push fbmode /data/local/fbmode
Something completely different?
Please elaborate.
Thank you.
-Kyle
Click to expand...
Click to collapse
Command prompt window... from the directory where you unzip the files. Honestly, I don't really know if all the steps are required. All I know is that the process has worked for me.
kylebenton said:
Ok, I'm on recovery CWN-based Recovery v5.0.2.7 FULL
There's an Android Composite ADB interface under Android Phones in Device Manager
USB plugged in of course
Edit: When I shut the device down the Android Phone>Android Composite ADB Interface is removed from devices in device manager, so it has to be seeing the device, right?
Click to expand...
Click to collapse
While in recovery, select "mount sdcard". It should show up on your computer as external storage. Then use your computer to download whatever rom you want and transfer it to your sdcard. Just make sure its in .zip format.
[Edit:] If that doesn't work: http://forum.xda-developers.com/showthread.php?p=23747671 ...to fix your drivers.
Duplicate post, deleted. Stupid XDA app.
soupmagnet said:
While in recovery, select "mount sdcard". It should show up on your computer as external storage. Then use your computer to download whatever rom you want and transfer it to your sdcard. Just make sure its in .zip format.
[Edit:] If that doesn't work: http://forum.xda-developers.com/showthread.php?p=23747671 ...to fix your drivers.
Click to expand...
Click to collapse
Awesome! Do you recommend any particular ROM for stability? I don't want to have to do this every month lol
Thanks again
kyle
Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others
So I was messing with my kindle and it was trying to upgrade it to jelly bean and i guess i missed one of the steps and bricked it. I was going through the process of unbricking but when i was trying to do extract the update.zip folder it would not allow me to because it could not mount the SD card. All i need to figure out how to do is get the SD slot mounted. I am slowly picking up on command prompt and still trying to figure out adb shell but that is all i need help with.
I can unbrick it if someone knows how i can get my kindle to mount back to my computer!
Any advice or step by step for it would be very helpful, Thanks guys
Could you be more specific as to how your Kindle is "bricked"?
soupmagnet said:
Could you be more specific as to how your Kindle is "bricked"?
Click to expand...
Click to collapse
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
soupmagnet said:
Forgive my redundancy but please describe the "boot loop". Does it just sit at the Kindle Fire logo? Does the Kindle Fire logo flash, or change brightness? Does it make it to the boot animation? Black screen?
Click to expand...
Click to collapse
It will go to the kindle fire logo and then it would go to a black screen. It makes no boot animation. It will change some brightness. The words kindle fire are in white and blue. It flashes where is needs to do the boot animation and then just goes to a black screen
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
dontgoback4cody said:
I can only get to CWM. It does nothing but boot loop and does not go any farther then that. I can plug it into the computer and get the drivers connected and KFU can recognize it. when i put it in cwm this is the first thing i see
Click to expand...
Click to collapse
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
acii22 said:
The image shows a very low battery. The behavior you describe suggests a low battery. You're in a boot loop caused by no power.
Let it sit for several hours (better...over night).
Edit:...ie. let it sit with your charger attached.....
---------- Post added at 11:14 AM ---------- Previous post was at 10:46 AM ----------
It might be a good idea to consider installing TWRP rather than using CWM. CWM is known to have problems with some newer ROMs.
Click to expand...
Click to collapse
I have tried to install it from KFU but it is always has a problem doing so. I let it charge over night and it is still doing the same thing. Here is what is says when i try to install twrp
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
soupmagnet said:
Replace the TWRP.img that comes with KFU, with the ACTUAL one from the TWRP website.
Click to expand...
Click to collapse
Ok i did that but it still will not let me connect the kindle to the computer it keeps giving me sdcard errors. any idea how to fix the sd card issue?
Hey were u able to fix it??
Had the same problem with mine when I used TWRP to format my SD card..but was able to solve it..
What I did was a very simple thing..got the kindle recognised as a drive..used windows partition manager to format it
It worked.. I tx the stock and installed it
Try it and let me know
Sent from my MB526 using Tapatalk 2
I had the same problem before and only had to reboot the kindle.
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
dontgoback4cody said:
Nothing is working. i have given up all hope. Like this is crazy. It is screwed up for good. I cant get it to mount. If anyone wants to take a shot at it just shoot me a pm with an address and we can discuss something about trying to fix it or what the hell i did to it. Its crazy! and really messed up.
Click to expand...
Click to collapse
I have an Idea. If you have fastboot working on your computer. You could try flashing a rom from your computer by typing
fastboot -w(wipes device)
fastboot update <path to rom> (flashes rom)
If it works, you can then fix the sdcard easier with adb/shell/partition manager. Its worth a shot.
I also found this on a website
ROM update without SDcard
If you don't have an sd card, or your slot is broken you can try this trick, but you will need a custom recovery like Clockwork.
Boot up your phone to recovery. And move your rom file to the adb directory, and start a command line ( cmd )
adb shell
mount data
adb push D:\custom_rom.zip /data/
Wait until the push finised, and restart your device to recovery again with "adb reboot-bootloader"
mount data
mount /data /sdcard ( mount the data folder into your sdcard folder, so your recovery will think that you have an sdcard installed )
Locate the ROM .Zip file you wish to flash.
Confirm the flash by following the on-screen instructions (ie: pressing the trackball, pressing the call button, etc.)
If no errors arise during the flashing process then the ROM flash was successful, Reboot the device.
With some root file explorer, remove the rom file if you don't need it anymore, to free up space.
Or use adb to remove the custom recovery
adb shell rm data/custom_rom.zip
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Then you need a factory cable to get into fastboot.
dontgoback4cody said:
I will give it a shot. Only thing is i dont think there is even any software on here. when i try to get it into fastboot mode here is what it says.
Click to expand...
Click to collapse
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
kishorev said:
Hey i had the same exact problem and i had posted what i did to recover it.. did you try..
I know it sounds too simple.. but it worked for me
sometimes its the way you have formatted ur sd card
Click to expand...
Click to collapse
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
soupmagnet said:
When you see the error message:
Code:
- exec '/system/bin/sh' failed: No such file or directory (2)
It means you don't have access to the shell in order to switch bootmodes and access recovery, which is needed to fix this type of problem. The only way to change bootmodes without access to the shell, is in fastboot. Unfortunately, you need access to the shell to change the bootmode to fastboot as well...catch-22.
For this, you need a factory cable. The factory cable will tell the device to boot into fastboot without the need for a shell. Even with a factory cable, and access to recovery, you'll still likely need to either reformat, or repartition your sdcard in order to get it to mount.
Click to expand...
Click to collapse
You are right..
But i too was had the same msg when i was trying to fastboot it.. but then it worked.. I had formatted it and then tx the stock rom and flashed it..
Probably i missing something here..
Anyways thnx
Can't mount SD card on kindle fire
I was in a similar situation and after reading the various forums i came across this action "hold down the power button until the kindle goes off and continue to hold for about 30 seconds I believe this resets the kindle and then tick debugging and mount usb storage the sdcard will open on your pc" and then you can go from there. Worked for me so good luck.
Ive been working on this kindle fire for the last 2-3 days.Here's what I know I can do:
I can issue commands in fastboot mode
I can issue commands in adb mode
I can even mount the kindle to my PC as a SDcard (when I give it the command in adb)
I checked the partitions and they seem to be stock, (ext4 on data, cache ect.) I ran the oem command anyways just to make sure.
However it appears nothing within TWRP actually works. Wiping anything just comes back with a failed message (right after verifying file systems), trying to load a ROM will act like it doing something (200mb file done in 2seconds) but really doesnt. Im not really sure where to go from here, it just appears that there is nothing on the kindle, no OS or otherwise, and I cant seem to find a way to load one.
Thanks in advance!
Which version of TWRP are you using?
Thepooch said:
Which version of TWRP are you using?
Click to expand...
Click to collapse
2.2.1, I believe its the latest version.
You have some kind of mounting issue use soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Thepooch said:
You have some kind of mounting issue use soupkit http://forum.xda-developers.com/showthread.php?t=1850038 .
Click to expand...
Click to collapse
That did the trick, kindle back up and running. Thanks a ton!
Good time of the day to everyone. I have the problem with my Kindle Fire first gen. Please tell me the solution If someone knows. First was the problem with picture on the screen then I changed the controller of LVDS and then image became normal. But first I thought that this problem is software and though I almost didn't see nothing on the screen I tried to solve the problem in TWRP. When display started to show good picture I did see that tablet do not boot on. So now I can start TWRP recovery but in the log I see that tablet cannot mount sd-card. This is half of the proble. I saw the solution on this forum how to mount by ADB and some command from command line. But the computer also do not see the tablet. The tablet shoes in device manager just from the begining of the booting for about 2 sec. And I cannot do something. Is there any solution in this situation?
Ichigo said:
You can't mount? Take a look at this: http://forum.xda-developers.com/showthread.php?t=1949372
Click to expand...
Click to collapse
Thanks, I will. The problem is that I cannot do any adb which needs that tablet is connected to computer and recognized. My computer see thee tablet only in the time of booting in the begining.
One question, is it possible to write all commands wich I see in instractions for unbricking kindle in native terminal of the TWRP?
Is it possible to solve the problem with "can't mount /sdcard (invalid argument)" from TWRP itself without ADB, I mean computer. Then I could
make some BAT file wich will handle connection with KF in the begining of booting and write update.zip to sdcard on the tablet, then I could
to flash it.
Please help! I can PAY for the real help by PayPal.
toly084 said:
One question, is it possible to write all commands wich I see in instractions for unbricking kindle in native terminal of the TWRP?
Is it possible to solve the problem with "can't mount /sdcard (invalid argument)" from TWRP itself without ADB, I mean computer. Then I could
make some BAT file wich will handle connection with KF in the begining of booting and write update.zip to sdcard on the tablet, then I could
to flash it.
Please help! I can PAY for the real help by PayPal.
Click to expand...
Click to collapse
Here`s your answer http://forum.xda-developers.com/showthread.php?t=1850038 a live usb with soupkit. If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Thepooch said:
Here`s your answer http://forum.xda-developers.com/showthread.php?t=1850038 a live usb with soupkit. If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Click to expand...
Click to collapse
Thank you very much. I see that Soupkit is just what I needed. First I need to install Ubuntu, then will try to recover my KF wich I made two of them not working. I hope one will work. I thought I have no luck and only way to reball a flash from another board of KF wich I have as spare.
Thepooch said:
If you want help and you can catch me online I would be happy to assist and it wont cost you a dime just time.
Click to expand...
Click to collapse
Dear Sir. So, I tried SoupKit. The same situation as with ADB in Windows. My KF can be seen just in the begining of the booting.
And this is not enaugh time to do something. Also I wanted to ask that man wich made SoupKit, but for now it is not allowed for me to pos there.
toly084 said:
Dear Sir. So, I tried SoupKit. The same situation as with ADB in Windows. My KF can be seen just in the begining of the booting.
And this is not enaugh time to do something. Also I wanted to ask that man wich made SoupKit, but for now it is not allowed for me to pos there.
Click to expand...
Click to collapse
Boot into recovery and see if your computer will detect it.
soupmagnet said:
Boot into recovery and see if your computer will detect it.
Click to expand...
Click to collapse
Thank you for the answer, I tried to post in your theme but it wasn't allowed.
The computer see my KF only in the begining of the booting 2-3 sec. I also tried your SoupKit in the Ubuntu, the same problem,
I just can flash bootloader, recovery and that's all.
toly084 said:
Thank you for the answer, I tried to post in your theme but it wasn't allowed.
The computer see my KF only in the begining of the booting 2-3 sec. I also tried your SoupKit in the Ubuntu, the same problem,
I just can flash bootloader, recovery and that's all.
Click to expand...
Click to collapse
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
soupmagnet said:
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
Click to expand...
Click to collapse
I'm sorry, but I can't do this right now. Notebook on wich I installed Ubuntu I left on the work and tablet also. Tomorrow I will try to do so. I will explain what happened. First I had a problem with picture on the screen, I hardly could see what is on the screen. I thought it was the software problem and try in the recovery to solve the problem. But as I couldn't see what I do, I done something what bricked my KF. The problem with picture was solved by reballing the LVDS controller. And now I have a tablet wich cannot mount system, data, sdcard what I saw in log of TWRP. And also tablet can't be seen now by computer as it was and I cannot recover tablet by ADB. I also asked before if is it possible to do something in TWRP in terminal that to solve the problem with mount of partitions.
toly084 said:
I'm sorry, but I can't do this right now. Notebook on wich I installed Ubuntu I left on the work and tablet also. Tomorrow I will try to do so. I will explain what happened. First I had a problem with picture on the screen, I hardly could see what is on the screen. I thought it was the software problem and try in the recovery to solve the problem. But as I couldn't see what I do, I done something what bricked my KF. The problem with picture was solved by reballing the LVDS controller. And now I have a tablet wich cannot mount system, data, sdcard what I saw in log of TWRP. And also tablet can't be seen now by computer as it was and I cannot recover tablet by ADB. I also asked before if is it possible to do something in TWRP in terminal that to solve the problem with mount of partitions.
Click to expand...
Click to collapse
First we need to see if Linux is detecting your device when plugged into USB, hence the 'lsusb' command. We need to get the communication problem resolved before you can fix your mounting issues. As far as using TWRP's command line to fix the partitions, not likely. I've tried it before and it didn't work out.
It's possible, for whatever reason, your device is reporting a different product ID than what is configured in the udev rules, but we probably won't know for sure until we have access to 'lsusb'.
soupmagnet said:
First we need to see if Linux is detecting your device when plugged into USB, hence the 'lsusb' command. We need to get the communication problem resolved before you can fix your mounting issues. As far as using TWRP's command line to fix the partitions, not likely. I've tried it before and it didn't work out.
It's possible, for whatever reason, your device is reporting a different product ID than what is configured in the udev rules, but we probably won't know for sure until we have access to 'lsusb'.
Click to expand...
Click to collapse
Tomorrow I will try "lsusb" and will write an answer.
toly084 said:
Tomorrow I will try "lsusb" and will write an answer.
Click to expand...
Click to collapse
Good time of the day. As I thought computer do not see the device.
But now I can remain in fastboot mode by the comman "fastboot getvar product". And SoupKit see the device in fastboot. Is it possible somehow to transfer the firmware file to the KF?
toly084 said:
Good time of the day. As I thought computer do not see the device.
But now I can remain in fastboot mode by the comman "fastboot getvar product". And SoupKit see the device in fastboot. Is it possible somehow to transfer the firmware file to the KF?
Click to expand...
Click to collapse
If SoupKit sees the device in fastboot as you say, use it to install recovery and boot into it
soupmagnet said:
If SoupKit sees the device in fastboot as you say, use it to install recovery and boot into it
Click to expand...
Click to collapse
I have FFF booty v1.4a installed and TWRP recovery installed.
I think because of the problem of the mounting of sdcard / system / data computer do not see the device.
toly084 said:
I have FFF booty v1.4a installed and TWRP recovery installed.
I think because of the problem of the mounting of sdcard / system / data computer do not see the device.
Click to expand...
Click to collapse
Use fastboot to reinstall TWRP and check 'lsusb' again.
soupmagnet said:
Use fastboot to reinstall TWRP and check 'lsusb' again.
Click to expand...
Click to collapse
By the help of your instructions from the another post about mounting of SYSTEM DATA CACHE and SDCARD,
now all partition can be mounted only SDCARD won't. But computer as it was before do not see device in normal mode,
just in fastboot. All work concirning mounting SYSTEM DATA CACHE was made from the terminal of TWRP.
soupmagnet said:
Okay, boot into Ubuntu, let the device boot up normally and enter the following in the terminal...
Code:
lsusb
Let me know what the output is
Click to expand...
Click to collapse
In the list there is no the device. Only standart wich belongs for notebook hardware. If I could mount sdcard then I could flash update.zip from fastboot, but I can't.
toly084 said:
By the help of your instructions from the another post about mounting of SYSTEM DATA CACHE and SDCARD,
now all partition can be mounted only SDCARD won't. But computer as it was before do not see device in normal mode,
just in fastboot. All work concirning mounting SYSTEM DATA CACHE was made from the terminal of TWRP.
Click to expand...
Click to collapse
Your mounting issues shouldn't have anything to do with whether or not Linux will detect your device. Are you using a LiveUSB, VM, or full Linux boot?
soupmagnet said:
Your mounting issues shouldn't have anything to do with whether or not Linux will detect your device. Are you using a LiveUSB, VM, or full Linux boot?
Click to expand...
Click to collapse
I installed full Ubuntu. I do not know why tablet can't be seen in linux.