yashsingh1/xdaforums huggingface dataset:
[Desire General] EddyOS:
Vodafone Desires aren't on 2.2 yet, only unbranded generic WWE Desires so I assume this is what you have...check the S/W version on your Desire, 2.09.405.8 is generic
[Desire General] cardiak:
This is exactly what I have. I guess my supplier just sent me a generic then.
[Desire General] cardiak:
Can anyone else help?

Is there a way say I could re-flash the radio without root or something?
[Desire General] u1008:
Try with the application "GPS Test" from market, it was able to get GPS lock om my phone after the 2.2 update when google maps couldn't.

Not sure why but I don't see any harm in trying.
[Windows Mobile Themes] rouzbehali:
Instructions :

1 : Download the files and copy them to your storage card

2 : replace the "welcomehead.png" with GTX Splash Screens (use Resco file explorer.etc )

3 : Perform a Soft reset

4 : Enjoy

5 : Leave comment :rolleyes:

these PNGs don't include the top black area you see in this post

Important NOTE : Please make a backup before replacing png files

_____________________________________________

-Visit my other works (Windows 7 Splash Screen) for WVGA and VGA devices

_____________________________________________
[Windows Mobile Themes] joshzzz2001:
nice skins! they all look good, i don't know which one to choose :)
[Windows Mobile Themes] andreimoto:
QVGA version please... ;)
[Windows Mobile Themes] SiL3nTKiLL:
they all look pretty cool!
[Windows Mobile Themes] mike2nl:
Cool looking. But which one i will use.. big apples, small apples every time these decisions :D. One more peace of amazing things for the long-life GHTX-CHT combination, yes...

EDIT:

#4 looks very cool on startup.
[Windows Mobile Themes] the show stopper:
do i have to rename the welcomehead.png ?
[Windows Mobile Themes] rouzbehali:
no need to rename.just copy and replace it
[Windows Mobile Themes] Pandemoniumone:
Thanks for sharing bro, very nice!!
[Windows Mobile Themes] navonils:
Thanks !!

IT WORK on MY w900 AS THE FILENAME WAS "WELCOMEHEAD.96.PNG" . I HAVE TO RENAME THE FILE..!! ADD SOME NEW THEME... PLZ
[Windows Mobile Themes] rouzbehali:
I'm glad you like them :)
[myTouch 3G Slide Q&A, Help & Troubleshooting] poetik517:
well i never thought i'd be writing one of these threads but the time has come.

i'm stuck in a bootloop after updating and flashing the latest superuser provided here. i downloaded the eclair/froyo version as i am running eugene's slidemeroot5r1 (eclair). after i flashed via recovery, i thought everything was fine since i got the "installation complete". however, after the reboot, i was greeted by the normal black bootup due to the rom i'm running, but it stayed.

i do not have any backup of any kind to restore. so where do i go from here? any help would be greatly appreciated. thanks.
[Vibrant General] Welshy992:
It seems to happen after the phone has been on for an extended amount of time. I don't have lag, and I'm not using the gps when it happens. In fact, it usually happens when I sleep. Has anyone else experienced this? My phone is not modified. I'm even running plain touch whiz. I'm considering returning if I can't resolve with a hard reset. No third party apps are running when this occurs. I routinely close processes before I stop using the phone. I love this phone, I'm just worried I have a bad unit.
[Vibrant General] bstromberg:
i'm having a similar issue, but with a rooted vibrant. the problem has spanned across two different handsets. the first one i rooted almost out of the box. but after a few days it started locking up after sitting for a while and i would have to pull the battery to get it to come back on. so i returned it, got a new one and held off rooting it to see if this one would do the same thing. the non rooted one had no problems at all, so i bit the bullet and rooted this one too, and sure enough later that same day it started doing the same freezes when trying to unlock it.

as soon as i rooted the second phone i downloaded rom manager and made a nandroid backup. after the backup i proceeded to remove some of the bloat, like dual clock, the startup/shutdown sounds, and some of the other crap that the vibrant comes with. i also installed and started up setcpu. it seemed that after i did all of this is when the freezes started up again. so i did a restore to before i removed all that stuff and now the phone is fine again. what is it about my process that is making this phone lock up like this?

