Database Info

root/no root

Im coming from a droid x and find to root this alittle challenging. While I cant get root I havent found one that I like. My whole purpose if to just get rid of bloat. After my last attempt I got crappy reception and wanted to unroot. I did and reception was back to normal. After all the problems and what with the gingerbread files I didnt want to go that route with that radio. So what are my options? With the last root attempt I used the 1 click method, was that my problem? Do I need to read up more on adb commands. Or should I say screw it and stay stock? There are multiple roms out there but havent found one for my particular needs. I know I bought this phone to learn more and be a challenge but this is trully a pain in the ass. So comments advise is greatly appreciated.

blueis300 said:
Im coming from a droid x and find to root this alittle challenging. While I cant get root I havent found one that I like. My whole purpose if to just get rid of bloat. After my last attempt I got crappy reception and wanted to unroot. I did and reception was back to normal. After all the problems and what with the gingerbread files I didnt want to go that route with that radio. So what are my options? With the last root attempt I used the 1 click method, was that my problem? Do I need to read up more on adb commands. Or should I say screw it and stay stock? There are multiple roms out there but havent found one for my particular needs. I know I bought this phone to learn more and be a challenge but this is trully a pain in the ass. So comments advise is greatly appreciated.
Click to expand...
Click to collapse
I wouldn't give up if i were you, rooting is the way to go. And ya thunderbolt is "different" but it seems from here on out most lockdown phones will be this perplexing at times, but good news to use, some companies have given up and will open up there future phones boot loaders. And its not because it lock down it just because they weren't "meant to be rooted and optimized for the user".
It seems weird that your reception got worse due to rooting, i have not heard that problem before or seen it posted in these threads. Most of the complants from rooting is either having random reboots, or the unfortunate brick or root didn't actually work for them.
Just make sure your up to date with the froyo radio when you were rooted, I know you cant check now, but maybe you used an older one the auto root method was using? Its worth a check. The newest one has had some good reception Verizon sent in a OTA.
And i used an auto one click way and it worked for me so it may depend on what one you used. But its advised to use adb.
Also there are a lot of basic de-bloat roms out there, they are just buried at the end of this forum, and never get updated because once they are de-bloated there is not much left that needs to be updated.
And dont worry about the Gingerbread problems, I wish i never left Gingerbread, i have had more problems on froyo then i was on gingerbread. With froyo i still have problems, but Gingerbread seems to run so smoothly, and a new leak is hopefully around the corner, there was one up but it was taken down and senior moderators said its coming be patience.
hope this helps

All rooting does is give you access to system files. There's no way that it would mess up your radio.
I'm also curious where the "1 click method" is.

a simple search would lead you to
http://forum.xda-developers.com/showthread.php?t=1009969

SomeGuyDude said:
All rooting does is give you access to system files. There's no way that it would mess up your radio.
I'm also curious where the "1 click method" is.
Click to expand...
Click to collapse
Well here is the file I was pointed to when I first started and I went from having no bars to 1x to 3g to 4g and all over the place.I guess I wont give up because I wanted an challenge but man this is different. More reading reading reading and find more on ADB.
http://depositfiles.com/files/wo74rmphi
Ill try for a couple more days after checking things out a bit.Thanks for the comments and help.

blueis300 said:
Well here is the file I was pointed to when I first started and I went from having no bars to 1x to 3g to 4g and all over the place.I guess I wont give up because I wanted an challenge but man this is different. More reading reading reading and find more on ADB.
http://depositfiles.com/files/wo74rmphi
Ill try for a couple more days after checking things out a bit.Thanks for the comments and help.
Click to expand...
Click to collapse
Never seen that file. Stick to the development section of this forum and you should be gtg. Most of what you need is stickied at the top.
Sent from my ADR6400L using Tapatalk

otakueric said:
a simple search would lead you to
http://forum.xda-developers.com/showthread.php?t=1009969
Click to expand...
Click to collapse
Thanks for the link, in my search I had a couple of other ways to do it but I did search.

