HooToo HT-TM01 - How to flash Stock Firmware?

xabolcs · 2020-10-06T00:01:20.010Z

Try with /b:

copy /b mtd4.bin+mtd5.bin+mtd6.bin+mtd7.bin+mtd8.bin Kernal.bin

But yeah, maybe there is a size check.

Try that kmod-mtd-write and write that 192 kB sized mtd1.bin from my backup to your u-boot partition!

mtd write /tmp/mtd1.bin u-boot

EpicLPer · 2020-10-06T00:21:32.586Z

Okay! Seems like kmod-mtd-rw, then unlock and then a write ot mtd1 to u-boot worked and I was able to boot with a new bootloader now! Looking in Wireshark now it does ask for "Who has 10.10.10.254?" so it looks promising

Now... Do I have to just flash kernel since mtd8 is already included there or do I still have to rename mtd8 to rootfs and flash that too?

xabolcs · 2020-10-06T00:26:42.815Z

Original u-boot searches for kernel and rootfs.

This could then be used as an backup to create an images to get back to the OEM firmware:
copy /b mtd4.bin+mtd5.bin+mtd6.bin+mtd7.bin kernel
copy mtd8.bin rootfs

Source: https://openwrt.org/toh/ravpower/ravpower_rp-wd03#execute_script_with_oem_firmware

EpicLPer · 2020-10-06T00:31:04.023Z

I think this is looking promising!!!

EpicLPer · 2020-10-06T00:36:01.235Z

YUP! Damn! I never thought I'd see this device work again, awesome!

Thanks so much for your help man! After many, MANY years of not being able to use that thing anymore it finally comes back to life as it's supposed to be I'll definitely put the stuff we talked about here in my blog for other people to easily find and being able to follow it too in case theirs is/was also as screwed up as mine!

xabolcs · 2020-10-06T01:18:25.699Z

EpicLPer:

I think this is looking promising!!!

TripMate-0E58 ... very interesting.
This is my device's MAC.
Please try factory reset on your device! Hold reset for a long time (30s? 1min?) while the TripMate is powered on.

EpicLPer:

I'll definitely put the stuff ...

It was easy, wasn't it?

get OEM u-boot binary
flash it with the help of kmod-mtd-rw and write
set up a TFTP recovery environment
get kernel and rootfs
- from someone else's backup
- extract from stock firmware upgrade file (with nice tools)

But don't forget to note how important that backup directory is!

