yashsingh1/xdaforums huggingface dataset:
[XPERIA X1 ROM Development] mattiL:
Two problems here (at least)

1. You did not Hard-SPL (the three coloured screen should say something like OliNex 0.72. )

2. To load ROM from memory card, call the file KOVSimg.nbh, not ruu_signed.nbh, that's for loading from windows ROM update utility)
[Touch HD Windows Mobile ROM Development] chemo79:
Hello guys,

Plz did any one has the original ROM for HTC hd without any additional.

thanks a lot.
[Touch HD Windows Mobile ROM Development] MJRL:
http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone
[G1 General] erdroid:
I have started a dialog with Rogers whereby I am asking nicely for them to honor the licenses which are listed in:

[Home]->[Menu]->[Settings]->[About phone]->[Legal information]->[Open source licenses]

The first source code I have requested is for the file /kernel listed in the above mentioned [Open source licenses].

An email sent nearly 24 hours ago has not been acknowledged by Rogers, despite the fact that their Contact Us email portal indicated that I would receive an acknowledgement within 24 hours.

Consequently, I called Rogers and managed to get a Rogers representative to email me back indicating that next business day (Monday) s/he would try to point me to the right person within Rogers.

Let's see if we can change what shows up when you search "Open Source" on the Rogers web site:

http://www.rogers.com/web/Rogers.portal?_nfpb=true&_pageLabel=search&Ntt=Open+Source
[G1 General] the.purple.engineer:
The actual kernel is written by HTC, but good idea, ask Rogers to point us in the right direction because we haven't gotten anywhere asking HTC directly.
[G1 General] PhaseBurn:
Here's an update for you. I've been contacting HTC customer service for a month now, and I've had my issue escalated to a VP at HTC America. I relayed to him all the hassle I've been put through for something they're legally responsible to provide, and the story I heard is as such:

HTC was asked by Rogers to make some last minute changes, but they didn't specify what. They were also asked to withhold source code for reasons that HTC wouldn't comment on. Basically, the representative confirmed that Rogers specifically asked HTC to do this. So I had the issue escalated to a VP at HTC America. After a month of hassle, and the final escalation earlier this week, here is the email response I got back today from the VP today.

David,

Thank you very much for your note and more importantly, thank you for your business and loyalty to HTC products. We owe all of our success to you and customers like you. I also want to thank you for taking the time to write me personally and communicating specific areas where we can improve in our customer service. I will investigate the issue and get back to you by Tuesday, 7/28 at the latest. Additionally, I will have our Head of Customer Service drive our Call Centers to do a better job of communicating, particularly on this issue. My apologies for the time you've had to invest in this to date.

All the best,

Jason

Jason B. Mackenzie

Vice President, North America Region

E-Mail: (Removed, but not hard to find)

So while it isn't "source code in my hand", it's at least *something*. I'll provide more info as it becomes available to me for sure.
[G1 General] cyanogen:
Wow, bullet dodging everywhere. I talked to some folks from Google and they don't have the code we are looking for, that's for certain. HTC blames Google, Google blames HTC, HTC blames Rogers. How complex is this problem really? It's probably 5 lines of code that they changed. We need to get past their buffer-wall of customer support and talk to someone in engineering.
[G1 General] lbcoder:
So Rogers asked HTC to break the law and they complied? :eek:

Can we get this confirmed in writing? An email (with headers) from an official at HTC stating that such a request was made regarding kernel source would help. If we do that, we would have the silver bullet we need to go after robbers AND htc in civil court -- think class action, and we should get some major kernel contributors and open source advocates on board-- I'm sure that LOTS of people would LOVE to take up this cause.

My prediction: if there was a class action civil case organized naming rogers and htc as defendants, htc will fold and hand out the source, probably quickly. Rogers... maybe not because they're bastards.
[G1 General] hellfenix:
I'm pretty sure they are having some meetings about that internally at HTC right now because I inquired about the source from HTC 3 days ago and they still haven't replied to me, not even a canned response. I'm pretty sure they are investigating right now how they can give us source while not giving away whatever they are trying to hide.
[G1 General] Northsun:
No, I don't believe this is a violation of the GPL, and some quick googling tells me that the FSF agrees (see http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#DoesTheGPLAllowNDA)

