Thread Previous • Date Previous • Date Next • Thread Next |
Here's some info, if they may help (including dmesg). I added a line to start adb into the init file in ubuntu initrd. The device boots, then adb starts. After a few minutes, adb stops working and after a few seconds the device reboots. "The device is in a bootloop or hangs on boot not showing up with adb shell: *boot into recovery mode and adb pull /proc/last_kmsg* to check the previous dmesg. Do not power off the device between the hang and booting into recovery as that likely leads to losing the ramconsole contents . Make sure you have proper permissions in the ramdisk and /init can start. Make sure you have a valid console=... argument on the kernel command line." Even after adding the lines to start adbd, there's still no /proc/last_kmsg. I rebooted directly from the stuck into recovery. The dmesg I attached is the one I get by running dmesg when the stuck is happening, before it reboots. Thanks, Rizqi (Trying to reply to the mailing list) On Dec 3, 2013 3:42 PM, "Reezqy Gilla" <xstinky12@xxxxxxxxx> wrote: > Anyway, here's some info, if they may help (including dmesg). I added a > line to start adb into the init file in ubuntu initrd. The device boots, > then adb starts. After a few minutes, adb stops working and after a few > seconds the device reboots. > > Thanks, > Rizqi > > > On Tue, Dec 3, 2013 at 3:38 PM, Reezqy Gilla <xstinky12@xxxxxxxxx> wrote: > >> >> >> >> On Mon, Dec 2, 2013 at 7:44 PM, Reezqy Gilla <xstinky12@xxxxxxxxx> wrote: >> >>> Thanks again for the fast reply. >>> Sorry but my device just stucks at splash screen, and adbd didn't start. >>> So I can't get last_kmsg since I have to pull out the battery first before >>> booting into recovery. >>> >>> "The device is in a bootloop or *hangs on boot not showing up with adb >>> shell*: boot into recovery mode and adb pull /proc/last_kmsg to check >>> the previous dmesg. Do not power off the device between the hang and >>> booting into recovery as that likely leads to losing the ramconsole >>> contents . Make sure you have proper permissions in the ramdisk and /init >>> can start. Make sure you have a valid console=... argument on the kernel >>> command line." >>> >>> Does the underlined word beans stuck on boot and not showing up on adb? >>> Then how do I "not power off the device between the hang and booting into >>> recovery"? >>> >>> And what does it mean by "valid console=... argument"? >>> >>> Thanks, >>> >>> Rizqi >>> >>> >>> On Mon, Dec 2, 2013 at 7:32 PM, Oliver Grawert <ogra@xxxxxxxxxx> wrote: >>> >>>> hi, >>>> On Mo, 2013-12-02 at 19:24 +0700, Reezqy Gilla wrote: >>>> > Thanks for the fast reply. >>>> > >>>> > May I ask one more thing? The kernel config for my device has >>>> > console=ttySAC3,115200n8 and androidboot.console=ttySAC3 boot >>>> > arguments by default. So should I change it? to what? >>>> > >>>> only if your system goes into a reboot loop after it switched from >>>> initrd to the rootfs (check /proc/last_kmsg from recovery mode in this >>>> case) if it boots fine into the rootfs this is not necessary ... >>>> >>>> ciao >>>> oli >>>> >>>> -- >>>> Mailing list: https://launchpad.net/~ubuntu-phone >>>> Post to : ubuntu-phone@xxxxxxxxxxxxxxxxxxx >>>> Unsubscribe : https://launchpad.net/~ubuntu-phone >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> >>> >> >
Attachment:
cmdline
Description: Binary data
Attachment:
consoles
Description: Binary data
Attachment:
dmesg
Description: Binary data
Attachment:
mounts
Description: Binary data
Thread Previous • Date Previous • Date Next • Thread Next |