yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] cheeseus:
You can install the software, take out all files you want to edit from the folder they were installed to, and then replace them with the edited files. Sounds easy, doesn't it?

This is what I do when I edit the resources of various EXEs and DLLs - sure the same will work for images.

You can afterwards repack the installed program using, for example, SK Tools (Installed Programs - Marked items - Make cab) and get yourself a working installer :)

There might be better and more professional ways to do the same - if anyone knows, please educate us :D
[General Questions and Answers] WaltA:
You could use a .cab editer like Cab Manager. With that, you can extract and add files, and then re-save the new .cab file.
[Touch HD General] thebaroninlondon:
Hi all

OK, my screen alignment on HD is so messed up i went to downgrade my HD HTC (1.56 Olinex -W6.5Miri) back to its original Orange SPL and OS so i can send it back to HTC under warranty.

Foolishly I changed the HSPL first to original stock so it is now a SPL 1.14.000 (no olinex or anything) in bootloader.

I went to then flash ROM to latest Orange HTC OS release from xda (compatible with that SPL) and just got the 262 error.

So, I have a big problem...

1. I cannot flash any ROM from bootloader - error 262 problem - hangs on 0%

2. I cannot cook a new HSPL in any way - error 262 problem

3. Ive got green screen and cannot in anyway load SSPL-Manual-TouchHD.zip and then run it (which normally fixes the 262 error)

4. Ive got green screen so my phone doesnt work

5. tried hard reset - now hangs on loading new OS in green screen

Is it bricked? Is there any software I can use to force reload of HSPL? is there anything i can do in green screen? I figure my aim is to get the phone back to 1.56 and start over again. FYI am using W7 on pc but uploaded new drivers etc.

Very curious to see if folk out there have any ideas...

Cheers in advance
[Touch HD General] Fallen Spartan:
You should still be able to flash your original stock rom unto your device and then follow proper methods to flash latest stock
[Touch HD General] thebaroninlondon:
thanks. i am frantically looking for a copy. i did download one from rapidshare but was only an upgrade. however the good news is it did start to install (ie got to 1%) which means some movement. if you anyone can advise where to get basic orange rom for 6month old HTC HD then let me know. ill keep searching...

ah a grain of hope...
[Touch HD General] Fallen Spartan:
Get it here on the wiki mate.

Would start with RUU_BlackStone_HTC_Europe_1.14.401.2_Radio_52.49a.25.26_1.09.25.14_Ship.exe
[Touch HD General] thebaroninlondon:
Many thanks Fallen Spartan

I realise you must deal with a lot of panic "BRICKS!" Not one to flap but exhausted all my knowledge. And as usual the solution was a simple one and not desperately technical.

FYI: The ROMs didnt work but went to actual Orange site and downloaded their exe file ROM and it went straight as if a normal upgrade.

Thanks for prompting me in the right direction. You just saved me £400!
[Touch HD General] Fallen Spartan:
No worries, thats what we're here for!
[Touch Pro2, Tilt 2 Windows Mobile General] m_jjacks:
Can anyone help me? Almost at every call my TP2 restarts... the ROM version is the oficial 1.19.401.1 (51489) wwe. Did anyone of you had this problem?
[JASJAR, XDA Exec, MDA Pro General] kazparov:
fixed fixed fixed
[JASJAR, XDA Exec, MDA Pro General] orb3000:
Try to reflash with a diferent ROM

And have a deep read in the Wiki:

http://wiki.xda-developers.com/index.php?pagename=HTC_Universal

Good luck,
[JASJAR, XDA Exec, MDA Pro General] kazparov:
i tried the reflash, but no luck
[JASJAR, XDA Exec, MDA Pro General] orb3000:
What about following the steps on the Wiki?

Let us know more details of your problem
[JASJAR, XDA Exec, MDA Pro General] kazparov:
i soled my uni
[JASJAR, XDA Exec, MDA Pro General] orb3000:
Who is the Universal section Mod??

I would love to know who is in charge of this section!!:confused:

:)
[JASJAR, XDA Exec, MDA Pro General] -Jonny-:
I thought it was midget?
[General Topics] lincolnwang:
Hi guys,