Even though Rogers would be in violation for distributing a modified kernel without source, HTC would not be.
[G1 General] PhaseBurn:
You're correct, and unless somebody who has code in the linux kernel they're shipping wants to file suit, we can't go after them legally as we aren't representative of somebody being damaged by their copyright infringement, despite that it hurts us. Stupid copyright law, even under the GPL, requires an author of the material to go after the company.

HTC designed the phone, and customized it for Rogers. I'm not honestly sure who bears the legal responsibility of releasing the source code for the GPL'd components, either Rogers or HTC, but one of them does and HTC is seemingly claiming responsibility for it.

Since you want email headers, here they are. Yes, I have blocked out email addresses (ONLY), as I don't need any more levels of spam nor does Mr. Mackenzie, I'm sure. I will post the full headers, unedited, in a .txt file somewhere if requested and link to it, I'm not trying to hide anything, I'm just not comfortable posting some things on public forums. I also did not disclose to Mr. Mackenzie that I'd be cross-posting his email reply anywhere, so the least I can do out of respect is not publicly post his email unless it's warranted.
[G1 General] cyanogen:
Something tells me that the software they are referring to is NOT the kernel and is most likely the custom apps and other software on the device. Your VP probably has no idea at all what a kernel is, especially if he wants to refer you to customer support. This should have been sent straight to their engineering staff. If you can get them to clarify this, maybe we should send the story to some huge site that loves this kind of stuff like Slashdot. Get the community nice and outraged :)
[G1 General] PhaseBurn:
Oh, I totally agree, and I sent a similar email to the VP of Engineering as well, but have not gotten a reply. In my email, I explained what a kernel was, and that the open source license in the Legal section of the device specifically covered /kernel which was all I wanted the source to. I'm not holding my breath I'll get something on the 28th besides a "we're still working on it" but at least it's something, and ultimately, I hope it does lead to the source we need. This is an excerpt of what I wrote to him, so I'm hoping that even if he doesn't understand it, it's enough for him to get over to the staff who does. I assumed that since it hasn't been released yet, it is likely NOT an Engineering decision, but being held up in Legal somewhere, which is why I went this route as well.

At least as a VP, he's in a position to comment and help if he so chooses. We'll see where it goes, all I can do...
[G1 General] SpEnTBoY:
I'm sure the FSF wouldn't mind knowing what's going on. ESR loves a good shuffle and the FSF COULD get a core member of the dev team or maybe a contributor or even Linus etc to bring it to the attention of Rogers and HTC that there is grounds to pursue further action of they remain non compliant.

I'm just saying there might be other avenues once we've seen how this one plays out. I'd hate to kick a wasp nest if there are valid and honest attempts to rectify the situation calmly. It could very well be just a case of honest ignorance that needs to be schooled back to a level of understanding ;)
[G1 General] PhaseBurn:
That's exactly why I haven't contacted them yet, and nobody (that I know of) is considering a lawsuit. I'm certainly not. If my attempts to get through to this VP fail, I have a few other contacts I can put pressure on to get HTC to provide it. Turning it over to the FSF and communities like Slashdot are an option I have considered, and may do at some point if HTC stops acting in good faith, but for now I believe they're either acting in good faith at the higher levels (the email reply from the VP confirms this IMO) or, really good at blowing smoke up my ass. Either way, I'll tolerate for now and have faith.
[G1 General] hellfenix:
We totally have to consider that big companies like HTC need some time to turn around so let's all wait patiently for that 28th date and see what comes out of it. Then we can decide where to take this further, thanks alot PhaseBurn, maybe something will come out of this :D
[G1 General] PhaseBurn:
No problem. Technical support is officially a dead end for this route, too. I just got a voicemail back from HTC's advanced support department saying "Technical Support does not have any way to distribute that [the Roger's kernel source] at the moment, so we've asked for our headquarters to weigh in and see what their official response is." They went on to say I've been put on a tracking list for when they do have their answer from headquarters, and when they have a response from HQ, they'll contact me when they have the official answer. So at least we know bugging tech support about it won't get us anywhere, but it will continue to draw attention to the issue at least... And yes, I have the VM saved as a .wav file just in case it's needed...
[G1 General] hellfenix:
HQ would be China (Or Taiwan?) and I'm pretty sure they are the one with the goods so this is good enough news.
[G1 General] PhaseBurn:
HQ is either Houstin, Texas, where HTC America is located, or, Taiwan, where HTC's world wide HQ is...

