Develop Bugs

[Q] Issues with rooted T989

My wife has a rooted SSGSII with the stock rom. I have the same phone but have a custom rom. She has alot of weird issues like sometimes freezes when a call comes in, her time in the system bar is often incorrect. She uses Magic Locker and sometimes her time in Magic Locker doesn't match the system time or they may both be off. I wonder if anyone has had this kind of issue. We have replaced the SIM card already. She used Titanium Backup to bring back her apps from her old Droid after rooting. I don't have any of these problems at all but she has crazy issues like this. Any thought about what might be contributing to these issues?

I've never experienced this before, but I have had major issues with titanium backup to the point that I no longer use it. Have you tried reflashing without using titanium?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

No. We didn't flash her device. We just used TB to restore some of her apps after she rooted it. TB website said it would be OK to use it with a Stock Rom.
Sent from my SGH-T989 using xda app-developers app

i would assume TB meant it would be okay if it was from the same device... its not best when you're restoring apps from a completely different phone. I you sure its completely stock? i would just go ahead and flash a custom rom.

Thanks for the help. Think I will flash a custom rom and see if that helps the issue.

Often times if you use TB to restore apps and previous app data, this will happen. Couple options. Try restoring just the app without the data, or use ODIN to flash a clean stock, then re-root and start over. A clean can resolve a lot of issues. I ODIN my phone at least once a month regardless.

sombionix said:
Often times if you use TB to restore apps and previous app data, this will happen. Couple options. Try restoring just the app without the data, or use ODIN to flash a clean stock, then re-root and start over. A clean can resolve a lot of issues. I ODIN my phone at least once a month regardless.
Click to expand...
Click to collapse
Yeah but stock ics have glitches
Sent from my SGH-T989 using xda app-developers app

Symlink: Some Symlinks failed

Can anyone advise how one would go about fixing the S3's internal partition tables? I believe I need to flash someone else's table?
Help!
Some context:
I've been having this issue where my S3 runs into a symlink failure/Status 7 error whenever I try to flash a Jelly Bean rom, ie. CM10/PA/Jellybro. This occurred despite me having the latest 5.8.4.7. CWM, wiped and reformatted EVERYTHING, etc. I posted a sample of where the recovery error log shows the flashing processes failing here:
http://forum.xda-developers.com/showpost.php?p=30287780&postcount=302
Lots of XDA member offered advice with no avail. I remember one member mentioned something about partition tables, so I dug a little deeper. I noticed that the error log also contained error messages about missing directories and my sd-ext not mounting, which is strange since I can access my external sdcard under /mnt/extsdcard directory, and the two directory names aren't matching. So I downloaded an partition table app and saw the following:
http://imgur.com/6r4Vo
Basically, it looks like my partition tables are somehow corrupted and my sdcard and external SD is being mounted for use, but somehow...incorrectly. I'm thinking this is the likely culprit.

What was the app you ran to get that? And what rom were you running when you took that screenshot?
You said its happening when you try to flash jellybean. Do you have any problems with cm9, or stock?
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
What was the app you ran to get that? And what rom were you running when you took that screenshot?
You said its happening when you try to flash jellybean. Do you have any problems with cm9, or stock?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I ran this app called partition table.
https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsImNvbS5jbHMucGFydGl0aW9uIl0.
Oy, I missed the reviews where people are saying that this returns bogus info.
Anyways, here's the situation with what I could/could not flash
-Could not flash CM10/ParanoidA/Jellybro/one other ICS rom that I couldn't think of
-COULD flash CM9, as well as restore nandroid backup of older redrum stripped stock (which is what I ran this off of)
-Tried to flash from CWM/TWRP, neither worked
Back to the partition table, even though that app may be malfunctioning, there were still lines in the recovery error log that indicated that the loader was trying to access /sd-ext, when the external SD in my CWM is displayed as /external_sd. Also, it was trying to reference, edit, and delete from non-existent sources, which seems to indicate that these instructions are being misdirected. If this sounds like another error, I'm all ears.

