yashsingh1/xdaforums huggingface dataset:
[Ornate TrueSmart] AndroidFileHost:
thanks

Now I do have a problem with my other omate.

I tried to operative omate flash tool and it worked great on my other omate. I tried to use it on my other and i get stuck on the boot logo of yours.

I did the return to stock flash tool and then tried the operative omate tool again and still stuck on the boot image.

Any ideas?

Get a bunch of errors in the tool like this

cp: /system/app/20140117_launcher_watch_822040a.apk: No such file or directory

cp: /system/app/Fleksy.apk: No such file or directory

rm failed for /system/app/20140117_launcher_watch_822040a.apk, No such file or directory

rm failed for /system/app/Fleksy.apk, No such file or directory

Have now tried the script 3 times and it doesnt work on this other omate of mine. Only way to get the omate working again is return to stock. Very weird. Same version as my other omate.

I have also wiped everything off the omate and tried again and still no go.

Trying a 4th time and get the same errors but also some others

iled to copy 'C:\Users\APAETZ~1\AppData\Local\Temp\CASUALap-2014-03-31-11.15.37\SCRIPTS\EnSec TrueSmart\framework-res.apk' to '/system/framework/framework-res.apk': No space left on device

5184 KB/s (2219176 bytes in 0.418s)

3189 KB/s (22866 bytes in 0.007s)

failed to copy 'C:\Users\AP~1\AppData\Local\Temp\CASUALapk-2014-03-31-11.15.37\SCRIPTS\EnSec TrueSmart\Settings.apk' to '/system/app/Settings.apk': No space left on device

failed to copy 'C:\Users\AP~1\AppData\Local\Temp\CASUALap-2014-03-31-11.15.37\SCRIPTS\EnSec TrueSmart\SuperSU.apk' to '/system/app/SuperSU.apk': No space left on device

failed to copy 'C:\Users\AP~1\AppData\Local\Temp\CASUALap-2014-03-31-11.15.37\SCRIPTS\EnSec TrueSmart\PlayStore.apk' to '/system/app/PlayStore.apk': No space left on device

Going to try to nuke this thing now lol see if i cant get everything deleted

cant get back to stock now ugh lol what a mess

Thanks
[Ornate TrueSmart] Lokifish Marz:
Flash the 20140120 firmware and format internal storage. It is key that you be using the 20140120 firmware and nothing else.
[Ornate TrueSmart] AndroidFileHost:
ah im an idiot I forgot about 20140120

My other omate dev edition was already on 20140120. My non dev one is on 20140115

Thanks Lokfish
[Ornate TrueSmart] sniperops1318:
Is there a guide for upgrading from 20130115 to 20140120? I am also on the wrong rom version.

Thanks
[Ornate TrueSmart] syounger64:
My 1900 1/8 Truesmart watch will not power on after returning it to stock. I tried pulling the battery a few times but it didn't work. I remember you trying to help someone by the name of irona who did something different. Does the power button tend to fail after a bad update or root?

What do you suggest? Any help would be greatly appreciated.
[Ornate TrueSmart] Agent.:
Device: 1900 1/8 TrueSmart

ROM/Firmware version: EnSec 20140318

Changes made to stock firmware: Patch Ran

What OS is on your PC if your PC was used: Windows 8.1

Issue: According to the Companion App and Clock Face app my Truesmart is not a Truesmart. I received it today and everything appears to work fine, all I did was appy the patch and now it wont let me use the Clock Face app or Companion because it says I'm not using a Truesmart

Steps Taken: Restarted Truesmart and reinstalled apps, reran patch
[Ornate TrueSmart] Lokifish Marz:
[MENTION=4562190]syounger64[/MENTION]

If you are having an issue with firmware flashing it needs ot be posted in thread/guide that you used to flash the firmware.

[MENTION=5117260]Agent.[/MENTION]

If you ran anything other than EnSec

TrueSmart

or Operative

TrueSmart

