Develop Bugs

[Q] Noob to xda, not so noob to android, flashing, etc...but having a noob problem

Hey guys,
I don't know that I've ever used anything from the XDA forum before unless it was passed and linked on Android Central or SDX. I've been rooting and toying with crap (not developing, just following smart people's instructions and borrowing their hard work on my own devices) since I got started out with my Samsung Moment.
I'm onto an epic 4g now, and decided that I needed to play with a new rom/kernal. I had it rooted with one click root/recovery before. So I flashed to stock, updated to EC05 and got to town flashing Syndicate Frozen Version 1.1.0 - with Twilight Zone. I didn't see a single post other than praise so it got my vote.
I'm having a problem though. And I've tried all of the usual fixes. Reflashing, rebooting, etc. etc. And I cannot figure out what is causing this highly annoying FC. Force close on Google Services Framework process.com.google.process.gapps
Anyone have that, or have the solution to what keeps causing this?

i believe you need to wipe googles data, go to manage apps in settings, clear data on all google apps you have. see if that works!

Well, at this time it appears that, that may have been a very stupid question. I guess after wiping data, clearing cache's, etc. that never occured to me. we'll see how this goes now.

No, it's not a stupid question, also don't be shy in posting these type of questions in the specific roms devolopment thread, there are a ton of nice people that are willing to help and have a lot more knowledge than me!
Sent from my SPH-D700 using XDA Premium App

A lot of times, a simple 1) boot into CWM 2)wipe data, cache and dalvik cache 2x each 3) reflash rom 4) reboot will do the trick.

running_the_dream said:
A lot of times, a simple 1) boot into CWM 2)wipe data, cache and dalvik cache 2x each 3) reflash rom 4) reboot will do the trick.
Click to expand...
Click to collapse
Well put.
Sent from my SPH-P100 using XDA App

running_the_dream said:
A lot of times, a simple 1) boot into CWM 2)wipe data, cache and dalvik cache 2x each 3) reflash rom 4) reboot will do the trick.
Click to expand...
Click to collapse
I actually clear the cache/dalvik cache/ etc when flashing so I never thought of anything else needing to be cleared. Techargon hit it right on the head though. For whatever reason the google framework data had to be cleared, and it has worked perfect ever since. I'll definitely be sticking around here. This is quite a large community and I'm about 24 hours into absolutely loving my first ROM and Kernal from her.
Thanks guys!

jmiller0519 said:
I actually clear the cache/dalvik cache/ etc when flashing so I never thought of anything else needing to be cleared. Techargon hit it right on the head though. For whatever reason the google framework data had to be cleared, and it has worked perfect ever since. I'll definitely be sticking around here. This is quite a large community and I'm about 24 hours into absolutely loving my first ROM and Kernal from her.
Thanks guys!
Click to expand...
Click to collapse
Glad it worked! XDA is an awesome community, good to see you're sticking around! Also it's nice to click thanks on any posts that help you, i do it all the time

[GUIDE] Flashing ROMs correctly, every time

So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers

very nice and clear. thanks so much. I just flash LIquidsmooth rom. Very happy for a newbie like me:good:

Fantastic work.
This guide, albeit it simple, is very clear and concise.
Newbies (like myself) are able to follow these instructions to ensure that flashing ROMS always turn out smooth.
+1

Yeah I figured it will would be a useful guide. I'm just glad others feel the same. Beauty of open source - doing things because you like it and to benefit the community
Sent from garaxy

Great summary! Subscribed and will link to this thread when the next noob comes along and says, 'haaaaaalp!'.
Sent from my HTC Incredible 4G on Verizon's periodically blazing fast and mostly reliable 4G LTE network using xda-developers app

thx!

Cobraboy,
I have linked this thread to my signature, is that ok with you ?

saldebot said:
Cobraboy,
I have linked this thread to my signature, is that ok with you ?
Click to expand...
Click to collapse
Perfectly fine man
Sent from garaxy

I say just read the OP instruction

thanks but
cobraboy85 said:
Perfectly fine man
Sent from garaxy
Click to expand...
Click to collapse
I am going to update with links thanks. Your instructions are clear but I will add the links.
thanks again

Do i have to clean data and cache 3 times?