Rooting is the only way to TRUELY enjoy this phone and all it has to offer IMO.

Ok well all of a sudden my phone cant receive call or make them but can make and receive texts? Any ideas on that. I got a phone call yesterday but it was a little wack. Called tech support and now no calls.

[Q] voice search bug but no OTA update yet

I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.

3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium

you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062

hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?

Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.

The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box

ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.

like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.

hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S

3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).

ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.

Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?

ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.

3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.

I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.

I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)

ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny

[Q] Touch screen acting up

Hello, I'm back again, in the Q&A section.
So I found a few threads regarding the touch screen on other phones, but I want to ask here so I can be sure...
So a little while after permanently rooting my phone, the touch screen started acting weird... To be specific, I downloaded Dotty, to see where it shows you where the point on the touch screen registers, and near the top, at a little horizontal sliver of the screen, any time I touch there it splits up the point into two different points, right outside of that sliver.
It's made that very difficult to select certain things on the screen, but sometimes the problem goes away after locking and unlocking the phone.
I just want to confirm with someone that this doesn't have to do with a bad ROM or a mistake on my part, as I've flashed multiple ROMS, and gotten the same results. I also tried wiping the phone, but no luck.
The ROM I'm currently using is MikShift - v1.01
If this is a hardware issue, then I guess I'll just have to remove any evidence of rooting the device, and take it to a store, but I was hoping if anyone else has any insight on this.
Thank you.
P.S. I've only had this phone for around 3 or 4 days.

Whitellama said:
Hello, I'm back again, in the Q&A section.
So I found a few threads regarding the touch screen on other phones, but I want to ask here so I can be sure...
So a little while after permanently rooting my phone, the touch screen started acting weird... To be specific, I downloaded Dotty, to see where it shows you where the point on the touch screen registers, and near the top, at a little horizontal sliver of the screen, any time I touch there it splits up the point into two different points, right outside of that sliver.
It's made that very difficult to select certain things on the screen, but sometimes the problem goes away after locking and unlocking the phone.
I just want to confirm with someone that this doesn't have to do with a bad ROM or a mistake on my part, as I've flashed multiple ROMS, and gotten the same results. I also tried wiping the phone, but no luck.
The ROM I'm currently using is MikShift - v1.01
If this is a hardware issue, then I guess I'll just have to remove any evidence of rooting the device, and take it to a store, but I was hoping if anyone else has any insight on this.
Thank you.
P.S. I've only had this phone for around 3 or 4 days.
Click to expand...
Click to collapse
I think this is probably a problem with the hardware. I remember several months ago other people reporting the same problem, maybe just a batch of bad devices. Touchscreen should be %100 functional regardless of the ROM your using.

Okay, that's kind of a downer,thanks anyways though.

#1 thing I have noticed with touchscreen problems: CLEAN THE SCREEN WITH A PAPER TOWEL AND ALCOHOL!!!
2) Uninstall dotty.
3) If that doesn't work, try running fix permissions from clockwork.
4) If that doesn't work there is a touchscreen calibration app in the market I forget what it's called.
5) If that doesn't work wipe the phone completely, and try flashing the latest Cyanogenmod nightly and the latest google apps and see if you have the same problem.
---------- Post added at 01:03 PM ---------- Previous post was at 01:03 PM ----------
crump84 said:
I think this is probably a problem with the hardware. I remember several months ago other people reporting the same problem, maybe just a batch of bad devices. Touchscreen should be %100 functional regardless of the ROM your using.
Click to expand...
Click to collapse
You are too quick.

Whitellama said:
Okay, that's kind of a downer,thanks anyways though.
Click to expand...
Click to collapse
well if you have only had the phone a couple days they should replace the phone no questions asked.

