Related
Ok i saw a few people wanting to find their MSL with out CDMA workshop or customer service. I'll show you how. (I guess this doesn't work for some who installed the OTA update. I installed the OTA and am rooted and it worked for me.)
1. Install aLogcat from the market (its awesome and free)
2. From your dial pad dial ##3282# when the EPST menu pops up select view mode
3.Open aLogcat let it run for a sec and let it catch up
4. Press menu then press send and select email
5. Enter your own email address and send it
6. From your computer open the email and hit CTRL and F at the same time it will bring up a search bar
7. In the search bar type in MSL and hit enter
8. You should now be looking at a line like this
I/EpstBroadcastReceiver( 2089): MSLCODE 1:+HTC_RMSL:######
the #s are where your MSL will be
9. You are welcome!!
I heard this doesn't work anymore after the ota. I have tried a similar method using the ame app but no luck. Does emailing the log make a difference cuz i just scanned the log on the phone looking for that msl entry.
Couldn't find it. Followed each step to a T.
I'm on the latest OTA, rooted, BTW.
They fixed it with the first OTA. If you can get back to a pre-ota stock then that works fine.
Otherwise the easiest way is to simply call Sprint and ask.
i never had OTA ( still don't ) and it still doesnt show anywhere...btw
adeyo said:
i never had OTA ( still don't ) and it still doesnt show anywhere...btw
Click to expand...
Click to collapse
Then you bought our phone with it already updated most likely. Because it works with the base ROM that the Evo was released with. It's how I got mine.
this should not be posted in the development subforum. An article stating the same thing, which afaik doesnt work any longer due to the first OTA, has already been created over a month ago. The easiest way is to call Sprint and ask them. It takes two minutes.
Mods, please move this topic to General or QA.
Thanks
geekykid said:
this should not be posted in the development subforum. An article stating the same thing, which afaik doesnt work any longer due to the first OTA, has already been created over a month ago. The easiest way is to call Sprint and ask them. It takes two minutes.
Mods, please move this topic to General or QA.
Thanks
Click to expand...
Click to collapse
As an FYI if you want the mods to move something (given that I doubt they have time to sift through every post of every thread) click the little ! icon on the upper right corner of the OP. That brings the post to their attention.
i have the ota (rooted) and it worked for me
if you want a good reason to give sprint customer service tell them every time you open an app that uses gps the phone crashes. tell them you need to reset the gps receiver using ##4772579# and you need your msl to do so. they didnt even ask me why when i asked for mine.
sugarsine said:
I heard this doesn't work anymore after the ota. I have tried a similar method using the ame app but no luck. Does emailing the log make a difference cuz i just scanned the log on the phone looking for that msl entry.
Click to expand...
Click to collapse
no i just find it easier to scan stuff on the computer especially since my log was 10+ pages
perhaps OP can change the name of this thread since it does work once the OTAs have been applied....hence it is wrong.
Bummer. No go in Froyo.
I'm posting this here because the LauncherPro forum is dead.
So I'm wondering, is LauncherPro Dead? The developer discontinued it? Can anybody give me some insight to why things are the way they are.
I'm new to the whole launcher scene, so I dont know the developer, i dont know the history of the site. At the moment im a customer whos paid, and got nothing but a failure of a site.
I bought pro few days ago, Direct Debit no eCheck nonsense, so payment is instant, (i buy a bunch of stuff direct debit and all come back instant). I received the unlock code email but the code didnt work, figured they'd be a delay.
Tried later, still not working...
Tried going to main website (launcherpro.com) and I get an error.
Access to the web page was denied.
HTTP Error 403 (Forbidden): The server refused to fulfill the request.
Click to expand...
Click to collapse
Tried going to the forums (launcherpro.com/forum/)
Access to the web page was denied.
HTTP Error 403 (Forbidden): The server refused to fulfill the request.
Click to expand...
Click to collapse
Tried going to the support (support.launcherpro.com)
Forbidden
You don't have permission to access / on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request..
Click to expand...
Click to collapse
...
So anyway figured they were having issues. Come back days later, Key still not working. Websites still not working, I had to proxy through just to post. Assuming outside US connections are being rejected for specific location requests.
I go to the request page, put in my email and get the lovely:
Sorry, we couldn't find that email address in the database. Please make sure you entered it correctly and try again.
Click to expand...
Click to collapse
How is this even flipping possible lol I get an email saying thank you! Here is your paypal email, here is your code, then later its like "oh no idk who you are!".
Email Fede, no reply, emailed again, replied saying go to the support forum. I would if I could flipping access it. So proxied through to support forum, posted a message, get an email confirming post: "Your support ticket ID is xxxx....", I click the link and hilariously get:
Error:
Ticket not found! Please make sure you have entered the correct tracking ID!
Click to expand...
Click to collapse
Why is the launcherpro system so messed up? Should I consider this a dead project and move on, loyalty is out the window.
I post here because this site is lively and hopefully I might get some clue as to what is going on, the launcher pro forums are like a wasteland.
What the hell you talking about man? check again works fine it maybe in your end.
No issues here accessing the site. I'm outwith the US.
If you can't access his site, how do you expect the code to be accepted? It contacts the server, so something is wrong between you and his server. But his box is fine and online.
Resolved The problem lied with DNS usage on ISP's in my area (Talktalk, Sky) which were not refreshing the new site but loading the old server, which was causing me to come up with the above post as the old server has not been used for 2 weeks, but is still accessible and not yet redirected. (Which it should be to prevent these sorts of issues) After changing to Google DNS I was able to get onto the site without the need of proxies.
I'd be happy for this thread to be locked.
Seems that HTC is finally acknowledging Peep's vulnerabilities and while not publicly releasing an update, they will send it out to people who request it...
http://blog.taddong.com/2011/02/vulnerability-in-htc-peep-twitter.html
It's about time they got a fix out for it!
By the way, the Tweet for @xdadevelopers went out saying this was for Android users, instead of Windows Mobile users.
We have published an article regarding this situation on our Portal
http://www.xda-developers.com/android/htc-peep-vulnerability-update/
How did you find the vulnerability, is there a packet analyzing tool for android?
No luck
I just received a response from HTC saying they have no idea what I'm talking about. I just sent them back a response with the linked article. Hopefully someone can get the update from them and post it here so we don't have to deal with them at all.
So is this Windows mobile only, or Android too?
Sent from my HTC Desire using XDA App
Lothaen said:
So is this Windows mobile only, or Android too?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I don't think Android uses Peep in its interface for Sense. I'm not 100% positive on that, but I know we've had an issue with this for WM for about five or six months now.
In trying to get a hold of this update, here are my responses from HTC so far for anyone interested.
Me said:
I just heard about the update to HTC Peep for Windows mobile users. I have an AT&T Tilt2 with Sense loaded on it. I was hoping you guys could send me the Peep update so I could use that tab again without worrying.
Click to expand...
Click to collapse
Kathleen said:
I understand how important it is for you to be able to update your Peep application. Unfortunately, we are not aware of an update for the Peep application. I have looked for the update and it is nowhere to be found. You will need to keep an eye on http://www.htc.com/us/support/tilt-2-att/downloads/ for updates for your device.
Click to expand...
Click to collapse
Me said:
I read about the security flaw in the HTC Peep tab back in August and never used it because of this. The Peep application discloses the username and password via a HTTP OAuth-related request during the initial sign in to anyone eavesdropping on the connection. It also exposes the username and password after the connection is established by having all of the requests from the mobile device to the Twitter service use a HTTP Basic authentication header even though the app is supposed to be using OAuth. For more information, please refer to this article: http://blog.taddong.com/2011/02/vulnerability-in-htc-peep-twitter.html
Click to expand...
Click to collapse
Lindsay said:
We have not made an official update, any updates found on 3rd Party websites are up to you to do the research and download yourself. Just know these updates are considered rooting on your Tilt 2, so make sure before you update you do the research.
Click to expand...
Click to collapse
Me said:
Then when will the update be made public? It is kind of a pain that I've waited for six months now to use a feature of this device because of a security issue. Also, how would this be considered rooting since I'm not using an Android device? Windows Mobile users have administrator-like privileges by default in this operating system. There is no such thing as rooting on a Windows Mobile device.
Click to expand...
Click to collapse
Lindsay said:
If you re-write the ROM it is considered rooting. If you can add any applications to the SD Card and install it to the device, that is not rooting. We do not have any information on any updates available for your device at this time. I apologize that we do not have any updates for HTC Peep.
Click to expand...
Click to collapse
Me said:
I don't mean to sound insulting, but rooting is not the same as flashing a custom ROM. Rooting is gaining root-level administrator privileges on a Linux based operating system. Windows Mobile provides this access to the user by default. There is no other setting for this. Android, being a Linux based distro, does not come with root privileges installed to protect itself from users inadvertently messing around with things they shouldn't. It is the same thing on desktop operating systems like Ubuntu, Fedora, and the like. Rooting is completely different from flashing a custom ROM, as you are suggesting. Either way, an updated Sense tab using HTTPS, as it originally should have done, would be as simple as installing a *.cab file. My question, then, becomes to whom should I address this issue to get further support should I decide to call about it with the information I have?
Click to expand...
Click to collapse
Lindsay said:
The fact is we do not have an update for your device at this time. I apologize for this, but at this time we do not have any updates.
Click to expand...
Click to collapse
Me said:
Yes, you mentioned that. I asked whom I should voice my concerns with since this is the case. I understand that you don't have any information to offer me. I wasn't questioning that. I would simply like to know where I should go from here as there has been a serious security flaw in this device for quite some time. I do not mean to insult you, if I have done so, and apologize if I have, but I want this matter resolved once and for all. Obviously, the users are not allowed to modify the HTC Sense code or this would have been resolved some time ago. If some users were allowed the Peep source code, this could be rectified very quickly with the SenseSDK, but as that isn't an option, I, and several others, look to HTC to provide support for their product and software. If it is simply a problem of my device becoming outdated, then the HTC HD2 (Leo_512, Leo_1024) has the same problem on the latest ROM image as well.
Click to expand...
Click to collapse
Lindsay said:
I have sent the forum you sent me to the appropriate department for review. If you would like to troublahoot you device I would be glad to further assist you, but at this time this email will need to be closed if there is no troubleshooting to be done on your device. Again, I have sent the forum to the appropriate department.
THREAD CLOSED
Click to expand...
Click to collapse
It doesn't look like HTC is playing ball here. I'm going to continue to try to figure this out as I would love to actually be able to use the Twitter tab for a change. I never really used it because of the security flaw that was found.
i contected taddong and they told me
yeah they told me they had no idea what i was talking about....i contacted "tadong" and they told me to sedn the link from there site regarding the issue to HTC and he would handle them if they wanted more info on it...i guess we'll see what happens
It doesn't look like HTC is playing ball here. I'm going to continue to try to figure this out as I would love to actually be able to use the Twitter tab for a change. I never really used it because of the security flaw that was found.[/QUOTE]
Uh... "If you can add any applications to the SD Card and install it to the device, that is not rooting."
Under that logic, if unrevoked forever ever releases a .apk to turn S-OFF, does that imply that merely doing that to get root access isn't rooting?
edit: this is what happens when companies aren't smart enough to release some kind of auto-app updater, separate from OTA updates. Stuff like this takes an eternity. How hard is it to add an "s" to the http of the authentication? (for that matter, why the hell is Twitter letting you log in this way in the first place?)
lol, first thing i thought of when i saw this posts title...
http://my.starstream.net/neobigd/htc_peep.jpg
HTC finally release the Peep security update for the Rhodium, Topaz, Leo, and Photon. I've attached the files to this post, but they can also be had at HTC's website at the link below.
HTC Peep security update
EDIT: These updates do not work with custom ROMs, it seems. The *.exe needs to be copied to your device and run from there. I'm working on extracting them and making proper *.cabs now.
Peep Update *.cabs
EDIT: DO NOT PM ME ABOUT THIS FIX. IT DOES NOT WORK.
Please do not PM me about this security fix. It has nothing to do with the current Twitter outage as of the beginning of May 2011.
After pulling them apart and recompiling them, with the help of JVH3, here are the HTC Peep Update *.cabs. These are for Windows Mobile users with version 6.5 or higher. It should work, in theory with version 6.1, but I didn't feel like testing it out. Obviously, you'll need Sense 2.5 as well. There are four versions, but they all seem to be exactly the same. I didn't notice any differences other than the dates they were packaged. The Rhodium version seemed to have a slightly smaller TwitterApp.exe file, but I still don't think it was different.
Disclaimer: I take no responsibility for anything you do to your devices. These are posted for informational purposes. If you choose to install the application update, then any side effects (of which there should not be) are on you.
Changes
This update changes the way the Twitter Tab (HTC Peep) authenticates your user account. Before this update, your account information is sent via unencrypted http headers upon login which reveal both the username and password to anyone who happens to be eavesdropping on the connection, whether it is by cellular data or wifi as seen below.
Code:
authenticity_token=c8b5abaf53f223e827d9258ddfef4285a816db5f&
oauth_token=I4FK956n1foaHjayLKXJT2IaBpsmoo0amKyPhebc&
session%5B[B]username_or_email%5D=USERNAME&session%5Bpassword%5D=PASSWORD[/B]
Also, when sending tweets or receiving them, their is a continuous authenticate request sent which exposes the username and password again as illustrated below.
Code:
GET /statuses/friends_timeline.json?count=50&page=1 HTTP/1.1
Accept: text/xml, application/xml;q=0.9, */*;q=0
[B]Authorization: Basic BASE64("USERNAME:PASSWORD")[/B]
User-Agent: TwitterEngine
Host: twitter.com
I haven't been able to confirm the status of the current update yet with traffic monitoring, but according to HTC, this update sets the Peep application to use OAuth to establish a connection with https to encrypt the username and password instead of leaving it exposed for all the world to see.
EDIT: This is not a 100% fix. It seems that while the initial session is now being sent over https using TCP port 443 (sending against the api.twitter.com domain), during the rest of the session, Peep switches back to HTTP basic. This still leaves the whole session after the initial login vulnerable to hijacking based on the Twitter's session ID through cookies. I suggest using a different Twitter client, as neither HTC nor Twitter care for our aging devices.
EDIT: DO NOT PM ME ABOUT THIS FIX. IT DOES NOT WORK.
i dont like to install os on sd card
squaloforte said:
i dont like to install os on sd card
Click to expand...
Click to collapse
What relevance does your post have to anything related to this thread?
Nothing about this thread has anything to do with installling an os or anything to your sd card.
It is about the twitter tab security flaw and the recent patch by HTC.
A patch could only be installed to the device, since patches need to replace files on the device.
Still getting login error!
I'm still getting login error problem on my HTC HD2 o2 uk phone, this update and the HTC HD2 Peep Security update on the HTC website http://www.htc.com/europe/SupportViewNews.aspx?dl_id=1085&news_id=866 doesn't work
Is anyone else getting this problem?
ramonguthrie said:
I'm still getting login error problem on my HTC HD2 o2 uk phone, this update and the HTC HD2 Peep Security update on the HTC website http://www.htc.com/europe/SupportViewNews.aspx?dl_id=1085&news_id=866 doesn't work
Is anyone else getting this problem?
Click to expand...
Click to collapse
Please try to keep up.
This fix has nothing to do with login errors.
This fixes a security vulnerablity.
Without the fix, user name and password are sent in plain text through http.
With the fix, oauth is used instead, so each request does not send this information. And when it initially is sent to authenticate, https is used.
The twitter tab works for just about everybody. And the fact that no one else is reporting problems since applying the fix indicates that the fix does not have a problem.
Things to check:
Do you have a twitter acount?
Are you entering your twitter user name and password correctly?
Is your twitter account locked by twitter? (try using it with your computer)
Do you have a data plan?
Do you have a strong cell signal with Edge or 3G service?
Have you tried soft resetting your device?
Are you in the UK?
If not, does the country you are in block access to twitter?
Can you browse web pages with your phone?
No need to reply to this reply to your post since your post was not on topic for this thread.
JVH3 said:
Please try to keep up.
This fix has nothing to do with login errors.
This fixes a security vulnerablity.
Without the fix, user name and password are sent in plain text through http.
With the fix, oauth is used instead, so each request does not send this information. And when it initially is sent to authenticate, https is used.
The twitter tab works for just about everybody. And the fact that no one else is reporting problems since applying the fix indicates that the fix does not have a problem.
Things to check:
Do you have a twitter acount?
Are you entering your twitter user name and password correctly?
Is your twitter account locked by twitter? (try using it with your computer)
Do you have a data plan?
Do you have a strong cell signal with Edge or 3G service?
Have you tried soft resetting your device?
Are you in the UK?
If not, does the country you are in block access to twitter?
Can you browse web pages with your phone?
No need to reply to this reply to your post since your post was not on topic for this thread.
Click to expand...
Click to collapse
My Peep app stop working in January, there are no problems with my twitter account, all I'm looking for is a solution or fix!
Do you know where i can get a Peep.cab?
ramonguthrie said:
My Peep app stop working in January, there are no problems with my twitter account, all I'm looking for is a solution or fix!
Do you know where i can get a Peep.cab?
Click to expand...
Click to collapse
As I previously said, this thread is dedicated to the HTC Security Patch for the twitter tab.
I suggest either looking for a thread dedicated to the twitter tab not working or creating your own thread in the question and answer section.
http://forum.xda-developers.com/forumdisplay.php?f=456
This thread is not the appropriate place for your question.
My HTC Peep stopped working on my Rhodium after installing this update. Peep worked right up until I installed the HTTPS Fix.
Verizon TP2, using the Custom ROM --> Verizon MR2 Fixed by Mr. X
(ROM Found here)
http://forum.ppcgeeks.com/cdma-tp2-...zon-mr2-fixed-mr-x-boots-unlocked-device.html
I see the "Tap Here to Authenticate" Screen
I type in Username/Password (which works when logging into the website)
HTC Peep tries to log in, but I get an error --> "You entered an incorrect username or password."
I cleaned out the Temp folder to try and get a fresh start, but no luck.
I tried to uninstall, but I am unable to uninstall properly.
I tried to Re-install, but no luck.
I shut down Sense, re-installed, and rebooted and turned on Sense, no luck.
So, minus doing a brand new ROM flash it looks like this .CAB tanked the Twitter tab for me. I didn't really want to keep using it unsecured, but it sucks that the update stopped it from working altogether.
I have just tried to enter a postcode into a contacts address but the only field is zipcode and it has the field locked to numbers, you cannot even paste a postcode into the field, is this a region issue I cannot find an option to change this but any setting I have in the phone are English (UK)
Not spotted this but you're correct
For now until this is fixed, hopefully, if contacts are entered in outlook and synced then the postcode will transfer ok.
That seems to work but very annoying.
descb600f said:
That seems to work but very annoying.
Click to expand...
Click to collapse
I agree with you as I generally enter details into phone and then sync to outlook when home........... now it's back to pen and paper when I'm out!!!!!!
same problem
i cant type in a post code apparently this is a common fault when i rang htc he found the fault to however he used the word "feature" and then said we may fix it if it is important... i said i type in 2 addresses a day i need to be able to type a post code as i have 2000 names and addresses in my phone
Not being able to enter a postcode is an annoying bug for a UK phone. You'd have thought that would have been picked up in testing. Guess I'll have to enter postcodes via GMail in a browser for now.
cooljhill said:
i cant type in a post code apparently this is a common fault when i rang htc he found the fault to however he used the word "feature" and then said we may fix it if it is important... i said i type in 2 addresses a day i need to be able to type a post code as i have 2000 names and addresses in my phone
Click to expand...
Click to collapse
Is this a joke??? "may fix it if it is important"?? I use my phone to enter contacts all the time and these then sync OTA to Outlook. It is an essential feature for me. If this doesn't work there is no way I'm getting this phone.
I think that in this situation complaining directly to Vodafone is the best solution and also opening a thread on their forums. People in other countries can do the same with Vodafaone/their local carrier. The carriers will then take it up with HTC and I expect that it will be fixed.
sjgore said:
Not being able to enter a postcode is an annoying bug for a UK phone. You'd have thought that would have been picked up in testing. Guess I'll have to enter postcodes via GMail in a browser for now.
Click to expand...
Click to collapse
Not got the phone yet (b'day at the end of June so have to wait a bit ... ) but tested this on my Desire HD and the People app on this allows you to add a UK post code (though it calls it a zip code - doh! ). I'm on 2.3.3 and fail to see why you can't do it from a software point of view. Have they never heard of code re-use?
Still, 99.99% of my contacts are sync'ed from Outlook so no problems. Can you not add the post code as a note and edit it back in Outlook later to "work around" the issue for now? It does peeve me when 'localised' apps aren't really localised at all, just, for the UK anyway, a variation of the US version. Null points!
Dave
dvhttn said:
Can you not add the post code as a note and edit it back in Outlook later to "work around" the issue for now? It does peeve me when 'localised' apps aren't really localised at all, just, for the UK anyway, a variation of the US version. Null points!
Dave
Click to expand...
Click to collapse
Now I'm wondering what would happen if you tried to use OCR software to read a business card into the phone.
DuoM said:
Now I'm wondering what would happen if you tried to use OCR software to read a business card into the phone.
Click to expand...
Click to collapse
The field is locked I tried copy and paste but only the numbers appeared the letters were omitted.
This thread is to track my dealing with HTC and their service department over the current Twitter Tab (HTC Peep) outage. Please don't PM me about it, I'll just make fun of you for not reading and searching.
The current outage has NOTHING AT ALL to do with the Peep security updates published back in February. For information on the past update, please refer to this post.
I am reaching out to everyone who uses this application to bug the crap out of HTC until they fix this problem. Please read this post all the way through so you can contact them with a bit of information. I originally tried to ask about it as simply as possible, but only got an idiotic response. The communication log will be posted in the next post.
Basically, for anyone experiencing issues with Peep, simply read the post I linked to and the following post. This will give you enough information to be able to contact HTC and make some noise. If you do contact them, please use proper grammar and be respectful. Typing like a pissed off high school girl (no offense to pissed off high school girls) will get us no where.
A brief history of Peep outagesSince the very beginning of HTC Sense, most experienced users have known about Peep's security flaws and have either decided to live with it, figuring that it wasn't very important to them, or simply used another client for Twitter. The problem is that Peep was accessing the Twitter API through use of unencrypted HTTP headers which exposed your username and password to anyone who might be eavesdropping on the connection via cellular data IP or WiFi.
Twitter experienced some headlines last summer where several celebrity and high profile accounts were compromised due to lax security features. This caused them to begin shifting their API towards a more secure end. In doing this, they notified the developers of Twitter clients of this shift and to update their applications accordingly. HTC was one of the few who did not update their applications.
Late last year, HTC's Peep application experienced some outages. HTC, instead of repairing the problem, petitioned Twitter about the outage and, after several weeks, the functionality of Peep was restored through an exception made in Twitter's API. This was the easiest solution for HTC, but the worst solution for the customers, since it still left the user's data exposed to risk and was only a temporary solution.
Then, sometime in late January/early February, the members of Tadong blog released their security information to the general public after trying for months to get HTC to fix the security flaw in Peep as outlined above. Subsequent to the release of the information, HTC finally release the security updates for Peep that corrected half of the problem. The initial log in attempt now used OAuth to establish a secure connection over HTTPS on TCP port 443. This fixed the update Twitter rolled out shortly after where some users got the "Forbidden" errors when trying to use the tab. It did not fix the remainder of the session where Peep would request data from Twitter. The rest of the time, Peep requested data over unencrypted HTTP basic headers just as it always had. This, as most of you know, caused problems with the most recent update to Twitter's API.
Twitter rolled out an update again at the end of April that broke the Peep client again. The problem wasn't really Twitter, though. Twitter has now disallowed any new requests to access it through unencrypted channels. This, of course, blocks Peep again. The sad thing now is that this would not be a problem if HTC had simply fixed the problem last year during the first outage or even produced a secure client in the first place.
This brings us to the present. I have contacted HTC with all the information I could gather about this problem. The conversation is listed in the next post. I encourage everyone reading this to learn a bit here and contact HTC via their support page. Any serial number should work as long in the contact form as it matches the correct device. The only Rhodiums to receive the Sense update were the Euro and AT&T ones, as far as I know. Leos ship with it, and I'm sure there were other devices that got Sense updates as well, such as the Photon and Topaz. I'm not up to speed on the models of those devices that got Sense, though. If you contact them, please post in here your conversations. If you need help crafting a proper response to the HTC support techs, please PM me. I will try to assist as best I can.
Communication log
Log between myself and HTC reps, Douglas and Danielle.
Me said:
I have both a Tilt2 and a HD2. Both are using HTC Sense as the primary GUI. On both of them, the Twitter Tab (HTC Peep) no longer works. I put in the right username and password and it always tells me that it is the wrong username or password. I have done this multiple times, and am absolutely certain that I am typing it in correctly.
After searching around for a while, it appears that I am not the only one to have this problem. I also have the HTC Peep security update installed on both of the devices, but it does not work with or without that fix.
Is HTC planning to roll out an update to fix this problem?
Click to expand...
Click to collapse
HTC Douglas said:
understand you are unable to log in to Twitter even with the Peep security update. The link you need to download the update for is different for your two devices.
Use this first link for your Touch Pro 2:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1085&news_id=874
And this link for your HD2:
http://www.htc.com/www/SupportViewNews.aspx?dl_id=1086&news_id=865
If this does not work you may need to restore your devices to factory settings and re-apply the appropriate hotfix after backing up your information, for example with ActiveSync or the Windows Mobile Device Center to sync your information with Outlook.
Sync software is available at: http://www.microsoft.com/windowsphone/en-us/apps/65-downloads.aspx
You can back up your information using ActiveSync or the Windows Mobile Device Center located at the following URL:
http://www.microsoft.com/windowsphone/en-us/apps/65-downloads.aspx
Essentially, plug your phone into the PC after installing the software and select Activesync as your connection type. Your computer will walk you through backing up your data.
A factory data reset will clear all data from the phone's internal memory and restore the device to manufacturer defaults. Information on your storage card will be kept. To reset the phone press start>settings>(menu>all settings)>system>clear data and confirm.
Click to expand...
Click to collapse
Me said:
I just mentioned that I installed the security update already, and the response I got was to install the security update? What kind of answer is that? Even if the line of thinking was that I perhaps installed the wrong update, how would that even be possible considering the updates require the installation to pass software version checks before installing? I was trying to make this as simple as possible, but considering the response I received, it is apparent I will be unable to do this.
The problem is that the Peep Security Update did not fix the problem all the way. Originally, the Twitter account information was sent via unencrypted http headers upon login which reveal both the username and password to anyone who happens to be eavesdropping on the connection, whether it is by cellular data or wifi. Also, when sending tweets or receiving them, their is a continuous authenticate request sent which exposes the username and password again in the same manner.
The security update is not a 100% fix. After installing the update, it seems that while the initial session is now being sent over https using TCP port 443 (sending against the api.twitter.com domain), during the rest of the session, Peep switches back to HTTP basic. This still leaves the whole session after the initial login vulnerable to hijacking based on the Twitter's session ID through cookies. Because this was not fixed properly in the first place, Twitter has blocked the application from accessing its api. Twitter has increased its security measures and disallowed new authenticate requests from unsecured clients. So any device that is currently authenticated in Peep will not be affected, but once the user logs out of Twitter, does a hard reset, or a ROM upgrade, the Oauth token will be invalidated or removed and will not allow Peep to log back in.
This is the position I am currently in, along with hundreds other users. It affects every user on HTC Sense as it will break the Peep client as soon as they log out. Since these devices are still being sold as brand new, HTC should still be providing support for them, since it is the HTC software that is not functioning as intended. Now, what is HTC prepared to do for every single Sense user? All that needs to be done is to FINALLY secure the Peep client and force it to use HTTPS instead of basic HTTP. The Twitter api will refuse all new auth requests that are unencrypted.
I have attached an eavesdrop of the timeline update request that is sent when the client refreshes. Notice that the username and password are UNENCRYPTED and shown in plain text. One more time I will ask what HTC is prepared to do to solve this problem. Please don't give me a cookie cutter response again. Thank you for your time.
Click to expand...
Click to collapse
The previously mentioned log is attached to this post.
HTC Douglas said:
Thank you for your reply. If you have performed the security update after performing a factory data reset please let me know and I can escalate this issue within HTC.
These are standard troubleshooting steps required to identify an issue and would be required before Escalations can review the case. I appreciate the additional data and log you included, as well.
Also so that I can escalate this issue, please reply with the following information:
Mobile device number:
Alternate contact number
Time zone:
Preferred contact time:
Current ROM version: (Start>Settings>about phone>software information on the HD2)
Click to expand...
Click to collapse
Me said:
As I mentioned, this is problem is persistent through hard resets and ROM updates. Anytime you log out or clear the Peep auth token in any way, it will not allow any further logins due to the (lack of) security of Peep. The only way around this currently is to back up the registry data associated with the Peep client in [HKLM\Software\HTC\HTCAccountManager] as well as the entire folder [\Temp\TwitEng]. If these are imported into a new flash of a ROM update or after a hard reset, the client will function again, as no new initial auth request will be needed. This still does not fix the problem of the client exposing usernames and passwords during EVERY update attempt. Nor does it allow less savvy users to use the Tab after having to hard reset or update the ROM.
The Tilt 2 is running ROM version 2.10.502.4.
The HD2 is running ROM version 3.14.531.1.
You may contact me via e-mail (email removed). I prefer not to be called.
Click to expand...
Click to collapse
HTC Douglas said:
Thank you for your reply. I have escalated the issue for further review. An escalations agent will reach out to you soon. Escalations contacts are performed in the order they are received so it may take a few days for us to review this information and get in touch with you.
Thank you for the detailed information about your analysis.
Click to expand...
Click to collapse
HTC Danielle said:
The previous agent has forwarded your email request to the next level for further review. The escalations team will be getting back with you as soon as they have any information for you. I hope you have a safe holiday weekend.
If you need any further assistance, you are welcome to send another inquiry through the HTC website by going through the Support page (http://www.htc.com/us/support) then tapping ‘send us an email’. You should input all the necessary information requested on the page.
Click to expand...
Click to collapse
Me said:
I will be awaiting further reply. Thank you for your attention to this matter.
Click to expand...
Click to collapse
HTC Travis said:
Thank you for provding us information about the shortcomings of our PEEP security update. I have verified that you are correct and have alerted our corporate office of this fact. They are researching the root cause in terms of the programming and will look into providing an update.
Click to expand...
Click to collapse
Me said:
This is great news. I'm having trouble seeing that I'm the first person to bring this to HTC's attention, though, seeing as this has been an issue for right about a month now. I figured someone else would have reported the problem before me. Please do keep me informed as this progresses. It should be as simple as forcing Peep to use secure HTTPS over TCP port 443 during the session as it does during the login procedure that was updated in February. Currently, it uses OAuth over HTTPS to establish the initial login, but switches back to HTTP basic for the remainder of the session. This allows the username and password to be seen in plain text every time the application requests an update from the Twitter API. Using this method also has another side effect. Twitter updated its security measures to disallow unencrypted requests. This means that Peep is no longer able to establish a connection since it moves from OAuth over HTTPS to HTTP basic during the initial session. If I can be of any other assistance, please let me know. I look forward to updates in this matter.
Click to expand...
Click to collapse
HTC Travis said:
You are not the first person to tell us they are having a problem with Twitter. You are the first person to provide us with this level of information and we thank you for that. Please reply to this email in a few days and someone should be able to give you more information.
Click to expand...
Click to collapse
Me said:
I see. I'm just doing what I can to benefit the dwindling Windows Mobile community. I will check back later this week. Thank you for the updated information.
Click to expand...
Click to collapse
Retain Twitter Tab/Peep functionality through a flash or hard reset
Before you ask, I don't have first hand experience with this. This is based on successful attempts by other members of the community.
This only works if the Twitter Tab/Peep currently still work for you. If it doesn't, then you are out of luck, and this will not work for you.
To retain the functionality of the Peep client through a flash of a new ROM or a hard reset, you will need to follow the steps listed below.
1. Stop Sense and soft reset to make sure that Sense doesn't continue altering information while you are backing up data.
2. Back up the entire key of "HKLM\Software\HTC\HTCAccountManager." You really only need the Twitter strings, but it's easier to just back up the whole thing.
3. Backup the entire folder of \Temp\TwitEng. This is where the Twitter authentication token is stored.
4. Flash the new ROM or hard reset, whichever you need to do.
5. Once the new ROM is stable and working, stop Sense and soft reset.
6. Restore the registry key and backed up directory.
7. Soft reset and then enable Sense. The Twitter tab should now continue working for you without any trouble.
EDIT: JVH3 made a pair of posts about this HERE and HERE. The second one talks about authenticating another device with the backed up data.
Great initiative ! I'm very curious to hear about HTC's reception of the issue, and see if they will take the initiative to fix it...or imagine a way to justify how not doing it
majorasshole said:
Great initiative ! I'm very curious to hear about HTC's reception of the issue, and see if they will take the initiative to fix it...or imagine a way to justify how not doing it
Click to expand...
Click to collapse
Please use this thread to contact HTC about the problem. Please don't link them to this thread, though. I started this with the intention that others would use the information I have gathered on the issue to contact HTC in an informed manner to get it resolved.
Basically, the more noise is made on this issue, the better chance there will be to have it fixed.
HOLY $ |-| 1 +, it worked!
Ok, so I received official word that Peep is being looked into by HTC. I would still encourage anyone reading this to contact them with the information I have provided here. The squeaky wheel gets the grease, as they say.
HTC Travis said:
Thank you for provding us information about the shortcomings of our PEEP security update. I have verified that you are correct and have alerted our corporate office of this fact. They are researching the root cause in terms of the programming and will look into providing an update.
Click to expand...
Click to collapse
Me said:
This is great news. I'm having trouble seeing that I'm the first person to bring this to HTC's attention, though, seeing as this has been an issue for right about a month now. I figured someone else would have reported the problem before me. Please do keep me informed as this progresses. It should be as simple as forcing Peep to use secure HTTPS over TCP port 443 during the session as it does during the login procedure that was updated in February. Currently, it uses OAuth over HTTPS to establish the initial login, but switches back to HTTP basic for the remainder of the session. This allows the username and password to be seen in plain text every time the application requests an update from the Twitter API. Using this method also has another side effect. Twitter updated its security measures to disallow unencrypted requests. This means that Peep is no longer able to establish a connection since it moves from OAuth over HTTPS to HTTP basic during the initial session. If I can be of any other assistance, please let me know. I look forward to updates in this matter.
Click to expand...
Click to collapse
HTC Travis said:
You are not the first person to tell us they are having a problem with Twitter. You are the first person to provide us with this level of information and we thank you for that. Please reply to this email in a few days and someone should be able to give you more information.
Click to expand...
Click to collapse
Me said:
I see. I'm just doing what I can to benefit the dwindling Windows Mobile community. I will check back later this week. Thank you for the updated information.
Click to expand...
Click to collapse
cajunflavoredbob said:
Before you ask, I don't have first hand experience with this. This is based on successful attempts by other members of the community.
This only works if the Twitter Tab/Peep currently still work for you. If it doesn't, then you are out of luck, and this will not work for you.
To retain the functionality of the Peep client through a flash of a new ROM or a hard reset, you will need to follow the steps listed below.
1. Stop Sense and soft reset to make sure that Sense doesn't continue altering information while you are backing up data.
2. Back up the entire key of "HKLM\Software\HTC\HTCAccountManager." You really only need the Twitter strings, but it's easier to just back up the whole thing.
3. Backup the entire folder of \Temp\TwitEng. This is where the Twitter authentication token is stored.
4. Flash the new ROM or hard reset, whichever you need to do.
5. Once the new ROM is stable and working, stop Sense and soft reset.
6. Restore the registry key and backed up directory.
7. Soft reset and then enable Sense. The Twitter tab should now continue working for you without any trouble.
Click to expand...
Click to collapse
Looks alot like what I posted here: http://forum.xda-developers.com/showpost.php?p=13790743&postcount=34951
Your thread is a better place for it though.
I also posted this: http://forum.xda-developers.com/showpost.php?p=13520319&postcount=34836
Which is helpful if you have another device that still is authenticated with the Twitter tab and transfering the info to another device.
Real glad you got things going with HTC to finally work on this.
JVH3 said:
Looks alot like what I posted here: http://forum.xda-developers.com/showpost.php?p=13790743&postcount=34951
Your thread is a better place for it though.
I also posted this: http://forum.xda-developers.com/showpost.php?p=13520319&postcount=34836
Which is helpful if you have another device that still is authenticated with the Twitter tab and transfering the info to another device.
Real glad you got things going with HTC to finally work on this.
Click to expand...
Click to collapse
Well, I already knew the key and file that needed to back up, but I forgot where I saw the bit about turning on and off Sense. Thanks. I'll add some credit for you.
Yea, there's a bit more that I can't post due to personal or sensitive information, but it's looking good so far. I'll keep updating this as more info rolls in. I'm hoping that other people contact them about it as well.
Very good afford cajunflavoredbob .
Lets hope Peep developer team in HTC are getting ready with new client
Thanks.
prabhat said:
Very good afford cajunflavoredbob .
Lets hope Peep developer team in HTC are getting ready with new client
Thanks.
Click to expand...
Click to collapse
I have a bit more to update tonight. They have sent the information onward and are working on a fix right now. No ETA was given, however.
Ive just suffered this problem today - logged out of peep and now i cant get back in again. As i didnt know about this issue, obviously dont have any backup! Thanks for pursuing this!
This has been my ongoing encounter with HTC Support for the Touch HD / Blackstone
Simon Lee Reply
Ok, could you keep me notifed if the touch HD will get the update or not ?
Thanks 2011/06/08 18:04:45
Bjorn [EU team] Close Pending I'm not saying it won't happen, I'm just saying that at this point I can not guarantee taht the touch HD will get such an update as it is an older device. I'm not saying it won't happen, I'm just saying that at this point I can not guarantee taht the touch HD will get such an update as it is an older device. 2011/06/08 16:15:10
--
Simon Lee Reply How come thou ? If theres no fix then that might meen i will have to buy a new phone, and am quite happy with the Touch HD ?
--
2011/06/08 10:57:55 Bjorn
[EU team] Close Pending I can not guarantee That a fix will be released for the Touch HD when te issue is resolved. I can not guarantee That a fix will be released for the Touch HD when te issue is resolved.
--
2011/06/08 07:59:10 Simon Lee Reply
Yeah, i realise its an Unoffical ROM, but thats beside the point, When tyou fix the HTC peep, will the Touch HD get a Upgrade for 6.1 with the HTC Peep fix?
--
2011/06/07 17:15:23 Bjorn [EU team]
Close Pending As your device is runnig an unaproved ROM we are unable to support it and can not guarantee that any applications will work properly. We have how ever had reports regarding this and are looking in to it on our approved ROM's, As your device is runnig an unaproved ROM we are unable to support it and can not guarantee that any applications will work properly. We have how ever had reports regarding this and are looking in to it on our approved ROM's,
--
2011/06/07 16:14:50
spikeyl said:
Ive just suffered this problem today - logged out of peep and now i cant get back in again. As i didnt know about this issue, obviously dont have any backup! Thanks for pursuing this!
Click to expand...
Click to collapse
Theres some kind of solution floating around here somewere
- Edit -
you could try this: http://forum.xda-developers.com/showthread.php?t=708770
Thanks - i found this earlier and tried all these but none of them work! Having read through the thread above I can see why though - it is related to the security authentication issue, so currently no fix.
spikeyl said:
Thanks - i found this earlier and tried all these but none of them work! Having read through the thread above I can see why though - it is related to the security authentication issue, so currently no fix.
Click to expand...
Click to collapse
Yeah, and HTC are planning on bring out a fix, but wont say which devices, will get the supported fix,
Simon_WM said:
Yeah, and HTC are planning on bring out a fix, but wont say which devices, will get the supported fix,
Click to expand...
Click to collapse
The only devices that will get the fix are the ones that have official Sense 2.5 ROMs. There are only four of them.
1. Leo
2. Rhodium
3. Photon
4. Topaz
My recent communications with HTC contain personal information regarding the fix. It is being worked on, but there is no current ETA that they have provided. I am keeping in touch with them and working with HTC to resolve the problem. I'll update this thread as more information is provided to me.
EDIT: Please don't post here about possible fixes. There is no fix for this error. The problem is with Peep and has nothing to do with Twitter. Logging in and out of Twitter on the desktop will have no bearing on the Peep application. No applications are allowed to access Twitter's API though unsecured connections, thus Peep is excluded.
My Twitter also stopped working sometime last week, but I don't ever remember logging out. However when I scrolled past the peep tab on my HD2 this morning it read "no tweets" instead of the click to login screen (or whatever it said). I clicked the screen and now have tweets going back to sometime yesterday. Is this any way connected?
jools5431 said:
My Twitter also stopped working sometime last week, but I don't ever remember logging out. However when I scrolled past the peep tab on my HD2 this morning it read "no tweets" instead of the click to login screen (or whatever it said). I clicked the screen and now have tweets going back to sometime yesterday. Is this any way connected?
Click to expand...
Click to collapse
This is unrelated if you did not log out, as far as we know. Twitter isn't yet blocking anyone from their API who already has a connection. They are only refusing new attempts.
HTC knows the problem, is working on it, but still no ETA
Just to add my story:
Originally Posted by Me
After flashing a new row to my HTC HD Mini, HTC Peep cannot sync with Twitter anymore.
I have flashed this rom: http://www.htc.com/europe/SupportDownload.aspx?p_id=314&cat=2&dl_id=980
And updated it with this update: http://www.htc.com/europe/SupportDownload.aspx?p_id=314&cat=0&dl_id=1085
When I enter my account and password, HTC Peep tells me: "You entered an incorrect username or password".
The account and password are OK, since I can use them via the web and other Twitter-applications.
I tried revoking HTC Peep as a Twitter-application and then re-adding HTC Peep.
But the message is still "You entered an incorrect username or password".
From an old backup I have retrieved registry settings at HKLM\Software\HTC\HTCAccountManager and the directory at \Temp\TwitEng.
After putting these settings back into the new rom I get a message: "The account was forbidden to access the twitter server!"
This is logically because I revoked HTC Peep as a Twitter-application at the Twitter website.
So, the HTC Peep client does not recreate the connection to Twitter.
Please provide a solution or update so that the HTC Peep client will work again.
Click to expand...
Click to collapse
Originally Posted by HTC
Thank you for contacting HTC Support.
The problems you are experiencing is because of a change in the Twitter API's that Peep has not yet adapted to.
Unfortunately I have no ETA for when this might be.
Until then I can only recommend using another Twitter client.
I hope this helps.
Click to expand...
Click to collapse
Originally Posted by Me
Thank you for the answer.
I am already using another Twitter client, but miss Peep...
I sincerely hope that Peep will be adapted soon.
Is this problem (already) sent to the development department?
Click to expand...
Click to collapse
Originally Posted by HTC Thank you for your email.
Yes, HTC is working on solving this issue as soon as possible.
If you have any further queries please don't hesitate to contact HTC again.
Have a nice weekend.
Click to expand...
Click to collapse
So, HTC knows the problem, is working on it. But still no ETA.....
wensing said:
Just to add my story:
So, HTC knows the problem, is working on it. But still no ETA.....
Click to expand...
Click to collapse
It's good to hear someone else's experience. I will ry to get back in touch with the HTC rep I've been communicating with this evening or tomorrow to see if there are any updates.