[ROM-AOSP] [OLD] Stock Jelly Bean 4.1.2_r1 for the Kindle Fire [10-10]

Hashcode · Jul 11, 2012

AOSP JELLY BEAN 4.1.2_r1 straight from Google sources
This ROM is completely up-to-date w/ the 4AI1.7 kernel and latest ducati from TI

Download 4.1.2_r1 ROM here [10-10]
md5sum: d300fbbd65f3037f54519f7c3c2bc4a5
PLUS YOU WILL NEED TO FLASH GAPPS AFTER
Jelly Bean Gapps here

Data wipe might be required as this is 4.1.2_r1. If in doubt, wipe and use Titanium Backup to restore apps.

Make sure to WIPE Dalvik Cache.

BUILDING THIS ROM
I've updated GitHub with the local_manifest and patches for creating this rom from AOSP sources:
https://github.com/KFire-Android/android_local_manifest/tree/jb-aosp

Each patch should be applied via: git apply <patch name> in the respective project where it belongs.

Enjoy

Hashcode · Jul 11, 2012

FIXED AS OF 10/10:

[ Will fill in as bugs pop-up ]

neilrl79 · Jul 11, 2012

Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.

sthomas38 · Jul 11, 2012

First!

Thanks Hash ! This is were dual-boot takes its interest

.

EDIT: Not the first

.

tjrocks91 · Jul 11, 2012

neilrl79 said:
Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.

Seems possible except you need wifi to download terminal emulator from the play store unless you have the apk for terminal emulator saved on your kindle fire already.

Anyways thanks hashcode, I'm really looking forward to flashing this in the morning!

Hashcode · Jul 11, 2012

neilrl79 said:
Awesome Hash, you are the man. I don't suppose terminal emulator would work in place of ADB would it, I don't have a pc on hand.

I'm using "su" binary from AOSP.. which doesn't seem to want to work with Superuser from the market. Oddly, that puts many people who can't seem to get adb to work in a bind. Hrm. Probably the best way to fix it would be to use a "su" binary from another build and load it up in recovery by mounting system (use the recovery gui to do that), then:
adb push su /system/bin
adb shell
cd /system/bin
chmod 6755 su
chown root.root su
exit

Of course you can always wait and just play with it a bit, an I'll have all of this worked out for the next build w/ working HD codecs.

It's late and I need some sleep

QuBe2 · Jul 11, 2012

Thank you hashcode and if anybody tells you how to fix the UMS bug can you say it to me i also have a bug with the nexus sense 4 rom i also need to enable it

yourbrotherrex · Jul 11, 2012

Using terminal emulator I'm getting
"uid 10039 not allowed to su"
"1|u0_a39@android:/"
I can use ADB, but wondering if there's a quick way without hooking it up. (Ive got root explorer, another binary I can use, yada...)

Sent from my SPH-D710 using Tapatalk 2
Edit:
Nvmind: Adb fixed in 2 seconds.
Awesome work.

sthomas38 · Jul 11, 2012

Any chance we could have TabletUI insted of PhoneUI?

acax456 · Jul 11, 2012

Thanks. U are the best dev ever

Sent from my LG-P500 using xda premium

sthomas38 · Jul 11, 2012

BTW GApps don't work well, at least I don't have any setup at first boot and Play Store crashes.

And my ADB is a mess, Windows keeps thinking the device is in a pluged in/unpluged loop... On Ubuntu it works

. And I have no USB storage notification when my device is connected

.

EDIT: And pictures are rotated in multitasking panel

.

yourbrotherrex · Jul 11, 2012

Did y'all notice that the superuser binary is in system/xbin and not system/bin in the ROM?
I guess that's why my root explorer isnt working, because the command for it looking in the superuser app IS sys/bin.
So, you'll have to use adb to move it.
(You don't have to grab one from another build, in other words.)
Pull it from system/xbin and push to system/bin.

Sent from my Amazon Kindle Fire using Tapatalk 2

QuBe2 · Jul 11, 2012

yourbrotherrex said:
Did y'all notice that the superuser binary is in system/xbin and not system/bin in the ROM?
I guess that's why my root explorer isnt working, because the command for it looking in the superuser app IS sys/bin.
So, you'll have to use adb to move it.
(You don't have to grab one from another build, in other words.)
Pull it from system/xbin and push to system/bin.

Sent from my Amazon Kindle Fire using Tapatalk 2

what i have done

1) flash base rom
2) flash gapps 29/4
3) flash superuser the latest from this website
http://androidsu.com/superuser/

and i have just a smooth rom

Mazahhhistt · Jul 11, 2012

how to root 4.1?

otterdude · Jul 11, 2012

go to http://androidsu.com/superuser/ and flash the newest arm zip as QuBe2 said

vbdss · Jul 11, 2012

Is the interface the tablet interface or phone interface? Because i have installed and it seens a big phone

sthomas38 · Jul 11, 2012

That's the default UI for tablets since the Nexus 7 uses it, but it can be switched to TabletUI.

otterdude · Jul 11, 2012

nice for a beta it is pretty quick and I used the adb trick and I got wifi

vbdss · Jul 11, 2012

Cant get adb to work, only get no device on adb

otterdude · Jul 11, 2012

vbdss I can help maybe

what OS are you using

[ROM-AOSP] [OLD] Stock Jelly Bean 4.1.2_r1 for the Kindle Fire [10-10]

Senior Recognized Developer

Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Member

Senior Member

Senior Member

Member

Senior Member

Member

Similar threads

Top Liked Posts