then those apps won't work. Which one of the four options did you run?
[Ornate TrueSmart] Agent.:
I downloaded this file http://goo.im/devs/LokifishMarz/Umeox x201/EnSec Security Patch and followed the instructions. That was the only download link to anything that I could find.
[Ornate TrueSmart] Lokifish Marz:
[MENTION=5117260]Agent.[/MENTION]

Yes. One file with four install options (look right below the "DOWNLOAD HERE" LINK)
[Ornate TrueSmart] Agent.:
Well I feel extremely stupid, I didn't see that drop down menu lol. Thank you for your help!
[Ornate TrueSmart] trent999:
You are not the first or only one to not see the drop down, Agent !
[Ornate TrueSmart] syounger64:
[MENTION=2521422]lokif[/MENTION]ish....sorry about that. Wasn't thinking straight after too many battery pulls from my watch
[Ornate TrueSmart] ipaq3115:
Is anyone else having trouble downloading the "EnSec + Operative 20140318"? I'm assuming this is the file I'm looking for http://goo.im/devs/LokifishMarz/Umeox x201/EnSec Security Patch

I've been trying to download it all day and it keeps failing before it gets more than a few megabytes. Are there any mirrors, or should I just wait it out? Looks like they might be doing maintenance or something. Anybody successfully download it recently?
[Ornate TrueSmart] trent999:
I got a 7k file. Seems like a problem.
[Ornate TrueSmart] Lokifish Marz:
I just DL'd and everything was fine. There are no mirrors as that requires I maintain the files on multiple download hosts. I have run into issues before where others have mirrored my work and either do not keep it up to date or something is not right with the mirrored file or the host they put it one has malware/viruses.
[Ornate TrueSmart] ipaq3115:
I completely understand. I got it to download four different download managers later, no idea what was going on but I've got it now, thanks for all your hard work! :good:

DownThemAll is what finally worked if anybody else encounters the same problem.
[Ornate TrueSmart] harozrock:
3g using at&t sim card true smart

Hey Im trying to get 3g.. i have the x201, i have an at&t sim card that was working in a note 3. Im only getting edge. I have updated APN settings. If this was already covered i apologize, but shouldnt i still be able to get 3g service? if so, how do i do it?
[Ornate TrueSmart] Lokifish Marz:
[MENTION=5812649]harozrock[/MENTION]

Not sure why the built in APN's are not working now as nothing has changed on the patch. Are you using AT&T or AT&T AIO prepaid? Also, are you sure you have a 1900 TS and not a 2100 TS as there seems to be some serious issues with them sending the wrong models.
[Ornate TrueSmart] harozrock:
Im almost positive that i have the 1900... is there a way to check that on the watch itself? also, i am using just at&t.
[Ornate TrueSmart] ipaq3115:
Best way is to check how much RAM you have under Settings > Apps > Running

If the two sides (available and free) add up to less than 512 you've got a EU version. I think there are 8 reports of EU devices sent to North America so far.
[Ornate TrueSmart] wce2k:
Enter Engineering mode from the Dialer by dialing *#*#3646633#*#*

BandMode

SIM1

[MENTION=3795702]Lokifish Marz[/MENTION]

Mine has 1900/850 checked, I'm trying to use 3G 850 and I can't make it work, just EDGE, any idea?

WCDMA-PCs-1900

WCDMA-CLR-850

Thank you in advance
[Ornate TrueSmart] harozrock:
sure enough, its les than 512...
[Ornate TrueSmart] ipaq3115:
Congrats! You have a EU watch. Lol, sorry to hear that. I'm in the same boat you're in.

Link to the 'wrong device' thread: http://xdaforums.com/showthread.php?p=51778002
[Ornate TrueSmart] Lokifish Marz:
[MENTION=296951]wce2k[/MENTION]

The x201 doesn't work on 3G 850MHz. Not sure if it's an antenna, radio, baseband or radio tuning issue.

[MENTION=5812649]harozrock[/MENTION]

