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

[kuronosan]

You must flash the stock firmware on that one first, then upgrade.

 

[kuronosan]

heyi mate a few days back my ts fell n it hit hard on home button n from there on home button is not functioning at all. is there any way to fix home button ?? i use software button but to reboot into recovery i need home button . i can reboot into recovery via reboot menu though but as stated in ur instructions need to press both buttons to reach recovery to wipe data.
since my home button is non functional should i proceed with kitkat update or not? please let me know if any way to update my ts to kitkat really waiting for kitkat.

You can reboot into recovery over adb.

 

[burlyoaf]

is that the same SuperSU that MTK installs?

Didn't have much luck with that

 

[kuronosan]

Uh, no.

 

[Shonky*]

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?

 

[kuronosan]

Might be a placebo, considering this is the original ROM.

 

[Shonky*]

Might be a placebo, considering this is the original ROM.

So you're saying that's basically impossible? It seems fairly real but I haven't gone back and forth enough to check.

I note that the original Unova ROM is dated August 2014 and the kernel is 22nd August 2014 looking at it now. The kernel in your TS version is dated October 2014. Where did it come from?

 

[kuronosan]

It came from the S8, which uses the same sensors.

 

[psnijjar]

ts not detected nor can be turned on

i tried to flash kk firware gave an error after that neither ts boot or screen lights or any vibrations nor its detected by driodtools or sp flashtool. only pc sound is heard at interval as connected and disconnected
urgent help please

 

[Shonky*]

Restore your backup. Might need to pull the battery and then plug in after pressing download the same as when installing this ROM.

Requesting urgent help with little more than doesn't work isn't going to help.

Can I stress to others reading this that this is not a trivial process and if you require it to work "urgently" do not flash an early first pass like this. Likewise if you're not really sure what you're doing (even though kuronosan's instructions are quite detailed).

---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------

It came from the S8, which uses the same sensors.

The kernel included with the ZGPAX S8 image in the other thread is 8th December but built by the same user as the October one in your ROM ([email protected])

 

[kuronosan]

It may be a later build than what I have. I'll look at it.

 

[Shonky*]

It may be a later build than what I have. I'll look at it.

My specific December date might be wrong but it was definitely December vs October (can't check until tomorrow).

Do you have any idea who [email protected] might be? I realise it's just a username @ machine_name but you never know.

 

[Ierlanfdan]

8th of December is confirmed. At least my windows is showing that as last modified date.

 

[kuronosan]

Alright. Let me check out that kernel.

 

[LaDamian]

I'm pretty sure I'm some kind of brick. I hope it is the soft kind... As it stands now, my watch won't even boot to the splash screen. I had it booting to that for a while via MTKDroidTool, but now the watch is totally black. The MTK droid tool will not even see the watch. Explanation:

I tried to flash the upgrade, but the part about the preloader was not included in the OP. I think I messed that up. I got a BROM error.

I'm still not sure where system.img goes. I added it to the box that said "android" because it was the only box that wasn't populated, and it seemed to make some sense. Please clarify where that goes.

I realize that you know this hardware pretty well, but please update the OP. I think it is lacking some key steps. This flash tool is very confusing. I have a full backup, but I feel like there isn't a proper way to even recover my watch at the moment.

Thanks

 

[Lokifish Marz]

My video walk through of how to flash using SPTools is still on my Youtube channel.

 

[kuronosan]

What BROM error did you get? And, had you followed my instructions, you would know that the correct preloader is included in my firmware.

So no, your watch isn't bricked if this is what you flashed. It's in an off state. Pull your battery and try again.

I also mentioned that you should ask questions before doing anything you aren't comfortable with.

 

[LaDamian]

What BROM error did you get? And, had you followed my instructions, you would know that the correct preloader is included in my firmware.

So no, your watch isn't bricked if this is what you flashed. It's in an off state. Pull your battery and try again.

I also mentioned that you should ask questions before doing anything you aren't comfortable with.

I don't remember the BROM error. That was back when I could still reboot the watch via adb. At that point I tried to restore a backup that I made using the MTK tool. The watch seems completely powered off now after a few reboots via adb. I can't get it to do anything.

I will try to pull the battery tomorrow if all else fails. I was really hoping not to have to open the watch. I should have asked about the system.img before I flashed because I have no idea where that is supposed to go. I assumed it would be the only remaining empty option "ANDROID". Was this not correct?

Also, is it possible that I just need to re install my drivers? I keep getting a "USB Device Not Recognized" error when trying to upgrade.

Thanks and sorry if the description is confusing. I seem to have had odd issues with your previous rom as well.

 

[kuronosan]

That requires a format and install of stock firmware to fix. Just pull the battery and you'll be fine.

 

[gerhardo]

My TS is not starting the upgrade, "Download DA" hangs for minutes. After starting I have to pull the battery to get the PC to recognize the unit again.
No response on power, but the device manager sees "MediaTek" (after pulling battery at least, when tring to download it changes to Unknown device) so the preloader does seem to work.
Any hints?

I have tried SPFT 3 too, same behavior.
(Of course tried reinstall VCOM drivers, other USB ports but not another computer.)
(slightly more info in the original post.)
Will need to charge the battery somehow....