The HTC Dream platform was designed by HTC Taiwan, and released to HTC America and HTC Europe for sales and support, so I'm not sure if it'd be HTC America or HTC Worldwide that has the code for the Rogers version of the device - there are subtle hardware differences between that device, and the other HTC Dreams released world-wide. I don't know to what extent HTC America and HTC Europe have engineering departments of their own, for instance. If I had to guess, I'd say it'd be HTC Taiwan that has the code we're in need of, and is the group that engineered the Rogers Dream/Magic platforms specifically. Of course that's just speculation on my part. I'm sure you all can speculate as well as I can, I've posted pretty much all I have, and right now, I'm just waiting until the 28th for a reply. I'll post what I get when I get it...
[G1 General] PhaseBurn:
So I got my reply from Jason at HTC just a few minutes ago.

The news is good - very good, but will require some patience...

So another 2 weeks. I'll post the link as soon as I get it, but at least we have our answer. They will be releasing it.
[G1 General] SpEnTBoY:
... did everyone else smile significantly when they read this? I love it when people and companies just 'get it', even if not every link in the chain is up to date. Great news and a serious dept of gratitude for doing the leg work PB!!

:D:D
[G1 General] hellfenix:
Wow, so basically they just didn't think about it and/or waited for someone to ask for it before setting up something on the website. HTC is playing it very safe and I can't blame them.

That is fantastic news, first week of August happens to be next week so it's not that bad of a wait, especially if they intend to implement some sort of source control system on their website.

Hopefully the sources will be integrated in the main Android Kernel assuming they were actually useful and not only meant to block us.
[G1 General] holdennull:
Wow, that's great. Good job and thanks.
[G1 General] cyanogen:
Great news, but I just think it's odd that they haven't contributed the code back to AOSP. Half of the ARM code thats in there now is written by HTC already..
[G1 General] lbcoder:
Perfect ;)

Guess I can drop my attack for now.
[G1 General] PhaseBurn:
It wouldn't surprise me if Rogers asked them to withhold this code, that they did so from *everybody*... After all, it seems to be specific to the Rogers Dream/Magic, likely because of the 3G frequency differences. As such the Legal dept that oversees the few people involved with the Rogers-specific sources may have said "These are Rogers-specific changes, we don't need to contribute them back" and it's very possible that the Legal dept didn't even know they constituted "source changes", just "modification to get it to work with the new frequencies", etc... from a non-technical point of view, I can easily see that.
[G1 General] lbcoder:
Well, just got another message from my contacts....
[G1 General] hellfenix:
I got the exact same response from Ryan today and I hadn't gotten an answer since July 21. At least now we know everyone in the company is aware of that haha
[G1 General] SpEnTBoY:
This is starting to get confusing :p they don't have the source code they were asked to not release by Rogers? or they didn't contribute the source code they were asked to withhold temporarily until Rogers approved the release?

Didn't the patch against the 2.6.25-htc kernel list dev email from HTC? ... just trying to keep up :o
[G1 General] mburris:
Ryan at HTC was saying basically that the Technical Support Peons do not have access rights to get the source code we are requesting. Which makes sense.

The HTC engineers in TW are the ones who have what we need, and hopefully we will have it by September, even though they say August (not holding my breath.)

So source code is legally required to be given upon request, eventually we get it, and hopefully soon.

Without it we will not be able to build a modified kernel. Once we have the small little piece of code, we could basically merge it with cyan's kernel, or any other flavor of custom kernel and get them running on our RD's (Rogers Dream).
[G1 General] Pokeon:
If HTC can pull it out by Aug then there gonna earn some major repect and wallet points.
[G1 General] PhaseBurn:
Totally... I'm rather impressed with the way they're handling it, to be perfectly honest. Yea, it'd be better if it never happened, but imagine if it was Samsung or LG...

I'm rather curious how LG and Samsung are going to handle the code-aspect of things, now that I'm thinking about it...
[G1 General] jackkerouac:
In the meantime, if you are just looking for a look change on your Rogers dream, you can try the "hero-lite" theme:

Works great on my Rogers Dream. Get it here.
[G1 General] lbcoder:
Would you mind not spamming this thread with that useless crap?
[G1 General] PhaseBurn:
I guess you can't blame the weather :-/

