Develop Bugs

Formatting system...?!?

I used to format /system every time I flashed a ROM on my gs2, but I saw in the numerous imei threads some posts about not doing so because it may be part of the lost imei issues. Do you do it ? Have you had issues ? I'm reluctant to do so , but feel it will be " beneficial to my flashing" if I did...
Sent from my SGH-T999 using Tapatalk 2

jasonren29 said:
Format system does not wipe out imei. It's when you root it the wrong way. If you want to play safe, you can go to development section use imei back up method to back it up
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my SGH-T999 using xda premium

No lie I formatted my system the other day and right after tried to revert to a stock android backup that I made. And wasn't able to do so because it told me M.D.5 sum mismatch after I reverted to it earlier in the day. Huh is what I was like and after that clockwork mod recovery would let me restore a cm10 backup I made said something about couldnt restore system. So out of frustration I went back to being unrooted. Just couldn't take the problems with clockwork mod because that's what where the problems ly. It wasn't me it was the recovery
Sent from my SGH-T999 using xda premium

jasonren29 said:
Did you changed the backup in any format? Change name or date? Any minor changes to the backup will fail md5 check
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
None what so ever. I really just flashed the stock back up right before I flashed my gsfree back up so no I made no changes what also ever. Some times when you format systems in clockworkmod recovery this could happen because it happen to me. Can't wait till ext4 touch recovery comes to us here in this forum. Not saying cwm recovery isn't nice but I never had any problems with other recoveries that have been offered.
Sent from my SGH-T999 using xda premium

einrae214 said:
No lie I formatted my system the other day and right after tried to revert to a stock android backup that I made. And wasn't able to do so because it told me M.D.5 sum mismatch after I reverted to it earlier in the day. Huh is what I was like and after that clockwork mod recovery would let me restore a cm10 backup I made said something about couldnt restore system. So out of frustration I went back to being unrooted. Just couldn't take the problems with clockwork mod because that's what where the problems ly. It wasn't me it was the recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
There are ways to fix that issue with the MD5 sum mismatch. I've had it happen a few times and ran a few commands thru ADB and got it working.

Kid Poker said:
There are ways to fix that issue with the MD5 sum mismatch. I've had it happen a few times and ran a few commands thru ADB and got it working.
Click to expand...
Click to collapse
Yes you are right. But I didn't want to go thru all of that. Really didn't have time so just unrooted my phone so there would be no more problems. I get like alot of people and become flash aholics. So I just stop it from being problem later down the road. Look I like rooting and adding mods to my phone like the next guy but there comes to a point where unnecessary issues can be avoided. Like the one I had.... but on the real tip I really enjoy the phone just the way it is STOCK I have zero issues and love the battery life that I have. So until some cooler roms come out I just don't have interest in cm9 or cm10 base roms. I mean I came from the sensation where I could flash a lot more variety of roms. I like this phone the way it is and really that's why I bought it.
Sent from my SGH-T999 using xda premium

[Q] Problem restoring from TWRP backup

Hi everyone. I used TWRP to make a backup of my CM10 nightly so I could flash a TW rom and be able to boot between the two by using the recoveries. Backed up CM10 no problem. Wiped/installed the TW rom (FreeGS3) successfully and it booted just fine. Used it for a little, then I restored my CM10 backup and it just shows the CM10 boot animation and nothing else is happening. I noticed that it made 2 data archives while backing up, but thought nothing of it. Upon further review, I discovered that I can boot with just the 1 data file restored but once I restore the 2nd data file, I get the endless boot animation. Is there anything I can do to solve this? I really need the data I have on here for school and it annoys me that it's sitting in a file that I can't restore!

