yashsingh1/xdaforums huggingface dataset:
[Ornate TrueSmart] kuronosan:
To answer your question, the second file is what you would want. You'd want to run the root script (there are two parts, the first is root, the second is security patches). You'd have to run the root script and then unplug the watch before confirming the EnSec script. Right now there's a bug that removes your camera app and doesn't copy the new one over... so we don't want that happening.

Alternatively, since the TS is already running in root mode, all you have to really do is just copy the SU/BB binaries to bin/xbin and install SuperUser to fix/secure the root.
[Ornate TrueSmart] Enlightenment79:
Thanks for your help. My Omate TrueSmart is now rooted. :)
[Ornate TrueSmart] kuronosan:
Any time.
[Ornate TrueSmart] zipizip:
Hi Kuronosan,

I have installed your rom and would like to know if it was necessary to install Dees bt-rom.

Please advise.

Tks
[Ornate TrueSmart] kuronosan:
In order to do what?
[Ornate TrueSmart] zipizip:
Your rom is working very well, thank you for your effort. However, I find that the bt of the TS could not detect a 2nd device for pairing after it has previously paired/connected to a first device despite already disconnected from it. As long as the first device is shown as a "paired" device (not connected) in TS, it cannot detect a 2nd device for pairing. Let me elaborate. I have 2 listening devices which I used for different hours of the day. After I have paired and connected with my first device and subsequently disconnected it at later part of the day, TS was not able to detect my 2nd device when it was turned on. I have to unpaired the first device from the bt setting in TS then it can detect/pair/connect my 2nd device. For my main mobile phone, it can show a list of previously paired devices which may not be connected. When any of the listed devices is near and turned on, the phone will automatically detect and connect it without having to pair/connect it again. I also do not need to unpair previous devices each I need to pair another device. I find TS bt does not work that way. My conclusion is, TS can only pair with one device at a time even when it is not connected to it. It can detect a 2nd device only when the first device is unpaired. BT menu in TS also lacks a "Scan" button for scanning for new devices.
[Ornate TrueSmart] kuronosan:
Have you tried swiping right to open settings, then selecting "Scan"?

