Tool: H2testw - To test hacked flash memory

[Binh@MyMPx]

Hi everyone,

I was reading a website and found it mentioned a tool called "H2TESTW" to test flash memory whether it has been hacked.

So, I've uploaded it to this site and can be downloaded here: H2testw - To test hacked flash memory

I would like to ask if anyone who has a hacked player to test this tool and see if find anything. It's a self executable program which doesn't require installation. Obviously it would work much better for those players that hasn't had the memory hack removed.

Would love to hear your feedback.

[lolita]

I'm somewhat against the use of this program on MP4 players since there's the risk of overwriting the firmware if the flash is really smaller than it specifies. There's also the fact that flash these days, unless you're lucky and get a 100K cycles SLC, has very low endurance (down to 1,500 cycles for some very new parts). It's OK for USB drives and the like, which don't store firmware on the same flash as the main storage. The better way is to open the device and read the part number directly.

[Binh@MyMPx]

Thanks lolita for your comments.

From the description of the program, it says this:

"H2testw does not overwrite or erase any existing data. It doesn't do any low-level tricks so administrator privileges are not required. If your hardware is working properly H2testw will not harm any existing data."

From that, I think it wouldn't overwrite the firmware. But then again, I'm not sure if anyone has tried this on their MP4 player yet. I would be interested to know if you do.

I'll see if I can buy myself a dodgy hacked player and try that and see what happens....... We don't have eBay here in New Zealand, so it may be slightly more difficult.

[lolita]

I'm getting conflicting information. Here, it says that h2testw writes to the drive to determine its true capacity. I can't see any other way to do so either, with only the ability to read/write sectors to the device and not e.g. use some extended commands that could get the flash hardcoded ID.

[Radio_Daze]

I tried this programme yesterday on my mp4 player. It confirmed to me that my 16GB player is in reality only 1.8GB. It did not overwrite the firmware.

[Loathly]

I have tested my 32GB Mp4 and it's 3.5GB only. How can I fix the Memory Hack, to make it 3.5GB only, and not 32GB as a fake? The other tool in the other sticky doesn't work.

[nane]

here is another way to check nand flash size ..
product code decoder: open your 2.8" touchscreen player and search nand flash product code.
the source decoder product code data are from samsung, hynix and micron directly.

NAND FLASH SIZE CHECK by nane

[Funt]

After using H2Testw my player is dead
After writing with H2Testw of apr. 2Gb player was disconnected and after that Win doesn't recognizes it.
Moreover I cant power on it

Board: QS27C21 Touch Key v0.1

[Grimsqueeker]

H2testw will only write to free memory.
It will not over-wright firmware or existing information stored in the memory.

If you disconnect the program whilst it is running, you run the risk of corrupting the information being written. This may cause problems, it's like switching the power off your computer when it is writing to the hard disk (not recommended).

If your player stops working after H2testw has finished, then I am afraid that your player would have stopped working if you had filled it's memory with data (music/video). That would have been caused by the way the firmware has been hacked , not by H2testw.

The fact that H2testw will only write to free memory will cause an incorrect "OK" value if files are stored on the device when testing is performed.

Before testing, copy all files from your player into a temporary folder on your PC, so that you can put them back when finished.
Delete the files on your player and then run H2testw.
It will take a long time to run the test if your player is claiming 32Gb, wait until the program indicates that it has finished.
Make a note of how much memory is indicated as "OK".

I have a "RIZONE" player.
I used H2testw to test it, deleted the primary partition, created a primary partition using the H2testw information and then formated the partition.
My player still works, I fill it with audio books several times a week and never have problems.

I would recommend that people used usb cables from other devices or invest in buying a good cable because the cables supplied with these cheep players are pretty crap.

As far as the uncertainty of over-writing firmware is concerned, the "RIZONE" either has separate memory for it, or the only way to gain access to it is by using flash software.
H2testw will not over-wright firmware.

[Funt]

I didn't disconnect the player by myself. I think it was disconnected by itself after H2testw start writing to memory which are not exist. Because real memory of my player 2GB, but system recognizes 8Gb.
Before I used H2testw with 2 another hacked players. One player was fully tested with H2testw and another also disconnected itself after H2testw start writing over 1.8Gb...but after this player works good...