And create a new for yourself with EnterRouterMode.sh (saved at pendrive's root directory) below:

EnterRouterMode.sh


#!/bin/sh
SDCARD=/data/UsbDisk1/Volume1/
USB=/data/UsbDisk2/Volume1/

FWCFPT="/proc/vstinfo"
FWFIRMWARE="/etc/firmware"
FWINFO=
if [ -r $FWFIRMWARE ]; then
	FWINFO=$FWFIRMWARE
elif [ -r $FWCFPT ]; then
	FWINFO=$FWCFPT
fi

readfwinfo() {
	grep $1 $FWINFO | cut -d= -f2
}

WORKDIR=`find /data -name EnterRouterMode.sh`/..
cd ${WORKDIR}

CURFILE=`readfwinfo CURFILE`
CURVER=`readfwinfo CURVER`
VENDOR=`readfwinfo VENDOR`
PRODUCTLINE=`readfwinfo PRODUCTLINE`
MTD_SN=`get_mtd_sn`

FWBACKUPPREFIX=fw-${PRODUCTLINE}-${VENDOR}-${CURFILE}-${CURVER}-${MTD_SN}
mkdir -p backup-${FWBACKUPPREFIX}
cd backup-${FWBACKUPPREFIX}

if ! (md5sum -s -c mtd.md5sum); then
	for mtd in `grep  ^mtd /proc/mtd | cut -d: -f1`; do
		dd if=/dev/$mtd of=$mtd.bin
	done
	sync
	cp $FWINFO fwinfo.txt
	echo $FWINFO > fwinfo-filename.txt
	cp /proc/mtd mtd.txt
	md5sum mtd*.bin *.txt > mtd.md5sum
	dmesg > dmesg.txt
	ip a > ip_a.txt
	env > env.txt
	get_mtd_sn > mtd_sn.txt
	cat > readme.txt <<EOM
This directory contains a backup from your $VENDOR device.


Put it to a safe place!

EOM
fi
cd ..


# nvram_get > $SDCARD/nvram_get.txt
# nvram_get rt2860_nvram_show >> $SDCARD/nvram_get.txt
# nvram_get show >> $SDCARD/nvram_get.txt
# nvram_get chkcrc >> $SDCARD/nvram_get.txt
# nvram_get gen > $SDCARD/nvram_get_gen.txt

/etc/init.d/teld.sh restart

xabolcs · 2020-10-07T13:46:50.383Z

Ravpower RP-wd02 impossible to flash back oem firmware

I wonder if a factory reset would help restore those, have to take a look later still

(@EpicLPer, you responded in the wrong thread! )

Thanks for testing!

EpicLPer · 2020-10-07T15:20:24.338Z

I know heh But yeah I'll try that later on.

hashcraft95 · 2020-10-08T09:14:16.212Z

@xabolcs , Thanks for providing all of the files and information. I have the exact problem you guys were talking about. If the offer still stands, could you make that custom sysupgrade.bin? It's a bit over my head.

xabolcs · 2020-10-08T10:36:56.458Z

Hello @hashcraft95!

Using an official 19.07.x release is easier than a random custom build from a random community member.

Just

sysupgrade to latest 19.07 (e.g. openwrt-19.07.4-ramips-rt305x-ht-tm02-squashfs-sysupgrade.bin),
install kmod-mtd-rw
insmod it: insmod mtd-rw i_want_a_brick=1

And you are there: with writable partitions.

Instead that custom sysupgrade I could provide a script later, which would flash the original Bootloader back to the device.

hashcraft95 · 2020-10-08T16:12:00.175Z

Insmod was my missing link, I got it up and running stock. Thanks so much!

tmomas · 2020-10-09T08:35:09.684Z

If your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.

EpicLPer · 2020-10-09T08:46:21.222Z

Problem is that this would close the topic in a few days which I don’t want in case people have problems and wanna ask things

xabolcs · 2020-10-09T15:21:30.212Z

I prefer marking this as solved too ... but before that, it would be nice to:

create a minimal HooToo HT-TM01 device page on Wiki - independently from that HT-TM02
- document the steps of this "Revert to Stock, but from wingspinner's build"
- link this topic for the details
create a new backup archive:
- readme.txt - with the steps
- Bootloader.bin, Kernel_RootFS.bin, params.bin, Rootfs.bin
- answer your wingspinner issue #21: where/how to edit that params.bin
put the new backup archive to archive.org (like TL-WR1043ND v4 EEPROM dump)

EpicLPer · 2020-10-09T15:34:09.482Z

Yep that’s why I’m holding off for now Until everything’s set up so others can easily follow along in case theirs is screwed up too.
I guess there’s no way to supply a sysupgrade image for people already on a working OpenWrt to easily revert? And then additional steps for people who screwed their install up beyond repair

tmomas · 2020-10-10T08:54:14.277Z

xabolcs:

create a minimal HooToo HT-TM01 device page on Wiki - independently from that HT-TM02

OpenWrt Wiki – 10 Oct 20

HooToo HT-TM01 (TripMate)

HooToo HT-TM01 (TripMate) This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram. DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version onto it! See 4/32 warning for...

Feel free to add usefull information about this device.

vaibhav157 · 2021-02-05T12:26:41.224Z

I tried upgrading the firmware of my HooToo Tripmate Nano (HT-TM02) but failed, now the device's blue LED keep on blinking and I am not able to see the WIFI network, device became unusable, I have tried to reset by inserting the pin but it seems not to be working.

Can anybody help me to get my HT-TM-02 back to life

xabolcs · 2021-03-08T20:19:38.458Z

HT-TM02 had to switch to source-only, exactly of the same error.

Your last hope is the 19.07 release.

ubr · 2021-06-20T19:33:37.021Z

Thanks for creating the new openWRT page for the HooToo TM01. I'm happy to add instructions there, but please confirm what is the recommended installation procedure for a factory-new TM01:

install the OpenWrt 19.07 "Install" firmware linked there straight from the stock menu?
install wingspinner's TM02 image (using an empty USB stick), and then sysupgrade to 19.07?
or simply install the official release recommended on the generic openWRT page for TM01–04?

xabolcs · 2021-06-21T07:01:35.867Z

Hi @ubr !

Well, it's a little bit complicated. Let me explain.

Sadly the current support isn't as good as it could (should? ) be:

it overwrites device specific parts of the device: the params partition
it changes the way of the TFTP recovery
- it listens on another address
- it uses different filename
- it uses one file instead of separate kernel and rootfs files
it creates a full backup to the usb drive where from the user installed, but
the user doesn't know about it, and wouldn't put it to a safe place

Because of the above I won't recommend the current way of installation.

I did my experiments (thanks @jwmullally for the initial work) about creating a safer device support which uses only the 1536 k Kernel_RootFS for kernel, and the 6144 k Rootfs partition for rootfs.
It's safe to use, and compatible with the official releases (currently 19.07.7).
(It's not finished yet, in terms of documentation )

But it's still a community build from a random guy from the Forum. So I couldn't recommend this too!