Unbrick a Teclast X98 Air II Bios

Teclast X98 Air II Intel Bay use Trail-T Z3736F Quad Core at 2.16 GHz it got 9.7 Inch IPS screen with a resolution of 2048*1536, 2GB of ram and 32GB of internal storage. With no surprise it catch the attention of many with a price around 200 euros.

You can find the tablet in different versions, the main difference it’s about been the tablet dual boot or not but you can find also other variants which seems to have minor hardware differences and different bios.

In this scenario you can understand how easy can be to brick your device just flashing the wrong bios version,  turning this nice toy in a piece of junk. But before you buy a new one you should try to recover your device with this easy guide.

This procedure can be also used to unbrick many other devices such as IPcam and routers, most of them uses in fact the same eeprom series, 25XX or 24XX series to be precised.

 

It’s easy to understand which eeprom we got, in this case, for instance we got a a 25xx series:

 

This is important to connect the programmer correctly.

 

What we need:

1) A Teclast X98 Air II or similar, of course

2) The Bios for you tablet version

3) A CH341A 24/25 series EEPROM Flash USB Programmer

4) A SOIC8 IC Test Clips Socket Adpter

You can find a kit at this address:

http://www.amazon.co.uk/gp/product/B00UG9O8D0

 

I would strongly recommend to buy this kit as has already been tested but any programmer should be just fine.

Please we aware that this procedure has been tested in Windows 7 only, it’s essential that you use the right software / driver combination, most of time when you use the wrong driver the software seems to be unreliable.

 

1) Install the software that you can download from here:

https://mega.co.nz/#!zIljnQrC!RLJ_qYzLhYZ-uVkvCe8OwkWyb0-eNNnzRlzXlJl_fTs

password is supercowz

 

you can also try a Linux version available here:

http://sourceforge.net/projects/ch341eepromtool/

 

2) Download the Bios from here:

http://techtablets.com/teclast-x98-air-3g/downloads/

 

3) Connect the clip on the chip:

Be careful about the clip orientation, it must follow the dot on the chip!

4) Connect the USB cable

5) If the cable has been connected in the right way you should see Device State: Connected on the bottom right side

6) Load the Bios on the software

7) press Erase

8) press program

When you power on the bios the first time, depending if you are flashing a different platform bios (for instance you  had an android tablet and you are flashing a bios for windows) it’s possible your tablet will boot up to UEFI, if does you tablet it’s fine, you just need to install the OS.

Kernel 3.13.3 for Ubuntu 12.10 32 Bit

I’m planning to move to Ubuntu 14.04 very soon, also because my server is still running on a 32 bit distro, I know I’ve been very lazy in the past few months, but in a place like that:

10151327_10203949344721790_1564162719193606614_n

is not easy to think about the Linux kernel 🙂

I had upgraded the Kernel because I had some issue with a dvb card and lirc (I use my server for everything except the coffee)

wget http://everythingisafile.com/Downloads/Kernel_U12.10_32-3.13.3/linux-headers-3.13.3-custom_3.13.3-custom-10.00.Custom_i386.deb

wget http://everythingisafile.com/Downloads/Kernel_U12.10_32-3.13.3/linux-image-3.13.3-custom_3.13.3-custom-10.00.Custom_i386.deb

to install:

dpkg -i *

enjoy -)

 

 

Check the ssh connection attemps

Checking the ssh connection attemps it’s a good start if you suspect an autorized access to your server, also if you are using a pubblic facing address with a standard port it’s a good pratctice to check the logs time by time.

The settings related to the ssh logs file are on:

/etc/ssh/sshd_config

OpenSSH logs using the AUTH facility of syslog and by default it’s set on a basic level called INFO. It’s possible of curse to increase the logging level to VERBOSE changing thefollowing line:

LogLevel INFO

to this:

LogLevel VERBOSE

 

All the connection attempts details of ssh login will be saved in your /var/log/auth.log file.

that can be easyly chacked with a:

grep sshd /var/log/secure | less

An example of a failed attemp to login from an autorized user is:

Jan 27 16:48:17 media-center sshd[9668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.wannalogintoyourserver.com user=root
Jan 27 16:48:19 media-center sshd[9668]: Failed password for root from 211.33.44.22 port 54052 ssh2
Jan 27 16:48:58 media-center sshd[9678]: Set /proc/self/oom_score_adj to 0
Jan 27 16:48:58 media-center sshd[9678]: Connection from 192.168.1.79 port 45643
Jan 27 16:48:58 media-center sshd[9678]: Connection closed by 192.168.1.79 [preauth]

Ipmitool in debian or derivated

To install:

sudo apt-get install ipmitool openipmi

incase of device issue (like in old versions of debian)

modprobe ipmi_msghandler
modprobe ipmi_devintf
modprobe ipmi_si

To see the current settings:

ipmitool lan print 1

Swich btw dhcp to static

ipmitool lan set 1 ipsrc static

Set the IP configuration:

ipmitool lan set 1 ipaddr 10.22.130.222
ipmitool lan set 1 netmask 255.255.255.0
ipmitool lan set 1 defgw ipaddr 10.22.130.1

User management

See the current user list:

ipmitool -I open user list 1

ipmitool -I open user test 2 20 password

(user 2 is root with password)

RMM4 Roles

Test the Customer Account:

ipmitool -I open user test 4 20 usrname

Example to how Set the user name:
ipmitool -I open user set name 5 administrator
where 5 is the user id number that you can pick up from the list command

Set the password:
ipmitool -I open user set password 5 password

Set the user role:

ipmitool channel setaccess 1 5 ipmi=on link=on privilege=4

Enable the user:
ipmitool -I open user enable 5

To test if the user work:
ipmitool -I open user test 5 20 password

To reset the BMC

ipmitool mc reset cold

ipmitool -I open user set password 2 ADMIN