yashsingh1/xdaforums huggingface dataset:
[Ornate TrueSmart] jembot:
Yes i'm aware of the HW and FW discrepancies between batches. Just wondering if there are other compatible custom roms floating around.

Anyway, I was able to root mine though. I guess we'll just have to wait for loki or other devs to step in for the 4th batch 2100.

Will just customize any way I could to suit my needs.
[Ornate TrueSmart] Stu|:
None at the moment, but there might be a patch coming soon to allow us to flash the existing roms.
[Ornate TrueSmart] agaruut:
I still could not fix the missing 1 2 3 buttons. how did u fix? can u explain to me in detail. cant make phone calls. thank you

installed frame work and changed dpi to 90. nothing changed.
[Ornate TrueSmart] kuronosan:
Oh, okay. Guess I won't need to lift a finger here after all.
[Ornate TrueSmart] haybill:
Not sure whether that is correct- since I am also not sure how much input you have with this particular ROM [ do you share any work with Dees Troy??]--and, if so--it would be great if you could help sort out a version of this ROM for the 1 8 2100 device--since this is lacking at the moment.

I realize that a suitable image is required of the device in question--but see that a few folks have offered to submit their firmware images.

We do have Swapp Link which is excellent--but, I hear that this app works even better with Dees Troy's Bluetooth ROM.
[Ornate TrueSmart] trent999:
I am trying to understand better what the situation here is myself. As i understand it, DeesTroy does not have any of the current 9 or 10 different TrueSmart firmware versions. So he relies on testers and codes based on his impressive skills. Awesome. His firmware includes all Loki's EnSec enhancements, I think, including proper rooting with su and no more user-running-as-root-allthetime, plus patches for various Android exploits, plus a number of build.prop edits to improve stuff like battery life. It is NOT Loki's Imperative Operative ROM though, instead it enhances the BT stack in some way I am not clear about, maybe improving stability but not adding missing profiles like for PAN ? Just guessing...

Since Lokifish pulled EnSec though, due to it being impossible to support across the multiple indistinguishable TrueSmart hardware revisions, does this ROM still work applied to for example the most recent batch of 1/8/2100 watches and all.

A summary would be appreciated at this point, since I am getting pretty confused. My TrueSmart is still as shipped a 1/8/1900 from early February. 20140120 firmware I think. I just am real careful with exposing it to nasty stuff outside, in a number of senses, and with what account info to trust it with since it is wide open insecure.
[Ornate TrueSmart] haybill:
I agree-- about the slight confusion regarding al the different iterations of TS firmwares.

