Database Info

User error-fixed

OK, with all my messaging and calendar issues, I decided to re-flash the stock tar (as I had used the old method of rooting). I set the phone up again, and now I am still stuck at the start up screen with the rings. It will not go any further. It works fine as long as I do not shut the phone down. From what I can tell, in order to fix it, I need to factory reset, which I am hoping to not do this time again (for the third time in a day). Where should or can I go from here?

redownload the tar file again, check the md5 sum to make sure its good.
Also make sure the tar file is for your carrier, ie; verizon. that may be your problem.

Ended up they are sending me a new device. Could be the device? Could be an app or setting I am restoring with TB though. Not sure. It is getting kind of frustraing since I am not hacking this as I have other phones in the past and am having more trouble with this than any other phone.

LTLFTCer said:
Ended up they are sending me a new device.
Click to expand...
Click to collapse
This is why we can't have nice things. If people didn't waste so much of Verizon's time and money with their hacking maybe Verizon wouldn't feel the need to fight so hard to keep us from being able to hack our phones.

Did you flash stock with recovery or did you Odin back? Cuz if you odin'ed back, you may have missed the step to uncheck auto reboot, then load stock recovery mode and wipe phone. If you Odin to stock and don't after that, but before booting, you will most likely boot loop or freeze.
For future reference....

jimmiem said:
This is why we can't have nice things. If people didn't waste so much of Verizon's time and money with their hacking maybe Verizon wouldn't feel the need to fight so hard to keep us from being able to hack our phones.
Click to expand...
Click to collapse
Andthis is why XDA sucks sometimes. Guys like you who troll and decide to post in a thread in a negative way instead of helping out earlier. And in all actuality, what is happening to my phone I do not think has anything to do with rooting. I had rooted on 7/9 for the sole purpose of wifi tether, nothing else had been done to the phone. It worked flawlessly until this week when the borwser, calendar and facebook decided to start force closing for no apparent reason. I figured a reboot would help and that started these issues. Sooo..therefore I decided to revert back from scratch and the problem is still there. I think we all would know that Verizon care wouldn't be able to hel outside exchanging the phone.
TechSavvy2 said:
Did you flash stock with recovery or did you Odin back? Cuz if you odin'ed back, you may have missed the step to uncheck auto reboot, then load stock recovery mode and wipe phone. If you Odin to stock and don't after that, but before booting, you will most likely boot loop or freeze.
For future reference....
Click to expand...
Click to collapse
Thanks, I did uncheck autoreboot. And was able to enter stock recovery. I actually factory reset again and other than the calendar issues, seems to be working fine so far.

LTLFTCer said:
Andthis is why XDA sucks sometimes. Guys like you who troll and decide to post in a thread in a negative way instead of helping out earlier.
Click to expand...
Click to collapse
You haven't even waited a day after posting for help before calling Verizon.. Too many people on these forums feel like Verizon is obligated to correct their problems even though they went against their Terms of Service..
Sent from my Commodore 64..
READY.
load"*",8,1

Hypnosis4U2NV said:
You haven't even waited a day after posting for help before calling Verizon.. Too many people on these forums feel like Verizon is obligated to correct their problems even though they went against their Terms of Service..
Sent from my Commodore 64..
READY.
load"*",8,1
Click to expand...
Click to collapse
Maybe so, but this didn't appear to be a root issue. Since this phone is so locked down I hadn't messed with anything and was getting multiple random force closes and then got stuck at the boot screen. No biggie, think I got it sorted out, went throgh and manually reset all settings and apps. Seems to have worked.

I'm glad you fixed the issue yourself..
Sent from my Commodore 64..
READY.
load"*",8,1

Another IMEI Q..

So, sorry to ask another one of these questions, but I don't wanna mess up my phone. So, my understanding is that if you flash ANYTHING, CM10, CM9, or a TW ROM, you have a chance of losing your IMEI? Because as of right now I have rooted my phone and unlocked my bootloader but I don't wanna go any farther if there's a chance I can mess up, because with my luck, I will...
Oh, and is there a chance I can get messed up just being rooted and unlocked if Verizon decides to push an OTA or anything really.

