[ROM-AOSP] Stock Jelly Bean 4.2.2_r1 for the Kindle Fire [02-12 4.2.2_r1]

Search This thread

hydeah

Senior Member
Nov 19, 2011
427
27
New York
I don't remember exactly where, but somewhere on this site, people successfully installed and used amazon prime video services on custom ROMs. Search for instructions..


Thanks, I'll search, I am more interested in getting FreeTime and FreeTime Unlimited to run on custom rom if possible, if not, I'll stick with stock rom for now.
 
Aug 30, 2008
29
7
Is there any way of installing the play store on the device after thus rom is loaded? I can't seem to install any apps as there's no option to log into a google account in the accounts part of settings.
 

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,750
2
9,592
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
from op
INSTALLATION
RECOMMEND FULL WIPE UNLESS UPDATING A 4.2 ROM Use Titanium Backup to restore apps.
Download the ZIP
Grab the GAPPS (12/12 from goo.im/gapps)
Reboot into recovery
Make your backup (You do make a backup right?)
Wipe Data/Cache)
Flash both the ROM and the gapps .zip files
Reboot and Enjoy


---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------

lots of GApps mirrors in my list http://goo.gl/kDt7fo
 

kvestas

Senior Member
Dec 17, 2012
297
164
link to rom not working, is there another link?:confused:

As you may see this rom is very old and its development had been discontinued almost a year ago.
So... The only chance, very tiny chance btw, is to ask developer upload the rom elsewhere. If you are lucky and your request will be kind enough you may get a proper response I guess. Of course if Hash is still subscribing xda and if he still has such an old build in his backup storage.
By the way, at least you should thank Shadow for his help in other threads. He is really trying to help you but I've seen no thanks in all his answers.
Thanks for understanding mate.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 205
    jb-kfire-trio-screenshot.png

    AOSP JELLY BEAN 4.2.2_r1

    Also included are some optimizations by Texas Instruments and the result is a BLAZING OS running on what is now considered an out-dated memory model (512MB RAM).
    Most OMAP 512MB devices are not supported by their OEM vendors past Gingerbread (LG may be an upcoming exception).

    This ROM represents exactly what is being pushed to Nexus 10/7 owners. Now you can join in the fun too!

    WHAT'S NEW IN ANDROID 4.2
    See for yourself: http://www.android.com/whatsnew/
    (Note that we don't have a camera or NFC so some of these are obviously not going to work for us)

    [2013/02/12] Download 4.2.2_r1 ROM here
    md5sum: f4cc5efb6de779da93670fb48a794d64

    PLUS YOU WILL NEED TO FLASH GAPPS AFTER
    Jelly Bean 4.2 Gapps here (CM10.1)
    (use top row CM10.1 link for 12/12)

    WHAT WORKS
    (Basically, most items I tested work, except I couldn't get the new swype-style input going on the keyboard)
    • [02/12] AOSP 4.2.2_r1
    • [01/22] Updated with new 3.0.50 kernel including better battery life
    • [01/22] Newest PVR/Imgtec graphics binaries
    • [01/22] Update wifi firmware to R5.SP3.06
    • [12/18] Fixed battery deep sleep
    • [12/18] Added multi-user login fix mentioned by NotShorty found here: http://forum.xda-developers.com/showthread.php?t=2018146
    • Hardware Acceleration (hwcomposer)
    • HD Codecs (YouTube/Netflix)
    • Small amount of OTG (some devices w/ powered hub supported)
    • Sound, but no microphone

    NOT WORKING
    • Bootanimation needs a display bugfix
    • Need to enable the swype-style 4.2 keyboard
    • I'll check out photo sync options
    • Looking into USB camera support (will probably be more useful when the 3.4 kernel is ready)

    REQUIREMENTS
    1. Should be running FireFireFire Bootloader 1.4a found here: http://forum.xda-developers.com/showthread.php?t=1632375
    2. Have a custom recovery installed, such as TWRP 2.2.x.x+ or Cannibal Open Touch: http://forum.xda-developers.com/showthread.php?t=2025793
    3. Easy method for both -> Use Smirkit: http://forum.xda-developers.com/showthread.php?t=1500935

    INSTALLATION
    RECOMMEND FULL WIPE UNLESS UPDATING A 4.2 ROM Use Titanium Backup to restore apps.
    1. Download the ZIP
    2. Grab the GAPPS (12/12 from goo.im/gapps)
    3. Reboot into recovery
    4. Make your backup (You do make a backup right?)
    5. Wipe Data/Cache)
    6. Flash both the ROM and the gapps .zip files
    7. Reboot and Enjoy

    FREQUENTLY ASKED QUESTIONS
    • Q: Does this include the new 3.4 kernel? A: No, it's not ready yet.
    • Q: Where's the "Developer" settings menu? A: Go into Settings -> About tablet, and tap the "Build number" box about 7 times. That enables it.

    BUILDING THIS ROM
    [ It's a rough build. Probably not going to update the public manifest ]

    Enjoy
    15
    OP Updated for 12/18 deep sleep fix build.

    http://goo.im/devs/Hashcode/otter/aosp/jb-4.2-kfire-hashcode-12-18.zip
    md5sum: 09b6d4feea0f6019969731ae46e9e6ab
    13
    I think optimizing the code should be a high priority.

    Seems with very rom release, people typically add more in. As a Kindle Fire only has 512 mb for ram, adding more in isn't exactly the best of ideals. Rather I think its better to keep this as minimal as possible (pure android os) & add only anything that which may improve the memory requirements (kernel update for example).

    This is exactly what im doing with the 3.4 kernel. Not just a kernel update but a complete overhaul of most of the drivers.

    Sent from my XT926 using Tapatalk 2
    13
    I'm testing a new fix for the deep_sleep issues. If it's working correctly, I'll update this build.
    12
    Couple of notes:
    1. I'm seeing memory GC issues which look to be causing sleep issues. Investigating.
    2. The "About" screen shows 4.2 but it's actually 4.2.1 because we don't have the missing month bug.
    3. I need to research the missing multi-profiles issue.
    4. I'll check out photo sync options
    5. I'm also looking into USB camera support (will probably be more useful when the 3.4 kernel is ready)