I have a 'List 3' shipped Euro 1 8 2100 TS [ I don't have the watch at hand/on my wrist at the moment so I won't try to guess the Firmware version--but, based on other users experiences who had what seemed to be the same version as mine--I finally got Lokifish's method using MTK Tools to flash TWRP Recovery--and then flashed his 'Unified UnRooted 1-8 Secured Tuned Stock ROM', and then followed his advice to gain Root Access using FramaRoot--and that's was about it--I have installed a few Apps--the most important by far being 'Swapp Lin' by [MENTION=334740]cyrilp[/MENTION] [ Cyril Preiss] which has given a whole new meaning to my Omate TS. That's about where I am--I also have Osmart Companion App by Kurt Huwig--although, as yet, I have not really given this a fair shot since I have been more focused on Swapp Link.

That's about it--but it would be great if someone with the knowledge compiled a list/review/ description of all the different firmwares/patches, etc that are floating around--I have quite a few versions that I have downloaded over time from XDA and am getting very confused--I am tempted to delete a bunch and just keep the few ones that I totally sure as to what they are.
[Ornate TrueSmart] yeahimdukenukem:
Would you be so kind and reupload Lokifishs stuff? He has removed it from his thread for a unknown reason.
[Ornate TrueSmart] trent999:
Lokifish made his reasons clear. His work and collection of tools were being hosted via storage donated for his use as a respected XDA developer. Due to his frustration resulting from Omate's multiple unannounced hardware revisions for the TrueSmarts, at least two this month, and other longstanding issues with Omate, Umeox, and MTK, Lokifish has left Android development altogether. Partially this is because some of his released work was soft-bricking at least the last two watch hardware revisions (3rd and 4th list watches) and these were impossible for him to code for to tell apart.

Since Lokifish is no longer an Android developer, hr feels he must not use the donated storage anymore and has removed the hosted files. This is a seriously major loss to us with TrueSmarts and to MTK Android devices in general. I hold this against LLPen much more than any of his many other broken commitments.
[Ornate TrueSmart] haybill:
http://xdaforums.com/showpost.php?p=52624906&postcount=85&nocache=1&z=1048681909725784

Try this.

And 'Thank' [MENTION=961968]thermalboyz[/MENTION]

P.S. Don't blame me if your device is incompatible and it get's a problem--I don't know your version, nor that of Thermalboyz--I don't have the firmware on my PC anymore--but the files that I flashed have worked fine--but mine was a version from List 3--and before the latest firmware alterations.

Check, check and re-check before flashing.
[Ornate TrueSmart] kuronosan:
Unless your watch is from mid-May you have no chance of bricking your device. Your sensors may not work, but that's about it.
[Ornate TrueSmart] funky0308:
Post screenshoot from "about device" and it'll be easier to tell which firmware you may flash.

[MENTION=912474]Dees_Troy[/MENTION]

Hi mate...

I'm starting to work on one project and I need one thing from you....

If you know, of course...

You noticed where are the changes in firmware for sensors between 512 and 1/8 devices?

OwatchON was working on earlier models, so I'm trying to enable it again in new firmware.

I really believe we should decide what to use...

It's draining battery, that's for sure but smartwatch without that function isn't smart at all...

Tnx for help mate..
[Ornate TrueSmart] yeahimdukenukem:
The firmware is from March. So it is safe to install it?

---------- Post added at 09:34 AM ---------- Previous post was at 09:26 AM ----------

Well, ok.

But isn't bad device support by the manufacturer THE reason why custom Android development even exists? THE reason why great projects like Cyanogenmod even started?

P.S.: We should end this here, cause it's off-topic in this thread...
[Ornate TrueSmart] haybill:
"But isn't bad device support by the manufacturer THE reason why custom Android development even exists?"

That's a fair point.
[Ornate TrueSmart] trent999:
Custom Android development exists because Android is Open Source. In MTK's case (and not just for the TrueSmarts) there is a real problem with compiling even the stock firmwares from the supplied source, and so there is little custom Android development.
[Ornate TrueSmart] jeremy.chan:
is this also abandoned already? OP has not replied in a long time..

Looks like we're all out of devs. Yay Omate.
[Ornate TrueSmart] trent999:
So many things on the TrueSmarts were broken because of mistakes and incompetence in the firmwares, none ever corrected, that a corrected and rebuilt firmware is essential as a starting point for further development. This can't be done currently, other than by MTK and maybe Umeox, and they are showing no desire to even try.

It is possible that in the near future a set of source files will be available that can actually be used to compile a bootable firmware, at least for some hardware varients of the TS. If so, we will be able to move forward - if any Dev will be willing still to touch the device after the way some previous devs have been disrespected.
[Ornate TrueSmart] funky0308:
Unfortunately I think, that won't happen...

Everyone is leaving Omate TS dev and there's no future...

Only and if Omate release new, better and polished firmware for TS thete could be some dev.and new things...

As I already said, I'm out and I didn't even started to work for TS, Loki is out and we really need someone like him.

Obviously, Dees_Troy is out as well...

No sign of him on his thread..

All TS users (including me) could be happy to have [MENTION=334740]cyrilp[/MENTION], just imagine TS without swapplink?!?

If you ate following G+ you could see Laurent LP arguing and insulting developers and supporters so there won't be new developers for sure, when they see that...

XDA support is mainly over...

Too bad, we could have fun with it, if we have sources and support from Omate...
[Ornate TrueSmart] haybill:
Is that really the case--@funky0308--that LLP has been arguing online with Developers?? On which Forum, Google Plus? I haven't been reading the Omate section of G+ for quite some time so I am out of touch--but, if what you say is true,[and I am sad to say that it might well be] then it is truly disgusting.

That idiot is so full of his own 'imagined' self-importance that he has already ruined what might have been a good device.

I managed to download and flash a suitable version of Lokifish's Secure Patched Stock ROM before it was disappeared and Rooted it with FramaRoot, now with Cyrilp's SwappLink it's a usable device but without future development it's days are probably numbered.

Selling the Omate TS is sadly probably the only answer if there are no Devs willing to work on it--that being said, mine has been advertised locally for 3 weeks and I have not had 1 single response.
[Ornate TrueSmart] funky0308:
Yeah buddy, unfortunately it's true...

https://plus.google.com/app/basic/stream/z130u5by2nb2tzgvt221fxta2relgnxoi04

(and this is only the tip of the iceberg)

I'm totally agree with you...

When you set up your device it's actually not bad, at all...

But we need new and better firmware, maybe even 4.3...

We need new OwatchON app, new launcher and new systemUI which could show statusbar in all apps and screens.

Back to argue subject - it's actually not important who is right there but I really believe LLP shouldn't do something like that, he is CEO for a love of God....

Just imagine Bill Gates, Wozniack (if I spelled that well) or anyone important in a company to do something like LLP did...

When you lose developers support and dev were heart of your company (because you have half finished firmware) your product is doomed...
[Ornate TrueSmart] trent999:
Given that, according to the Master of Time Ortiz, the sources LLPen just completed uploading are not going to be compilable into a bootable firmware without a lot of additional work, I think we can all just mark the Omate TrueSmart saga as over and done with at this point.

In the future I will avoid devices connected with Omate, Umeox, and especially MTK.

And Evercross... :)
[Ornate TrueSmart] -Android Freak-:
I tried to flash this on my 1/8 2100MHz version. It's now totally worthless and I can't get the watch to flash anything anymore.

