MIUI for Nexus 7

Search This thread

timmytim

Senior Member
Jan 6, 2011
1,695
2,498
Phoenix
So I have good news and bad news.........

Good News = I finally got a logcat at boot!!!!

Bad News = I cannot yet decipher it so I have to reach out to the community over in the Q&A section.

Im still working on it boys and girls :)
 

Attachments

  • logcat.txt
    354.2 KB · Views: 13

timmytim

Senior Member
Jan 6, 2011
1,695
2,498
Phoenix
So I have good news and bad news.........

Good News = I finally got a logcat at boot!!!!

Bad News = I cannot yet decipher it so I have to reach out to the community over in the Q&A section.

Im still working on it boys and girls :)


Got past those errors and now on to the next ones. Man, I need to have a few stiff drinks after this port, lol. I just hope it boots soon. haha
 

glukosio

Senior Member
Dec 11, 2009
351
47
Verona
So I have good news and bad news.........

Good News = I finally got a logcat at boot!!!!

Bad News = I cannot yet decipher it so I have to reach out to the community over in the Q&A section.

Im still working on it boys and girls :)

i think that the problem might be again with dalvikVM, it goes on until dalvik and then it's aborting VM ang goes on in loop again... of course it's as far as i understood from logcat
Code:
...
D/dalvikvm(  128): Trying to load lib libjavacore.so 0x0

D/dalvikvm(  128): Added shared lib libjavacore.so 0x0

