wingspinner/hootoo-tripmate-ht-tm02-openwrt

Patches, files and instructions to upgrade the HT-TM02 to OpenWRT

hootoo-tripmate-ht-tm02-openwrt's Issues

works with HooToo® TripMate Nano HT-TM01?

Can't access failsafe mode

Hello,

I've followed the steps and flashed with openwrt-ramips-rt305x-ht-tm02-squashfs-factory-r44945-basic.bin. The system was working and while I was setting it up with relayd made a typo in my /etc/config/wireless. To correct this I am trying to load the device into failsafe more.

I hold the reset button when the lights are flashing and get the familiar fast flash but I am unable to connect to (or ping) 192.168.1.1. I have my computer setup with:

IP: 192.168.1.2
Subnet mask: 255.255.255.0
Gateway: 192.168.1.1

I have 3 or 4 of the HooToo Tripmate Nanos and have confirmed when setting them into failsafe I cannot access 192.168.1.1 Is there another address that has been set? Am I missing a step?

All.bin

Hi

I'm trying to debrick ( spi programmer ) a tm02 but I don't have any flash backup to write, and the official firmware in hootoo download page doesn't fit ( chip is 8192kib [8388608 bytes], while image is 8925617 bytes )

do you have any backup or full image to restore?

Android usb tethering to HooToo TM02 openwrt

Hello! I've successfully installed openwrt on the tripmate nano but can't seem to get it to talk to my android phone when i set it to usb tether. I've tried creating different interfaces and following a few guides like these...
https://wiki.openwrt.org/doc/howto/usb.tethering
http://lgallardo.com/en/2011/05/26/usando-el-anclaje-de-red-tethering-de-android-en-openwrt/
...with no success. I was able to connect the hootoo to a wifi as a client in case it needed to download a package. Any advise?

Build envorinment

May I ask what your build environment is? I want to use a mt7601u wifi stick with my TM02, but the trunk build bricked my device and I had to send it in for a replacement. I think the next best thing to do is to build an image myself with the newer kernel version that supports it, but I have no idea how to do it, and I won't be able to get another replacement if I brick this one.

Default root password of my Tripmate TM02 was 20080826

You may want to update README to indicate that the root password of Tripmate TM02 is "20080826". Also, the telnetd on mine was running already out of the box. I found the hardware was really similar to RAVPower Filehub, and I found the root password of that one a while back via internet search. I think these are all the same wifi soc, with very similar firmware.

Possible to flash someone elses HT_FLASH?

I didn't know that the HT_FLASH folder contained the whole backup of the HooToo device and it seems that over the years at some point I've overwritten said stick already... Is there any way to use someone elses HT_FLASH backup on my own device? Is the MAC hardcoded into the backup? If not, if someone reads this issue who still has a backup, could you send it my way?

Thanks in advance!

a

a

Firmware Upgrade image is in Wrong Format

When I tried using the image "openwrt-ramips-rt305x-ht-tm02-squashfs-factory-r44945-ws.bin" to upgrade the firmware through the stock image's System's Firmware upgrade menu, it said that the image was in the wrong format. I had to use "openwrt-ramips-rt305x-ht-tm02-squashfs-factory-r42649.bin". Only that one was accepted.

opkg binaries fail to run

Hi,

With the "Factory Image (WS)" in the repo, it looks like the Chaos Calmer binaries that opkg pulls down no longer work. Ash keeps saying "not found" for basically every binary I try to run (not all). I think they might use a different libc like musl or something like that (I'm a complete newb to OpenWRT, but doing some research that seems to be the core reason)

Upgrading to the latest stable (15.05, r46767) solves all these issues. Is there a plan to update the "Factory Images" in this repo to use this build?

Here is the sysupgrade image, as found on the OpenWRT site. It works great, but I had to manually upgrade.

If you don't want to create the image, I can send you a pull request. I just have to learn how to use your tool that creates the images. (However I have no way to test it because I don't know how to flash back to stock)

kmod-fs-ext4 fails to install

It appears that the kernel's check sum doesn't match with what's in the opkg repo for kmod-fs-ext4 now.

root@OpenWrt:~# opkg install kmod-fs-ext4
Installing kmod-fs-ext4 (3.14.18-1) to root...
Downloading http://downloads.openwrt.org/snapshots/trunk/ramips/packages/base/kmod-fs-ext4_3.14.18-1_ramips_24kec.ipk.
Collected errors:
 * satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-ext4:
 *  kernel (= 3.14.18-1-0949d9896fafd7612d570d0e07786ac5) *     kernel (= 3.14.18-1-0949d9896fafd7612d570d0e07786ac5) *     kernel (= 3.14.18-1-0949d9896fafd7612d570d0e07786ac5) * 
 * opkg_install_cmd: Cannot install package kmod-fs-ext4.
 root@OpenWrt:~# 

Hardware reset

Is there a way to reset the HooToo device if I can't reach it due a bad configuration?
Is the reset button still working with OpenWrt?

Building an openwrt factory image

Hi Ron,

