[Q] Just got my replacement.... out of the loop... guide me.

[GADGTGUY]

Hi,

I have finally received my replacement watch. (yay)

I was so discouraged after waiting 3 months to get it that I sort of fell out of the loop on what's been going on in the community.

The watch I got has the following:

(when I got to OTA) - truesmart-20140801-1006

Under About:
Android 4.2.2
Kernel - 3.4.5
OUI 2.1
Build - Omate_Truesmart_20140801.10312_v2.0



So,

Do I need to update anything?

How do I ROOT this version as what I did with my previous watch doesn't seem to work anymore.

Any suggestions for next steps or apps/things to load?

I tried going through all the old threads but there seems (to me at least) a lot of info that is no longer relavant or doesn't pertain to what I have now... I am just trying to make sure I am on the right path as I don't want to screw this watch up like the last one.


Much appreciated.

D.

 

[walscobry]

what I would do

**** DO THE LAST PART OF THIS POST FIRST ***

Build - Omate_Truesmart_20140801.10312_v2.0

### First time I have seen this date on a firmware

Do I need to update anything?

### Look like you have newest firmware already

How do I ROOT this version as what I did with my previous watch doesn't seem to work anymore.

### Not sure since you have newer firmware but if it is like older versions you are sorta rooted now. If this true then all you need to do is push SU and BusyBox via ADB and set permissions. Then install SuperSU or one of the other GUI level root managers.

Any suggestions for next steps or apps/things to load?

### My touchscreen is bad and my watch is unusable but in the couple weeks I got to play with it I found that NOVA launcher + Swipe Status bar to a better desktop than the stock launcher. Google MyTracks worked great for logging walks / trips and even logged while the screen was off.

I tried going through all the old threads but there seems (to me at least) a lot of info that is no longer relavant or doesn't pertain to what I have now... I am just trying to make sure I am on the right path as I don't want to screw this watch up like the last one.

### Given your newer firmware you might just be blazing a new trail. I would find/Download the ALLTOOLS kit that Lokifish put together if you can find it. Then use MtkDroidTools to make a backup of your firmware (then share that with the rest of us, please) and your device IDs just in case. In fact I would do this first before anything else.

DO THIS LAST BIT FIRST ^^^^ !!!!

Also I don't think TWRP recovery is working for firmware 5/27/14 or newer so...

Good Luck!

 

[gerhardo]

Also I don't think TWRP recovery is working for firmware 5/27/14 or newer so...

Daniel Ortiz (with Dees Troy) fixed TWRP for "May list #4" and later with new TWRP. (In post on July 9 on G+.)
Not sure how to tell the difference with new eemc. The scatter file is different, but you need a reference...

https://plus.google.com/111628072657804333818/posts/bVRd9aDvBwm

 

[GADGTGUY]

I'd be happy to do a dump of this firmware if it is newer than what people have.

Walk me through it and I will take care of it.

D.

 

[walscobry]

thanks for the may info

Well that did lead me to the may twrp that I have been looking for but it does not work. By that I mean it only sees the boot partition and also when exiting exclaims that no rom is present. I don't think it is full aware of the partition layout of my 5/27/14 firmware after OTA update. But exiting does return the TS to normal so not much harm done in trying.

As for a walk thru. Using the MtkDroidTools is fairly read whats on screen and proceed carefully. But I will refresh myself with it and try to be ready for more questions.

FYI while in TWRP I did not get the constant screen touching and dragging from the lower right corner like I do when booted into the full OS. Some people have mentioned static. I think it might be what us HAM radio guys call getting RF back into the system. In TWRP I am guessing all radios (cell, wifi, BT) off so no RF getting into the touch controller cable. I wonder if I open it up and see if there is someplace to insert a little RF blocking foil near that cable. This might have been a fruitful try even if I still have no recovery.

Also I was asking to share the backup of your firmware only. DO not share your Device ID / IMEI numbers!