W/dalvikvm(  128): Unable to register: not native: Llibcore/icu/ICU;.getBestDateTimePattern:(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;

E/dalvikvm(  128): JNI posting fatal error: RegisterNatives failed for 'libcore/icu/ICU'; aborting...

I/dalvikvm(  128): Can't dump thread 1: threadObj not set

E/dalvikvm(  128): VM aborting

F/libc    (  128): Fatal signal 6 (SIGABRT) at 0x00000080 (code=-6), thread 128 (zygote)

I/DEBUG   (  126): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG   (  126): Build fingerprint: 'google/nakasi/grouper:4.4/KRT16S/920375:user/release-keys'
...

i think it may be the same problem as from last_kmsg
 
  • Like
Reactions: timmytim

timmytim

Senior Member
Jan 6, 2011
1,695
2,498
Phoenix
i think that the problem might be again with dalvikVM, it goes on until dalvik and then it's aborting VM ang goes on in loop again... of course it's as far as i understood from logcat
Code:
...
D/dalvikvm(  128): Trying to load lib libjavacore.so 0x0

D/dalvikvm(  128): Added shared lib libjavacore.so 0x0

W/dalvikvm(  128): Unable to register: not native: Llibcore/icu/ICU;.getBestDateTimePattern:(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;

E/dalvikvm(  128): JNI posting fatal error: RegisterNatives failed for 'libcore/icu/ICU'; aborting...

I/dalvikvm(  128): Can't dump thread 1: threadObj not set

E/dalvikvm(  128): VM aborting

F/libc    (  128): Fatal signal 6 (SIGABRT) at 0x00000080 (code=-6), thread 128 (zygote)

I/DEBUG   (  126): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG   (  126): Build fingerprint: 'google/nakasi/grouper:4.4/KRT16S/920375:user/release-keys'
...

i think it may be the same problem as from last_kmsg

I was actually able to get past this one. The issue was that the core.jar smali: Llibcore/icu/ICU was looking for this smali code:.getBestDateTimePattern and it didnt exist in the MIUI ROM so I swapped out the core.jar from the AOSP ROM and it fixed that.

Now I am getting error related to another smali in framework.jar. The weird problem is that I added the smali code but it still wont get past the error. I even replaced the entire file which should have worked because it was supposedly a non-required smali and it still throws the same error. I will upload the new logcat so ya'll can see it.
 

timmytim

Senior Member
Jan 6, 2011
1,695
2,498
Phoenix
Im getting the weirdest Logcat errors that I am having so much trouble with. MIUI V6 for the Nexus 7 2013 is built on KRT16O and I cannot find an AOSP ROM for our 2012 model that is KRT16O, I can only find KRT16S which Im guessing (because of all the issues) is part of the problem since the frameworks are different even though it was just a slight update.

Anyone got a KRT16O ROM/Factory Firmware stashed anywhere from when Google released it? You cannot download that version from the Nexus Firmware Page.

In the meantime I am working on a new Miui V5 ROM to hold us over, lol.

Porting V6 will be much easier once Miui releases the source to the Patchrom project. :fingers-crossed:
 

Kotaless

Senior Member
Im getting the weirdest Logcat errors that I am having so much trouble with. MIUI V6 for the Nexus 7 2013 is built on KRT16O and I cannot find an AOSP ROM for our 2012 model that is KRT16O, I can only find KRT16S which Im guessing (because of all the issues) is part of the problem since the frameworks are different even though it was just a slight update.

Anyone got a KRT16O ROM/Factory Firmware stashed anywhere from when Google released it? You cannot download that version from the Nexus Firmware Page.

In the meantime I am working on a new Miui V5 ROM to hold us over, lol.

Porting V6 will be much easier once Miui releases the source to the Patchrom project. :fingers-crossed:

Here KRT16O :good:
https://dl.google.com/dl/android/aosp/nakasi-krt16o-factory-db4a1a8a.tgz
 

timmytim

Senior Member
Jan 6, 2011
1,695
2,498
Phoenix
Can you say Miui v6 for the grouper? Finally!

Working out some very minor bugs but will be uploading as an alpha for now even though it seems really stable. Oh and it's based on KK 4.4.2 ;)

This would not be possible without the assistance of my buddy @pspunderground
 

Attachments

  • 20140330_075551.jpg
    20140330_075551.jpg
    262.5 KB · Views: 167
  • 20140330_075727.jpg
    20140330_075727.jpg
    260.6 KB · Views: 161

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    Xiaomi just released a Beta MIUI V5 for Nexus 7 2013, maybe one of our talented devs can port it over?


    Way ahead of you :good:

    Been trying to get it to boot on the Grouper for about a week. I will let ya know how far I get with it in a couple days. May need some help on this one though since the devices are so different. Im really diggin that tablet UI though. About damn time Miui did that :p

    Here are the screen shots if you want to see what it looks like: http://en.miui.com/thread-16879-1-1.html
    5
    Coming soon, I promise. I'm fixing a keyboard bug at the moment then I will upload


    Have at it! Let me know what you think

    http://xdaforums.com/showthread.php?t=2700212
    5
    So I have good news and bad news.........

    Good News = I finally got a logcat at boot!!!!

    Bad News = I cannot yet decipher it so I have to reach out to the community over in the Q&A section.

    Im still working on it boys and girls :)
    5
    Can you say Miui v6 for the grouper? Finally!

    Working out some very minor bugs but will be uploading as an alpha for now even though it seems really stable. Oh and it's based on KK 4.4.2 ;)

    This would not be possible without the assistance of my buddy @pspunderground
    4
    i think that the problem might be again with dalvikVM, it goes on until dalvik and then it's aborting VM ang goes on in loop again... of course it's as far as i understood from logcat
    Code:
    ...
    D/dalvikvm(  128): Trying to load lib libjavacore.so 0x0
    
    D/dalvikvm(  128): Added shared lib libjavacore.so 0x0
    
    W/dalvikvm(  128): Unable to register: not native: Llibcore/icu/ICU;.getBestDateTimePattern:(Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String;
    
    E/dalvikvm(  128): JNI posting fatal error: RegisterNatives failed for 'libcore/icu/ICU'; aborting...
    
    I/dalvikvm(  128): Can't dump thread 1: threadObj not set
    
    E/dalvikvm(  128): VM aborting
    
    F/libc    (  128): Fatal signal 6 (SIGABRT) at 0x00000080 (code=-6), thread 128 (zygote)
    
    I/DEBUG   (  126): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    
    I/DEBUG   (  126): Build fingerprint: 'google/nakasi/grouper:4.4/KRT16S/920375:user/release-keys'
    ...

    i think it may be the same problem as from last_kmsg

    I was actually able to get past this one. The issue was that the core.jar smali: Llibcore/icu/ICU was looking for this smali code:.getBestDateTimePattern and it didnt exist in the MIUI ROM so I swapped out the core.jar from the AOSP ROM and it fixed that.

    Now I am getting error related to another smali in framework.jar. The weird problem is that I added the smali code but it still wont get past the error. I even replaced the entire file which should have worked because it was supposedly a non-required smali and it still throws the same error. I will upload the new logcat so ya'll can see it.