hi, Am Samstag, den 11.10.2014, 09:55 +0100 schrieb Dave Morley: > I updated my phone over ota this morning and am stuck on BQ logo with > no movement, no adb shell, and no way to recover without a pc. and a > fresh flash > to debug such cases you can switch adb into not depening on the session startup:
Bring the device into recovery mode ... mako: adb shell mount /data/ubuntu.img /cache/system echo "start on android-container persist.sys.usb.config=*adb" >/cache/system/etc/init/android-tools-adbd.override exit adb reboot krillin: adb shell mount /system echo "start on android-container persist.sys.usb.config=*adb" >/system/etc/init/android-tools-adbd.override exit adb reboot now your device should bring up adb even if there is no session starting and the emergency shell doess not kick in after a while. i'm working on a DeveloperMode wikipage where such info will be aggregated. > I don't know if the image got screwed up or if a mesa package got > pulled in by mistake. http://people.canonical.com/~ogra/touch-image-stats/rtm/98.changes we definitely had a Mir update ... and yes, that seems to have a messy dependency on a mesa lib ... :( 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
