HP Scanjet 7000 deleted partition

[El_Jeezy]

Hello,

Does anyone have the recovery steps for reviving an HP ScanJet 7000 after its partition has been deleted? I had a tech select that option while troubleshooting and now it has no real OS to boot into other than the shell OS. We've tried connecting it to the web, but it realy doesn't do anything.

Any help provided would be appreciated.

Thanks,

LGz

[DanielVSG]

Same Problem here.....:catsad:

[SHThompson]

Replace the hard drive with a new one from HP.

This is a futuresmart firmware machine, but it doesn't behave as well as the newer futuresmart devices.

[DanielVSG]

Hi,

thank you for your answer.

I tried a HDD from a working device in this broken device.

It was working fine, so i thought i can clone this working HDD to the disk which was unable to boot.

I´ve done it with Acronis.

The disk was cloned and the partitions were back, but in the device ist still says "Disk not bootable" but on my laptop the disk seems to be okay....and is a exact copy of the working one....

When i order a new disk from HP, is this disk allready partitioned?

With all data needed for this device to start?

I have the problem that i can not install the firmware trough the preboot menu, because i don´t know how to send the firmware to it....

After i configured network in the preboot menu and select "firmware download", it says "waiting for connection on ip xxx.xxx.xxx.xxx port xxxx".

At this moment the device is pingable on its internal network card (not the jetdirect!)

But if i try to copy the fw to this ip (with cms-command: copy <fw-name>.bdl xxx.xxx.xxx.xxx) it says "access denied - 0 files transferred"

It seems to be possible to install the firmware through this method, but nobody can tell me how......

Do you might know how to use it?

Thank you very much!

[revolutionx · Accepted solution]

You have to transfer the file to port 8816 as a binary without any preceeding info, so FTP/TFTP and others won't work, essentially you need to dump the file directly to the IP of your scanner. So, you can use netcat (included on unix/mac, for windows you'd have to download this tool) to push the file, as follows:

nc 1.2.3.4 PORT < /DIR/TO/FW/SJ7000n_FW_62463_12379.bdl 

replace 1.2.3.4 with the IP, "PORT" with the port listed on your scanner's screen (8816 usually), and then place the path to your file after the "<"

[SHThompson]

Question for revolutionx, have you actually done that procedure?

I had checked and even on an HP internal support web site and not been able to find any documented process for reloading firmware on the Scanjet 7000 that had lost it.

And the answer to the hard drive question is that when you order the HDD part number for your machine you get a hard drive preloaded with the firmware for your machine you plug it in and it should work.

As I recall the part number starts with the product number of the machine, there are two different hard drives with similar part numbers. But the first digits of the correct part number will match the model number of the machine.

[El_Jeezy]

This is the closest I've seen so far to a working solution, but with my windows implementation of ncat, it does not support redirection (says it's for a future implementation). Now, I am using the standalone/static version of ncat for Windows (from NMAP.ORG), so perhaps that's why the redirect is not yet supported. I will try the full version, shortly, and report back if that works.

[El_Jeezy]

OK, installed NMAP from their official site, and ran the installed version of ncat. The redirect (<) was still inop, so I tried a cat to the command... Here's my output (heads up, it still failed). I'm going to try a Linux implementation, ext, to see if that'll work for me. On the ScanJet 7000nx, I now see the message: Download error: Unsupported Bundle!  which seems to mean that I have the wrong bundle that I downloaded from HP... Gonna go bak and look into this, as well.

PS C:\Users\El Jeezy\desktop> cat sj7000nIfw_2204081_233277.bdl | ncat -v -v -v 192.168.1.14 8816
Ncat: Version 6.49BETA6 ( http://nmap.org/ncat )
NCAT DEBUG: Using trusted CA certificates from C:\Program Files (x86)\Nmap\ca-bundle.crt.
libnsock nsock_iod_new2(): nsock_iod_new (IOD #1)
libnsock nsock_connect_tcp(): TCP connection requested to 192.168.1.14:8816 (IOD #1) EID 8
libnsock nsock_trace_handler_callback(): Callback: CONNECT SUCCESS for EID 8 [192.168.1.14:8816]
Ncat: Connected to 192.168.1.14:8816.
libnsock nsock_iod_new2(): nsock_iod_new (IOD #2)
libnsock nsock_read(): Read request from IOD #1 [192.168.1.14:8816] (timeout: -1ms) EID 18
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 26
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 26 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 35 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 35 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 42
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 42 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 51 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 51 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 58
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 58 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 67 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 67 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 74
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 74 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 83 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 83 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 90
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 90 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 99 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 99 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 106
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 106 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 115 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 115 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 122
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 122 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 131 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 131 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 138
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 138 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 147 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 147 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 154
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 154 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 163 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 163 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 170
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 170 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 179 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 179 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 186
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 186 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 195 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 195 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 202
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 202 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 211 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 211 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 218
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 218 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 227 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 227 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 234
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 234 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 243 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 243 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 250
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 250 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 259 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 259 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 266
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 266 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 275 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 275 [192.168.1.14:8816]
libnsock nsock_readbytes(): Read request for 0 bytes from IOD #2 [peer unspecified] EID 282
libnsock nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 282 [peer unspecified] (4608 bytes)
libnsock nsock_write(): Write request for 4608 bytes to IOD #1 EID 291 [192.168.1.14:8816]
libnsock nsock_trace_handler_callback(): Callback: READ ERROR [An existing connection was forcibly closed by the remote host.  (10054)] for EID 18 [192.168.1.14:8816]
Ncat: An existing connection was forcibly closed by the remote host. .

[El_Jeezy]

Alrighty then... used my MacBook to push the BDL file to my ScanJet. It looked like it was working great. Saw the "receiving files" feedback on teh ScanJet and received no errors. When the upload was finished, the ScanJet went back to its mainscreen and then I went ahead and reset it. It will still not load. Here's the last output from the ScanJet as it was finishing the BDL file load:

FimRxStream: StartNextFile, pk offset CF26C9, file #1

Closing file

Copying dispatcher executable

Setting bundle sequence to 4

Closing repository

After that, it returns to the main screen, I see it try to boot (HP Logo 1/7) then displays the following:

HP Q965 System

Intel (R) Celeron (R) CPU    440   @ 2.00 GHz

Scone_0005.HP090209_1753.UEFI2.0 X64

Disk is not bootable, please download firmware.

So, what I am thinking now is that I need to look for a 64-bit  version of the firmware, as, perhaps, I may have a 32-bit, even though 32-bit should be compatible with a 64-bit??? Anyway, will look into that avenue, next...

[revolutionx]

Are you pushing the full firmware file to the unit? There are some .bdl files that are simply incremental patches, which would not provide you with the full OS.

The full firmware file you need is SJ7000n_FW_62463_12379.bdl, which is 1.6 Gigabytes. You can download the file from HP here: SJ7000n_FW_62463_12379.bdl

PS, cat should work fine too, I didn't mention it since I had some errors with cat on the mac I used, while nc operated smoothly. Probably user error.

@SHThompson

We've reloaded three units with this file. Both the 7000N and 7000NX (with encryption) operate normally on this software. HP's service documentation today is sort of a hollowed out shell of what a service manual should be. Where did you even find the service docs for this unit? I keep coming accross broken links and need the manual for the service PIN, would you be able to link me to it?