EDIT: nevermind...i found some other people with the same problem in a setcpu thread...seems setting the sleep profile too low will cause the phone to not wake up after sitting too long
[Vibrant General] Welshy992:
Uh, I'm not getting any freezing, but I know there is an issue with SetCPU. A certain setting will causes problems on the Vibrant. My issue is just unexpected reboots after the phone has been on for approximately 170 hours.
[Vibrant General] PePPaZ:
I had many random restarts and general craziness from my non rooted stock vibrant. A factory restore fixed all problems.
[Vibrant General] Welshy992:
Yeah, if it happens again I'm going to try a factory reset.
[Droid Incredible Android Development] Starfire-1:
UPDATE: As you can see from the page 5 and some good trial and error, the port may be related to Chrome to Phone. Whew.

I am posting this as a separate thread as I do not know the extent to which my observation applies...

Recently I flashed the SkyRaider 2.2 Sense ROM (updated the radio, no extra apps etc.) and found the ROM to be great - everything worked.

As I am a Linux geek as well - Using the busybox utilities I checked for open ports on the phone. As with the stock ROMs, two TCP ports were open for dmagent and com.htc.bgp. However, there was also a UDP port (13010) that was open.

/system/xbin/netstat -p

did not identify the process that opened the port, although it did identify the processes that opened the TCP ports.

The reason netstat could not identify the process is because it could not map the inode of socket handle to a process listed under the /proc directory.

If you see an open port on your phone, then

cat /proc/net/udp

and you should see a line of information for the open port and an inode number (for me it was 104)

For running processes, there is an information directory under /proc/<pid> (e.g. /proc/2435) and below that and fd subdirectory with handle numbers for files and sockets. So for example if you

/system/xbin/ls -l /proc/<anypid>/fd

you may see something like

5 -> socket:[<inode>]

The problem with my ROM is that there is no process with a # -> socket:[104] in its fd directory. So I don't know what opened it, if it is still open or what would happen if I hit the port with a datagram.

So my question is - are other SkyRaider 2.2 Sense people seeing the same? Are other leaked Froyo derivatives seeing the same?

As I don't like to run around with apparently open and unidentified ports, I reverted back to stock.

P.S. I PMed the SkyRaider author and he replied that he did not know what the port was and I have not heard back - so I thought I should at least post what I have seen so that others can look into it. Maybe I'm just too paranoid. :)
[Droid Incredible Android Development] Nic2112:
This could be random, but it seems that port 13010 is used by a Trojan type virus.

Protocol	Service	Name

tcp	*****Controller	[trojan] *****Controller

tcp	HackerBrasilHBR	[trojan] Hacker Brasil - HBR

tcp	HackerBrasil	[trojan] Hacker Brasil - HBR
[Droid Incredible Android Development] obededom:
can somebody explain this in simpleton terms?

...cause it sounds like shizzle just got deep.
[Droid Incredible Android Development] Starfire-1:
I in no way want to panic anyone - or even state for certain that this is any more than a weird oddity on my phone.

In simple terms - programs can open "listening" ports on their computer (or in this case the phone as it is Linux under the hood) so that external computers can connect and communicate. There are all sorts of protections that can be applied, firewalls, and binding open ports to certain interfaces,etc.

In my case I saw a port open that I could not identify to originator (process) that was bound to any interface and by default the iptables firewall is down - so it is open. The big difference between TCP and UDP is that TCP sets up a "pipe" between the computers whereas UDP accepts little messages one at time.

I'm only bringing this up to see if anyone else sees the same thing.

If not - I am honestly sorry for having brought it up. But for safety's sake I thought I should at least post what I saw.
[Droid Incredible Android Development] Starfire-1:
I saw that too although it probably is unrelated to this (a Windows trojan for example). But the port number was ominous.
[Droid Incredible Android Development] drkramm:
Im sure 90% of the ports on Windows are ran by trojans .. and I'm also positive that anyone that write in a Trojan for Android would pick a different port ... that being said I'm still interested to know what's goin on with this port
[Droid Incredible Android Development] Ruoh:
Is that possibly the port which Google uses to remotely shut down phones/apps/etc?
[Droid Incredible Android Development] opcode1300:
http://androidspin.com/2010/08/10/first-android-sms-trojan-released-into-the-wild/

maybe..
[Droid Incredible Android Development] Starfire-1:
Your search is under process 104. In this case, 104 means inode 104 (that is an entry in a file system table). The problem is that any of the (many) processes that are listed could reference this.

Try

/system/xbin/ls -lR /proc | grep 104

and or

/system/xbin/ls -lR /proc | grep socket

I saw a bunch of socket inode references to 104x, but not 104.
[Droid Incredible Android Development] shamowfski:
I didn't install any media players.
[Droid Incredible Android Development] shamowfski:
Tried:

