Device Name is empty on both pictures. 

Could you read it manually by this command 

Register 0x21 ReadBlock 

Send it 10x times to check consistency. 

Reflash the battery with original dump and check if Device Name appeared. 

unable to go further

DELL TP1GT61J

here is the pack name at the beguinning.

It looks like firmware is corrupted. 

Was communication Ok at the beginning ?.. 

the communication was ok .I unsealed, read, edited, wrote.

As the edited rom did not solved the issue, I decide to write back the original, that is where I got stuck, no way to see the chip again.

Will check your dump, may be it was not edited correctly. 

thanks in advance!

any updates about this issues ?

Dump was not edited correctly which caused the chip to not communicate properly. 

bq304xx FCC edit tutorial should not be applied to bq403xx chips due to different byte order organization. 

bq304xx uses Big Endian while bq40370 uses Little Endian byte order. 

https://en.m.wikipedia.org/wiki/Endianness

So FCC = 612mAh is 0x0264 in Hex value should be searched in the dump after byte swapping to 0x6402. 

This value located at 0x034A offset. 

Instead, service bytes at 0x0A34 were changed what bricks the controller. 

whoooa!!!!

I learned it the hard way!