After porting (I mean getting down in the mud porting, not replacing one or two files then doing a build.prop edit and calling it porting), you might run into a few problems. This is where logcat comes to the rescue. What then happens if adb is unable to detect your device or you get device offline whenever you run the adb devices command? Without a logcat to tell you what's wrong, you're flying blind in the porting skies.
In this brief guide, we'll be treating one technique that could help get adb and logcat dump working again.
* Setup Android kitchen (see http://forum.hovatek.com/thread-647.html )
* Ported ROM (Not the same as Port ROM)
* Base ROM
Hint: This guide assumes you've already ported the Port ROM to the Base ROM in Android Kitchen and have the working folder
you could try the
command as it helps fix some instances of device offline in adb. If that doesn't work, then proceed with this guide.
Copy the following files from the Base ROM to the Working folder (see http://forum.hovatek.com/thread-650.html ) of the Ported ROM
* system/xbin/busybox (if present)
* system/xbin/zip (if present)
* boot.img-ramdisk/default.prop (unpack > replace > repack boot.img)
In the update-script (META-INF > com > google > android) , add the following at the end
set_perm 0 2000 0755 SYSTEM:vendor/lib
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
show_progress 0.1 10
show_progress 0.2 0
show_progress 0.2 10
write_raw_image PACKAGE:boot.img BOOT:
You can now go ahead and build the ROM from the working folder