ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Cannot communicate over adb/fastboot after flashing image

    Ask your questions right here!
    3
    20
    1165
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • tomT
      tom admin @Kashish Garg 0
      last edited by

      @Kashish-Garg-0 With your device plugged in to your host pc via usb, what do you see with lsusb on your host PC?

      Kashish Garg 0K 1 Reply Last reply Reply Quote 0
      • Kashish Garg 0K
        Kashish Garg 0 @tom
        last edited by

        @tom

        Bus 005 Device 008: ID 05c6:900e Qualcomm, Inc.
        

        Thanks for your help!

        tomT 1 Reply Last reply Reply Quote 0
        • tomT
          tom admin @Kashish Garg 0
          last edited by

          @Kashish-Garg-0 Okay so the device is booting into EDL mode, which is what is used for QDL flashing. Can you confirm that the EDL switch is turned off?

          Kashish Garg 0K 1 Reply Last reply Reply Quote 0
          • Kashish Garg 0K
            Kashish Garg 0 @tom
            last edited by Kashish Garg 0

            @tom Yes the EDL Switch is turned OFF, pointing away from the Processor

            tomT 1 Reply Last reply Reply Quote 0
            • tomT
              tom admin @Kashish Garg 0
              last edited by

              @Kashish-Garg-0 And when you went through the QDL process did the QDL flashing complete as expected? Should take around 10 minutes to complete

              Kashish Garg 0K 1 Reply Last reply Reply Quote 0
              • Kashish Garg 0K
                Kashish Garg 0 @tom
                last edited by

                @tom I just re ran it and it took around 7 minutes or so and gave the appropriate output:

                FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                <data>
                <log value="INFO: Calling handler for setbootablestoragedrive" /></data>
                FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                <data>
                <log value="INFO: Using scheme of value= 1" /></data>
                FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                <data>
                <response value="ACK" rawmode="false" /></data>
                FIREHOSE WRITE: <?xml version="1.0"?>
                <data><power value="reset"/></data>
                
                FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                <data>
                <log value="INFO: Calling handler for power" /></data>
                FIREHOSE READ: <?xml version="1.0" encoding="UTF-8" ?>
                <data>
                <response value="ACK" rawmode="false" /></data>
                
                tomT 1 Reply Last reply Reply Quote 0
                • tomT
                  tom admin @Kashish Garg 0
                  last edited by

                  @Kashish-Garg-0 And then if you remove and replace both power and usb is it still booting to that same mode?

                  Kashish Garg 0K 1 Reply Last reply Reply Quote 0
                  • Kashish Garg 0K
                    Kashish Garg 0 @tom
                    last edited by

                    @tom You mean is it going to EDL mode after replacing power/usb and moving the EDL Switch to off?

                    Bus 005 Device 011: ID 05c6:900e Qualcomm, Inc. USB2.0 Hub
                    

                    Is what is being printed with lsusb now

                    tomT 2 Replies Last reply Reply Quote 0
                    • tomT
                      tom admin @Kashish Garg 0
                      last edited by

                      @Kashish-Garg-0 Sounds like we'll have get an RMA going for this one: https://www.modalai.com/pages/rma

                      1 Reply Last reply Reply Quote 0
                      • tomT
                        tom admin @Kashish Garg 0
                        last edited by

                        @Kashish-Garg-0 It's possible your board has a QSM8250 (M0054-2) instead of a QRB5165 (M0054-1), see here for the diffs: https://docs.modalai.com/m0054-versions/#m0054-1-and-m0054-2

                        If that is the case then you will have to QDL using a different build, which you can download from downloads.modalai.com, look for M0054-2 Starling QDL Image 1.7.4 2024-02-09-1.7.4-M0054-2.zip under the "All" category

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Powered by NodeBB | Contributors