yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] whatsitsnamenow:
The latter 2 are still Sense Roms. Vael just strip all (most) of the Sense. There is no way now to get the HTC mail program to work with CM6(I know as I have tried multiple times). Your best bet is try K-9 mail (which is great). Or you need go back to a Sense Rom. All the Roms are Sense except CM6 and SuperEVO. Be aware that some of these Roms does not have the HTC mail program anymore, but since they are Sense Rom all you do is find the HTC mail.apk and install it.
[EVO 4G Q&A, Help & Troubleshooting] lowspeed:
Does k-9 work with exchange? I tried setting it up giving me errors.

Also is it still push email ?
[EVO 4G Q&A, Help & Troubleshooting] whatsitsnamenow:
I never tried it with exchange so I am not qualify to answer that. It doesn't do push email yet but neither does the android email or the htc mail. All of them are timed polling. The only one that does push email is the stock gmail app. I email myself and gmail is almost instant but of course it doesn't help if you have other email accounts. For me its the best option right now. Its free so can't hurt to try it out.:D
[EVO 4G Q&A, Help & Troubleshooting] lowspeed:
Just FYI, Both stock and htc mail will do push email on exchange.
[EVO 4G Q&A, Help & Troubleshooting] tdusen:
K9 does Push email, if you're connected to an IMAP server that supports the IDLE extension.
[Droid 2 General] mikejs78:
Anyone know where I can find a tun.ko for the Droid 2? Trying to set up VPN Connections for a colleague to connect to a Cisco VPN. I have it working on my X. Is a different tun file needed or would the same one work?

Thanks.
[Droid 2 General] psionicalpha:
I'm relatively new to the whole android thing (as the droid 2 is my first droid phone), but my understanding is that because moto hasn't released the source yet, it is impossible to compile a tun.ko. The tun.ko for the droidx won't work because it is a different version of the kernel than the 2 is running (.29 vs .32, I think).

I've been looking for this as well, as I'm unable to connect to my work vpn over 3g (but works fine onw ifi), which is really the only thing that is making me miss my iphone at this point. Hopefully once moto releases the source, we'll get a tun.ko that will let us use the aftermarket vpn solution (rooted, of course).
[Droid 2 General] natez0r:
I know this is an old thread, but I figured I would reply and say that I was able to get the one posted on this forum:

http://www.droidforums.net/forum/motorola-milestone/79613-looking-tun-ko-motorola-milestone.html

working. Here is the direct link:

http://www.saturnwiki.net/droid_tun_driver/2.6.32.9/tun_alt.ko

This works for my kernel 2.6.32.9-g462500f.

Hope this helps someone.
[Droid 2 General] aredubya:
Outstanding - I've been searching high and low for this info. However, what I don't know is how/where to load the file. I have a rooted Droid 2 running ApeX 1.0.2.5, so presumably, all I should need to do is get this tun.ko object dropped in the right place, set up openvpn.conf properly and it'll work. I'm not sure where to drop it though. Any hints?
[Droid 2 General] KnightCrusader:
I got the tun.ko from this location, and I am having the same problem that the person on droidforums was having - I can make a connection, but I am not getting a DHCP address from my server.

Did you have this problem at all? I can't figure out if the tun.ko file isn't compatible, or if my configuration is wrong. (And I tested my configuration on a Windows machine - it works fine).
[XPERIA X1 Android Development] eLeMent225:
I got the android 2.2 releases from tremere (26/7)

i copied it on the sd card and run the haret.exe but an error shows me that it can not start because of an unsigned code or a missing component

the release 2.1 from the howto worked.... after trying the new one the 2.1 is not working too with the same error

can anyone help me please ?
[XPERIA X1 Android Development] cyberdesigner.net:
please read the howtos again and carefully... then follow them step by step.

it is working!
[XPERIA X1 Android Development] eLeMent225:
ok i did it again with the howto for the 2.1 version but it doesn´t work ...
[XPERIA X1 Android Development] CARAVELLE-II:
Haret problem

Hi

Where you able to fix the problem? I have the same problem
[XPERIA X1 Android Development] radzix27:
Have you overclocking your Xperia? Haret starts only with stock speed ;) (means 528MHz)
[XPERIA X1 Android Development] naklar:
The only way I found to resolve that error was to do a hard reset.
[XPERIA X1 Android Development] calvinfoo:
Have u tried formating the sd card with hp format tool? If it doesnt work maybe buy a new sd card or flash a new rom for xperiax1 should do the trick....
[XPERIA X1 Android Development] CARAVELLE-II:
Same problem