And the rest of that honestly is not my problem. I didn't design the firmware, so I have absolutely no control over how many devices you can or cannot pair to.
[Ornate TrueSmart] zipizip:
Thanks for reminder regarding the settings options in the bt menu. I always forget about swiping right for the options. Now I can find the "Search for Devices" option.
[Ornate TrueSmart] Evar678:
My TS's build version is 20140706_V2.0, which of these do I download?
[Ornate TrueSmart] kuronosan:
None of them? If you're already on 0706 you needn't do anything else.
[Ornate TrueSmart] Evar678:
... Oh, thanks. I feel rather dumb.. :(
[Ornate TrueSmart] nrseife:
Kuronosan,

When I am selecting the sport mode I noticed that I can only turn on the watch by pressing the power button (which I am trying to avoid). With the normal mode the 2nd button also turns on my TS or I can use Awesome On Off (turns on screen when I tilt TS, works most of the time in normal mode)....do you know why and if there is a simple fix to that? What is different in sport mode that the 2nd button is not turning on my watch and Awesome on off stopped working completely? Anyone using a similar app that works in sport mode?

In sport mode Walk Logger is a lot more accurately logging my steps....so I really would like to continue using this mode...

Thanks!
[Ornate TrueSmart] kuronosan:
That's a firmware issue beyond my control unfortunately.
[Ornate TrueSmart] Eddie08280:
Hi! I've got the 0801 version too and would like to root it (in the least complicated way). This alternative sounds quite easy, but I am not sure what 'copy the SU/BB binaries to bin/xbin and install SuperUser' means. Could someone please explan that to me a bit more detailed or point me to the right thread?

I really don't want to screw something up, since i waited now almost a year for my smartwatch. Just need root access for some apps (like cpu tuner)
[Ornate TrueSmart] nrseife:
Btw, I realuzed that the screen is actually always on in sport mode (only backlight is off). That's why after hitting power buttons I am sometimes in weird settings etc instead in the some watchface...I accidentally touched the screen, but did not see the impact until the vacklight is on after pressing the power button. So what I need is an app where only a small area is sensitive to touch and all it does is turn on the backlight....anyone knows such an app?
[Ornate TrueSmart] gerhardo:
Not exactly what you ask for, but app No Touch can ignore inputs and be activated when you turn off/on the screen.

SportsMode is useless, no bigg difference in low intensity or None, if the screen is on it uses battery.

I use No Touch connected to a special button mapping:

http://xdaforums.com/showthread.php?t=2714281
[Ornate TrueSmart] LaDamian:
Finally got my TS 1/8 European developer addition (Only a year late, woo!). I got the drivers to install, and I successfully backed up my stock firmware. I also think I backed up my IMEI and Navram (Navram has a backup. I don't know if this includes IMEI), but the instructions have a link that leads to a missing thread.

I did a phone information dump hoping it would help anyone more knowledgeable than myself.

Hardware : MT6572

Model : TrueSmart

Build number : ALPS.JB3.MP.V1.8

Build date UTC : 20140328-102943

Android v : 4.2.2

Baseband v: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16

Kernel v : 3.4.5 (user@user-desktop) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #14 SMP Thu Mar 13 18:04:17 CST 2014

Uboot build v : -----

LCD Driver IC : 1-s6d04d2x01

I have a few questions regarding flashing this:

1. I think I am Pre-May European 1/8. Is this correct?

2. If the answer to #1 is correct, do I flash the "EU 512/4 users or those with non-aluminum, non-May firmware units must click here unless you want to soft-brick your device"? I don't see a link specifically for EU 1/8 non-may firmware.

3. If the answer to #2 is correct, can anyone provide a link to that download? The link from Post #2 is dead.

4. After flashing this, do I need to install TWRP, or will it be included?

5. Do I need to do a separate backup for the IMEI? I have two backups of the nvram. One is in a .bin format and the other is in a .tar format.

Thanks a lot for any input. I've been waiting for this watch for a very long while, but I don't want to use it until I get it properly secured.
[Ornate TrueSmart] kuronosan:
Based on your kernel build alone you have a pre-May unit, so the answer would be yes. Flash only pre-May firmware. Also, you'll need to flash TWRP using mtk tools.

As far as the links, a few posts up are the new files. Sorry, I haven't updated the OP.

Your IMEI will most definitely need its own backup. MTK places this on a hidden partition which is easily corrupted during firmware flashes. Having a backup of the nvram and the imei is the only way to protect yourself, since they don't secure the partition.
[Ornate TrueSmart] LaDamian:
Thanks for the quick reply.

I noticed that you posted a link for the pre-May kernel, but also said that there weren't any benefits from it. Is this why that link is not found when I click on it?

I see a link for TWRP for the may units, but I do not see one for pre-May units. Can I just download 2.7.1 from their website?

EDIT: Sorry. I see now that there is a .tar file for TWRP in the download.

I found a youtube clip showing how to backup the IMEI using the MTK droid tool, and I had done it correctly.

Thanks again
[Ornate TrueSmart] LaDamian:
I'm actually super confused now. I think I misread your answers at first.

I don't see any scatter files in the downloaded EU rom, you said the OP wasn't updated, and you mentioned that I will need TWRP.

Does this mean that the roms are only in a TWRP flashable zip? That would be great, but I'm scared I will flash a bad version of TWRP.

Is the "openrecovery-twrp-2.7.1.0-omatesmartwatch2.img" version correct for all watches at aren't post-May watches?

Can I just push it using adb instead of the mtk droid tool?

Thanks for all the hard work. Please let me know if I need to take these questions to another thread. I've spent a couple hours looking for the correct information, but a lot of the use of the MTK tools seems to be missing.
[Ornate TrueSmart] kuronosan:
The answer to your question is yes. There's only one twrp image, the other was repackaged by me. Droid tool just pushes over adb for you.

If you're going to do it, push it to dev/recovery.
[Ornate TrueSmart] LaDamian:
For some reason flashing the latest Pre-May zip is failing in TWRP. I get the following message:

assert failed: run_program ("/tmp/twrpTar", "-x", "-d", "system", "-t", "/tmp/system.tgz") == 0

E:Error executing updater binary in zip '/internal_sd/EU PreMay- 07.06 EnSec.zip'

Error flashing zip 'internal_sd/EU PreMay- 07.06 EnSec zip'

and a little red "Failed" shows up on the screen.

This is all after a full wipe. I downloaded the update zip for a second time in case the first download was corrupt. Any ideas what I may be doing wrong and how to fix it?

Thanks
[Ornate TrueSmart] kuronosan:
You don't have a 1GB RAM model. You have a 512MB model.

Go to the update script and change the install location from temp to sdcard/install.
[Ornate TrueSmart] LaDamian:
Well, I finally got a rom installed thanks to you other awesome work. I had to install the "easy" method of your Retrosmart rom.

I tried updating the script, but I could never get this to flash. I still don't know what was causing it. At first I assumed Omate had lied or screwed up once again, but according to an installed hardware info app, it does have a gig of ram. Hopefully I can figure this out in the future. This rom looks really great.
[Ornate TrueSmart] LaDamian:
I was finally able to flash this rom after downgrading my version of TWRP from 2.7.1.0 to 2.7.0.0. No changes were needed in the installer script. I hope this helps anyone else that has trouble flashing this.

Thanks again for all your hard work.
[Ornate TrueSmart] kuronosan:
Interesting. Good to hear.
[Ornate TrueSmart] Kuma-sama:
I noticed that you posted a link for the pre-May kernel, but the link is not found when I click on it. Was it removed?
[Ornate TrueSmart] Kcspaceman:
This link no longer seems to be working. Would you be able to re-upload it somewhere please kuronosan?
[Ornate TrueSmart] syounger64:
Hi Kurosan...I sent you the backup files for my watch a couple of months ago then you reported to not to find anything special.

So I should use the NA version to upgrade my watch? My version is still the same version as I sent you. I'd like to start using this watch. Thanks.
[Ornate TrueSmart] kuronosan:
The firmware I was waiting for is now working so I'll be updating this soon enough.
[Ornate TrueSmart] syounger64:
That's great news!
[Ornate TrueSmart] knosalaa:
dead links

Can you please reupload NA firmware so the link works - need 1900 mhz 1/8 rom

Thanks
[Ornate TrueSmart] kilroo:
Are these still the correct/best stuff to use for those of us who need SIM and sensors? (coming from Loki's last release of EnSec+Operative, if that matters)?

What is the proper way to confirm that everything went correctly after flashing the firmware and baseband?

Is the kernel optional (pre-May) or is that 404 a showstopper?

Is one supposed to run the script from the first post after flashing the firmware and baseband?
[Ornate TrueSmart] mghtymse007:
NO LINK, NA 1/8 pre-may En-sec v1.3

does anyone have a working link for the last NA pre-may En-sec v1.3 release? The above posted links only has the EU...

or

[MENTION=1337268]kuronosan[/MENTION], can you upload and post a new link?

Thanks!!!
[Ornate TrueSmart] KingJavier91:
Quick question

How is one suppose to tell whether they have a pre may or post may build? I purchased my omate from someone and he doesnt have any idea if the watch i received is a pre may or post may
[Ornate TrueSmart] thgxda:
Hi kuronosan,

first of all thank you very much for all your efforts, especially even without relevant support by Omate or MediaTek, to get newer ROMs done.

I really hoped to get at least a 4.3 ROM for the TrueSmart, that could support sensors and BT4LE, but neither Omate nor MediaTek are able and/or willing to support the volunteers, that are doing their work for free (an Android 4.3/4.4 update was promised by Omate)!

how can I check this?

I have my 1/8 EU TrueSmart "before May", and already installed some updates on it, long time ago.

I'm not very happy with my TS anymore, mostly because BT4LE is not working and some sensors only work with display on, from time to time the screen does "funny" things and puts random touches on my watch, that makes it unusable.

So while BT4LE will not be "solvable" (at least if you still want to have sensor support), may be other problems will?

How can I check my real version, my TS says:

"Android-Version: 4.2.2, Kernel-Version: 3.4.5, Omate_TrueSmart_EnSec 20140427_V2.0"

So probably I'm at pre-May?

PS: Can you please "renew" the links for the kernel?

Pre-May Kernel:

...www-dropbox-com...52n3fe0piq...n-May.zip?dl=0

They only result in a 404.

Thanks a lot,

kind regards thgxda
[Ornate TrueSmart] steff_1964:
Hi Kurosan,

thx for all your work.

My Omate (8gb, 2100, pre-May, Steel) force-closes the camera at 5MPx, so I added one line to your "runme.bat"-file of your "Camera Patch Script" to get the google camera pushed onto my Omate:

.......push liblightcycle.so /system/lib/

Adb push GoogleCamera.apk /system/app

echo [*] F.........

This worked, and I can take 5MPx-Pics, but the video camera does force close all the time now.

Is there any way to get real 720p Video recording instead of864x480@30fps?

Cheers, Steff
[Ornate TrueSmart] kuronosan:
I don't think so, no. I'm not sure what else to change.
[Ornate TrueSmart] andress.cz:
Hi, could you please renew the links?
[Ornate TrueSmart] mghtymse007:
Pre-May, NA, 1/8

got the IronMan firmware loaded. AMAZING!!! The battery life is truly remarkable!! Great job! Any chance of ever getting the 1900Mhz 3G operational?

On that note, I just can't do enough with only the 2G working. So, I would like to go back to the final EnSec release..

The links in OP#2 are no longer working. Can you please relink/repost? Don't need the "All Tools" zip, just the image. if you want,

PM me and ill give you URL and login auth to my FTP... i then can post a link for those that still need it.
[Ornate TrueSmart] japodude:
any working Links please
[Ornate TrueSmart] madarx:
zc01

can in flash it on my zc01 512Mb RAM 2GB ROM mtk6572 dual core 1.3 its clone from Omate but the driver installer in my pc recognized it as omate driver
[Ornate TrueSmart] kuronosan:
Correct.
[Ornate TrueSmart] kuronosan:
Copy the contents into the original firmware folder you downloaded and flash the new lk.bin and boot.IMG instead. You should overwrite any existing files in whichever you downloaded.

Just as a note, folks. There is a huge difference between the May Shipment EU scatter and the EU scatter. If you aren't sure which one you need, post what firmware you are on and I will tell you.
[Ornate TrueSmart] MaloyO:
Ok. So I should try the pre-May flash.

I'm pretty convinced it was 140513 firmware but I could be wrong. Or I've done something else and royally messed it up!

I'll let you know how it goes.

That didn't go well. Got the same message as when I tried to flash the later firmware. What have I done?!
[Ornate TrueSmart] gillebob:
Followed details posted by midafaya and yourself and im booting again, thanks.
[Ornate TrueSmart] kuronosan:
I'll need to link you to a preloader, or try flashing from an eMMC scatter. Typically that means your partition is borked and you'll now need to format and start over.
[Ornate TrueSmart] MaloyO:
Ok, my back up has a preloader. Should I just flash that by itself?
[Ornate TrueSmart] kuronosan:
Start with that, yes.
[Ornate TrueSmart] MaloyO:
Trying to flash the preloader ... SPF tool gets to the end of the 'download da 100%' and then just keeps counting the time.

I can see in USBDeview that the MediaTek USB VCOM keeps connecting and dis-connecting.

So far 10 minutes has passed with no change in SPF tool and no error message.

Really do appreciate this kuronosan. I'm going to owe you some serious beers. I don't want to take up all your time and it's late here so could I hit you up tomorrow for your brain power?

Thanks again.
[Ornate TrueSmart] kuronosan:
I'm available any time. You might need to pull the battery for that one.

Typically the reason that happens is the preloader didn't disengage correctly so it's somewhat in a state of limbo. The only way to remedy that is to reset the device.

After you flash successfully (only the preloader) you should be able to flash everything else.
[Ornate TrueSmart] kuronosan:
FAQ updated.
[Ornate TrueSmart] midafaya:
After using this ROM for a few hours, I find it pretty laggy.

I had several freezes too, that made the watch auto soft reboot.

(Using EU may shipments version + root & security patch)

Aside from this, every sensors seem to work, connections are like stock.
[Ornate TrueSmart] kuronosan:
That's because it is stock.
[Ornate TrueSmart] midafaya:
I apologize for my remarks about the rom being laggy. There's actually no difference with the stock received with the watch.

stock is stock as you said.
[Ornate TrueSmart] kuronosan:
Well, out of curiosity (sorry, health care is incredibly busy these days) when is it freezing?
[Ornate TrueSmart] MaloyO:
Hey kuronosan.

I've just spent two hours trying to get this preloader to download. It is having none of it.

Hope you've got some bright ideas ;)
[Ornate TrueSmart] kuronosan:
Give me some pictures or tell me the error. Is it just going to full and then saying BROM ERROR (5054/4032)? If so, you'll need to flash using an EMMC scatter file and a backup. It needs to rewrite the partition database.

This likely will also mean you need to format the entire NAND (including the preloader) once you get it restored and flash (at the same time) the stock ROM or backup to restore it.

I've fixed this error several times and it almost always required me to re-flash using the EMMC scatter (which is just the scatter file without PMT information, but customized to your chip).
[Ornate TrueSmart] kuronosan:
Also, links updated. I'll explain in a bit.

UPDATE

Thanks to some input and helpful advice from [MENTION=912474]Dees_Troy[/MENTION] TWRP has been repackaged and has been confirmed by one user to now be working on their Aluminum/May unit. Download is available in the links. Be sure to give Dees kudos for the idea, it sure taught me quite a bit more about recoveries than I knew before.
[Ornate TrueSmart] MaloyO:
No error message. The bar just fills up to 100% and stays there. As you say in the common issues it's dis-engaging when at the 100%.

You sound like you got more hope than me at this point. Where can I get the EMMC scatter file?
[Ornate TrueSmart] kuronosan:
Judging from the scatter file you're using the new firmware right? I have an EMMC from the new and from the old, but if it's sitting at 100% and then does nothing afterwards (but eventually times out to a BROM error) it's because the computer isn't actually engaging the preloader in the first place.

Check your device manager for what's showing up when you plug the watch in. If you plug the watch in and haven't done anything, but Preloader shows up and stays connected (without flashing) you need to uninstall all the drivers and start over with driver install/etc.

Sometimes what happens is the watch ends up in META mode (which is an entirely different mode altogether) if the computer doesn't catch it. It will still see it as a CDC gadget but because you're in Flash Tool and not META tool your PC doesn't know the difference.

I think that might fix your issue.

edit: I looked back over your posts and noticed this:

So you flashed the Pre-may update. If this is correct (you flashed 0706 instead of 0706-May) then you need this right here:
[Ornate TrueSmart] cmdaz:
20140328 fw

Is this post only about May units and 4/512 NA units?

I have a 1/8 2100 unit with FW 20140328

I installed TWRP and applied Loki's "Unified unrooted 1-8 1900 & 2100 Secured Tuned Stock ROM"

What difference between my current configuration and the devices upgraded with your package?

Anyway as my device is not rooted, I'm not allowed to run the script (operation not permitted, trying to run the mount command manually in adb command box)

Should I live with my current configuration and try Framaroot, or is there another solution to get aligned with devices patched with your script to get a 07.06 FW?

Tanks a lot.
[Ornate TrueSmart] allnutts:
am i doing something wrong again? I have gone through the MTK Droid Root & Tools stage successfully,and gone into Smart Phone Flash tool, selected the scatter file, but it doesnt seem to recognise that the phone is there. the bar at the bottom doesnt move at all.I can only find the dpinst drivers in the Win 7&8 folder (im on XP). My watch is the EU 1/8 delivered in June.
[Ornate TrueSmart] kuronosan:
If you're running that you should be rooted. This post is about every unit.

The only difference with the new firmware is that it has smart mode and a few "enhancements".
[Ornate TrueSmart] kuronosan:
Did you disable quick boot and turn off the watch?
[Ornate TrueSmart] MaloyO:
I have un-installed the drivers, rebooted and re-installed. When I plug my TS in it is recognised as 'MediaTek USB VCOM (Android) (COM4)'. It keeps connecting and disconnecting.

When I try to download a preloader it connects as 'MediaTek USB VCOM (Android) (COM4)' but then disconnects and reconnects as a 'other devices : Unknown device'

What would you suggest next?
[Ornate TrueSmart] allnutts:
I did disable quick boot and the most I get is the three low tones "blips" that signify that it's not connecting.
[Ornate TrueSmart] kuronosan:
Check your cradle pins and make sure they contact the battery. If it keeps blooping that's the most likely reason.
[Ornate TrueSmart] kuronosan:
Pull the battery and try again. Let me know what happens.
[Ornate TrueSmart] MaloyO:
Ok, I've got another cradle but it is at work. I'll grab it tomorrow and see if that makes a difference with establishing a stable connection.

Thanks kuronosan.
[Ornate TrueSmart] kuronosan:
Having a spare battery also helps. One unit I repaired refused to flash until I changed the battery.
[Ornate TrueSmart] allnutts:
It acted slightly differently, acknowledged that something was connected bur then still didn't lead drivers. I then got the three low dings again :-/
[Ornate TrueSmart] kuronosan:
Alright. Walk me through everything you've done from the beginning, including if you've flashed anything at all.
[Ornate TrueSmart] MaloyO:
Wa hey! We may get this TS working again yet.

So I've flashed the eMMC scatter and then the other back-up scatter that you gave. Now I have boot image (standard Omate TS).

Before I jump right in...what should I do next?

I was a lucky one with two cradles and three batteries. Some combination of them allowed me to start the flash process.
[Ornate TrueSmart] kuronosan:
Okay, you should be able to flash the 0706 package and the patch to get things booting again.
[Ornate TrueSmart] GooG2e:
Can you post file that helps to quit bootloop pls?

An how I can switch off my watch?
[Ornate TrueSmart] kuronosan:
It's in the second or third post. You hold down the power button to switch it off.
[Ornate TrueSmart] MaloyO:
Well it was looking good...but now I've gone back to square one again. No boot image and will not flash again.

I'll start from scratch again tomorrow. With a bit of guidance, from the top man kuronosan, I am going to bring this TS back to life. ;)
[Ornate TrueSmart] kuronosan:
Walk me through everything you did to get it working, what the result was, and what you did afterwards. Be detailed, include the file names you flashed and the scatter you used to flash it. I don't mind a long post. I read incredibly fast.