Yes, there is a chance to lose your imei anytime you flash. However, if you search, there is a way to back it up and restore it 100%. Use search.
Since you have already unlocked your bootloader, never accept an OTA. There is a possibility it could brick your phone.
Sent from an overpriced Verizon tower.

My understanding is that there is a small chance you can lose your IMEI no matter what ROM you're flashing. I personally flash 2-3 ROMs almost everyday and haven't had any issues though. You can also restore your IMEI using QPST. There's a thread that shows how.
If you're running stock rooted with the insecure aboot, I strongly suggest disabling the OTA update app so verizon can't sneak an update to your phone. I think its FWUpgrade.apk. Accepting an OTA could brick your phone if its unlocked.
Sent from my SCH-I500 using xda app-developers app

knifedroid said:
Yes, there is a chance to lose your imei anytime you flash. However, if you search, there is a way to back it up and restore it 100%. Use search.
Since you have already unlocked your bootloader, never accept an OTA. There is a possibility it could brick your phone.
Sent from an overpriced Verizon tower.
Click to expand...
Click to collapse
yep ive had it happen flashing AOKP on one phone and then flashing synergy on another...
didnt back up the first, but did botth ways of backing up on second and still both ways fail to work... had to inject both of em.

Okay, thanks guys. Another concern is that the only computers in my house are macs (Not my decision) and I'm not sure if I can do all of the IMEI restore stuff without having to shell out for a VM program...

xlxfoxxlx said:
yep ive had it happen flashing AOKP on one phone and then flashing synergy on another...
didnt back up the first, but did botth ways of backing up on second and still both ways fail to work... had to inject both of em.
Click to expand...
Click to collapse
What do you mean by inject?
I haven't had an issue yet (knock on wood), so I haven't had to go through it yet. I've also decided to take a break from flashing until someone gets a better handle on the problem, but I have read of at least one occurrence of the imei disappearing while receiving a text well after flashing a ROM.
Sent from an overpriced Verizon tower.

After much pain and thrashing I finally got injecting my IMEI to work on OS X running VirtualBox and Windows 8 Preview (which you can currently download for free).
I'll do a writeup sharing my knowledge of how to get it done over virtualization.

xlxfoxxlx said:
did botth ways of backing up on second and still both ways fail to work... had to inject both of em.
Click to expand...
Click to collapse
This is concerning to me. After injection, my understanding is that everything works but the phone reads as roaming. My basic understanding from reading all the IMEI threads under the Development Forum is that people are still looking to fix the roaming issue

toddbw said:
After much pain and thrashing I finally got injecting my IMEI to work on OS X running VirtualBox and Windows 8 Preview (which you can currently download for free).
I'll do a writeup sharing my knowledge of how to get it done over virtualization.
Click to expand...
Click to collapse
This would be appreciated! Mac users, I've found, are left out in the dark for a lot of stuff for android...

nyjumpman said:
This is concerning to me. After injection, my understanding is that everything works but the phone reads as roaming. My basic understanding from reading all the IMEI threads under the Development Forum is that people are still looking to fix the roaming issue
Click to expand...
Click to collapse
Does the roaming issue have any negative effects?

xCHPx said:
Does the roaming issue have any negative effects?
Click to expand...
Click to collapse
Not apparently, but there's always the chance Verizon can get unhappy about it, as they provide roaming for free.
I've heard a reprovision can fix the roaming issue, but you'll need to be on TW and the reprovision will do a full wipe as a side effect.
I don't know if roaming is even fixable theoretically, but if it is, you can probably just be on roaming until the devs figure something out.

WildZontar said:
Not apparently, but there's always the chance Verizon can get unhappy about it, as they provide roaming for free.
I've heard a reprovision can fix the roaming issue, but you'll need to be on TW and the reprovision will do a full wipe as a side effect.
I don't know if roaming is even fixable theoretically, but if it is, you can probably just be on roaming until the devs figure something out.
Click to expand...
Click to collapse
Okay, thank you. It doesn't really make sense that it would switch to roaming, but what do I know

What does IMEI refer to???? May lose if I flash a custom ROM?

I hear people referring to IMEI and that may lose it of they flash a custom ROM? What does this to refer to and what are the implications?
Thank you -