picture99 said:
Do i have to clean data and cache 3 times?
Click to expand...
Click to collapse
Personally, I say no. A few people aparently found it to sometimes be necessary on a previous phone and are just more comfortable continuing to do it that way. I never have wiped more than once, and never had any problems.
Its just what you're more comfortable with in the end. It shouldnt hurt anything, so its not a wrong way, just unnecessary imo.
Sent from my SGH-I747 using xda app-developers app

Thanks for this very useful information.

I would wipe, wipe dalvik, flash rom, flash gapps, reboot.
No problem here so far....any problem doing it this way?

how do you wipe system partition thru recovery? i don't see system partition when i load TWRP

th1nkm4d said:
how do you wipe system partition thru recovery? i don't see system partition when i load TWRP
Click to expand...
Click to collapse
It's just called System inside the Wipe menu.

thx for this crystal clear tutorial.

Are all contacts/text messages/ and phone logs deleted when wiping everything?

gyggyty said:
Are all contacts/text messages/ and phone logs deleted when wiping everything?
Click to expand...
Click to collapse
Only when data is scrubbed

cobraboy85 said:
Only when data is scrubbed
Click to expand...
Click to collapse
I followed these steps and worked for me. THANKS!

[GUIDE] Flashing ROMs correctly, every time

***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it. Also, I would recommend this be posted in the dev section as this is where people go to install ROMs, not the QA section. People go to QA after they have an issue. This is meant to be preventative, not a fix for an already broken device.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers

posting a link to youtube would be an awesome way to show us noobs how to Exactly go about it also..when i had my captivate i flashed a rom called cognition,super easy following the guy on the video

What about other ROM's?
Can you show us how to flash ROM's from another carrier such as AT&T? There are a couple of ROM's I am really interested in trying out but have no luck doing so because of me not knowing what the heck I'm doing or how to do it. If you could post instructions that would be really nice.

Since I'm already rooted I can't make a video on how to root but ill make a how to flash a rom once you're rooted for the note 2 if you guys are interested

Interesting!
Next time I flash a ROM, I will wipe thrice, as you say.
But do you know why it is important to wipe thrice? Does the extra two times really do something additional to scrub the disc?
I am truly interested, and I would like more insight on *why*
Also, the dev for the Jedi ROM suggests fixing permissions after the first boot.
In my experience, this has led to better performance on other devices in addition to the GNII - perhaps that is also worth mentioning.

techn0crat said:
Interesting!
Next time I flash a ROM, I will wipe thrice, as you say.
But do you know why it is important to wipe thrice? Does the extra two times really do something additional to scrub the disc?
I am truly interested, and I would like more insight on *why*
Also, the dev for the Jedi ROM suggests fixing permissions after the first boot.
In my experience, this has led to better performance on other devices in addition to the GNII - perhaps that is also worth mentioning.
Click to expand...
Click to collapse
There has been debates forever about the wiping more than once theory. I have always done this out of habit. You could compare it rinsing a dish in the sink that has some food on it... you wash it once really quick... you see nothing on the dish... you throw it in the cabinet. Later you see some small smudging on it and end up cleaning it again. Same idea. Just being thorough. As I said in the OP I have always done it this way simply to be thorough. And I have never once been the rogue user with an isolated issue.
To answer your q about permissions, if the ROM dev suggests that for his ROM, do it. It is not always required. But if instructed to do so, it should be done.

Is there a reason why it suggests to wipe three times?

I think it may go back to floppy disk days, or hard disks possibly leaving "footprints" on it, old images or data but im not sure. Just a theory.
G●Note~2 {Jedi X5}

Yes please add a section to the OP about flashing roms from other carriers. The steps are identical, except you flash a modem. We onky have the one availabke now so its very easy. Keep in mind n7100 roms will not work, and n7105 roms need minor porting. But you can take any rom from the us variants and flash it. Reboot, let it sit a bit, etc, flash modem. Its very easy and the att forum seems to be getting more love anyway
Sent from my SGH-T889 using Tapatalk 2

I don't promote people flashing ROMs that are not built for that specific device so I will not do it. Sorry.