I'll try these...
VICODAN said:
#1 thing I have noticed with touchscreen problems: CLEAN THE SCREEN WITH A PAPER TOWEL AND ALCOHOL!!!
2) Uninstall dotty.
3) If that doesn't work, try running fix permissions from clockwork.
4) If that doesn't work there is a touchscreen calibration app in the market I forget what it's called.
5) If that doesn't work wipe the phone completely, and try flashing the latest Cyanogenmod nightly and the latest google apps and see if you have the same problem.
---------- Post added at 01:03 PM ---------- Previous post was at 01:03 PM ----------
You are too quick.
Click to expand...
Click to collapse
Thank you for the options, I was only assuming it was a hardware problem because everywhere else I looked online, with other phones, that's what people said. I'll try all of these things, and post on the results.
EDIT: Okay, I uninstalled Dotty ( I'm not sure what the point of that was, however), I tried the fix permissions, and I couldn't find the calibration app. If anyone knows where it is, that sounds useful, but I searched and searched. Next, I guess I'll just have to find something optimal for cleaning screens, since I don't think we have alcohol anywhere. I'll try flashing Cyanogen too, since that's easy. Also, there have been times when the touch screen stops working completely.

No luck
Okay, I've tried all of the above, without luck. I'm all ears if anyone has any final advice, but it's really not that much of a hassle to restore everything to the factory default, and take it down to a Sprint Store.
I'm not quite sure how to set everything back to how it was when I got the phone, yet, but I imagine there are guides for that already.

Whitellama said:
Okay, I've tried all of the above, without luck. I'm all ears if anyone has any final advice, but it's really not that much of a hassle to restore everything to the factory default, and take it down to a Sprint Store.
I'm not quite sure how to set everything back to how it was when I got the phone, yet, but I imagine there are guides for that already.
Click to expand...
Click to collapse
Just run RUU

I've already got it back to default, but that probably would've been a faster idea. XD Thanks anyways, though.

Whitellama said:
I've already got it back to default, but that probably would've been a faster idea. XD Thanks anyways, though.
Click to expand...
Click to collapse
No problem buddy! Good luck and let us know how it goes!

Superuser is still around
So like always, I apparently missed the fact that superuser is still on the phone, and quite difficult to remove...
So would flashing the radio fix that? I've dug around a little, but I'm not quite sure which file I should be flashing, or where I can get it.

Whitellama said:
So like always, I apparently missed the fact that superuser is still on the phone, and quite difficult to remove...
So would flashing the radio fix that? I've dug around a little, but I'm not quite sure which file I should be flashing, or where I can get it.
Click to expand...
Click to collapse
If your planning on taking it back to Sprint you'll need to turn s-on, not just remove super user. Run the ruu, you can find mirror at the bottom of the first post here http://forum.xda-developers.com/showthread.php?t=1255474
Sent from Gingerbread Speedy 4G

I have had this problem with two Shifts, and both were replaced by Sprint as faulty hardware. It is quite annoying. I would RUU and take it back.

Yep, I do intend on taking it back.
And thank you crump, I'd be lost without all the awesome people like you on this forum.
I'll do that.
EDIT:
So I checked the page, and all I see is stuff about 2.2... The phone came with 2.3 so this might be a dumb statement but I'm assuming that I'm to run the 2.2 RUU, and upgrade normally back up to 2.3 from there. If I'm wrong, please let me know, otherwise, I'll have at it.

You could also just use the 2.3 RUU for GB. It's posted on THIS thread.

prboy1969 said:
You could also just use the 2.3 RUU for GB. It's posted on THIS thread.
Click to expand...
Click to collapse
OR you could just run the 2.2 ruu and not update and let them know you were rooted as a sign of your anger and protest
but thatll probably just piss them off and not replace it....I would personally do it tho

That suggestion made me smile, but I don't want to take any chances...
And thank you for the 2.3 RUU link! I will download at once!

Welp, my phone just started this too. This marks number 4 for me. I'm getting tired of replacing these things. It's been an average of 1 every two months!

Econ212 said:
Welp, my phone just started this too. This marks number 4 for me. I'm getting tired of replacing these things. It's been an average of 1 every two months!
Click to expand...
Click to collapse
Seriously? I've had the same shift since day 1! That scares the crap out of me if mine ever actually does break. Are they making/refurbing them with cheap lower quality parts or what?

You could revert back to 2.2 and accept the ota... That should load the new hboot. If that doesnt work then i dont know. Most roms Ive had turns off the ota. For good reason i might add. But you can get a hold of one that you can turn it on with. Or get stock 2.2 and update.
Sent from my PG06100 using XDA App

Update?

I have a wifi only Xoom and it is Rooted. My question to you is, since it is rooted I obviously cannot be updated via OTA, it keeps showing up that I need to update. I cannot turn off automatic update when I go to about then update. Its really no big deal tbh, but it is really flipping annoying and just keeps coming back...
I would really appreciate some feed back and hope someone knows how to fix my problem. Thanks XDA!!!
Sent from my Xoom using xda premium

Assuming you have CWM installed, you could follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=1575393
Install the update via CWM and get to 4.0.4 that way...... Ok, its not inhibiting the update notification per-se, but gets you on the latest stock build and keeps your rooted status.....

I would also suggest you check out voodoo root saver on the market. Its supposed to let your root survive an ota update.

Nickitt said:
I have a wifi only Xoom and it is Rooted. My question to you is, since it is rooted I obviously cannot be updated via OTA, it keeps showing up that I need to update. I cannot turn off automatic update when I go to about then update. Its really no big deal tbh, but it is really flipping annoying and just keeps coming back...
I would really appreciate some feed back and hope someone knows how to fix my problem. Thanks XDA!!!
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Make sure you read the "General" and "Android Dev" sections also - don't just ask a question in "Q&A". As stated in post #2, there is an existing (though only about 1 day old) solution - and it worked quite well for me.
Good luck.

willysp said:
Make sure you read the "General" and "Android Dev" sections also - don't just ask a question in "Q&A". As stated in post #2, there is an existing (though only about 1 day old) solution - and it worked quite well for me.
Good luck.
Click to expand...
Click to collapse
Well mister, how about you go ahead and post that sweet little HTML so I may click on it and square this away eh?
Or, it would be amazing if someone can just simply tell me which process to freeze. Cannot find a damn process with the word "update" in it to freeze.
IDGAF about a damn update, like I said, I am CONTENT with everything I have on my XOOM right now. Simply need to find the "process name" to freeze..
Sorry to be short, but I am pissed off, aggravated and personally am about to throw this in the Hudson river.

Nickitt said:
Well mister, how about you go ahead and post that sweet little HTML so I may click on it and square this away eh?
Or, it would be amazing if someone can just simply tell me which process to freeze. Cannot find a damn process with the word "update" in it to freeze.
IDGAF about a damn update, like I said, I am CONTENT with everything I have on my XOOM right now. Simply need to find the "process name" to freeze..
Sorry to be short, but I am pissed off, aggravated and personally am about to throw this in the Hudson river.
Click to expand...
Click to collapse
I thought from your first post that you wanted to be able to update and stay rooted. I referenced the "sweet HTML" already in post #2 as a way to update and stay rooted.

Google Play Broken Beyond Repair?

I have tried a few custom roms and then when I reflash back to any of the 3 stock roms floating out there for the GS3 Verizon my Google Play Store remains permanently broken. Alogcat indicates that it is getting back an unexpected response code 400 from google. I suspect this may mean that it fails to update because SSL is broken in some way but I could be wrong.
I have done all the normal things one does to bring back the market such as clearing the data on Google Play and services framework and rebooting, but that has no positive effect. Nor does deleting my account and re-adding it or creating a new account. Also Google+ will say "No Connection" but once I close out of it and reopen it, it will always log in to my account automatically without error. I will say that the error is reminiscent of the kind of error you would expect if your time is wrong, but it is correct. Any help will be appreciated it..

Go post in Q&A Forum.
iSheep... iSheep... Meowww that's Apple

This does not belong in development.
Sent from my Galaxy SIII

considering that out of all the roms I have tried Play now only works in one of the many roms posted here.. I feel like it is connected.
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies build 20121005 is the only rom I can flash on my device now and having a working Google Play but I absolutely hate this rom. It has bugs, it lacks polish.. yet it also seems as if it screwed up Play in some way on my device... so please install this rom and tell me I should be posting somewhere else.. where everyone only discusses the usual methods of fixing Play and no one takes any real steps to really debug the problem to get to the root of it.

glitchbit said:
considering that out of all the roms I have tried Play now only works in one of the many roms posted here.. I feel like it is connected.
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies build 20121005 is the only rom I can flash on my device now and having a working Google Play but I absolutely hate this rom. It has bugs, it lacks polish.. yet it also seems as if it screwed up Play in some way on my device... so please install this rom and tell me I should be posting somewhere else.. where everyone only discusses the usual methods of fixing Play and no one takes any real steps to really debug the problem to get to the root of it.
Click to expand...
Click to collapse
Doesn't matter if you have the issue on every rom it doesn't belong in the development section. Take the real step of posting this in the proper section.
Sent from my Galaxy SIII

I would have to agree seems like the good place to post it since we are all flashing roms and they bare having this issue... I was pleased to see this here as in have been having this issue on synergy 74 and up and now I see it's others so now all the developers will be aware of what's going on and maybe find a fix
Sent from my SCH-I535 using xda app-developers app

READ FORUM RULES BEFORE POSTING
Development is for Developers to post threads
Questions go in Q&A
Thread moved
Moderator

I love how people comment in a thread telling you that you posted in the wrong section, but don't offer up any advice.
I don't know a whole lot about your issue, but instead of flashing a stock rom maybe you could odin back to stock, accept OTA, and start over?
Not sure if that would clear up your issue, but hope I helped...!

josh995 said:
I love how people comment in a thread telling you that you posted in the wrong section, but don't offer up any advice.
I don't know a whole lot about your issue, but instead of flashing a stock rom maybe you could odin back to stock, accept OTA, and start over?
Not sure if that would clear up your issue, but hope I helped...!
Click to expand...
Click to collapse
Thanks Josh, but yea I have been flashing back to stock via Odin a lot, more times than I can count now! I've been using the HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5 image file but Kies says it is the most recent as well so there is no newer OTA to come down. I've also tried LG and HD roms via Odin, but regardless the Google Play Store remains broken. I am positive that I have restored everything back to its original configuration as per multiple guides on the subject. It is extremely frustrating as I have spent countless hours now trying to fix this one issue. I've spent more time researching this issue on google, in the forums and irc chat rooms and speaking with more devs than what those people would care to know about. There is a serious issue here that is being ignored.
I develop iPhone apps, I do IT support, and network infrastructure for a large manufacturer and I always get a great deal of enjoyment figuring things out but something like this, which should be so simple and just work, ticks me off to no end. For me this just creates the case in point why it makes it difficult for me to care much for the Android platform as a whole. It still has a lot of growing up to do before it catches up with iOS. I use a phone to get from point A to point B and I expect a certain baseline level of performance and things to just work. I left the platform 2 years ago and from the outside it looked as though things have been improving, but I can see now that not much has changed in the OS or community and the platform isn't ready for much of anything beyond a tablet for me personally as it is just a no go as a phone OS.

I would really like to figure this out still.. so to the first person who can give me the resolution or help me significantly in some way I will gift $50 to you over paypal.

Arriving at a solution
glitchbit said:
I would really like to figure this out still.. so to the first person who can give me the resolution or help me significantly in some way I will gift $50 to you over paypal.
Click to expand...
Click to collapse
Well, you don't seem to be flashing a Base ROM using Odin. It being broken like that usually indicates DPI issues, which are carrying across ROMs.
1. Is your phone encrypted? (Do a reset and Erase everything from within, that should fix it) Settings > Backup and Reset > Reset
2. Is the ROM you are flashing using Odin a Base FW?

I had this happen on an old incredible. What it turned out being was that my phone wasn't activated. I don't think that is your problem because it sounds like you use it, but could be a corrupted area of the phone that flashing doesn't touch. I don't think its a ROM because I've flashed them all and my market has always worked.
I would try a couple things to see if either helps. First, Odin back to stock then turn you phone off pull the sim card, boot back up and let it settle, power off put the sim back in and power up. Second, if that doesn't work dial *2767*3855# to repo vision your phone, but this factory resets and people say it erases your internal SD card so back that up. Hope one of those help.
Also if neither of those work, try a new sim card. That seems to fix 90% of peoples problems on this phone.
Sent from my S3 running Eclipse 2.1

kintwofan said:
I had this happen on an old incredible. What it turned out being was that my phone wasn't activated. I don't think that is your problem because it sounds like you use it, but could be a corrupted area of the phone that flashing doesn't touch. I don't think its a ROM because I've flashed them all and my market has always worked.
I would try a couple things to see if either helps. First, Odin back to stock then turn you phone off pull the sim card, boot back up and let it settle, power off put the sim back in and power up. Second, if that doesn't work dial *2767*3855# to repo vision your phone, but this factory resets and people say it erases your internal SD card so back that up. Hope one of those help.
Sent from my S3 running Eclipse 2.1
Click to expand...
Click to collapse
kintwofan, you may be on to something. I have flashed the 3 base roms for my phone G7, LG, and HD to no avail. I actually use this phone on another carrier and so I have manually programmed this phone myself. So there may be something regarding the activation that is causing this issue.

glitchbit said:
kintwofan, you may be on to something. I have flashed the 3 base roms for my phone G7, LG, and HD to no avail. I actually use this phone on another carrier and so I have manually programmed this phone myself. So there may be something regarding the activation that is causing this issue.
Click to expand...
Click to collapse
Sounds like may need a buildprop change. Try changing buildprop to your carrier. Although one of my rezounds is on Tmobile without problems. Using T-mobile APN. S3 should auto add the APN. At least it does with international sim.

Use market enabler then to see if you can tell it your carrier. I'm sure you can Google the apk
You could also still do the reprovision, but I'm sure you'll have to reprogram it.
Sent from my S3 running Eclipse 2.1

Market enabler didn't work on synergy 74
Sent from my SCH-I535 using xda app-developers app

GREGHARKINS said:
Market enabler didn't work on synergy 74
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I assume you're on Verizon so did you try the other suggestion I posted? I used to run synergy with no problem so I would assume something got corrupted on your phone in a segment that isn't flashed.
Sent from my S3 running Eclipse 2.1

OTA attempts to activate this phone on the carrier fails, hence the manual programming. I have tried market enabler and and market unlock but they fail to work in the stock roms and the synergyrom. The only rom that has a working Market/Play is http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies I specifically used 1005 and 1012 and they both work fine.
I don't know what he does differently but it works for whatever reason.. http://forum.xda-developers.com/showthread.php?t=1788443
I just don't really care for the rom, it seems like my reception and wifi has issues on it vs the stock.

glitchbit said:
OTA attempts to activate this phone on the carrier fails, hence the manual programming. I have tried market enabler and and market unlock but they fail to work in the stock roms and the synergyrom. The only rom that has a working Market/Play is http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies I specifically used 1005 and 1012 and they both work fine.
I don't know what he does differently but it works for whatever reason.. http://forum.xda-developers.com/showthread.php?t=1788443
I just don't really care for the rom, it seems like my reception and wifi has issues on it vs the stock.
Click to expand...
Click to collapse
Interesting, so the reprovision didn't work? Have you tried just pulling the play store from his gapps? Also, you could try his jellywiz ROM maybe he did the same thing to it were your play works, if you like touchwiz. I guess you could also upload the build.prop from that working ROM and I'll compare it to mine when I get time and see if I notice any major differences.
By the way have you tried Eclipse ROM, its very nice and bug free.
Sent from my S3 running Eclipse 2.1

Still looks probably to be a buildprop vs carrier change issue. CM is built off source and works and the TW roms are built off different carrier bases and don't work. Playstore looks at the buildprop.