Develop Bugs

[Q] Rooted Unlocked = Broken Camera

Hey guys. I finally unlocked and rooted my phone but somehow broke my camera. It loads up and takes a picture but it never saves. I thought I had read about this issue a while back but my searches have come up empty. I did download another camera app called fxcamera and it seems to work just fine. I liked the original app and would like to get it working again if possible. Oh yeah I'm still using the stock rom. Any ideas?

I don't really know where to begin with this issue. It seems so minor and appears to be the only thing not working at this time. It weird because nothing changed. Its only been rooted and unlocked. I tried to clear data. That didn't help. I'm thinking I just need to flash a new rom. I just haven't decided which one yet. I don't have time to play with a few so whatever I pick needs to my daily driver for awhile. Maybe I need to reset to factory again? Again any ideas?

I've too seen others with this issue...
Not sure what they did to fix it...
But I also remember one user flashing multiple roms in the attempt to fix and didn't fix it.
Sorry I'm not of further help at the moment, I'll do a quick search as well.
Edit:
Might be a permissions error.
Try deleting the dcim folder from your SD card first...
And then check this thread:
http://forum.xda-developers.com/showthread.php?t=1473629&highlight=camera+not+saving
The code user #2 gives can be imputed through "Terminal Emulator" found in the market.
Type "su" and hit enter.
App will ask for superuser permission...accept, obviously.
Then input his code.

Thank you for trying but Im still stuck. I tried deleting the DCIM folder but it wont let me. Just says folder cannot be deleted. I then tried to run that command in terminal emulator but it says it cant find busybox. I really dont know what im doing here but its my guess it cant find busybox because its not installed where its expecting it to be. And I cant install it where it expects it to be. Would it make sense to wipe everything out and install a new ROM?

Just reboot the phone. If that fails, clear data and reboot.
Sent from my ADR6350 using xda premium

Still no go. In the meantime I was able to get my camera working again by renaming the DCIM folder To DCIM1 and creating a new Folder called DCIM with two subfolders 100ANDRO and Camera. Not sure if the subfolders were needed but it worked. The old folders with my backed up content still sit there now useless and still cant delete. Cant I just wipe everything and start from scratch. I really just want a clean install. I dont need to backup anything. I didnt need to backup anything after rooting and unlocking but I figured why not.

You can reformat your internal SD card via CWM. If it still doesn't work I'd put it back to stock and take it back to the store and complain it doesn't work properly. Assuming the camera doesn't work as desired once back to stock.

Kalavere said:
You can reformat your internal SD card via CWM. If it still doesn't work I'd put it back to stock and take it back to the store and complain it doesn't work properly. Assuming the camera doesn't work as desired once back to stock.
Click to expand...
Click to collapse
+1 If you have problems with any part of the phone just unroot and take it back. if that fixes the camera. then you know it was the method you used to root and I would try another method.

Fix it from recovery
I had a similar problem because I copied files to my sdcard folder while in recovery, which uses root ownership but when the system is booted, sdcard is mounted under a different userid which does not have permission to modify root owned files.
1. boot to recovery
2. use adb shell to cleanup or chown root-owned files to 1023:1023 so they can be modified after rebooting

If you are still having problems you can always just use the ToolKit to unlock and flash a google stock rom which will wipe everything including virtual sd card and should fix any problems.
Mark.

Kalavere said:
You can reformat your internal SD card via CWM. If it still doesn't work I'd put it back to stock and take it back to the store and complain it doesn't work properly. Assuming the camera doesn't work as desired once back to stock.
Click to expand...
Click to collapse
Im confident this isnt a hardware issue
mskip said:
If you are still having problems you can always just use the ToolKit to unlock and flash a google stock rom which will wipe everything including virtual sd card and should fix any problems.
Mark.
Click to expand...
Click to collapse
Thanks Mark your right seeing as though I just want a clean install at this point anyways. I remember looking at that in the tookit but it was late and I think I dismissed it because I believed at the time it would also lock or unroot it or both. Im guessing since you recommended this option that is not the case.
Thanks everyone for their input. I appreciate it.