I just had an exciting experience on my HTC Touch. Actually I found a sensor-enabled task manager named Rosseta TaskMgr on www.rossetamobile.com. They also have some nice screenshots there.

With this little application, you can shake or roll your phone to switch between running applications.

Now you don't need to worry about which harware key to be assigned to what kind of Alt-tab app.

It's just so convenient and fun to switch between running apps with it.

cheers,

lincoln
[General Topics] lincolnwang:
Here are some screenshots.
[Hero, G2 Touch Q&A, Help & Troubleshooting] chanmama:
sorry for my poor english

i got a problem as sunject mentioned.

when i finished a call, my screen will not auto lock, does anyone have same problem or just mind? anyone can teach me how to auto lock after a call???
[Hero, G2 Touch Q&A, Help & Troubleshooting] deeren:
what do you mean autolock? just press the end button after your call and it will lock the screen
[Hero, G2 Touch Q&A, Help & Troubleshooting] eabinsan:
most phones' keypads remain locked when you receive a call. the hero unlockes when you take an incoming call (or is this only when one uses the touchscreen?).

maybe he is using a bluetooth headset. when the phone indeed unlocks itself during the call, this would be a major pita when you just want to keep the phone in your pocket. anyone tried that yet?
[Hero, G2 Touch Q&A, Help & Troubleshooting] isk2005:
i answered a call with my bluetooth headset & the screen unlocks itself....this is kinda disappointing........
[G1 Android Development] jashsu:
The answer is simple:

do not include any non-open source apks or code that you have not explicitly received permission to distribute.

Instead, after building your entire update.zip, strip out all the proprietary software. Then, create a .bat and/or .sh file that will perform the following tasks:

- Download the official update.zip from the google.com site.

- Extract the required apks, obexes and jars.

- Add them to the correct locations in your update.zip

- Sign the update.zip (so include signapk.jar with your script)

- Rename the file update.zip

Name your zip as "incomplete-update.zip" (or something of the sort) and include your completer script with the file. Users will run the script and receive a complete update.zip as you had intended to distribute. THAT'S IT! A completely license-abiding way to distribute cooked "roms" without infringing on Google's licenses.
[G1 Android Development] Drizzy Drake Rogers:
I wish google or HTC would contact me, I would say huh, what, me no speak spanish.... lol
[G1 Android Development] TheArtiszan:
Only if that would actually stop lawyers. God I hate lawyers. If that defense worked MMOGlider.com would still be working.
[G1 Android Development] jashsu:
It would, atleast in this case.
[G1 Android Development] afflaq:
Glider actually had a detrimental effect to the community, these mods don't. Horrible comparison.
[G1 Android Development] patientzero:
One man's detriment is another man's free market. It's a tough question.

Disclaimer: I hated MMOGlider and the people who use it, and wish they would've died in car crashes.
[G1 Android Development] stellarman:
This would work. But, it seems to me you could also take a similar approach that works like this:

1) Strip the proprietary code out of the update before signing.

2) Sign and distribute the update.

3) People install the update and return to the recovery screen.

4) Drop into terminal mode and run a script that downloads and installs the missing proprietary code in the proper places.

5) Reboot and enjoy.

Any reason that wouldn't work equally well (but be somewhat simpler)?
[G1 Android Development] jashsu:
It doesn't seem like it would be a good idea to boot into the OS with major parts missing (esp stuff like framework.apk). However, if it can be worked around then yes, that would be a method too. Any variation on the theme of "partial update.zip plus files from a locally downloaded official update" would be good.

Is it more work to do this than just to distribute a fully complete (but not license compliant) update.zip? Yes. But it not only protects the cook from being C&D'd, it also helps to legitimize the "ROM" cooking scene.
[G1 Android Development] camalot:
You are still distributing the the unlicensed files, you are just providing a different way to distribute them. instead of including them directly in your ROM, you are supplying a script that adds them to your ROM.
[G1 Android Development] G1-evolve:
Man all this is too much.... I might get rid of my G1. Google is always trying to ruin the good things for us. -__-"
[G1 Android Development] fauxhawk:
The framework.apk is APL and part of the Android source. To see what you get without the Googlebits, just run the emulator.