# ls -l -R | grep socket:[104]

ls -l -R | grep socket:[104]

No results.
[Droid Incredible Android Development] figasse:
# find -inum 104

find -inum 104

./sys/devices/platform/msm_serial.0/power/wakeup

#

No idea though why wakeup could use udp port for anything :)
[Droid Incredible Android Development] kriskmk:
wow.. this is interesting.. and I think we should thank the OP here for bringing it to light.. It raises a serious question.. since we are all blindly downloading custom ROMs made by people we do not know (in the real life)... how safe are these ROMs in terms of invading our privacy?

Jeez.. someone could easily roll a trojan along with a custom ROM and open up a port to squeeze out TONS of information.. I mean.. lots of people use apps on their android phone for banking etc.. not to mention our gmail user account and password.

How do we know all of this is safe and is not being siphoned off by the creators of these ROMs?
[Droid Incredible Android Development] adrynalyne:
Crud, you are on to me. I guess I will head for a non-extradition country once I am done siphoning the bank accounts of my rom users.
[Droid Incredible Android Development] Asterdroid:
It's cool, I love your work. You can keep my 3 dollars.
[Droid Incredible Android Development] larsrya8:
Was it 104 for you?
[Droid Incredible Android Development] adrynalyne:
Awesome!

:D
[Droid Incredible Android Development] RLKirk:
lol, that made me giggle
[Droid Incredible Android Development] Asterdroid:
I'm just pissing into the wind here as I know nothing about Linux, but could all of the above be related to the supposed security issues with Tapatalk? Might be something to look at.
[Droid Incredible Android Development] kriskmk:
No need to get offended.. I am not pointing fingers at anyone in particular.. I am only asking a reasonable question. The fact that this is such an open ecosystem.. it gives plenty of opportunities for someone to do mischief.. what is our protection against it (other than the obvious).
[Droid Incredible Android Development] adrynalyne:
Back to a serious, and less paranoid, note.

This may be the port that Google has shown they can use to remove software from Android phones .

There was an article on that recently where Google scrubbed both an app from the market, and from user phones. I believe it was a proof of concept for some sort of security bypass...?

Or, perhaps its the port used by chrometophone.

Just some thoughts.
[Droid Incredible Android Development] adrynalyne:
Oh, I was very offended. How dare you?!

HOW DARE YOU?
[Droid Incredible Android Development] kriskmk:
oh it's pretty simple trust me.
[Droid Incredible Android Development] opcode1300:
It IS a valid concern.

I dont think many users put

much if any

thought into the security of the apps and ROMs they use until it is to late. I dont think any of the well known users on XDA would do anything to damage the community. But oblivious users will be an issue the AndroidOS will need to deal with.

It's the price for freedom.
[Droid Incredible Android Development] adrynalyne:
You guys are hilarious. It was a tongue in cheek comment.

If you think my above comments re: siphoning bank accounts were serious:

--Take your ball and go home. ;)
[Droid Incredible Android Development] kriskmk:
but is there some built-in firewall in the Android OS that cannot be tampered with and form a part of the core? How easy or difficult is it for someone to slip in a trojan that reports back with information?
[Droid Incredible Android Development] Starfire-1:
If netstat says that you have an open UDP port that is LISTENING, then

cat /proc/net/udp

You will probably only see one line of data but over on the right will be the inode number associated with the socket.

@figasse had an interesting find - had not thought to use find this way. Might give us a hint as to where to look in the official sources. Kind of hints at the "Power on LAN" function for some PCs where you send a datagram to a "sleeping" computer and it wakes it up.

BTW - although I am new to rooting and ROMs, I do appreciate the work that authors put into their offerings. I just need to answer the questions before I feel good about accessing sensitive info via the phone.
[Droid Incredible Android Development] opcode1300:
That was not directed at you, but meant to get others to think about what they do before they start screaming that android sucks, ROM Dev's are evil hackers out to punch babies, etc

p.s

I'll play with my balls right here thanks! =)
[Droid Incredible Android Development] figasse:
Yes, it was 104 on my phone as well.
[Droid Incredible Android Development] adrynalyne:
Just leave it off the webcam, ok?

:D
[Droid Incredible Android Development] Asterdroid:
(In my best Martin Lawrence voice) This **** just got real.
[Droid Incredible Android Development] adrynalyne:
I myself don't punch babies.

I do kick kittens, however.
[Droid Incredible Android Development] acidbath5546:
Interesting read.....