Well, that is an odd problem! If stock based and other roms flash and run normally, I seriously doubt it'll be a partition related problem. While in cwm recovery, in mounts and storage did you check to make sure your sd was mounted? I may be wrong but I seem to remember some had problems with it correctly recognizing the external sd. In twrp there should be an option just above the slider to use either internal or external.
Sounds like its a problem more with your recovery to me. Try downloading goo.im from play store and use that to install the latest twrp recovery.
If that doesn't work the only other thing I can think to try is to apply the FULL latest update from samsung, UVALH I believe. Install using kies and I think it will rewrite the whole system to pure stock. You will have to reroot, but its definately worth trying before messing with the partitions. If you do that, use goo.im to reinstall twrp and give it a go again.
If I think of anything else to try ill let you know but for now that's the best I can think of.
Just to be sure what model phone do you have? T999, T999V, i9300?
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Well, that is an odd problem! If stock based and other roms flash and run normally, I seriously doubt it'll be a partition related problem. While in cwm recovery, in mounts and storage did you check to make sure your sd was mounted? I may be wrong but I seem to remember some had problems with it correctly recognizing the external sd. In twrp there should be an option just above the slider to use either internal or external.
Sounds like its a problem more with your recovery to me. Try downloading goo.im from play store and use that to install the latest twrp recovery.
If that doesn't work the only other thing I can think to try is to apply the FULL latest update from samsung, UVALH I believe. Install using kies and I think it will rewrite the whole system to pure stock. You will have to reroot, but its definately worth trying before messing with the partitions. If you do that, use goo.im to reinstall twrp and give it a go again.
If I think of anything else to try ill let you know but for now that's the best I can think of.
Just to be sure what model phone do you have? T999, T999V, i9300?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I'm on the T999, T-Mobile.
To your question I've tried TWRP and CWM and neither works. The external SD cards were mounted in recovery during my attempts. I've actually tried using an earlier version of CWM to flash directly from the external SD card, to the exact same results.
I'll try the Samsung update; my hope is that it also provides a partition refresh. It is indeed a unique problem!

Its the best thing I can think of, so hope it fixes everything. If it is a corrupt partition it should rewrite it, so lets hope!
One other thing, what version of twrp were you using? 2.2.1.1 is the latest for our phone. I think there's an older unofficial one out there and even though it would say the sd was mounted, you would have to go into the backup section and look at available space to confirm that. There were also problems with the touch cwm recovery...
I think the way the gs3 handles the sdcard is part of the problem with those though.
Anyway, good luck! Let me know how it goes!
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Its the best thing I can think of, so hope it fixes everything. If it is a corrupt partition it should rewrite it, so lets hope!
One other thing, what version of twrp were you using? 2.2.1.1 is the latest for our phone. I think there's an older unofficial one out there and even though it would say the sd was mounted, you would have to go into the backup section and look at available space to confirm that. There were also problems with the touch cwm recovery...
I think the way the gs3 handles the sdcard is part of the problem with those though.
Anyway, good luck! Let me know how it goes!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
TWRP didn't work and neither did flashing the new Samsung update.
I'm absolutely baffled at this point. I can't find what the hell are causing these symlink errors anywhere.

Sorry I don't have any other ideas. Just to be sure though, did you flash the rooted rom, or use kies or odin to install the update directly from samsung?
Actually, one or two more ideas, though I wouldn't expect much at this point.
You could try using odin to reflash the original shipped version....you never know.
Or
Go into the updater-script and wherever it tries to use /sd-ext, change it to /external_sd, or whatever your error log says its looking for.
Definately ask another dev if its worth trying before doing that!
You may want to examine what is happening with any simlinks in there as well. Unfortunately Im probably not the best person to troubleshoot that stuff. But if you want to attach a copy of your logfile ill be glad to take a look.
Sorry I haven't been better help for you.
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Sorry I don't have any other ideas. Just to be sure though, did you flash the rooted rom, or use kies or odin to install the update directly from samsung?
Actually, one or two more ideas, though I wouldn't expect much at this point.
You could try using odin to reflash the original shipped version....you never know.
Or
Go into the updater-script and wherever it tries to use /sd-ext, change it to /external_sd, or whatever your error log says its looking for.
Definately ask another dev if its worth trying before doing that!
You may want to examine what is happening with any simlinks in there as well. Unfortunately Im probably not the best person to troubleshoot that stuff. But if you want to attach a copy of your logfile ill be glad to take a look.
Sorry I haven't been better help for you.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
No I'm more than appreciative, believe me.
I've attached some log files from various attempts. There are some common error lines, including various referencing missing directories and such.
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Click to expand...
Click to collapse

Cool, just got home so ill take a look at these in a bit.
In the meantime there's a new rom, Speed Rom which you may want to try. A few min ago I saw the dev had posted that it is in fact based on cm10.
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Cool, just got home so ill take a look at these in a bit.
In the meantime there's a new rom, Speed Rom which you may want to try. A few min ago I saw the dev had posted that it is in fact based on cm10.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Hey, I actually fixed it; It turns out I had to reflash a stock insecure kernel, reboot into recovery, AND force a signature check to get it to work. It's strange, because the first flash had some issues and upon trying to reflash it I had to repeat the whole kernel flash process all over again or else it ran into the same symlink error.
I had tried flashing other kernels before but still had errors; it took be sitting down and flashing every kernel for the phone I could find, paired with a ODIN stock flash, to get it to work. I'm still not sure why this phone seems to have this sensitivity about it.
Anyways, thanks for your help; I'm going to post this around in case anyone else has this issue.

