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

[Gawis]

I followed instruction and flashed it without any problem on my EU TS 512MB Dev Edition, coming from the previous RSR.
Thanks for all your effort!

Is there any way to get the original RetroSmart watch face without using SWApp Link?

 

[fibroman]

Hi. I have tried to flash this rom and It seemed like it worked. I got the checkmark green box and then I rebooted, but it never left the omate truesmart screen after waiting for over 15 minutes.
So then I pulled battery and tried to enter recovery mode. I hold home key and power key at the same time for about 8 seconds and get the menu that says hit power for recovery. I have tried all possible combinations after this, like let go of home button and keep holding power button, or let go of both buttons and then hit power button, or let go of both buttons and just tap power button, but in each and every case, it just reboots to the omate truesmart logo, and never gets past that!!!
Does anyone have any tips or a tutorial on how to get into recovery mode from this point?
Thanks.

 

[gerhardo]

Does anyone have any tips or a tutorial on how to get into recovery mode from this point?
Thanks.

It seems like the recovery (and more) was not flashed correctly. Flash again (repeat until working, the upgrade is flaky).

 

[fibroman]

It seems like the recovery (and more) was not flashed correctly. Flash again (repeat until working, the upgrade is flaky).

Thanks for the reply. My problem now is that my device is no longer getting recognized in any of the 4 computers that I have tried. I have uninstalled and reinstalled the drivers but the flash tool (3 different versions and the MTK Droid tool won't recognize my device.
I can get into ADB sometimes, but when I issue the command adb reboot recovery, it just goes into a reboot loop about 3 times and then just stays on the Omate logo screen.

 

[gerhardo]

Thanks for the reply. My problem now is that my device is no longer getting recognized in any of the 4 computers that I have tried. I have uninstalled and reinstalled the drivers but the flash tool (3 different versions and the MTK Droid tool won't recognize my device.
I can get into ADB sometimes, but when I issue the command adb reboot recovery, it just goes into a reboot loop about 3 times and then just stays on the Omate logo screen.

Continue flashing. I had to flash over 50 times to get it upgraded. (My device was stuck very early, did not even flash the preloader.)
If you see the device in PC device Manager, you have coomuncation, even if no file transfer. Since you have adb occasionally, even android tries to start.

 

[fibroman]

Thanks for the reply. My problem now is that my device is no longer getting recognized in any of the 4 computers that I have tried. I have uninstalled and reinstalled the drivers but the flash tool (3 different versions and the MTK Droid tool won't recognize my device.
I can get into ADB sometimes, but when I issue the command adb reboot recovery, it just goes into a reboot loop about 3 times and then just stays on the Omate logo screen.

When I am in mtktools, it says -exec '/system/bin/sh'failed: No such file or directory (2)nRet(-1). for all lines.

---------- Post added at 12:04 PM ---------- Previous post was at 11:45 AM ----------

Do you happen to know what the adb commands are to flash back to stock.
maybe that should be my next step so that the device can be recognized again.

 

[gerhardo]

When I am in mtktools, it says -exec '/system/bin/sh'failed: No such file or directory (2)nRet(-1). for all lines.

---------- Post added at 12:04 PM ---------- Previous post was at 11:45 AM ----------

Do you happen to know what the adb commands are to flash back to stock.
maybe that should be my next step so that the device can be recognized again.

You cannot flash with adb, mtktools do not have communication "on the lower level required to flash". If you get into recovery, you can use that. Otherwise you have to use SPFT.
JB->KK requires upgrade once. If that has succeeded, flash KK should work.

Flashing MediaTek devices requires patience. Not recommended for those with a weak heart.

 

[kuronosan]

When I am in mtktools, it says -exec '/system/bin/sh'failed: No such file or directory (2)nRet(-1). for all lines.

---------- Post added at 12:04 PM ---------- Previous post was at 11:45 AM ----------

Do you happen to know what the adb commands are to flash back to stock.
maybe that should be my next step so that the device can be recognized again.

This error means your system image didn't flash properly.

 

[fibroman]

This error means your system image didn't flash properly.

Ok. so how can I reflash it again, even though the device is not getting recognized with the flashtool.
Or is there a way to flash/format it so that I can start from scratch.
Or just get a proper recovery (twrp)etc. on it so I can access the watch again and go from there.

 

[gerhardo]

Ok. so how can I reflash it again, even though the device is not getting recognized with the flashtool.
Or is there a way to flash/format it so that I can start from scratch.
Or just get a proper recovery (twrp)etc. on it so I can access the watch again and go from there.

Pull the battery and flash with SPFT again. Repeat until working. The flashing is seriously flaky.

 

[fibroman]

Pull the battery and flash with SPFT again. Repeat until working. The flashing is seriously flaky.

O.K. so when I try to run the flashtool again, and load the scatter file, it comes up with this error:
Brom Error: S_DL_Load_Region_is _Overlap (5016)

I think I had this same error originally , but after the error it still allowed me to flash it.
the list of files were shown and the android and recovery files were unchecked.
So I clicked them and linked the android to the system.img file from the firmware and linked the recovery to the openrecovery twrp img file.
It allowed me to flash from that point originally and seemed to have been successful based on the green checkmark box at the end of the original flash.
But obviously not since I am still stuck getting no further then the omate logo screen.

 

[Shonky*]

If you're getting the boot logo and you think it flashed properly do a wipe from within recovery.

 

[fibroman]

At this point , I do not think it was actually flashed properly and I can't access recovery because of it I think.

 

[fibroman]

O.K. so when I try to run the flashtool again, and load the scatter file, it comes up with this error:
Brom Error: S_DL_Load_Region_is _Overlap (5016)

I think I had this same error originally , but after the error it still allowed me to flash it.
the list of files were shown and the android and recovery files were unchecked.
So I clicked them and linked the android to the system.img file from the firmware and linked the recovery to the openrecovery twrp img file.
It allowed me to flash from that point originally and seemed to have been successful based on the green checkmark box at the end of the original flash.
But obviously not since I am still stuck getting no further then the omate logo screen.

Is there any alternative firmware that I can use so I wont get the Brom overlap error?

 

[knosalaa]

callisto 300

Upgraded my NA Callisto 300 - Flashing went flowless. The problem I'm having now is:
BT very weak - headset has noise, file transfer do not work
Wi-Fi - weak signal, can't get rid off bogus access point showing error= x10
Battery weaker
no 3G data
I have a simcard in my watch and at first dialer would not come up, with suggestion from here after wiping data in launcher dialer comes up but the problem is that in USA holding dialer "1" key calls your voice mail this no longer works in KK upgrade

How can I correct some other all of these issues?
I know 1st page of this thread has all tools with folder that has needed files - how do I flash NA baseband (assuming NA is for USA carriers)

Please help

 

[Bushrod]

I must be a lucky one as it worked first time for me with SPTool 3.1332.

The only problem I'm seeing is with BT. It's really flaky. When I first boot the phone and the TS and can make a BT tether with no problem. Some random time later is disconnects and I have to reboot them both again. Anyone else seeing this? I have a Nexus 5 on 5.0.1 stock rooted.

I'm also having problems with the latest SWApp Link staying connected. Anyone?

 

[Viperdk81]

Flash Baseband

Hi and thanks for this great and fast rom, but I have a problem flashing new baseband 2100, I got the file from you google drive but have no ide of how to get it to the phone, any help will be much appreciated

And another thing, with this rom the screen use a lot of battery, about 45% of the battery. On 4.2.2 the screen use was only about 3% :/

I installed the rom from windows 10 with SP flash 5.1 to Omate truesmart 1/8 with no problems at all, thanks

 

[steve_neal]

Phone - App isn't installed after reflash to 4.4.2

All seemed to go well - green tick in SPI Flash - Truesmart (1/8 2100) rebooted and I was able to Wipe (there weren't separate Wipe and Factory Reset options that I could see?)

However I get "App isn't installed" when I try and run the Phone app to test the voice calls. I did have a 3UK SIM installed when I re-flashed and see 3G/HSDPA indication. All seems to be well apart from the Phone thing.
I can send SMS messages and can ring the phone and answer the call. I just can't open the app to manually make calls. I must be missing something obvious...

** EDIT - sorry - original forum search didn't find the solution which is to go to Settings->Apps->Launcher and wipe data.
I also have the NVRAM ERR0x10 error so I'll try and resolve that next **

 

[gerhardo]

The only problem I'm seeing is with BT. It's really flaky. When I first boot the phone and the TS and can make a BT tether with no problem. Some random time later is disconnects and I have to reboot them both again. Anyone else seeing this? I have a Nexus 5 on 5.0.1 stock rooted.

I'm also having problems with the latest SWApp Link staying connected. Anyone?

BT was unusable for me with 4.2, works OK in 4.4 (to SGS2 with CM11). Have just briefly tried tethering though, worked fine (I have a SIM with data in the TS).

I do not have a too good experience with SWApp Link, either, cannot blame the app though.
The notifications from my 4.1 work phone are like "2 new messages", but SW App Link presents what it has access to.
But I would like an easier way to deactivate sync. If I start exercising without deactivating SWAL, I get popups and high battery drain. Occasionally problem reconnecting, not much to say.
I doubt I will use SWAL.

Hi and thanks for this great and fast rom, but I have a problem flashing new baseband 2100, I got the file from you google drive but have no ide of how to get it to the phone, any help will be much appreciated

Flashing baseband in EnSec & Operative done with adb, the following should work (the baseband should be unique in 4.2 compared to 4.4.

adb shell mount -o remount,rw /system
adb push .\1900Baseband\modem_1_wg_n.img /system/etc/firmware/modem_1_wg_n.img
adb shell chmod 644 system/etc/firmware/modem_1_wg_n.img
adb reboot

And another thing, with this rom the screen use a lot of battery, about 45% of the battery. On 4.2.2 the screen use was only about 3% :/

This could be presentation only, better in KK. JB presented the apps driving the screen instead.
ART is supposed to be even better in presenting than Dalvik, really the service using Android System is interesting.
(I use Dalvik, Xposed is a requirement.)
Power usage is much improved in KK, MediaTek has maybe learned more than to design chip.

I installed the rom from windows 10 with SP flash 5.1 to Omate truesmart 1/8 with no problems at all, thanks

Maybe half of my first 50 flashes gave an error message, the following 20 (repartitioning) went fine, with exception of one read-back.
Same PC and USB port.

 

[Blufires]

I've tried everything I can think of but I can't get GravityBox to enable swipe down status bar reliably (I've only been able to drag it down once or twice).

I've found a great alternative though. I've just installed NiLS Lockscreen Notifications. It comes with a 2x2 widget that includes a clock and shows notifications. I've disabled the lockscreen/watchface and placed the NiLS widget on my default homescreen. This gives me clock & notifications on my main screen, and turns on the screen when a new notification arrives. After adding some settings switches to the next homescreen over, I don't need a notification bar.