> > 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 > > doing this will just confuse udev I suspect since it produces the right > links itself based on udev rules ... > > Ok, i will take them out, no problem.
> > > > > 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 > right (see above) ... did you use some adb version on the device before > that required you to accept a key on the PC ? it usually stores that > somewhere (I forgot where exactly, either under /cache or /data in some > "persist" directory) try to find it and delete the dir ... > Ok, no, our android version is 4.2 and in our android dont ask for any key. Anyway i will delete cache and all files and folders of data, keeping system.img only. But if i remember correctly in one of my test i deleted adbd file and the result was the same, it shows serial and offline... i will test it too. > > > > > > 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? > > > well, lets get adbd to work, then you can debug ... beyond this there is > always /proc/last_kmesg that you can look at from recovery after a > failed boot, might probably make sense to take a look there. > Yes, this is what i want... adbd working so i can debug and se what is the problem :). The /proc/last_kmsg method is not posible in our device because there is no a way to enter recovery directly, you need to enter bootloader menu and then go to recovery, so last_kmesg is overwriten by bootloader dmesg :(. Thanks Luis
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
