JBL Link View Rom

Search This thread


New member
Apr 30, 2020
I have a working unit now. Just unsure how to copy the rom off for the other unit I have.
Were you able to get the rom on to the demo unit by chance? I have a few demo and retail models and I'm hoping to get them working but there does not seem to be much information on this issue beyond this thread.


Sep 10, 2019
Were you able to get the rom on to the demo unit by chance? I have a few demo and retail models and I'm hoping to get them working but there does not seem to be much information on this issue beyond this thread.
This is the reply from JBL Support.

Thank you for contacting Harman Support. This case was endorsed to us, audio specialists and we will do our best to assist you regarding your concern. Please be advised that for the Link View, all demo speakers are manufactured to be displayed at authorized dealers for display purposes. There are no steps on how to remove them from demo mode even the reset procedure because their sole purpose is to be a demo unit. We suggest contacting the place where you bought it from as this place is not an authorized dealer.

Thank you for understanding.

I assume that most demo units supplied, are not fully functioning, however one of the units I have was fully functioning, prior to a JBL merchandiser installing a standard stock unit. The standard reset (holding both volume buttons at the same time) won't work.


Sep 10, 2019
it does not make sense that they would make a special separate motherboard just for demo units.
Plenty of companies do it, or they leave a daughterboard off. EG JBL portable speakers, and UE Boom demo units don't have bluetooth. Sony are one of teh few that have a full working unit, as well as Apple. Sony will usually give a full/partial credit on the demo, whereas typical Apple don't do anything on their Homepods.


New member
May 28, 2020
I have a working unit now. Just unsure how to copy the rom off for the other unit I have.

Hello. Any update with copying the rom?

---------- Post added at 12:24 PM ---------- Previous post was at 12:20 PM ----------

This is the information I was sent via PM from andrukarc . No idea if it is correct or not.

here is a link on how to extract a backup
I can't do it because there is no place to buy in my country. JBL link View they are not supported in Ukraine and so they are not imported here, but I have a demo model and I would also like to revive it.
If so backup then we flash the device and it will become like a regular model.
I know how to go into firmware mode and solder for this program.

Hello. Any update with updating the firmware?


Senior Member
Dec 4, 2015
New Britain, Connecticut
Google Pixel 4a
All you need to do It’s just purchase a replacement logic board for whichever version you have then take the speaker part and replace the logic board and you’ll have a functional speaker here this is a link to the JBL link 300 logic board just to give you an example


In all honesty though these devices are not simply demo models that can’t be taken out of their current state their actual devices which were meant for sale that the stores that bought them probably get instructions from JBL on how to place them in demo mode it’s honestly going to be some combination of buttons being held down for upwards of 30 seconds try everyone you can. Stores don’t really produce like the demo models anymore they just have secret methods that they don’t inform the public about and instead inform retailers but these devices are identical to the ones that are sold normally I’ve stripped them down and seen both of them edit it’s not a locked firmware it’s just a locked mode that it’s in with no clear instructions on how to get out as of right this moment

Start with holding volume up and connect for as much is a minute without releasing it
Last edited:


Senior Member
Dec 4, 2015
New Britain, Connecticut
Google Pixel 4a
I can confirm I bought a JBL link 300 today in demo mode he just arrived and I managed to get it out of demo mode by holding the play button in the plus button on top until the Wi-Fi icon on the bottom of the device blinked a few times I held it for maybe 30 to 1 minute in total so I can confirm that they’re not different models they are exactly the ones that are being sold just in a separate mode


