[GUIDE] Flashing ROMs correctly, every time - T-Mobile, Samsung Galaxy SIII

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!

Related

[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] codefireX problems

I have installed the rom of cfx_ace-4.2-BR11 & cfx_ace-4.2-SR1 and install all my apps, change my wallpaper and stuff, butt when I reboot my phone it resets to first installation (lose my wallpaper, my apps, and settings). Can someone help me with this? I really like this ROM.
I use a HTC Desire HD.
Did you a Fullwipe before flashing the ROM?
L3moon said:
Did you a Fullwipe before flashing the ROM?
Click to expand...
Click to collapse
Yes I did full wipe, dalvek & cache
Download again. Flash rom. Reboot. Wait a few minutes. Do your settings, reboot, flash gapps, reboot.
Technically, it doesn't really matter in what order you do it (I believe it so), some people swear by x or y method. In short, you should be able to flash the rom and gapps without needing to reboot in between and without loosing anything. It's odd that you are. After flashing both of those then download your apps, that is, if you use gapps.
Sent from a dream.
Tworan said:
Yes I did full wipe, dalvek & cache
Click to expand...
Click to collapse
Dalvik and cache is not a full wipe. A full wipe is system, data, and cache.
Yes i know, tried it still doesnt work. Installed another rom that One Works fine, going to try and reinstal the rom this weekend.
Sent from my HTC Desire HD using xda app-developers app
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
yauchildchew said:
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
Click to expand...
Click to collapse
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
@gregkneitas said:
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
Click to expand...
Click to collapse
Flash gapps. Linked in cfX OP.
I do have the gapps file downloaded. I just dont know how to get it on my phone and working. I used a ROM manager app for the ROM file.
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
bananagranola said:
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
Click to expand...
Click to collapse
Like I said, I didnt flash the ROM, I used a ROM manager app.I dont know how to get to the recovery screen. Could someone please help me out with a step by step. Keep in mind vol down + power doesnt put my phone into recovery
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
bananagranola said:
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
Click to expand...
Click to collapse
Figured it out, thanks!
Next question is I downloaded Gmail App, and it wont sync with my account. I login, and everything but it just sits at the screen saying "Waiting for sync, your email will appear shortly" I've waited well over 10mins and no sync. Ideas?
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
bananagranola said:
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
Click to expand...
Click to collapse
It appears I didnt. You solved the problem! Thanks a bunch. Sorry for all the questions.
Ok last question, will adobe flash player work with this ROM? If so how can I get it. I search the market and the app isnt there. And its not on my phone either
4.2 in general doesn't support flash. You could try searching for the apk and sideloading it. Make sure you enable installation from unknown sources in Settings - Security.
sashank said:
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
So, when fixing one thing, the process could probably break some working features.

Storage issues help

I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.
Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****
RADIO EDIT------
Sent from my PG86100 using xda app-developers app
edited and deleted for the sake of peace
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!
jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...
The fix you used is for samsung devices. That could have caused your problems.

[Q] What causes "Unfortunately, HtcDm has stopped" message?