Sorry guys i forgot to say is a htc hd2
[XPERIA X1 Android Development] matejdro:
Um, then what are you doing in X1 forum? Releases are far from being compatible. Go to HD2 forum then.
[HD2 General] receptor123:
Hello everyone

I looked every place and tryed everything to make that igo primo motherfu. work on my hd2 USA, and always have the same problem. Its stop at igo load screen and stops milímeters before compete. I even tryed new rom and i got the same problem. Now my HD2 has the stock rom and radio 2.10.50.26. Does some one could help me make Igo primo work at my HD2? :confused:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] petersonldp:
I downloaded the ROM RUU_Rhodium_S_HTC_PTG_1.86.410.0_Radio_Rhodium_4.49.25.17_Signed_Ship, available right here in the forum, go to the rom for my TP, I realized that the ALT has not worked, or the special functions of the QWERTY keyboard does not work . I wish my colleagues gave me a suggestion to solve the problem due. I thank everyone's attention. Hugs.

:o
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] steviewevie:
What model of phone do you have exactly ? It is an AT&T one or a T-Mobile one ? I wonder what keyboard layout you have.

Is this a Portuguese ROM ? Sorry I am not sure exactly what this ROM is, I realise it's an official one.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] petersonldp:
Good afternoon, my device is HTC Touch Pro2 T-Mobile, I'm from Brazil, and how has WM6.5 rom with PT-BR, I chose one that is en_US. Layout of it is English Universal. PORTUGUESE ROM is from Portugal. It is an official ROM, only unlock the SPL to accept other ROMS. Any help will be of good use. Hugs
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] steviewevie:
ok, so you have a T-mobile branded phone ? Then it has a different keyboard layout. You should be able to find a cab file that will give you the keyboard layout for T-mobile if you do a search ;)
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] usehgal:
Hi. This is one of very few message I've posted. But have found some great information through the site and its members.

I had the UK spec HD2 and enjoyed using it, few months into owning it I installed some custom firmware and trying a few different Roms.

Last month the phone literally died, I couldnt turn it on, charge it or do anything. Even though it worked perfectly for months.

I sent it to HTC, and they said they will charge me £180 to repair as the "illegal" firmware was on the phone. The warranty states that only is the modification is the reason for the fault can the warranty be void. They would not clarify that the firmware was the cause of the phone being broken and instead insisted that simply because the firmware was on it the phone was out of warranty.

i had three long phone calls with the customer support guy telling me that any modification would void the warranty, to the point where he told me if you use a set of headphones that did not come with the phone this is technically voiding the warranty. Even though I clearly read out their own warranty wording which stated that the modifcation should be the cause etc....

In the end they changed there tone and sent me a simple email to say your warranty is void because we believe the firmware broke the phone. Even though the phone was running fine for months. If there anything I can do or has anyone else had any experience ?
[HD2 Android Q&A, Help & Troubleshooting and Genera] fischerben:
hi,

i don't now if this is the right forum to ask for this question

i have installed froyo 2.2 on my hd2, i have one problem, and that is with the Gps i can't get any signal it just seeking and seeking, when i go in to google maps or navigation, could anybody help me with that problem
[HD2 Android Q&A, Help & Troubleshooting and Genera] polo735:
Did you make sure that GPS is enabled? Do you have a clear view of the sky? What build of froyo specifically are you running? What radio?
[HD2 Android Q&A, Help & Troubleshooting and Genera] daemonfly:
I'm running Bangsters 1.2a and it takes forever to find a GPS signal, but especially with Google apps. Waze seems to fair a bit better, but no where as fast as back in WinMo.
[HD2 Android Q&A, Help & Troubleshooting and Genera] fischerben:
yes i turn gps on and i can see in top op the screen that it is seeking, i have tried outside, inside but same result.

iam running this http://gamesquare.co.uk/froyo.html but it stands version 2.2 in my phone. and radio 2.12.50.02_2

but can it be because i run dutty's leo sense as winmo os
[HD2 Android Q&A, Help & Troubleshooting and Genera] polo735:
Thats strange. If I were you I'd just keep trying different radio/rom/android build combinations. If you never get it working then it may be a hardware issue.
[HD2 Android Q&A, Help & Troubleshooting and Genera] buzz killington:
Where are you located? In many (most/all?) builds if you're not in the U.S. you have to edit the gps.conf file to give the gps your region.

Start here and see if it helps.

http://xdaforums.com/showpost.php?p=7278623&postcount=1

It's probably related to the gps.conf, search for more information if it still doesn't work. The HD2 gps locks on quite fast with the a-gps assist. Faster than all of my pnd and golf gps devices except Garmin with its hotfix.
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.

Finding update package...

Opening update package...

Verifying update package...

E:failed to seek in /cache/update.zip (Invalid argument)

