Related
Hi all!
Without much ado I am presenting you this repo for CM10 that lets you build somewhat functional CM10 ROM for Kindle Fire HD 8.9".
(Obviously this is not end-user friendly yet. If you don't know how to compile CM10 yourself, you are not a target audience for this yet, sorry. Many things don't work to make it viable main ROM yet anyway)
Build instructions (assuming you met all other CM10 build dependencies).
Download code:
Code:
mkdir android/system
cd android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/bowser-jb/local_manifest.xml
repo sync -j16
Build:
Code:
. build/envsetup.sh
lunch cm_bowser-userdebug
. vendor/cm/get-prebuilts
mka bacon
In the out/target/product/bowser output dir you'll have two important files generated:
recovery.img and cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip
For the first install only:
Step 0; Connect kindle to your computer, have android sdk installed and adb and fastboot in the path.
Step 1: (very important) Back up raw partitions from kindle responsible for recovery, boot and system.
(this requires root, though root-less installation is also possible, you will need the backups to return to stock!)
Code:
adb shell su -c "chmod 777 /dev/block/*"
adb pull /dev/block/mmcblk0p9
adb pull /dev/block/mmcblk0p10
adb pull /dev/block/mmcblk0p11
[code]
Save these block images.
Step 2: Prepare and run CWM:
[code]
rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\x00\x50\x7c\x80' >>/tmp/stack ; done
adb push /tmp/stack /data/local/tmp/
adb shell su -c "dd if=/data/local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot bs=6519488 seek=1"
adb shell su -c "chmod 777 /cache"
adb push /path/to/cm-10-XXXXXXXX-UNOFFICIAL-bowser.zip /cache/
adb shell su -c "echo 0 > /sys/block/mmcblk0boot0/force_ro"
adb shell su -c "echo -n 3 | dd of=/dev/block/mmcblk0boot0 bs=1 count=1 seek=4104"
fastboot flash recovery /path/to/recovery.img -i 0x1949
This last command will stop waiting for the fastboot device to appear. Do not unplug the kindle from USB.
Now reboot kindle: either power it off and on via it's GUI, or do adb reboot from a different terminal session (do not interrupt fastboot command still waiting!)
You'll see a "fastboot mode" on the screen and fastboot command started earlier will finally finish after writing the image onto the kindle.
Reboot kindle again via fastboot:
Code:
fastboot reboot -i 0x1949
This will reboot you into CWM recovery
Step 3: In CWM recovery, do install from sdcard and install the cm-10...zip file we transferred in the previous step.
the /data/ settings from stock amazon install are not compatible with CM10, but (very important)Do not reformat /data/ and /cache from CWM, this will result in a corrupted filesystem due to 3.0.21 kernel currently used by amazon not having necessary fs features!!!
Instead, clean /data via adb while booted to CWM:
Code:
adb shell "mount /data"
adb shell "rm -r /data/*"
Step 4: Now, installation is complete, you may reboot and it will bring you to your freshly-installed CM10 - enjoy.
(note by default this CM10 install starts with adb disabled, so you'll need to enable it in settings again).
How to reflash back to stock
Step 1: Remember where did you put those backups from step 1 during install.
Step 2:
Code:
fastboot flash recovery /path/to/mmcblk0p9 -i 0x1949
Now either connect a powered off kindle, or reboot an already connected kindle.
(note: I don't remember if stock rom is smart enough to wipe /data in this case or if it bootloops, so you might want to do rm -r /data/* before the final reboot)
once Kindle enters fastboot mode and recovery image is written, write the other two images too:
Code:
fastboot flash boot /path/to/mmcblk0p10 -i 0x1949
fastboot flash system /path/to/mmcblk0p11 -i 0x1949 # This one will take a few minutes
fastboot reboot -i 0x1949
Now you are back to factory stock.
Not so short video on the install starting from somewhere around step 3 for those who cannot perform the steps, but need to ensure this ROM is not for them yet:
Many things don't work yet:
- Sound
- Video playback
- Sensors (no rotation)
- Camera
- BT
- probably some other stuff I have not noticed yet.
Please do send in your patches/fixes.
Very cool, I'm gonna give this a try when I get some time tomorrow.
Thanks!
Neato(tm)!
Sent from my Nexus 4 using xda app-developers app
These are some amazing news!
Thanks a lot, verygreen. You are doing a really importaint thing. In my country no amazon services work, so the stock ROM is the biggest problem with Kindle 8.9.
Looking forward for the next builds!
Best regards.
Sorry if this is a stupid/annoying/heard it a million times please shut up already question, but does this mean anything the 7" variant?
xDecapitator said:
Sorry if this is a stupid/annoying/heard it a million times please shut up already question, but does this mean anything the 7" variant?
Click to expand...
Click to collapse
Eventually, this will translate to the Kindle Fire HD 7" as well. :fingers-crossed:
So, can you tell us what is the status of the build right now? What works fine, what doesn't? When can we see the first build to test?
Thanks for your answers and best regards!
This question belongs in general discussion not Development
Witcher_Kh said:
So, can you tell us what is the status of the build right now? What works fine, what doesn't? When can we see the first build to test?
Thanks for your answers and best regards!
Click to expand...
Click to collapse
I am not the first to answer your question in the following manner and I am sure I won't be the last. These developers spend hours of their free time developing code so that people like you and I can use it without paying unless it is through a donation to the developer. They typically don't have time to answer every person who asks when will the code be ready. so for you and others who are not developers your answer is:
"The next release will be ready when it is released and not until."
Early stages with such promise, hoping for a HD 7" inch variant
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
somdave2005 said:
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
Click to expand...
Click to collapse
Uh, wut?
somdave2005 said:
I'm assuming that with CM10, you won't be able to use all the special Amazon services like Amazon videos, lending library, etc. Doesn't that take away the whole point of buying a Kindle fire HD?
Click to expand...
Click to collapse
No - KF HD is a beautiful piece of hardware at a nice price, crippled by Amazons software. Where I live, almost all Amazon content is blocked anyway, so I won't lose anything. Amazon ebooks are basically the only content available to me, but that's just a matter of installing the Kindle app in CM.
eagerly watching and waiting... i havent got the stones to try it out now but ill test the first alpha! thanks for your work
Very very nice. Just waiting hopefully the developers will completed soon.
What about KFHD 7" ? If CM10 will work for KFHD 8.9", will work for 7" too or not? Sorry my english, please.
I am eager to try working this over to the 7HD but it might be premature. Do you guys think this software will still work with the fire 2 and 7HD?
Sent from my EVO using Tapatalk 2
craby1925 said:
I am eager to try working this over to the 7HD but it might be premature. Do you guys think this software will still work with the fire 2 and 7HD?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I thought i ask the same. I have KFHD 7" as well and want to try CM10 on it..
esox_hu said:
I thought i ask the same. I have KFHD 7" as well and want to try CM10 on it..
Click to expand...
Click to collapse
Just to clear this up.
I do not have Kindle Fire HD 7" and so I cannot try.
We've got a volunteer to try this at irc and bootloader unlock works the same way (as expected, but you need a different bootloader binary).
We were not able to get anything to show up on the screen after booting CM10, thought it appears the OS boots and behaves fine, backlight is on too.
Anyway, I'd much rather prefer people to buy Nexus 7, it costs the same as Kindle Fire HD 7, but is a much more open device with much more developer support.
If you need CM10 and further, get Nexus 7 and you'll be soo much more happier. You still can run kindle app on it to read your books if you so desire.
With this out of the way, let's not touch on the 7" device topic here anymore, it's for 8.9" development discussion only. Thank you for your understanding.
Yes, exactly.
verygreen said:
Anyway, I'd much rather prefer people to buy Nexus 7, it costs the same as Kindle Fire HD 7, but is a much more open device with much more developer support.
If you need CM10 and further, get Nexus 7 and you'll be soo much more happier. You still can run kindle app on it to read your books if you so desire.
Click to expand...
Click to collapse
Hear, hear!
The N7 is an amazing deal, has incredible specs with pretty much everything included, AND it's been made easily unlockable by the distributor. To anyone who wants continued access to devices in the future, there's no reason to support closed, locked systems.
So I just want to voice my agreement. If you're in the market for a 7" tablet, N7 > Kindle Fire HD 7".
Pass it on.
fattire said:
Hear, hear!
The N7 is an amazing deal, has incredible specs with pretty much everything included, AND it's been made easily unlockable by the distributor. To anyone who wants continued access to devices in the future, there's no reason to support closed, locked systems.
So I just want to voice my agreement. If you're in the market for a 7" tablet, N7 > Kindle Fire HD 7".
Pass it on.
Click to expand...
Click to collapse
I would have gotten the N7 but I wanted a larger screen.
Hello,
I have been trying to install whatsapp on my kindle fire hd and followed a guide that said to use the allwinner mod apk.
I did install the allwinner mod, selected samsuns s9000 and tried to install whatsapp
It failed, so i rebooted the kindle.
Now I am stuck at bootloop.
I see the kindlefire boot going but the system never boots.
I tried with kindle first aide to re-flash the original firmware, but failed since it seems unable to connect.
I tried to connect from command line but I cant get the fastboot command to go, tried with the original cable and with another one that I have got and that has always worked.
Im now out of ideas.
Since the kindle is rooted I dont think i can send to amazon, any idea?
Thanks
You need to get a fastboot cable to get your kindle into fastboot mode in order to flash it. They are pretty cheap.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to get a fastboot cable to get your kindle into fastboot mode in order to flash it. They are pretty cheap.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hello and thanks
I noticed that it responds to adb with a normal cable,
since i know that the allwinner mod changes the build.prop I was wondering if there is a way to restore the original one via abd.
Is there someone that has a build.prop to send me (kindle fire hd 7)
In the meanwhile I put on order the fastboot cable...
Thanks
A lot of build.prop can be found at persano's thread http://forum.xda-developers.com/showthread.php?t=2116243
But make sure to pick the right one.
Unfortunately I don't know If you can resp. how to put it in the right place to make it work.
Mistaz said:
A lot of build.prop can be found at persano's thread http://forum.xda-developers.com/showthread.php?t=2116243
But make sure to pick the right one.
Unfortunately I don't know If you can resp. how to put it in the right place to make it work.
Click to expand...
Click to collapse
Hello
many thanks I managed to get it out of the bootloop.
the procedure is:
download the build.prop and save to the computer /home (i use linux) then open a terminal and connect the usb cable to kindle
Code:
adb shell
su
mount -o remount,rw /system
exit
exit
adb push ./build.prop /sdcard/build.prop
adb shell
su
cp /system/build.prop /sdcard/build.prop.old
cp /sdcard/build.prop /system/build.prop
exit
exit
adb reboot
and that's it.
How was adb working during a boot loop? That's bizarre.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I don´t get it managed to root my KFHD "7.
It´s on 11.3.2 and I´m using the stock USB Cable (is factory cable mandatory?). I made chmod 777 for the RunMe.sh and I´m running a MacBook Pro on Mavericks.
"./adb devices" shows my device...
I already found this http://forum.xda-developers.com/showpost.php?p=50985251&postcount=347
I absolutely do not understand, why it won´t work. Of course for some of you it will become absolutely obvious, why it won´t work, when they read this.
This is what I get:
Normal mode enabled!
Checking if i should run in Normal Mode or special Sony Mode
Please connect device with ADB-Debugging enabled now ...
remote object '/system/bin/ric' does not exist
remote object '/system/app/Backup-Restore.apk' does not exist
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now ...
Pushing busybox ...
5178 KB/s (1085140 bytes in 0.204s)
Pushing su binary ...
4653 KB/s (91980 bytes in 0.019s)
Pushing Superuser app
5267 KB/s (996704 bytes in 0.184s)
Pushing ric
26 KB/s (57 bytes in 0.002s)
Making busybox runable ...
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again ...
Copying files to it's place ...
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Click to expand...
Click to collapse
Yes, I´m root user on the Mac.
Thanks for your help!
Ps: These are the threads I already read and I´m looking at...
[ROOT] How To: Root the Kindle Fire 7" HD or 2 with Linux/MAC - Noob (Simple) Version
manual fastboot whitout factory cable... regarding that, the factory cable doesn´t seem to be mandatory for rooting the device?!
[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [12/09 FREEDOM 7.4.6]
That´s what I want on the KFHD: [ROM-AOSP] Unofficial CM11.0 KFire HD 7 (KK 4.4_r1.2) [03/25 CODEC FIXES]
You can't put custom ROMs on the 2013 HD(which I identified by the 11.x.x os), only root access. On another note I just realized that that rooting thread for the 2013 HD didn't have a Linux/Unix compatible rooting script, only a batch file which is for windows, I assume the script is pretty simple, haven't looked at it yet. How about I convert it to bash and see if it will work for ya? I'll just have to grab the mac location for bash but other than that its pretty straightforward.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You can't put custom ROMs on the 2013 HD(which I identified by the 11.x.x os), only root access.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It´s this one: http://www.amazon.de/Kindle-Fire-Zoll-HD-Display-WLAN/dp/B00CTV13Z4/ref=sr_tr_sr_1?s=digital-text&ie=UTF8&qid=1397119675&sr=1-1&keywords=fire+hd
Yea that's a 2013 model, we can't install ROMs on that model, also reread my post, I was editing it when you answered back.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Yea that's a 2013 model, we can't install ROMs on that model, also reread my post, I was editing it when you answered back.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I read it now. Thanks, that would be great. Althought I will most probably send it back, because I were not aware of that fact and the stock ROM is slow and ugly ? But nevertheless that would be good for other Mac users too, I think ?
I'll post it tomorrow as I'm going to bed, I don't wanna work on it while I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
My Kindle Fire 7" HD was giving me problems a few days ago, so I used a factory cable to run KFHD_SRT_v1.2.3 (Option 2) to restore my system. It restored my Kindle with no errors, but while registering, there was no options for selecting a Wifi connection. I tried manually entering the Wifi information with no success. I skipped the Kindle registration since I couldn't connect to Wifi, and found that the ON button under the Wireless Internet options is now greyed out. "Need help connecting to Wi-Fi?" is shown underneath the On/Off buttons, but it does nothing when I click on it.
How should I attempt to connect my Kindle to wireless?
I've requested that this thread be moved to
7" Kindle Fire HD Q&A, Help & Troubleshooting
Moved!
If rooted try running
Code:
adb shell "su -c 'idme print'"
, see if your WiFi and Bluetooth mac adresses list still on that command. I like to make sure its not a bad boot block before running a few other checks.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
If rooted try running
Code:
adb shell "su -c 'idme print'"
, see if your WiFi and Bluetooth mac adresses list still on that command. I like to make sure its not a bad boot block before running a few other checks.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
My Kindle is rooted, but the device doesn't seem to be detected by adb. When running the command, I get
C:\Users\<User Name>\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb shell "su -c 'idme print'"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
In Windows 7, I went to the Device Manager and found Kindle Fire -> Android ADB Interface. No yellow triangles indicating a problem with the drivers. Then I went to "C\Users\<User Name>\.android\adb_usb.ini" and found that 0x1949 is listed. Then I checked Kindle Settings -> Security and found that Enable ADB is On.
What am I missing here?
taylerzy said:
My Kindle is rooted, but the device doesn't seem to be detected by adb. When running the command, I get
C:\Users\<User Name>\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>adb shell "su -c 'idme print'"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
In Windows 7, I went to the Device Manager and found Kindle Fire -> Android ADB Interface. No yellow triangles indicating a problem with the drivers. Then I went to "C\Users\<User Name>\.android\adb_usb.ini" and found that 0x1949 is listed. Then I checked Kindle Settings -> Security and found that Enable ADB is On.
What am I missing here?
Click to expand...
Click to collapse
try uninstalling the adb interface in the device manager then refreshing the device manager to notice the device again, and install it with my drivers. If you are using the stock amazon drivers they tend to not always work, not sure if this is the case this time but its always a good idea to use googles(which is essentially what mine are, i just modifed the inf file to include the kindles vid and pid).
stunts513 said:
try uninstalling the adb interface in the device manager then refreshing the device manager to notice the device again, and install it with my drivers. If you are using the stock amazon drivers they tend to not always work, not sure if this is the case this time but its always a good idea to use googles(which is essentially what mine are, i just modifed the inf file to include the kindles vid and pid).
Click to expand...
Click to collapse
The device is now detected: adb devices shows List of devices attached "D025A0A0242714AL device".
adb shell "su -c 'idme print'"
Reading idme data ...
version: 1.2
boardid: 8030800000000000
serial: D025A0A0242714AL
mac: E0CB1D4A4F48
sec: 9NDPKB437GXFH0ZP0F4F
bt: E0CB1D4AF7FC
pid: (zeros)
pid2: (zeros)
bootmode: 1
postmode: *
mfg:
taylerzy said:
The device is now detected: adb devices shows List of devices attached "D025A0A0242714AL device".
adb shell "su -c 'idme print'"
Reading idme data ...
version: 1.2
boardid: 8030800000000000
serial: D025A0A0242714AL
mac: E0CB1D4A4F48
sec: 9NDPKB437GXFH0ZP0F4F
bt: E0CB1D4AF7FC
pid: (zeros)
pid2: (zeros)
bootmode: 1
postmode: *
mfg:
Click to expand...
Click to collapse
Fixed! I tried many different things, but what finally fixed it was very simple.
I downloaded an updated version of SRT that has an option for restoring factory recovery:
http://forum.xda-developers.com/showthread.php?t=1951254
KFHD_SRT_v1.3.5- 7.3.0
After using option 3 with admin privileges, my Kindle automatically detected nearby WiFi connections.
Good, I was going to confirm at least four boot0 block is OK, but you figured the rest out so co grants and sorry for the slow reply, I'm taking it a bit easy this weekend because I have been spending too much time trying to work on a project that's a bit above me and my brain needs a bit of a break.
Sent from my Amazon Kindle Fire HD using Tapatalk
same issue
same solution (restoring original recovery got my wifi working again)
IDK why custom recovery is not compatible with WIFI
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
GogoplataMMA said:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
Click to expand...
Click to collapse
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
stunts513 said:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
Click to expand...
Click to collapse
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me.
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?
They are up and running when I click em. You were on this thread right?: http://forum.xda-developers.com/showthread.php?t=2096888
If that doesn't work you can always use binary's root.
http://forum.xda-developers.com/showthread.php?t=1886460
Use the old normal method if I remember correctly.
Sent from my Amazon Kindle Fire HD using Tapatalk
Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.
I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."
I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.
I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.
It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?
I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.
I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.
Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
i.imgur.com/gZrrqXm.jpg
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
GogoplataMMA said:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
Click to expand...
Click to collapse
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.
Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.
EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
======================================================================
Device type:
0) Xperia Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Please connect Device with enabled USB-Debugging to your Computer
The system cannot find the path specified.
Doing a Backup first, please confirm this on your device!
The system cannot find the path specified.
Done!
Press any key to continue . . .
Click to expand...
Click to collapse
It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9110232560198 device
Click to expand...
Click to collapse
I'm at a loss now. Any ideas?
EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.
adb push stack /sdcard/ is where the issue occurs. Everything else worked.
I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.
ERROR:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push stack /sdcard
/
cannot stat 'stack': No such file or directory
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
GogoplataMMA said:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
ERROR:
Click to expand...
Click to collapse
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link
Edit: link grabbed! http://forum.xda-developers.com/showthread.php?t=2277105
I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(
And all because of that stupid update... ughhhh. Sucks!
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>
I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\
And yes, 100% it's the 8.9". The resolution is 1200p.
OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
Sent from my Amazon Kindle Fire HD using Tapatalk