[ROM][JB][4.2.2] 07.06 EnSec STOCK Secure + Root

[kuronosan]

Because the new boot.IMG is for a PCB with different modules loaded. It doesn't boot on older units.

 

[sauliux]

but it did boot after all...

 

[aeron16]

Dan the man - I upgraded mine which was EU 1/8GB on 0318 Unified stock ROM to the 0706 Ensec version yesterday. All working well now.. Battery seems slightly improved, lag seems lesser plus GPS lock is much faster. Thanks for helping to keep Loki's invaluable work going!

EDIT: Saw your earlier comments on the Camera Patcher script!

 

[peacey3]

Does anyone have a scatter file for 512/4 2100Mhz or 1/8 1900MHz

Thanks

 

[nrseife]

I just realized my used one that ai got a few days ago has the ensec 20140427 V2.... is this good enough (I.e., safe; battery performance etc seems ok)...does not seem to be rooted?

Sent from my GT-N5110 using xda premium

 

[zippiz]

Hello Kuronosan,

I received my TS in late July and it's the alumi version. My firmware is 20140513. I followed your instruction on page 1 of this thread and:

1. flash the firmware " TS-EU-0706-May_Shipment".
2. After flashing, the TS ended in an endless boot logo loop.
3. I replaced the 2 files you provided and flashed again.
4. Same thing happened, boot logo kept on looping.
5. I took the battery out and replaced it but it didn't help.
6. I thought maybe I should flash back to my original firmware using my backup.
7. I loaded the scatter file to the flash tool and flashed.
8. I didn't work either, this time it was the old boot logo.
9. I tried one more time flashing using your firmware
10. Still end up with an endless loop with your latest boot logo..

Please advise what I can do to get my watch back to normal again.

Thank you and sorry to trouble you.

Cheers

 

[kuronosan]

Did you flash the lk/kernel?

 

[zipizip]

Did you flash the lk/kernel?

If you are referring to this:

"I flashed the May Firmware update and now my watch bootloops!!!

Download this file and replace the lk.bin/boot.img in your folder with the ones from the patch RAR and reflash."

Yes, I replaced the 2 files with the ones in the firmware "TS-EU-0706-May_Shipment" and reflash.

But still boot loops continue

 

[kuronosan]

Did you factory reset?

 

[kuronosan]

And if so, did you make a backup? I will need to see that scatter file.

 

[zipizip]

825

And if so, did you make a backup? I will need to see that scatter file.

Oop! No factory reset (not in your instruction), but did a backup. Do you still need to see the scatter file?

 

[kuronosan]

Yes.

 

[zippiz]

Hi Kuronosan,

I can't attach the file. Here's the scatter file in text from my backup.

PRELOADER 0x0
{
}
MBR 0x880000
{
}
EBR1 0x900000
{
}
__NODL_PRO_INFO 0x980000
{
}
__NODL_NVRAM 0xc80000
{
}
__NODL_PROTECT_F 0x1180000
{
}
__NODL_PROTECT_S 0x1b80000
{
}
__NODL_SECCFG 0x2580000
{
}
UBOOT 0x25a0000
{
}
BOOTIMG 0x2600000
{
}
RECOVERY 0x2c00000
{
}
SEC_RO 0x3200000
{
}
__NODL_MISC 0x3240000
{
}
LOGO 0x32c0000
{
}
__NODL_EXPDB 0x35c0000
{
}
ANDROID 0x3fc0000
{
}
CACHE 0x2c9c0000
{
}
USRDATA 0x441c0000
{
}
__NODL_FAT 0x96dc0000
{
}
__NODL_BMTPOOL 0xffff00a8
{
}


Hope you can help resolve the problem. Thanks

 

[zippiz]

Hi Kuronosan,

While waiting for your reply, I tried one more time flashing the 0706 firmware, and mid-way got the following error message:

BROM ERROR : S_FT_DOWNLOAD_FAIL (4008)

I've never had this error before, what's happening...

 

[kuronosan]

Which firmware did you use?

 

[zippiz]

TS-EU-0706-May_Shipment

 

[kuronosan]

You'll have to do a format and download all using a backup emmc.

 

[zippiz]

Hi Kuronosan,

Some good news. Feeling frustrated after the last failed flashing, I left the watch alone to "die". After more than an hour later, I thought maybe I should give it a last shot. Loaded the 0706 scatter.txt and began to flash the watch for the last time. The flashing went through without error this time. After that It did not reboot nor it was turned on. Thinking I should let it charged for a while I left it in the cradle connected to my PC. About 4 hours later, I took it off the cradle and turned it on. To my surprise, it miraculously booted up without boot loops and came to life again. All the standard apps were there. I really don't understand why. I continued to apply the run.bat file. Followed the prompt instructions and ended with a "No Command" on the screen. Upon pressing the on button, it rebooted and I was back at the desktop with a "superuser" icon appearing among others. I have not tested the functions of the various apps but I think the camera function is not working properly. Could video but not taking pictures. Any solution?

I will be testing the other functions later. Thanks for all your help so far. Will keep you updated.

 

[kuronosan]

Excellent. Yea, I still need to fix the camera patcher script. I'm just going to package a new firmware.

 

[zippiz]

Eagerly looking forward to your latest firmware. I don't know what to do if you have not been around to give us, Omate users the support. The bunch of people at Omate is not really doing anything to support this device. Really appreciate your effort.

By the way, I am unable to install the Google Camera apk from your camera patch file into in the device. Have I missed out something?

Before I installed your fw, I noticed that there were some problem with the bluetooth of the watch. When it's paired with a bluetooth listening headset, the signal range between them seemed very short. When I was running with the watch on my wrist and a bluetooth listening headset on my ears, I could hear sound when my hand (with the watch) was closed to my chest. However, when I moved my hand away from my chest, the sound got cut off. Do you have any idea why it is so?