IFLATLINEI said:
Im confident this isnt a hardware issue
Thanks Mark your right seeing as though I just want a clean install at this point anyways. I remember looking at that in the tookit but it was late and I think I dismissed it because I believed at the time it would also lock or unroot it or both. Im guessing since you recommended this option that is not the case.
Thanks everyone for their input. I appreciate it.
Click to expand...
Click to collapse
Flashing the Google Stock Image will not relock the bootloader but you will lose root. You can easily use the ToolKit after you flash the Rom to root the phone again if you wish.
Mark.

My nightmarish ordeal with Jellybean

All I wanted to do was upgrade my stock Takju phone to Jellybean. I don't get to.
It started with the preview. I flashed it. Everything seemed to be okay, except that none of the apps could find any files on my /sdcard. I then realized that programs like Root Explorer and Airdroid saw a completely different /sdcard than what my PC or any phone apps did. I asked around, fixed permissions from as many apps as offered, tried wiping every partition I could think of, but nothing fixed the problem.
So I waited for the "official" build to come out. I figured this time I'd try a "dirty" install, so that the permissions would be where they need to be. The phone refused to boot. It got stuck on the boot animation.
So, I used GNex Toolkit to wipe the phone to factory specs. It was like I just got it. I ran the phone once, Rooted, installed TWRP, wiped everything twice for good measure, installed the JB ROM, and held my breath.
It looked good at first, but it STILL had the same /sdcard issue, but this time had the added fun of the USB port breaking after 30 seconds, making me unable to copy any files over to the fake partition anyway.
So now I'm copying files back to the phone which was restored once again to 4.0.4 (USB port works fine now). I've spent 14 hours on this so far only to end up right back where I started. The thing I find baffling is that, based on what I've read here, I am the ONLY person in the entire world having this problem, despite working with what is, for all practical purposes, a factory fresh phone.

You are not the only person with the SD sdcard0 issue. Perhaps the only person with transfer of file and recognition issues. When the full jelly bean image comes out I am going to flash that hoping it clears up the double SD issue.
butter and jelly please...

I had a similar problem, I had to completely erase the SD card ("fastboot erase userdata" does not work, had to reflash a new image for the sd).
One of the causes is that the /sdcard "partition" points to /data/media in ICS but it goes to /storage/sdcard0 on JB (thanks to XBIRDIE98 for that info). I think the Play Store GNex not wiping borks the filesystem when both of them point to the /sdcard partition. Some apps see /data/media while others see /storage/sdcard0

Yep, I have this **** too. Only negative to 4.1.1 I've found
Sent from my Galaxy Nexus using xda premium

I finally got it back to where I started. I had to trick CWM into finding the file because it was in a different folder than where it should be, But, the USB port once again works, so clearly it had something to do with how sdcard0 is setup. I might try it again once a complete image comes out and I can push it with GNex Toolkit.
Why can't there be a "complete" backup that also gets the SD Card/

Glad to hear you got that sorted. Try flashing direct to takju 4.1.1 and skip 4.1

It's nice to hear that someone else had usb problems too. I thought it was some sort of mechanical problem. Maybe I still have hope after all.

Same thing here. No issues with cwm or anything but sdcard0 what I have to
Sent from my Galaxy Nexus using Tapatalk 2

Had a similar problem at one point. Had to fastboot all the stock images back.
Sent from my Galaxy Nexus using xda premium