I think the easiest is to have the updater copy the proprietary bits from the phone to your SD card, perform update, then copy back. then reboot.
[G1 Android Development] stellarman:
Read my post again. I am not suggesting that you try to boot without the parts. I am saying to use the terminal WITHIN Recovery. Do the step of re-adding the proprietary bits BEFORE you leave Recovery and reboot.
[G1 Android Development] tnleeuw:
Actually people, let's not forget that perhaps Cyanogen had to modify some closed-source apps like Market and Camera on several occasions, right? To avoid crashes due to resource-id changes?

So just downloading older binaries might not always work?

--Tim
[G1 Android Development] kanstin:
I sent a twitter to Cyanogen about this last night. Downloading every time would be slow and a waste of bandwidth. I think you could do it one of two ways.

1) add a script to cm-recovery that is executed with ALT+G the extracts the apks, etc from an official google dist file on the sdcard and copy them to the proper locations.

2) add a script (which does the extraction, etc. from a zip on the sd) someplace into update.zip. cm-recovery looks for that script and if it exists then it will automatically execute after the normal update routine is complete

3) a combination where the script is in update.zip but the users has to hit ALT+G to execute it.

I think #2/#3 would be most flexible because you wouldn't have to change recovery image for different ROMs and all ROM developers could have a custom script in their update.zip to fit their needs.
[G1 Android Development] Sxyman815:
rewrite those applications if they haven't already been rewritten in one way or another many dialers, a couple marketplaces, youtube, all the apps could be developed just like messenger and browser come on lets just get around google and create the missing apps
[G1 Android Development] fauxhawk:
Anything that requires a user to press more keys is dumb. The problem Google has is that their apps are being redistributed by rom makers.

Lets take a look at how Google circumvents the same restrictions for HTC binaries: http://source.android.com/documentation/building-for-dream

Remember they are advocating circumventing HTC's proprietary licenses by running a script to copy these files. We need to do the same thing, and as long as we are coping the files, using the phone as the SOURCE, the process can be transparent to the user.

Edit:

Also has anyone thought about the fact that HTC proprietary files are being redistributed also? The phones are UNUSABLE without these files.
[G1 Android Development] kanstin:
Yeah, it is dumb. Option #2 runs the script automatically and and Option #3 requires pressing ALT+G. Option #3 is in case the lawyers get really nasty; there is no way they can say that option is in violation because it requires user intervention (pressing ALT+G).
[G1 Android Development] HTCinToronto:
would this approach at distribution impact the optimization and tight fit of the ROM?
[G1 Android Development] testing567:
This is pretty much the same idea I had last night.

http://xdaforums.com/showthread.php?t=564303
[G1 Android Development] Loccy:
But you are not distributing these files. The update.zip you supply has absolutely no intellectual property which you are not entitled to distribute. Even the script, the IPR for it would be with the dev who write it. Now it might well be illegal - and personally I'd debate whether it is, but let's leave that for now - to *RUN* that script. But that's not the dev's concern and everything he supplied would be his own IPR.

Say you had a friend who worked for Google. It's the same as the difference between this friend emailing you a copyrighted MP3, versus you using Google to search for the same MP3 and then clicking on a link that appears. In the latter case Google hasn't distributed anything - they've merely provided the means for you to find the file on-line. YOU are then the one who breaks the law by downloading it. In the former case, it's your friend - and possibly Google as the people who provide the email system - who break the law.

Any dev who provided a script to download what is needed from a place on the internet and extract them from a zip would be very difficult to C&D.
[G1 Android Development] uberingram:
This is all very stupid. I honestly think the legal team at Google is behind this more than the Android branch because any half wit not tied to a court room has got to understand we'll find a way around this.

Oh well. If this goes sour I'm buying a TP2.
[G1 Android Development] lucky 69:
man dont do that.this will get solved soon and all will be well again ! there's always a fix .hopefully soon .hell microsoft does this stuff alot .but were still running stuff that we should'nt have, but we do! they should be happy that dev do what they do ! it's a great test bed ! thanks to all you dev. can't to see what happens .
[G1 Android Development] newspeak:
I like this idea the best and it seems to have the best chance of sensibly working ...like it or not the google apps and integration is one of the main reasons people get these phones...the idea of a totally open source build is a great idea but personally i would hate to lose the "google experience"

