DO NOT UNDER AND CIRCUMSTANCE USE THESE RECOVERIES
CWM TOUCH
There is something wrong with the original CWM touch and the way it handles partitions.
THESE WILL CORRUPT YOUR /DATA & /EMMC PARTITIONS AND YOUR PHONE WILL NEVER BOOT AGAIN
There are tons of posts about this problem
http://forum.xda-developers.com/showthread.php?t=1504808
http://forum.xda-developers.com/showthread.php?p=22794885
+ any thread with brick in the title -
Read these threads all you want, the common problem is touch recovery screwing up /data and /emmc. NOT EVEN A TAR W/ PIT IN ODIN WILL WORK
BEWARE.
Once you get it all screwed up and try to fix it with odin, you'll get stuck here. (image below) I have tried odin 1.82/1.83/1.85 & Heimdall with the .pit and re-partition option enabled, Still doesn't work.
Really?!?!?! have used touch recovery like 20 times and had no problems except for 1 soft brick
Sent from my SPH-D710 using XDA App
*GalaxyDev* said:
Really?!?!?! have used touch recovery like 20 times and had no problems except for 1 soft brick
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Seems to be happening when you do a factory wipe from inside the touch recoveries.
Sent from my SPH-D710 using XDA App
I'll keep this in mind I actually have to think if I've done a factory wipe with the touch recovery yet not sure I have. But outside of that I've not had any problems with the touch recovery.
No offense, but I feel that people who use touch recovery are not acting as smart as they really are.... You can accidentally wipe your phone completely without an issue....
I'm sure if there was really an issue the downloads would have been pulled by the devs.
I don't think the issue is in the recovery but rather User Error. I used Touch Recovery about 100 times to test my theme before Rogue Recovery came out for FB15. I no longer use it but I never wiped with it, I knew it was temporary and those who treated it as an all out Recovery are those who probably got bricked. I don't like it when people brick phones and I do feel bad for those who are bricked.
URGENT The beer is bad! Nobody drink the beer!
I hafta agree with ssconcepts.
Sent from my SPH-D710 using XDA App
If i save 1 phone its worth it.
With folks trying out ICS, many will want to return to GB, and may try and wipe with Touch Recovery. This will corrupt the /data and /emmc partitions.
Can't fix my phone no matter what I attempt.
I'm just saying with all the other recoveries there was no real wrong move.
Hit a wrong button in touch and its over.
Don't wipe/format anything with a touch recovery to be safe. I just want to help others I'm not trying to scare people away.
BTW - Check Out
http://forum.xda-developers.com/showthread.php?t=1504808
Look at how many views there are.
We should start a check-in.
I have the Rogue Hitman kernel & recovery on my now-obsolete GB nandroid and I never had problems with it...Then again I never factory wiped. I always used Calkulin's wipeall .zip thing.
This is from someone else but it is very close to what i did:
I just couldn't help myself and I flashed shabbys ICS test build this morning. Well the more I started reading in the thread about guys having issues restoring there backups I tried it. Flashed the cwm touch recovery....did a full wipe and then went to restore my nand of Blend. Booted up and gets stuck at the Samsung boot screen. I let it sit there for about 10 minutes. Then from there I pressed volume up and power to see if i could get back into cwm. I was able to and had rogue recovery. I then went to do a full wipe again. The data wipe took about 2 minutes....which was strange...then wiped cache and dalvik. Then went to flash Blend(not the nand backup) and again stuck at the samsung boot screen.
So I then went into odin mode and attempted to odin back to stock using the D710USEL29_20120105.stock from qb777's you tube vid. All went good....got the pass and once again stuck at the Samsung boot screen. Then from there I went back into odin download mode and attempted to odin the stock rooted file(not the file to keep your data file) and it got stuck at "Data.img" in odin.
Good lookin out posting this here glass. I'm not confident enough to put it ALL on touch recovery. I've used touch before plenty of times with zero issues, with this phone and the HTC Thunderbolt.
BUT one person I trust as I believe we all do is sfhub. If you read thru the "stuck at data.img" thread it sounds as if he is leaning toward the touch recovery being the issue. I'm not speaking for him tho.
As for the person earlier stating user error....I did exactly what was stated to do in an ICS op. The only thing I used the touch recovery for was wiping and restoring a backup and all went to sh#t from there.
Obviously ya'll do what you want, I just got my replacement phone today and I'm staying the hell away from touch recovery. I think now the risks far out way the advantage of just touching your screen instead of using volume buttons. Maybe just take a few minutes to read thru these "bricked threads" and decide for yourself.
I wonder if there's a way to safely run an Android virtual machine on a PC and try to recreate this without sacrificing a phone.
I didn't think we were supposed to wipe when recovering a Nand. Perhaps I'm wrong but might this be the problem?
Sent from my SPH-D710 using XDA App
I don't think it was necessarily the touch recovery that bricked my phone. I think it was the way the touch recovery is handled because it's temporary and the way ICS is handled.
I used the permanent touch recovery on EL29 and only soft bricked once. Other than that it worked fine.
The permabrick happened after I had been using FB17 flawlessly for just under 24 hours. I wanted to check out the ICS 4 ICS theme. So I loaded up the temp touch recovery and flash the deodex fb17 rom. Worked fine. Reflashed temp touch again. Flashed theme. Worked fine. Noticed rom was laggy.
This is where things went south. I flashed the temp recovery. Because I wanted a clean install I figured I'd do a factory reset and wipe everything a couple times. It froze in the middle of the factory reset while wiping data. I think it was at this point that the partition got borked.
I think if I had odin'd everything instead of using the temp touch recovery I would have been fine. This is of course my own fault. There were bricks prior to mine and I didn't do my homework.
However, I do agree with a warning for everyone that this has been happening.
Sent from my SPH-D710 using Tapatalk
may i ask why is this in the Q&A? Its not a question.. and its not the answer to everyone problem since 50% is saying it is the recovery and then 50% say its just the user.... but half of the people who use it and restored from ICS got this error..so someone with a bad ESN phone need to test both methods and see whats up
dgn_sandibalz said:
I don't think it was necessarily the touch recovery that bricked my phone. I think it was the way the touch recovery is handled because it's temporary and the way ICS is handled.
I used the permanent touch recovery on EL29 and only soft bricked once. Other than that it worked fine.
The permabrick happened after I had been using FB17 flawlessly for just under 24 hours. I wanted to check out the ICS 4 ICS theme. So I loaded up the temp touch recovery and flash the deodex fb17 rom. Worked fine. Reflashed temp touch again. Flashed theme. Worked fine. Noticed rom was laggy.
This is where things went south. I flashed the temp recovery. Because I wanted a clean install I figured I'd do a factory reset and wipe everything a couple times. It froze in the middle of the factory reset while wiping data. I think it was at this point that the partition got borked.
I think if I had odin'd everything instead of using the temp touch recovery I would have been fine. This is of course my own fault. There were bricks prior to mine and I didn't do my homework.
However, I do agree with a warning for everyone that this has been happening.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
That sucks. Maybe the OP should edit the title of his post to"don't fake flash and/or wipe with temp cwm touch" and leave hitman out of this.
Sent from my SPH-D710 using XDA App
Sfhub just posted what he thinks is happening in the stuck at data.img thread. Makes sense.......even to a dumba#s like myself.
Its not tje actual touch recovery. Its when u use it as a temp flash recovery. I did the same thing by wiping data. I tried for three hours flashing everything created for this phone and nothing. Data and emmc gone!!!
Sent from my Nexus S 4G using xda premium
Related
Hey guys,
so i was on a plane yestarday and obviously they want you to turn your phone off. I did so and when i landed i tried turning it back on but only to my surprise it would. Was just stuck at the White HTC screen and just kept resetting and doing the same.
Luckily I was able to get into the bootloader and reflash the rom and backup, however, its a pain in the butt to have to do so every time my phone shuts off or I have to shut it off.
Havent tried another custom rom yet, will do so shortly, but just wondering why this is happening? Any advice?
What rom were you on? And make sure to install with a clean install.
i was using calkulins evio rom.
and yes, i did a full factory wipe with cache and dalvik as well....is there all required for a clean install?
hasseye said:
i was using calkulins evio rom.
and yes, i did a full factory wipe with cache and dalvik as well....is there all required for a clean install?
Click to expand...
Click to collapse
You pretty much want to wipe everything but the sd card. So cache, data, dalvik, boot, and system. Then flash your rom and boot it up.
Sent from my hand with XDA Premium installed
I have this same problem with calks rom. Maybe try a different kernel?
Sent from my PC36100 using Tapatalk
Fyi, if you used cwm to do the wipe, this is probably where you failed. Cwm fails to wipe dalvik most times. I have had weird issues on sense roms specially when using cwm. I changed to ra and no wipe problems since.
How do I know this? After so called full wipes using cwm and installing evio most or all of my apps and settings would still be there.
I have confirmed this with many others that have used both recoveries. Ra is nicer anyway.
Real men don't need rom manager anyway.
Sent from my EVO 4G using XDA Premium App
hermanlf said:
Fyi, if you used cwm to do the wipe, this is probably where you failed. Cwm fails to wipe dalvik most times. I have had weird issues on sense roms specially when using cwm. I changed to ra and no wipe problems since.
How do I know this? After so called full wipes using cwm and installing evio most or all of my apps and settings would still be there.
I have confirmed this with many others that have used both recoveries. Ra is nicer anyway.
Real men don't need rom manager anyway.
Sent from my EVO 4G using XDA Premium App
Click to expand...
Click to collapse
I just don't understand why koush dosen't fix this and be done with it. I love that program... I use titanium backups dalvik cleaner anywho just saying that all
I'm having this sort of issue as well. I have wiped many times, gone back to stock, unrooted, even updated the hboot version. Has anyone figured out what exactly may cause this sort of boot loop? Sometimes, my phone just randomly reboots (even on stock default) and gets stuck in a boot loop.
Keeping the battery out for about 5 minutes allows it to boot back up, but I'm getting rather frustrated with it. I can't seem to pinpoint an exact issue. sometimes, it seems my battery is rather warm to the touch, sometimes, it's nice and cool. I've tried sense roms, non-sense, GB, and as I said earlier, stock RUU. Nothing I've done stops the reboots. I took it to the sprint store, and they saw nothing wrong with it. (Of course, it didn't reboot for them. Figures, eh?) I even got 2 alternate batteries. (One was the super big extended life)
Has anyone else had this same issue? I'm at a loss of where to go from here. I've poured over these forums, and the development forums for days. I never had this issue before...it's only started happening in the last week and a half. Keep thinking I must have missed something, but I'm not sure what.
Ok here is a strange thing I can't wrap my head around. I have been rooting and flashing for quite awhile, but have a problem I cant solve....I have a EVO hardware 2 about a year old that has been rooted and running MIUI fine for several months. I recently have been playing with kernels and undervolting. I noticed some random reboots and tried resetting voltages back to normal and flashing diffrent kernels back, but still it locks on bootup or reboots. So I RUU flashed back to stock and everything worked fine, boots good no reboots and temp around 34 deg. nice and stable. Figured all was good re-rooted and boom back to not booting again. I have tried old nand backups that were stable but they do the same thing. Is there some trick to doing a full wipe that I an missing? Also just to mention I recently had problems with the GPS locking on and add the new driver to try and fix it...
Thanks for any ideas....
PS new info...I put a blank card with just the new miui flash on it and reflashed.....it seems to fix the problem...there must be some settings on the card that conrols the cpu settings....will test further and report...may help someone else...
What recovery are ya running?...sounds like its not wiping corectly.....if yur using CWM I would recommend AMON....ALSO.....SUPERWIPE is the way to go....wipes system,data, and boot twice when u flash it....I'm lying in bed and my PC is shut down....u can just google SUPERWIPE ....and for AMON just head over to his thread for his PC36IMG.....BUT IT SOUNDS LIKE YUR RECOVERY ISNT WIPING PROPERLY......would hurt to try em
Sent from my PC36100 using XDA Premium App
If you have Amon Ra, you really don't need those "super wipe" things.
Just wipe all twice and then do cache and dalvik again, separately, and you'll be fine.
Even that's over kill....
HipKat said:
If you have Amon Ra, you really don't need those "super wipe" things.
Just wipe all twice and then do cache and dalvik again, separately, and you'll be fine.
Even that's over kill....
Click to expand...
Click to collapse
Dood I've always wiped ALL and dalv twice....up until a couple of months ago.....ran into a lot of bootloops....BIG TIME....but I figured it wild be a little reassuring for him......also I'm not sure what the other responses he got else where.....al personal preference I guess......have a good one guys
Sent from my PC36100 using XDA Premium App
I was running stock rooted G.B. 2.3.6 and just to see what would happen (I kinda knew already) I did the official upgrade to the ICS 4.0.3. Of course it went from UVKL1 to UVLE1 and I had backed everything up with Titanium Backup and also with Rom Manager. I lost root, because I did a factory reset because it wouldn't install the first 2 times. Oh, I was doing it through Kies. I wanted to do it by the book sort of.So after the install I tried to get root again but when I got into CWM recovery I had no functions working except reboot. No update.zip from sd, or anything else. I could scroll up and down and stop on the different options but when I pushed the button to make the choice it jumped back to reboot and that is all I can get. I rebooted and retried 4 or 5 times and same thing. So, now what ? I like the 4.0.3 but hate the massive amount of bloat and the ads and f**ked up notification popup/ads. I want my root back. I would be willing to start fresh again with a good, fast, everything works, custom ICS but don't know which to choose. that is one of the reasons why I tried this "official" upgrade. Again, as always, Thanks in advance for everyone who helps anyone here on XDA. K.K.-Out
Have you tried reflashing cwm?
Sent from my SGH-T989 using XDA
khkaiser13 said:
I was running stock rooted G.B. 2.3.6 and just to see what would happen (I kinda knew already) I did the official upgrade to the ICS 4.0.3. Of course it went from UVKL1 to UVLE1 and I had backed everything up with Titanium Backup and also with Rom Manager. I lost root, because I did a factory reset because it wouldn't install the first 2 times. Oh, I was doing it through Kies. I wanted to do it by the book sort of.So after the install I tried to get root again but when I got into CWM recovery I had no functions working except reboot. No update.zip from sd, or anything else. I could scroll up and down and stop on the different options but when I pushed the button to make the choice it jumped back to reboot and that is all I can get. I rebooted and retried 4 or 5 times and same thing. So, now what ? I like the 4.0.3 but hate the massive amount of bloat and the ads and f**ked up notification popup/ads. I want my root back. I would be willing to start fresh again with a good, fast, everything works, custom ICS but don't know which to choose. that is one of the reasons why I tried this "official" upgrade. Again, as always, Thanks in advance for everyone who helps anyone here on XDA. K.K.-Out[/QUOT
Try this
http://forum.xda-developers.com/showthread.php?p=3649
Vibrant- Kankwich CM9
Galaxy S2 Hercules- An amazing machine on any rom. Believe me!!
Click to expand...
Click to collapse
blackangst said:
Have you tried reflashing cwm?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
I haven't tried anything yet. I haven't had time. I will try as you suggest. it was on my list of things to try. Thanks, Blackangst.
khkaiser13 said:
I haven't tried anything yet. I haven't had time. I will try as you suggest. it was on my list of things to try. Thanks, Blackangst.
Click to expand...
Click to collapse
I hope it works for you. Check the md5 to make sure you don't have a corrupt download too (of cwm)
Sent from my SGH-T989 using XDA
Thanks ToledoG28, I tried that link and it wasn't a good page. I appreciate the effort. Maybe you could double check it and let me know.
OP: Here's CWM 5.0.2.6. After flashing and once youre back into your phone, you can install ROM manager and upgrade to whatever you want. Push this via Odin.
This happened to me. I had just had to wipe the cache in recovery and it booted. I would try that first
You have to use darkside wipe and darkside cache wipe. The regular recovery wipe isn't working properly.
You just need to Odin ics.
Sent from my SGH-T989 using xda premium
Guys he can't get into recovery. How can he flash super wipe etc if he can't? And how will odining ics fix that? He needs to odin the recovery i posted.
Sent from my SGH-T989 using XDA
I got it solved you guys. Thanks to all of you. I did another factory reset, and then found the actual T989 Hercules .tar file (the one I used was from a post for ICS from November or December and was actually an Infuse tar file.) and reinstalled it. I was able to after I got cwm recovery old style not touch. Touch was what was giving me problems. So I Odin the new Hercules.tar and then rereinstalled Superuser zip and everything went smooth. The only thing I am seeing as a problem is the phone won't sleep. If I have the phone plugged in, I can't shut it off. It wants to immediately turn itself back on. I like to have it shut down and charge at night sometimes. But it won't let me. Any ideas? Thanks again everybody.
I cannot speak for other CWM builds but when trying to flash Jedi Knight 3 with my T989 I notice many issues. Phone sticks when trying to restart...constantly missing NFC/Android Beam...and then once getting everything re-installed it hangs at one of the loading screens when trying to restart the phone...so as a recommendation like the uploader of this ROM states, use TWRP recovery.
In case you are unsure of how to get TWRP, download GooManager from the market, when you are in the app, hit the menu key, then click Install OpenRecoveryScript, tap Yes, and then ensure that the file name contains your specific model number. If it does, go ahead with the download and it will automatically install, once done, choose the option to Reboot Recovery. There you have it, you should now be able to access TWRP recovery mode.
Anyone else have any suggestions when it comes to this ROM build? I personally enjoy its look and feel and a lot of the features, especially the Yoda ringtone (which I am sure can be obtained elsewhere, but who does not love to be lazy?!? lol)
I made a thread earlier explaining why TW roms malfunction with CWM.
http://forum.xda-developers.com/showthread.php?t=1926754
Flash TWRP and wipe WITHOUT TDJs scripts.
Sent from my SGH-T989 using xda premium
RushAOZ said:
I made a thread earlier explaining why TW roms malfunction with CWM.
http://forum.xda-developers.com/showthread.php?t=1926754
Flash TWRP and wipe WITHOUT TDJs scripts.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
HA! I actually used that post quite a bit before switching to TWRP. I was referencing that post and the Jedi Knight 3 post to do everything, but after countless failed attempts with CWM I got the phone re-flashed and booted and then went the easy route of getting TWRP on my phone.
It was kind of sad that CWM had so many issues, especially when I would hang in the restart process from the Android environment and then during the boot process it would get stuck on the loading screen. Became very annoying, but now that I have TWRP, so far everything seems to be working properly, except for NFC/Android Beam, but I did find an enabler on here so I guess I am gonna give that a try and see if that works.
jacodaburr said:
HA! I actually used that post quite a bit before switching to TWRP. I was referencing that post and the Jedi Knight 3 post to do everything, but after countless failed attempts with CWM I got the phone re-flashed and booted and then went the easy route of getting TWRP on my phone.
It was kind of sad that CWM had so many issues, especially when I would hang in the restart process from the Android environment and then during the boot process it would get stuck on the loading screen. Became very annoying, but now that I have TWRP, so far everything seems to be working properly, except for NFC/Android Beam, but I did find an enabler on here so I guess I am gonna give that a try and see if that works.
Click to expand...
Click to collapse
Lol good thing you got it working.
Sent from my SGH-T989 using xda premium
RushAOZ said:
Lol good thing you got it working.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
So far yes, slowly re-installing all my apps because before I would re-install all my apps and then try to restart the phone and it would hang at the loading screen. Got about 5-10 of my 50+ apps restored, and so far so good!
jacodaburr said:
So far yes, slowly re-installing all my apps because before I would re-install all my apps and then try to restart the phone and it would hang at the loading screen. Got about 5-10 of my 50+ apps restored, and so far so good!
Click to expand...
Click to collapse
You shouldn't have a reboot hang with twrp even if you used the super wipe script. Like I said in my other post for some reason the super wipe script breaks the roms ability to reboot with CWM. That's why TDJ made the cache wipe script so it would fix reboot issues because CWM 5.0.2.7 has a few issues. You should be gold bud!
Sent from my SGH-T989 using xda premium
RushAOZ said:
You shouldn't have a reboot hang with twrp even if you used the super wipe script. Like I said in my other post for some reason the super wipe script breaks the roms ability to reboot with CWM. That's why TDJ made the cache wipe script so it would fix reboot issues because CWM 5.0.2.7 has a few issues. You should be gold bud!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Everything was fine and dandy, was able to reinstall apps, and then I restarted the phone, now it is giving me a SIM Error.
EDIT: Scratch that, shut the phone off, left it off for a minute, and turned it back on, now the SIM registers, although Wi-Fi Calling is telling me SIM in invalid for for Wi-Fi calling. It is funny the hoops I've had to jump through for this...Wi-Fi calling fixed... love this stuff!!! Now if I can just figure out how to get the NFC/Android Beam to work---NFC/Android Beam have re-appeared...
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