[HTC EVO 3D] Unknownforce:
Well, just checking in again... with the latest info...

I again was able to get my device fully restored via using my tool, not a backup copy, but I did this the first time without issues as well, so nothing new there... my goal is to get it to work for everyone else of course and on a wide scale, not just fixing one or two at a time...

So where am I at with that?

Well, the good thing is... The first test, as you may or may not know, broke people's radios like completely, in the newest patching, this no longer happens, woohoo!

Now, I also found (in my own phone) EVERYTHING that gets changed and everything that I CAN revert without needing any tools (just a simple PG86IMG flash)

In that testing, I've found that 5 Partitions differed, 17, 19, 26, 27, and 28.

17 - This was only a minor version number, not important.

19 - radio_config

26 - modem_st1

27 - modem_st2

28 - devlog - not important, just a log file basically.

26 and 27, I determined are not important to us here. Reason being... I did fastboot erase modem_st1 and st2, and they came back and re-wrote themselves. (differently than they were before, so I know they changed and erased properly)

So in that, I've proven now that 19 is the only partition we truly need to fix... We pretty much already knew this, but I was just re-building from the ground up and going over all bases.

On to 19...

Good news... I've figured out why people's phones are having issues... But... it's not helping me thus far. The reason it's messing up people's phones is because of the way the radio_config partition is read by the radio. The radio_config partition is actually a combination of partitions all grouped into one. Now, each of these "mini partitions" contain little bits of info to tell the radio how to talk to the towers. Examples would be IMEI numbers, MEID numbers, PRI, PRL, MSL, etc. Each one has it's own "designated" place.

Now on to the bad news and why it's not helping me really... What I'm seeing is that the PRL and activation info, and some other of the important info is getting shifted around in this partition... and can exist in multiple places on different phones... Ultimately, in some cases, confusing the radio because it can't find what it's looking for to operate properly...

To complicate things... the VM firmware doesn't always move them around on everyone's phone... Nor to the same locations...

To put it in more basic terms... think of these "mini partitions" as library books, and you have a master computer to look up where each book is located... the problem we're currently facing is that the VM firmware has come in and replaced and moved some of these books around. So... now when someone goes to the master computer and looks up PRI information, or Phone information or MSL or whatever else, These books have been moved to another location without telling the Master computer where it's put them... so it's now pointing at the wrong location. So when the radio asks what's the "secret" code to communicate it to the towers, the radio_config partition (master computer) kicks back the wrong information, thus causing the radio not to function properly.

This is also why certain people cannot get the patch to work. because although my books are in one place, theirs are in another... So it's patching the wrong books and ultimately breaking their activation info.

So, I have to figure out how to do one of two things here... either figure out a way to get the books back to where they belong (at least line up similar to my own phone) OR determine how the phone's "master computer" or indexing system works... and then use that info to tell the tool where to first find the correct book and then patch it accordingly.

Need-less-to-say, It's not an easy task... Especially when I only have one device to test with, and I also use it as my personal daily device... And on top of which, mine always ends up in the same spots, where others' do not.

I'm working with testers as best I can, but without being able to see results first hand it makes for a slowed process of elimination here.

Well, just figured I'd stop in and give some info. So I'll check back in and update more when I can.