E:signature verification failed

Installation aborted.

If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.

Any ideas?
[Droid Incredible Q&A, Help & Troubleshooting] jdmba:
...

I believe the standard array of initial questions would be:

1) Did you flash S-OFF?

2) Is your card FAT32 formatted

3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
Yes.

Yes.

This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.

On a side note, I've tried wiping cache in ROM Manager as well.
[Droid Incredible Q&A, Help & Troubleshooting] smtom:
Toggle Signature Verification and/or is d/l corrupt?

In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?

Also, I read some superb advice here:http://http://xdaforums.com/showthread.php?t=765930

check out the advice in post # 285 and see if that fixes you up.
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...

Here's my device setup...

Radio - 2.15.00.07.28

Kernel - King's BFS #4

ROM - SR Vanilla RC 2

CWM Version - 2.5.0.5

ROM Manager Version - 2.0.2.6

Here's a process I'm following...

1. Open ROM Manager

2. Clear Download Cache (Just to be sure!)

3. Select Backup Current ROM which causes reboot into recovery.

4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*

5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.

6. The backup progresses like it should have after the first reboot.

Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.

Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.

I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
[Droid Incredible Q&A, Help & Troubleshooting] akpe:
I had the same problem trying to flash the latest leedroid

I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.

Flashed normally and up to now it looks like it worked (waiting for first boot)

Hope this helped :)
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
[Droid Incredible Q&A, Help & Troubleshooting] smtom:
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
[Droid Incredible Q&A, Help & Troubleshooting] PIYIRIO:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.

*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
[Droid Incredible Q&A, Help & Troubleshooting] PIYIRIO:
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
[Droid Incredible Q&A, Help & Troubleshooting] smtom:
Interesting.... Please post as this shakes out.
[Droid Incredible Q&A, Help & Troubleshooting] srt4mn:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.

If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
[Droid Incredible Q&A, Help & Troubleshooting] jbdan:
Me as well
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
I've reached out to the developer. Hopefully we will hear from him soon.
[Droid Incredible Q&A, Help & Troubleshooting] Koush:
Can you guys try clearing your download cache, and then reflashing recovery?
[Droid Incredible Q&A, Help & Troubleshooting] Pedro80:
Possible workaround

Cache wipe have been tried, see post #3.

I have some info that may be valuable:

This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out :-P

I observed the _exact_ same behavior:

- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)

- Tried DL cache wipe in RomManager,

- Tried reflash of recovery

This fixed it for me:

- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img

- Re-flash CM (this may be optional, I don't know)

- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)

- Allow RM to flash 2.5.0.7-bravo via download

- Now "Backup ROM" and "Reboot to recovery" works as intended

- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)

Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
[Droid Incredible Q&A, Help & Troubleshooting] VCURamEngineer:
Worked for me. Thanks Koush!
[Droid Incredible Q&A, Help & Troubleshooting] buckweet:
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..

i'm using virtuous 2.7
[Droid Incredible Q&A, Help & Troubleshooting] Oldtymehockey:
I am having this issue when I attempt to back up a current ROM or partition my SD card through ROM Manager.

I get an error in ClockworkMod Recovery v2.5.0.5. When the sequence goes to:

Verifying update package...

E:failed to seek in /cache/update.zip (Invalid arguement)

E:signature verification failed

Installation aborted

When I got my new Kingston card (that was replaced on warranty) I ran a Titanium Backup and created an update.zip.

Then, as mentioned above, I attempt to back up my current ROM in ROM Manager and the problems start.

I may try to run the sequence that originally created the update.zip file when I originally rooted. That is all I can think of that might work.
[Droid Incredible Q&A, Help & Troubleshooting] jonimalabarea:
I solved this problem changing the ClockworkMod from 2.5.0.7 to 2.5.0.0 version on my htc desire. The last option of Rom Manager "All ClockworkMod recoveries" allow to choose the version.

good luck!
[Droid Incredible Q&A, Help & Troubleshooting] cupidicious:
this works!!

Thanks for that. If you try switching and it doesn't work the first time, try again. f.y.i. I was trying to partition by SD and kept getting the same error messages. Changed to 2.5.0.0 and was able to partition!:D

Been looking for a resolution of days!
[Droid Incredible Q&A, Help & Troubleshooting] Spannaa:
I had the same problem on my HTC Desire and this worked for me.

Thanks.
[Droid Incredible Q&A, Help & Troubleshooting] unixslave:
This is the correct procedure...

