Just wanted to share my experiences playing with the Next1's firmware...
eBook readers based on the Rockchip RK2729 have 3 hidden partitions.- A backup firmware (only updated using the Firmware Upgrade tool (RK28DM) available here)
- The firmware actually loaded (150MB partition)
- User settings. (80MB partition)
We can see (and then backup) 2. and 3. above using the following method:
- Attach the reader to the computer using the mini-usb cable.
- Create an empty file with the following name: rkusb.tag
- Copy it into the root of internal memory (NEXTBOOK Partition). There may be another unnamed partition for the microSD card, if installed. Make note of the Drive Letters assigned.
- Turn off the reader
- Shutdown and restart the computer
- Turn on the reader and wait until the USB connection picture is displayed
- Wait a reasonable time to recognize the reader (the previously visible partitions above may have the Drive Letters re-assigned now)
- After the computer finds the two new partitions, copy the contents of each of them into a zipped file or "as is" onto your hard drive
- Delete the empty file created (rkusb.tag) in internal memory
- Power cycle the reader and the hidden partitions will “disappear” as before.
Notes:
- Do not try to copy the individual files into the hidden partitions to update the firmware.
- The OS loader of the reader checks the CRC of the files from partition 1. to 2. and if they do not match, they are replaced.
- To update you have to create an image (FAT) .img file using UltraISO or WinImage, and replicate the file structure of the larger (150MB) hidden partition’s contents.
- Then use the software Rockchip DK28DM_Setup to install the firmware upgrade tool and update with your .img file.
For other devices, other possible empty filenames, instead of rkusb.tag, to try are:
- teclast.sys, FRK.TAG, HTC_001.Tag
If you aren't comfortable messying around with your device's firmware, then
don't! Proceed with extreme caution as there may be a slight chance you can "brick" your device if the above is preformed incorrectly.
These instructions work for me, but I won't be held responsible for any damage done to your device by following them (or not!).