The Friday reply. Will follow up Monday when I get something... At least thanks to Haykuro's post, we can at least run custom firmware now...
[G1 General] hellfenix:
Tuesday and still nothing? Evil Weather!
[G1 General] PhaseBurn:
Yea, no email received Monday or Tuesday. I've drafted another email to them to ask what gives...
[G1 General] lbcoder:
Update from tech support (Ryan):

From the sounds of it, this may be bigger than just the kernel source since this website is for source for "Android phone*S*" and not just Rogers Dream.
[G1 General] jashsu:
Of course Android phones could be referring to a plurality of a single model as well. i.e.: "I sold a hundred HTC Dreams. My customers are pleased with their Android phones." That said, given the similarities Magic shares with Dream, I wouldn't be surprised to see some source for that as well.

Edit: oh yeah day off on Friday for Typhoon Morakot was pretty nice. ;-) Taipei wasn't even heavily impacted.
[G1 General] jashsu:
Well to be fair, part of the "magic sauce" of the Android project is that implementers are not beholden to license-alike for derivative products. <3 Apache License. And due to Google's preference for "cathedral open source", there's likely still quite a lot of disparity between their internal codebases (and what gets rolled into official releases) and the AOSP.
[G1 General] :
I'm having a hard time understanding what's so special about their code anyway? Is there any hurry?

Now that Haykaru has properly rooted the phone, what does Rogers have in their code that we could want?

It's not that I disagree it should be released, as it has to based on the GPL, but what is the motivation to get it sooner rather than later?

-James
[G1 General] lbcoder:
Well for one, the current root hack depends on a known-phone-killer SPL, which requires htc's kernel patches.
[G1 General] :
The T-Mobile G1's are not at risk from this? I might be ignorant here, I'm curious.

-James
[G1 General] lbcoder:
Changing things in the KERNEL is NEVER a risk since you can always restore it. Installing a dangerous SPL (especially one that is a known killer) *IS ALWAYS* a risk.
[G1 General] cyanogen:
Is it time to bring the wrath of Slashdot on them yet? :rolleyes:
[G1 General] SpEnTBoY:
Ooooooh ... evil ... intriguing but evil :D. I don't think they have the same sense of urgency that the community (and customers) would like them to have. It's very easy to say "we're working on that" or "we're looking in to it" to keep the hordes at bay for a while, the problem is the development on these devices is FAR exceeding the vanilla mash they distribute and the people that need the one or two minor components that the vendor has, shouldn't have to wait for an official PR release of a code distribution site.

That being said I understand the legal aspect of it. What I don't understand is, if they've resolved to make it available and understand they have legal (read licensed based legal) obligation to provide it ... why not give it to the people asking for it and formalise a method of distribution later?? We're not asking for the envelope or a fancy delivery ... just the damn content!

maybe I'm over simplifying but dragging this out longer is in no ones best interest if the ends are going to be the same after the delay :rolleyes:

</2 cents>
[G1 General] PhaseBurn:
Never got a reply to the email I sent on Wednesday. If I don't have a reply on Monday, I'll be taking it to the next level on Tuesday morning.
[G1 General] hellfenix:
gaahhh slow HTC is slow :D
[G1 General] PhaseBurn:
Get your pitchforks and torches...

I'll keep you updated as I get further correspondence with HTC but as it stands, corporate has denied permission to release the kernel source at this time.
[G1 General] SpEnTBoY:
now the question is ... what's the next step or who could we tell? FSF comes to mind and so does looking here to make sure they are in fact in violation:

GPL Violation

There's something to be said for accountability.
[G1 General] cyanogen:
I'm pretty certain that the patch for the Magic 32A will work on the Rogers Dream. And if not, the same principals can be used to get it working. We need someone with one of these devices to try booting a kernel with that patch. HTC can suck it.
[G1 General] SpEnTBoY:
if this can be done via fastboot with just a boot image I have no issues at least trying. The problem was I built 20 kernels (paired down, with/without features etc etc) and couldn't get a single damn boot image to load. Problem was I wasn't sure if it was my image or the kernel.

Anyone have a break out or serial cable yet? and for that matter, can you read raw off the device during init even if you don't have the serial/console portion of the kernel or bios loaded (as I have no idea where it was failing)?

