Calkulin system vs ruu system dump and wimax flashing

---

This information was deleted but is important to have. The old thread was a mess and deleted. This is not a flame just facts that needs to be seen.

The ota calkulin put out radio and all.is EXACTLY the same as the ruu files. There is NOT nw wimax or radio in the ruu. Below is a diff comparison of the two

Http://pastehtml.com/view/1a08c0f.html

Now that we are sure roms based on ota patch have right files, we ned to figure out wimax.
U renvoked put a news article out saying flash image is loosing data flashing wimax radio. How do wr fix this?

http://unrevoked.com/rootwiki/doku.p...lic/jul3update

wait you reposted this after a mod deleted it ?

I'm sure the old thread was deleted because of flames. This is a working thread on figuring out wimax because wr are sure the files we have been using all along are proper. There is nothing wrong with posting this information


Do not start flaming. I'm not.


One method from old post was to use dd on the partition. Treve you still out there I lost your post.

was i flaming?? no i was asking there is a difference don't get so defensive

im still here. im taking a back seat to alla this, but whatever.

Yes i did diff's and i did permissions checking on OTA vs RUU. they look proper. i do not believe itis anything in the roms i checked out (calkunins OTA files and damagecontrol obviously) i believe it is something to do with wimax.

now my theory was in the last flaimbate thread was that we could mount the wimax img to a loopback mount point and use dd to write it to the wimax partition. im not sure if A) it is a yaffs2 img or something that can be mounted and B) if we can even directly write wimax partition (/dev/block/osmethingorother) dd should be a 1:1 write though..

someone else might have some insite

How can we verify what is written to.wimax partition?

I think a good start would be to start with a device that has the newest updated wimax firmware and *is working* and dumping the partition like this:

Dump your wimax data by issuing "fastboot oem saveprt2sd wimax -n wimax.bin" command (varies, anywhere between 7 to 8.5 MB, mine was 7MB)
Dump complete partition (~12MB) by issuing "fastboot oem saveprt2sd wimax -n wimax.bin -a" comman

( from http://forum.xda-developers.com/showthread.php?t=716694 )

And see what the differences are after intentionally messing it up.

Then do the same thing on a device still running 24772 with first a working image and then a messed up one. (Once you have the backup getting back to a working state should not be an issue as seen in that thread.)

Doing it with 2 different versions should give us a good idea of what they're doing that flash_image is not. Well, we already know they saving and adding the keypair, but this should put us on the right track as to how to do it ourselves.

My phone's currently stock and on the official 1.47 release because I had other issues and had to go in and get a replacement setup on friday or I'd take a look.

WARNING

---

thread was deleted for a few reasons. 1) it wasn't in no way shape or form a development thread, there for it didnt belong in the development forums. 2) it was a flame focused thread. not only by the OP but the rest of the members in thread pursued the same suite. i wont delete this thread but i will move it. let it get out of control again and in the trash it goes. i believe this is a general discussion thread as ur only making a comparison for FYI purposes. on another note, next time a thread is deleted u can PM me or the mod who deleted it and tell ur side of the story to get the thread reopened.

but again this is my warning. start flamming and ill start banning

How is writing out wimax image dumps general? I think mods just are upset because of flipz putting fake facts. This is absurd

I pmed a few mods. Moving this is in bad form

Originally Posted by fallentimm

How is writing out wimax image dumps general? I think mods just are upset because of flipz putting fake facts. This is absurd

from what i see here it belongs in general. all it this is just a diff of two groups of files. the last thread went nowhere and so is this one. what exactly do u plan to do with this diff? what purpose does is serve but to defend a members work in some form? why does it belong in the development section?