Having a 512/4 2100 would certainly keep 3G from working on AT&T
[Ornate TrueSmart] wce2k:
Well, no more to say.

Thank you
[Ornate TrueSmart] thompsos:
Display Option Menu FCs

Nevermind, I must have broken something myself.
[Ornate TrueSmart] rik81:
no longer works the shortcut settings in the status bar

1.Device: Callisto 100

2.Firmware version: Omate_Truesmart_20140120_working sensors

Great Patch/Mod does everything by itself .... and it works fine

Only one problem after install this Patch: No longer works the shortcut settings in the status bar

Does anyone know a way to fix?

It is also possible to have the volume control in the menu power (such as the original firmware of the Callisto 100)

Thanks
[Ornate TrueSmart] stealph:
EU 1/8 2100 Compatibility

Will the EU 1/8 2100 model need the security patch? Not yet received mine.

Thanks for any help.
[Ornate TrueSmart] Lokifish Marz:
[MENTION=1244493]rik81[/MENTION]

It's a known issue. I don't have a fix for it right now but the trade off was folks not having to pay for apps to enable accessibility settings.

[MENTION=365010]stealph[/MENTION]

Not sure. Considering that every x201, no matter what the brand or model, so far has required it, I'd say the chances are extremely high.
[Ornate TrueSmart] Dennispgp:
I just recieve the EU 1/8 2100 model, it is on custom build version 20140328.182336_V2.0 which version of EnSec can I use?

Kind regards,

Dennispgp
[Ornate TrueSmart] haardman:
I've also just received my 2100MHz running:

Android v4.2.2

Baseband: MOLY.WR8.W1315.MD.WG.MP.V.4, 2013/08/14 18:15

Kernel 3.4.5

Omate: OUI 2.1

20140328.182336_v2.0

Wondering what I need to do...
[Ornate TrueSmart] Lokifish Marz:
I still do no have a copy of that 0328 firmware so have no way to test it.
[Ornate TrueSmart] Mardaso:
How can I make a copy for you? I'm also on 0328 firmware and got my Omate yesterday.
[Ornate TrueSmart] Tickox:
Hello, I also got the 1/8 2100Mhz version this week. It has firmware 20140328.18 2336_V2.0

I really would like to install patches and get root and so on. I just don't feel safe to setup my email account when there is so many security bugs.

What can we do to help ?
[Ornate TrueSmart] Lokifish Marz:
I need somebody to make me a backup using MTKDroid Toolbox. All Tools has this included. The only problem I see is that I don't even have a 1/8 2100 to test it on so I'll be working blind.
[Ornate TrueSmart] Tickox:
Hey Lokifish, you should be the first one to get one of each model directly from the Omate team....! Hello OMATE....!

I only have one clock and don't want to send it the world around (live in Sweden).The wait has been long enough as it feels right now.

I will make a copy for you with MTKDroid Toolbox this weekend if i can :)

I think it will be more and more people that really want this for this model.

I will happily donate for your work.

Thanks.

Donation done.
[Ornate TrueSmart] Mardaso:
[MENTION=3795702]Lokifish Marz[/MENTION]: I've made a backup. What's the best way to get the files to you? Send a dropbox link to your paypal mail address?
[Ornate TrueSmart] Lokifish Marz:
[MENTION=2950218]Mardaso[/MENTION]

You can PM me the link. Thanks.
[Ornate TrueSmart] gentoolkit:
I was just checking out the EnSec + Operative 20140318_v2 SCRIPTS folder and comparing the EnSec TrueSmart files against my new 1G/8G/2100Mhz. I was planning to apply it manually. However, I have a few questions:

00setperm and 99loki scripts contain a lot of chmod 666 and chmod 777 commands. Why? Why isn't chmod 644 or chmod 755 enough?

My Truesmart is missing the following executables: /system/bin/busybox, /system/bin/fstrim and /system/bin/sysctl. It seems that the casual script doesn't install these. Do others have these as default?