I posted a question about this same type of issue yesterday here:
http://forum.xda-developers.com/showthread.php?p=31573026
...and nobody has seemed to give a crap. But I too have been having trouble restoring my CM10 nandroids. I dunno what the deal is. It's weird.
Also I posted the question in the CM10 nightly thread, and all I got was, "TWRP works fine for me. TWRP restores fine for me. Blah, blah, blah...
Although did read in other places, rootzwiki and around google that TWRP has been known to not restore CM10 nands well for some reason. Something having to do with it not restoring the kernel data well. And the only way around it is to reflash whatever kernel you were using. Kind of a drag. But I'm with you, my TW rooms have been restoring just fine, but the CM10s have been a mess.
Considering switching back to CWM.
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
I posted a question about this same type of issue yesterday here:
http://forum.xda-developers.com/showthread.php?p=31573026
...and nobody has seemed to give a crap. But I too have been having trouble restoring my CM10 nandroids. I dunno what the deal is. It's weird.
Also I posted the question in the CM10 nightly thread, and all I got was, "TWRP works fine for me. TWRP restores fine for me. Blah, blah, blah...
Although did read in other places, rootzwiki and around google that TWRP has been known to not restore CM10 nands well for some reason. Something having to do with it not restoring the kernel data well. And the only way around it is to reflash whatever kernel you were using. Kind of a drag. But I'm with you, my TW rooms have been restoring just fine, but the CM10s have been a mess.
Considering switching back to CWM.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
So am I basically screwed? I have my notes and stuff for school saved on there and I kinda need them, and about 40,000 text messages. :/ Did yours make 2 data archives?

iTzFeRReTTi said:
So am I basically screwed? I have my notes and stuff for school saved on there and I kinda need them, and about 40,000 text messages. :/ Did yours make 2 data archives?
Click to expand...
Click to collapse
Actually I only get one data archive. But someone somewhere did mention something about using the "extract from nandroid" option in Titanium Backup. I haven't tried it yet, but supposedly it works. I think there's other "extract from nandroid" app on the market if I'm not mistaken.
As of right now, I'm about to email the Team Win development team to ask them about the issue. Maybe they can tell me what's going on. Cuz it's only recently this started happening with the restoring of CM10 nandroids, at least for me.
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
Actually I only get one data archive. But someone somewhere did mention something about using the "extract from nandroid" option in Titanium Backup. I haven't tried it yet, but supposedly it works. I think there's other "extract from nandroid" app on the market if I'm not mistaken.
As of right now, I'm about to email the Team Win development team to ask them about the issue. Maybe they can tell me what's going on. Cuz it's only recently this started happening with the restoring of CM10 nandroids, at least for me.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I've used TWRP to make CM10 backups and this is the first time that this has happened to me and of course it happens when I need it most! I flashed a TW rom so I could flash the corporate PRL (24006). I went to restore my backup and bam, no boot.

iTzFeRReTTi said:
Yeah I've used TWRP to make CM10 backups and this is the first time that this has happened to me and of course it happens when I need it most! I flashed a TW rom so I could flash the corporate PRL (24006). I went to restore my backup and bam, no boot.
Click to expand...
Click to collapse
Same thing happened with me. Did the whole Prl thing, and now they're not restoring well. Happened to me with trying to restore the last three CM10s I've ttied to restore. I dunno if the Prl change would have anything to do with it. Although I did get one to settle down after wiping cache and delvik twice, and fix permissions.
But gonna try it again tonight.
Also, I emailed team win and linked them back to here. Hopefully we'll hear back soon.
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
Same thing happened with me. Did the whole Prl thing, and now they're not restoring well. Happened to me with trying to restore the last three CM10s I've ttied to restore. I dunno if the Prl change would have anything to do with it. Although I did get one to settle down after wiping cache and delvik twice, and fix permissions.
But gonna try it again tonight.
Also, I emailed team win and linked them back to here. Hopefully we'll hear back soon.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I tried changing the PRL back to what it was before the backup and it still doesn't boot unfortunately. :/ Luckily I backed up the TWRP backup to my computer so I don't have to worry about losing it. Does your boot animation just keep playing over and over again after it reboots?

iTzFeRReTTi said:
I tried changing the PRL back to what it was before the backup and it still doesn't boot unfortunately. :/ Luckily I backed up the TWRP backup to my computer so I don't have to worry about losing it. Does your boot animation just keep playing over and over again after it reboots?
Click to expand...
Click to collapse
Yeah it does. For the 3rd one I tried restoring, it at least booted into the rom, but once I started using it, it would force close after a couple minutes. And it would do that over and over. Until I wiped cache and delvik.
Was going to try doing a nandroid with the same prl and restoring. Cuz I've only experienced this problem when I've tried to restore a nandroid with the old prl.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:48 PM ---------- Previous post was at 08:34 PM ----------
Also, here's a link to Nandroid Browser. This should help you to get your stuff for school.
https://play.google.com/store/apps/details?id=de.goddchen.android.nandroidbrowser
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
Yeah it does. For the 3rd one I tried restoring, it at least booted into the rom, but once I started using it, it would force close after a couple minutes. And it would do that over and over. Until I wiped cache and delvik.
Was going to try doing a nandroid with the same prl and restoring. Cuz I've only experienced this problem when I've tried to restore a nandroid with the old prl.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:48 PM ---------- Previous post was at 08:34 PM ----------
Also, here's a link to Nandroid Browser. This should help you to get your stuff for school.
https://play.google.com/store/apps/details?id=de.goddchen.android.nandroidbrowser
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
For the third what you tried restoring? And the nandroid browser doesn't see anything in my CM10 TWRP backup folder.

