Forums - RB5 can't reboot after QFIL or MULTIDL_TOOL to flash image

12 posts / 0 new
Last post
RB5 can't reboot after QFIL or MULTIDL_TOOL to flash image
viclin
Join Date: 24 Apr 19
Posts: 8
Posted: Tue, 2021-02-23 17:42

Usually, I use QFIL to flash image, after complete, RB5 can reboot normally.

but now, after QFIL, RB5 can't reboot normally, I just see green LED ( power LED) light 3 sec after QFIL show success, and green LED off.

I can't get any response by key "abd device".

and RB5 can enter 9008 mode, then try QFIL again, it still also same phenomenon.

and I use MULTIDL_TOOL_v1.0.14 aslo get same phenomenon.

  

 

  • Up0
  • Down0
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Wed, 2021-02-24 09:39

Where do you get QFIL image? I think you should use sdkmanger to update system image.

Let me know details.

  • Up0
  • Down0
mistry Moderator
Join Date: 18 Apr 18
Posts: 56
Posted: Wed, 2021-02-24 11:57

Hi Viclin,

If I understand correctly, you were able to flash and boot the device with QFIL previously.
But now it does not work? What has changed?
Is it a new image that you are flashing? 

Is the device still in EDL mode after you boot up? What do you see in the device manager?
Can you please capture the debug log from QFIL and from the USB port on RB5?

Thanks for sharing this information, it will help us troubleshoot.

 

  • Up0
  • Down0
viclin
Join Date: 24 Apr 19
Posts: 8
Posted: Thu, 2021-02-25 18:51

Dear Expert,

I get SW image from Qualcomm QRB5165.LE.1.0-00005-STD.PROD-1, and use QFIL to flash image.

do you have test image that I can flash it on this broken board?

I swap pcie1 and pcie2, then use fastboot to flah image, after flash complete, then fastboot reboot RB5, but happen can't boot up.

Then I use QFIL to flash original SW image ( no swap pcie1/pcie2), then flash complete, LED light a little time, then off.

then I check device manager, it can't find camera. ( without 9008 and 901D)

But I can press button to enable 9008 ( edl) mode again, and use QFIL to flash again, then happen can't boot up again.

 

 

  • Up0
  • Down0
viclin
Join Date: 24 Apr 19
Posts: 8
Posted: Thu, 2021-02-25 18:52

Dear Expert,

I get SW image from Qualcomm QRB5165.LE.1.0-00005-STD.PROD-1, and use QFIL to flash image.

do you have test image that I can flash it on this broken board?

I swap pcie1 and pcie2, then use fastboot to flah image, after flash complete, then fastboot reboot RB5, but happen can't boot up.

Then I use QFIL to flash original SW image ( no swap pcie1/pcie2), then flash complete, LED light a little time, then off.

then I check device manager, it can't find camera. ( without 9008 and 901D)

But I can press button to enable 9008 ( edl) mode again, and use QFIL to flash again, then happen can't boot up again.

 

 

  • Up0
  • Down0
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Tue, 2021-03-02 10:22

Make your board as original setting and QFIL your baord, you can connect debugging USB  and get the boot-up log message.

  • Up0
  • Down0
viclin
Join Date: 24 Apr 19
Posts: 8
Posted: Thu, 2021-03-04 02:39

by coneect USB, and try to get debug log. unfortunately, I can't see any message ouput by putty screen. ( I try to use normal RB5 board, I can see some message show in putty)

  • Up0
  • Down0
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Thu, 2021-03-04 11:56

It is better to use sdkmanager to flash images to device.

Can you give me the link to QFIL image you flashed to device?

I will try it.

 

  • Up0
  • Down0
viclin
Join Date: 24 Apr 19
Posts: 8
Posted: Thu, 2021-03-04 17:39

Please get flash image from  https://drive.google.com/drive/folders/1zzdPrq7e8al9pxmKHS3WsD6fteFEbryL...

About use "sdkmanager to flash images to device", do you mean to use MULTIDL_TOOL_v1.0.14?

 

 

 

  • Up0
  • Down0
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Mon, 2021-03-08 08:23

Hi viclin

I could use QFIL to update the images from the link you provide.

but I think that is old release version, please use sdkmanger to update your board

/ $
/ $
/ $ ls -l
total 120
drwxr-xr-x    3 root     root          4096 Jan  7  2021 WEBSERVER
drwxr-xr-x    2 root     root          4096 Jan  7  2021 bin
drwxr-xr-x    2 root     root          4096 Jan  7  2021 boot
drwxr-xr-x    3 root     root         16384 Jan  1 00:00 bt_firmware
-rw-r--r--    1 leprop   leprop        1039 Jan  7  2021 build.prop
drwxr-xr-x    1 root     root          4096 Jan  7  2021 cache
drwxr-xr-x    1 root     root          4096 Jan  7  2021 data
drwxr-xr-x   18 root     root          8640 Jan  1 00:03 dev
drwxr-xr-x    6 root     root          4096 Jan  1 00:00 dsp
drwxr-xr-x    1 root     root          4096 Jan  7  2021 etc
drwxr-xr-x    4 root     root         16384 Jan  1 00:00 firmware
drwxr-xr-x   25 root     root          4096 Jan  7  2021 home
drwxr-xr-x   10 root     root          4096 Jan  7  2021 lib
drwx------    2 root     root          4096 Jan  1 00:00 lost+found
drwxr-xr-x    9 root     root          4096 Jan  7  2021 media
drwxr-xr-x    3 root     root          4096 Jan  7  2021 mnt
drwxr-xr-x    9 root     root          4096 Jan  1 00:00 overlay
drwxr-xr-x    4 root     root          4096 Jan  1 00:03 persist
dr-xr-xr-x  541 root     root             0 Jan  1 00:00 proc
drwxr-xr-x    2 root     root          4096 Jan  7  2021 res
drwxr-xr-x   15 root     root           480 Jan  1 00:03 run
drwxr-xr-x    4 root     root          4096 Jan  7  2021 sbin
lrwxrwxrwx    1 root     root            11 Jan  7  2021 sdcard -> /mnt/sdcard
dr-xr-xr-x   13 root     root             0 Jan  1 00:03 sys
drwxr-xr-x    4 root     root          4096 Jan  7  2021 system
-rw-r--r--    1 root     root            12 Jan  7  2021 target
drwxrwxrwt    4 root     root           100 Jan  1 00:03 tmp
drwxr-xr-x   11 root     root          4096 Jan  7  2021 usr
drwxr-xr-x    8 root     root          4096 Jan  7  2021 var
drwxr-xr-x    3 root     root          4096 Jan  7  2021 vendor
/ $
/ $
/ $ su
Password:
/ $ su
Password:
/ #
/ #
 
  • Up0
  • Down0
kevin.dai
Join Date: 21 Oct 20
Posts: 137
Posted: Mon, 2021-03-08 08:29
  • Up0
  • Down0
mita.rathod
Join Date: 17 Sep 18
Posts: 59
Posted: Mon, 2021-04-05 11:38

H/W failure caused device boot up issue. H/W replacement resolved issue and hence closing the ticket

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.