You will probably need to know how to this devices bootloader works. Does it allow you to modify the boot sequence? Can you access the boot sector, etc, etc? You will then need to figure out how to get and configure the proper linux kernel for the device. You know already that android 2.3.3 is already running (linux kernel 2.6.35, at least). Therefore, if you were able to get linux upgraded to the latest kernel of the android version you wanted to run, you could theoretically just "make" the proper android version for your device. Of course, you hit the nail on the head with the proprietary binaries/ hardware related libraries issue. One approach, if the device doesn't come with factory images (which it is required to do so, but its China, so it may exist, and I assume you don't read Mandarin : ) is to take proprietary image from another device with a similar locked down component and link the module into the linux kernel of your device. If it boots, who knows, it may work, and you can go from there. With this though, you are probably getting yourself into developing some pretty gnarly device modules. At least gnarly to someone who doesn't do them often. But I suppose this would be a great opportunity to do so!
R/ btlhs On Monday, July 23, 2012 11:45:26 PM UTC-7, Kevin K. wrote: > > Hi all, > One of my friends bought a 7' tablet (running Android 2.3.3) from China > few months back and he doesn't use it anymore. > No support is provided by the manufacturer (Factory images are not > available). Device configuration (exact info about hardware, etc.) is > unknown. > Can I still make a custom ROM for this device? What about proprietary > binaries / hardware-related libraries? > I wish to set up a separate project wherein I can checkout AOSP source > code and compile it to generate ROM. I don't want to do ROM modding (taking > a custom ROM of similar device and then replacing some of its files) > > Thanks, > KK > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