Anyone succeded in reviving the device from not being "flashable" with flash-tool?

Edit: Sorry, I didn't flash this one. It was TWRP I tried to flash. Either way the watch is dead.
[Ornate TrueSmart] funky0308:
Don't get...

Why did you do that?

It's clearly said that it's not compatible with 1/8 2100 devices...

If you can access recovery or adb then your Truesmart adventure is over.

There's no way to revive device after flashing wrong kernel/firmware.

If you tried to flash ROM without kernel (deleting boot.img from ZIP) You'll probably get same results but you would (most likely) retain recovery so you could flash 2100 ROM or access ADB...
[Ornate TrueSmart] trent999:
Yes there is a way ! Using the MTK tools you can reflash your original firmware if you can find an exact copy of your version. Be sure to back up your IMEI's first, using the tools, or you CAN permanently lose them. Guides are available here on XDA, but I am going kayaking so best to look around carefully yourselves.
[Ornate TrueSmart] -Android Freak-:
I thought MTK required ADB? Does it not? MTKDroid doesn't detect my watch...

It shows up with flash tool but as soon as I try to flash my old backup files it disconnects and won't start flashing. :(

---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------

Sorry, my bad. I didn't flash this one... it was TWRP that I tried to flash. Also this was before it was known that Omate had changed the hardware.
[Ornate TrueSmart] funky0308:
Of course it's using adb, don't know what this guy is saying....

Mtktool is just a shell.
[Ornate TrueSmart] kuronosan:
No it isn't. Geez.
[Ornate TrueSmart] trent999:
Kuronosan, I probably got something wrong with my attempt to help, named the tool wrong or something, was generally confused and confusing. Would you please help me by straightening things out. I am sorry - I know I shouldn't post advice I am not clear on myself.

I do know the TrueSmart can be recovered at least. I also know that clear steps on how are available on XDA. I am not sure where though, which thread, or even if the thread is still up. Things have been changing a lot in our community recently and my TrueSmart is not currently available to me.
[Ornate TrueSmart] kuronosan:
SPFT will fix his unit. Don't worry, I'm not chastising you... Just correcting him. :p
[Ornate TrueSmart] tshoulihane:
Providing you have the right images, this device is very hard to brick. SP Flash Tools is what you need.
[Ornate TrueSmart] death_entry:
Doh glad Id read the instructions id been looking forward to getting BT Tethethering working... I have an EU model, how do I get you the boot.img thingy?? Anyway would it be possible to get the tethering on the Loki Firmware? I flashed it but it won't see my phone's bluetooth internet :( boohooo
[Ornate TrueSmart] -Android Freak-:
Hey,

Yeah, this thing is still responding when connecting it to the PC with SP Flash Tool... But somehow it gets disconnected after 6 seconds. (?) I donät know why... It' won't flash my backup or a backup I got from someone on XDA.

I downloaded newest SP Flash Tool and restore my old backup from scatter file... and i get this error...

Any ideas what's wrong?

Thank you for being so helpful! :)
[Ornate TrueSmart] trent999:
The reason for that is that the Bluetooth stack Omate supplied does not have a functional PAN profile, I heard. Lokifish could not write one without more information nor the ability to recompile the firmware with the new BT profile in it.

I am not sure how the BT ROM was created and what it fixes exactly, at what cost if any.
[Ornate TrueSmart] tshoulihane:
Sorry - can't help there. Haven't tried this part. I would guess your scatter file doesn't match the hardware, or the boot.img is wrong (so RAM is not correctly initialised???)
[Ornate TrueSmart] kuronosan:
I know exactly what's wrong.
[Ornate TrueSmart] funky0308:
You tried with AllTools/MTKTools?

Try flashing firmware with that flashing tool.

If you still have that problem, try to flash only recovery image.

If you succeed, restart to recovery and flash ROM from there...
[Ornate TrueSmart] -Android Freak-:
Yeas, I've tried that too, and since the watch won't boot I can't get ADB to work, which I believe is required for MTKdroid. Either way that won't work neither. :(
[Ornate TrueSmart] funky0308:
Yeah...that's the main problem.

When you stuck with a soft bricked device you can access it via adb/fastboot and similar tools but if you have hard bricked device there's nothing you can do...

I understood that your device boot for a six seconds and you have that time to flash img but, as I said at the beginning - if you don't get detection by PC then there's no help for it...

Sorry mate....that's terrible
[Ornate TrueSmart] kuronosan:
Do you have access to chrome remote? I can fix it for you.
[Ornate TrueSmart] -Android Freak-:
That's very kind, but, no, i don't have access to chrome remote. If you know what's wrong would you maybe help me and tell me?

Thank you for your help! :)
[Ornate TrueSmart] kuronosan:
When you plug your watch in while powered off, check device manager. Tell me if anything appears. I'll go from there.

Need to know what firmware you had and what firmware you tried to install.
[Ornate TrueSmart] -Android Freak-:
My watch is from the 4th shipping list and it's a 1/8 2100MHz.

I switched computer (windows 7 64bit).. and the Mediatek COM5 port seems to work here, by not disconnecting and reconnecting all the time.

After a battery pull, this device shows up.

And the Mediatek COM port correctly works in SP Flash Tool.

So when I click "download" in SP Flash Tool it all works until I receive a DRAM error when trying to reflash the backup I made.

:(

Thank you for your continued help! I really appreciate it. :good:
[Ornate TrueSmart] funky0308:
Are you trying to restore your backup or someone else?

Path of scatter file is kinda idd to me, that's why I asked..
[Ornate TrueSmart] kuronosan:
When did you receive your watch?
[Ornate TrueSmart] -Android Freak-:
May 21st...

---------- Post added at 10:13 PM ---------- Previous post was at 10:11 PM ----------

Now that you mention it... This might be a backup I received from someone here on XDA.

I'll try with my own scatter file and backup files... Don't know what the difference would be since they were (supposedly) from the same batch... But can't hurt trying. :confused:

Edit 1:

Ok, tried my own backup now... and got the same error...

:(

Searching the web I found this quote:"That error because flashing wrong preloader and dsp_bl. You can use preloader and dsp_bl from mito A300. I Successfull solve that error and unbrick my Mito T720." -This was regarding another MTK device but maybe this is helpful? Source:http://xdaforums.com/showthread.php?t=2580150

Edit 2:

Ok, I tried removing the battery completely when doing the flash again. and i got EXACTLY the same error... Could this be a battery issue? I charged the battery in an external charger (slowly) until it was 4.2 Volt.

Edit 3:

Ok, I tried uninstalling drivers with usbdeview-x64 and restarted PC. removed battery, and connected watch to PC. Drivers installed just fine. tried to flash my backup with SP Flash Tools, same error.

Tried again with fully charged battery, and no SD-card = same result. - "BROM ERROR:S_DL_GET_DRAM_SETTINGS_FAIL_(5054) [EMI] Obtain DRAM Failed! "
[Ornate TrueSmart] Aerox912:
There are multiple thing going wrong Android Freak.

First of all, the backup you are trying to restore is not complete judging from the screenshot you posted of your SP Flash tool. The preloader is missing in your scatter file, so thats why you get the first error.

Start by opening MTKdroid tools and on the backup restore tab, choose prepare blocks for flashing. It will create a folder called Files for flashtools inside your backup folder. Use only the scatter file inside that folder. You will notice there is a preloader.bin inside there and in the original backup folder there is a preloader_and_dsp file that is not prepared yet. So after you prepared your bakcup try again.

Second thing i notice is that you are using Mediatek VCOM driver. My windows 8.1 also picked that one, but thats not the right one.

After you connect your omate without doing anything else in SP flash tools, check device manager. After some seconds a unknown device popped up in my device manager, i don't know if this was after i pressed download in SP flash tools actually. But when that unknown device pops up, manually assign it to the preloader VCOM driver. Then your good to go
[Ornate TrueSmart] -Android Freak-:
Thank you Aerox! I will try that tomorrow. Sounds like you´re on to something!

I´ll report back tomorrow after work. :)
[Ornate TrueSmart] Aerox912:
Hope this will fix your omate, this is what happened to me last saturday with exactly the same errors as you and also the non functioning Mediatek vcom driver. It just hangs at download DA 100% after preparing the backup and trying to flash it so thats when i found out the driver thing. Took me 4 hours to figure it out :p
[Ornate TrueSmart] kuronosan:
That's what I was going to advise. The drivers are fickle and sometimes installing them again will work. These devices really are screwed up sometimes.

Your scatter file is definitely wrong for your device. The DRAM error is because the eMMC partition doesn't match scatter file.

You'll need to format it and then flash with the proper scatter, from someone who had the same model. Then you can use your backup files to flash.
[Ornate TrueSmart] -Android Freak-:
Hello again,

I just had to try before going to work today...

I have rebuilt the scatter file and it created a folder called: !Files_to_FlashTool. Preloader is now checked in SP Flash Tool.

But I can't get the computer to choose any other driver. I tried removing it dozens of times and manually pointing it to the folder with the drivers that came with the "AllTools"-package. But it just will not change from Mediatek VCOM to anythiing else like the "preloader VCOM". I can't see it at all...

When manually pointing the device manager to the I can choose "I have a disk" and I can see something called gadget serial.. but that wont work either.

Now I hear it connect and disconnect all the time... This is driving me nuts! :p:eek::silly:

---------- Post added at 07:33 AM ---------- Previous post was at 07:21 AM ----------

Thanks. I fixed the scatter file... I think...

But the driver is all wrong apparently... I don't know how to get the computer to choose "preloader driver"..
[Ornate TrueSmart] -Android Freak-:
Ok, I solved the driver error by downloading a driver from this site:

http://www.blog-android.com/general/vcom/

But now I have a new error.... HALP! I'm getting closer though... :D:cyclops:

EDIT 1:

SUCCESS!!!! Ok, I flashed it successfully now. The trick was installing the new driver manually as shown above and choosing Mediatek DA driver WITHOUT BATTERY.

THEN... after the driver installed, remove device... put the battery back in th ewatch, and auto format the drive with SP Flash Tool...WITH BATTERY.

Then flash the scatterfile WITH the battery inside... SUCCESS!

It now boots until the logo... Now I guess my IMEI is wrong or something? But at least it boots now!

YAY!!! :D :D :) :) :laugh::highfive::good:
[HTC One Mini] mhammadakkad:
i have 3 questions

1 the FUU is a tool that i can use to flash every Rom that suits my device ?

2 if i flashed a rom will i lose all my data in the Storage?

and finally i updated my device to kitkat and i hate the sound of it it was very good and after update its too bad i have posted this but i got no answer

http://xdaforums.com/showthread.php?t=2694005

so i'm thinking to get back to JB what is the best way to fix sound or to get back to JB ??

sorry of bad english :)

and thanks..
[HTC One Mini] AnGrY sCoTsMaN:
1, simply put, NO!. FUU is a utility to update firmware eg.. OTA updates (if you are unable to update normally)

To flash any rom you need....unlocked bootloader, custom recovery (to gain root) and maybe s-off depending on which rom you choose to flash and depending on which hboot

you have (all is explained in these threads)

2, not if the data is stored on /sdcard and you only factory reset which wipes data, dalvik and cache (not internal memory eg../sdcard)

3, if you are rooted, install xposed framework. then install 30 steps volume module or search xda for sound mods compatible with your rom.

hope this helps ( all the info you need is on here, so just search the threads)

cheers
[Android Apps and Games] gamazing:
Hello everyone!

If you enjoyed flappy bird, you probably would enjoy this brand new game!

Easy instructons, fancy gameplay and much more!

Check out the video!

youtube.com/watch?v=QWmG1yZA5Sg

Screenshots:

Instructions: left- or right side touch will rotate the arrow, avoid the schrinking shapes and get the highest score possible!

Free download:

Android:

play.google.com/store/apps/details?id=com.facebook.DodgeIt"