krayzielilsmoki said:
Since I'm already rooted I can't make a video on how to root but ill make a how to flash a rom once you're rooted for the note 2 if you guys are interested
Click to expand...
Click to collapse
you could unroot and then do a step by step vid. this guy is so good at explaining it,for example,,http://www.youtube.com/watch?v=MsafJ-9uRqk yeah i know its for the captivate,but i didnt know anything at all about rooting and flashing . i just followed him and iwas a happy man after being stuck on eclair cause at$t was so slow to update,,,any how just an idea,seems like alot of work but i think it would kill off many questions,i know i ask enough now as it is..lol

cobraboy85 said:
I don't promote people flashing ROMs that are not built for that specific device so I will not do it. Sorry.
Click to expand...
Click to collapse
I have to agree with this. If you need flashing instructions, flashing ROMs meant for other devices is probably not the best idea at this point.
G●Note~2 {Jedi X5}

This is great advice about the MD5 verification. Everyone should check before flashing, it will ensure you have a good download with 100% confidence. If the MD5 doesn't match, don't flash it! And if a developer doesn't provide an MD5 with each download, ask them to.
However, wiping three times (or any other number of times except one) is nonsense. Would you format a USB thumb drive 3 times? An external hard drive? Android partitions are no different.
If it makes you feel better to wipe multiple times, go ahead, it won't hurt anything. You're just wasting time.

^kind of agree with you there. I would ask anybody here why they wipe dalvik cache when flashing a kernel then, considering the /data/dalvik-cache/ partition is nothing more than dex opted files of all your apks. I will also say that recently I have gotten in the habit of never wiping dalvik when flashing a kernel and it has not made a single difference in stability.
... point I am trying to make is what you said here, if it makes you feel better, do it lol. Doesn't hurt anything.

Indeed, cache wipes are seldom needed too. In fact, a lot of flashable .zip files have scripts which wipe the appropriate partitions automatically anyway when you install them. I guess old habits die hard...

I would also add that after flashing a ROM and you reboot that ROM, for use, you should wait at least 10 minutes before doing ANYTHING with your phone. That will allow the phone to fully and properly build cache and dalvik cache.. after a flash I let my phone just sit for 20min. Doing this has saved me from lags and bugs.

First I just wanted to say great job to the OP on creating this thread. I also strongly believe that this type of post really should be in the Development section, and you definitely nailed the reasoning for it. I've always considered writing up a thread like this myself, but I never got around to it unfortunately (<--Procrastinator ). There's just a few thing's I'd like to chime in with because I really believe they can help people who are new to the world of rooting. First and foremost (imo) I strongly believe that insecurity plays a huge role in determining whether or not you'll be successful with rooting and Android in general. I completely understand that statement can be applied to almost anything in life, but there's a very good reason why it's especially true when it comes to rooting. It simply boils down to people not wanting to feel (or look) stupid, and it seriously impacts the way a person handles different situations. My advice is to be comfortable with saying "I don't know what I'm doing" and "It's most likely not working correctly because I missed something or I didn't follow the directions exactly". I am not saying that to be ignorant or joking whatsoever, because if you have little to no experience when it comes to this stuff, it's nothing more than the hard truth. It doesn't make you stupid if you don't know how to fly a jumbo jet if you've never done it before, so why would it make you stupid for not knowing how to root a phone if you've never done it before? It doesn't and that's the entire point. If you try flashing a rom and it doesn't boot up or something isn't working correctly, 99.999998 percent of the time it's because you messed something up along the way. Especially when you see tons of posts in the thread like "awesome rom" or "it works great", because it's WAY more likely that you messed something up, versus you happening to have the one messed up phone out of thousands that are working perfectly. That's not saying you're stupid or incapable of doing it, again it's nothing more than the hard truth. It's also not impossible for that to happen either because it has, but it's few and far in between whereas making mistakes or forgetting something is a frequent occurrence for all of us. I can't tell you how many times I've seen people complaining about how something didn't work right, when the vast majority aren't having those issues (or just the known issues). Those types of posts are another example of what you should never do, because in reality you're blaming everybody else since you're apparently incapable of making mistakes. You'll be surprised how many times a problem you're having will turn out to be from forgetting something, even though you were absolutely positive you've done everything correctly. Anyway I really think that accepting the fact that you don't know what you're doing (yet), can make it WAY easier to learn in the long run. One last thing that I'd recommend especially if you're new to this whole rooting world, is to get in the habit of making nand backups (especially before you flash anything) because the 5 minutes it takes to do one can save you hours of frustration. Hope this helps somebody anyway

Paragraphs man. They make reading easier by separating thoughts.
I'm sure what you have to say is insightful but a megablock of text is tough to get through.
Don't sell yourself short by making your posts impossible to ponder.
Hastily spouted for your befuddlement

True in most cases but in our case every lte note two in the world regardless of carrier is identical. the only differences are minor software ones.
Sent from my SGH-T889 using Tapatalk 2

I also think wiping three times is a waste of time. These devices are digital not analog (the plate analogy is much more fitting in the analog world). A wipe is a wipe, doing it more than once seems like voodoo to me .

[Q] HELP! Galaxy S3 freezing and erasing stuff!

My Samsung Galaxy SIII from Sprint just freezes from time to time and I have to hold down the power button for 10 seconds to manually shut it down and boot it back up, sometimes whenever it boots up it has deleted all of my contacts and text messages. The phone also just reboots randomly, and during some of the times I turn the phone back on it says some applications have crashed, usually it was always Skype so I uninstalled it and it still crashes.
Can anyone help? I've tried unrooting, restoring, factory reset, flashing different roms, nothing changes!

bump
bump

I just said I have rooted and unrooted and the only way(that I know of) to do that is with Odin, anyway, yes, I've completely restored(as mentioned in original post) and I've used many different ROMS, like MOAR, Cyanogen, MIUI and a few others with the same results, I've used both CM and TWRP recoveries.

I know this is silly but sometimes it is as simple as going into recovery and wiping cache and dalvik.
Sent from my Wicked GS3

Well OK then @icytux. I apologize for trying to help. I come across many people who fail to do all of these things and 99% of the time it is "USER ERROR" I'm sure you wiped as you were flashing the roms what I was referring to is after the rom loads and your problems start. That's when you should go into recovery and wipe data and dalvik and maybe fix permissions. Also some people tend to think the are performing a full wipe and they are actually not. I use twrp and go to advanced wipe and select data, system, cache, and dalvik. I also do a recommended triple wipe and don't restore all of my apps with data through Tibu. People do this with system apps not knowing what they are doing and that is some things that cause some people's issues. I have no idea of your level of knowledge but what I do know is you seem to be rude to the people who are trying to help you out. I'm sure next time you have an issue and start a thread, myself and @Jessooca will probably not be trying to help you out since you basically just spit in Our face. HAVE A NICE DAY
Sent from my Wicked GS3

@mikeman45
Look, I'm sorry for sounding like an ass and insulting you if I did, I really didn't mean to come by that way but I did know to format , Data, System, Cache, Dalvik Cache three times or more before installing a new ROM or before flashing with ODIN, I've used different USB cables, re-downloaded files, ports and even different computers, the one thing I did not know from everything everyone here has said was fixing permissions, I'll try that, thanks.
PS.
The one thing I won't do is crack open my S3 as I don't know if that will negate the ability to trade the phone in to Sprint for a new one when the contract expires.

Thread cleaned of childish and off topic junk. Users are reminded that respect is a requirement for members here, that includes members who have titles attached to their accounts.
Be nice or get out. Next time, report offending posts and do not reply.

icytux said:
@mikeman45
Look, I'm sorry for sounding like an ass and insulting you if I did, I really didn't mean to come by that way but I did know to format , Data, System, Cache, Dalvik Cache three times or more before installing a new ROM or before flashing with ODIN, I've used different USB cables, re-downloaded files, ports and even different computers, the one thing I did not know from everything everyone here has said was fixing permissions, I'll try that, thanks.
PS.
The one thing I won't do is crack open my S3 as I don't know if that will negate the ability to trade the phone in to Sprint for a new one when the contract expires.
Click to expand...
Click to collapse
Mr. Icy, it does appear that you have taken the right steps to alleviate your issues... May I suggest reformatting your internal (phone) memory and either reformat your sd card, get a new one or take it out all together?? I know this sounds strange but it appears as if your memory isn't formatted correctly, possible has a virus, or may just be bad... If its bad and you have exhuasted all your resources here I would let sprint know and get a replacement... I had a bad S3 once (it was the port though)... Let us know and good luck! I really hope you get it fixed I know it can be VERY fustrating!