New member
Apr 27, 2019
Okay, several facts that we have:
  • Old fact 1: when you hold "Volume Up" button in will load in "Recovery Mode", but this recovery mode hasn't any function, as I see
  • Old fact 2: when you connect to PC via USB cable, PC will recognize device as "Qualcomm HS-USB Android DIAG 901D" (also known as Diagnostic Mode), what we can do with device in this mode is unknown.
  • Semi-New fact: To boot in fastboot you need to click multiple times "Volume Down" button when device is booting after power off, and it will give you several seconds to begin use fastboot mode, or it will just continue booting (but when you'll sent any fastboot command as like "fastboot oem device-info" it will continue work in fastboot mode) :)
    Here is some info which I get from device:

    C:\adb>fastboot oem device-info
    (bootloader) Device tampered: false
    (bootloader) Device unlocked: false
    (bootloader) Device critical unlocked: false
    (bootloader) Charger screen enabled: false
    (bootloader) Display panel:
    OKAY [ 0.058s]
    Finished. Total time: 0.059s

    C:\adb>fastboot oem unlock
    FAILED (remote: 'oem unlock is not allowed')
    fastboot: error: Command failed

    C:\adb>fastboot flashing unlock
    FAILED (remote: 'oem unlock is not allowed')
    fastboot: error: Command failed

    C:\adb>fastboot getvar all
    (bootloader) version:0.5
    (bootloader) battery-soc-ok:yes
    (bootloader) battery-voltage:3902000
    (bootloader) unlocked:no
    (bootloader) secure:yes
    (bootloader) version-baseband:
    (bootloader) version-bootloader:
    (bootloader) display-panel:
    (bootloader) off-mode-charge:0
    (bootloader) charger-screen-enabled:0
    (bootloader) max-download-size: 0x1fe00000
    (bootloader) at-attest-uuid:3FED472C636D443297A3932DD5A22AE4
    (bootloader) at-attest-dh:1: p256
    (bootloader) slot-count:2
    (bootloader) current-slot:b
    (bootloader) slot-retry-count:b:5
    (bootloader) slot-successful:b:yes
    (bootloader) slot-active:b:yes
    (bootloader) slot-unbootable:b:no
    (bootloader) slot-retry-count:a:4
    (bootloader) slot-successful:a:yes
    (bootloader) slot-active:a:no
    (bootloader) slot-unbootable:a:no
    (bootloader) has-slot:dpo:no
    (bootloader) has-slot:msadp:no
    (bootloader) has-slot:apdp:no
    (bootloader) has-slot:keymaster:yes
    (bootloader) has-slot:mcfg:no
    (bootloader) has-slot:syscfg:no
    (bootloader) has-slot:dip:no
    (bootloader) has-slot:limits:no
    (bootloader) has-slot:dsp:yes
    (bootloader) has-slot:cmnlib:yes
    (bootloader) has-slot:config:no
    (bootloader) has-slot:keystore:no
    (bootloader) has-slot:devinfo:no
    (bootloader) has-slot:userdata:no
    (bootloader) has-slot:factory:no
    (bootloader) has-slot: oem_bootloader:yes
    (bootloader) has-slot: oem:yes
    (bootloader) has-slot:vendor:yes
    (bootloader) has-slot:vbmeta:yes
    (bootloader) has-slot:system:yes
    (bootloader) has-slot:boot:yes
    (bootloader) has-slot:sec:no
    (bootloader) has-slot:fsg:no
    (bootloader) has-slot: DDR:no
    (bootloader) has-slot:ssd:no
    (bootloader) has-slot:fsc:no
    (bootloader) has-slot:misc:no
    (bootloader) has-slot:modemst2:no
    (bootloader) has-slot:modemst1:no
    (bootloader) has-slot:devcfg:yes
    (bootloader) has-slot:tz:yes
    (bootloader) has-slot:rpm:yes
    (bootloader) has-slot:aboot:yes
    (bootloader) has-slot:sbl1:yes
    (bootloader) has-slot:bluetooth:yes
    (bootloader) has-slot:drm:yes
    (bootloader) has-slot:modem:yes
    (bootloader) has-slot: persist:no
    (bootloader) partition-type:dpo:
    (bootloader) partition-size:dpo: 0x2e00
    (bootloader) partition-type:msadp:
    (bootloader) partition-size:msadp: 0x40000
    (bootloader) partition-type:apdp:
    (bootloader) partition-size:apdp: 0x40000
    (bootloader) partition-type:keymaster_b:
    (bootloader) partition-size:keymaster_b: 0x100000
    (bootloader) partition-type:keymaster_a:
    (bootloader) partition-size:keymaster_a: 0x100000
    (bootloader) partition-type:mcfg:
    (bootloader) partition-size:mcfg: 0x400000
    (bootloader) partition-type:syscfg:
    (bootloader) partition-size:syscfg: 0x80000
    (bootloader) partition-type:dip:
    (bootloader) partition-size:dip: 0x100000
    (bootloader) partition-type:limits:
    (bootloader) partition-size:limits: 0x8000
    (bootloader) partition-type:dsp_b:
    (bootloader) partition-size:dsp_b: 0x1000000
    (bootloader) partition-type:dsp_a:
    (bootloader) partition-size:dsp_a: 0x1000000
    (bootloader) partition-type:cmnlib_b:
    (bootloader) partition-size:cmnlib_b: 0x100000
    (bootloader) partition-type:cmnlib_a:
    (bootloader) partition-size:cmnlib_a: 0x100000
    (bootloader) partition-type:config:
    (bootloader) partition-size:config: 0x80000
    (bootloader) partition-type:keystore:
    (bootloader) partition-size:keystore: 0x80000
    (bootloader) partition-type:devinfo:
    (bootloader) partition-size:devinfo: 0x100000
    (bootloader) partition-type:userdata: ext4
    (bootloader) partition-size:userdata: 0x434bd000
    (bootloader) partition-type:factory_bootloader:
    (bootloader) partition-size:factory_bootloader: 0x1000000
    (bootloader) partition-type:factory:
    (bootloader) partition-size:factory: 0x2000000
    (bootloader) partition-type: oem_bootloader_b:
    (bootloader) partition-size: oem_bootloader_b: 0x400000
    (bootloader) partition-type: oem_bootloader_a:
    (bootloader) partition-size: oem_bootloader_a: 0x400000
    (bootloader) partition-type: oem_b:
    (bootloader) partition-size: oem_b: 0x1f400000
    (bootloader) partition-type: oem_a:
    (bootloader) partition-size: oem_a: 0x1f400000
    (bootloader) partition-type:vendor_b:
    (bootloader) partition-size:vendor_b: 0x8000000
    (bootloader) partition-type:vendor_a:
    (bootloader) partition-size:vendor_a: 0x8000000
    (bootloader) partition-type:vbmeta_b:
    (bootloader) partition-size:vbmeta_b: 0x10000
    (bootloader) partition-type:vbmeta_a:
    (bootloader) partition-size:vbmeta_a: 0x10000
    (bootloader) partition-type:system_b: ext4
    (bootloader) partition-size:system_b: 0x20000000
    (bootloader) partition-type:system_a: ext4
    (bootloader) partition-size:system_a: 0x20000000
    (bootloader) partition-type:boot_b:
    (bootloader) partition-size:boot_b: 0x2000000
    (bootloader) partition-type:boot_a:
    (bootloader) partition-size:boot_a: 0x2000000
    (bootloader) partition-type:sec:
    (bootloader) partition-size:sec: 0x4000
    (bootloader) partition-type:fsg:
    (bootloader) partition-size:fsg: 0x180000
    (bootloader) partition-type: DDR:
    (bootloader) partition-size: DDR: 0x8000
    (bootloader) partition-type:ssd:
    (bootloader) partition-size:ssd: 0x2000
    (bootloader) partition-type:fsc:
    (bootloader) partition-size:fsc: 0x400
    (bootloader) partition-type:misc:
    (bootloader) partition-size:misc: 0x100000
    (bootloader) partition-type:modemst2:
    (bootloader) partition-size:modemst2: 0x180000
    (bootloader) partition-type:modemst1:
    (bootloader) partition-size:modemst1: 0x180000
    (bootloader) partition-type:devcfg_b:
    (bootloader) partition-size:devcfg_b: 0x40000
    (bootloader) partition-type:devcfg_a:
    (bootloader) partition-size:devcfg_a: 0x40000
    (bootloader) partition-type:tz_b:
    (bootloader) partition-size:tz_b: 0x200000
    (bootloader) partition-type:tz_a:
    (bootloader) partition-size:tz_a: 0x200000
    (bootloader) partition-type:rpm_b:
    (bootloader) partition-size:rpm_b: 0x80000
    (bootloader) partition-type:rpm_a:
    (bootloader) partition-size:rpm_a: 0x80000
    (bootloader) partition-type:aboot_b:
    (bootloader) partition-size:aboot_b: 0x100000
    (bootloader) partition-type:aboot_a:
    (bootloader) partition-size:aboot_a: 0x100000
    (bootloader) partition-type:sbl1_b:
    (bootloader) partition-size:sbl1_b: 0x80000
    (bootloader) partition-type:sbl1_a:
    (bootloader) partition-size:sbl1_a: 0x80000
    (bootloader) partition-type:bluetooth_b:
    (bootloader) partition-size:bluetooth_b: 0x80000
    (bootloader) partition-type:bluetooth_a:
    (bootloader) partition-size:bluetooth_a: 0x80000
    (bootloader) partition-type:drm_b:
    (bootloader) partition-size:drm_b: 0x400000
    (bootloader) partition-type:drm_a:
    (bootloader) partition-size:drm_a: 0x400000
    (bootloader) partition-type:modem_b:
    (bootloader) partition-size:modem_b: 0x2000000
    (bootloader) partition-type:modem_a:
    (bootloader) partition-size:modem_a: 0x2000000
    (bootloader) partition-type: persist:
    (bootloader) partition-size: persist: 0x800000
    (bootloader) serialno: * HERE WAS SOME HEX CODE *
    (bootloader) kernel:lk
    (bootloader) variant:msm8x53_som_pr
    (bootloader) product:msm8x53
    Finished. Total time: 1.779s
  • New fact: also, if load with click on both buttons you can activate Download Mode on device, and it will be recognized as "Qualcomm HS-USB QDLoader 9008" (also known as Download Mode)

Also interesting answer from JBL support:
Based on the serial number you have provided us, this seems to be a Demo unit which is only meant to be displayed in retail stores, and is not meant to be sold to customers.

I am pretty sure that there is not a way to flash the firmware of this unit, but I am escalating your case to our specialists in order to be one hundred percent sure about this. As I can imagine it is no fun to have a Link View without the option to actually use it.

Irek66, maybe you can try to boot your normal link view in recovery mode and try to see if it will load normal recovery, please?

Also, if it wouldn't be possible to get original firmware, maybe let's try to flash custom one rom. It's seems that Lenovo Tab 4 Plus and Lenovo Tab 3 Plus based on similar chip :)
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Hello I have both units, DEMO and fully a working one. What's next?
  • 2
    Today I accidentally erased the system partition via Fastboot. And now it doesn't show the demo clip. This means I need to load the system.img into it . But how to pull this partition from the working device - I don't know yet. I keep looking for a method. I think JBL use Snapdragon 625 APQ8053 and Android Things OS. If I could get developer mode I would use ADB to download system.img from working device
    I've got a working Link 10 if anyone can point me in the right direction. Is the firmware/hardware the same? How could I copy it without blowing up my Speaker.... ??
    Try to Keep This Thread Up……
    Hello I have both units, DEMO and fully a working one. What's next?
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone