[ROM][KK][4.4.2][STOCK]Omate TrueSmart IRONMAN Firmware

[gerhardo]

It's not bricked "for sure"

Do you have the driver installed for the Download Agent. After plugging in, a virtual com port is created and the Download Agent is loaded, this then creates a different virtual COM port with different USB ID and different drivers (or at least the same with the different vendor and/or product IDs) IIRC. It seems you have the first stage com port working. Have you installed the dpinst.exe/DPInst64.exe drivers? Try re-installing them (run the .exe as administrator manually - it doesn't seem smart enough to do it on it's own).

Take a look at Device Manager for unknown devices when it stops.

Thanks for helping

Reinstalled VCOM drivers (many times), the TS is seen as "Mediatek USB" in Device Manager - on for a minute or so after connecting, then off.
(And I flashed several times before getting into this state.)
SPFT sees the TS when starting, can download DA (says 100%), but just do not continue after that.
After that the device is Unknown in Device Manager.
So sure, it seems like the port presents itself in a way so drivers can no longer be loaded, but what more than VCOM is needed then?

 

[Shonky*]

Thanks for helping

Reinstalled VCOM drivers (many times), the TS is seen as "Mediatek USB" in Device Manager - on for a minute or so after connecting, then off.
(And I flashed several times before getting into this state.)
SPFT sees the TS when starting, can download DA (says 100%), but just do not continue after that.
After that the device is Unknown in Device Manager.
So sure, it seems like the port presents itself in a way so drivers can no longer be loaded, but what more than VCOM is needed then?

There are plenty of different versions/brands of virtual com ports so just because the first one works doesn't mean the second one will. Go to the Details tab and then Hardware IDs. That will tell you the device VID/PID for sure.

The driver *should* be in the DPinst(64).exe files from memory which are installed by just executing the .exe as Administrator. The "0 Needed Files" directory has two sets of drivers in it I think.

 

[bienjamu]

might help someone

hi guys,

i had a few issues installing KK but got there in the end, managed to get it into a state where it wouldn't boot and after that i seemed to have driver issues for the most part. windows kept looking for drivers for "Alcatel T Single RNDIS Interface" but failed to download them, so i googled it and used the link to the "PC suite software" in the reply here:
answers.microsoft.com/en-us/windows/forum/windows_7-hardware/alcatel-t-single-rndis-interface-2-driver-problem/396bb91f-d85c-438a-a381-45ce3f3fad07
(haven't been a member long enough to post a proper link, sorry)

after that, and lots of plugging it into different ports to get it to recognise the device, i got it to work as per the instructions.
(except i ran a format and download first, followed by upgrade firmware)


can't be certain the alcatel driver was what worked for me as i was trying all sorts of combinations. but might be worth someone else testing if you are also having usb driver issues.

thanks for the kk.

 

[kuronosan]

Sure.



I am not worried, this unit was semibricked already (no mic and no GPS, bad BT).
(One usage is to get Swipe Status bar working in KK.)
One kind of bricking is to run out of battery.

I do not get any response from SPFT unless downloading. When downloading, I get "Mediatek USB" directly, but nothing more, so for sure it is "kind of hard" bricked...

Screenshot after trying to flash preloader from the backup prior to the upgrade. Same result whatever is downloaded and for Format+Download.
No settings in SPFT is changed from what I know, I have tried enabling "DA DL with checksum" too.

Thanks for helping

Reinstalled VCOM drivers (many times), the TS is seen as "Mediatek USB" in Device Manager - on for a minute or so after connecting, then off.
(And I flashed several times before getting into this state.)
SPFT sees the TS when starting, can download DA (says 100%), but just do not continue after that.
After that the device is Unknown in Device Manager.
So sure, it seems like the port presents itself in a way so drivers can no longer be loaded, but what more than VCOM is needed then?

This happens when your preloader acts wonky due to a bad flash. What I do is grab the stock scatter file, flash the preloader, and format and download the stock firmware.

I've had to use a different computer when this happens. Your computer basically looks at the device, says "oh I know you", while the flash tool says "hey have you seen this device". The computer says "yes!" and then proceeds to waste the flash tool's time by standing around not saying where.

Sometimes you just have to ask another computer.

 

[kuronosan]

hi guys,

i had a few issues installing KK but got there in the end, managed to get it into a state where it wouldn't boot and after that i seemed to have driver issues for the most part. windows kept looking for drivers for "Alcatel T Single RNDIS Interface" but failed to download them, so i googled it and used the link to the "PC suite software" in the reply here:
answers.microsoft.com/en-us/windows/forum/windows_7-hardware/alcatel-t-single-rndis-interface-2-driver-problem/396bb91f-d85c-438a-a381-45ce3f3fad07
(haven't been a member long enough to post a proper link, sorry)

after that, and lots of plugging it into different ports to get it to recognise the device, i got it to work as per the instructions.
(except i ran a format and download first, followed by upgrade firmware)


can't be certain the alcatel driver was what worked for me as i was trying all sorts of combinations. but might be worth someone else testing if you are also having usb driver issues.

thanks for the kk.

Alcatel is the default driver assigned to the prekernel modem interface by windows.

When an MTK device loads it has three stages:

Modem (deep, deep layer only accessible with tools)
Preloader (flash tool talks to this)
LK (your bootloader)

There is one other mode but it's only accessible with a special box.

When the preloader fails to hook it defaults to modem. When you don't have the driver installed it defaults to Alcatel.

 

[LaDamian]

This happens when your preloader acts wonky due to a bad flash. What I do is grab the stock scatter file, flash the preloader, and format and download the stock firmware.

I've had to use a different computer when this happens. Your computer basically looks at the device, says "oh I know you", while the flash tool says "hey have you seen this device". The computer says "yes!" and then proceeds to waste the flash tool's time by standing around not saying where.

Sometimes you just have to ask another computer.

I tried to describe this action, but it wasn't as clear as what you've posted here. I think this is why some people, myself included, have had luck using a different set of flash tools. Using a different version of the flash tools has a similar effect to switching computers without needing a second computer.

 

[stealph]

Watch Manufacturer - Omate TS-1/2100MHz 1GB/8GB Extreme Edition
Date Received - Post May
Last Known Firmware - EU Ensec Stock 0706
Case Material - Aluminium
Used MTK Droid tools to make backup.
Flashed - Omate 1-8-2100 TrueSmart 20140328 stock rom, success! using SP flashtool v5.1352.01. (no boot from this but might have put everything back in place) Link to ROM https://www.dropbox.com/sh/2auyzxge37d9gao/AAB0IffB6LTdeI0Lzq3dNA3qa?dl=0
Flashed - [ROM][KK][4.4.2][STOCK]Omate TrueSmart IRONMAN Firmware - Success!
Flashed - Chainfire's SuperSU using TWRP.
Used MTK Droid tools to restore IMEI from backup.
Result - Success! KK 4.4.2 on my wrist.
Not tested GPS yet.
Thanks Kuronosan and everyone else who made this possible.

 

[psnijjar]

Watch Manufacturer - Omate TS-1/2100MHz 1GB/8GB Extreme Edition
Date Received - Post May
Last Known Firmware - EU Ensec Stock 0706
Case Material - Aluminium
Used MTK Droid tools to make backup.
Flashed - Omate 1-8-2100 TrueSmart 20140328 stock rom, success! using SP flashtool v5.1352.01. (no boot from this but might have put everything back in place)
Flashed - [ROM][KK][4.4.2][STOCK]Omate TrueSmart IRONMAN Firmware - Success!
Flashed - Chainfire's SuperSU using TWRP.
Used MTK Droid tools to restore IMEI from backup.
Result - Success! KK 4.4.2 on my wrist.
Not tested GPS yet.
Thanks Kuronosan and everyone else who made this possible.

heyi mate could please send me link for stock rom i need it please

 

[stealph]

heyi mate could please send me link for stock rom i need it please

Sorry I don't have a link, it's on my PC.
Uploading to Dropbox will provide link when I find out how to share it

 

[psnijjar]

Sorry I don't have a link, it's on my PC.

could please upload it i have downloaded many rom but none of them seems working.
would be very grateful of u if u upload it please .

---------- Post added at 07:35 AM ---------- Previous post was at 07:24 AM ----------

@kuronosan
please could you send me a link for stock rom for truesmart
Watch Manufacturer - Omate TS-1/2100MHz 1GB/8GB Extreme Edition
Date Received - Post May
Last Known Firmware - stock rooted
Case Material - Aluminium
thank you in advance

 

[stealph]

could please upload it i have downloaded many rom but none of them seems working.
would be very grateful of u if u upload it please .
Uploading to Dropbox will provide link when I find out how to share it

---------- Post added at 07:35 AM ---------- Previous post was at 07:24 AM ----------


@kuronosan
please could you send me a link for stock rom for truesmart
Watch Manufacturer - Omate TS-1/2100MHz 1GB/8GB Extreme Edition
Date Received - Post May
Last Known Firmware - stock rooted
Case Material - Aluminium
thank you in advance

Uploading to Dropbox will provide link when I find out how to share it
Link in original post (this is all new to me so bear with me)

 

[psnijjar]

Uploading to Dropbox will provide link when I find out how to share it
Link in original post (this is all new to me so bear with me)

thank you so much will download n flash n will tell if i gety ts to get life again

 

[psnijjar]

error 4032

somebody please help get rid of error 4032
brom error: s_ft_enable_dram_fail(4032)
i have tried almost everything i could find on internet
i have changed usb cables, cradles, removing battery, trying on different pc , tried different roms and stock roms, tried uninstalling alactel drivers, tried uninstalling mtk vcom drivers and installing , tried different versions of sp flashtool, tried flashing preloader that too didnt work it also gives 4032 error
m almost giving up please someone tell me m doing something wrong or wat to do. hoping someone for help m even open to ship watch if someone can fix it or open to use chrome remote desktop extensions .
my watch is
Watch Manufacturer - Omate TS-1/2100MHz 1GB/8GB Extreme Edition
Date Received - Post May
Last Known Firmware - stock rooted
Case Material - Aluminium
dan @kuronosan ???? help here

 

[kuronosan]

DRAM fail means it didn't read the scatter correctly and couldn't initialize the chip. What happens when you format + download?

Get the stock stuff here:
https://drive.google.com/folder/d/0Bz7sBdJpIWEgMjdPRkJ3T3BQdFE/edit

Or the full backup here:
https://drive.google.com/folder/d/0Bz7sBdJpIWEgSTYzWGpIdXhIQjA/edit

 

[psnijjar]

DRAM fail means it didn't read the scatter correctly and couldn't initialize the chip. What happens when you format + download?

Get the stock stuff here:
https://drive.google.com/folder/d/0Bz7sBdJpIWEgMjdPRkJ3T3BQdFE/edit

Or the full backup here:
https://drive.google.com/folder/d/0Bz7sBdJpIWEgSTYzWGpIdXhIQjA/edit

i get same error after 1:50 seconds

 

[burlyoaf]

I'm finding I'm getting better GPS reception when using the original Unova IRONMAN ROM. The signal is still fairly weak (standing outside I get about 4-5 satellites receiving) but compared to this this ROM where it takes much longer to get a lock if at all. Using GPSTest from the Android store.

Any ideas why that might be?

Not working for me. I got --- ERROR : pttycmd1 device NOT found!

The FIX !!!
Turned out, the problem is the secro.img. Flashing with the one from this KK rom erase all things related to baseband.
So, here are 2 options fixes if you don't have baseband after flashing, assumed you already rooted.
1. Try to restore your NVRAM backup from your previous ROM with MTK Droid tools. If you get "can't found pttycmd1" error then do step 2.
2. Open SP flash tool with scatter from the the KK rom and ONLY select PRELOADER & SEC_RO. The preloader should use the KK rom and the sec_ro you should use your previous working rom (that you back up before flashing KK with MTK droid).

Now, my TS-1 is showing 3G and the GPS is working fine. Perfect!

This worked a treat thankyou!

 

[Stu|]

Finally got round to upgrading my watch and it's working perfectly!

Do NOT try to flash this from Windows 10, or from a VM inside Windows 10. It just won't work at all. I had to use my work Windows 7 laptop to get it done. Don't waste your time like I did

 

[jhax01]

I think that number is a lot higher actually..... but, 42 is quite fitting as this is now the answer to the ultimate question...

It has been an exciting couple of days testing and flashing.

Despite all the trial and errors, not once did the watch become unrecoverable.

If you load Google Now Launcher and the latest Google Search APK (and setting it up properly) you can use the "Ok Google" feature from the lock menu as well as in the OS.

I stopped wearing my LG G and am now wearing the TS daily....

Kudos for all the hard work!

I knew there was light at the end of the tunnel!

D.

How are you getting the Google now launcher working? Are you changing the DPI, using xposed or taking other steps? Google now is my favorite launcher but I'm having a heck of a time getting it working... I'd appreciate any tips you have, thanks!

 

[GADGTGUY]

I didn't do anything special actually.

I just installed it from the play store and activated it.

I love having it on the watch.... it's almost the perfect launcher for the watch.

D.

 

[jhax01]

I didn't do anything special actually.

I just installed it from the play store and activated it.

I love having it on the watch.... it's almost the perfect launcher for the watch.

D.

Really? All that comes up for me is a welcome screen that doesn't let me select anything or get past it. I even tried hooking up a Bluetooth keyboard to see if that would let me select whatever it is on the screen that is halting progress. Guess I'll try uninstalling and starting over.