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.

New to Galaxy Nexus (Toro) - Questions and Concerns

Hey everyone. Bought a GN off Swappa.
I'm hoping I can get some help (or assurance that things are fine) about some odd things I noticed:
!) Downloaded the GN Toolkit v7.8.0 and tried to install drivers. Got some fail error, but the toolkit also said that if I got the error it would still work. Every time I plug in my phone, I get a new message from Win 7 x64 that it's "installing a driver". Even though I've already installed drivers. What gives? It also seems to want to install different drivers for when I'm in bootloader or recovery. I've also tried using the download from Samsung's website (Verizon_Wireless_I515_Galaxy_Nexus_USB_Driver_v1.4.6.0.exe) and I still get it. And then following the manual install instructions from the toolkit, I still get a lot of pop ups. It seems the only truly comprehensive method is to install PDAnet. Can anyone confirm? However, I didn't like how it created extra network adapters though. The guide to the toolkit says you can uninstall PDAnet after finishing to retain just the drivers but I didn't have a chance to do that. By then, I'd already used Windows Restore to go back in time and try and find the best driver setup from the get to. I'd really really like to just get the drivers right the first time. Thoughts? Help?
2) It seems that when I moved all my old micro sd card pictures from my Rezound to my PC, and then copied them to the Gnex (while it was working; I'll get to that in a second), the ownership on the Camera folder got messed up causing the Gallery app to force close on every ROM (bekit's theory). Actually, it wasn't really the Gallery. It was the Camera app that would FC but it would say it was the Gallery. Anyhoo, in the process of trying to fix this, I decided to just wipe the SD partition (I should've done an in-ROM factory reset....) and clean install to verify that /data/media/DCIM/Camera was the problem. Except now none of my ROMs are on my phone. Whoops. Well let's copy them over from the computer. Now the phone isn't being recognized. Double whoops. If only those drivers from step 1 weren't such a PITA...
I'm fairly confident that with the latest CWM touch I still have and the Toolkit, I can get a booting ROM again. But the driver and gallery problem I could really use help on.
So. I'm going out of town Friday. I really hope I can get some help getting this up and running by then. Thank you very much.
EDIT: Also, My Gnex keeps showing up under the Asus device listing in Device Manager. I've previously installed drivers for both my Rezound and my room mates Transformer (I rooted and installed a ROM on his tf101). Do I have to uninstall these first?

Maybe try starting here first, and it may answer some of your questions.

for the camera issue, I had a very similar one when copying my pics over to the Nexus from my Rezound. Don't copy them into the DCIM folder. Because they are encoded differently than the Nexus' pics, they wont show up properly or something like that. Instead, copy them to a new folder on the SD called "Old Pics" or something like that. They will show up in a separate section in the Gallery, but that's a fair tradeoff