this is simple its easy to do and we really need to run it by a lawyer to make sure it would work and just run with it
[G1 Android Development] Chahk:
Step one: cut a hole in the box...

Wait, wrong forum.

If google's C&D letter is about distribution of closed-source software, why not make a backup of existing apps the first step. Since we all own "Google Experience" phones already, we have them on our phones already. So flashing a ROM would include an extra step before the actual flash to back up the naughty apps to SD card, and restoring them after.
[G1 Android Development] DavidChill:
theoretically that seems easy enough to do. Couldn't a script be developed that would help make the process easier for people who aren't comfortable going into Recovery or even doing console commands?
[G1 Android Development] Chahk:
I don't see why not. Any ROM cook already knows exactly which APKs, JARs, etc. files are not in the AOSP branch (they have to pull them in manually, if I'm not mistaken). It should be trivial for them to compile a list of these files, and then write a script similar to switchrom that TARs them to /sdcard (to keep permissions) before flashing the ROM, and restores them back to original directories after.
[G1 Android Development] matt_stang:
This is bull**** guys. ROM cookers don't need to change a single thing about making their ROMs. KEEP THE CLOSED-SOURCE APPS IN THERE. If Google decides to force you to stop doing this (as apposed to politely asking) they will be losing the respect and the loyal fans that their Android operating system has earned them. If Google wants to turn us, the majority of Android's community and fan-base, against them, so be it. They will only be hurting themselves.

Also, as has been pointed out several times, Google should be THANKING all of the ROM developers for not only developing killer ROMs, but also developing Android itself, and for showing the true awesomeness of this open operating system. I don't know much about the situation and apparently not very many people have any true details about what's going on, but honestly, I think Google either has done this unintentionally (someone at Google jumped the gun) or they will realize their mistake and contract their demands.
[G1 Android Development] lbcoder:
How about this; YOU develop a world-class rom, keep the google apps in, wait for the letter, ignore it, and see what happens.

For that matter, when things get back to mostly normal and the bigger romdevs are pushing out stuff withOUT google, you just have to shove the google back in, slap your name onto it, and distribute it. I suggest MAILING a copy with a legitimate return address directly to google's lawyers...

Let us know how it works out... :rolleyes:
[G1 Android Development] Ryanmo5:
LMAO that's too good.
[G1 Android Development] jashsu:
Not really.
[G1 Android Development] jashsu:
The downside to this approach is it assumes that all the proprietary ingredients the "rom" cook used is already present and up-to-date on the phone. That might not be the case in all usage scenarios (e.g. if the user is upgrading from a freshly downgraded device).
[G1 Android Development] jashsu:
As long as the workaround operates within completely license-compliant means (like the one I described in the first post) , I'm sure the legal team at 1600 Amphitheatre Pkwy could not care less.

Frankly I think (as I stated in the now locked "petition" thread) what really took the cake in Cyanogen's case was the inclusion of the unreleased Market software. C'mon guys, this should be pretty obvious: if you leak a company's software before its official release, chances are said company is gonna get pissed. It doesn't take a rocket scientist to come to that conclusion.
[G1 Android Development] jmon777:
wrong thread sorry
[G1 Android Development] DameonAndMeagan:
I think Cyanogen should just create his own ROM and charge for it. Give Google a run for there money cause I for one will would rather pay for a cyanogenROM that is fast and more stable then a google rom any day!!! Hopefully these apps can be replaced. Cyanogen Maps, Cyanogen Voice, Cyanogen Market, Cyanogen Tube, etc... sounds good right about now!!
[G1 Android Development] bbuchacher:
here here cyanogen should start his own company
[G1 Android Development] svxdriver:
There is a problem with this whole idea...

