Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
rocketfans14 said:
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
Click to expand...
Click to collapse
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
stunts513 said:
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
Click to expand...
Click to collapse
I have checked the md5sum of the files using a program I found here on xda. I'll try to do the cd from file right now and I'll let you know how that went. Thank you for the quick reply.
Ok, I got it up to the TWRP recovery screen. But how do I continue to flash the stock in step 4 after installing cm10.2 and gapps? Also, I do not have a factory fastboot cable.
EDIT
After installing CM10.2 and gapps, I hit reboot on TWRP and has 'unfortunately, com.android.phone has stop working' message popped up on the screen. Is it because I haven't continue to the section "Flashing back to stock" in step 4?
EDIT2 (I don't think this is related to the bootloader problem but I would like some assistance)
I rebooted again and didn't get the 'unfortunately' messages again. However, when I plug it into my computer, the device doesn't charge when it is active but charges when I put it into sleep mode. Is there any way to fix this issue?
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
stunts513 said:
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I see. Where can I find CM11 and how do I flash it? Is it just:
1.put the file into /sdcard
2.reboot into TWRP recovery
3.uh, wipe memory?
4.install CM11
5.reboot
correct me if I'm wrong. I wasn't sure if these are the correct steps because there are a lot of different guides and most of them don't have the same steps.
P.S. Since the kindle only has 8gb, is there a way to free up more memory on the device other than the needed memory space for the os?
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
stunts513 said:
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
"Factory reset to go to?" Also, I should put CM11 zip and gapp in sdcard right?
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I'm sorry if this sounds stupid but how do I factory reset my device? I've been working on rooting to installing bootloaders and finally at the point of getting android os on it non stop. Brain cells are dying rapidly...
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
stunts513 said:
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thank you so much for all the help. Everything went smoothly after your advises.
Update: It was running well for a while until when it ran out of battery and I recharged it, it won't boot into CM anymore. It just boots into TWRP recovery even if I pressed the option to reboot system and normal boot... What should I do?
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I wiped what you said and tried to flash the rom and gapp but when booting, it will still boot into TWRP.
I'll briefly explain what I did prior to the issue.
After everything was all set up, I went to see if there were any updates which there was, the nightlies for CM 11 0518. I hit download and after download was complete, I hit the option "install and reboot". After the orange kindle fire logo came up and briefly after, the blue one, it boot into TWRP. I tried to reboot again but still no changes. So I went ahead and did a factory reset and flashed the two zip files again. The devices still boots into TWRP... I have no idea what to do afterwards and here I am requesting assistance from someone who knows things like these better.
Have you tried wiping internal storage? That's a last resort, maybe somehow your selinux xattribs got messed up. A internal storage wipe would clear them. But it will wipe your sdcard area so backup anything you want to keep over adb first.
Sent from my Amazon Tate using Tapatalk
I haven't tried wiping the internal storage yet. How do I backup over adb? Also,since you said this might be a last resort method, if it fails, is there no other way to fix it? Not even restoring back to its out of the box state and start all over again with rooting and installing bootloaders etc?
PS. I don't know if it is related to what you are talking about at all but when I plug it into my computer, it doesn't recognize my kindle fire.
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
So in short, to backup, I can just use a adb pull command?
After that, I am lost. I don't really understand what you are saying...
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
So the steps are something like:
Backup with adb
Wipe internal storage
Flash the rom and gapp?
Alternative solution:
Restore the whole device
Repeat the root process
Installing the 2nd bootloader again
Flash rom and gapp
And the rest is if I were to restore the device, it is more flexible to use kindle fire first aide than to use TWRP?
Related
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
Hello,
at first, sorry for my bad english, I'm from Germany
I want so sell my tablet and the customer wanted me to install CM10.1 on the Kindle Fire 2.
So I rooted it, installed TWRP and CM10.1 with GAPPS. This all was done correctly, but when
I looked in Windows on sd card, I saw that there was a lot of data left. So I thought, you could
wipe internal storage to remove all your data.
Now, I booted up again, but suddenly, there were no widgets left, wallpaper is now black and
which is most important: the task bar (this thing on the bottom of the screen) is away. So cannot
enter my homescreen, if I am on the apps screen.
I already installed CM10.1 a secound time, but the result is equal.
Can you help me with this problem ?
Thank you!
K3n$! said:
Hello,
at first, sorry for my bad english, I'm from Germany
I want so sell my tablet and the customer wanted me to install CM10.1 on the Kindle Fire 2.
So I rooted it, installed TWRP and CM10.1 with GAPPS. This all was done correctly, but when
I looked in Windows on sd card, I saw that there was a lot of data left. So I thought, you could
wipe internal storage to remove all your data.
Now, I booted up again, but suddenly, there were no widgets left, wallpaper is now black and
which is most important: the task bar (this thing on the bottom of the screen) is away. So cannot
enter my homescreen, if I am on the apps screen.
I already installed CM10.1 a secound time, but the result is equal.
Can you help me with this problem ?
Thank you!
Click to expand...
Click to collapse
Did you try going into TWRP to wipe cache, dalvik, factory reset and system, before reflashing 10.1?
There is one good thing, you are still booting after wiping internal storage.
If that doesn't work, it sounds like you will need to restore back to stock and flash again. Read this post, then follow the link to Kindle first aide.
http://forum.xda-developers.com/showthread.php?p=38768721
How to get adb work in TWRP?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Did you try going into TWRP to wipe cache, dalvik, factory reset and system, before reflashing 10.1?
There is one good thing, you are still booting after wiping internal storage.
If that doesn't work, it sounds like you will need to restore back to stock and flash again. Read this post, then follow the link to Kindle first aide.
http://forum.xda-developers.com/showthread.php?p=38768721
How to get adb work in TWRP?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Hey,
thanks for your reply.
I will test this again, but i think I done this already this way ( wipe cache, dalvik, factory reset and system, before reflashing 10.1)
The secound problem is that I didnt backuped my stock rom. I want to sell it and I thought the customer might restore my data.
So I skiped this step.
I got adb through Tweezermod (cordless) > http://forum.xda-developers.com/showthread.php?t=2106463
Also, I got no Fastboot cable (sale).
Now, I will read your linked post
Thanks for your help
Hey,
currently, I want to restore the stock rom and I followed your linked instruction.
At point 15, I don't know what I have to do.
Activating adb doesn't work either.
Can you help ?
Step 15 reads like all you are doing is running the First Aide program from the shortcut you created on the desktop.
Or are you talking about option 15?
Sent from my Amazon Kindle Fire2 using Tapatalk HD
No, I meant point 15 in the instruction. The problem is (i think) that adb is not running correctly.
Nothing happens
Now, the customer has the kindle. So I help him to get his kindle running fine
He asks if he can continue at point 15 when his fastboot cable arrives.
Did I understand correctly fastboot cable = adb is working without complicated command line actions ?
K3n$! said:
Did I understand correctly fastboot cable = adb is working without complicated command line actions ?
Click to expand...
Click to collapse
"fastboot cable" = put the device in fastboot mode
You still need working drivers.
And what is this fastboot mode exactly ?
K3n$! said:
And what is this fastboot mode exactly ?
Click to expand...
Click to collapse
K3n$!,
may want to read the FAQs at http://forum.xda-developers.com/showthread.php?t=2228539.
Don't take it personal, but I'm wondering how you have been able to install TWRP recovery at all without knowing what the fastboot mode is...
@E_Zatopek: There is no question/answer that tells me what this fastboot itself is.
It always shows how to get fastboot mode but doesn't mention what this mode excatly is.
Maybe, I missed to see it.
K3n$! said:
@E_Zatopek: There is no question/answer that tells me what this fastboot itself is.
It always shows how to get fastboot mode but doesn't mention what this mode excatly is.
Maybe, I missed to see it.
Click to expand...
Click to collapse
OK, got your point.
Let me try to explain: "fastboot" is a client-side program (included in Google's Android SDK and many other Android toolkits) that can communicate with an Android device after this has been booted up in "fastboot mode". As a prerequisite to facilitating this communication, you have to install and properly setup "adb drivers" first.
In fastboot mode you can manipulate the device's partition directly: you can erase or format partitions and - most important for us, who want to install custom ROMs and have to occasionally restore the previous state - flash new data to the boot, recovery and/or system partitions.
If you enter "fastboot" at the Windows/Linux command shell, the resulting output should give you a better idea of what fastboot can do for you.
There are many different ways to boot up a device in fastboot mode - some of them device-specific (like pressing and holding the volume up or down button when switching the device on), some of them pretty generic.
You should really read as many forum threads discussing the use of fastboot and related problems as possible before actually using it on your device. Working with fastboot always brings the risk of bricking your device.
hello people,
about this guide http://forum.xda-developers.com/showthread.php?t=2128175
steps 3 and 4 do not work.
Where should I put the files that I download?
whitesalt said:
hello people,
about this guide http://forum.xda-developers.com/showthread.php?t=2128175
steps 3 and 4 do not work.
Where should I put the files that I download?
Click to expand...
Click to collapse
correct the question
fastboot does not respond.
the command adb devices yes
why???
whitesalt said:
correct the question
fastboot does not respond.
the command adb devices yes
why???
Click to expand...
Click to collapse
The device has to be in fastboot mode to show up via fastboot.exe
Regarding your issues flashing the bootloader/TWRP, try using FireFlash, an apk that automates the process of flashing the exploitable bootloader and TWRP, using the freedom boot.img and TWRP files from the thread you mentioned in your post They can be anywhere on the device storage.
Stick the FireFlash apk on the device storage, install it with ES File Manager, plug in the freedom boot.img into the boot slot and the TWRP img into the recovery slot, check the box to flash 8.1.4 bootloader if you aren't already using it (red letters will warn you if you aren't) and check apply stack override. also check disable auto recovery update. execute the flash, and you're done.You can also use FireFlash to easily update TWRP later on if you like.
humpster said:
The device has to be in fastboot mode to show up via fastboot.exe
Regarding your issues flashing the bootloader/TWRP, try using FireFlash, an apk that automates the process of flashing the exploitable bootloader and TWRP, using the freedom boot.img and TWRP files from the thread you mentioned in your post They can be anywhere on the device storage.
Stick the FireFlash apk on the device storage, install it with ES File Manager, plug in the freedom boot.img into the boot slot and the TWRP img into the recovery slot, check the box to flash 8.1.4 bootloader if you aren't already using it (red letters will warn you if you aren't) and check apply stack override. also check disable auto recovery update. execute the flash, and you're done.You can also use FireFlash to easily update TWRP later on if you like.
Click to expand...
Click to collapse
found within the forum
I open Fireflash and find the inscription: warning: current bootloader not kfhd8-u-boot-prod-8.1.4.bin.
Can I switch back?
FlashBoot I click to go into the "flash install script" or "reboot into recovery"?
I can also directly follow the program? reliable?
thanks
is stuck to the initial written "kindle fire" orange. help!
If you are not seeing the blue logo, then the 2nd-bootloader / freedom boot / twrp img is not installed correctly.
I will post a small set of instructions in a few mins. But they require you have a working fastboot connection.
Sent from my XT926 using Tapatalk 2
Hashcode said:
If you are not seeing the blue logo, then the 2nd-bootloader / freedom boot / twrp img is not installed correctly.
I will post a small set of instructions in a few mins. But they require you have a working fastboot connection.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
apparently neither do fastboot adb recognizes the device!
how can I check better?
I remember that already fastboot did not work before, so I installed Fireflash and finally brick
whitesalt said:
I remember that already fastboot did not work before, so I installed Fireflash and finally brick
Click to expand...
Click to collapse
Have you tried using KFFA found here:
http://forum.xda-developers.com/showthread.php?t=2096888
It has MANY options for fixing USB drivers, installing 2nd-bootloader, etc.
Hashcode said:
Have you tried using KFFA found here:
http://forum.xda-developers.com/showthread.php?t=2096888
It has MANY options for fixing USB drivers, installing 2nd-bootloader, etc.
Click to expand...
Click to collapse
nothing happens! the program fails to work because it waits for the device that does not find! I ask amazon replacement?
whitesalt said:
nothing happens! the program fails to work because it waits for the device that does not find! I ask amazon replacement?
Click to expand...
Click to collapse
What operating system are you using on your computer?
If using Windows 7 or 8: are your Kindle HD 8.9 drivers up to date? Check this thread out to uninstall and reinstall the proper drivers: http://forum.xda-developers.com/showthread.php?t=2069117 (it references another thread that helps uninstall "phantom" device drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361)
We need a bit more information in order to help you out.
GenghisKhan67 said:
What operating system are you using on your computer?
If using Windows 7 or 8: are your Kindle HD 8.9 drivers up to date? Check this thread out to uninstall and reinstall the proper drivers: http://forum.xda-developers.com/showthread.php?t=2069117 (it references another thread that helps uninstall "phantom" device drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361)
We need a bit more information in order to help you out.
Click to expand...
Click to collapse
hello,
I use windows xp and windows 7, the guide can not use it because the kindle is blocked! the day after tomorrow comes the new kindle you help me not to make mistakes? I listed exactly what is right to do? remember that the error was born from the fastboot that did not work! thanks
whitesalt said:
hello,
I use windows xp and windows 7, the guide can not use it because the kindle is blocked! the day after tomorrow comes the new kindle you help me not to make mistakes? I listed exactly what is right to do? remember that the error was born from the fastboot that did not work! thanks
Click to expand...
Click to collapse
My point is that it is crucial to have proper drivers present and working BEFORE you even get into fastboot mode.
I would recommend you go back and re-read Hashcode's thread. Back up your system files before modifying anything, so you can go back if anything goes wrong.
GenghisKhan67 said:
My point is that it is crucial to have proper drivers present and working BEFORE you even get into fastboot mode.
I would recommend you go back and re-read Hashcode's thread. Back up your system files before modifying anything, so you can go back if anything goes wrong.
Click to expand...
Click to collapse
but if something goes wrong, without the fastboot mode you can not recover anything the same right?
Surely my mistake was not to test the fastboot. Why can not I work in the device?? for drivers?
I think my kindle volume button is broken. Every time I reboot the device it always enter safe mode.
I reflash the device to stock but the problem still appear, now I want to back to custom rom but I cannot get in to TWRP (the volume up button not working) so I stuck at blue logo.
Fastboot and ADB still working.
Is there any way to install CM10.1 using fastboot/adb only without TWRP?
You can still get into twrp without using volume button, you just need to run adb on your PC with your kindle connected and adb enabled as follows:
adb reboot recovery
Or try
adb shell "su -c 'reboot recovery'"
If it is the second one u can run it from a mobile terminal app on the kindle, just take off the adb shell part.
Once you have cm installed I know for a fact you can reboot into recovery from the shutdown menu, but u have to enabled developer stuff on cm after u flash it. You can tell I'm half asleep when I can't remember the proper term and say "stuff"... Anyways if you want feel free to try what I suggested or search around for what I suggested. I am going to bed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
TWRP problem
Hello people
First of all thanks Hashcode for putting so much effort into it
I ran into a little bit of problem
First off regarding the BLUE LOGO
I first get ORANGE then BLUE n then ORANGE again with the animation
Second regarding TWRP
I can't seem to get into recovery while pressing the volume up button
It gives me a bad boot kinda error n then takes me to Fastboot mode
I hope you guys can help me out with this
Thanks
EDIT
Thanks to the above post i was able to enter recovery
Now it gives me two options
1 reboot kindle
2 reset to factory defaults
Question : How do i install CM 10.1 from there
You apparently didn't follow the instructions in the 2nd bootloader thread very well because you seem to have skipped a step.
To further explain what soupmagnet means, you didn't flash twrp to your recovery, that's the stock amazon recovery and is completely useless.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To further explain what soupmagnet means, you didn't flash twrp to your recovery, that's the stock amazon recovery and is completely useless.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I entered every command perfectly
Do i need to re flash TWRP????
If so , HOW???
Background
1) got this kindle fire for my mom a month or two after it first released, the dev scene was very new back then and I did a basic root so that I can sideload some stuff onto it to get around the amazon store
2) adb and fastboot should have been installed back then (i recall doing an adb push)
------
Problem
1) I needed to flash a new rom that'll properly support youtube for my mom. After some reading, it seemed like the first thing i need to do was install FFF and TWRP
2) I downloaded the KFU, hit install FFF and then it reboot to the orange kindle fire logo (not blue, not flickering or anything else)
3) from here, I can't really do anything. the KFU and unbrick utility both cannot detect it (error: device not found or "waiting for device")
4) I followed a thread and went into the .android folder to add the needed lines to a file, and then to the folder in programsx86 and added a few lines, this made it so when i plugged in the stuck logo my computer made a badoop sound (which it didn't before)
5) If i try typing fastboot or adb into my cmd prompt, it just says its not recognized as a command even though i'm sure it should be installed
At this point, from my understanding...
I need to get into fastboot somehow (i'm not sure if i need a factory cable to do this)
and then try to go from there?
I'm very unfamiliar with working with fastboot and adb, i only have previous experience with my galaxy phones which never used any of these, so clear instructions are greatly appreciated.
Sorry for the long post,
Thank you for any help
L
To use adb or fastboot you need to cd ("change directory") in command prompt.
Ex. cd: C:\Users\Admin\Program Files.... etc, ad nauseum to wherever you installed KFU. You can also open up the folder where kfu is installed and drag adb.exe or fastboot.exe directly into command prompt.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
To use adb or fastboot you need to cd ("change directory") in command prompt.
Ex. cd: C:\Users\Admin\Program Files.... etc, ad nauseum to wherever you installed KFU. You can also open up the folder where kfu is installed and drag adb.exe or fastboot.exe directly into command prompt.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I feel silly...thanks. I managed to get it to boot up again.
Now to proceed forward and flash another rom, i just wanted to double check something
Follow these videos: http://forum.xda-developers.com/showthread.php?t=2150317
Use KFU to install TWRP
Install FFF
And from there its just like normal where i reboot into recovery, wipe everything, flash the zip, and then off i go?
Thanks again for your help
Yep! One quick tip: It's always a good idea to make a backup before flashing anything, just in case of something possibly going bad.
Sent from my Nexus 7 using Tapatalk
projectvirtue said:
I feel silly...thanks. I managed to get it to boot up again.
Now to proceed forward and flash another rom, i just wanted to double check something
Follow these videos: http://forum.xda-developers.com/showthread.php?t=2150317
Use KFU to install TWRP
Install FFF
And from there its just like normal where i reboot into recovery, wipe everything, flash the zip, and then off i go?
Thanks again for your help
Click to expand...
Click to collapse
The purpose of the thanks button was not for you to say thanks in a post.
Sent from my Amazon Kindle Fire using xda app-developers app
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.