My Truesmarts /system/bin/logwrapper executable doesn't accept run-parts as a parameter (see sysinit script). Does anyone else have this problem?

Where exactly is the "all apps running with root permission" problem fixed?
[Ornate TrueSmart] Lokifish Marz:
Those 666 and 777 are the exact same perms that a number of well respected tuning apps use. In fact, use Android Tuner with the same options and set it as init.d and compare. In some cases dropping them to 655 and 755 caused serious inconsistencies with parts of the scripts actually working.

xbin, it's an error in the script that I need to fix. There are also entries that are not currently active as well.

If it wasn't working then init.d would not work. Install-recovery.sh calls sysinit which calls logwrapper run-parts for init.d.. This can easily be verified by simply checking the SD Cache size which is set to 3072 by 99loki and not the default 128.

The x201 runs in root user, this gives unchecked root access to the whole device. If an app issues the proper su request it fails but if a malicious app/website simply executes commands without the su request it works. By installing su and super user this at least minimizes this risk. For example, you can push files, alter permissions and remove files and never issue the su request once. Myself and others have been able to erase the IMEI and MAC addresses doing this very thing.

Is this perfect? No. Then again with all the holes and crappy coding the x201 comes with from Umeox, it's still a major improvement. I have not spent much time on it lately as I got tired of seeing the same things I told them back in the beginning of November go unfixed on every firmware release.
[Ornate TrueSmart] gentoolkit:
OK. For me, setting more strict permissions seem to be working fine. I am just bit worried about setting chmod 777 for certain places.

It seems that it does not work. Unless I made a some kind of mistake. It seems that run-parts executable is missing. However, this works after I installed the busybox:

/system/bin/logwrapper busybox run-parts /system/etc/init.d

I realized that much. I was just wondering how this problem is fixed exactly. [edit: A stupid question removed]

I really appreciate your work. Do not get me wrong. I was just thinking that some of the observations might be useful.
[Ornate TrueSmart] Lokifish Marz:
If you ran the patch, it's not even tested on the 1/8 2100 so if things don't work that's to be expected.

If I can verify that the changed permissions works on all devices and firmware then I'll alter them. But the changes need to work universally and have failed to work in the past.

I haven't even looked at the 1/8 2100 firmware yet so not sure what the issue is with init.d not working. It does work in all the other models and brands so far.

If you are moving over things manually there are somethings that are installed script wise and some things that are installed by pushing files.

Out of the 14-15 different firmwares I've looked at, not one has su installed or superuser. This can go bad real quickly. I'm not sure if they fixed this on the 1/8 2100 firmware yet.

Please keep in mind that I didn't even get a copy of this firmware til today and have not had time to go through it line by line. Seeing that the PCB is different than all the other models and I do not have a 1/8 2100, this is probably what it will take as flashing it asking for a soft brick.

Input/feedback is welcome as I may miss something and there are multiple solutions to certain issues and I can't think of them all.
[Ornate TrueSmart] azizbouharb:
Can you please send me the link to the rom, my watch has a chinese rom and i flashed every other possible rom, still the sensors on my watch are not working, i need this version to make my watch work.

