yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Android Development] LinearEquation:
I don't think anyone is trying to rush anyone. Many KFHD users have seen the potential of Android from these fine custom roms. Whether or not I purchase a Kindle Fire HDX rests soley on whether or not any custom roms will be sorted our for them, even if in the far future.
[7" Kindle Fire HD Android Development] Hinzman420:
Is there any chance you could make a kinology for the kf2 non hd?
[7" Kindle Fire HD Android Development] sneakysnake16:
For some reason my kindle won't charge even though its plugged in. Tried multiple ports chargers and phones and all work but this from. Worked fine on cm10 though. Any ideas?
[7" Kindle Fire HD Android Development] rsommerv:
I really wish I'd discovered this months ago, I love it. Two issues that I've come across so far: in Dolphin browser when I drop down a selection list I don't see the list op options, they are still there and tapping on areas of the screen result in different values being placed in the entry field. In my case this was when using two drop downs for Month and Year.

Second issue is in Chrome, I no longer get the tabbed stack that I was used to on my previous install (just a stock, but rooted). ie new winodws open a tab horizontally like the desktop version, previously I saw the url of the current window with a number next to it indicating the number of open tabs, tapping on the number opened a vertical stack of the browser pages.

Thanks for the rom.

*Edit: it seems the lack of tab stack is a chrome difference between phones and tablets, so Kinology is behaving correctly and my previous install was not.
[7" Kindle Fire HD Android Development] markbc01:
Strange, I have no charging problem with Kinology, and a quick search of this and the old thread does not show that to be an issue. Best to test to see if it really is charging, but perhaps it is not displaying the charge symbol. So (as long as you have more than about 30% or so remaining) I would download another program that monitors battery use/levels and will show if the KFTT is charging but not showing it.

However, if your KFTT *really* is not charging, then I would nandroid back to CM10.1 and do full recharge, or simply reinstal the stock, rooted version of the Amazon rom (That is something like step three in Julian's multi-file install process). If this gets the charging icon/or charging routine working again, then I would do a clean, new install of Kinology (steps four and five).

---------- Post added at 08:51 AM ---------- Previous post was at 08:44 AM ----------

I also use Dolphin. It's my main browser in Kinology3, and I do have the drop downs or select from list options (sorry:)). Have you tried clearing the data /cache for Dolphin? Also, maybe reinstalling it will be a second option. I use the "regular" Dolphin browser not their beta newer version -and the normal Dolphin seems to work well for me.

Good Luck! :cowboy:
[7" Kindle Fire HD Android Development] sneakysnake16:
Thanks your right it just doesn't show a charge animation but it definitely charges
[7" Kindle Fire HD Android Development] ninjabeaver:
How long should it take on the loading animation this is the first time installing

Never mind..I was too impatient
[7" Kindle Fire HD Android Development] markbc01:
+1 That first boot up is long. . Maybe up to 5-9 minutes!

I think that all deodexed roms have this long-first-boot characteristic, although I don't really understand why!
[7" Kindle Fire HD Android Development] itouchables:
The cache is being built up

sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
[7" Kindle Fire HD Android Development] markbc01:
Thank you itouchables for the reply!

This started me looking and I understand a bit more about this now.

"Regular" or "stock" or "official" roms applications (apps) all have TWO parts: part one is the "app" part (*.apk) and part two is the "odex" part (anyapp.odex) The odex part is used to help pre-load the app faster. The odex part has unique app information that helps it load and run faster.

When folks customize apps or roms, they can't work well with apps that have two-parts. So they combine all the features from the app file and the odex file into the ONE app file! This makes the app into a ONE file entity. That one file is much easier to modify or adjust for a customized rom.

Unfortunately, when the android java machine runs our apps (with NO *.odex files) it needs to manually build links into the dalvik cache ("builds" the dalvik cache) in order to run the apps/system as required.

This is slow because the java machine needs to "build" vice "load" like it would for a stock rom where all apps have app.odex files, which the java machine can access pretty quickly. . .

What this means is that the phone -the first time it sees a custom rom that is deodexed-- needs to "build" the dalvik cache as itouchables mentioned.

Normally, on stock roms, it just has to "read" the odes files for all the apps. So, the first time java scripts read and build the dalvik, it takes time. . . that's the cost of flashing a custom rom!

I *think* I have that right. . .but honestly, I am not so sure… regardless, the time we wait makes sense now -the phone (or Kindle Fire HD) in this case, is not sitting idle, that time is being used by the machine to build the cache. (And) when it is done it definitely is worth it for the chance to use these great roms (like kinology3)! :victory:

Thanks again itouchables for this info. . . it is a fascinating learning point for KFTT users like me!

:good:
[7" Kindle Fire HD Android Development] itouchables:
Yup:D:D:good: you are right on target..nice to see people interested in the inward workings of their stuff.:good:
[7" Kindle Fire HD Android Development] Hafficci:
Thank you so much, JulianPaolo!! Really hard work done here in order to get a usable Amazon Firmware on our KFHD!! :thumbup:

I've come from 7.4.6, and now I can use my tablet in all his splendour, while maintaining the original launcher!!

As said before, thank you so much for the effort!! ;)

Enviado desde mi KFTT usando Tapatalk 2
[7" Kindle Fire HD Android Development] goyash:
Thank You really great rom. Great experience every minute since install ( been about a week) and I cant really think of any way it could be better! I love the way everything is well integrated. Keep up the great work
[7" Kindle Fire HD Android Development] ioft:
I'm feeling slightly noobish. I assume to install this coming from CM10.1 I need to reinstall the Amazon OS and then go through steps 2-5? It seems to hang on the second bootloader (I let it sit for an hour each time so I don't think it's cache building related) when I do this; or even if I just try to flash the AIO zip for steps 2-5... thoughts?
[7" Kindle Fire HD Android Development] LinearEquation:
No, just follow his instruction for flashing it.
[7" Kindle Fire HD Android Development] moorek:
Getting back Stock (square one)

I've completely hosed myself and my Fire HD is in limbo. I had Kinology 3.1, was having problems and went back and installed an older Kinology zip by mistake (too many zips and got confused). I would like to just start from scratch. Is there anyway to put the Fire HD back to stock and no recovery? I've looked for instructions and can't find something definitive.

Thanks!
[7" Kindle Fire HD Android Development] fooshack:
Does anyone know how to get the reading view option to show up in the Silk browser?

Thanks,

Foos
[7" Kindle Fire HD Android Development] dmullens:
I know this is an odd request...but is there any way to turn on the special offer ads from Amazon?

Thanks.
[7" Kindle Fire HD Android Development] markbc01:
The first aide kit by prokennexusa had an option to disable ads, also I thing that there are other xda threads (in the general section) that offer techniques that don't involve going through Amazon. . . Please see the link to his first aide program

here:

http://xdaforums.com/showthread.php?t=2096888

---------- Post added at 04:54 PM ---------- Previous post was at 04:49 PM ----------

((For @moorek)) Assuming you have twrp loaded as part of the process of loading kinology, all you need to do is re-install the new image of the latest amazon base that is either the second or third file to flash in the kinology flashing process...

Recovery is really very good to keep -even if the rom itself gets screwed up. Also, if you have a nandroid backup (done in TWRP) you can go into recovery and restore that and it should work. .

The process to load files up to loading the latest Amazon rom is mentioned in the op instructions and also may be mentioned in early posts on this thread. .
[7" Kindle Fire HD Android Development] markbc01:
I just re-read my post to @moorek, and it might not have been too clear. Here's a better answer:

1. go to JulianPaoloThiry 's original post for this Kinology3 thread

2. then click on the install/download link (http://android.jupath.me/custom-roms/kinology/installation-download/

3. then scan down to the "Longer, more informative version" of the instructions (at the bottom of the page)

4. then go through step 1, step 2, step 3 and step 5 (chose the option to wipe data in step one)

(basically just skip step 4 the installation of kinology)

... That should provide you with a clean, rooted Amazon version including Gaaps and if you did not want Gaaps then skip step 5!

:)

Oh, I notice you mentioned deleting TWRP. The only way I know to do so (if you really want to delete TWRP recovery as well), and perhaps the easiest way to do so might be:

1. go to the Amazon update page and read the Amazon instructions on manual updating.

2. There is a link on the Amazon website for the Kindle Fire HD 7" (KFTT) page that allows you do manually download the full version of Amazon's latest rom (called an update) (7.4.6). Here is the download link: (https://s3.amazonaws.com/kindle-fire-updates/update-kindle-7.4.6_D025_4620220.bin ) .

3. Follow their instructions to copy that file to the correct directory on your KFTT and you can start an automatic reset you Kindle Fire HD 7" back to the latest stock version.

4, However -this will also un-root your KFTT, so you will have to re-root your KFTT!

4b. (There is one more option -and that is to use Prokenexusa's Kindle Fire First Aide tool and do an adb transfer of the latest (rooted) software to your KFTT, but please check out his thread to try any of that! (the link is in my previous post))
[7" Kindle Fire HD Android Development] JulianPaoloThiry:
I think you can just reinstall the dtcp apk, though I have not tried it.
[7" Kindle Fire HD Android Development] JulianPaoloThiry:
3.2 Released

3.2 - 2013/11/21

This is a service release - there are no changes to Kinology itself. The following apps have been updated:

AdAway 2.8

Adobe Air 3.9.0.121

Adobe Flash Player 11.1.115.81

Amazon Appstore 6.1020.1095

Amazon Atlas Framework 2.0

Amazon Email 2.040_2040005610

Amazon GameCircle 2.6

Amazon Help and Feedback 2.10

Amazon Photos 3.2.5004610

Amazon Silk Browser 1.0.135.187

Amazon Video Swanfleet-21309310

Google Gmail 4.6

Google Hangouts 2.0.128

Google Play Services 4.0.33

Google Play Store 4.4.22

Google Text-to-Speech Engine 2.4.3

IMDb 3.3.1

KindleStoreWebApp 1.4.1.0.117.0

Kindle Video Library 1.0.8.0

Shop Amazon 1.51.72

SuperSU 1.75
[7" Kindle Fire HD Android Development] markbc01:
Thank You Julian for keeping this Rom up to date! :good::good:

Kinology has been great -and continues to be the most stable, best way to use the Kindle Fire HD 7" (KFTT); especially for folks like me who use Amazon content a lot! I can't think of using anything else :D
[7" Kindle Fire HD Android Development] markbc01:
Ouch, I spoke too soon ;-(

I just tried to upgrade. I had problems.

According to the instructions I loaded two files

Kinology-step1-boot-7.4.6

Kinology-update-3.1-3.2

Installed them both via TWRP. TWRP stopped after the first file installed and the message on the screen asked me to reboot recovery (I did). I had to find the second file and install (ok).

However, upon system reboot the screen became a test pattern of colors. I rebooted and the screen was a gray static screen. (see picture

1) Rebooted into recovery and tried to reinstall (loaded both files. (see picture 1) Rebooted and the same "gray static "test screen.

2) Went back into Recovery and tried to restore my latest nandroid backup (Kinology 3.1) and the screen kept hanging on second (blue) Kindle Fire Screen.

3) Went back into Restore and tried to restore an earlier nandroid backup. It delivered the same grey screen.

4) In recovery I mounted my usb and pushed the a-i-o package over and tried to install, but it seemed to fail. I will re-download and try that again.

5) Are there any obvious errors I made, and corrections I can make. I can still access TWRP, so I don't feel too nervous, but am a bit concerned anyway :confused:

Thanks in advance
[7" Kindle Fire HD Android Development] JulianPaoloThiry:
I'm not sure what to say. The way you upgraded is exactly the way I did it on my own device. I've never seen static like that.... ever.

Just an FYI though - If you put the .md5 files on your device alongside the .zips, TWRP will verify that the checksum matches before attempting to flash so you can be sure 100% sure the files transferred correctly to your device.

The first thing I would try would be to flash the old boot file (still available here) and then restore your nandroid backup and see if it works. If it doesn't, then something beyond the norm has gone wrong with your device....
[7" Kindle Fire HD Android Development] markbc01:
Hi and thanks for that advice

I'll do that check sum!

AlsoThanks for the old file link. .

I suspected I would need it :)

I'll let you know when I try it after I return home tonight.

Thanks again
[7" Kindle Fire HD Android Development] markbc01:
Whew! That did not work out like I expected :(

OK, So after those weird screens and my update, I still could get into twrp without issue however writing to the KFTT disk was an issue.

Thank you Julian for the link, however, I wish I had downloaded it and flashed it earlier.

I did download it and pushed it and then even tried to side-load it via adb in TWRP. However, I did this too late.

I did this only after trying nandroid the second time (and it failing). It seems that all files I pushed or side-loaded after trying the two-file update reinstall and 2d nandroid backup either would not "stick" (file transfer fail message in adb: disk is read only) or they would simulate loading (download/sideload complete) --yet have no effect.

Rebooting TWRP, several times even, did not change the status.

A bit of ( redundant) detail:

- i tried shelling into the KFTT (it worked ok!), and to mount (any) target directory as RW manually, but that did not work (regardless of the directory).

- Also tried in TWRP to run the nandroid restores yet again -but at this point the restores simply would not run. TWRP repeatedly reported "operation failed" without taking any actions.

- Using adb to shell into the KFTT and trying to push files to install or side load did not work as well. My (MAC) file system (Finder and the android file transfer utility) did not see the KFTT, even though xterm windows recognized it well.

After about three hours total of this, I simply "surrendered," & rebooted into fastboot (using my SKorPn cable ) and restored a boot/ a system/ a recovery image that I had.

A couple of hours (and one meal) later, I am on a fresh install of Amazon 7.3. (wow that is old!). (The images I restored are from the recommended backups I made per Hashcode's recommendations in his TWRP thread -it paid off!) Anyway, they are older, but rooted. I have SU and "Market" (older version!) and all things back up and running as native (OTA disabled) Amazon Rom. My KFTT has not seen this rom in a long while.:fingers-crossed:

So. . . time to start all over. . next weekend after Thanksgiving --while watching football and digesting turkey :o

Lesson learned:

1) do a NEW nandroid backup prior to updating.

2) was good to have a factory cable **REALLY IMPORTANT**

(ADB to get to fastboot -that only works when the KFTT works, at times like these -a cable is needed)

3) don't try too much or too many "fixes" too fast when things go south

(I should have waited and used Julian's older boot file prior to trying the restore (at least the 2d time)) I might have self-recovered right then. :(

4) really good to have backup images ready to use fastboot restore (boot.img, recovery.img,system.img & sometimes stacks)

(thank Prokennexusa! -his Kindle Fire First Aide kit paved the way, and even using its process to manually restore worked!)

Edit: all setup again, but it's a bit "clunky, " fonts sizes not as nice. I miss Kinology already :-/
[7" Kindle Fire HD Android Development] runningman04072013:
Just dropping by to say thanks for this great ROM and for the recent service update to 3.2. I was recently gifted the Amazon Prime membership, so I was looking for a way to return my device back into Amazon's content portal. Thank goodness for Kinology. Enough said. =) Cheers.
[7" Kindle Fire HD Android Development] markbc01:
Help Please!

Background (Friday):

- Kinology was working well until I updated (see my above three posts). Nandroid would not restore.

- Used Fastboot to flash old boot/system/recovery and restore my KFTT back to an old (Amazon 7.3) rooted,working rom.

Latest actions (Sunday):

1. Successfully reinstalled TWRP,

2. Tried to flash the Kinology 3.2 a-i-o (only) (tried skipping step one. Failed (static screen). Flashed step one file, no joy.

[see pix0 & pix1]

3. (again) Used Fastboot to flash old boot/system/recovery and put my KFTT back to that old (Amazon 7.3) rooted,working rom. Also re-installed TWRP again.

4. Tried to flash Kinology using the file-by-file procedure, followed exactly as instructions, but stopped after flashing through Step 3. (flashed up to the point where Amazon rom 7.4.3, including Amazon update was installed)

[see pix2].

That Flash failed! Upon reboot only had similar static screen on reboot but this time broken lines.

[see pix3]

5. Used Fastboot to flash old boot/system/recovery and put my KFTT back to an old (Amazon 7.3) rooted, working rom. KFTT working ok, but waiting for any suggestions prior to reinstalling TWRP and more flashing .

Please, what have I missed/done wrong/need to do, to get back into Kinology?

Thanks in advance!
[7" Kindle Fire HD Android Development] JulianPaoloThiry:
I will double check the integrity of all files later today. I don't see any obvious missteps. They line up with how I test before releases.

Also, put those MD5 files on your device ;) I still see "skipping md5 check" messages.
[7" Kindle Fire HD Android Development] markbc01:
Thank you very much for checking!

You Rom is great and I doubt there is a problem, unless it possibly might be with one update file?

However, I am thinking that your files are all ok, and it is probably a configuration issue with my KFTT setup.

Don't quite know where though...

OK, I have finally downloaded *all* of the md5s now from your install page -that will help when I reinstall next time. :good:

I also just tried to reinstall TWRP and that surprisingly failed! (I have installed twrp about five times without issue. Had a bootlooping (red) kindle fire logo that never turned to blue!) All the (Hashcode's) TWRP file MD5s were good. But I knew that anyway since I had flashed them all successfully yesterday! Go figure. . .:confused:

Now back to my old rooted 7.3 Amazon configuration with data intact (used fastboot), but will hold off until next weekend since I know this will be a time-trap and I have too much other stuff going on right now. :(

Thank you again for following up!
[7" Kindle Fire HD Android Development] galearned:
Reverting from cm10.1 to Kinology 3.2

Thought I would post a test I conducted last night on migrating from KIndle OS to CM10.1 and back to Kinology 3.2.

I was running Kindle OS 7.4.3 with root and TWRP 2nd bootloader.

I placed Kinology Step 1, the Kinology wipe without backup, and the big Kinology Kinology-aio-3.2.zip all in one package a01 on the tablet SDcard

I then placed the Hashcode 7.4.3OS.zip file on the sdcard

Lastly, I placed the CM10.1 OS.zip and gaaps.zip files on the sdcard.

As stated, the tablet was previously configured with root and TWRP 2nd bootloader.

1: Booted into recovery and wiped factory reset

2: Installed CM10.1 and rebooted into CM10.1

3: Booted into recovery and wiped system then installed Kinology step 1 , Kinology wipe, and the Kinology all in one package and rebooted (Was successful).

4:Booted into recovery and wiped factory reset and installed cm10.1 again. The install was successful.

I conducted a second test where I flashed all of the files in series using recovery without rebooting until the last zip file was flashed.

1: While running cm10.1, booted into recovery and wiped factory reset.

2 In recovery flashed the following five zip files in order without exiting recovery:

Hashcode 7.4.3OS.zip

Kinology Step1.zip

Kinology wipe without backup

Kinology all in one package

Kinology 3.2 update

3: Rebooted tablet and Kinology booted up normally and worked perfectly.

At least in my test, I was able to go back and forth between CM10. Kindle OS and Kinology without any issues.

The fact that Kinology was able to get installed without any issues speaks well of the work Julian has done on the packaging.

Regarding the issue of not finding sdcard files or finding them in odd places, Kinology appears to create a "0" mount under mnt and put the original sdcard folders in the "0" folder and this folder is also linked to the new Kinology folders (E.g., what is in "Sdcard " also shows up in"0". The folders that are unique in the Cm10 install are placed only in the "0" folder.

Example: I created a "Back" folder in cm10.1 and after the Kinology install, the Back folder was now in "0" and not in "Sdcard".

All my installation files were setting in the "Back" folder and were still there after the Kinology install.

When I reverted back to cm10.1 from Kinology, the "Back" folder was now in the "sdcard" folder where it was originally.

Thus, no folders or files are lost when moving from one OS to the other and the reverse.

The only question I have is whether the Kinology-aio-3.2.zip contains the Kinology 3.2 update file or not but, I installed the update anyhow. If the 3.2 update is already in the Kinology-aio-3.2.zip file then flashing the update would not be necessary.

Edit: I just answered my own question with closer reading of instructions: The update is needed only if updating from an earlier Kinology release.

Regards
[7" Kindle Fire HD Android Development] tonie972:
I just placed an order for a Kindle HD and looking to root this thing. Can amazon still be able to detect that I have a kindle because I need Amazon to be able to recognize it so I can borrow books from them. Thanks
[7" Kindle Fire HD Android Development] markbc01:
Amazon does not really care if your root the Kindle Fire HD.

If you break it and try to return it they may say something, but most often they don't even complain even then.

When you root the KFTT (Kindle Fire HD 7) you can do everything with it that a new, unrooted KFTT can do.

This is DIFFERENT from the very first generation of Kindle Fire, where it would not play videos if it detected you were rooted.

The KFTT does not react differently whether rooted or no. All you get is more capability.

If you root and add the Kinology rom, then you get a few more benefits that are listed in the first page -I have run the

KFTT rooted, and also using Kinology. Kinology seems better for me --and you still can do everything a new Kindle

can do!

Good Luck!

(Of course, the is all about the 2d generation of Kindle Fire. I have not worked with the newest ones that just came out with

the KF HDX)