IMEI
If you flash a non TW ROM you could lose your IMEI, which allows you to log on to the Verizon network. If it gets borked you'll have to restore a back-up or try to restore from the IMEI number in the battery compartment. There are a couple of great threads on hot to do it. Just Search. I just backed-up mine and it was really easy. Don't forget to thank the DEV. They are amazing. If i could have children I would want one of there's.
Jothen2002 said:
I hear people referring to IMEI and that may lose it of they flash a custom ROM? What does this to refer to and what are the implications?
Thank you -
Click to expand...
Click to collapse

You can lose it with a TW rom as well.
Sent from my SCH-I535 using xda app-developers app

Consider the IMEI as a serial number of sorts that's unique to your device (though not necessarily true) so that it can identify itself to the network through the sim card. Also consider that it can be corrupted and removed for many unknown reasons at this time.
Moral of the story: Back it up before making any changes to the phone.
This method backs it up from stock while your IMEI is still intact: http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/
This method with attempt to repair said IMEI when it's gone south/missing: http://forum.xda-developers.com/showthread.php?t=1802024

tu3218 said:
You can lose it with a TW rom as well.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Actually if you're on stock rom/kernel then you don't have to worry about randomly losing your IMEI. It only seems to occur when flashing or running a custom kernel. This means a custom touchwiz kernel can cause it.
Some people are saying its not a preventable issue. I'm sure I'm not alone in thinking that's unacceptable. I'm hopeful one of the many smart devs working on this phone can figure it out. This phone has overcome too much to be gimped by an issue like this. The IMEI issue essentially makes running custom kernels impractical for people who cannot afford to lose their phone's basic functions; it can happen at any given time.
I'll continue to hope that since this issue exists across all carrier editions it will be solved.

Div033 said:
Actually if you're on stock rom/kernel then you don't have to worry about randomly losing your IMEI. It only seems to occur when flashing or running a custom kernel. This means a custom touchwiz kernel can cause it.
Some people are saying its not a preventable issue. I'm sure I'm not alone in thinking that's unacceptable. I'm hopeful one of the many smart devs working on this phone can figure it out. This phone has overcome too much to be gimped by an issue like this. The IMEI issue essentially makes running custom kernels impractical for people who cannot afford to lose their phone's basic functions; it can happen at any given time.
I'll continue to hope that since this issue exists across all carrier editions it will be solved.
Click to expand...
Click to collapse
First of all thanks for sharing...
So I have already installed a custom rom ( currently synergy r39) and a custom kernel imoseyon 0.2.2...
So I better go make a back up ASAP ...

I lost mine once while running an unofficial cm nightly. I flashed it and everything worked fine. Then I restarted the phone and I lost my imei. It was a pretty quick fix because I backed up efs.bin file. I then used the qualcomm tool to restore the imei and then I pushed the efs.bin backup over the current one. I then reflashed that cm nightly again and I was working again. It took about 25 min. The only downside is if this happens and you don't have a computer you can't use your phone till you get to one.
Best thing is to not panic and check the threads here. It's an easy fix. I wouldn't be worried.
Sent from my SCH-I535 using xda premium

Div033 said:
Some people are saying its not a preventable issue. I'm sure I'm not alone in thinking that's unacceptable. I'm hopeful one of the many smart devs working on this phone can figure it out. This phone has overcome too much to be gimped by an issue like this. The IMEI issue essentially makes running custom kernels impractical for people who cannot afford to lose their phone's basic functions; it can happen at any given time.
I'll continue to hope that since this issue exists across all carrier editions it will be solved.
Click to expand...
Click to collapse
+ 1
This issue has pretty much scared me away from flashing. The set up I have going is working, so I'm hesitant to take nightlies for a test drive and increase my chances of being without a phone until I can cuss enough to get it fixed.
Sent from an overpriced Verizon tower.

I'm curious if the AT&T or Sprint Galaxy S III owners are seeing this IMEI issue much, as well.
- ooofest

ooofest said:
I'm curious if the AT&T or Sprint Galaxy S III owners are seeing this IMEI issue much, as well.
- ooofest
Click to expand...
Click to collapse
All variants are.
Sent from my SCH-I535 using xda premium