This is on Verizon HTC one, dev unlocked, rooted and NOS 1.0.2 This message has been popping up lately, and more frequently. May I know what is the cause behind this? Any solution/fix?
TIA.
trust2me said:
This is on Verizon HTC one, dev unlocked, rooted and NOS 1.0.2 This message has been popping up lately, and more frequently. May I know what is the cause behind this? Any solution/fix?
TIA.
Click to expand...
Click to collapse
If you are using a custom ROM, I'd ask over in the respective thread. Mine is still stock (didn't get a chance to unlock day 1) and I have not seen this message.
EDIT: Or, perhaps try a full wipe - system/cache/dalvik/factory reset, etc...
peteschlabar said:
If you are using a custom ROM, I'd ask over in the respective thread. Mine is still stock (didn't get a chance to unlock day 1) and I have not seen this message.
EDIT: Or, perhaps try a full wipe - system/cache/dalvik/factory reset, etc...
Click to expand...
Click to collapse
Thank you for your informative response. I tried reboot, clear cache, factory reset, the message still pops up and am unable to determine the pattern. Tried to remove the SIM card and stay on wifi for a day. It appears at random times.
P.S. Being a new member to this forum, I don't have a privilege to post it in the development thread, so I thought this would be the most appropriate place. If I am the only one who is getting his message, then I must have done something wrong. Although, I have been using android since OG droid, apart from rooting, I never really got into customization. And when I saw this phone, it screamed to give it a little personal touch Anyway I will keep an eye on this post. And big thanks to all the developers and users here, I have started to learn a lot from these discussions.
trust2me said:
Thank you for your informative response. I tried reboot, clear cache, factory reset, the message still pops up and am unable to determine the pattern. Tried to remove the SIM card and stay on wifi for a day. It appears at random times.
P.S. Being a new member to this forum, I don't have a privilege to post it in the development thread, so I thought this would be the most appropriate place. If I am the only one who is getting his message, then I must have done something wrong. Although, I have been using android since OG droid, apart from rooting, I never really got into customization. And when I saw this phone, it screamed to give it a little personal touch Anyway I will keep an eye on this post. And big thanks to all the developers and users here, I have started to learn a lot from these discussions.
Click to expand...
Click to collapse
just do some random posts like welcome to the forums, and good for you!
to get the post count up, it's a joke and shouldn't even be needed.
Ask these questions in the respective ROM thread..
Newt will have a better chance of seeing it
Don't worry about posting in a developer thread, just post in the respective ROM thread. Also, I'm not sure what process you went through, but if you are having problems, it's usually a good idea to clear everything and start fresh with a new ROM, so be sure to clear all of these: data, cache, dalvik, system, and possibly even perform another data wipe after you install the custom ROM
Sent from my HTC6500LVW using xda app-developers app
peteschlabar said:
Don't worry about posting in a developer thread, just post in the respective ROM thread. Also, I'm not sure what process you went through, but if you are having problems, it's usually a good idea to clear everything and start fresh with a new ROM, so be sure to clear all of these: data, cache, dalvik, system, and possibly even perform another data wipe after you install the custom ROM
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Thank you for your response. Yes, as per your suggestion (and lessons learned from using OG Droid and Razr Maxx), after system backup, I religiously do clear cache, Dalvik, factory reset and then install/play with system settings (new ROMs in this case). One of the things I did is: when I listed the /system/app/ folder, I saw few .odex files without respective .apk files. So I mounted /system while in recovery and removed those stray .odexes. I thought I might have deleted some files that I should not. So I wiped everything and reinstalled the ROM. however, the issue is still there. Anyway, I will keep looking for the bug.
andybones said:
just do some random posts like welcome to the forums, and good for you!
to get the post count up, it's a joke and shouldn't even be needed.
Ask these questions in the respective ROM thread..
Newt will have a better chance of seeing it
Click to expand...
Click to collapse
Haha, you are awesome when I saw "You, new guy, you are not allowed to...." message this was the first thing that came in my mind. On a second thought, I realized, this must be the same reason (posting random/irrelevant) posts is why these restrictions exist. Also, you guys are doing amazing job of helping users like me to not only understand and learn about hardware and software issues, but resolving all the amateur mistakes that we make. So I am trying to keep the posts as relevant as possible.
As per the error message, it looks like some HTC app is trying to download data and unable to retrieve proper information. If I can figure out which app is throwing this message, it might help to find what information/app is trying to get access to and then resolve that problem.
BTW, thanks for BoneStock ROM. Am super excited to see that ROM getting Aroma-tized.

[Q] Gremlin cleaner?

