search

AsteroidOS / asteroid

Build script for AsteroidOS, an open-source operating system for smartwatches
http://asteroidos.org
GNU General Public License v2.0
872 stars 64 forks source link

LG Urbane in boot loop, possibly bricked #96

Closed frankgerhardt closed 4 years ago

frankgerhardt commented 4 years ago

I followed the instructions in https://asteroidos.org/install/bass/ using Debian 9.

Flashing worked fine:

$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
504KPLC0044952  unauthorized

$ adb reboot bootloader

$ fastboot flash userdata asteroid-image-bass.ext4
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'userdata'...
OKAY [  2.275s]
sending sparse 'userdata' 1/2 (262140 KB)...
OKAY [  8.682s]
writing 'userdata' 1/2...
OKAY [ 56.432s]
sending sparse 'userdata' 2/2 (174900 KB)...
OKAY [  5.792s]
writing 'userdata' 2/2...
OKAY [143.314s]
finished. total time: 216.494s

$ fastboot flash boot zImage-dtb-bass.fastboot
target reported max download size of 268435456 bytes
sending 'boot' (17754 KB)...
OKAY [  0.673s]
writing 'boot'...
OKAY [  1.374s]
finished. total time: 2.047s

$ fastboot continue
resuming boot...
OKAY [  0.002s]
finished. total time: 0.002s

After the last command, the watch booted, and rebooted, and rebooted. Adb can not find the watch any more.

The watch is connected to the charger. I can tell if it is fully chared or not. It was in the boot loop for many hours. The watch is quite hot (overheating?). Is the battery icon acting like a progress bar?

Can I somehow get into the fastboot menu again, to try flashing again? Any key "combination" for 

$ adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
504KPLC0044952  unauthorized

$ adb reboot bootloader

$ fastboot flash userdata asteroid-image-bass.ext4
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'userdata'...
OKAY [  2.275s]
sending sparse 'userdata' 1/2 (262140 KB)...
OKAY [  8.682s]
writing 'userdata' 1/2...
OKAY [ 56.432s]
sending sparse 'userdata' 2/2 (174900 KB)...
OKAY [  5.792s]
writing 'userdata' 2/2...
OKAY [143.314s]
finished. total time: 216.494s

$ fastboot flash boot zImage-dtb-bass.fastboot
target reported max download size of 268435456 bytes
sending 'boot' (17754 KB)...
OKAY [  0.673s]
writing 'boot'...
OKAY [  1.374s]
finished. total time: 2.047s

$ fastboot continue
resuming boot...
OKAY [  0.002s]
finished. total time: 0.002s

After the last command, the watch booted, and rebooted, and rebooted. Adb can not find the watch.

The watch is connected to the charger. I can tell if it is fully chared or not. It was in the boot loop for many hours. Is the battery icon acting like a progress bar?

Can I somehow get into the fastboot menu again, to try flashing again? Any key "combination" for pressing the single button?

output2

wgahnagl commented 4 years ago

Swipe down from the top left corner to the bottom right to open up the boot menu 👌

From there you should be able to flash again using fastboot

frankgerhardt commented 4 years ago

Thank you! That worked. I wiped everything and did a factory reset. Then I did not fastboot continue but Start from the bootloader.

ryanm101 commented 4 years ago

I just had exactly the same issue. Choosing start and not using fastboot continue worked for me too. Thanks for posting the fix