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

[kuronosan]

Ok, pulled down the patch again and removed battery. Tried to flash and I'm getting error BROM Error : S_DL_GET_DRAM_SETTING_FAIL (5054).

Is this trying to tell me I'm not using the right firmware?

Correct.

 

[kuronosan]

Downloaded your EU1/8, could you give details on how you recommend flashing the patch files.

Copy the contents into the original firmware folder you downloaded and flash the new lk.bin and boot.IMG instead. You should overwrite any existing files in whichever you downloaded.

Just as a note, folks. There is a huge difference between the May Shipment EU scatter and the EU scatter. If you aren't sure which one you need, post what firmware you are on and I will tell you.

 

[MaloyO]

Correct.

Ok. So I should try the pre-May flash.

I'm pretty convinced it was 140513 firmware but I could be wrong. Or I've done something else and royally messed it up!

I'll let you know how it goes.

That didn't go well. Got the same message as when I tried to flash the later firmware. What have I done?!

 

[gillebob]

Copy the contents into the original firmware folder you downloaded and flash the new lk.bin and boot.IMG instead. You should overwrite any existing files in whichever you downloaded.

Just as a note, folks. There is a huge difference between the May Shipment EU scatter and the EU scatter. If you aren't sure which one you need, post what firmware you are on and I will tell you.

Followed details posted by midafaya and yourself and im booting again, thanks.

 

[kuronosan]

Ok. So I should try the pre-May flash.

I'm pretty convinced it was 140513 firmware but I could be wrong. Or I've done something else and royally messed it up!

I'll let you know how it goes.

That didn't go well. Got the same message as when I tried to flash the later firmware. What have I done?!

I'll need to link you to a preloader, or try flashing from an eMMC scatter. Typically that means your partition is borked and you'll now need to format and start over.

 

[MaloyO]

I'll need to link you to a preloader, or try flashing from an eMMC scatter. Typically that means your partition is borked and you'll now need to format and start over.

Ok, my back up has a preloader. Should I just flash that by itself?

 

[kuronosan]

Start with that, yes.

 

[MaloyO]

Start with that, yes.

Trying to flash the preloader ... SPF tool gets to the end of the 'download da 100%' and then just keeps counting the time.

I can see in USBDeview that the MediaTek USB VCOM keeps connecting and dis-connecting.

So far 10 minutes has passed with no change in SPF tool and no error message.

Really do appreciate this kuronosan. I'm going to owe you some serious beers. I don't want to take up all your time and it's late here so could I hit you up tomorrow for your brain power?

Thanks again.

 

[kuronosan]

I'm available any time. You might need to pull the battery for that one.

Typically the reason that happens is the preloader didn't disengage correctly so it's somewhat in a state of limbo. The only way to remedy that is to reset the device.

After you flash successfully (only the preloader) you should be able to flash everything else.

 

[kuronosan]

FAQ updated.

 

[midafaya]

After using this ROM for a few hours, I find it pretty laggy.
I had several freezes too, that made the watch auto soft reboot.

(Using EU may shipments version + root & security patch)

Aside from this, every sensors seem to work, connections are like stock.

 

[kuronosan]

After using this ROM for a few hours, I find it pretty laggy.
I had several freezes too, that made the watch auto soft reboot.

(Using EU may shipments version + root & security patch)

Aside from this, every sensors seem to work, connections are like stock.

That's because it is stock.

Sent from my GT-P5110 using Tapatalk 2

 

[midafaya]

That's because it is stock.

Sent from my GT-P5110 using Tapatalk 2

I apologize for my remarks about the rom being laggy. There's actually no difference with the stock received with the watch.

stock is stock as you said.

 

[kuronosan]

I apologize for my remarks about the rom being laggy. There's actually no difference with the stock received with the watch.

stock is stock as you said.

Well, out of curiosity (sorry, health care is incredibly busy these days) when is it freezing?

 

[MaloyO]

Hey kuronosan.

I've just spent two hours trying to get this preloader to download. It is having none of it.

Hope you've got some bright ideas

 

[kuronosan]

Hey kuronosan.

I've just spent two hours trying to get this preloader to download. It is having none of it.

Hope you've got some bright ideas

Give me some pictures or tell me the error. Is it just going to full and then saying BROM ERROR (5054/4032)? If so, you'll need to flash using an EMMC scatter file and a backup. It needs to rewrite the partition database.

This likely will also mean you need to format the entire NAND (including the preloader) once you get it restored and flash (at the same time) the stock ROM or backup to restore it.

I've fixed this error several times and it almost always required me to re-flash using the EMMC scatter (which is just the scatter file without PMT information, but customized to your chip).

 

[kuronosan]

Also, links updated. I'll explain in a bit.

UPDATE

Thanks to some input and helpful advice from @Dees_Troy TWRP has been repackaged and has been confirmed by one user to now be working on their Aluminum/May unit. Download is available in the links. Be sure to give Dees kudos for the idea, it sure taught me quite a bit more about recoveries than I knew before.

 

[MaloyO]

Give me some pictures or tell me the error. Is it just going to full and then saying BROM ERROR (5054/4032)? If so, you'll need to flash using an EMMC scatter file and a backup. It needs to rewrite the partition database.

This likely will also mean you need to format the entire NAND (including the preloader) once you get it restored and flash (at the same time) the stock ROM or backup to restore it.

I've fixed this error several times and it almost always required me to re-flash using the EMMC scatter (which is just the scatter file without PMT information, but customized to your chip).

No error message. The bar just fills up to 100% and stays there. As you say in the common issues it's dis-engaging when at the 100%.

You sound like you got more hope than me at this point. Where can I get the EMMC scatter file?

 

[kuronosan]

No error message. The bar just fills up to 100% and stays there. As you say in the common issues it's dis-engaging when at the 100%.

You sound like you got more hope than me at this point. Where can I get the EMMC scatter file?

Judging from the scatter file you're using the new firmware right? I have an EMMC from the new and from the old, but if it's sitting at 100% and then does nothing afterwards (but eventually times out to a BROM error) it's because the computer isn't actually engaging the preloader in the first place.

Check your device manager for what's showing up when you plug the watch in. If you plug the watch in and haven't done anything, but Preloader shows up and stays connected (without flashing) you need to uninstall all the drivers and start over with driver install/etc.

Sometimes what happens is the watch ends up in META mode (which is an entirely different mode altogether) if the computer doesn't catch it. It will still see it as a CDC gadget but because you're in Flash Tool and not META tool your PC doesn't know the difference.

I think that might fix your issue.

edit: I looked back over your posts and noticed this:

TS had 140513 firmware.

I'm the one on G+ that got excited Sunday night and tried flashing the pre may update.

So you flashed the Pre-may update. If this is correct (you flashed 0706 instead of 0706-May) then you need this right here:

 

[cmdaz]

20140328 fw

Is this post only about May units and 4/512 NA units?

I have a 1/8 2100 unit with FW 20140328
I installed TWRP and applied Loki's "Unified unrooted 1-8 1900 & 2100 Secured Tuned Stock ROM"

What difference between my current configuration and the devices upgraded with your package?

Anyway as my device is not rooted, I'm not allowed to run the script (operation not permitted, trying to run the mount command manually in adb command box)

Should I live with my current configuration and try Framaroot, or is there another solution to get aligned with devices patched with your script to get a 07.06 FW?

Tanks a lot.