Archpope said:
All I wanted to do was upgrade my stock Takju phone to Jellybean. I don't get to.
It started with the preview. I flashed it. Everything seemed to be okay, except that none of the apps could find any files on my /sdcard. I then realized that programs like Root Explorer and Airdroid saw a completely different /sdcard than what my PC or any phone apps did. I asked around, fixed permissions from as many apps as offered, tried wiping every partition I could think of, but nothing fixed the problem.
So I waited for the "official" build to come out. I figured this time I'd try a "dirty" install, so that the permissions would be where they need to be. The phone refused to boot. It got stuck on the boot animation.
So, I used GNex Toolkit to wipe the phone to factory specs. It was like I just got it. I ran the phone once, Rooted, installed TWRP, wiped everything twice for good measure, installed the JB ROM, and held my breath.
It looked good at first, but it STILL had the same /sdcard issue, but this time had the added fun of the USB port breaking after 30 seconds, making me unable to copy any files over to the fake partition anyway.
So now I'm copying files back to the phone which was restored once again to 4.0.4 (USB port works fine now). I've spent 14 hours on this so far only to end up right back where I started. The thing I find baffling is that, based on what I've read here, I am the ONLY person in the entire world having this problem, despite working with what is, for all practical purposes, a factory fresh phone.
Click to expand...
Click to collapse
i used ASTRO file manager to make sure the update.zip was in the correct SDCARD folder. Just go to the root folder and you'll find your SDCARD, but it's probably a bit late to be saying this....

Do the AOSP builds of JB (4.1.1) still create this symlink, or whatever, to sdcard0 on fresh installs? Or are the bugs from some weird partitioning a holdover from the GSM ports, which only had 16GB flash memory?
I tried VanirBEAN v3 when it came out and noticed that issue. I was getting random system crashes and sometimes reboots once I decided to nandroid restore my 4.0.4 backup. So after backing up /data/media/ through ADB I did an entire fastboot flash of the stock IMM76K image (here if anyone needs it) to ensure my device was back to 100% stock. I'm currently on 4.0.4 (AOKP M6) and reluctant to go back to JB because of this very issue - I'm just glad to have everything back to normal.

Thegodfather156 said:
Same thing here. No issues with cwm or anything but sdcard0 what I have to
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It's supposed to be like that. People are making issues out of things that aren't issues at all.
/sdcard symlinks to /storage/sdcard0
Just as
/mnt/sdcard symlinks to /storage/sdcard0

I think the concern is that pre-JB /storage/sdcard0 doesn't exist. So when you install JB, you get duplicate symlinks to wherever "sdcard" is.
I no longer have /storage/sdcard0, or at least I can't find it anymore. However, I can navigate to /data/media and find the same contents as /sdcard. My main concern is that there might be more partitioning going on behind the scenes that break things on restores between ICS and JB.

I've swapped back and forth at least a dozen times and not had duplicated symmlinks.

binglejellsx2 said:
My main concern is that there might be more partitioning going on behind the scenes that break things on restores between ICS and JB.
Click to expand...
Click to collapse
This was my concern. I had to reflash the sdcard partition since I had 5GB of storage space missing

harveydent said:
This was my concern. I had to reflash the sdcard partition since I had 5GB of storage space missing
Click to expand...
Click to collapse
Same here. I thought I was just imagining things. After returning everything back to the sdcard, I now had 9gb free instead of something like 2gb.

i had same issue to. used nandroid back up and fresh install worked for me.

I have been having issues with the sdcard since flashing the preview too and through several roms
Initially it didnt see any of my pics...a few hours later they were there.
Turns out on boot Android Media Server is running at about 40-50% for about an hour.
Once this is done then my pics show up in gallery and the phone runs great.
I dont have that many pics so if you have more I could see this taking hours.
(I use Watchdog light to see what hogging the CPU)
I've tried several things to fix including renaming the DCIM folder and creating a new one...putting a .nomedia file at the root of the SDCARD
Nothing seems to work. I watched the logcats looking for some media scanner errors but never see any.
Right now Im running a CM10 Kang.
At this point I will probably reset to factory and start from scratch and then copy my data back.
I wish there was another solution, maybe partition the SDCARD?
Archpope said:
All I wanted to do was upgrade my stock Takju phone to Jellybean. I don't get to.
It started with the preview. I flashed it. Everything seemed to be okay, except that none of the apps could find any files on my /sdcard. I then realized that programs like Root Explorer and Airdroid saw a completely different /sdcard than what my PC or any phone apps did. I asked around, fixed permissions from as many apps as offered, tried wiping every partition I could think of, but nothing fixed the problem.
So I waited for the "official" build to come out. I figured this time I'd try a "dirty" install, so that the permissions would be where they need to be. The phone refused to boot. It got stuck on the boot animation.
So, I used GNex Toolkit to wipe the phone to factory specs. It was like I just got it. I ran the phone once, Rooted, installed TWRP, wiped everything twice for good measure, installed the JB ROM, and held my breath.
It looked good at first, but it STILL had the same /sdcard issue, but this time had the added fun of the USB port breaking after 30 seconds, making me unable to copy any files over to the fake partition anyway.
So now I'm copying files back to the phone which was restored once again to 4.0.4 (USB port works fine now). I've spent 14 hours on this so far only to end up right back where I started. The thing I find baffling is that, based on what I've read here, I am the ONLY person in the entire world having this problem, despite working with what is, for all practical purposes, a factory fresh phone.
Click to expand...
Click to collapse