Awesome! Great work figuring that out!
(And props for changing the title!)
I'm still a little confused as to why symlinks were failing, but in the end as long as there's a resolution Im thinking it'll be ok!
After getting it to install again have you tried installing anything from recovery? Just curious if its a problem you will have to dance around on future flashes, or if this seems to have solved it altogether.
Either way, excellent job! I love solutions!
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Awesome! Great work figuring that out!
(And props for changing the title!)
I'm still a little confused as to why symlinks were failing, but in the end as long as there's a resolution Im thinking it'll be ok!
After getting it to install again have you tried installing anything from recovery? Just curious if its a problem you will have to dance around on future flashes, or if this seems to have solved it altogether.
Either way, excellent job! I love solutions!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I just can't tell. And it's also worth noting that that failure occurred with different kernels.
I'm going to flash more JB roms as they come along but I'll have backups ready this time. Ostensibly, now that I have a base down I should be able to get around similar errors with a little elbow grease, as opposed to days of OCD-driven anguish. But you'll note that I already ran into the error right after successfully flashed it the first time. I still feel like there's some setting or another that needs to be adjusted in the background. But for now, at least I can sleep.
Cheers and thanks for the help and suggestions mate. :good:

Rest well! You deserve it after all that!
And id be keeping multiple nandroid backups laying around!
Anyway, I've only had a chance to glance at those logs you posted. Now that things have calmed down ill look at em more closely in case anything jumps out at me. I think you are probably right that there is still some issue in there somewhere. I don't know about you but I hate that feeling!
But at least that sense of urgency is diminished!
Ill let you know if I find anything a little later.
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Rest well! You deserve it after all that!
And id be keeping multiple nandroid backups laying around!
Anyway, I've only had a chance to glance at those logs you posted. Now that things have calmed down ill look at em more closely in case anything jumps out at me. I think you are probably right that there is still some issue in there somewhere. I don't know about you but I hate that feeling!
But at least that sense of urgency is diminished!
Ill let you know if I find anything a little later.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I just tried to flash the latest 8/20 CM10 with all of the aforementioned precautions and it failed a couple of times, even reflashing the 8/18 rom from last night didn't work. It seems like after several tries it just...clicked? And it then did flash.
I wonder if it's a bad sector in my internal memory?

Ugh, I would hope not. How long have you had the phone? If you can it may be worth thinking about trying to exchange for another.
Bad memory can cause all sorts of crazy problems. If it were me I might not want to risk waiting to see how it goes.
Sent from my SGH-T999 using xda app-developers app

I have similar issues. If I flash speed rom or any cm10, I get the error. Also if I flash wicked v2 it won't boot, this is a rom based on stock4.0.4. My question is where did you find the signature verification? I have stock recovery 3e I believe, but don't see that option.
Btw, all other roms flash and run fine, including aokp, wicked v1, xquisite, and everything else.

You'll have to have a custom recovery installed.
Sent from my SGH-T999 using xda app-developers app

feckmu said:
I have similar issues. If I flash speed rom or any cm10, I get the error. Also if I flash wicked v2 it won't boot, this is a rom based on stock4.0.4. My question is where did you find the signature verification? I have stock recovery 3e I believe, but don't see that option.
Btw, all other roms flash and run fine, including aokp, wicked v1, xquisite, and everything else.
Click to expand...
Click to collapse
DocHoliday77 said:
You'll have to have a custom recovery installed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Right, you'll want CWM or (I think) TWRP. CWM definitely has it; you should be able to flash it from rom manager if nothing else.

Meh, looks like I'm right back where i started, symlink failures up the wazoo again.
Need to find way to flash roms in ODIN, if that's even possible.

[Q] Anything other than a TW and my camera just wont work, Help?

Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?

Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.

The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.

I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.

mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)

mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.

try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use

mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/

run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.

mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA

Was it already rooted?
Sent from my SGH-T999 using xda premium

mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that

Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium

mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.

This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium

mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though

dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium

mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.

dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium

[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

[Q] Quantum Rom issues

Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.

It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk

codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow

DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.

iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.

also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.

What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.

Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)

DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things

DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...

supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.