iTzFeRReTTi said:
For the third what you tried restoring? And the nandroid browser doesn't see anything in my CM10 TWRP backup folder.
Click to expand...
Click to collapse
For the 3rd nandroid, once it booted up, I immediately booted into recovery and wiped cache and delvik, and rebooted. I did that like three times before it settled down a bit. But ultimately it didn't fix it 100%. I still got FCs. Just not as frequent.
But I finally restored a couple "new" nandroids with the same prl, and I had no problems. I really think it had something to do with the two prls clashing.
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
For the 3rd nandroid, once it booted up, I immediately booted into recovery and wiped cache and delvik, and rebooted. I did that like three times before it settled down a bit. But ultimately it didn't fix it 100%. I still got FCs. Just not as frequent.
But I finally restored a couple "new" nandroids with the same prl, and I had no problems. I really think it had something to do with the two prls clashing.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
But I have gone back into my TW rom and updated the PRL back to what my CM10 backup has it and still won't boot. I have narrowed it down to just being the data archives not restoring properly because it will boot if I don't restore data at all, just that I have nothing on there for data. Is there a way I can restore without data, then restore the data while booted into CM10?

iTzFeRReTTi said:
But I have gone back into my TW rom and updated the PRL back to what my CM10 backup has it and still won't boot. I have narrowed it down to just being the data archives not restoring properly because it will boot if I don't restore data at all, just that I have nothing on there for data. Is there a way I can restore without data, then restore the data while booted into CM10?
Click to expand...
Click to collapse
To be honest, I'm stumped about your situation. Because I'm not sure why your old back up is not restoring for you, even tho you change prl back. Cuz my remedy was basically to delete all my old cm10 back ups and start fresh with some new nandroids. And they all seem to be restoring well now that haven't changed the prl. But I know you want to try and salvage your old data. At this point, I'd try and email Team Win and tell them about your situation. They may be able to give you some more tips.
PS . I'm still waiting for a response from the email I sent a couple says ago.
Sent from my SPH-L710 using xda app-developers app

drewmonge said:
To be honest, I'm stumped about your situation. Because I'm not sure why your old back up is not restoring for you, even tho you change prl back. Cuz my remedy was basically to delete all my old cm10 back ups and start fresh with some new nandroids. And they all seem to be restoring well now that haven't changed the prl. But I know you want to try and salvage your old data. At this point, I'd try and email Team Win and tell them about your situation. They may be able to give you some more tips.
PS . I'm still waiting for a response from the email I sent a couple says ago.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Basically it restores fine as long as I don't restore the data files, which are kinda important. :banghead:
Sent from my SPH-L710 using xda app-developers app

By the way, I just threw my CM10 backup on my SD card to see if it would work and it's currently restoring so I'll let you know if it works. I'm just trying anything at this point!
EDIT: It's restoring archive 2 right now! That never happened before. This should be good. So anxious!

OMG IT WORKED! I'M SO HAPPY! drewmonge, put the backup on your SD card and restore and it will work!

It's the kernal. I had the same problem but just from switching between TW and ASOP roms. Flash a new kernal made for whatever type (asop or tw) you're trying to install and it'll work. Mine happened on a s4 though, but I bet same base problem.

Cyanogen 10

I am new to rooting, mods etc. I have managed to get the Cyanogen 10 onto my Sprint Galaxy S3 and put the voicemail app. I find that the phone loses it's data connection intermittently and also sometimes the phone wont turn on and I have to hit the power button for a reboot.
I have searched these forums and the cyanogen ones and there is loose mention of this in posts dated back to August but nothing more recent.
1.) Is this a known bug and/or has it been fixed?
2) Is there a ROM that doesnt suffer from these bugs?
Thanks
BDO