Thanks for sharing your findings; its clear you put a lot of time and effort it in - and its saved a lot of other engineers and hackers a lot of time.
I'm trying to build a factory image for another device; with identical hardware to the HooToo. Its the RAVPower RP-WD01. It does not have an Ethernet port, so I need to flash it and have Wireless work straight away.

I can do this if I can build a 'factory' image with a sysupgrade image with wireless ready to go. I have a HooToo TM02 to practice on. I have pulled revision r42649 and applied your patch; I have baked in a wireless config.
You mentioned in your posts on openwrt forums:

"Factory firmware update mechanism is not compatible with standard OpenWRT images. I’ve decoded the factory image format..."

"This is the "factory" upgrade image to be used by the factory HooToo software to do the initial upgrade to OpenWRT.It is based on the same binary image as the normal OpenWRT sysupgrade image but has been re-packaged with a loader, CRC, etc. such that the factory HooToo software will accept it. The factory HooToo software is filename sensitive and will reject the file if it's too different from what it expects. If the TM02 rejects this name try changing it to "fw-WiFiPort-HooToo-TM02-2.000.018"

Can you offer any direction on how to develop the loader and the CRC required, also the filename check?

Thanks
Ian

Support for HT-TM03

Hello,

I have got a HT-TM03 (the one with the 3Ah battery).
It works fine with your software, thank you.

The only change I had to do was the path.

Your software has the hardcoded path to /data/UsbDisk1/Volume1 in the upload script, which isn't too handy on this unit, because it features an MicroSD card reader.
The microSD card reader always gets called /data/UsbDisk1/Volume1
the USB drive was /data/UsbDisk2/Volume1

For me to get the upload working I just symlinked the directories over a serial line, but thats of couse not the best solution.

I would think it would be a good idea to parse/grep through the mount-output and look for devices in the /data/ directory.

Anyway, apart from that, it seems to work nicely. Thanks,
Tobias

Build image including USB serial patches

Can you please provide an upgrade image (for openwrt) that incudes the patches you provided? I don't have a way to make a build from scratch and would REALLY love to get the feature that lets me use the USB as a serial device to capture serial logs from another device. Your help would be greatly appreciated. Thank you for putting this page together as it has helped me tremendously so far.

Can you go into further details?

I made it to step #7, all appears to be working fine.
#7. LUCI should be up and running so browse to 192.168.1.1 and configure as needed. This install is intended as only an initial install to get openwrt on your device so the first thing you should do is upgrade using the latest trunk "upgrade" binary from openwrt.org.

I went to openwrt to look for the this latest trunk "upgrade" but it's a maze. Any suggestions on exactly what steps to take to get to the right upgrade?

Fstab support?

Hello good sir. First off thank you for all of your work on this and getting openwrt supported on our Tripmates. I'm trying to get exroot setup however I'm getting "block

How to get back to Stock?

Sorry if this is maybe a little offtopic but so far you're the most competent I found working on such a project.

Anyways, I want to go back to stock on my HT-TM01, since the TM02 is basically the same hardware as the 01 it should have similar instructions :)

Do you know how I could do that? When I go to their firmware download page all I get is a ".046" file which I guess is basically a image renamed.

Thanks a ton already and sorry if it's a bit offtopic to this project!

kernel v.s. opkg kmods out of sync

It is apparently the same issue. Because your kernel is different (in the hash string), no new kmods will load, and it means although I have space, I can't install openvpn-openssl since it depends on a kmod that can't be downloaded.

Is there a sysupgrade in the main BB tree that will work?

How to recover bricked board?

I have managed to brick the board and I'm now trying to burn a new image to it through recovery console. You have mentioned that you have used the console to burn a new image. How did you do it? This was after I have burned your basic image (which worked fine until I wanted to run sysupgrade again and messed it up).

From what I can tell, the console I have is far inferior to modern uboot. I have not even managed to get tftp working. It just tells me that arp has timed out etc. Commands like cp.b are also missing. I have cp.linux but it doesn't work (giving a garbage size when i do it after uploading image). What address should I upload it to?

Do you know where I can get a working version of uboot and do you know how to flash it? What address do I load it into? How do I permanently flash it to spi flash?

RT5350 # version

U-Boot 1.1.3 (Sep 1 2012 - 08:34:08)

RT5350 # loadb 3000
.. load uboot256.bin image with kermit

RT5350 # bootm 3000
Booting image at 00003000 ...
Image Name: SPI Flash Image
Created: 2014-01-09 9:10:07 UTC
Image Type: MIPS Linux Standalone Program (uncompressed)
Data Size: 105456 Bytes = 103 kB
Load Address: 80200000
Entry Point: 80200000
Verifying Checksum ... OK
OK
(hang)

This is as far as I have gotten so far. Any help would be appreciated. :)

Can I use any of your images and load it like this?

Simple question about wifi radios

Apologies if this is the wrong place to raise this, but I have a basic question about using OpenWRT on the TM02 that I've been searching for a couple of hours about and can't find the answer.

I used to use the stock firmware to connect to a hotel wifi and share it on another wifi network to all of my devices. I can't find a way to do this with the OpenWRT firmware without 2 wifi radios - am I missing something really obvious here?