icytux said:
@mikeman45
Look, I'm sorry for sounding like an ass and insulting you if I did, I really didn't mean to come by that way but I did know to format , Data, System, Cache, Dalvik Cache three times or more before installing a new ROM or before flashing with ODIN, I've used different USB cables, re-downloaded files, ports and even different computers, the one thing I did not know from everything everyone here has said was fixing permissions, I'll try that, thanks.
Click to expand...
Click to collapse
It's OK I understand your frustration. I am a mechanic /electrician and work on half a million to 1 million dollar equipment everyday and when there is a problem I start off with the simple stuff and just keep eliminating things until I find the problem. That's all I was trying to do with my advice to you. Now since we know you went through all that simple stuff I would do like Vectus said and wipe your internal as well. Save the important stuff obviously so you can transfer it back to phone from your computer. I would also backup your sd card and reformat it. Then download the rom you want and make sure you have the matching firmware /modem /kernel ect .... That you will need. That would be my next step if I was you and if it all works good put the Stuff that you want /need back a few at a time so if it happens again it will be easier to pin point if you have a corrupted file somewhere. Keep us updated as we will try our best to continue to help.
Sent from my Wicked GS3

mikeman45 said:
It's OK I understand your frustration. I am a mechanic /electrician and work on half a million to 1 million dollar equipment everyday and when there is a problem I start off with the simple stuff and just keep eliminating things until I find the problem. That's all I was trying to do with my advice to you. Now since we know you went through all that simple stuff I would do like Vectus said and wipe your internal as well. Save the important stuff obviously so you can transfer it back to phone from your computer. I would also backup your sd card and reformat it. Then download the rom you want and make sure you have the matching firmware /modem /kernel ect .... That you will need. That would be my next step if I was you and if it all works good put the Stuff that you want /need back a few at a time so if it happens again it will be easier to pin point if you have a corrupted file somewhere. Keep us updated as we will try our best to continue to help.
Sent from my Wicked GS3
Click to expand...
Click to collapse
Thank you, I will be doing this tonight, I'll update the status in a day or two to see if it worked or not.

icytux said:
Thank you, I will be doing this tonight, I'll update the status in a day or two to see if it worked or not.
Click to expand...
Click to collapse
Any good news?
Sent from my Wicked GS3

Hey, sorry for the long wait, my ISP thought it would be funny to cease my internet connection even though I paid this month, anyway.
Sadly no luck, the phone continues to do random reboots, shut downs and such, thankfully contacts, text messages or apps haven't been deleted, so I guess that' one problem fixed.

bump

icytux said:
bump
Click to expand...
Click to collapse
bump

I know this is a long shot. But back in the day I had an OG EVO 4G with a bad factory battery. The battery was causing an intermittent short ( it was a manufacturing defect in the battery) . Thereby causing the voltage to fluctuate wildly, causing reboots. So with that in mind. Have you tried a different battery ? Just trying to eliminate possibilities.

Regardless of which ROM freshly installed I get "process com.google. etc..." errors

Regardless of which ROM freshly installed I get "process com.google. etc..." errors
Before I provide more details if needed I just wanted to check the first thing that I should which I'm clueless of. But so far its been a few ROM's. The latest were a couple stock ones and before that, the last time I was regularly using this phone a few years ago I believe it was an ASOP(did I get that right?) ROM. Are there a few common sources I can check for problems that might solve this? The messages seem to just pop up whenever and they are all different but usually start with process com.google then something else. Just need a point in the right direction as when I google these the only general solutions I found were to clean a variety of caches, apps and I've tried clearing dalvik and regular cache from TWRP but that never helped. So any ideas would be appreciated. Also for some reason can't install apk's. Play store works tho. I get that 'error parsing' error. Not sure if related.Trying to set this phone up as a backup phone.

Though I do not know the answer to your problems I would like to suggest you move your thread to Q&A or General because you will not get any answers in the section you posted in...A mod Might move it but if not you definitely should...Just word of advice that's all

majicmazo said:
Though I do not know the answer to your problems I would like to suggest you move your thread to Q&A or General because you will not get any answers in the section you posted in...A mod Might move it but if not you definitely should...Just word of advice that's all
Click to expand...
Click to collapse
Thanks. Actually its been solved. For the moment at least. I think for my latest reinstallation actually. Don't know why it ever gets these issues. I guess I'm afraid to accept that it could be hardware somehow which would be more difficult to solve than software. Well anyway, hopefully it stays this way