Wrong area to post my friend!
I have SENSATIONS and its WICKED!!

These are questions to be asked in the cm threads

Where is the correct place to post?

bigdaddyo811 said:
Where is the correct place to post?
Click to expand...
Click to collapse
Where you downloaded the rom bro

bigdaddyo811 said:
Where is the correct place to post?
Click to expand...
Click to collapse
Shadefactor said:
Where you downloaded the rom bro
Click to expand...
Click to collapse
While the response given to you is usually correct, you do not meet the requirements to post in a development section. So I have moved your question to the correct section. (Q&A section)
If you have a question about a particular rom that you downloaded, then you will post the question in that particular rom's thread. If it is just a general question, then you post the question in here. (Q&A section).
Development section is strictly reserved for development related items. No question threads should be started in there.

bigdaddyo811 said:
I am new to rooting, mods etc. I have managed to get the Cyanogen 10 onto my Sprint Galaxy S3 and put the voicemail app. I find that the phone loses it's data connection intermittently and also sometimes the phone wont turn on and I have to hit the power button for a reboot.
I have searched these forums and the cyanogen ones and there is loose mention of this in posts dated back to August but nothing more recent.
1.) Is this a known bug and/or has it been fixed?
2) Is there a ROM that doesnt suffer from these bugs?
Thanks
BDO
Click to expand...
Click to collapse
What voicemail app are you using? I'm just curious, I don't think it's related to your issues. I am using Google Voice, but I'd like to know what else is available.
sent from a secret underground bunker

I'm very new to all this and really needed help...
1 - I am rooted and looking to run cyanogenmod and a kernel that supports over and under clocking...I have gaaps zip and the stable cyanogenmod zip on my phone. I did a nandroid backup, a titanium backup and backed up by contacts to Google.
2 - Should I do another nandroid backup when I do a factory reset (before flashing rom) that way I have a backup of the phone completely stock?
3 - After flashing I can reinstall my apps with the free version of titanium backup correct? And will the backup be wiped if it's on internal storage during factory reset?
4 - And do I do a nandroid restore after flashing rom or is that just in case something goes wrong or I don't like the rom?
5 - If I want to over and under clock I still need as kernel right? Basically I just want better battery life...does cyanogenmod generally improve battery life?
Sorry for all the questions I've been doing alot of reading and just not started watching YouTube videos...just wanna be cautious
...thank you
Sent from my SPH-L710 using xda app-developers app

beyeond said:
I'm very new to all this and really needed help...
1 - I am rooted and looking to run cyanogenmod and a kernel that supports over and under clocking...I have gaaps zip and the stable cyanogenmod zip on my phone. I did a nandroid backup, a titanium backup and backed up by contacts to Google.
2 - Should I do another nandroid backup when I do a factory reset (before flashing rom) that way I have a backup of the phone completely stock?
3 - After flashing I can reinstall my apps with the free version of titanium backup correct? And will the backup be wiped if it's on internal storage during factory reset?
4 - And do I do a nandroid restore after flashing rom or is that just in case something goes wrong or I don't like the rom?
5 - If I want to over and under clock I still need as kernel right? Basically I just want better battery life...does cyanogenmod generally improve battery life?
Sorry for all the questions I've been doing alot of reading and just not started watching YouTube videos...just wanna be cautious
...thank you
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I always do a nandroid right before a ROM flash. Then delete any older nandroids I have. You just want to be able to restore your device to it's state immediately before the flash if anything goes wrong.
Your backups will not be wiped. You will be able to restore them, but I seriously suggest purchasing the full version of TB.
Restoring the nandroid will give you exactly what you made the nandroid of. Its a back up if you do want to go back, or if something goes wrong. Only restore it when you want to return to it. I.e. if you don't like CM or if it's not working right.
You need the kernel to oc. The stock CM kernel doesn't do it. Make sure the kernel that you are flashing is meant for the ROM. Otherwise you're in for trouble.
Good questions for a beginner. Good luck.
sent from a secret underground bunker

Thanks so much for the help. If I have a problem with cm10 I can just restore the nandroid, I don't have to un flash it or anything? Just boot to recovery and restore and that's it?
Sent from my SPH-L710 using xda app-developers app

