u8220 serial number:unknow

[Guest jeffrey6705]

as title described.

my phone was unable to detect serial number in blue screen. ofcourse, i can get it from my box or take of the battery to see it.

But the major problem is, when i connect to windows, and type adb devices, it shows '?' insteads of any name.

by the way, it still can upload apk which the project i compiled. and the eclipse show '?' too :)

SO......anyone can help me??? because of that i can't see LOGCAT in adb, that was to frustated >.<

Help!!!

[Guest CarpetDiem]

Update another official rom?

[Guest Ellia]

It's a well known problem and I don't know any solution. I think it's kernel related.

[Guest jeffrey6705]

Update another official rom?

i guess that wont work, because i guess that isnt related with rom.

by the way, i have tried many unoffcial rom, still wont work.

Edited December 18, 2010 by jeffrey6705

[Guest jeffrey6705]

It's a well known problem and I don't know any solution. I think it's kernel related.

you got that problems too?? how about your phone in android 1.5 version? still same?

[Guest Ellia]

If I remember right official 1.5 have the same bug.

[Guest McSpoon]

The original release of the U8220 Android 1.5 didn't report the serial number. But when they released the kernel source code for it, we compiled it, and bizarrely it was working. So Pauls MCR roms at the time had it reporting the serial number correctly and even working in Eclipse.

Then they released the Eclair update which had the serial number broken again. It might be possible to fix it by hacking the Pulse 2.1 kernel source-code. But it remains unresolved for now.

[Guest jeffrey6705]

The original release of the U8220 Android 1.5 didn't report the serial number. But when they released the kernel source code for it, we compiled it, and bizarrely it was working. So Pauls MCR roms at the time had it reporting the serial number correctly and even working in Eclipse.

Then they released the Eclair update which had the serial number broken again. It might be possible to fix it by hacking the Pulse 2.1 kernel source-code. But it remains unresolved for now.

I am so pity :) seems like no cure >.<

thanks anyway!