I've just taken a look at the sources of the mtd driver in the kernel, but haven't actually found a lot that would be of interest to us. The actual communication with the NAND seems not to take place here. It's probably handled by an even lower level, perhaps some I/O layer that sits beneath, don't know. The kernel is simply too huge, this will turn into a search for a needle in the haystack.
Your success on this s-off will be an hboot editor, but will have a broken phone, like a 10-15 sec. delay before phone powers up I mean lcd turns on, but at least your s-offed. xtc clip ftw btw .nuff said.
I've just taken a look at the sources of the mtd driver in the kernel, but haven't actually found a lot that would be of interest to us. The actual communication with the NAND seems not to take place here. It's probably handled by an even lower level, perhaps some I/O layer that sits beneath, don't know. The kernel is simply too huge, this will turn into a search for a needle in the haystack.
Well, if there is no other way, and we have to pin it down, then we either have to look through the kernel or the radio. If we do the radio, and find secu_flag then we have a "pure" S-OFF, if we do the kernel, I suspect it will take longer and we will have a "patchwork" S-OFF. At least we will have S-OFF. But we also need to think timewise. Don't want to finish this when this phone is not sold anymore and when we are the only people left. By the way, Samsung Android phones have a "Download Mode". I've used it many times. Also, once you are in download mode, you use a GUI program called ODIN, like a RUU, it assists you in "downloading" the file to the phone and flashing it.
Well, if there is no other way, and we have to pin it down, then we either have to look through the kernel or the radio. If we do the radio, and find secu_flag then we have a "pure" S-OFF, if we do the kernel, I suspect it will take longer and we will have a "patchwork" S-OFF. At least we will have S-OFF. But we also need to think timewise. Don't want to finish this when this phone is not sold anymore and when we are the only people left. By the way, Samsung Android phones have a "Download Mode". I've used it many times. Also, once you are in download mode, you use a GUI program called ODIN, like a RUU, it assists you in "downloading" the file to the phone and flashing it.
Sent from my HTC Wildfire S A510e using XDA
In order to do either we need to be able to write to the nand so both will need us to **** with the kernal in the hope it works. Nbh what would we be looking for in general? We might have some luck if get a small army of us to go hunting through it.
Well sooner or later it will be available for almost anything. They said they will support "all devices with a newer chipset than Google Nexus One". That would even include the WFS. I think the Nexus One is still on a QSDxxxx chip. The MSM7227 of the WFS is a real powerhorse against what the Nexus One is using lol!
The Nexus One's QSD8250 is much more powerful than MSM7227. Both have Adreno 200 graphics and are Snapdragon S1s but QSD has a Scorpion (Cortex A8) core with 1GHz native clock, vs MSM7227s ARM11 w 600MHz native clock. I wouldn't hold my breath for official CM9 on WFS sadly.
In order to do either we need to be able to write to the nand so both will need us to **** with the kernal in the hope it works. Nbh what would we be looking for in general? We might have some luck if get a small army of us to go hunting through it.
sent from my android powered beast!
Well there could be a small army, made from only the best, and we could all have private training and mission briefing. I'll manage the weapons (2 AK-47S and 2 PP90M1, Air Support, Care Packages, UAV, and the other stuff)
The Nexus One's QSD8250 is much more powerful than MSM7227. Both have Adreno 200 graphics and are Snapdragon S1s but QSD has a Scorpion (Cortex A8) core with 1GHz native clock, vs MSM7227s ARM11 w 600MHz native clock. I wouldn't hold my breath for official CM9 on WFS sadly.
Well, in fact the QSD8250 is built around a newer IP-core. However, "much more powerful" is quite a bit of an exaggeration. QSD8250 was released Q4 2008, is ARMv7 on 65 nm manufacturing process and "Adreno 200" GPU.
The MSM7227 has an older IP-core, namely the ARM1136EJS, which is an ARMv6, so the QSD8250 might have a bit more compute. Indeed, I didn't find lots of details about this SoC. Actually I didn't even find an official release date. However, you can find specification of close relatives, like the MSM7227A and MSM7230, which were released 36 / 9 months later than the QSD8250 respectively. Both feature a 45 nm (more recent) manufacturing process and either an "Adreno 200 enhanced" or "Adreno 205" GPU.
The QSD series is effectively retired and superseded by the MSM series. So yes, the design of the QSD8250's IP core is newer than that of the MSM7227, but the latter seems to be the more recent System-on-Chip. Also, the Nexus One was released on the 5th of January 2010 and shipped with Android 2.1 (Eclair), while the Wildfire S was released on the 15th of May 2011 and shipped with Android 2.3.3 (Gingerbread).
Not so sure what that means for CM9 support, since I don't know whether the MSM7227's older IP-core might be a hindrance "instruction-set wise". It certainly won't be a hindrance "performance wise" or "I/O- and peripheral-wise", so as long as CM9 will run a chip with ARMv6 instruction set I don't see any reason for not supporting the MSM7227.
Quote:
Originally Posted by Bad-Wolf
Also, once you are in download mode, you use a GUI program called ODIN, like a RUU, it assists you in "downloading" the file to the phone and flashing it.
Sent from my HTC Wildfire S A510e using XDA
Yes, Odin is a leaked Samsung-internal utility. There's a clean-room implementation of it that is called Heimdall and is licensed under MIT license.
From HTML to LEDs or Android to Arduino, Hardware Hacking is a pastime of many people … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?