beyeond said:
Thanks so much for the help. If I have a problem with cm10 I can just restore the nandroid, I don't have to un flash it out anything? Just not to recovery and restore and that's it?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That's right. You can just restore it through recovery.
sent from a secret underground bunker

mjben said:
That's right. You can just restore it through recovery.
sent from a secret underground bunker
Click to expand...
Click to collapse
Thanks. One more question. I downloaded the stable version. Its that what I want? If they have a stable one then why do the nightlies.keep getting made? Are they just basically daily beta versions? If I get the latest nightly would I have to do this whole flashing and restoring my apps every time I want the new nightly? Thanks for helping me guys.
Sent from my SPH-L710 using xda app-developers app

I usually stick with the stable release. Not that I know of anything specifically wrong with any nightly; I also haven't read any of the change logs to see what the differences are. I would assume, like you seem to, that the team would be working on improvements.
When I have flashed nightlies, I didn't wipe data and restore apps. Just flashes the nightly, gapps, then clean caches.
BTW, a lot of people do say that restoring apps and their data with TB to a new ROM causes problems. I believe this could be true, but I do it anyway. If any app does give me trouble after a restore I deal with it individually.
sent from a secret underground bunker

mjben said:
I usually stick with the stable release. Not that I know of anything specifically wrong with any nightly; I also haven't read any of the change logs to see what the differences are. I would assume, like you seem to, that the team would be working on improvements.
When I have flashed nightlies, I didn't wipe data and restore apps. Just flashes the nightly, gapps, then clean caches.
BTW, a lot of people do say that restoring apps and their data with TB to a new ROM causes problems. I believe this could be true, but I do it anyway. If any app does give me trouble after a restore I deal with it individually.
sent from a secret underground bunker
Click to expand...
Click to collapse
Can anyone else confirm issues with using titanium backup on a newly flashed rom? That would seem like a pain for those that mod their phone almost daily..
Sprint Galaxy S3 - JB/Stock ROM rooted

Phone restarts before finishing backup restore

Hi.
I have no idea what's wrong. My backups usually restore easily with no problems. I have two backups currently. One made on the 11th and one made on the 15th. I've restored to the 11th many times before because I was testing out ROMs then. I decided I was satisfied with the one I already had, and kept it the way it was, restoring back to the 11th. I've used it since then, downloading apps and stuff. But today, I wanted to try another ROM. So I made the backup for the 15th. I didn't like the ROM i was testing out, so I TRIED to restore to the 15th. But, while restoring on CWM, it just stops, and my phone restarts. I thought it was just ONE bad restore. But I tried multiple times, and the same thing keeps happening. So I decided to restore to the 11th to see if it was just a bad backup, but same thing happens when I try to restore. Please help! I've searched the forums and googled it before posting. But I haven't found any threads with this specific problem. Thanks a lot!

Try clean installing the ROM of the backed up ROM, and then restoring backup.
Sent from my SAMSUNG-SGH-I747 using xda premium

diablo009 said:
Try clean installing the ROM of the backed up ROM, and then restoring backup.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
By clean installing you mean reflashing cm 10.1 and gapps right?

yeeedelta said:
By clean installing you mean reflashing cm 10.1 and gapps right?
Click to expand...
Click to collapse
Yes. The original ROM of which you took backup.

diablo009 said:
Yes. The original ROM of which you took backup.
Click to expand...
Click to collapse
Okay. I tried it. Flashed the original ROM and gapps that I started with. Still the same thing. But, I tried starting from scratch, making a backup of that, and restoring it to see if it was still a problem. But the brand new backup works now, but the others still don't. It seems as if it always restarts when restoring a specific data.

Looks like some data got messed up. Sorry, this is as far as I can think of.
Sent from my SAMSUNG-SGH-I747 using xda premium

What version of cwm are you on?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta

I'm currently using 6.0.3.1. I made the backups using the touch version and tried restoring on touch as well. But I reverted back to this and tried restoring but it didn't work either.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] ROM or phone glitch

I haven't posted enough to be able to ask this question in the development section - I usually find the answers I'm looking for and never feel the need to post - but I started having a lot of problems w/ my phone today.
First off, the ROM I just flashed is the latest Wicked Sensations. Everything was fine for the last 2 days, but this afternoon, the thing started going haywire everytime I would touch the screen. It's like there were multiple screen presses within the same area that I had just touched. When that wasn't happening, it would take a few moments before it would allow any touch input and be ok for a few seconds before going haywire w/ the ghost screen touches. (I know, shotty description.)
Just wondering if it's possibly my phone, the ROM, or if anyone else experienced this. I saw no one else that had in that thread so I'm wondering where I should go from here. Reflash, new ROM, throw the phone against the wall...?
Thx!

