New tests. This is what i added to my default boot cmdline datapart=/dev/mmcblk0p9 debug rw console=tty0,115200n8 no_console_suspend=1 and the result is the same.
I added too symlinks in init script: #Added symlinks for dev devices ln -s /dev/userdata /dev/mmcblk0p9 ln -s /dev/USERDATA /dev/block/mmcblk0p9 ln -s /dev/UDA /dev/block/platform/intel/by-uuid/80868086-8086-8086-8086-000000000008 ln -s /dev/DATAFS /dev/platform/intel/by-uuid/80868086-8086-8086-8086-000000000008 to make sure that i cover all the possibilities, but doesnt work :( Anyway, it's supposed that if this doesnt work adbd should start and this is not happening: List of devices attached 0123456789ABCDEF offline But in /scripts/panic/adbd i modified /sys/class/android_usb/android0/iSerial to AABBBCCCDDDEE and now when i do a adb devices i get: List of devices attached AABBBCCCDDDEE offline So init script is running, and it launch to panic/adb script, and /sys is working ok, but /sbin/adbd isnt :( I think that there is a problem with /dev, not mounting or something and this is why it doesnt mount data partition and adbd is not working (because i read somewhere that it needs /dev/urandom or something like this). Any clue of how i can test if /dev is working correctly or if i need to modify any udev configuration? Thanks --------------------------------------------------------------------------------------------- Que todos esos ceros y unos vayan directamente a tu mierdecilla de teléfono inteligente y que cualquier inutil sea capaz de suscribirse en 12 segundos *no es «magia», es sudor y talento.* On Tue, Mar 18, 2014 at 7:58 PM, Oliver Grawert <[email protected]> wrote: > hi, > Am Dienstag, den 18.03.2014, 19:52 +0100 schrieb Corvus: > > > > > > > > You can also edit your boot.img by hand as well (using abootimg), so > > > you can then just replace your custom initrd and use it to boot your > > > device. > > > > > > > My boot.img is not working with abootimg because is not standard. I > > cannot even extract it :-( > > > well, the ubuntu initrd should definitely work, just make sure to not > set a boot= arg (which should already get you adb (you don't get it > because you force boot=touch which is non-existent and will make /init > just fail without even switching to the script that will fire up adbd on > panic)) and give a proper device path to datapart=. > there should be no additional modification needed inside the initrd ... > > ciao > oli > > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : [email protected] > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp > >
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
