Related
does it matter if i flash my phones rom deleting the old one..
basicly...
If i change the rom 1x - 10,000x will the phone still run the same or does it eat up memory and force phone to lag
razr315 said:
I'm not sure exactly what you mean, but I will attempt to answer what I understood.
I would recommend a nandroid backup before flashing anything over the current rom. Especially stock.
I would also do a full wipe before flashing another rom.
Does this answer your question at all?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I asked..
Does it matter how many times you flash your phone if you wipe does it leave residual memory to eat up and lag your phone or does it not affect it at all
razr315 said:
Oh yeah, that's a good question. Id like to know that myself seeing as how I flash mine about 20 times a day...lol
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe it does when I went into recovery I clean not only the factory wipe but also the cache wipe but i'd be curious to know more
i have not ever noticed any issues with flashing multiple ROMs, as long as you are wiping then you should be fine and no residual issues will be found, if you choose not to wipe you will likely end up in a boot loop, or a "brick" as some call it, but those are fixable with a wipe and reflash. if someone wants to correct me then great something new i learned, but i flashed almost every ROM for the G1 and never had any issues so long as i wiped the phone
tubaking182 said:
i have not ever noticed any issues with flashing multiple ROMs, as long as you are wiping then you should be fine and no residual issues will be found, if you choose not to wipe you will likely end up in a boot loop, or a "brick" as some call it, but those are fixable with a wipe and reflash. if someone wants to correct me then great something new i learned, but i flashed almost every ROM for the G1 and never had any issues so long as i wiped the phone
Click to expand...
Click to collapse
the G1 might be a bit different then the Slide hence the question
but thankyou for your input
Probobly just cache I wipe everything just in case
Sent From My R..r..r..rooted MyTouchy Sliderz
Hi all,
I have HTC wildfire for almost a couple of years, recently it started to randomly restart, about 5-8 times a day (the phone is off during the night).
At the time it begun I had OLDWildPuzzleROM_2.2 Froyo v8.0.11 ROM, with HBoot 0.8.
Before the restarts happened I rooted my phone using unrEVOked-3-2-Windoze (it stayed S-Off though).
I don't think the restarts happened right after the root so I'm not sure that is the cause
I few days ago I flashed it with "RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed" which changed my HBoot from 0.8 to 1.01.0001. I found the ROM here and followed the instructions.
I had to make a goldcard (I formatted the SD card using the phone and not using the PC).
My phone continues to randomly restart.
We don't have HTC representative in my country, only non official labs that deal with repair, so I can't go to the company for repair. talking to the lab guy he says it is probably a software issue and not a hardware issue, though I don't understand how it is possible since I flashed a completely new ROM. Oh, and the lab guy says he will charge me whether the repair works of fails....
Do you have any suggestions?
Many thanks
PS
I read about boot loop, I'm not sure what boot loop is, but when my phone restarts it shows the HTC logo as it does during power on or full restart.
bootlooping is random restarting or continuous looping of boot.
reasons could be many......
overclocking your cpu to high.
low on memory (too many apps installed / running).
v6 / supercarger / juwwes ram scripts etc etc.
MokeeOs
So that doesn't apply to me
I don't overclock
I have restarts even without installing any apps
I don't know what v6 / supercarger / juwwes ram scripts mean
any ideas of what should I do?
slymobi said:
bootlooping is random restarting or continuous looping of boot.
reasons could be many......
overclocking your cpu to high.
low on memory (too many apps installed / running).
v6 / supercarger / juwwes ram scripts etc etc.
MokeeOs
Click to expand...
Click to collapse
Clonimus said:
So that doesn't apply to me
I don't overclock
I have restarts even without installing any apps
I don't know what v6 / supercarger / juwwes ram scripts mean
any ideas of what should I do?
Click to expand...
Click to collapse
like slymobi already mentioned it could have several reasons - but we've already excluded a few...
Another idea is to start your phone without the sdcard and look if the reboots continue
Important: flashing a different ROM to solve the issue almost doesn't help if you haven't done a complete wipe/factory reset - it has also been reported (not confirmed, though) that Clockworkmod recovery randomly fails with wiping - so it might also help to repeat the procedure.
Probably slymobi will point to a thread where he explains a complete wipe... (you could search in his threads - I'm busy and it's really hot here atm )
I mean: to be sure I always try to format + wipe + factory reset (sound redundant but feels safer...)
eventcom said:
like slymobi already mentioned it could have several reasons - but we've already excluded a few...
Another idea is to start your phone without the sdcard and look if the reboots continue
Important: flashing a different ROM to solve the issue almost doesn't help if you haven't done a complete wipe/factory reset - it has also been reported (not confirmed, though) that Clockworkmod recovery randomly fails with wiping - so it might also help to repeat the procedure.
Probably slymobi will point to a thread where he explains a complete wipe... (you could search in his threads - I'm busy and it's really hot here atm )
I mean: to be sure I always try to format + wipe + factory reset (sound redundant but feels safer...)
Click to expand...
Click to collapse
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Clonimus said:
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Click to expand...
Click to collapse
Sorry, couldn't find how to do a system format. can you help?
Does "wipe" as you call it the same as factory reset? if so that I did but no format.
In the recovery go under Mounts and Storage and select Format System.
Technically factory reset is a wipe, it wipes cache, data and sd-ext
Clonimus said:
thank you,
I will try to find a tutorial that illustrates how to do a format and complete wipe, I will appreciate it if someone will have the time to point one, but will look for it myself too.
so I understand you all think it is not a hardware issue.
BTW I did a factory reset on my original ROM before I flashed a new one.
Click to expand...
Click to collapse
There's another thing you might want to check: a lot of people had reboots when they (or the phone) switched on 3G. So do you have reboots, too, with data/3G off?
Furthermore I also know of at least one case where the reboots were caused by a damaged battery - so it might be a hardware issue as well - but in most cases I know of it hasn't been
Re. how to do a clean wipe/format: in this thread I describe my method (sometimes I'll do it different, though) and slymobi describes how he does it (your choice): http://forum.xda-developers.com/showthread.php?t=1833966
Lesicnik1 said:
In the recovery go under Mounts and Storage and select Format System.
Technically factory reset is a wipe, it wipes cache, data and sd-ext
Click to expand...
Click to collapse
yes but as you probably know, sometimes that might just not be clean enough...
reboot into recovery,power off then volume down button and power button at same time,in this menu,using trackball to select,
wipe data / restore factory settings,
wipe cache,
go into advanced and wipe dalvik cache.
press power button to go back.
go into mounts and storage,
format data,
format cache,
format system,
format sdext,
DONT FORMAT SDCARD
you have now wiped your phone clean.
press power button to go back,
install rom from sdcard,navigate to where your rom is on your sdcard and select / confirm,
let it install..........
don't reboot,if gapps are needed?
flash correct gapps in same way as you just flashed rom........
reboot.
MokeeOs
eventcom said:
There's another thing you might want to check: a lot of people had reboots when they (or the phone) switched on 3G. So do you have reboots, too, with data/3G off?
Furthermore I also know of at least one case where the reboots were caused by a damaged battery - so it might be a hardware issue as well - but in most cases I know of it hasn't been
Re. how to do a clean wipe/format: in this thread I describe my method (sometimes I'll do it different, though) and slymobi describes how he does it (your choice): http://forum.xda-developers.com/showthread.php?t=1833966
yes but as you probably know, sometimes that might just not be clean enough...
Click to expand...
Click to collapse
Thank you eventcom,
Actually I didn't think about it but the restarts started a bit after I started using the 3G internet.
If so will the format-wipe-flash procedure will help? this phone suppose to be 3G capable, no?
Many thanks
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
slymobi said:
reboot into recovery,power off then volume down button and power button at same time,in this menu,using trackball to select,
wipe data / restore factory settings,
wipe cache,
go into advanced and wipe dalvik cache.
press power button to go back.
go into mounts and storage,
format data,
format cache,
format system,
format sdext,
DONT FORMAT SDCARD
you have now wiped your phone clean.
press power button to go back,
install rom from sdcard,navigate to where your rom is on your sdcard and select / confirm,
let it install..........
don't reboot,
flash gapps in same way as you just flashed rom........
reboot.
MokeeOs
Click to expand...
Click to collapse
Thank you slymobi,
but as I wrote above, when I did the RUU thingy I had to do the goldcard procedure and so I formatted my SD card.
Does it have a ROM image after I did the RUU flash?
what is "flash gapps", is it one of the option in the menu? sorry, I'm new to all of this
thank you for your patience and valuable help
gapps is the google apps package.needed for most non sense roms I think
its fine that you have formatted the sdcard at that stage. I meant whenever your performing recovery wipes to be careful not to format sdcard as it does exactly what it says and you will delete all contents of sdcard.
MokeeOs
Lesicnik1 said:
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
Click to expand...
Click to collapse
can you flash just the radio?
Lesicnik1 said:
If the reboots happen because of you enabling 3G I think re-flashing the radio will fix that. (Not so sure on that, someone please complete me)
Click to expand...
Click to collapse
forgot about this.
yep I think you're correct,if it is the 3g? but what triggered it?
MokeeOs
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
Clonimus said:
can you flash just the radio?
Click to expand...
Click to collapse
lol I knew this was coming next.
yes you can. I'm busy now so hopefully someone will guide you.
if not search forum on how to flash radio etc etc.
MokeeOs
Yes you can.
First download the file I attached and this file: http://www.mediafire.com/?lkhsl6hojm7vplv
Put both on the SD card
Flash the first one in the recovery, this will give you a temporary 2.5.X recovery, that goes away on reboot.
Within that recovery flash the second file I put up (the radio file itself)
Lesicnik1 said:
Yes you can.
First download the file I attached and this file: http://www.mediafire.com/?lkhsl6hojm7vplv
Put both on the SD card
Flash the first one in the recovery, this will give you a temporary 2.5.X recovery, that goes away on reboot.
Within that recoveryond flash the sec file I put up (the radio file itself)
Click to expand...
Click to collapse
I feel so stupid asking this, but how do I 'flash the in the recovery'? I don't know the basics, also the 'Within that recovery and flash the sec file' is a bit esoteric for me
I feel stupid since I am an electronic engineer and working with J-Tag and embedded systems
Thank a lot
Flash them both, just like you flash a ROM
Once you flash the first file a new recovery will pop up, within that one, flash the radio file
Lesicnik1 said:
Flash them both, just like you flash a ROM
Once you flash the first file a new recovery will pop up, within that one, flash the radio file
Click to expand...
Click to collapse
That's my point exactly, I never flashed a ROM on a cell phone
I used the RUU exe, it was as simple as running a windows application.
Do I have to root the device? and mimic a ROM update procedure to do that?
Or wait, is it by using the bootloader menu that comes up when you press down+power on?
lesicnik I would have thought you of all people would give better instructions. Especially after yesterdays pm. lol.
MokeeOs
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!
hey, new user here, don't know if this has come up before but i did a search and haven't found anything that has the same particulars as i do.
recently my phone hasn't been responding to power button or home button wake up, intermittently. freezes up sometimes and some apps force close more than usual. then the other day, my phone died on me (full battery discharge) and when i finally got around to charging it, it charged fully but it wouldn't turn on past the Samsung boot logo, and gets real hot while doing so.
Also, the samsung boot logo appears before the AT&T splash screen tone starts.
im running stock Rooted 4.1.2 with the latest perseus kernel version.
any suggestions? i havent made a nandroid in a couple weeks, so my preferred route would be without a data wipe.
i can still access CWM recovery, btw.
well damn wheres the help?
I would download the stock rom and flash it again. If that doesnt work, custom rom time. I honestly cant see this problem getting fixed without a data wipe though good luck and keep me posted.
Sent from my X501_USA_Cricket using Tapatalk 2
With the non-response issues you describe, and the fact that you are seeing multiple force closes on the device....start with a wipe of the cache and dalvik cache in recovery.
It sounds as if the device is having cache file management issues, and trouble within the file structure.
While I dont think you have any hardware issues, it does sound like the software is suffering for one reason or another, and a base cleaning of the caches may help.
If no improvement is seen after cache cleaning, then we move to the data next.
I realize you want to keep your data intact, but if corruption has occured, you will have no choice but to factory restore the device and test again.
Try the cache cleaning first, then boot and test....
Beyond that...as the above poster states...a fresh install may be needed....g
Before a data wipe try reinstalling the kernel, and also try dirty flashing the Rom.
Not sure I would recommend a dirty flash to him. Plenty of times the result for users has been bad. Though as stated above yours, It does appear to be a file system error. He is probably right and I should have thought about wiping the dalvic cache first.
Sent from my X501_USA_Cricket using Tapatalk 2
i was afraid this would happen....
tried wiping both caches with no new results.
ive read that dirty flash has had mixed results. if i can at least get the OS booted so that i could backup what i need to, that would be a good thing.
im thinking its a kernel issue, since the phone gets real hot while stuck on the samsung screen. could i be right?
thanks guys:good:
i also tried reinstalling the kernel through cwm recovery, nothing new
FIXED
did a data/factory reset from recovery. it kept everything! thank god for cloud backups. Google is the JOINT!! i even kept my kernel and root, and at&t backed up my texts and calls....thanks everybody for the help, i really appreciate it!
its still kinna hot though...turned it off to let it cool down and see what happens when i start it back up....will keep posted if anything
Great. Know I didnt help too much but glad you got it worked out. :thumbup:
Sent from my X501_USA_Cricket using Tapatalk 2
DroidOblivion said:
did a data/factory reset from recovery.
Click to expand...
Click to collapse
Great news ....
Data corruption is so very easy to get.
As we mix and match pieces of code, those issues do arise.
Sadly, the causes are often elusive.
But the plan "B" wipe generally does the trick, as is the case here.
Happy flashing....g
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.