Thread: my ECU bricked
View Single Post
Old 01-24-2017, 10:12 AM   #46
vgi
Senior Member
 
Join Date: Apr 2013
Drives: frs
Location: nj
Posts: 723
Thanks: 237
Thanked 348 Times in 232 Posts
Mentioned: 58 Post(s)
Quote:
Originally Posted by steve99 View Post
Yes sh boot mode allows you to re-write both areas but the problem is no one has sucessfully read the boot area it has more protection than the standard user area. this is the 0000-7ffff which is just padding in the roms we use as we dont write back this area we start at 8000-13ffff.
when you use sh boot mode you need the actual data from 0000-7ffff which no one has, the tactrix guys were working on reading the boot area.
steve, not sure why you quoted my post as you're writing again the same info you had written before (minus the part i quoted, the one that made me cringe)?

i merely suggested to get information from people that wrote the tool (which would be used - EcuFlash) and can provide 100% correct and current answer versus getting rumors, assumptions, have herd somewhere from someone that also herd it somewhere from someone.., or simply stale info. it's common sense which for some reason escapes people.

eg, let's take your post, here's a quote from it: "but the problem is no one has sucessfully read the boot area" - you lay it out as a fact, 100% correct, no doubts whatsoever that no one in the whole world is able to read the boot area of that ECU. may i ask how you know that, where did you get that information from? Denso and its engineers aside, do you know all developers that are working on hacking ECU from all the companies that provide tuning solutions like EcuTek, EceFlash, FlashEdit, etc and got all that information from them at the time of your posting (latest info)? even assuming all the above, that's already "yesterday's news" as today someone might have hacked it.
vgi is offline   Reply With Quote