HTC can suck it LOL ... I actually agree ... I really don't give a **** if they get the code out now or not. I care that whatever we need to have working in fact works, and that they, if in violation, are held to the terms of the software license for the simple fact that if it was a closed source license violation on their OWN code you can be damn sure they'd be looking for blood.

EDIT: what I meant was their own code affected by only their own licensing ... not that of the GPL
[G1 General] PhaseBurn:
I got this last night at 2:54 AM Pacific. Finally! Huzzah!
[G1 General] hellfenix:
Niiice! Thanks PhaseBurn.

So has anyone diffed that to see if there's anything new in there?
[G1 General] SpEnTBoY:
:eek: thanks for all the leg work PhaseBurn!! all in all I guess it wasn't _too_ long for them to release it. Hopefully this is going to help dev's going forward! :D
[G1 General] lbcoder:
Without actually reading through things, I can say for certain that there is a LOT of new source code... over 900 KB of new stuff for both TROUT(DREAM) and SAPPHIRE(MAGIC). Take a look under arch/arm/mach-msm.
[G1 General] natmanz:
Thanks for all of the work of prodding HTC, PhaseBurn!

I grabbed the sources and used the /proc/config.gz from my phone, compiled with arm-eabi-4.2.1 and it works perfectly. I was able to fastboot a recovery image with the kernel. Then I compiled the iptables modules and was able to insmod them as well. Excellent!

So it looks like HTC did the right thing after all.

Edit: My phone basically works with my compiled kernel. The one thing that doesn't work is the wlan.ko module. If I try to insmod it from a shell, the insmod program just hangs. /proc/modules shows "wlan 590644 1 - Loading 0xbf000000". dmesg shows:

<6>[ 80.145385] TIWLAN: Driver loading
<4>[ 80.145965] wifi_probe
<4>[ 80.146209] trout_wifi_power: 1
<4>[ 80.486663] trout_wifi_reset: 0
<4>[ 80.559722] trout_wifi_set_carddetect: 1
<7>[ 80.559997] mmc0: card_present 1
<6>[ 80.560241] mmc0: Slot status change detected (0 -> 1)
<3>[ 80.577117] mmc0: Command timeout
<4>[ 80.583312] mmc0: card claims to support voltages below the defined range. These will be ignored.
<4>[ 80.583801] mmc0: SDIO card claims to support the incompletely defined 'low voltage range'. This will be ignored.
<6>[ 80.609252] mmc0: new SDIO card at address 0001
<6>[ 80.622283] TIWLAN: Found SDIO controller (vendor 0x104c, device 0x9066)
<6>[ 80.657775] TIWLAN: Driver initialized (rc 0)

I also tried recompiling wlan from main android sources (in system/wlan/ti/sta_dk_4_0_4_32), but that has the same problem.

PS: Looks like the stock kernel is compiled with arm-eabi-4.3.1 and not 4.2.1 like I mentioned before.

Edit 2: I found information http://xdaforums.com/showpost.php?p=4260681&postcount=33 and http://groups.google.com/group/beag...ad/25fcddf411c5da57/12a225de7b5ff629?lnk=raot that indicate the problem was with a call to sdio_memcpy_toio() freezing. I changed the wlan module to use write_direct() and read_direct() as well, and now it loads okay and wifi seems to work okay. An objdump of HTC's wlan.ko module shows that it indeed imports sdio_memcpy_toio(), whereas my modified module doesn't import it anymore. That makes me wonder if HTC made some modifications to the wlan module as well, and if so, then those need to be released under the GPL v2 (as indicated in the source code for the module).

Has anyone else compiled the kernel and had similar issues with the wlan module?
[G1 General] xtrememanix:
Hi there, ive just rooted my phone on rc29 with radio 1.22.12.29.

now i wish to install the jf1.51adp rom but i was wondering if i should update the radio before or after flashing the rom.

Any help is much appreciated :o
[G1 General] wddglr:
Radio first. :)
[G1 General] akapoor:
Always Radio first!!

:D
[myTouch 3G, Magic General] str4vag:
Hi all,

Just got my unlocked HTC Magic yesterday. Purchased in Malaysia.

However, there is no access to android market (not installed on phone).

The gmail contact sync, google calander sync is also not there. anyone can help me with this?
[myTouch 3G, Magic General] ClintonH:
You could always go here for your apps. Sorry can't help with the Google stuff. :)

Clinton