[Q] E4GT FI27 Boot Loop

If I'm posting this in the wrong place I apologize in advance. I'm also a bit freaked out since my phone seems to be kaput right now, but I have faith this is fixable. I need some of you professionals to give me your advice on how to go about fixing this.
Okay here we go...
I have in the past rooted my phone without any major issues by just reading this awesome site. I recently used "SPH-D710_FI27_CL1127689_Rooted_NoData" to root my phone using the one click method and everything was working fine. I realize now that I should have backed up all of my user data on the phone prior to updating to ICS from Gingerbread.
So, I think I made a newbie mistake by actually using Titanium Backup Pro (updated to latest version) to restore 1 file called wallpaper from the date 03/2012 (March 2012) which was when my phone was using Gingerbread 2.3.4 I think. I remember hitting the restore button and getting an option to restore only the data, so I chose this and a notification said, "Reboot phone for changes to take effect". Once the phone rebooted I unlock the screen and see the wallpaper I had from earlier this year. Now, I think the main problem is that I'm now using Ice Cream Sandwhich 4.0.4 and restoring the wallpaper from Gingerbread 2.3.4 has caused some underlying issues which is causing my phone to constantly reboot.
I went to the Sprint store and explained the issue and the Sprint representative said my phone needed to be reset because it seems to be glitching out. I informed him that I had files on my phone that I wanted to try to backup to my computer before I completely wipe the phone. Now, I'm home and I'm trying to get my phone to pop up in Windows 7 x64. I keep getting USB connection errors while connecting my phone to my PC because the phone keeps constantly rebooting while the drivers are trying to install then as soon as the phone reboots the driver installation fails.
USB Device Not Recognized
SAMSUNG Mobile MTP Device failed installation
So I've tried uninstalling Samsung Kies and the USB drivers and then re-installing them and rebooting. Still no joy because my phone keeps constantly rebooting. It is never going to complete installing because the phone is completely unstable at this point in time. Further research led me to updating the MTP from Microsoft. After installing this I rebooted. Problem is I'm still getting connection issues while trying to connect my Epic 4G Touch to my PC because the drivers are not able to install because of the constant reboots, even though they were installed previously. This is how I was able to root my phone to begin with.
So basically what I'm trying to do is backup my files on my phone to my computer (which it now may be too late) before I just completely reflash a fresh ROM (Full Restore on FI27) and start over from scratch.
I had the idea of actually reapplying "SPH-D710_FI27_CL1127689_Rooted_NoData" to hopefully reset the kernel so I could backup my phone to my computer. This hasn't resulted in any changes whatsoever either. I'm completely stumped and would really appreciate some wisdom here.
I hope all of this makes sense and I hope someone out there is nice enough to take a little time to point me in the right direction.

I have just placed the phone in download mode with the idea of re-downloading "SPH-D710_FI27_CL1127689_Kernel" and USB drivers have been installed successfully.
Nice to see this thread is getting some views, but no one has any advice to give me?

What files on your phone do you need?