And we all know that part of cooking WinMo ROMs came with the requirement of first Kicking kittens...then stomping frogs and then punching babies ....

Adrynalyne did u forget the order so quick...for shame sir ;)
[Droid Incredible Android Development] Starfire-1:
So a little more digging...

Over at the android source tree, msm_serial.c source file seems relevant to the figasse's find.

It looks like tty console interface code, but nothing in the code yells out that it is intended to deal with IP interfaces (network). Serial interfaces are usually the clock/data/hardware stuff, but they can be a primary command interface.

It's quite a coincidence that an open network port is possibly intermingling with a low level command path. It may be legit (maybe someone closer to the source could comment), but I'm not feeling too good about it.
[Droid Incredible Android Development] Starfire-1:
Unfortunately that's the problem. :) If a process opens a socket by the normal means, there should be a socket:[104] somewhere in the tree.
[Droid Incredible Android Development] mobilehavoc:
FWIW, I have the same UDP port open and listening on my phone which has the new 2.2 OTA leak installed...not Skyraider. Can someone perhaps try this on a 2.1 rooted phone? Wonder if it has to do with Froyo send to phone functionality?
[Droid Incredible Android Development] Starfire-1:
Im back on rooted, stock 2.1 and a netstat -lpn only shows the two TCP ports that I believe are legit (at least they identify themselves).

One thing that I did right after I discovered the open port was to block incoming data with the iptables firewall. You would do this via adb shell or a terminal program as superuser and

if you run

iptables --list -v

you should see all "chains" with the default ACCEPT policy (i.e. wide open)

iptables -A INPUT -p udp -m udp --dport 13010 -j REJECT

run the first command again and you should see the blocking rule. If you reboot the phone though, you'd have to do it again.
[Droid Incredible Android Development] adrynalyne:
Try chrometophone with it blocked.

If you are willing, of course.

I am curious if it still works.
[Droid Incredible Android Development] Starfire-1:
Good one! It also occurred to me for any one out there with a legit, pristine Froyo - you should be able to type

netstat -lpn

without root. If you do, please let us know if you see the open UDP port.
[Droid Incredible Android Development] mobilehavoc:
I'm rusty on my Linux commands...how do I monitor the port with auto refresh? I want to watch while doing a chrometophone transfer to see if I see activity.
[Droid Incredible Android Development] Starfire-1:
I *think* if you flush the chain

iptables -F INPUT

and put the same rule in with "-j LOG" at the end and then the reject rule, it should log the access attempt. Where on the phone the log file is ... that I don't know. :D
[Droid Incredible Android Development] fiveoh:
I applied this and chrometophone no longer works. After rebooting the phone it works again.
[Droid Incredible Android Development] adrynalyne:
About as pristine as I can get...but its a leak no matter what.

Uploaded with ImageShack.us
[Droid Incredible Android Development] mobilehavoc:
KNEW IT! I love Chrome to phone by the way.
[Droid Incredible Android Development] Nic2112:
Ah that makes sense, for chrometophone to work it needs a way to "push" the link to the phone so that would require an open port.

Of course that opens another door, if Google can push a URL to your phone, how secure is it? Could someone push things to other people's phones? Some more security concerns to ponder about :)
[Droid Incredible Android Development] mobilehavoc:
I was wondering why this would show up without the Chrometophone app installed and then I realized this functionality is part of Froyo.

http://code.google.com/android/c2dm/
[Droid Incredible Android Development] fiveoh:
Others.