Make backup in recovery
Then wipe EVERYTHING, system, data, internal sdcard (if you have nothing.you.need) and cache
Note reflash your rom and wait a day or two before restoring any apps/data

CNexus said:
Make backup in recovery
Then wipe EVERYTHING, system, data, internal sdcard (if you have nothing.you.need) and cache
Note reflash your rom and wait a day or two before restoring any apps/data
Click to expand...
Click to collapse
I will reflash, but I have a question about making a backup - if I make a backup of it as it is now, won't it save whatever may be causing it to glitch like this?
FYI - When I flashed the ROM, I wiped everything through TWRP but don't remember if the option for the internal sdcard was checked, or if there was an option. I didn't save any old apps so I didn't restore anything. Once I had what I wanted, I made a backup within the hour. Would that be a possibility next to reflashing the ROM again (restoring from this backup)?

ki77en said:
I will reflash, but I have a question about making a backup - if I make a backup of it as it is now, won't it save whatever may be causing it to glitch like this?
FYI - When I flashed the ROM, I wiped everything through TWRP but don't remember if the option for the internal sdcard was checked, or if there was an option. I didn't save any old apps so I didn't restore anything. Once I had what I wanted, I made a backup within the hour. Would that be a possibility next to reflashing the ROM again (restoring from this backup)?
Click to expand...
Click to collapse
Hmm, you could try that, add long add it was a full clean flash
And in TWRP when you choose Wipe > Advanced Wipe, it gives you a series of check boxes to choose what to write and if you choose /data, it wipes /data/media too which is the internal storage

CNexus said:
Hmm, you could try that, add long add it was a full clean flash
And in TWRP when you choose Wipe > Advanced Wipe, it gives you a series of check boxes to choose what to write and if you choose /data, it wipes /data/media too which is the internal storage
Click to expand...
Click to collapse
Doing as suggested - backup, full wipe and reflashing. Will give it a couple days and see how it goes, then reply back to this thread. (As I sit here wondering if I should just check out another ROM...)
Thx!

ki77en said:
Doing as suggested - backup, full wipe and reflashing. Will give it a couple days and see how it goes, then reply back to this thread. (As I sit here wondering if I should just check out another ROM...)
Thx!
Click to expand...
Click to collapse
No problem! Be sure to ask if you have any other questions or concerns

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Guess I didn't read enough
Well last night it took all of about 2hrs before the touch sensitivity went haywire again, so just for the h3ll of it I tried another ROM. That time the bad effects were immediate.
I'm now on the backup I made of the stock and rooted ROM which gives me no problems. Not sure what in the updates could be causing the problem but I would hate to hear that I'm up the creek w/out a paddle.
Going to try installing the system updates after I remove root unless there's another suggestion.
Thanks for any advice.
Sent from my SPH-L710 using xda premium

ki77en said:
Guess I didn't read enough
Well last night it took all of about 2hrs before the touch sensitivity went haywire again, so just for the h3ll of it I tried another ROM. That time the bad effects were immediate.
I'm now on the backup I made of the stock and rooted ROM which gives me no problems. Not sure what in the updates could be causing the problem but I would hate to hear that I'm up the creek w/out a paddle.
Going to try installing the system updates after I remove root unless there's another suggestion.
Thanks for any advice.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Hmm, could have been a bad download

could have been a bad rom download. try re downloading the rom. maybe transfer it to your phone with a diferent cable. heck, maybe restart your computer first and try doing these steps again. something you might want to try also, after you flash your phone and restart it let it sit 5 minutes or so before touching it as the rom needs to finish building caches doing it's thing,

I don't think it's ROM related b/c when I went to recovery after that latest flash...Well I just happened to be using the latest TWRP and since it's touch operated, well it was a fun time trying to work w/ it while the screen was going haywire. Point is, it did it in recovery, too.
My thoughts are this - try installing system updates like 'normal' and if nothing goes wrong w/ the screen, then try a ROM but skip the part of clearing the system data and only wipe cache and dalvik.
How does that sound?
Sent from my SPH-L710 using xda premium