I searched for something like this, but couldnt find anything. Ive been flashing between different Roms since I got my phone, and wanted tosee if there was something that I could flash to wipe away all the gremlins from previous Roms. I still do a clean flash and wipe dalvik, cache, and factory reset. But ive been noticing little issues here and there.
itsLYNDZ said:
I searched for something like this, but couldnt find anything. Ive been flashing between different Roms since I got my phone, and wanted tosee if there was something that I could flash to wipe away all the gremlins from previous Roms. I still do a clean flash and wipe dalvik, cache, and factory reset. But ive been noticing little issues here and there.
Click to expand...
Click to collapse
Well There isn't one as such. Typically what I do is.
1. Factory Reset
2. Wipe Dalvik, Cache and sometimes /Data
3. Flash the Rom & Gapps.
4. Reboot Setup everything
5. Reboot Again to Recovery and then wipe Dalvik+Cache and then flash custom Kernel if I wanted.
I may skip Step 5 if I want to stick with Rom's own kernel. I know you went through this, I just wanted to specify the sequence. If you still have issues then post them on the new rom's thread.
Perseus71 said:
Well There isn't one as such. Typically what I do is.
1. Factory Reset
2. Wipe Dalvik, Cache and sometimes /Data
3. Flash the Rom & Gapps.
4. Reboot Setup everything
5. Reboot Again to Recovery and then wipe Dalvik+Cache and then flash custom Kernel if I wanted.
I may skip Step 5 if I want to stick with Rom's own kernel. I know you went through this, I just wanted to specify the sequence. If you still have issues then post them on the new rom's thread.
Click to expand...
Click to collapse
Thanks. I know on the SGS Blaze 4G someone developed a gremlin cleaner that you could flash along with wiping everything manually. Just wondered if there was one for the S3. Im using Goosh rom, but it looks like the developer dropped support.
itsLYNDZ said:
Thanks. I know on the SGS Blaze 4G someone developed a gremlin cleaner that you could flash along with wiping everything manually. Just wondered if there was one for the S3. Im using Goosh rom, but it looks like the developer dropped support.
Click to expand...
Click to collapse
Take a look at this thread. Hope it helps.
itsLYNDZ said:
I searched for something like this, but couldnt find anything. Ive been flashing between different Roms since I got my phone, and wanted tosee if there was something that I could flash to wipe away all the gremlins from previous Roms. I still do a clean flash and wipe dalvik, cache, and factory reset. But ive been noticing little issues here and there.
Click to expand...
Click to collapse
What little issues and on which ROMs? It matters.
Factory reset wipes data and cache. Dalvik cache is on the data partition, isn't it?
So factory reset, wipe system. Should be all you need to do.
Aerowinder said:
What little issues and on which ROMs? It matters.
Factory reset wipes data and cache. Dalvik cache is on the data partition, isn't it?
So factory reset, wipe system. Should be all you need to do.
Click to expand...
Click to collapse
Ive been reflashing Goosh rom, but after 2-3 months or so I have to reflash it because it slows down and starts to have issues. Havent installed or updated any apps. I dont have many and I know they can affect it. So thats when ive been doing. I really like the rom and get great battery life, but the dev has dropped support for it. Even to tell me to "use a different ROM" because he doesnt care. But each time I reflash it after a couple months, it doesnt seem to work as well as the very first flash from when I first got the phone. I feel like things are building up/not getting completely wiped.
itsLYNDZ said:
Ive been reflashing Goosh rom, but after 2-3 months or so I have to reflash it because it slows down and starts to have issues. Havent installed or updated any apps. I dont have many and I know they can affect it. So thats when ive been doing. I really like the rom and get great battery life, but the dev has dropped support for it. Even to tell me to "use a different ROM" because he doesnt care
Click to expand...
Click to collapse
Please try Auto Memory Manager on most aggressive setting. Check and see how things go. If you see FCs then dial back to medium.
On a side note, Better Battery life ? See these Screenshots for Battery life of other roms to compare/
itsLYNDZ said:
Ive been reflashing Goosh rom, but after 2-3 months or so I have to reflash it because it slows down and starts to have issues. Havent installed or updated any apps. I dont have many and I know they can affect it. So thats when ive been doing. I really like the rom and get great battery life, but the dev has dropped support for it. Even to tell me to "use a different ROM" because he doesnt care. But each time I reflash it after a couple months, it doesnt seem to work as well as the very first flash from when I first got the phone. I feel like things are building up/not getting completely wiped.
Click to expand...
Click to collapse
Unless you're completely wiping everything, including internal sd, then there will of course be lingering data. But consider doing a true factory reset, which formats /data. From a custom recovery, it doesn't format because it's preserving your internal sd data. You'll have to specifically choose Format Data from within the recovery.
Something else you can try is in Settings, Developer Options, at the bottom choose Limit Background processes and I would select 3 to start. If it doesn't help much go to 2 and test.
Sent from my SGH-T999 using Tapatalk
Perseus71 said:
Please try Auto Memory Manager on most aggressive setting. Check and see how things go. If you see FCs then dial back to medium.
On a side note, Better Battery life ? See these Screenshots for Battery life of other roms to compare/
Click to expand...
Click to collapse
I cant find the screen shots on that page :/ I would like to see a comparison of battery life between roms.
itsLYNDZ said:
I cant find the screen shots on that page :/ I would like to see a comparison of battery life between roms.
Click to expand...
Click to collapse
I had linked another post of mine here on XDA. Are you sure in the entire post you didn't see linked screenshots ?
There's one set near the top and bellow that there is "Hide Button" which hides my own set.
Here is a Direct Link and the other shot.
Perseus71 said:
I had linked another post of mine here on XDA. Are you sure in the entire post you didn't see linked screenshots ?
There's one set near the top and bellow that there is "Hide Button" which hides my own set.
Here is a Direct Link and the other shot.
Click to expand...
Click to collapse
No, but I did read how to use Greenify to control Google Service Framework from that thread... Didnt see any screenshots..
itsLYNDZ said:
No, but I did read how to use Greenify to control Google Service Framework from that thread... Didnt see any screenshots..
Click to expand...
Click to collapse
You probably clicked on a link in the post that took you to the GSF related Thread.
Also in my last post I linked 2 screenshots. Were they not accessible ?
Please visit This thread. You are interested in Post # 11.
Perseus71 said:
I had linked another post of mine here on XDA. Are you sure in the entire post you didn't see linked screenshots ?
There's one set near the top and bellow that there is "Hide Button" which hides my own set.
Here is a Direct Link and the other shot.
Click to expand...
Click to collapse
Can you tell me what Rom was being used in this screenshot that you linked to? I would like to stay with a TW rom.... Also, does it matter if I flash via TWRP or CWM? Im so used to CWM....

Categories

Resources