captivate
[Droid Incredible Q&A, Help & Troubleshooting] welshyoot:
Sorry to sound thick, but how would you clear the download cache?
[Droid Incredible Q&A, Help & Troubleshooting] baram:
have you tried hitting menu?
[Droid Incredible Q&A, Help & Troubleshooting] welshyoot:
Um.. from where mate?
[Droid Incredible Q&A, Help & Troubleshooting] NilsP:
The problem is more than likely that you have a ROM installed that does not have the correct root permissions set for superuser. Because of this ROM Manager is failing to write/post everything it needs for the action in the boot to recovery. In other words, the action is set but ROM manager is not authorized to boot into recovery. That's not technically correct but it is what happens.

Copy another/different ROM to your SD card and flash it in recovery. Your problem should be solved.

It is generally caused by either a bad set_perm or symlink for su in the update-script or it got clobbered (technical term HaHa) some where along the line. That is why the binary fix permissions (outside of ROM Manager) sometimes helps.
[Droid Incredible Q&A, Help & Troubleshooting] general714:
Thanks so much, this was driving me nuts. Your solution works like a charm. Cheers! :D
[Droid Incredible Q&A, Help & Troubleshooting] smithey253:
worked a treat! Thanks a lot.
[Droid Incredible Q&A, Help & Troubleshooting] SirMille:
Worked for me too! HTC Desire.

Hit the MENU button inside ROM Manager, then clear the download cache.

After that go to ROM manager again, and you can flash recovery.
[Droid Incredible Q&A, Help & Troubleshooting] bunchesinoz:
Worked the charm on HTC desire.. you da man!
[Droid Incredible Q&A, Help & Troubleshooting] nooby10:
Hi all,

had same problem when flashing to new rom using Rom Manager:

Revolutionary CWM v4.0.1.4

Finding update package...

opening update package...

Verifying update package...

E:failed to seek in /cache/update.zip (Invalid argument)

E:signature verification failed

Installation aboreted.

Solved it by:

after getting above message, simply pull out battery, replace battery, manually go into boot recovery (vol. down/power), Rom Manager automatically started up and installed rom.

Not sure why, maybe I was just lucky! http://media.xda-developers.com/images/smilies/biggrin.gif

Hope this helps!
[Droid Incredible Q&A, Help & Troubleshooting] mishuxp:
How it worked out for me...

I had the same problem.

All i did was go into Rom manager and flash a previous version of CWM, v4.0.1.4.

Rebooted then in recovery mod and all went great from there
[Droid Incredible Q&A, Help & Troubleshooting] onejester:
ClockWorkMod Failed To Seek In...

"Originally Posted by NilsP

The problem is more than likely that you have a ROM installed that does not have the correct root permissions set for superuser. Because of this ROM Manager is failing to write/post everything it needs for the action in the boot to recovery. In other words, the action is set but ROM manager is not authorized to boot into recovery. That's not technically correct but it is what happens.

Copy another/different ROM to your SD card and flash it in recovery. Your problem should be solved.

It is generally caused by either a bad set_perm or symlink for su in the update-script or it got clobbered (technical term HaHa) some where along the line. That is why the binary fix permissions (outside of ROM Manager) sometimes helps."

Hi I tried everything in this thread using ClockWorkMod

E:failed to seek in /cache/update.zip (Invalid argument)

E:signature verification failed

Galaxy s2 GT I9100 ICS 4.0.3

Carrier Orange

Kernel 3.0.15-I910000XWLP7-CL340913dpi@DELL134#3

It was the same story with gingerbread so I tried updating the firmware via kies thinking this may fix the problem. It didn't.

I just want to back up the original configuration before I go experimenting. Are there any other ways to do this in case of a problem (if I cant get clockwork mod working)? If I'm understanding correctly, if I do as NilsP suggests there's no way of reverting to the original?

NB I already purchased and tried the Droid3 bootstrap recovery which when asked to reboot into recovery, just robots the phone into normal mode.

Thanks guys

Edit/Update: Flashing of CRM v4.104 worked (it didn't before). I had to go back and do it twice. I actually picked this tactic up previously in another post somewhere, but it didn't work with gingerbread rooted config.

I hope this saves time for anyone with this problem.
[Droid Incredible Q&A, Help & Troubleshooting] froelibt:
same exact problem

I am also having the exact same problem with the ¨failed to seek in /cache/update.zip when rebooting in recovery mode from rom manager

and am also having the exact same problem with fix permissions utilily in rom manager. if you find answers please let me know
[Android Apps and Games] FrstdOne:
DownloadManager from Redsea Software has been removed from the Market. I have the other software from that developer but it requires DownloadManager to work fully.

I spent an hour and a half scouring the Internet last night trying to find it and all I've come across are broken links.

If anyone could upload the .apk for DownloadManager from Redsea Software I'd be really appreciative.