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
Related
I saw that the final release of cm7 came out and I'm super excited for it! I've been running RC3 for awhile and it's been working fine, but there have been some issues that I would like to have fixed with the update.
My question is: Is there a way to update the rom without losing all of my data or having to do a full wipe?
Any help is appreciated. Thanks!
You wont need to do a full wipe, just download the ROM to your sd card, boot in to recovery and do a nandroid backup. Then select wipe cache. Once that has finished head to advanced and select wipe dalvik cache (some people say to do this some don't, I do) then flash the ROM.
You will only lose all your apps and setting if you select wipe data, you only need to do this if you are have serious issues that cant be fixed by any other means. Or if you changing to a completely different ROM.
And remember to do a nandroid before touching anything else in the recovery menu
That's it? Awesome! I know what I'll be doing tonight.
Or you can just do it from rom manager and not check the wipe data. I swear some of you just like taking the long way.
Always do a nandroid?No. Nandroid your original rom? YES. Nandroid custom rom? Only if you like it..but to do a nandroid every single time you flash new rom is ****
Sent from my Vision using XDA Premium App
Spastic909 said:
Or you can just do it from rom manager and not check the wipe data. I swear some of you just like taking the long way.
Always do a nandroid?No. Nandroid your original rom? YES. Nandroid custom rom? Only if you like it..but to do a nandroid every single time you flash new rom is ****
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
ROM Manager can some time cause issues when you flash directly from the app, Some people prefer to do it manually. Ok it might not be totally necessary to wipe the cache's between flashes but does really hurt?
And I resent you saying that doing a nandroid is "F'in Retarded" how frequently do we see people on these forums who have flashed something there not supposed and there most recent backup was weeks ago. It never hurts to do a nandroid it adds 5 minutes to the total time it takes flash something.
As some one who does do a nandroid every time I take your insult personally. And that sort of language is not appropriate in a forum where people of all ages can view.
LOL i don't even have a nandroid of my original ROM. I just got 1 image of RC4...
So I wanted to be 'better off safe than sorry', and I did a nandroid backup (using the latest CWM) before doing a CM7 RC3 -> CM7 Final non-full data wipe upgrade. I had a bunch of problems from the get go, and wanted to revert back to my RC3 backup as I didn't have time to fiddle with everything to get it tweaked from scratch...
However I can't for the life of me get Clockwork to recover my backup. It stops half way through and I'm left sitting at the main orange menu with no confirmation or details on what happened.
Any thoughts?
cjward23 said:
Glad its not just be with this mentality. Better to be safe than sorry. I haven't had to start from scratch since the first nightly, because I all ways have a recent nandroid, some times things do go wrong.
Click to expand...
Click to collapse
I did the backup (2 actually) and just installed the update. Everything seems totally fine so far and I'm really happy with it! Seriously stepping up to cm7 has made my G2 go from a decent phone with a nice keyboard to a flipping fantastic phone!
Many thanks!
raitchison said:
Your definition of *** seems to be basically the opposite of mine. What if an update breaks something (especially if you are cutting corners by not wiping or by using ROM manager) if you don't have a nandroid of your phone before you flashed that update you are screwed, you will need to start over from scratch.
Click to expand...
Click to collapse
Yeah, I agree with you completely. Doing a nandroid takes 5 minutes. Then later you can just move it to your desktop computer, to not take up space on your SD card. I have 3 TB of storage on my desktop, so no worries about saving as many nandroid backups as I feel like.
I've seen random issues pop up on my phone for no obvious reason, with no clear fix. But reverting to a nandroid cleared it up.
Really no reason NOT to do it.
hi everyone. ok here's my problem, yesterday i installed acs ics 5.5 rom, then i nandroid restored the ei22 deodexed stock just to test the nandroid restore, just to see if it worked for me. i then again flashed back to the ics 5.5 rom, and this morning i nandroid back to ei22 again, because i wasn't happy of the non - 4g function.
anyways, later on today i decided to go into "my files" and delete 3 of the 4 nandroid backups that i had. because i believe the 3 that i deleted were bad. well after i did that, i started getting apps force closes, and now i can't open gtalk or my text message app.
if i do a factory reset, should that fix the problem? before i turn to odin and perform the whole process all over again?
NOTE - everytime i did the restores and flashes, i did do a pre-rom wipe with acs recovery.
androidmaster1 said:
hi everyone. ok here's my problem, yesterday i installed acs ics 5.5 rom, then i nandroid restored the ei22 deodexed stock just to test the nandroid restore, just to see if it worked for me. i then again flashed back to the ics 5.5 rom, and this morning i nandroid back to ei22 again, because i wasn't happy of the non - 4g function.
anyways, later on today i decided to go into "my files" and delete 3 of the 4 nandroid backups that i had. because i believe the 3 that i deleted were bad. well after i did that, i started getting apps force closes, and now i can't open gtalk or my text message app.
if i do a factory reset, should that fix the problem? before i turn to odin and perform the whole process all over again?
NOTE - everytime i did the restores and flashes, i did do a pre-rom wipe with acs recovery.
Click to expand...
Click to collapse
Someeone just posted a similiar issue they associated with the8ir sd card.
They said after nand bkp they had fc's and no apps on sd showed. Wiping cache and dalvik would be pre factory default wipe imho.
Sent from my SPH-D700 using XDA App
Yes, a Factory data reset will clear the FCs. But you will lose 3rd party apps and anything you have set up will have to be set up again. If you have a nandroid you can trust you can do an advanced restore data to get those things back.
Sent from my SPH-D700 using XDA App
so does that mean that i have to go into recovery and repartition the sd card?
update - heres what it says on bootup - UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
WHAT DOES THAT MEAN?
androidmaster1 said:
update - heres what it says on bootup - UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable.
WHAT DOES THAT MEAN?
Click to expand...
Click to collapse
No idea but sounds like you need to do a factory reste
sent from a phone using an app
Djinn23 said:
No idea but sounds like you need to do a factory reste
sent from a phone using an app
Click to expand...
Click to collapse
None of that will touch your sd card. And you don't need to. The errors are in phone memory.
kennyglass123 said:
None of that will touch your sd card. And you don't need to. The errors are in phone memory.
Click to expand...
Click to collapse
+1
sent from a phone using an app
ok, here is the update to what's happened. last night i odin back to ec05 and redid the process again for updating and rooting, and now everything works ok.
i don't know what happened, but it was so bad, that i couldn't even use my phones dialer to make a call. but the problem is fixed. THANKYOU EVERYONE, for your help, i really appreciate it.
androidmaster1 said:
ok, here is the update to what's happened. last night i odin back to ec05 and redid the process again for updating and rooting, and now everything works ok.
i don't know what happened, but it was so bad, that i couldn't even use my phones dialer to make a call. but the problem is fixed. THANKYOU EVERYONE, for your help, i really appreciate it.
Click to expand...
Click to collapse
Awesome good work. Just out of curriosity...did you try the reccomendations here? What were the results?
Glad u got it up and thanks for the update.
sent from a phone using an app
yes i did. i did a factory reset and wiped the cache partition and dalvik cache, and still nothing. somehow after i deleted the 3 nandroid backups, things got messed up. i kept getting errors of framework and gapps process issues. i don't know what could have caused it, but it wasn't pretty. at least i was able to get it fixed with odin.
question regarding this type of issue though, if i would have checked marked re-partion along with the reboot, what would happen? cuz i was really tempted to do so, but i didn't, given the fact that i didn't know exactly what would happen.
If you check repartition you need to include the PIT file which is the map of the partition for our phone. That will put your phones partition back to what it was when new.
ok, and where can i find the pit file? sorry again for the dumb question, but this is the part that is very new to me.
androidmaster1 said:
ok, and where can i find the pit file? sorry again for the dumb question, but this is the part that is very new to me.
Click to expand...
Click to collapse
No problem, we are here to help. The PIT file should be packaged with Odin so when you unpacked it into a directory it should be there. Victoryxxxxx.PIT
ohh yea, i have that file. so that's what that file is for. ever since i got odin and started using it, i've bee wondering what that file was for. ok, so, in what type of circumstances can i use that file? like what happened to my phone yesterday? or what?
just so i have an idea of when i should use it.
When in doubt you can always use the PIT and repartition. F.reset resets all the clocks in the phone so there is no need to fear if you accidentally leave that checked.
I'm having the same issues here. Once I flash a rom, after a week or two I get this FCs but I notice this usually happens when I swap batteries or restart my phone. Once I flash a new rom or same rom everything works just fine until I have to swap or restart my phone.
What's causing this? Mine friend epic is having the same issue and he is getting tired of the phone to the point of putting it for sale. Is there a way to fix this?
Sent from my SPH-D700 using XDA App
lepapirriky said:
I'm having the same issues here. Once I flash a rom, after a week or two I get this FCs but I notice this usually happens when I swap batteries or restart my phone. Once I flash a new rom or same rom everything works just fine until I have to swap or restart my phone.
What's causing this? Mine friend epic is having the same issue and he is getting tired of the phone to the point of putting it for sale. Is there a way to fix this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You are not shutting down correctly causing bad data writes to your phone. Turn power off, after the vibration make sure keyboard lights are off before you pull battery. Also make sure you have journaling enabled.
Sent from my SPH-D700 using XDA App
I have used marcusant and sleeper rom at the moment, and they usually shut downs completely with the screen, but yes I make sure the light on the kb are shut. I don't know much about journaling, I guess I have to read about it.
Sent from my SPH-D700 using XDA App
lepapirriky said:
I have used marcusant and sleeper rom at the moment, and they usually shut downs completely with the screen, but yes I make sure the light on the kb are shut. I don't know much about journaling, I guess I have to read about it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Then it is strange that swapping batteries would cause any kind of data corruption. I believe those ROMs have journaling on by default. FCs are usually easy to fix. Most times it is a Google Services Framework error. This can be fixed using Titanium Backup and scrolling to Google Framework Services, select it and choose wipe data. Do that for any other app that FCs as well.
Sent from my SPH-D700 using XDA App
Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..
crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens
Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!
lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.
Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related
Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.
Alright will do as suggested
How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far
So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.
I made a noob mistake... I had a rooted Samsung Galaxy S3 SPH-L710 with the auto brightess being to dim for me. I jumped the gun and installed the "auto brightness" fix for the i9300 without thoroughly researching and finding that it wasn't for my model - DUH! :crying:
My phone will not boot now. I can get into CWM but cannot restore to a backup because apparently it didn't complete correctly and I get a MD5 mismatch error. No backup, no boot, no joy. <more tears>
My plan of action is to download and install the stock ROM using Odin 3.07, then re-root, and reinstall my apps with Titanium Backup. (Then take a new backup that I'll TEST before making any further changes!! )
Does this sound like the appropriate course of action?
Does anyone have a link to download the stock firmware fast? The samsung-updates-com stock ROM for the SPH-L710 is so slow it timed out on me already.
Thanks.
And yes I know I'm an idiot...
ninjadave007 said:
I made a noob mistake... I had a rooted Samsung Galaxy S3 SPH-L710 with the auto brightess being to dim for me. I jumped the gun and installed the "auto brightness" fix for the i9300 without thoroughly researching and finding that it wasn't for my model - DUH! :crying:
My phone will not boot now. I can get into CWM but cannot restore to a backup because apparently it didn't complete correctly and I get a MD5 mismatch error. No backup, no boot, no joy. <more tears>
My plan of action is to download and install the stock ROM using Odin 3.07, then re-root, and reinstall my apps with Titanium Backup. (Then take a new backup that I'll TEST before making any further changes!! )
Does this sound like the appropriate course of action?
Does anyone have a link to download the stock firmware fast? The samsung-updates-com stock ROM for the SPH-L710 is so slow it timed out on me already.
Thanks.
And yes I know I'm an idiot...
Click to expand...
Click to collapse
Best course of action back to stock :::: http://forum.xda-developers.com/showthread.php?t=1904099
I assume you know how to use Odin so here's the file as posted by Skunk Ape1. All credit goes to him.
http://d-h.st/GVs
Thank you!
Also, you can connect your sdcard to your computer through recovery...then just put any rom on there (doesnt have to be stock) and flash it (full wipe), because it seems as though you've corrupted the /system partition in some way since the the phone starts up at all
No need to go back to stock necessarily
Also, I would suggest that you make a backup of your phone as is now...that way when it get it functioning again you can manually restore your apps and data and any tweaks you mightve had in your build.prop or init.d
Sent from my PG06100
Why don't you just put into the recovery and wipe your system and just reinstall the rom. All your data will remain.
Anthraxed MA4
CNexus said:
Also, you can connect your sdcard to your computer through recovery...then just put any rom on there (doesnt have to be stock) and flash it (full wipe), because it seems as though you've corrupted the /system partition in some way since the the phone starts up at all
No need to go back to stock necessarily
Also, I would suggest that you make a backup of your phone as is now...that way when it get it functioning again you can manually restore your apps and data and any tweaks you mightve had in your build.prop or init.d
Sent from my PG06100
Click to expand...
Click to collapse
As you see:
My plan of action is to download and install the stock ROM using Odin 3.07, then re-root, and reinstall my apps with Titanium Backup. (Then take a new backup that I'll TEST before making any further changes!!
So I suggested the closest thing to what he/she was looking for...problem solved long ago, again theres this troll rambling off more gibberish
No need for your input necessarily
take a hike, dont worry bout me/my/my posts and buy a real phone...
SGSIIIJB said:
So I suggested the closest thing to what he/she was looking for...problem solved long ago, again theres this troll rambling off more gibberish
No need for your input necessarily
take a hike, dont worry bout me/my/my posts and buy a real phone...
Click to expand...
Click to collapse
That was a little unnecessary, there's no need to be a jerk when someone else suggests something.
metalfan78 said:
That was a little unnecessary, there's no need to be a jerk when someone else suggests something.
Click to expand...
Click to collapse
no all help is great! from everyone!!! except that person (lil history there)
SGSIIIJB said:
no all help is great! from everyone!!! except that person (lil history there)
Click to expand...
Click to collapse
Which one?
Transmitted with a portable device using Xparent Blue Tapatalk 2
SGSIIIJB said:
no all help is great! from everyone!!! except that person (lil history there)
Click to expand...
Click to collapse
History? Really now, you would think that people would be more mature when others offer alternative advice, even if it may differ from your own
Note that I never said your answer was wrong, I was simply offering another solution and I believe its up to the OP to decide which is better, not you or me.
Sent from my PG06100
I'm glad I did a search because I would have hated starting a new forum for nothing. I'm having the exact same issues with my GS3. I flashed a 4.4 kit kat rom and after that now I can't restore my stock 4.1.2 ROM, or flashed any others. I get the same MD5 mismatch when trying to restore the old rom. I went back into to ODIN and tried bringing back to stock but and it does is reinstall the stock recovery and give me a whole list of "FAILED" messages. I like the 4.4 ROM but I want out and I can't figure out how. Do you guys have any idea what I can do?
---------- Post added at 03:23 PM ---------- Previous post was at 03:12 PM ----------
CNexus said:
Also, you can connect your sdcard to your computer through recovery...then just put any rom on there (doesnt have to be stock) and flash it (full wipe), because it seems as though you've corrupted the /system partition in some way since the the phone starts up at all
No need to go back to stock necessarily
Also, I would suggest that you make a backup of your phone as is now...that way when it get it functioning again you can manually restore your apps and data and any tweaks you mightve had in your build.prop or init.d
Sent from my PG06100
Click to expand...
Click to collapse
@CNexus, I tried this as well. I actually tried installing your stock rooted 4.3 rom and it just get's stuck on the splash screen. Any advice?
Try again but perform a full wipe (data, internal storage [if nothing important is there], cache, dalvik cache, and system)
No go. I'm going nuts over here. I know I'm a noob this is probably annoying but I want to thank you for your help. So I tried restoring after doing a full wipe and still get the "md5 mismatch". Then I wiped again and trued installing 4.3 and it stayed on the splash screen for over 20 minutes. Aside from flashing a stock tar file on odin, is there another method to fully restoring the phone to stock?
Sent from my SPH-L710 using xda app-developers app
http://forum.xda-developers.com/showpost.php?p=48637859&postcount=1223
FYI:
http://forum.xda-developers.com/show...php?p=48620997
Latest CWM won't let you flash anything other that KitKat (4.4.x) ROMs per this post...
Sent from my SPH-L710 using Tapatalk
Got this tip from pitcherj, it solved everything. I'M BACK BABY!!!!:laugh::good:
Hey guys, I've been having this issue for a while now, but I've been deathly busy the last couple months so I haven't posted about it!
My issue is this: I've been having issues with the phone randomly freezing which results in the phone soft-resetting itself. I also have issues with apps randomly crashing. Occasionally, I will turn off the screen and when I try to turn it back on, it won't work and the phone will soft-reset. Another interesting thing I've noticed is that when I'm listening to music (stored on the SD card), sometimes I'll get distorted sound for a while. Usually, it fixes itself, but occasionally this leads to the phone soft-resetting. In general, since these symptoms started showing up, I've been dealing with stuttering and lag on my phone
Is there a possibility that my microSD card went bad? (could that even cause this kind of problem?) My card is kind of old, but I don't have any spare microSD cards to test
I'm currently using STS Rom on MK4, but this problem happened before I flashed that ROM. Before that, I was using Whompasaurus 4.2 (MA7)
Please let me know if you need me to do something to my phone!
Thanks in advance! I appreciate it
chronostorm said:
Hey guys, I've been having this issue for a while now, but I've been deathly busy the last couple months so I haven't posted about it!
My issue is this: I've been having issues with the phone randomly freezing which results in the phone soft-resetting itself. I also have issues with apps randomly crashing. Occasionally, I will turn off the screen and when I try to turn it back on, it won't work and the phone will soft-reset. Another interesting thing I've noticed is that when I'm listening to music (stored on the SD card), sometimes I'll get distorted sound for a while. Usually, it fixes itself, but occasionally this leads to the phone soft-resetting. In general, since these symptoms started showing up, I've been dealing with stuttering and lag on my phone
Is there a possibility that my microSD card went bad? (could that even cause this kind of problem?) My card is kind of old, but I don't have any spare microSD cards to test
I'm currently using STS Rom on MK4, but this problem happened before I flashed that ROM. Before that, I was using Whompasaurus 4.2 (MA7)
Please let me know if you need me to do something to my phone!
Thanks in advance! I appreciate it
Click to expand...
Click to collapse
I have the same problem. A d about your quesrion if the sdcard can be causing this freezing. The answer is yes. Try formatting both Internal and external memory. Put all your data to your comp and then format and see if that work's. I havent done it because my comp wont turn on :/.
Hopefully it helps
coolwater22 said:
I have the same problem. A d about your quesrion if the sdcard can be causing this freezing. The answer is yes. Try formatting both Internal and external memory. Put all your data to your comp and then format and see if that work's. I havent done it because my comp wont turn on :/.
Hopefully it helps
Click to expand...
Click to collapse
Thanks for the reply!
I'm relieved that I'm not alone, but sorry to hear you're having the same issues. It's not fun at all
I've reformatted the memory before, but I'll try it again. I'll let you know how it goes!
chronostorm said:
Thanks for the reply!
I'm relieved that I'm not alone, but sorry to hear you're having the same issues. It's not fun at all
I've reformatted the memory before, but I'll try it again. I'll let you know how it goes!
Click to expand...
Click to collapse
Yes it sucks. It is what it is :/. Alright sounds good!!
so, a quick update. Unfortunately, after wiping everything, I'm still having issues, but it doesn't seem as bad. It might be a wonky flash though, so when I get some more time next week, I'll try flashing again.
I do have to get a new SD card for sure though. When I use that SD versus a backup one that I have, I get more crashes.
I had the same issues. Noticed it was happening whenever my signal was low - Wifi or mobile radios. It would just freeze for minutes at a time or soft reset. I couldn't get anything done! I ended up flashing different custom recoveries and wiping partitions and formatting system, data, cache, all storage, carrier and efs (after backups of course) I flashed the StockMC2 zip with flash counter reset and it seems my problem worked itself out. I thought it was a hardware issue for sure, but that seemed to get it working again. Even fixed my laggy home key issue.
I recommend being extremely-and-dangerously careful if you find you want to venture towards the efs or carrier partition meddling. Read up to the fullest and make sure you use backups.
Sent from my SPH-L900 using XDA Premium 4 mobile app
ArchangelRenzoku said:
I had the same issues. Noticed it was happening whenever my signal was low - Wifi or mobile radios. It would just freeze for minutes at a time or soft reset. I couldn't get anything done! I ended up flashing different custom recoveries and wiping partitions and formatting system, data, cache, all storage, carrier and efs (after backups of course) I flashed the StockMC2 zip with flash counter reset and it seems my problem worked itself out. I thought it was a hardware issue for sure, but that seemed to get it working again. Even fixed my laggy home key issue.
I recommend being extremely-and-dangerously careful if you find you want to venture towards the efs or carrier partition meddling. Read up to the fullest and make sure you use backups.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the tip! I'll try it sometime and report back
To isolate the SD card issue try storing all your files to the internal and see how that goes first? If the problems persist then it could be the card?
When I ran Whomp it was very smooth, fast and stable (on multiple Note 2's). Could be a bad download? After clearing up the card issue I would recommend odin back to stock and start fresh again to see if the issues get fixed.
flynhawn2002 said:
To isolate the SD card issue try storing all your files to the internal and see how that goes first? If the problems persist then it could be the card?
When I ran Whomp it was very smooth, fast and stable (on multiple Note 2's). Could be a bad download? After clearing up the card issue I would recommend odin back to stock and start fresh again to see if the issues get fixed.
Click to expand...
Click to collapse
Thanks for the reply,
I tried switching SD cards and I still had the issue, so I figure it's not the SD card. I had Whomp before, but I've tried a few different ROMs since then and I've had the issue with every rom, unfortunately
Have you tried ODIN back to a stock firmware and re-root? Since I flash a lot of roms too I normally (as a habbit) flash back to a completely stock firmware just to get misc files/junk/bugs/slowness if any, off my phone and this normally helps with whatever issue I was running in to. Hope this helps?
Sorry for the late response. Just a couple days ago I ODIN'ed back to stock, but unfortunately, the problem is still there
Sent from my SPH-L900
Is it possible a logcat would help? If I remember right, it's difficult to grab a logcat for sudden and random restarts, right?
Regardless, taking a look at a logcat app, it seems I do get a decent number of errors. I'll look into this a bit more when I get some more time after my current set of exams
bumping my thread! Still no luck. Anybody have any additional ideas?
chronostorm said:
bumping my thread! Still no luck. Anybody have any additional ideas?
Click to expand...
Click to collapse
Give the Odin One-Click a try from @rwilco12 found here http://forum.xda-developers.com/showthread.php?t=2591898 this is MK4 or you can try here @rwilco12 forum found here http://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy Note II (SPH-L900)/Stock ROMs and pick and choose what version you want
Hoping this might help you
Sent from my SPH-L900 using xda premium
Harjan112 said:
Give the Odin One-Click a try from @rwilco12 found here http://forum.xda-developers.com/showthread.php?t=2591898 this is MK4 or you can try here @rwilco12 forum found here http://rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy Note II (SPH-L900)/Stock ROMs and pick and choose what version you want
Hoping this might help you
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I tried using your method! The phone has frozen once in the first hour I've been toying with it, but I don't know if it's the same issue. Hopefully it'll work! I'll report back after using my phone for a while
Soooooo interesting thing that I found out. My data folder isn't actually being wiped in all this! I went to check it out and it turns out some app files in /data/data/ are still there even after ODIN, full wipes, etc.
chronostorm said:
Soooooo interesting thing that I found out. My data folder isn't actually being wiped in all this! I went to check it out and it turns out some app files in /data/data/ are still there even after ODIN, full wipes, etc.
Click to expand...
Click to collapse
Not to doubt your intelligence but merely just to make sure, which one-click version did you end up getting, because there are two (2) versions ... full restore and NoData restore Rooted and unrooted, I believe MK4 hasn't have rooted version and only full restore.
Have you tried a factory reset after one-click that should wipe it.
I used the MC2 full restore unrooted without any problems.
Sent from my SPH-L900 using xda premium
Well, with the stuff that you linked, I used the MA7 full restore rooted. (Maybe I should try the MC2 full restore unrooted) But I've also ODIN'ed stock MC2 as well. I've wiped using factory reset from the settings menu as well as through Philz and TWRP making sure system and data were both selected. I wanted to avoid knox for now, so I used older versions.
chronostorm said:
Well, with the stuff that you linked, I used the MA7 full restore rooted. (Maybe I should try the MC2 full restore unrooted) But I've also ODIN'ed stock MC2 as well. I've wiped using factory reset from the settings menu as well as through Philz and TWRP making sure system and data were both selected. I wanted to avoid knox for now, so I used older versions.
Click to expand...
Click to collapse
Now come to think of it I might have actually done a format /system, format /cache, format /data and format /data and /data/media in philz under Mounts and Storage and rebooted into download mode and did the one-click MC2 Full Restore after that.
just make sure not to format the ext. SD card.
Give that a try.
Sent from my SPH-L900 using xda premium
Harjan112 said:
Now come to think of it I might have actually done a format /system, format /cache, format /data and format /data and /data/media in philz under Mounts and Storage and rebooted into download mode and did the one-click MC2 Full Restore after that.
just make sure not to format the ext. SD card.
Give that a try.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
That is the best way to go about this. Stick with the stock unrooted MC2 with flash count reset via Odin. You can then use The Note 2 ToolKit to root etc. I'm thinking if your bootloader was updated via the MK4 with Knox, you should try to downgrade it back to the MC2 version. toolkit allows you to flash the older bootloaders.
Do this:
FIRST flash Phil's recovery version 6.07.9.
Then wipe everything except external sdcard. Next flash the stock unrooted MC2 with flash count reset
http://forum.xda-developers.com/showthread.php?t=2086769
Once you complete that, immediately do a rom restore from settings and verify you are on the MC2 modem and kernel.
Then use the Note 2 toolkit from here: http://forum.xda-developers.com/showthread.php?t=1957155
At this point you need to flash the ALL IN ONE boot image, root &,recovery. I use the older version 2.0 of the ToolKit because it works best for my phone.
Once your rooted, etc. then reboot your phone into recovery and flash AGAIN Phil's recovery version 6.07.9
Then reboot recovery and once in Phil's recovery do all the wipes again and then flash the ROM of your choice.
You will also need to flash the correct modem for the ROM you flash. If you flash a JellyBean/MK4 ROM, you need to flash the MK4 modem. ROMS will have the kernel built in but if your flashing a TW ROM double check the kernel date and it doesn't hurt to reflash the stock MC2 or MK4 kernel because I have flashed a few stock TW ROMS that did not update the kernel so double check your kernel in settings-about phone.
This should get you back on track.