What happens when the updates come out?? ur still stuck with the same files ur phone came with.. Will they work?? Haven't some of these apps been modified already to make them work and if not how about themes.. You can make a nice looking rom and everything flows and looks good till u open a google app.. that just sucks if u ask me.. And I still think this would cause problems in the future as the OS is updated.. What are you going to do install the official update and then have to re-root to get your rom u like back? Oh, and if I recall when the first "soggy donut" showed up it barely worked.. any official updates that a script would download and take the apps from would be the older versions of them and would they work with the newer branch of code? I think the answer is to just make replacement apps.. google services are mostly setup to allow other sites and apps to access and use them anyway.. Hell most the apps already have alternative you can use.. the tough one to work out though is the Market. But if Moblin is going to be able to connect to it there must be a way to build another app for it.. besides I think the devs here can build better apps then the google apps anyway.. We can either waste a little time coming up with a work around like this that may cause problems again latter down the road or we can take a little more time and do it right.
[G1 Android Development] jashsu:
Aside from the fact these apps access some closed APIs, they are large complex apps that I doubt a single person would be able to easily replicate in any reasonable length of time. However, if you know some Java, no one is stopping you.

Please stay on topic.
[G1 Android Development] B-man007:
lol anyone think that the open source nature of android was used as a a pretense to help android gain a competitive advantage in mobile os? They've already got like 15 phones with android on them. now that they have footing, they want to use it to their advantage

edit: sorry! wrong thread
[G1 Android Development] nvk:
Moving forward

After you get tired of fuming at google for having a business, a business model, and for exercising their rights to do things they want to even if you don't like them... why not act like grownups and work within the rules.

Consider:

We're familiar with all sorts of work-arounds and compromises. From living with the imperfections of an OS rather than writing one's own, to stopping at stopsigns and red lights in the dead of night. Living in society means respecting the rules even when you don't like them.

But it's also useful to consider just what bothers another party (google) and why they invoke rules and rights. Google wants its software installed on new phones. That means providing an incentive to partners, like HTC and T-mobile. The opportunity to distribute a new software version is such an incentive. It's therefore valuable to Google, and Google may choose to protect it, by such means as the law permits -- even if they're awkward/imperfect/annoying to you. You, after all, aren't doing something in partnership with Google (remember, a partnership requires two willing partners, not one party wishing the other do what it's unwilling to).

These ROM's also create another problem for Google and its partners: they're so easy to install that lots of people install and use them, not just beta testers. And that generates support calls, and expense, for the partners. The partners' business model doesn't include supporting software they didn't generate, or reading your mind. (Just think about the support requests in the threads here.) Sorry, software support isn't free. (And I won't paint your house or wash your windows either.)

Hence the idea of stripping off proprietary software, rather than distribute it. Google's legal remedy in the above matters -- what the law provides, pre-packaged -- is a limit on distribution of software. It's no different from songs and music. If the user keeps and installs software that was legitimately provided by Google and its partners, Google doesn't have a legal remedy against ROM cooking and distribution of open-source stuff. (It might appease them still further if a boot-screen message warned about voided software warranty, as in reducing the frustration of a support call where the support person assumes, wrongly, that the software is standard.)

So just get over the insult that Google doesn't choose to sponsor ROM cooking, and modify procedures -- as clearly outlined in this thread -- to avoid violating the rules on intellectual property rights.

nvk
[G1 Android Development] digital_1:
That's not necessarily true. Some Linux distributions get around that all the time with the DVD Decryption library (libdvdcss2) by including a script that installs it rather than including the library itself.

e.g. sudo /usr/share/doc/libdvdread3/install-css.sh
[MDA Compact II General] salmanmukhtar40:
hello guys...

i have recently got the charmer but i am unable to install any cab or other file on the phone. it shows an error " .... is not a valid windows CE setup file'' so what am i missing. i will be thankful for ur help.
[MDA Compact II General] ChrBeck:
You are using the wrong cab files guy.
[Palm Treo Pro Accessories] Trombonez:
I've lost the L in Palm on the back of my Treo Pro. Where can I buy a new one? Anybody? Thx!
[Palm Treo Pro Accessories] pseudofilosofen:
I Bought one here:

http://stores.shop.ebay.com/VALLEYLIQUIDATIONCENTER__W0QQ_armrsZ1

Regards,

Anders H. - http://www.sophia.no
[Palm Treo Pro Accessories] Ineedtoys:
That's expensive! I got one from here, appears to be the geniune article, not a copy, and price is pretty good too.

http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=290327163330

I've put a spare safely away in the box so when I come to trade the Treo it'll have a nice brand new cover on.