If you can figure out the hardware (including processor/GPIO 
pins/flash/etc...), you can try building a Linux kernel for it. Once you 
get a working Linux kernel (with Android patches), you still need to find a 
way to enter some recovery/bootloader modes in order to flash it. If you 
don't need kernel changes, you can probably ignore them, but first make a 
backup of the system partition. You can also extract many device-specific 
information from the initramfs so also backup the ramdisk. You can usually 
find some init.*.rc files under the root directory, which are also 
device-specific information (usually except init.goldfish.rc). You can then 
try to compile a "vanilla" AOSP and try to flash it to the device, but 
probably many hardware will not work. You will need to work them out 
yourself.

I've once tried to port Android 2.3.7 to a device (which was originally 
Windows Mobile), the device can function, but some drivers are missing so 
functionality is restricted.

Kevin K.於 2012年7月24日星期二UTC+8下午2時45分26秒寫道:
>
>  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

Reply via email to