Well, here's what I did. I'm more concerned with getting this phone up and running. After I do that, I can get rid of duplicate drivers (or maybe I'll keep them all so everything works). Anyway, I used System Restore to go back to step 1.
Now when I use the Gnex Toolkit, it downloads the stock Google image for Toro, but it cannot extract it Ugh. I searched the thread for package extract problems and there wasn't a single post. -_-
Edit: Oh, the file the toolkit dl'ed is only 7 kb... I wonder if this has anything to do with Goo.im being down recently... Just found it elsewhere and am in the process of flashing.
To think I tore everything down because of the stupid f'ing pictures from my Rezound xD
I don't know why I didn't just put them in a separate folder. That's what I did when I moved from the Droid 1 to the Rezound...

Don't use a toolkit is the first step to rooting the GNexus. There are plenty of guides out there that explain how to do it manually.
Not trying to sound like an ass, but it will save you time if (when) you soft brick your device at some point. Everyone does it, I mean its the cool thing to do!
Sent from my Galaxy Nexus using Tapatalk 2

rockingondrums said:
Well, here's what I did. I'm more concerned with getting this phone up and running. After I do that, I can get rid of duplicate drivers (or maybe I'll keep them all so everything works). Anyway, I used System Restore to go back to step 1.
Now when I use the Gnex Toolkit, it downloads the stock Google image for Toro, but it cannot extract it Ugh. I searched the thread for package extract problems and there wasn't a single post. -_-
Click to expand...
Click to collapse
Sorry, but I can't help you with the toolkit.
If you want to do things without a toolkit, I'd be happy to guide you through things. There are a few step-by-steps available.

miketoasty said:
Don't use a toolkit is the first step to rooting the GNexus. There are plenty of guides out there that explain how to do it manually.
Not trying to sound like an ass, but it will save you time if (when) you soft brick your device at some point. Everyone does it, I mean its the cool thing to do!
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The phone was already rooted when I got it. Running aokp nightly #1. I just wanted to try other things.
efrant said:
Sorry, but I can't help you with the toolkit.
If you want to do things without a toolkit, I'd be happy to guide you through things. There are a few step-by-steps available.
Click to expand...
Click to collapse
I found the stock image and flashed it. I'm very familiar with the basic adb and fastboot commands and such.
My main problem now is that I've flashed the stock 4.0.4 image and my Camera is STILL force closing. I even put all my pictures in to a folder OUTSIDE of the DCIM directory. Actually, I put them in the Pictures directory so maybe that's still an issue. I'm going to try moving all my Droid 1 and Rezound picture folders to just the root directory and I HOPE that works.
Otherwise, I think there's a hardware problem. Maybe the camera cable came loose. But if it were loose, wouldn't it just not work? Would it give a force close error? Would it give a different error, since it's the cable and not the software?

rockingondrums said:
[snip[
I found the stock image and flashed it. I'm very familiar with the basic adb and fastboot commands and such.
My main problem now is that I've flashed the stock 4.0.4 image and my Camera is STILL force closing. I even put all my pictures in to a folder OUTSIDE of the DCIM directory. Actually, I put them in the Pictures directory so maybe that's still an issue. I'm going to try moving all my Droid 1 and Rezound picture folders to just the root directory and I HOPE that works.
Click to expand...
Click to collapse
Did you flash the system, boot and userdata images within? If not, did you flash the system and boot images, and wipe data in CWM? If you did not do one of those two options, it's not surprising that you are having force closes.

efrant said:
Did you flash the system, boot and userdata images within? If not, did you flash the system and boot images, and wipe data in CWM? If you did not do one of those two options, it's not surprising that you are having force closes.
Click to expand...
Click to collapse
The beauty of the toolkit is it automatically extracted and flashed the .tgz file for me. I had to do it this way because previously I wiped EVERYTHING on the phone with CWM. system, boot, data, cache, dalvik, AND sdcard. That was back when I was trying to fix the gallery issue. Tore it all down to start over.
I'm still moving pictures out of any picture related directories in the hopes that solves the issue. It's taking awhile. That's actually another concern I had: Windows Explorer seems to be a little slower copying/moving files to the GN internal storage than with other phones. It also shows a goofy looking icon of a generic looking PMP when the GN is plugged in.
When this file transfer is done, I'm going to put CM10/Gapps on the card, wipe everything and flash it clean. If it still FC's, I'll probably erase the pictures from the phone (again) and see how to go from there.

rockingondrums said:
The beauty of the toolkit is it automatically extracted and flashed the .tgz file for me. I had to do it this way because previously I wiped EVERYTHING on the phone with CWM. system, boot, data, cache, dalvik, AND sdcard. That was back when I was trying to fix the gallery issue. Tore it all down to start over.
Click to expand...
Click to collapse
The downfall of toolkits is that you do not know what it is actually flashing. If you do it yourself through fastboot, you can be sure you flash everything that you are supposed to. And it makes no difference if you wiped EVERYTHING. Fastboot works with EVERYTHING WIPED.

efrant said:
The downfall of toolkits is that you do not know what it is actually flashing. If you do it yourself through fastboot, you can be sure you flash everything that you are supposed to. And it makes no difference if you wiped EVERYTHING. Fastboot works with EVERYTHING WIPED.
Click to expand...
Click to collapse
Honestly, I'm beginning to think it's faulty hardware. I'm going to take out the camera tomorrow and clean it (I work at a phone repair place as luck would have it). If that doesn't work then I'll look in to buying replacement hardware.
Thanks for all the help and info people. I'll probably update this when I've solved it.

[Q] Flashed a 4.2.1 ROM from a 4.1.2... Don't know what to do with '0' File... help.

Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:

0Capita said:
Hi, its my first time posting, I figured I wanted to sign up to XDA eventually so why not when I feel like I've completely ruined my phone... or at least internal sd card...
Basically I rooted my phone and was flashing the Jellybam rom, and everything was going smoothly until I got to the bootloader and my phone started bootlooping. My first thought was 'Oh but I have a backup'. So I went to my backup in CWM and to my dismay I got an error saying "No files were found."
I could clearly see my files from exploring around on my sd card however they were now in a file called '0' and CWM could not read them from there. Without a working ROM I started to panic. However I had a zip of CM10 still on my internal sd card so I flashed that and (luckily) it worked.
Not really being too competent with flashing new ROMs yet I was quite happy that I had anything. So I used titanium backup to reinstall my old apps and data. However once they were installed I now get an error with 'the process android.process.media has stopped'.
I'm guessing this has do do with the fact that I have all my files still on the '0' folder. All the other folders from the '0' folder were the same except they were all empty, soooooo I decided to delete them. At this point I'm guessing that was a really bad idea because my initial plan of moving all the files from '0' to my pc then back to my phone, I did not think about the fact that I would be moving 14 Gb of data...
So basically now I'm hoping if someone knows a way to revert my phone to 4.1.2 by somehow moving all the files from '0' back onto the internal storage (basically getting rid of this '0') folder. The CM10 ROM is a 4.1.2 ROM so its not like I'm fudging up my phone further (I hope).
If you could be as detailed as possible as to what to do that would be great, because I'm really really new to this....
From what I've read I've heard a couple of suggestions:
1. updating the recovery.img of CWM will work? How exactly do I do this?
2. opening abd shell recovery and moving the files like that (however I deleted all the other files in the internal storage apart from '0' because that was where all the data was stored and everything else was empty...'
help. :crying:
Click to expand...
Click to collapse
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.

BWolf56 said:
1- Your solution
2- Was quite the bad idea to delete it all so this solution won't work now.
clockwordmod.com is where you'll find the latest recovery.
Click to expand...
Click to collapse
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!

0Capita said:
So how exactly do I do that? I just download the the latest clockwork mod and flash it? Why can't it be updated via an automatic updater? And what will it do to the file or will it change clockwork mod so that it will scan the entire sd card?
Also if I just remade folders identical to the ones I deleted, will that still work?
I'm just trying to get my phone to be as functional as it was before this all started.
Thanks for replying btw!
Click to expand...
Click to collapse
That's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.

B said:
Wolf56;371questions it's a lot of question for the simple fix I gave you.. I haven't used cwm in a while so Idk what changed in the update but if people said it fixed it, then it did..
0, 1, 2, etc.. Is something that came with JB, it's for the different users. Not much can be done about it.
About how you should do that: Go on their website, FOLLOW their instructions to a T, Enjoy.
As for why it can be updated via an automatic updater.. Well I'm not the person you should ask.
Click to expand...
Click to collapse
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.

0Capita said:
Sorry for all the questions, I'm just worried that I messed up my phone. Would you know if I were able to be able to access my old clockwork mod backups and used one of them, would it put my 0 files back into the internal storage like they used to? Or would it only revert the settings and I would still be SOL.
Click to expand...
Click to collapse
Yes, that's the whole point of the cwm update. Now to flash it!

Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.

BWolf56 said:
Yes, that's the whole point of the cwm update. Now to flash it!
Click to expand...
Click to collapse
Well here's my latest problem... I tried to update CWM with an .img however when I tried to run it in the terminal it said there was not enough space... I don't know what to do... there is definitely a couple gigs free so I don't know what is wrong...

mrhaley30705 said:
Or, go digg through the cm nightly thread. They had a flash able zip that would restore your internal sd after downgrading Android versions.
Click to expand...
Click to collapse
the cm nightly thread? So theres a zip that would make 4.2 go back to 4.1?
Okay update:
I managed to flash update the new version of CWM... still can't use backup... I get a /system fail

It doesn't downgrade you're ROM. It fixes the 0 folder issue

mrhaley30705 said:
It doesn't downgrade you're ROM. It fixes the 0 folder issue
Click to expand...
Click to collapse
Ugh Okay I've given up... I dont know what else to try. Now that I've updated my CWM I cant flash the old CM10 because it reads it as a 4.1 and uncompatable... FML.
Can anyone point me to where I can find the Odin stock factory? I guess I'll just start from scratch...

http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app

Helloworld294 said:
http://db.tt/rWFbAFiF
Link to restore files from /0 directory
Credits go to madmack
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
OOOMMMMMGggg ahhhhhh, that would have been so helpful but I've already started to factory reset it. Thanks though!
ahhhhhhhhh

Forget cwm it sucks use twrp and be done with all the problems
Sent from the scary door....

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] problems with flashing a new rom and more

Hey guys, it's been a long time since I've been flashing roms and stuff and I barely came back since I was tired of this jellybean Rom I'm on. Right now I have an older Rom that from what I an seeing isn't being developed anymore, wicked v10, Android 4.1.1, and I went through all the backups, with using tb to back up my apps, and I went into my recovery, cleared data and system, flashed quantum 3.6.4, flashed pa gapps, the same old stuff, and after I set up, I noticed the emulated sd card as I expected as it did that to me when I used to run aokp, but I could not ever find for the life of me any of my titanium backup backups, screenshots, etc. Even when I checked my other sd card folders. I found that strange since when I restored my backup, I was easily able to find the rest of the things mentioned. So what am I doing wrong? Also, is there a way to port my sms to hangouts as the new Rom used, and will I be able to used the restore backups of my contacts through the xml or something file that I generate in my contacts app when I used the app that comes with the new Rom? Thx in advance

Adding on to the fact I cannot edit my old post from my buggin out xda app, I seem to have found out whats wrong, which is that my internal sd is either not mounted properly, or cannot be read properly, while flashing ANY kitkat rom. I tried to search forums and google for a solution to this but I couldn't turn up anything. So can anyone at least tell me if this is a recurring bug on cm11 or kitkat based roms or am I just screwing up on something along the way?
Sent from my GalaxyS III

Have you tried Odin flashing your firmware and factory resetting after?
Could also be the /0/0/0/ folder problem. Every time you flash a rom it adds another /0 and that becomes the default directory. Look in /storage (maybe wrong, going by memory). It's well documented though. Check the faq sticky, I think it may be covered there.
Sent from my SM-N900T using Tapatalk

DocHoliday77 said:
Have you tried Odin flashing your firmware and factory resetting after?
Could also be the /0/0/0/ folder problem. Every time you flash a rom it adds another /0 and that becomes the default directory. Look in /storage (maybe wrong, going by memory). It's well documented though. Check the faq sticky, I think it may be covered there.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I have not tried odin flashing and all that stuff just yet but I checked every possible folder using es file explorer and it seems not to be mounted. I will check the faq though
EDIT: FAQ didn't come up with anything. The only thing I can do now is to Odin my phone but I'm not sure exactly if it would work and be worth my time. It seems as if other people with different devices using cm11 and cm11 based roms have had this issue
Sent from my GalaxyS III

Is theres a way to fix apps failing to connect to facebook. I installed S3rx Rom a few times and downloaded it a few times also and it keeps happening. Also thethering activates, im able to connect devices but when I go to connect to internet I get webpage cannot be displayed.