READ image: 13 offset: 0xf000 length: 0x1000 READ image: 13 offset: 0xe000 length: 0x1000 READ image: 13 offset: 0xd000 length: 0x1000 READ image: 13 offset: 0xc000 length: 0x1000 READ image: 13 offset: 0xb000 length: 0x1000 READ image: 13 offset: 0xa000 length: 0x1000 HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0 Many thanks for your assistance… Maybe the documentation needs to be updated…! and what I was seeing on the console did not match this…Īfter your comment that fastboot probably had installed, I tried booting into fastboot mode again, and this time it did work….Rescue image for DragonBoard 410c, boot into fastboot mode only When attempting to enable fastboot mode (which I had already done - successfully - several times before…) the system hung, before the ‘reset / fastboot: processing commands’ messages… I did check the switch settings etc… and retried several times… According to the documentation, the rescue sd process is supposed to produce a message similar to QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261 cmdline: root=/dev/mmcblk0p10 rw rootwait console=ttyMSM0,115200n8 androidboot.emmc=true rialno=b94c1d70 androidboot.baseband=apq adv7533_dsi2hdmi.panel=dsi mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_qcom,cc-debug-8936 failed to get ffbm cookie use_signed_kernel=0, is_unlocked=0, is_tampered=0. I really don’t want to completely reinstall everything, especially as I just got Fedora 22 running on the device, and was about to take a backup, before this happened… I have tested the setup with the standard ubuntu/qualcomm install image, and this loads/runs OK, so the sdcard can be read… I copied the ‘rescue’ image (db410c_sd_rescue.img) onto a spare SDcard, as per the instructions, but this did not update fastboot when booted…Īndroid Bootloader - UART_DM Initialized!!! The fastboot on my 410c stopped working, after a boot image install that failed…
0 Comments
Leave a Reply. |