I just got the Phone to show up in Windows Explorer by plugging in the USB cable right when the Yellow 4G came up and I was browsing the phone and I noticed the SD Card was not showing up, but before long the phone rebooted and I'm still trying to access the phone but the damn thing keeps rebooting constantly.
I'm just trying to backup photos I don't have backed up anywhere else. Other than that I'm hoping I can do a full restore using "SPH-D710_FI27_CL1127689_Rooted_Restore" and that will at least get my phone back to operating normally right?

Just go into the recovery menu and do a factory reset. It won't format your SD card.
Sent from my SPH-D710 using xda premium

m4xwellmurd3r thanks for the advice.
I got impatient and went ahead and flashed "SPH-D710_FI27_CL1127689_Rooted_Restore" and my phone is back to operating normally. My SD card is still intact as well! What is really surprising is the fact that the pictures that were on my phone are still there. I don't understand, I obviously did something wrong. Also no longer having USB connection issues so that is a big relief as well!
Of course all the applications I had installed are no longer present, but why are my pictures still intact after using a Rooted Restore.
I want to completely wipe my phone and then create a backup with Titanium Backup and call it Stock_Version#. Then after I root the phone and get everything setup the way I like it I want to create another backup called something else. Is this the correct way to go about doing this?

Because none of your storage gets wiped by factory resets. Resets only affect the rom portion of your phone not storage. Glad you got it working
By the way rooted restore already wiped everything on your phone and rooted it so you're good to go
Sent from my SPH-D710 using xda premium

m4xwellmurd3r said:
Because none of your storage gets wiped by factory resets. Resets only affect the rom portion of your phone not storage. Glad you got it working
By the way rooted restore already wiped everything on your phone and rooted it so you're good to go
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Really? Okay, so I shouldn't see any empty folders for apps I no longer use?
I swear everytime I start looking at the folders in my phone I see things I don't recognize and it just bothers me. This is one reason I wanted to reset my phone and start over fresh.
Also is there a good tutorial for using Titanium Backup?

Any folders made on the SD card and internal storage will remain since factory resets won't touch the data, even if the app is gone
Sent from my SPH-D710 using xda premium

So when you install an app just to test it out then you un-install it remnants of that app are still left behind. This I have to say I don't like. There has to be a better way to keep the file structure free from accumulating garbage. Is there a better way or not?

Ci2e said:
So when you install an app just to test it out then you un-install it remnants of that app are still left behind. This I have to say I don't like. There has to be a better way to keep the file structure free from accumulating garbage. Is there a better way or not?
Click to expand...
Click to collapse
You could always delete the /data contents for the APK but not if it's in android.secure.... you won't know what is what in there.

@garwynn - What is the difference between SPH-D710_FI27_CL1127689_Rooted_Restore.exe, and SPH-D710_FI27_CL1127689_Rooted_Restore_v2.exe?
Also I want to completely reset my phone now that I have everything backed up to my PC that I care about. So do I need to do a factory reset on the phone and then flash one of the files above?
The plan is to get a fresh start and use Titanium Backup like I should have been doing from the start!

Ci2e said:
@garwynn - What is the difference between SPH-D710_FI27_CL1127689_Rooted_Restore.exe, and SPH-D710_FI27_CL1127689_Rooted_Restore_v2.exe?
Also I want to completely reset my phone now that I have everything backed up to my PC that I care about. So do I need to do a factory reset on the phone and then flash one of the files above?
The plan is to get a fresh start and use Titanium Backup like I should have been doing from the start!
Click to expand...
Click to collapse
Copied from the v2 thread.
garwynn said:
...What's the difference? Flash order.
Normally our one clicks don't have the same order as Sextape's leak.
Version #2 is a test of using the same order and so far so good for me.
Click to expand...
Click to collapse

That's great I can't find that thread at all, can you give me some linkage?
MoHoGalore can you answer my second question?

Ci2e said:
That's great I can't find that thread at all, can you give me some linkage?
MoHoGalore can you answer my second question?
Click to expand...
Click to collapse
Click the tiny arrow beside Garwynn's name in the quote I posted. It'll take you to that thread i copied it from.
No, you do not need to factory reset when you use an Odin one click.

