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.
Related
I have a rooted kindle with burrito root 10 months ago and now and tried to install cm10.
thought it went ok but is stuck in bootloop showing splash screen. Brick.
I must have messed up the bootloader because I can't get anywhere with KFU other than the device is online.
I reinstalled drivers, tried to reinstall FFF, twrp. no luck.
i've been reading threads a good part of the day and found fire kit with ubuntu running via USB.
I did that, then ran,
"sudo /cdrom/fk"
then I tried "usb_fix_parts_and_install_fff_twrp"
It failed saying "no such file or directory"
I'm not super familiar with ubuntu or their code.
Please help me unbrick this.
amscomputerpro said:
I have a rooted kindle with burrito root 10 months ago and now and tried to install cm10.
thought it went ok but is stuck in bootloop showing splash screen. Brick.
I must have messed up the bootloader because I can't get anywhere with KFU other than the device is online.
I reinstalled drivers, tried to reinstall FFF, twrp. no luck.
i've been reading threads a good part of the day and found fire kit with ubuntu running via USB.
I did that, then ran,
"sudo /cdrom/fk"
then I tried "usb_fix_parts_and_install_fff_twrp"
It failed saying "no such file or directory"
I'm not super familiar with ubuntu or their code.
Please help me unbrick this.
Click to expand...
Click to collapse
From what you wrote I suppose that you have original Kindle Fire and not Kindle Fire HD...
Anyway you could take a look on this thread.. someone wrote that he was able fix Booting loop with it
http://forum.xda-developers.com/showthread.php?t=1896570
I hope it will help you,
Kerbik
Bricked Kindle Fire in bootloop.
Kerbik said:
From what you wrote I suppose that you have original Kindle Fire and not Kindle Fire HD...
Anyway you could take a look on this thread.. someone wrote that he was able fix Booting loop with it
http://forum.xda-developers.com/showthread.php?t=1896570
I hope it will help you,
Kerbik
Click to expand...
Click to collapse
Yes, I have a original KF. Thanks for the thread.
I downloaded the file called "7.1.5_stock_build.prop.zip".
I don't seem to know as much as I thought I did with command prompt because I can't seem to get it to load.
what directory should stock_build _pro file be in?
I followed the following script:
Code:
# adb shell
# echo 'ro.kernel.qemu=1' > /data/local.prop
I then get the following error:
* daemon not running. starting it now *
* daemon started successfully *
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: can't create /data/local.prop: Permission denied
1|[email protected]:/ $
Wrong forum...
"I downloaded the file called "7.1.5_stock_build.prop.zip"."
I may be wrong, but I think that file is only for the HD, not the Gen 1 model (last year's model). If you jam it on your device you'll likely only make it worse (assuming you can get worse than bricked!)!
You need to get over to the Gen 1 forum as this is one for the HD series and won't be of any help to you.
Link:
http://forum.xda-developers.com/forumdisplay.php?f=1306
no99sqrd said:
"I downloaded the file called "7.1.5_stock_build.prop.zip"."
I may be wrong, but I think that file is only for the HD, not the Gen 1 model (last year's model). If you jam it on your device you'll likely only make it worse (assuming you can get worse than bricked!)!
You need to get over to the Gen 1 forum as this is one for the HD series and won't be of any help to you.
Link:
http://forum.xda-developers.com/forumdisplay.php?f=1306
Click to expand...
Click to collapse
ok thanks.
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
Hi everyone, today i would like to ask for your help with a pretty big problem i have with my Kindle fire HD, you see, i was updating from my current rom 7.4.4 to CM 10.2. to achieve thi i followed this tutorial http://forum.xda-developers.com/showthread.php?t=2271909 , everything was going fine until i installed 2nd-Bootloader and TWRP recovery. The problem came up here, when i realized that i forgot to move the rom and the files for google play into the SD card, now whenever i try to do this i can't seem to get my PC to recognize the Kindle with TWRP (i can browse my files and such with TWRP directly through the kindle itself) i tried to move the required file with adb and fastboot but i can't get it to work.
The kindle is rooted and running version 7.4.6 from amazon.
i have a backup for the rom and the files but i can't use fastboot.
i have a backup for each of the following files: boot0block, stock-boot, stock-recovery, stock-system
all the adb drivers and sdk are functioning perfectly.
When i connect it to my PC with windows 7 i can see the kindle recognized by the device manager but it has yellow triangle next to the icon.
i also tried using an otg cable but the kindke did not recognize it.
any and all help is appreciated, i don't want my tablet to die Dx
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Ph0enix_216 said:
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I tried this but the problem is that the pc not find device , it show me in device manager yellow triangle next to the icon of kindle
When i send a adb command , the adb say "Device not found"
Thanks you anyway!
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
stunts513 said:
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Click to expand...
Click to collapse
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Shur'tugal said:
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Click to expand...
Click to collapse
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help your save my tablet
Thanks you very much
Finally i exit for this bricked
Enviado desde mi GT-I9300 usando Tapatalk 4
I have a dude im install CM 10.2 perfect , but i dont remember install de google apps as i have to do now?
Thanks
One step further
My apologies for hijacking this thread. I had made the same error as the OP. however, instead of searching here for solution, I panicked and wiped the cache and user data using the SR tool and wiped everything. Now unfortunately my kfhd tells me it can't boot, which my incompetent mind tells me is likely because I have no rom?
I've tried to use first aide to do a system recovery but I get told the files are too large and it can't do anything.... Any suggestions or thoughts from people? Appreciate any help I can get. Been up late the last 3 days trying to sort this out, while I thought I was going to provide m wife with a slick android device!!
That's odd, I wouldn't think wipe your data partition and cache would cause that to happen, then again there are some files stored under data the system uses out side of apk's so I guess that could be why. Did you get your kindle into fastboot? If you did I would suggest trying to use kfhd system restore tool if kffa didn't work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
deeman77 said:
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
Click to expand...
Click to collapse
All the files, or just the system.img?
soupmagnet said:
All the files, or just the system.img?
Click to expand...
Click to collapse
each one of them unfort.
Do you have twrp installed?
hloomsc some
soupmagnet said:
Do you have twrp installed?
Click to expand...
Click to collapse
I did. Not sure i do now post trying to do a wipe. Don't see any blue when I start up, just the original kindle letter coloring, after which I get a message saying it can't boot
any suggestions anyone or is my kfhd pretty much killed? there's got to be a way to load some rom on to it!!
You should be able to load the original images over fastboot, something just isn't working right. I would say its far from hard bricked, it should still be fixable, its just a matter of troubleshooting it. If you have the kindle fire system image I would try manually flashing it but you need to know what you are doing. If you CD into the SRT folder where im assuming the IMG files are in the same folder as fastboot, try running "fastboot -i 0x1949 flash system system.img" think I got the syntax right, haven't had to ever use fastboot myself, anyways if you run that what does it report back? Hopefully not the same error, or it might be something messed up with the image.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
thanks for the advice. ended up re downloading the images again and this time it worked. go figure.
back to starting again to get my custom rom on.
once i have a custom rom, guessing there are no amazon bits left in there that would cause any updates to come through right?
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good afternoon: I bricked a nice 8.9 tablet several weeks ago using ADB sideload...
I used ADB Sideload to install Gapps since I was already in TWRP and was too lazy to reboot and transfer the gapps.zip file to my tablet.
The sideload installed the gapps.zip as I expected it to and I was brought back to the main TWRP screen.
When I clicked on reboot/reboot system, the tablet started flashing the three partitions (boot, recovery and system) as I was watching. TWRP then left me at the booting screen doing nothing. I did not know why the tablet decided to flash the three main partitions but, I opted to push the power button and that was the last time I saw my tablet.....
Apparently ADB sideload is only for ROM's? I had only used it to flash ROMs prior but, I thought ADB Sideload should be able to install any properly zipped file designed to flash with TWRP?
Regards
In an attempt to install TWRP to my TATE device, I seemed to have broken the ability to enable wireless (it is toggled off, grayed out, and cannot be enabled).
I followed the steps from here (http://forum.xda-developers.com/showthread.php?t=2128848) but did not want to install CWM. Wireless did work on my rooted Kindle before these steps were taken.
The steps that were taken causing it to no longer work are:
1. Install the stack override in /system:
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
2. Stop the auto recovery update script:
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
3. Flashing uncorrupted bootloader, boot, recovery:
Code:
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.6.3.1-recovery.img
fastboot -i 0x1949 reboot
The recovery did install correctly as I could boot into TWRP and create a backup. I also created a backup before the entire process using adb. What should I do to enable wireless? Thank you.
JArch3r said:
The recovery did install correctly as I could boot into TWRP and create a backup. I also created a backup before the entire process using adb. What should I do to enable wireless? Thank you.
Click to expand...
Click to collapse
If it were me I would factory reset and try again. You can use the nandroid backup you made beforehand as well. When ever wifi goes hinky a factory reset seems to be the best solution.
LinearEquation said:
If it were me I would factory reset and try again. You can use the nandroid backup you made beforehand as well. When ever wifi goes hinky a factory reset seems to be the best solution.
Click to expand...
Click to collapse
Thank you for the solid advice. I discovered the issue arose from blindly following the instructions in the thread -- it said to use kfhd7-freedom-boot-7.4.6.img instead of the applicable version. I googled and found the 7.2.3 version on HashCode's goo.im page, repeated all of the steps using it, and wireless works perfectly now.
In my searches of trying to solve the problem, I discovered users with the same issue. Kindle Fire (HD) users unavailable to connect to wifi and "MAC address unavailable." Running idme /? in a terminal on the device states "Could not open /dev/block/mmcb1k0! Can't read the idme." I believe they would benefit from reading this.
JArch3r said:
Thank you for the solid advice. I discovered the issue arose from blindly following the instructions in the thread -- it said to use kfhd7-freedom-boot-7.4.6.img instead of the applicable version. I googled and found the 7.2.3 version on HashCode's goo.im page, repeated all of the steps using it, and wireless works perfectly now.
In my searches of trying to solve the problem, I discovered users with the same issue. Kindle Fire (HD) users unavailable to connect to wifi and "MAC address unavailable." Running idme /? in a terminal on the device states "Could not open /dev/block/mmcb1k0! Can't read the idme." I believe they would benefit from reading this.
Click to expand...
Click to collapse
I am having the same exact problem. can you post a link to repair info you are referring to above. Thanks
crustysmooth said:
I am having the same exact problem. can you post a link to repair info you are referring to above. Thanks
Click to expand...
Click to collapse
One page where the files are available: https://www.androidfilehost.com/?w=files&flid=34232
You can also just google "kfhd7-freedom-boot-7.2.3.img" or the name of the file you need.
Excuse me, but can you provide download link for kfhd7-freedom-boot-7.2.3.img ?
google didn't help
Hello everyone....
I have a kindle fire HD 7" 7.4.6
I rooted and added TWRP with 7.2.3 bootloader
I installed CM11 Kitkat the ROM is a bit buggy but nice.
I tried to go from kitkat to kinology which allows use of Amazon and Google services.
But flashing failed.... I can't seem to get kinology to work.
This is the set of walkthroughs I used.
To root & add TWRP. I used a rootjunkie YouTube video ( can't post link)
To install cm 11:
also a rootjunkie video
knowing this, I tried installing kinology using this walkthrough:
Original kinology page.
No luck, does anyone know how I can move my system to kinology?
please help,
Thanks to all in advance
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok first, thanks for the reply. Second, yes i did do a wipe before the install.
I am going to go check out your link now and see.... ill keep you posted.
Thanks again....
Quick question.... can the process in your thread be done through fire flash 11? ( i am an absolute noob at this, so it may be a silly question...)
i can follow along as to what must be done, but i dont feel comfortable doing a process without a guide.....do you know of any threads with a walk through for this?
There aren't any tutorials for this as far as I know, I got this command from Hashcode in the irc, just run the command mentioned above from a command prompt (while in recovery) while cd'd into a utility that came with a copy of adb, like my wallpaper fix for example that's in my signature. If you don't know anything of command prompt like what CD commands normally I would say read up on basic command prompt because its very simple, but because of a nice trick I remembered recently you can avoid the CD command, just shift + right click the folder with adb in it and hit "open command prompt here", then run the command I posted (while in recovery).
Sent from my Amazon Kindle Fire HD using Tapatalk