Others obviously need to test this. Don't take my testing as an answer.
[Tilt, TyTN II, MDA Vario III General] acompres:
I Check the option to not charge when connected to usb, and it's unchecked, it will just charge, and not get detected by ActiveSync, and also when i go on bootloader mode It doesn't even recognize the cellphone this way, i think i screwed my cellphone :( Any way to fix it?
[Nexus One Q&A, Help & Troubleshooting] mezmer1ze:
Hi,

I'd like to try some ROM with HTC Sense, but don't know which one is the best when it comes to battery life and useability?
[Nexus One Q&A, Help & Troubleshooting] Vakman:
I would say use one that is on 2.2 to start with.

[ROM][FRF91] eViL's Q&D HTC Sense v.1.00 - base 2.09 Desire 720p video

http://xdaforums.com/showthread.php?t=730290

OR

[ROM] [v1.2] KiNgxKxNexus FroyoDesire2Nexus {8/7/10}

http://kingxklick.com/forum/viewtopic.php?f=3&t=14

Both are 2.2 Sense UI ROMs.

Both are just as usable.
[Nexus One Q&A, Help & Troubleshooting] Sparatan117:
Is there anyone who has made a rom to just add the sense UI materials to the already built rom, sorta like with themes where you don't have to flash a whole brand new rom.

(keeping in mind that the phone is already rooted)
[Desire General] desire888:
Im a bit confused as there seem to be a few methods to do this. I want to have an ext3 of 1024, so that rules out clockwork mod. I have managed to setup as2d using recovery-windows.bat. However I want to reformat and repartition again. Think the SD has been stuffing up.

which is the best method?

1. [Recovery] AM Desire Recovery v1.1 [27th June] Fake-Flash

2. [RECOVERY] AmonRA 1.7.0.1 Recovery R5 *UPDATED*

3. some gold card method involving r1-a2sd-desire-dalvik-fresh-signed

is a2sd+ dependent on the ROM flashed?? When setting up the ext I see no option of enabling a2sd+

also once all is this is set up, can I just reformat the fat32 partition in windows7 if required? what is the recommended allocation unit size?

Thanks!
[Desire General] ephumuris:
I recommend amon ra r5 as its a permanent recovery image. The a2sd scripts are part of the Rom and not recovery. And once your ext is set up you can wipe the fat32 in Windows I'm sure.
[Desire General] desire888:
Tried unrevoked3 to flash recovery-RA-desire-v1.7.0.1-R5.img. I get the following error message

Device "/sbin/sh: getprop: not found

" is not supported at this time

is this due to using windows 7 64bit??
[Desire General] ephumuris:
Probably i'm no good with Windows specific. I used a Linux Live cd to do mine as it's almost automated.

However if you just want to sort your ext out then go with amon ra fakeflash. Like i said a2sd+ is not recovery dependant.
[Desire General] mmaacc:
Unrevoked has issues with Windows in general, better use Linux or MacOS. A Linux life CD will do just fine.
[Desire General] desire888:
what livecd do you guys recommend?

btw will something like this work?

cd /data/local

cat /sdcard/flash_image > flash_image

chmod 755 flash_image

./flash_image recovery /sdcard/recovery-RA-desire-v1.7.0.1-R5.img
[Desire General] kmetek:
try rom manager?
[Desire General] ephumuris:
I just used ubuntu live cd.
[Desire Q&A, Help & Troubleshooting] bobsie41:
I installed my froyo update on 31st Aug. and the same day i forced all of my apps to be installed to SD using ADB shell pm SetInstallLocation.

Since then i have installed numerous apps with a high percentage of the data being taken onboard my SD card as intended.

Today, all of a sudden, i find myself unable to install any apk getting a message 'installation unsuccessful.'

I have 66.61mb of phone storage available and 3.37gb remaining on my SD card.

On my SD card i have a folder '.android_secure' containing 114mb af ASEC files which i assume is the folder for the apps stored on my SD card but i am not really sure about this.

Could anybody advise as to what is the problem as i am really at a loss with this and don't know what to do.
[Desire Q&A, Help & Troubleshooting] bobsie41:
Anybody help please?
[Desire Q&A, Help & Troubleshooting] jamesmcuk:
Obvious I know but its not connected via USB in disk drive mode to the PC while you are trying to install is it. Sometimes its the simplest things
[Desire Q&A, Help & Troubleshooting] bobsie41:
Thanks for you're input but no it isn't.

I am not very clever with android so far but, am i correct in assuming no partitions are neccessary for apps to sd using this method.

All that i could think of was that there was no room somehow on the part of the sd card were the apps are installed.

Hope i am making sense as i am not really sure what i am doing but usually learn quickly!
[Desire Q&A, Help & Troubleshooting] jamesmcuk:
Hmm I have read that some roms haven't been to clever on unmounting the card after a reboot. Did this start happening following a reboot of the phone?

Space wise I think it should say insufficient space if its a space issue.

Maybe try mounting the card through the phone on the PC and then ejecting it properly from the PC. You could also try searching for info about SD cards not being unmounted on android.

Sorry cant be of more help.
[Desire Q&A, Help & Troubleshooting] bobsie41:
Thanks again for your input.

Yes, this did start after i loaded an apk to my sd card via my pc then tried to install it. This wouldn't work and also i was not able to install from the market.

I have tried your above procedure but it did not make any difference so will now try to investigate what you suggested further.

Thanks again.
[Desire Q&A, Help & Troubleshooting] geordie1976:
Is it because you are from the future?

(sorry - couldn't resist) :-)