I just got done using an Odin One Click -> SPH-D710_FI27_CL1127689_Rooted_Restore.exe, all my data was left intact. Are you sure you know what you're talking about?

Ci2e said:
I just got done using an Odin One Click -> SPH-D710_FI27_CL1127689_Rooted_Restore.exe, all my data was left intact. Are you sure you know what you're talking about?
Click to expand...
Click to collapse
Lol. So your google account settings remained? You didn't have to setup anything?? If that's the case, either it was the no data version or it didn't flash.
And if you're taking about formatting the usb storage, like blues said in the other thread you asked, it doesn't format it.
But feel free to get other opinions.
:edit: And the only way I'd ever suggest to "factory reset" from the privacy menu, would be to use a gb build. But don't take my word for it, read the brick bug thread.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

I'm just getting confused here I think your right. So basically if I do a factory reset via the settings menu, that will reset everything but keep the same model FI27. Then all I'll need to do is reflash the SPH-D710_FI27_CL1127689_Rooted_Restore.exe, right?

Ci2e said:
I'm just getting confused here I think your right. So basically if I do a factory reset via the settings menu, that will reset everything but keep the same model FI27. Then all I'll need to do is reflash the SPH-D710_FI27_CL1127689_Rooted_Restore.exe, right?
Click to expand...
Click to collapse
See my edit above. I'll never suggest using that option with an ics build at this time.
Now, having said that, i have done it but with the brick bug, that choice is yours.
What i try to do is just format the drives (both internal and external) when connected to my laptop then power off, then use a one click.
Safe method - use a gb one click, factory reset via privacy option in settings and format usb, then use the fi27 one click.
Sent from my SPH-D710 using Xparent ICS Tapatalk 2

Okay tell me I understand this correctly.
Format both internal/external drives via settings > privacy > Factory data reset (this does not touch the SD Card, right?) while USB cable connected.
Power off phone and boot into download mode, then flash a "Stock Gingerbread Rom" (matching the model #, will it still be FI27 or not?) then at this point if I'm still on FI27 all I'll need to do is reflash "SPH-D710_FI27_CL1127689_Rooted_Restore" to regain root.
If after doing a factory reset and flashing a stock gingerbread rom I may have to wait for updates to be pushed to my phone, or not?

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] TWRP trouble

Hi. I managed to root my S3 and remove Knox. At first, TWRP was working fine, but after a few unsuccessful attempts to flash CM, I think i screwed it up. My backup files are gone, and it won't make a new one as it "cannot access storage." It also takes up about 6 gigs of storage on the phone per applications manager, which seems like a lot.
Is there a way to delete it and do a fresh install? now that I am rooted, would another backup/recovery be better?
I have tried searches, nothing seems to be on oint. Perhaps I was casting my net too wide or too narrow.
THANKS

Probably has to do with the /0/0/0 folders. Every time you flashed something, itd create a new /0 directory. Your stuff is still there but the path is messed up so it doesn't know where to look. In twrp file manager look for /storage/0/0/0 or something/somewhere like that. (It's been a while so I may not be remembering exactly right) this is a well documented issue though, so if im wrong just Google it and you're sure to find the right info. I believe it may be covered in one of the sticky threads too.
Sent from my SM-N900T using Tapatalk

Idk if this is your issue or not but I had a problem where recovery couldn't find the files or access storage I had the wrong version of recovery flashed and it wouldn't read anything I originally had the right one but somehow I lost recovery and ended up flashing the wrong one and it did what you are describing I'm on cwm so I'm not sure which is the right twrp but I'd just make sure you have the right one for your model. Good luck figuring it out though I know you will if you do your homework you will get it.

I went in and looked at the files, I had several named backups. I deleted all but one.
Goo Manager wouldn't load the newest TWRP, so I went to the app store and downloaded the app.
Now it takes far less space and recognizes the one backup.
THANKS for bearing with me.
I put a copy of the backup on my computer, just in case. Going to try flashing CM again, hope I can get it to work.