Related
This past week, I have tried both Myu Warm Treats for Android and Baked Snack roms. I have been using CyanogenMod ever since I rooted my phone, and I love it. I just wanted to try out a couple of other roms I kept hearing about. Anyways, everytime I flash a new rom, I keep getting these error messages saying that the "process-android-media" or something has encountered an error. I keep getting that and another error like it saying that the mms process has unexpectedly closed. This has happened on both of the roms I've tried and nothing I have tried will fix it. When I flash recovery back to Cyanogen, it's perfectly fine. What should I do?
The most likely problem is forgetting to wipe everything in recovery before flashing a new rom. Wipe userdata and cache and Dalvik cache. Then everything should work fine.
btw, it's really best if you put questions in the Q&A section. I fear a flame war will emerge from this thread.
How are you trying to flash the ROM? It should be done with Amon RA or Clockwork (or ROM Manager if you're using Clockwork), so no processes should be ending while you're flashing.
Also, this belongs in Q&A Forum, not Development.
Yeah, I just thought the ROM Manager would take care of wiping all the data and what-not. And sorry for not following whatever "protocols" you guys have for these types of things. It's maddening when you can't figure out a problem like this on your own. I just wanted to find some help as quickly as possible.
I have been having all sorts of problems with my phone, mainly from it running super low on storage space, even though I have moved virtually everything to the SD card that I can, and keep wiping the address book (which of course screws everything up). Some kind folks had helped me out a lot, but in the end suggested I just wipe it all and start over, but I was waiting to get a new SD card, which I finally have, and I just wanted to make sure I understand everything correctly before leaping in.
So I understand I need to format the SD card, and I was hoping someone could give me or point me to a guide to doing so. I understand I need to get A2SD, is that right? And so once I format it, I can just put everything on my old card onto the new one, yeah? And I understand I need to install Amon RA and get rid of Clockwork Mod, I get that. So then after I do all that, I should just flash a new ROM and not restore anything, and if things seem better, then I can batch restore apps, is that right? I think I just want to stick with the stock ROM, but is there a rooted version of the latest update available?
If someone would be so kind as to walk me through this one last time, keeping in mind I am pretty much a noob, that would be much appreciated.
Oh, I also would love to do the Firerat custom MTD partitions thing (http://forum.xda-developers.com/showthread.php?t=855424), tried to do it once before but screwed some things up, had to revert back to a previous backup, so figured now would be a good time to try that again, so if anyone can give me the rundown on that too, that would be super.
Thanks so much!
im gonna try and help you here, first back up everything you have on your sd card to your computer so you dont loose it when partitioning, then download a PCIMG36.zip of amon ra, put it on sd card and boot into bootloader and select yes when prompted, that will put amon ra as your recovery. now that you have amon ra and already backed up the stuff in your sd card to your computer go ahead and in recovery selcect partition sd card, its gonna ask you for a swap size( i use 0 but you can use 32 if you like, 0 works fine), then its going to ask for partition size for me 1024 is more than enough(1024 equals 1gb), once this is done, select upgrade ext2 to ext3. now your sd card is partitioned. you can go ahead and put all your stuff back into your sd card and flash the rom(for a2sd to work your rom has to have it built in, other wise you are going to have to flash it) if your rom has it built in it will automatically kick in. once your rom is flashed you can go ahead and restore apps, i would do them one by one, sometimes there are issues when doing batch, and also unless the app is really important i would only restore the app not its data, but i do restore app and data for important apps. if all goes well you should have a lot more free memory on your phone, you can check if apps are going to sd ext by opening titanium back up and at the bottom you should see sd a2sd or sd ext and next to it amount of free memory, if your phone internal is still low after all this and gets lower when installing apps you can fix it by going into terminal emulator and typing
su (hit enter)
a2sd reinstall (hit enter, this will move all apps to sd ext)
any more questions ust ask
With the new 2.1/3.0 hybrids, you're better off using larger partitions. I found swap 64 or 128 and EXT of 2048 works out better, if you have an 8gig or larger SD Card
Thanks so much for the quick responses! I am going to give this a shot later tonight, but another quick question.
I think I've got down how to partition it, thanks a lot for breaking that down for me. And I did just get a 32 GB SD card, so I'll go with the 128 swap and EXT of 2048, that's no big deal.
Now for what ROM to flash - I've just used the stock before, haven't flashed any other ROMs, but if I'm going this far, figure I might as well give it a try, why not. So what ROM would you recommend that has A2SD already built in?? If you could just give me a quick run down (or point me to somewhere where there is one, I'm sure it already exists) on how to go about flashing the ROM (I think I just download it though and install it through bootloader, is that right??), that would be super appreciated.
Thanks again!!
Roms are flashed through recovery and what Rom to use wow that will get you a lot of opinions.
Sent from my PG86100 using XDA App
man there are so many roms for so many tastes, but i would suggest Vaelpak 3.2 rc2 which is still a sense rom, but has a lot of customization options. to flash your fresh rom you need to put the rom on your sd card, then turn off phone, go into bootloader, go into recovery, select wipe, and wipe cache, dalvik cache and data, do each twice to make sure, then go back and select flash zip from sd card, scroll to the bottom and look for the rom, select it and reboot
Once again, thanks for the replies and the detailed explanation, much appreciated. Didn't get around to it last night, will do so tonight. I definitely understand there are a ton of ROMs out there, but am just looking for something pretty simple I guess, since all I've used is the stock so far. Vaelpak 3.2 rc2 sounds good, I'll give that a try. So just to make sure I understand, when I install this ROM, that's everything, right, so I don't need to worry about installing the latest Android software. Or do I still need to install the latest Gingerbread update (and if so, how do I go about doing that?) in addition to installing this ROM?
Sorry for the million questions, and thanks again!
VaelPak is a very extensive ROM. If you REALLY want to stay close to stock, but have the most updated, complete, streamlined, error free experience, go with Synergy or MikG.
I LOVE VaelPak, but there is a LOT of options, themeing, development, etc in there. It's definitely not for a beginner. Also, his newest release, which is based in GB is pretty awesome, but it's an AOSP Rom, which I'm not a fan of.
Hi all,
So this is really strange, I feel like I must just be missing something, but I finally pulled the trigger, did it all, flashed my first ROM (exciting!) and all seems to have gone smoothly, except that I cannot figure out how to access Titanium Backup?!? I thought it came with MikG (I decided to give that ROM a shot), but did not see it, so went to the Market and re-downloaded it, and it says downloaded, but I cannot click on "open" and it is nowhere to be found in the apps list, or anywhere for that matter. Help! What the heck is going on? Any thoughts?
Thanks much!
Did you have a notification saying "Titatium Backup Installed" or something like that? I've had the same problem in the Gingersense roms if I leave the market before the download AND installation is complete. Not every time but sometimes.
I was just being a little slow there, I had installed the key, but not the actual program. Oops So all good, got that working, but a couple quick more questions.
Sadly it seems that I did not have TB set to backup everything on a regular basis, looks like it was just set up to backup new apps and new versions (yikes!, I know). So I've been restoring some apps little by little, and when I restored Angry Birds I noticed I was stuck back on the first level and I was like, this isn't right, looked at the date, and last backup was like March/April. This is kind of a drag for some things, like that, and especially beyondPod, lost all my settings and a number of feeds there, but I think it's probably just something I'm going to have to live with, right? I of course made a nandroid right before I wiped and flashed, but it seems like even more of a hassle to go back to that nandroid, backup things to Titanium, then reflash MikG and restore everything again, rather than just recreating what I've lost, right? Just wanted to make sure I wasn't missing something, there's no other way around this.
Thanks for any assistance.
Let me start by saying I'm new to posting on these forums. I've been flashing roms now for over 7 months and have enjoyed it immensely.
The other day I ran into a problem that I've never had before. I was running Nil's 3.5 rom which is a great rom, and installed the V6 Supercharger Script (also great) to see how it would work with the rom. I installed everything, had V6 working and was prompted by V6 to change I believe it was /data and /cache files. I thought ok there shouldn't be a problem. So I ran V6 and everything seemed to run with no problems. Then things got a bit laggy so I decided lets try and uninstall V6 and see if that helps. V6 restored my settings that were backed up, and I uninstalled V6. I decided at this point to do a complete wipe and reflash the rom. This is when I encountered my problem.
I reboot the phone into recovery mode: (Using the lastest clockworkmod recovery)
wipe data factory reset
wipe cache partition
I go under mounts and storage, format
/boot
/system
/datadata
/data
/cache
I get an error stating "error formatting /data" and "error formatting /cache".
I am unable to restore any backups that I had already made because I receive this error message. When I install a new rom, I receive bootloops. The only rom that works, is Nils 3.5 rom that is still stuck on the phone, and when that loads, nothing works properly. I cannot download apps, the apps already installed force close on me.
I have no clue on what to do. Now I am asking myself, did I brick my phone? Any help, suggestions would greatly be appreciated.
Thanks
Update:
I decided to try downgrading to the official 2.2 stock version with S-On with hopes of trying to start from scratch and now I am stuck in bootloops. The phone goes to the red eye, pauses for about 20 seconds and reboots. Any suggestions on what to do now?
Just had this issue on my wife's phone. System random rebooted after an app update and now /cache and /data won't format. Nothing posts past the white Incredible screen.
Came up with some solutions that I have yet to try, but here's what I found:
http://forum.cyanogenmod.com/topic/32272-error-formatting-data-when-restoring/
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20
http://forum.cyanogenmod.com/topic/18288-error-formating-cache-wont-boot-past-htc-screen/
Looks like basically we need to force fix the file system and push something initial onto the phone though adb.
I'll keep this tab open and post my results as I try some fixes tonight on my wife's phone.
Bad news for you guys. I had this happen a month ago and could not fix it. Someone over at the CM forums helped me try and fix the partitions in the internal memory, but we both think the hardware was the culprit. I was under warranty still and got a replacement phone.
Link
That is the thread I'm following. So far I've had moderate success with the commands posted here:
http://forum.cyanogenmod.com/topic/...hen-restoring/page__view__findpost__p__250529
that are designed to totally re-create the partitions. Attempting to format at the moment from the phone recovery with no connection to the computer. I'm hoping this isn't all hardware related.
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
Grr... still getting errors. Might be dead in the water.
After about a week and a half messing around with things, I have been unable to fix this issue. Luckily I was able to upgrade and went with the Rezound.
I was able to get the format data command to work from within CWM once or twice, but not consistently. I really do think my phone hardware failed. It is scary that if it happened three months later, I would have been out money.
If I'm not mistaken nils roms format the phone to a different type ext. You may want to find a way to reformat the phone to the stock ext. I may be completely wrong on this but since you currently have a brick it might be worth looking into.
Sent from my Incredible Stock+ Ginger Tiny
This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100
Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app
Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.
Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...
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.