Thanks in advance
[Ornate TrueSmart] Lokifish Marz:
It's incomplete and lacks critical files.
[Ornate TrueSmart] gentoolkit:
I just realized that the reason why the init.d directory did not work when I installed the patch manually was that I did not run the pwn executable or something went wrong otherwise at that point. I did run busybox --install /system/xbin/ at some point but I probably gave up with the init.d directory before that. Unfortunately I cannot confirm this right now.﻿
[Ornate TrueSmart] azizbouharb:
Thanks, ill be looking forward for it
[Ornate TrueSmart] koskos:
For Callisto 100, which patch should I apply? I ran 20140318 and EnSec worked fine for me, but when I tried running Operative (both TrueSmart or x201 I ended up stuck at the logo page and had to re-install original firmware or Callisto (after which the root was lost).

Another issue is that EnSec deletes original unlock displays (watch faces from Callisto, which are quite pretty) and leaves only two options - 1 analog and 1 digital. Is there any way to return the original 10 or so watch faces from Callisto to EnSec?
[Ornate TrueSmart] Lokifish Marz:
Did you flash the 512/4 WORKING SENSORS firmware prior to running the patch
[Ornate TrueSmart] koskos:
No, I didn't. My understanding was that the 512/4 WORKING SENSORS should be installed from TWRP, i.e. after running the patch. Otherwise, if there's no TWRP yet, how do I install 512/4 WORKING SENSORS prior to running patch? (sorry, didn't find any clear instructions about that in this thread...)
[Ornate TrueSmart] Lokifish Marz:
As stated numerous times in this thread, firmware first using SPTools then the patch/mod. I will edit the instructions so that this can not be misinterpreted.
[Ornate TrueSmart] thorax.axp:
No sensors with WORING SENSORS firmware on AW-420

Did patch to working sensors firmware "EU 512-4 2100 20140120 working sensors"

Applied operative mod, but no sensors.

Watch is an AW-420.rx, is there a working sensor firmware + operative mod ?
[Ornate TrueSmart] haybill:
The very fact the you have finally got hold of the Firmware for 1/8/2100--is cause for celebration. I understand that your not having a device in hand to test makes things a lot more tricky, but, as these elusive devices are finally sent out there will be more and more of us willing to do your 'physical' testing for you.

Thanks for sticking with this crap game.

I notice that you have a Umeox--but from your comments it is almost as, or more so, screwed up as the Omate--or are you happy with it?

I am searching for a workable alternative to my 'yet to arrive' Omate TS.

Are you still awaiting your Omate--and [ pray to Dog] is it a 1/8/2100??

---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------

Do you mean that the actual Firmware is incomplete [He says worriedly]--or just the version sent out to you? Using MTK tools is not an easy thing for many of us.

.

---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------

Err--something tells me that Loki is not satisfied that it is a Flashable firmware--it would be ill-advised to flash something that is lacking critical files, surely???

Finally--just saw my name on the Kickstarter comments Mailing list for 24 April--so, if I can be of assistance,[ assuming Customs don't screw with me too hard]-- I am available as soon as I can get my grubby hands on the gadget.
[Ornate TrueSmart] Lokifish Marz:
Omate is Umeox so the Pearl, iconBIT, xTouch and so on all come from the same place. Mediatek compiles the firmware. So the except for an app or two, wallpaper and the watch case, they are all the same device which is an x201. It even says so in the build.prop.

The backup that I was given is incomplete and a brick risk to use. I had to build a firmware using files from other sources.
[Ornate TrueSmart] haybill:
Sorry to seem a bit slow--but, are you saying that you HAVE built Firmware for 1/8/2100 Edition, already??
[Ornate TrueSmart] Lokifish Marz:
http://goo.im/devs/LokifishMarz/Umeox x201/Firmware

And a prepatched ROM as well.
[Ornate TrueSmart] haybill:
Well, since my name is now on a delivery list--I might actually receive my watch soon-ish--so, it should be Root and Recovery and then Flash Loki's ROM, I guess--ASAP.

Huge Thanks from me--and probably a whole bucket load of other folks--we owe you, big time.

I might have to add to my previous donation--and anyone else should do so, also.
[Ornate TrueSmart] useretail:
Looks like you got 1/8 2100 firmware. (Omate_1-8_2100_TrueSmart_20140328.zip)

When we can expect EnSec Enhanced Security + Operative patch?
[Ornate TrueSmart] Lokifish Marz:
Will try to get a working patch out for all devices but it has been problematic and my time is limited these days
[Ornate TrueSmart] useretail:
Thanks. We all appreciate what you're doing. In the light of last security vulnerabilities discovered (i.e. heartbleed) this patch is vital.
[Ornate TrueSmart] eozdalga:
[MENTION=3795702]Lokifish Marz[/MENTION] I just got a new replacement Omate (as the BT/Wifi was broken)! I wanted to simply install your patch but I see I'm not on the 20140120 firmware that the first Omate came with. The new Omate has 20140328 installed as stock (image attached). Do you know if I can still and should install the patch?
[Ornate TrueSmart] Lokifish Marz:
I don't have that firmware either. Gonna need to flash to 20140120 or what I suggest is install TWRP and flash Dess BT ROM if you are going to use your TS as a companion.
[Ornate TrueSmart] eozdalga:
Thanks for the reply. I don't plan to use as companion so I might flash to 20140120 then patch as you suggest. Do you think it's possible (or is there a way to know) if this firmware is secure and hence no need for patch?

Edit: FYI, this stock firmware seems better than the 20140120 stock. GPS really good out of box!
[Ornate TrueSmart] Rajesh_ya:
After flashing 20140120 firmware and then Ensec Owatchon does not work

Hi,

I just bought my Omate 512/4 2100 from ebay.. Flashed the 20140120 working sensors firware and then patched the Ensec.. did the factory reset..

When I open the Owatch on app then sensor does not seem to work. the level indicators do not move at all and I cannot get the shake to work.. I tried shaking the device as fast as I can but the app does not show any activity.

Any help would be much appreciated..

Thanks guys..
[Ornate TrueSmart] Lokifish Marz:
Not sure what to tell you. "201401220 working sensors" was tested on three of the known 512/4 versions. I have not seen new firmware for the 512/4 in some time now and that model is not even sold by Omate anymore.

Your not working most likely means there is yet a fourth version or the sensors are bad. about all I can suggest is either returning it, is possible, or flashing various firmware til you find one that works.
[Ornate TrueSmart] gentoolkit:
I just got my Windows 8 installation up and running. Unexpectedly F-Secure anti-virus began to warn that the EnSec patch contains adware:

Adware:Android/[B]Dowgin[/B].70759!gen

The file in question is framework-res.apk.

I was confident that this was just a false alarm. However, I pulled the corresponding files from my other devices and found nothing suspicious. Then I scanned the stock framework-res.apk from Omate and found the same adware. Maybe this is just a false alarm but I thought that it might be a good idea to mention about this.
[Ornate TrueSmart] Lokifish Marz:
What was your original FW version?
[Ornate TrueSmart] gentoolkit:
ro.custom.build.version=20140328.182336

ADD: I was not going apply the patch. I just had the file on my hard disk.
[Ornate TrueSmart] eozdalga:
[MENTION=3795702]Lokifish Marz[/MENTION] Is there a way for me to get you the newer 20140328 firmware off my Omate? Do you think there's a chance it doesn't need the patch and it secure?
[Ornate TrueSmart] Lokifish Marz:
No firmware from Omate or any other x201 is secure this includes 0328.
[Ornate TrueSmart] unirambler:
Question on changing "Operative Truesmart"

First, thank you, Loki, for your hard work on the patches and ROMs for the Truesmart. It really does make the watch useable for me. :good:

Now, for my question (and as you can tell, I am a noob at this flashing stuff). I used the "EnSec + Operative Casual Edition" Java file on my Truesmart (1900, 1/8) and flashed "Operative Truesmart" so now I have custom build version "Operative 20140318" on it. Everything is working well for me ( I use it as a stand-alone).

However, I was wondering, if I decided to flash a different version (for example, if I decided to go to the "EnSec Truesmart" so I could have the look of the original Truesmart or wanted to totally change the ROM - to use the "Unified 1/8 1900/2100 Unrooted Secured Tuned Stock" for example) - would I need to restore my Truesmart to it's original firmware first? If so, how would I do that? I backed it up before doing anything using the MTKDroid Tools but don't know how to restore from that. The thread on "Returning to Stock" uses an older downloaded firmware than I originally had and I would want to return to what I had, not something older.

Thanks again for all of the work you are putting/have put in to this - you and all of the other devs that have made this watch succeed so far!