ki77en said:
...Point is, it did it in recovery, too.
Click to expand...
Click to collapse
Well. Hate to just break it to you like this, but it definitely sounds like a hardware problem if it did it in recovery too

CNexus said:
Well. Hate to just break it to you like this, but it definitely sounds like a hardware problem if it did it in recovery too
Click to expand...
Click to collapse
I was going to throw out hardware issue too. @ the op, does stock still not give you the ghost touch issue still? If it doesn't, then I'm not sure entirely. I'd recommend using a different recovery and checking the md5 of your rom then do a completely clean flash. Maybe your phone just doesn't play nicely with twrp
Sent from my SPH-L710

Yes, I was thinking hardware too but I'm just confused as to why it's only w/ updated software that it goes goofy. That's why I was thinking of trying the updates on the stock ROM to see if that was where the problem was. If it is, then I'm insured and should be able to take it in to the Sprint store.
With the original ROM I first tried, I tried 4 different downloads and when I first noticed the problem, that's when I went to the Wicked Sensations ROM. These all included the most recent OTA.
Btw.. I mostly download to my phone via my WiFi. I did try pc to phone in that ROM that I downloaded several times, but it was still the same.
Sent from my SPH-L710 using xda premium

ki77en said:
Yes, I was thinking hardware too but I'm just confused as to why it's only w/ updated software that it goes goofy. That's why I was thinking of trying the updates on the stock ROM to see if that was where the problem was. If it is, then I'm insured and should be able to take it in to the Sprint store.
With the original ROM I first tried, I tried 4 different downloads and when I first noticed the problem, that's when I went to the Wicked Sensations ROM. These all included the most recent OTA.
Btw.. I mostly download to my phone via my WiFi. I did try pc to phone in that ROM that I downloaded several times, but it was still the same.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Well, it could've been a bad download, but the recovery thing just throws me off on that

CNexus said:
Well, it could've been a bad download, but the recovery thing just throws me off on that
Click to expand...
Click to collapse
I've only tried TWRP in the last couple days b/c it was suggested in the installation instructions of the particular ROMS. Would like to know why.
I like it, but CWM has never done me wrong.
Flashed the updated stock rom from this thread and kept root w/ the zip that's on that thread. Nothing's happening, of course, which is not only confusing but irritating.
Just downloaded the last ROM I tried last night onto my laptop and will transfer it and try it again after I make a backup of its current state. Will also take the suggestion of letting it sit for several minutes before seeing if the ghost is still following me.

ki77en said:
I've only tried TWRP in the last couple days b/c it was suggested in the installation instructions of the particular ROMS. Would like to know why.
I like it, but CWM has never done me wrong.
Flashed the updated stock rom from this thread and kept root w/ the zip that's on that thread. Nothing's happening, of course, which is not only confusing but irritating.
Just downloaded the last ROM I tried last night onto my laptop and will transfer it and try it again after I make a backup of its current state. Will also take the suggestion of letting it sit for several minutes before seeing if the ghost is still following me.
Click to expand...
Click to collapse
Always check md5 of Rom downloads, that will rule out a bad download
Sent from my ANTHRAX sniffing GS3

Personally, I would resort to odin and start from a fresh slate. See if you can wipe the system and internal storage from twrp(or cwm), then flash the stock image and go through the whole rooting process (using the toolbox). That way, you can rule out software related issues if it's still a problem. Also, I'd see if it's still there before rooting..that's what I would do...
---------- Post added at 05:14 AM ---------- Previous post was at 05:05 AM ----------
ehabnoreddin said:
Personally, I would resort to odin and start from a fresh slate. See if you can wipe the system and internal storage from twrp(or cwm), then flash the stock image and go through the whole rooting process (using the toolbox). That way, you can rule out software related issues if it's still a problem. Also, I'd see if it's still there before rooting..that's what I would do...
Click to expand...
Click to collapse
My bad... You JUST said you basically did that...

I did as I said I was going to do and flashed the stock. Lost my recovery so I tried Odin for the first time and put it back on there and proceeded to make a backup of its current state.
A few hours later I went ahead and flashed the new from I transferred over and I'm happy to say that everything is allll good... so far.
Never had any problems on the updated stock so it doesn't seem to be hardware related but it took a couple days later on one rom which is when I originally posted.
Sent from my SPH-L710 using xda premium