ruben8448 said:
I lost mine once while running an unofficial cm nightly. I flashed it and everything worked fine. Then I restarted the phone and I lost my imei. It was a pretty quick fix because I backed up efs.bin file. I then used the qualcomm tool to restore the imei and then I pushed the efs.bin backup over the current one. I then reflashed that cm nightly again and I was working again. It took about 25 min. The only downside is if this happens and you don't have a computer you can't use your phone till you get to one.
Best thing is to not panic and check the threads here. It's an easy fix. I wouldn't be worried.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Had a couple questions for you as I'm running the CM10 alpha and about to move to the nightlies. Is there any advantage to backing up the efs.bin file as opposed to creating the QCN file that is described in the IMEI backup threads? Can you use QPST to backup the efs.bin? It sounds like its better to have both than just the QCN file. Sorry I don't know what exactly the efs.bin file is so apologies if I'm not making sense.
Thanks!

xsteven77x said:
All variants are.
Click to expand...
Click to collapse
Yeah, I have been getting that impression from reading around since my post.
I'm not going beyond root for this phone until something more definitive to prevent the IMEI issue can be found.
I must have flashed ROMs on my Incredible hundreds of times, quite casually, and it seems best to avoid the problems we're seeing with people who have attempted to restore their identifier and still have roaming indicator showing, etc.
- ooofest

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.

Might need new SIM, should I unroot?

I've just moved to college, and ever since then I've been having a lot of issues with mobile data. It worked better a few days ago, but now I can't get any internet at all. I called Verizon, and they said that since my signal strength is alright, and that they report having towers in my area, this should not be happening. The rep suggested that the SIM card is damaged, and that I might need to go get a new one.
This is plausable, since my phone has been getting much hotter lately, since I'm walking around campus more. One MicroSD card has already corrupted on me, and the second one almost did. I guess it's possible the heat is damaging both the MicroSD cards and the SIM card.
So here's my question: I'm rooted, and I'm running HyperDrive RLS9 as my daily driver. Will they need to check something on the phone in order to give me the SIM? Would it be a problem if they did find out I am rooted, and give me trouble for it?
I'd really, really hate to flash back to stock and unroot, so I'm asking if anyone has had experience in dealing with the Verizon reps and whether or not this will be an issue.
Thanks in advance.
Sent from my SCH-I545 using xda app-developers app

BJSerpas said:
I've just moved to college, and ever since then I've been having a lot of issues with mobile data. It worked better a few days ago, but now I can't get any internet at all. I called Verizon, and they said that since my signal strength is alright, and that they report having towers in my area, this should not be happening. The rep suggested that the SIM card is damaged, and that I might need to go get a new one.
This is plausable, since my phone has been getting much hotter lately, since I'm walking around campus more. One MicroSD card has already corrupted on me, and the second one almost did. I guess it's possible the heat is damaging both the MicroSD cards and the SIM card.
So here's my question: I'm rooted, and I'm running HyperDrive RLS9 as my daily driver. Will they need to check something on the phone in order to give me the SIM? Would it be a problem if they did find out I am rooted, and give me trouble for it?
I'd really, really hate to flash back to stock and unroot, so I'm asking if anyone has had experience in dealing with the Verizon reps and whether or not this will be an issue.
Thanks in advance.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
All I could say from experience is just flash a stock ROM to your phone then take it in. Also have you tried a factory reset?
Sent from my SCH-I545 using xda app-developers app

If you have another device just take that one if you don't want to Flash back to stock. Otherwise just flash back to stock and un-root just to be on the extra safe side.

clapper66 said:
All I could say from experience is just flash a stock ROM to your phone then take it in. Also have you tried a factory reset?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I pretty much planned to flash back to stock before bringing it. I did do a factory reset, but it didn't help any.
xRECKSx said:
If you have another device just take that one if you don't want to Flash back to stock. Otherwise just flash back to stock and un-root just to be on the extra safe side.
Click to expand...
Click to collapse
I don't have another device, unfortunately. It looks like I'll have to go through the process of unrooting, although I need to be careful, since if I accidentally flash VRUAME7 somehow, I'm stuck.
Any recommendations on the quickest way to unroot/flash stock? I of course plan on immediately rooting again after I get the new SIM, provided my network issues are fixed.
Sent from my SCH-I545 using xda app-developers app