View Single Post
  #138 (permalink)  
Old 12-17-2009, 05:19 AM
tek818's Avatar
tek818
PPCGeeks Regular
Offline
Location: Los Angeles
 
Join Date: Oct 2008
Posts: 237
Reputation: 265
tek818 is becoming a PPCGeeks regulartek818 is becoming a PPCGeeks regulartek818 is becoming a PPCGeeks regular
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: hard spl unlock not working on my replaced phone...

Quote:
Originally Posted by cmonex View Post
some AV programs need to be disabled, because the packer I used to pack the program isn't liked by symantec.
I use NOD32 and that one doesn't complain. nor does Avast on my laptop. again a case where symantec sucks... :P
anyway, the reason for AV problems is stated in 1st post of the HSPL release too. I don't know what this nonsense idea is about hiding files in memory.

as for IP's, *any* page you visit online *will* see your IP so any site can and will probably log IP's (just think of the website statistics that all hosting providers offer you by default),
and most people (unless maybe if you are the police or something) can't do anything with an IP, so that's not terribly insecure I would say
we also log the IMEI and the PC's ID, but that's again not interesting.
we cannot identify you personally from any of this info. we do not take any info/personal data off your phone etc. etc.
so, that's all we log, and we don't look at the logs ourselves (unless requested), the server code tries to use it to detect unlock uses.

still, if you are worried and you don't want to believe when I say that we are not doing anything shady, and if you don't find the many references convincing about me and Olipro helping people since 2005 (on XDA since 2007), free for most of the time as well, then don't use the program, it's that simple.

does this answer help. I hope so.

also...I just noticed in your post.. what does the expression "pure action" mean??
I am not saying you are trying to keep files hidden on my hard drive, I am saying that your packager hides the RUU files so they can not be captured/copied.

As for my "pure" comment, I am simply referring to the way in which you choose to blacklist IPs/IMEIs. I'll give you a perfect example... When my first TP2 had to be replaced for dead pixels, I took my replacement phone home and tried to run HSPL. I got the commercial message... fair 'nuff I have already unlocked a phone from this PC/WAN IP (granted I relocked it before bringing it back to Sprint).

What is not ok, is for me to be unable to then take my replacement phone to my office or use a neighbor's wifi (with permission of course) and run HSPL. There is no good reason why you should blacklist the phone until you allow the IMEI or the user pays. It's not like some commercial phone salesman is going around all day war driving for open wifi access points and reinstalling windows just to unlock some phones...
Reply With Quote