Database Info

Dualing phones

I'm currently running an HTC touch pro 2 and i still have my HTC touch pro. I turned my TP1 on the other day for the first time in many months and the phone picked up a text message, not only did it pick it up, it picked it up at the same time my TP2 did. Unfortunately it hasn't happened since.
What i'd like to know, is there a way i can emulate the IMIE number on the tp2, so that i can have both my TP2 and my TP1 working at the same time.
I want to be able to use my TP1 as a full data device while i make my calls on my TP2 or vice versa.
If you can't post the answer here for what ever reason feel free to private message me.
*edit it will recieve every txt message that is sent to my number but it won't send and it won't take incoming calls.

Good luck with that, cause that aint gonna happen. Well, at least not anyway that I can possibly think of. Carriers wont allow more than one phone per mobile number. They say it isn't possible, but I personally think it IS possible and that they just wont allow it. Technically, it should be able to work. But the problems would fall with the GPS. Even if GPS was on in one device while off on the other, they couldn't track someone if they wanted to. I'm sure there are other reasons to this. I have never heard of what you are experiencing. They probabbly didn't fully remove the old phone's IMIE data from the system, hence why you can receive texts but not send anything. What service are you on?

THE-COPS said:
Good luck with that, cause that aint gonna happen. Well, at least not anyway that I can possibly think of. Carriers wont allow more than one phone per mobile number. They say it isn't possible, but I personally think it IS possible and that they just wont allow it. Technically, it should be able to work. But the problems would fall with the GPS. Even if GPS was on in one device while off on the other, they couldn't track someone if they wanted to. I'm sure there are other reasons to this. I have never heard of what you are experiencing. They probabbly didn't fully remove the old phone's IMIE data from the system, hence why you can receive texts but not send anything. What service are you on?
Click to expand...
Click to collapse
1) unfortunately telus.
2) The GPS on my phones has been completely deactivated except for when I want to turn it on. I refuse to allow someone to turn it on remotely, also in Canada that's akin to wireless phone tapping so the cops can't do it. And even if they could legally i'd still reprogram my phone so they can't.
3) That's my point. If they didn't fully remove it and my old phone can still get the txt messages that means they can re-add the old MEIE numbers back to the system and both should work. OR if i could put an emulator onto my phone or even hard code the MEIE number change on my old phone to the same as my new one...

Remember back in the day when cellphones were still a new thing, the brick and bag phones and so on, well someone figured out how to clone phones and the practice caught on like wildfire and since then has been literally outlawed. AS IN IT IS ILLEGAL TO CLONE ONE OR MORE PHONES TO THE SAME IMEI, MSID, DEC OR HEX SERIAL TO GAIN USE OF MULTIPLE PHONES ON THE SAME LINE AT THE SAME TIME. Not being mean or an ass to you, but I would research this a little bit and tread lightly on the subject. Stuff like this is not tolerated very well on xda.
Plus, now it would be almost impossible to do this with any carrier as the data the phone sends out is not just what you want it to. Whenever it connects to the network is sends and receives configuration data such as manufacturer and model among other things and will throw red flags if it doesnt match up to what the expected result of the data sent and received to the network and carrier has on file.
Again, tread lightly on this path.

