port jelly bean Unsuccesfull HELP NEEDED

---

I have not succesfully ported Android 4.1 Jelly Bean to our devices HELP NEEDED

Now i have one problem it's not booting

i see the Galaxy Tab 8.9 Logo after that a nexus s booting logo and the boot logo fades away really fast after that black screen on boot and not booting into Android 4.1

Any help is welcom

Originally Posted by safariking

I have succesfully ported Android 4.1 Jelly Bean to our devices

it's not booting

Rrrright

If it's not booting you didn't successfully port it, so i'm wondering how someone could help you.

There is no point in trying to port it. We will have Jelly Bean source in about two weeks. If ICS drivers work with JB, like everyone seems to think, then it should be easy to make it work.

But if you just want to play with it... What kernel and which Rom are you using as base? Did you extract the boot image and use our ICS kernel and rc files in ramdisk? Did you use libs from our ICS rom?

Originally Posted by poisike

There is no point in trying to port it. We will have Jelly Bean source in about two weeks. If ICS drivers work with JB, like everyone seems to think, then it should be easy to make it work.

But if you just want to play with it... What kernel and which Rom are you using as base? Did you extract the boot image and use our ICS kernel and rc files in ramdisk? Did you use libs from our ICS rom?

Used CM9 Nightly's and copied apps,framework,fonts and media from JB to CM9/ICS after that i have changed the updater-script and the build.prop file after that i have copied some other thing from JB to CM9/ICS!

Originally Posted by safariking

Used CM9 Nightly's and copied apps,framework,fonts and media from JB to CM9/ICS after that i have changed the updater-script and the build.prop file after that i have copied some other thing from JB to CM9/ICS!

I would try it the other way, copy our libs to JB rom. You probably need to copy our graphics libs, egl folder and hw folder. You probably need to use JB ramdisk and copy our rc files (with our device name) to it. You should also enable adb at boot, so you can see where it hangs. Then repack the boot.img with our kernel.

Originally Posted by poisike

I would try it the other way, copy our libs to JB rom. You probably need to copy our graphics libs, egl folder and hw folder. You probably need to use JB ramdisk and copy our rc files (with our device name) to it. You should also enable adb at boot, so you can see where it hangs. Then repack the boot.img with our kernel.

Im in the infuse forums and accidentally stumbled across this, but i have to point this out... You cannot simple take the ramdisk from another JB device and repackage it with yours. The ramdisk contains device specific information/files that differ from phone to phone.. So i dont think i need to explain what happens if you do what you suggested without making the necessary changes..

Originally Posted by scott.hart.bti

Im in the infuse forums and accidentally stumbled across this, but i have to point this out... You cannot simple take the ramdisk from another JB device and repackage it with yours. The ramdisk contains device specific information/files that differ from phone to phone.. So i dont think i need to explain what happens if you do what you suggested without making the necessary changes..

You are correct. I was in hurry when i wrote this and i didn't think about the possibility that the person who asked possibly doesn't know that.