"AS IN IT IS ILLEGAL TO CLONE" I'm serious, I'd like to see an actual Canadian law stating this. And if it's not illegal in Canada then it's a legit question. Well it's still legit.
"not tolerated very well on xda." Why? the whole point of these forums is to learn and teach people how to modify their phones. If they didn't want people sharing this information they should never have started this website to begin with.
As to my actual question and as to one stated answer
"They probably didn't fully remove the old phone's IMIE data from the system"
If it's still partially in the system that means it could be wholly in the system and means it should be able to be done. If they say it can't but i'm still getting txts on both phones that means the carriers are lying and are just making excuses to get more money. If thats all it is i'll do my best to get every penny out of them for every penny they're stealing from me.
Ok rant done, how do I clone my IMIE number? (no i won't tread lightly)

slight22 said:
"AS IN IT IS ILLEGAL TO CLONE" I'm serious, I'd like to see an actual Canadian law stating this. And if it's not illegal in Canada then it's a legit question. Well it's still legit.
Click to expand...
Click to collapse
its considered fraud under the law in most counties, like changing the VIN on a car, even if there isnt a specific law to deal with it
and besides that, its against the rules of this forum, so even if it was legal to do its not ok to ask about here

defaultdotxbe said:
its considered fraud under the law in most counties, like changing the VIN on a car, even if there isnt a specific law to deal with it
and besides that, its against the rules of this forum, so even if it was legal to do its not ok to ask about here
Click to expand...
Click to collapse
Your making a mountain out of a mole hill and there is a very real difference between a 6 or 8 hundred dollar phone and 15 thousand dollar plus car; unless you own both then i see no issue switching out the vin, as long as you own the cars.
as to being the against forum policy i challenge that on the simple fact there is nothing wrong with sharing knowledge.

slight22 said:
Your making a mountain out of a mole hill and there is a very real difference between a 6 or 8 hundred dollar phone and 15 thousand dollar plus car; unless you own both then i see no issue switching out the vin, as long as you own the cars.
Click to expand...
Click to collapse
lawmakers disagree
as to being the against forum policy i challenge that on the simple fact there is nothing wrong with sharing knowledge.
Click to expand...
Click to collapse
forum admins disagree

"lawmakers disagree"
I can't trace out anywhere where they say cloning your phones IMIE is illegal in Canada, and i also just got of the phone with HTC and they said they don't know of any laws saying it is.
As to the forum admins, they are allowed to disagree, but i'll be they want to know just as much as I do.

Another thread (closed) on this site which discusses ESN cloning: http://forum.xda-developers.com/showthread.php?t=380172
Just search on google, and you will find what you need. There are programs like cdma workshop out there.

Restore *not change* my IMEI

I know this is a touchy subject due to the potentially illegal uses of IMEI numbers. Let me be very clear, I want to restore MY original IMEI number. Here is my situation:
Through various ROM flashes I have changed my IMEI number. Kies says my device in unregistered because I have the wrong IMEI. I wanted to try going back to stock since GB is now available without using a custom ROM. I have my device's original IMEI number saved in a document (in case it was ever stolen). I do not have a backup of my original EFS folder, only the IMEI number itself saved in a text document.
Is there any way for me to manually input my devices IMEI number and save it back into my phone?

http://forum.xda-developers.com/showthread.php?t=881162
Sent from my SAMSUNG-SGH-I897 using XDA App

Thanks for the suggestion. I had already seen this, but since it was talking about setting the values to a "generic" setting I was trying to avoid it. I tried it anyway and it didn't fix the problem. I unrooted the phone and took it to AT&T. The problem ended up being that the APN setting couldn't be accessed and they weren't configured. The rep was able to do a hard reset. Not sure what kind of reset it was though. Not factory. It didn't revert back to Froyo, but it did remove all the apps (to include all google apps) I had to reinstall the market and restart the phone before it would work. Anyway, everything seems to be working fine now. I just wish I could have seen what the rep was doing so I could describe the solution better, but he was on the other side of the counter and didn't seem to want me to see.

IMei Problems in turkey and registration rules
Hi there
I know this will probably yield me a "no its illegal" reply but please hear me out on this. Im a good person!
I moved to turkey 6 months ago to work here as an IT teacher in an international school. I brought with me my lovely HTC HD2 which i had hacked using XDA software to now run andoid (was very pleased with my phone). registered my phone here with my passport. The phone then broke and while trying to fix it I snapped some of the internal data cables...
I have my old HTC wildfire here but cant use it on the GSM network as im only allowed to register 1 phone to my passport every two years!
I know its not technically allowed but i was thinking of changing the imei on my wildfire to that of my broken (but registered) HTC HD2 and was figuring if i got caught for it that they would see that the imei number is in fact registered to me anyway.
I have searched high and low for solutions for this. I found the Iwizard but I think that this was released in 2007 and my phone was released in 2010 so i am presuming that this will not work. also had some problems and questions about using activesync on my windows 7 computer along with presuming that I cant connect an android phone to activesync.
As I said before. Im not tying to commit a crime here but just trying not to go out and spend lots of money (and phones do cost lots of money here) on buying a turkish phone.
if anyone can help then please let me know
my email is [email protected]
cheers..

Thats called cloning. Will not be discussed here as it is illegal in the states and many other places. Check Turkish law, they may not have any laws against it, however you would still be on your own as its not discussed here.
Sent from my SAMSUNG-SGH-I897 using XDA App

just because something is illegal doesnt mean it is illegal to discuss it. it is called freedom of speech. this guy stated he wish he knew how to clone a phone. if you preface your response with the fact the information is not intended for illegal use, you are not aiding anyone. he is responsible for his own actions. a good example of this is when a group attempted to ban "the anarchists cookbook" , a judge ruled that even though the book detailed how to construct illegal devices it could not be baned. the judge cited the first amendment.
i would never advise anyone to break a law but i would not look down on anyone who seeks information. my point is this: it is illegal to make TNT in your basement but it is not illegal to speak or write about how TNT is made. the op should seek his information on the web elsewhere since xda is not for q and a for phone cloning. there are many web sites that explain cloning and it is not illegal to read or write about this matter.
Sent from my SAMSUNG-SGH-I897 using XDA App

Uh ya, and in short, its not discussed on XDA. I never trounced on anyone's freedom of speech.
Sent from my SAMSUNG-SGH-I897 using XDA App

georgiajad said:
just because something is illegal doesnt mean it is illegal to discuss it. it is called freedom of speech. this guy stated he wish he knew how to clone a phone. if you preface your response with the fact the information is not intended for illegal use, you are not aiding anyone. he is responsible for his own actions. a good example of this is when a group attempted to ban "the anarchists cookbook" , a judge ruled that even though the book detailed how to construct illegal devices it could not be baned. the judge cited the first amendment.
i would never advise anyone to break a law but i would not look down on anyone who seeks information. my point is this: it is illegal to make TNT in your basement but it is not illegal to speak or write about how TNT is made. the op should seek his information on the web elsewhere since xda is not for q and a for phone cloning. there are many web sites that explain cloning and it is not illegal to read or write about this matter.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's not about whether or not it is illegal for the topic to be discussed. If you allow potentially illegal information to be placed on the forum freely then you open the community up to unnecessary scrutiny. There are a lot of people out there that do not like developers helping people alter there mobile devices. Yes it's legal, but it also pisses a lot of companies off. So one way the community protects itself is through self-censorship.

that's right

reply
ConeyKiller said:
Thats called cloning. Will not be discussed here as it is illegal in the states and many other places. Check Turkish law, they may not have any laws against it, however you would still be on your own as its not discussed here.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
cheers for taking the time to at least explain this. I was under the impression that someone from XDA had previously posted software on here for the very purpose i am describing in my last post (re turkey). I saw a screen capture of the software (iwizard) and it has a picture of a turkish cup of tea on it. I was guessing that XDA had decided to help people in turkey with the the registration issues we have. But after about 1 week of free time spent searching the internet for solutions I am ready to give in and just go out and buy a turkish mobile phone (can sell me blocked one in england next time i go home) .
Cheers and thanks for all the great software I have previously had from the site for my HTC HD2
f

Unofficial Verizon Locked Bootloader Discussion Thread

Figure we can keep the back and forth here and out of the R&D thread...
Sent from my SCH-I535 using xda premium

I'm curious how closely the USCellular model is to Verizon's and if it is the USCellular model that Samsung will sell as a "developers edition"
Any ideas?

I hope it's not too late. That thread seems long gone... I'm just glad people are staying out of AdamOutler's r&d thread. They actually seem to be getting somewhere.

Wontfinishlast said:
I hope it's not too late. That thread seems long gone... I'm just glad people are staying out of AdamOutler's r&d thread. They actually seem to be getting somewhere.
Click to expand...
Click to collapse
There's some very intelligent people working in there. It amazes me.

Thanks for creating this thread. I keep an eye on the bootloader threads and get tired of having to suffer through pages and pages of people *****ing and moaning about everything related to the bootloader issue except the actual progress in development.
Sent from my LOCKED (Verizon, you suck), SCH-I535.

For anyone interested, I submitted a complaint to the FCC regarding the locked bootloader on the GS3. If you'd like to do the same, go to fcc.gov and click on file a complaint. Then choose wireless provider and then choose the option related to deceptive actions. There is a 1000 character limit to your complaint. Here is the text of my complaint.
Verizon is the only major carrier to have released the Samsung Galaxy SIII with a locked bootloader. There was nothing in Verizon's advertised specs about a locked bootloader. Their explanation is that the device is locked to maintain the security and integrity of the network. However, they are currently selling another Samsung phone, the Galaxy Nexus which has an unlockable bootloader. Also, Verizon has announced a "developer edition" of the Galaxy SIII with an unlockable bootloader for use on Verizon's network. That device must be purchased directly from Samsung for $599. How can Verizon claim a network security and integrity issue and then sell, offer and allow such devices on their network? I feel that Verizon has tricked many customers into paying for a device that they can't use to it's full potential. They know that "security" is a great loophole for complying with the letter of their Auction 73 Block C requirements while totally violating the spirit of that agreement.
That complaint is 990 characters. If you'd like to copy it for your own use, please feel free to do so. Hopefully, enough of us will do this to get the attention of the FCC, consumer organizations and those in positions of influence over the wireless industry.
Sent from my LOCKED (Verizon, you suck), SCH-I535.

I didn't get a chance to file a complaint with the FCC last night but will tonight.
Sent from my SCH-I535 using xda premium

Filed mine yesterday..

Got a call from VZW customer service today. They asked if I was content with my recent upgrade!
She agreed with me that often people buy Androids instead of iPhones because Androids are so customizeable. I expected to be able to use an OS of my choosing on this phone, so I am upset that Verizon locked the bootloader. She understood and sympathized, and now on a server somewhere in the world, there's a short note stating that I'm unhappy with my upgrade.

makogaleos said:
Got a call from VZW customer service today. They asked if I was content with my recent upgrade!
She agreed with me that often people buy Androids instead of iPhones because Androids are so customizeable. I expected to be able to use an OS of my choosing on this phone, so I am upset that Verizon locked the bootloader. She understood and sympathized, and now on a server somewhere in the world, there's a short note stating that I'm unhappy with my upgrade.
Click to expand...
Click to collapse
Hahaha.. awesome!
I understand the notes on my Verizon account are "colorful."

This is Julius Genachowski , head of the FCC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does this look like a person who knows what a locked vs. unlocked bootloader is? You guys are shooting over the heads of your audience by assuming they know the terms you're using.

BarryH_GEG said:
This is Julius Genachowski , head of the FCC.
Does this look like a person who knows what a locked vs. unlocked bootloader is? You guys are shooting over the heads of your audience by assuming they know the terms you're using.
Click to expand...
Click to collapse
Help us draft a response to help describe the issues, without losing our audience then.

ancashion said:
Help us draft a response to help describe the issues, without losing our audience then.
Click to expand...
Click to collapse
Now now. I assume Gary H has waaaaay better things to do than constructively help a minority of peers, like post rude and useless commentary in Internet forum threads created to provoke attention to a problem that shouldn't exist in the first place.
Sent from my SCH-I535 using xda premium

Honestly, with the latest kexec method, I'm not sweating the boatloader anymore
Sent from my SCH-I535 using xda app-developers app

wera750 said:
Honestly, with the latest kexec method, I'm not sweating the boatloader anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Now I may be wrong here because I've never flashed a rom but come to the S3 from an X2 so I've done my time with encrypted boot-loaders, but-
I thought we could change settings/features/etc. on each Rom, but, changing the base kernel of the OS is impossible. Thus, when a new OS is released from Google- say key lime pie, and it drastically changes the kernel, we will forever be prevented from putting that on our device.
Again, I may be wrong. My understanding of it is very limited.
---------- Post added at 09:13 AM ---------- Previous post was at 09:12 AM ----------
jaj6503 said:
Now now. I assume Gary H has waaaaay better things to do than constructively help a minority of peers, like post rude and useless commentary in Internet forum threads created to provoke attention to a problem that shouldn't exist in the first place.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Damn- I'm already out of thanks to give.
I'd give you a gold star, but there ain't any. how about a :good:

jaj6503 said:
Now now. I assume Gary H has waaaaay better things to do than constructively help a minority of peers, like post rude and useless commentary in Internet forum threads created to provoke attention to a problem that shouldn't exist in the first place.
Click to expand...
Click to collapse
It's "Barry" and I have no problem helping you guys.
"People choose Android phones for their openness. That openness allows portability so we can use the phones we've purchased from a single carrier on other carriers so that, based on the free market competition the FCC fosters, we have choices. Up until Verizon launched the new Samsung Galaxy SIII which is projected to sell in the tens of millions, Verizon (like all the other carriers) supported Android's openness and portability. With this new device, Verizon has locked the bootloader (the ability for users to modify the phone) limiting its portability. They did so without any communication with customers only finding out after entering in to a 2-year binding agreement with penalties. If other carriers follow Verizon’s dangerous precedent, and it’s reasonable to think they will, it runs contra to everything the FCC works so diligently to uphold. ”

BarryH_GEG said:
It's "Barry" and I have no problem helping you guys.
"People choose Android phones for their openness. That openness allows portability so we can use the phones we've purchased from a single carrier on other carriers so that, based on the free market competition the FCC fosters, we have choices. Up until Verizon launched the new Samsung Galaxy SIII which is projected to sell in the tens of millions, Verizon (like all the other carriers) supported Android's openness and portability. With this new device, Verizon has locked the bootloader (the ability for users to modify the phone) limiting its portability. They did so without any communication with customers only finding out after entering in to a 2-year binding agreement with penalties. If other carriers follow Verizon’s dangerous precedent, and it’s reasonable to think they will, it runs contra to everything the FCC works so diligently to uphold. ”
Click to expand...
Click to collapse
Thanks for your post, Barry.
FCC is not ignorant to their own laws. That is, their jobs, after all. It is okay to include a bit of legalese in this case. Maybe mentioning Block C requirements §27.16(e).
I think you guys are barking up the wrong tree though with the encryption of the bootloader locking down the OS. That, they don't care about which has already been proved by Verizon's response to the Razr FCC complaint suggesting it was for "customer service requirements" and "Network security."
Section (e) of §27.16 also includes a blip about the locking down of the device to prevent said device from being used on a different network.
Verizon, will have to explain the reasonableness of keeping an encrypted lock on your device after you've decided to make the switch.
But, for it to work, you must first be truthfully denied by Verizon for this request. Only then, can you back them into a corner.
Truthfully, this will work for all 4g devices, from the Razr to the S3 with encrypted bootloaders.
I explain in more detail here, however, I got very few responses as it think it was over the heads of most.
Really, it's quite simple and again, VZW will have to explain how the action is reasonable, which I can't think of one way they can do. Not when I've decided to take this device to a different network. Basically, they'll tell the FCC it's "reasonable" to lock me to VZW's network which is expressly prohibited by that law. I just can't see how they can do it.
Edit- I'm all out of thanks to give so :good:

ancashion said:
Now I may be wrong here because I've never flashed a rom but come to the S3 from an X2 so I've done my time with encrypted boot-loaders, but-
I thought we could change settings/features/etc. on each Rom, but, changing the base kernel of the OS is impossible. Thus, when a new OS is released from Google- say key lime pie, and it drastically changes the kernel, we will forever be prevented from putting that on our device.
Again, I may be wrong. My understanding of it is very limited.
Click to expand...
Click to collapse
I believe you are mistaken.
I came from a Droid 2 Global, where we had a similar situation. We were stuck on the Gingerbread kernel, and with no kexec, we were unable to chain-load a new kernel. We eventually got ICS ports like CM9, but that's because developers made lots of wrappers to make the existing Android ICS framework compatible with the Gingerbread kernel.
This is different from the Galaxy S3, however. We have a working kexec port that allows us to chain-load any custom kernel we want. This means that the bootloader initially loads the original, signed Samsung kernel, and then while that kernel is running, it actually loads our new, unsigned kernel directly on top of the currently running kernel. The unsigned kernel is then the one handling everything. There is pretty much nothing from the kernel-upwards that we can't modify- it's only the lower level stuff, which is pretty much just the bootloader itself.
We now have an auto-kexec method that streamlines the entire process, too. Previously, the kexec/kernel package had to be flashed in recovery before starting Android, otherwise the new kernel would not be loaded. The auto-kexec method keeps everything on a cache partition, and automatically flashes the package with each reboot. Basically the only drawback to our auto-kexec method is that it takes a bit longer to reboot/start the device, because it must first automatically boot into recovery and flash the package.
Still, this method pretty much entirely circumvents the bootloader. Plus, if you've taken a look at the CM9 install guide for our device, the actual installations of ROMs with auto-exec are now as simple as flashing the custom recovery to the device and then flashing a ROM via recovery. It's near-identical to how you normally flash ROMs.
Because of all this hard work, AOSP ROMs with custom kernels are a reality, and I can only hope we'll see official support from the CyanogenMod team and other major ROM teams.

ExodusC said:
I believe you are mistaken.
I came from a Droid 2 Global, where we had a similar situation. We were stuck on the Gingerbread kernel, and with no kexec, we were unable to chain-load a new kernel. We eventually got ICS ports like CM9, but that's because developers made lots of wrappers to make the existing Android ICS framework compatible with the Gingerbread kernel.
This is different from the Galaxy S3, however. We have a working kexec port that allows us to chain-load any custom kernel we want. This means that the bootloader initially loads the original, signed Samsung kernel, and then while that kernel is running, it actually loads our new, unsigned kernel directly on top of the currently running kernel. The unsigned kernel is then the one handling everything. There is pretty much nothing from the kernel-upwards that we can't modify- it's only the lower level stuff, which is pretty much just the bootloader itself.
We now have an auto-kexec method that streamlines the entire process, too. Previously, the kexec/kernel package had to be flashed in recovery before starting Android, otherwise the new kernel would not be loaded. The auto-kexec method keeps everything on a cache partition, and automatically flashes the package with each reboot. Basically the only drawback to our auto-kexec method is that it takes a bit longer to reboot/start the device, because it must first automatically boot into recovery and flash the package.
Still, this method pretty much entirely circumvents the bootloader. Plus, if you've taken a look at the CM9 install guide for our device, the actual installations of ROMs with auto-exec are now as simple as flashing the custom recovery to the device and then flashing a ROM via recovery. It's near-identical to how you normally flash ROMs.
Because of all this hard work, AOSP ROMs with custom kernels are a reality, and I can only hope we'll see official support from the CyanogenMod team and other major ROM teams.
Click to expand...
Click to collapse
Thank you for your reply. I have no more thanks to give so :good: will have to do. I'll try and come back to give the props you deserve.
My apologies for being so thick on it. I've got a ton to learn.

BarryH_GEG said:
This is Julius Genachowski , head of the FCC.
Does this look like a person who knows what a locked vs. unlocked bootloader is? You guys are shooting over the heads of your audience by assuming they know the terms you're using.
Click to expand...
Click to collapse
No but he looks like the type that would have 3 hot female geek interns that could explain it to him. FCC takes the time to figure out the whole situation I dunno how you can judge what someone looks like as to what power they may have... Hes got the finger that could potentially hit the red button. I mean common hes go a red tie! I'll try and file a complaint this weekend. I'm not really cool with the whole 14 day return deal. I want the phone that was advertised because I had to upgrade due the the fact i was forced to... keep in mind they didn't let us know via Verizon to customer communication only through thrid party...

EDNYLaw regarding locked bootloader's

Author is xda member Ednylaw
To file with the FCC, EDNYLaw has created a formal complaint. To use, simply click the link below, download the .docx and input YOUR name and information required below.
http://dl.dropbox.com/u/26329079/FCC%20Complaint%20Web.docx
Here is EDNYlaw in his own words:
Quoted from Post 55: http://forum.xda-developers.com/showpost.php?p=29945914&postcount=55
EDNYLaw said:
I am the Attorney who wrote that comment on Droid Life and wrote the FCC Complaint. Please direct all your questions to me as I'm happy to answer them and help move things forward. A couple of things:
1) To those that think unlocking a bootloader is pointless with all the workarounds, I don't want to hear it, if that's how you feel, you're entitled to your opinion but please don't pollute this thread with your useless comments. Help or get out. PS: if the bootloader gets unlocked I fully expect either a) a statement from anyone saying it was pointless thanking the community if they choose to unlock or b) you DO NOT unlock your bootloader
2) I have not taken Verizon to court, the FCC did not take Verizon to court. The FCC made a determination that Verizon is violating the C Block regulation (it's a regulation, not law, there's a difference) and fined them. The violation was in regard to tethering apps and Google wallet. While my complaint touched on these things, the gravamen of my complaint was regarding locked bootloaders and custom ROMs, which I believe there is still a significant argument to be made.
3) Anyone who wants to read my full complaint (and send it to the FCC or their US Senators/Representatives under their name) it is located here: https://docs.google.com/document/d/109uYmho_6daIpAl0ACPSFoK0qrd6K9wp5yeqM7dEaoI/edit edit it accordingly as the beginning part was specific to me
4) Keep me informed and up to date about anything. The more minds the better. I've subscribed to this topic so I'll check in when I can.
5) As of yet I can't really think of a cause of action to take Verizon to court other than an injunction, but I'm not even thinking about a lawsuit unless it's funded or I get some help from other attorneys. I have a full time job and I'm learning to develop in my free time so I just don't have the time to pursue a giant lawsuit by myself for free right now
Click to expand...
Click to collapse
EDNYLaw said:
If OP could put this in the OP it'll probably be helpful:
When I say fill in your information I mean:
I've bolded the things you need to fill in
STATE OF YOUR STATE )
)ss:
COUNTY OF YOUR COUNTY )
----------------------------------------------------------------X
In re Verizon Wireless
YOUR NAME
Complainant,
-against-
Verizon Wireless
----------------------------------------------------------------X
You do not need an FCC Complaint Number, the reason I had a complaint number was I had previously sent in a complaint.
Make sure you also "sign" it at the bottom (last page) above where it says Complainant
Click to expand...
Click to collapse
Continued...
EDNYLaw said:
1) Use my complaint (provided in my post above) and in the first part where it says Verizon Wireless against... fill in your name and in the last part where it says "Respectfully Submitted" put your info in (Name, address, telephone, email)
2) I filed the complaint with the FCC and got a BS canned response from Verizon, I refiled and got the same canned BS response. After my Senator followed up I got a response from the FCC saying I could file a formal complaint, but clearly that was just a dead end since I filed 2 formal complaints and pushed the issue with my senator. Though I guess someone at the FCC caught wind because that 7/31 decision seemed to agree with my complaints and the timing was a little too coincidental
3) Completely free: go to fcc.gov and click on file consumer complaint. Email, fax or mail my complaint with your information filled in to them. I would also send it to your US Senators. Anyone from Minnesota, I think Senator Franken would be a great person to follow up with something like this.
4) In order to help out, SPREAD THE WORD! The more people that are vocal about this the better. When I was doing this with Moto I tried to get Droid Life, Android Central and Phandroid to post an article but none of them were interested. I say, spam them and get them to post an article with my complaint and what people can do. Again, the more people that are complaining and vocal, the more likely a response will be had. Give people my complaint to fill in, email the fcc chairman and commissioners (google to find their emails, it's just [email protected]). If you (or someone you know who is interested in this type of thing) is an attorney, feel free to PM me and maybe we can talk about something. Again, I don't have a tremendous amount of time to invest in this for no pay and by myself. But if there were enough attorney's interested I'd do it pro bono (for free) with the help of a group of attorneys.
And as I said, if you have questions about Verizon's policy and potential violations, ask me and I'll try to answer them. I did all the research and writing myself in my spare time and I think I nailed it insofar as the legal issues. There is next to no case law on the specific issues so I had to make legal arguments based on what little resources I had and the plain language of the regulation. Now at least that the FCC has released this decision, there is some precedent that they are actually willing to enforce a regulation instead of being a puppet for the wireless carriers (though I'm not completely convinced they're autonomous, 1.25 million to Verizon is nothing when their profits were 2.4 billion last year, that's .0005% of their profits for those keeping score at home)
Click to expand...
Click to collapse
Thanks EDNYLaw. Mine is going in the mail today!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good bye HTC Rezound, hello Galaxy S3!

Haha this is epic. Here comes another fine Verizon!
Sent from my SCH-I535 using xda app-developers app

Dude I wish you well, and your kinda my hero today lol
Sent from my Xoom using xda premium

Very nice; thanks for posting it.
More momentum for our filing our complaints.
http://forum.xda-developers.com/showthread.php?t=1808956
FCC will win, VZW will send an update....right at the moment I say to myself, "Ah....it took weeks but I have my phone exactly how I want it!"

am i the only one who sees no reason for unlocking the bootloader? we have a perfectly functioning workaround.

brockkk said:
am i the only one who sees no reason for unlocking the bootloader? we have a perfectly functioning workaround.
Click to expand...
Click to collapse
Perfectly is an overstatement. It kinda sucks and we don't have a ton of development cause devs frankly don't want to deal with it.
Sent from my SCH-I535 using xda premium

We do have a good workaround, however we shouldn't need a workaround.
Hopefully this goes somewhere, and Verizon has to fork out some more of that money of ours.

What was the outcome of this letter? It was pre Nexus S, so I assume it's been dealt with?

brockkk said:
am i the only one who sees no reason for unlocking the bootloader? we have a perfectly functioning workaround.
Click to expand...
Click to collapse
Workarounds are a stop-gap, duct tape, a rubber band and bubble gum, and should be temporary. Many (myself included) don't want to deal with it and it isolates us from a significant part of the dev community. One of the reasons I wanted the SIII is for its large, wide-spread attention...but ours is gimped.
The bigger issue is that VZW won't stop at bootloaders; how long before they lock everything?
The biggest issue is VZW is doing an end-run around the law.

AndroidGraphix said:
Just read this and thought it would be nice to share.
http://www.google.com/gwt/x/e?u=htt...Ymho_6daIpAl0ACPSFoK0qrd6K9wp5yeqM7dEaoI/edit
Good bye HTC Rezound, hello Galaxy S3!
Click to expand...
Click to collapse
Where did you read that? Also, keep us updated!!!

ddggttff3 said:
Where did you read that? Also, keep us updated!!!
Click to expand...
Click to collapse
Found on Droid life.
Good bye HTC Rezound, hello Galaxy S3!

Drama queens. The development is fine.

brockkk said:
Drama queens. The development is fine.
Click to expand...
Click to collapse
The reason why we are "drama queens" is because Verizon is violating the law and is telling us that they could care less about that they locked the bootloader even if it violates the Block C since they can somehow get away with stuff like that.

brockkk said:
Drama queens. The development is fine.
Click to expand...
Click to collapse
Obviously a noob with no idea of the potential this phone has and how crippled it is with a locked bootloader. Either that or he is killing time until he can preorder the iphone 5.
Sent from my unlocked GTab 2 running CM10

This guy needs to talk to them about Google wallet. Stupid Verizon.
Sent from my SCH-I535 using xda app-developers app

Anyone know who the author is ??
the title is little misleading only cuz the fcc has not taken them to court yet, and more then likely Verizon will comply before it makes it to court
it looks more of very formal and will written compliant to the fcc (could be wrong still reading from phone)
very valid points presented in the compliant the fcc will diffidently pay attention to this one
i would suggest the author attache the petition in this thread to the complaint
http://forum.xda-developers.com/showthread.php?t=1756483
Sent from my Encrypted S3

Yeah, well. They claim that an unlocked bootloader shaves a few seconds off boot time. But it also has the ability to prevent bricks, and it makes development more open-ended. Right now all of vzw's custom rom devs have to bake kexec into the rom, which require extra work.
Sent from my SCH-I535 using xda app-developers app

To everyone saying that some people here are drama queens, look at all the development the international version has: http://forum.xda-developers.com/forumdisplay.php?f=1566. Just about all I see on that page is ROMs, ROMs, and more jelly bean ROMs. The locked bootloader has turned devs away from our version (as many people have already said). You may be happy with CM10 and a kexec workaround, but a lot of us want more options.

tonu42 said:
Look at how far whining has gotten for the Droid Series by Motorola. No where.
Click to expand...
Click to collapse
Did Motorola have an agreement with the FCC prohibiting such activities?
If it doesn't stop now, how long before your recovery also becomes locked?

kmoore11 said:
To everyone saying that some people here are drama queens, look at all the development the international version has: http://forum.xda-developers.com/forumdisplay.php?f=1566. Just about all I see on that page is ROMs, ROMs, and more jelly bean ROMs. The locked bootloader has turned devs away from our version (as many people have already said). You may be happy with CM10 and a kexec workaround, but a lot of us want more options.
Click to expand...
Click to collapse
International version had a jump on Verizon. Hell every other carrier did. I browsed the first page of at&ts development and counted 7 ROMs Verizon had 4 on their first page. And don't even bother looking at sprints development section. This is all getting blown out of proportion.

[Q] Verizon will not activate

So, I bought a Verizon galaxy s iii off of craigslist, but did not have a sim card to use. So I brought the phone into the verizon store to get a sim card for it, and I was told that the phone is on a "missing or stolen list" so they could not activate it. Would unlocking the phone allow me to activate it, or is there any other solution? Any help would be greatly appreciated.

Should have checked the esn. Might as well sell it on eBay as a bad esn phone for parts.
Sent from my SCH-I535 using xda premium

Only solution is to call the police. Unfortunately you've been scammed.
Sent from my SCH-I535 using xda app-developers app

I thought you could just pop your current 4g sim in and it will work.....you just cannot activate it going from 3g to 4g. I swear i did this to a bad imei thunderbolt and it worked....

This is exactly why you meet people from CL when buying a phone at the verzion store. I make them come in with me, check the ESN. Then we go back out and I give them the money. No other way ever.
Sent from my SCH-I535 using Tapatalk 2

once a person call verizon and reports it lost or stolen it is permanently flagged in their system and cannot be activated anymore, I think in europe all the carriers share banned esn's with each other so you cant just steal a gsm phone and use it on a different gsm carrier, not sure if they do that here
I would see if you can contact the person you got it from but most likely they are long gone and they scammed you knowing full well the phone was stolen, this is why its better to deal with ebay since you are protected from this stuff

do you root your phone?

My issue is very similar but not exactly the same, posting here instead of new thread
This thread seemed to be closest match to what I'm facing... Hi, I'm trying to fix a phone. It's a Samsung Galaxy S3 that's deactivated. It has a Verizon logo on it, but calling 611 connects to AT&T who tells me to call Verizon who claims the imei # is bad because they tried looking it up multiple times and were unable to locate ANY info in their system about it, they recommended that it's not a Verizon phone and I go into the store for the relevant carrier (Which there aren't any AT&T stores around anymore, and I don't feel like walking into Verizon until I've got better/more info so I'm not feeling like an idiot). I believe the phone was previously rooted, because it had a few apps on it such as "rootland" but no su or busybox, but I'm not sure. Rootchecker was already installed but says "no root access" or "root denied". I performed a factory reset. It did nothing. I simply want to have it be capable of being actived on a prepaid acct, I know it was used this way before on Verizon. The baseband is showing as S:i500.05 K.EI20 the kernel version is 2.6.35.7 the model # is SCH-I500. What do I do? My phone number is 60three nine2three 2zero4six my name is Sandra. Please help! I've goggled for hours and simply cannot seem to find any up to date info which is useful! I don't know what to do anymore, my friend needs a working phone as hers sucks and I'm trying to help by getting this one fixed for her to try, because she doesn't have the $ to buy one and this was given to me when the previous owner got a new one and didn't want it anymore but she didn't tell me it was basically a paperweight (probably why she gave it away)... Anyways, help would be fantastic, also I have a computer but no internet, only data plan on my cell, which is why my number is included because if I need to hook it up and hot spot I can but wouldn't be able to communicate online at the same time... The number I provided is connected to a separate phone which is mine and is 100% working, it's a Verizon Galaxy S5 which I'm also trying to root, and it's a pain in the ass not having internet since the block of geohash and towelroot exploit stopped, but I'm close I think, I've done my research and I believe I simply have to down grade the kernel first with odin. I've never actually used odin or rooted a phone but I'm doing my best to learn as much as possible and not bother people. I don't want to be a noob and annoying. Just really stuck here. Sorry msg is so long, figured I'd try to be as detailed as possible to reduce any time on your end so you can either help or point me in a different direction by not having to go back and forth asking questions. Of course if there does happen to be something I left out please don't hesitate to ask. I am seeking your assistance after all. I don't want to bug you or anyone with my issues and lack of ability to sort through... I'm pretty sure I'll have used most of not all my data before being able to read any replies, so calls/text is best to the phone number I included, which I'll repeat again. Sixzerothreeninetwothreetwozerofoursix. I AM PRONG MY PHONE NUMBER ON PURPOSE AND I UNDERSTAND THE RISKS OF DOING SO INCLUDING STALKERS OR CREEPS OR HACKERS OR WEIRDOS ETC ETC ETC. I GET IT. MIGHT BE CALLED STUPID BUT WHATEVER. I'VE HAD THIS NUMBER FOR A VERY LONG TIME AND IT'S NOT HARD TO GET, I GET STRANGE CALLS CONSTANTLY AND I'VE LEARNED HOW TO UNBLOCK CALLER ID AND BLOCK FREAKS FROM CALLING/TEXTING A 2ND TIME. I NEED HELP AND AM WILLING TO CHANCE MORE CALLS/TEXTS OR OTHER ISSUES BY POSTING MY #. I'm a big girl I know the world is scary, I've lived through nightmarish crap, I'll be alright and won't blame anyone but myself if this causes **** to hit the fan. It's official and in writing so xda cannot be held liable AT ALL for ANYTHING, nor can ANYONE ELSE if it is related to my choosing to post this, which I am doing of my own choosing. I'll now eagerly await any help available to fix my issues. I'm hopeful I've come to the right place asking the right people who will help me understand more about what I could do to learn how to get better educated on these topics and in future not require so much of your valuable time. I'm more than willing to put in the time and effort to take responsibility for enacting any actions to perform a solution, I've just gotten very confused and overwhelmed trying to navigate correctly and learn what needs to be done. Pointing me in the correct direction would be wonderful! Thank you in advance!
---------- Post added at 12:41 AM ---------- Previous post was at 12:36 AM ----------
It has a US cellular logo physically on it. Calling 611 puts me through to AT&T, but I know for a fact it was last used on Verizon prepaid.
---------- Post added at 12:49 AM ---------- Previous post was at 12:41 AM ----------
Sorry for that, I have spent so many hours researching the 3 relevant companies, root/unroot info, kernels, roms, builds, learning about variations on android os, and anything I coups find remotely related that I had a slight mix-up, but hope that's now clarified.