Is it safe to delete my internal storage? I've made a backup to my desktop
Sent from my SGH-T999 using Tapatalk 2
Yep. I do it when going from 4.1 to 4.2. Never had an issue
Sent from my SGH-T999 using Tapatalk 2
As long as you backed it up you're fine, I hate 4.2, all because of the multi-user thing and what it does to our memory cards. The average person don't need multi-user support on their damn phone. A tablet on the other hand, yes, I can see where it would be useful, but a phone? Google, you are stupid!! I tried a few 4.2 ROMs not expecting it to creat emulated\0\0\0\0, HORRIBLE!!!! Each time I flashed a new 4.2 ROM it created another folder and placed all my stuff in there. Not to mention the CWM issues when trying to restore back to 4.1. I lost a lot of files in the process of putting my memory card back to the way it should be. There should be an aroma installer where we have the option of ripping the multi-user code out of the ROM. Oly reason I'm still on a 4.1 ROM.
IRIE4IPIER said:
As long as you backed it up you're fine, I hate 4.2, all because of the multi-user thing and what it does to our memory cards. The average person don't need multi-user support on their damn phone. A tablet on the other hand, yes, I can see where it would be useful, but a phone? Google, you are stupid!! I tried a few 4.2 ROMs not expecting it to creat emulated\0\0\0\0, HORRIBLE!!!! Each time I flashed a new 4.2 ROM it created another folder and placed all my stuff in there. Not to mention the CWM issues when trying to restore back to 4.1. I lost a lot of files in the process of putting my memory card back to the way it should be. There should be an aroma installer where we have the option of ripping the multi-user code out of the ROM. Oly reason I'm still on a 4.1 ROM.
Click to expand...
Click to collapse
Just a heads up, if you updated your recovery to the latest it should not recreate the /0 folder. Yes I agree there should be an option for having the folder or not, but it isn't going to kill you, and it shouldn't ruin your day.
Related
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
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....
I'm sure that to some this topic has been discussed to death but I've yet to find any reading material that has helped me understand. If you know where i can find material on what I'm about to ask please point me to it so i can understand. Anyways, here goes:
Ever since 4.2.2 came out flashing back & fourth between 4.1 and 4.2 has been a pain. This is due to the fact that flashing a 4.2 ROM creates a new directory on the SD card ("0") and files either get moved there, or you have to move them manually (especially when going back to a 4.1 ROM). Now what I've been doing as a workaround is right b4 moving from 4.1 to 4.2 (or vice versa) i copy all the contents of my SD card to my external. Then as I'm wiping b4 the flash i go ahead and wipe my internal storage too. Then after flashing my new ROM i copy the contents back to internal storage from the external. Obviously this is time consuming and a pain. Now i read somewhere that the new cwm recovery does something that helps in some way with the issue of new directories getting created every time you flash a 4.2 ROM. I usually use twrp so I'm not very familiar with newer versions of cwm (i used it a lot years ago tho). So my question is two-fold i guess: 1) will the new cwm help at all with my dilemma described above (and if so, how)? And 2) if it doesn't help has anyone found a way to deal with my dilemma in a more efficient way than i?
Thanks in advance guys.
Hello my name is George and I'm a flashoholic.
pathtologos said:
I'm sure that to some this topic has been discussed to death but I've yet to find any reading material that has helped me understand. If you know where i can find material on what I'm about to ask please point me to it so i can understand. Anyways, here goes:
Ever since 4.2.2 came out flashing back & fourth between 4.1 and 4.2 has been a pain. This is due to the fact that flashing a 4.2 ROM creates a new directory on the SD card ("0") and files either get moved there, or you have to move them manually (especially when going back to a 4.1 ROM). Now what I've been doing as a workaround is right b4 moving from 4.1 to 4.2 (or vice versa) i copy all the contents of my SD card to my external. Then as I'm wiping b4 the flash i go ahead and wipe my internal storage too. Then after flashing my new ROM i copy the contents back to internal storage from the external. Obviously this is time consuming and a pain. Now i read somewhere that the new cwm recovery does something that helps in some way with the issue of new directories getting created every time you flash a 4.2 ROM. I usually use twrp so I'm not very familiar with newer versions of cwm (i used it a lot years ago tho). So my question is two-fold i guess: 1) will the new cwm help at all with my dilemma described above (and if so, how)? And 2) if it doesn't help has anyone found a way to deal with my dilemma in a more efficient way than i?
Thanks in advance guys.
Hello my name is George and I'm a flashoholic.
Click to expand...
Click to collapse
Hey George, I was wondering what version of TWRP you are using. I'm currently on v2.4.1.0 and have gone back and forth between 4.2.x and 4.1.x Roms without this problem. I've also heard of others who have had this problem with this same version.
topherk said:
Hey George, I was wondering what version of TWRP you are using. I'm currently on v2.4.1.0 and have gone back and forth between 4.2.x and 4.1.x Roms without this problem. I've also heard of others who have had this problem with this same version.
Click to expand...
Click to collapse
Well i flashed the cwm recovery a couple of hours ago so I'm not real sure what version i was on. I can tell u tho, that it was NOT a very old version. I came back to the s3 about a month ago and i installed it the day i got it. So it can't be a version older than 1 month. Can you clarify for me? What do you mean you don't have this problem? You mean to say that when you flash a 4.2.x ROM you don't get a new directory on your SD card at all?
Hello my name is George and I'm a flashoholic.
topherk said:
Hey George, I was wondering what version of TWRP you are using. I'm currently on v2.4.1.0 and have gone back and forth between 4.2.x and 4.1.x Roms without this problem. I've also heard of others who have had this problem with this same version.
Click to expand...
Click to collapse
Its a issue that has been brought up on the TWRP thread. It does have to do with the internal sd card and the "0". I just make sure my backups are on my external sd card. If you do that you'll have no issues.
Sent from my stock rooted Galaxy S3
Hello everyone,
I think I've screwed up my gf s3, royally.
What I have done.
Goo's aosp kit at and gapps.
Flashed both*I don't think gapps flashed however.
I got the ROM, but no gapps.
What is messing me up royally, is I can't access my twrp backup.
Its like it rewrote the internal memory or something, I just want to try kitkat and be able to just restore my nandroid.
Since I don't have data, I want to nandroid restore but can't.
Help is much appreciated!!
Edit:
I can make calls but no data.
Edit.t
I thought this wouldn't touch back up made with twrp??
Edit:
I've looked everywhere in twrp recovery to restore the back up.
Also to note I have no SD card
What ROM were you running before you flashed? Are your APN settings correct?
audit13 said:
What ROM were you running before you flashed? Are your APN settings correct?
Click to expand...
Click to collapse
Also, your backups are likely still there, just hidden. AOSP Roms tend to work from the /sdcard/0/ directory, while your backups are likely in the /sdcard/TWRP/ directory, which is outside of what AOSP Roms see. You might need to flash a non-AOSP ROM so that it restores the path to your backups.
Thanks for the suggestions!!
Well I got the data situated.
What I did:*the gf did*
Apparently she had the no 4g issue with the ROM previously used, she called her carrier and in the networks settings she had to get the correct thing for it.
There was two choices, 1. Cingular and the other for something else, and for the third part she called her carrier again and she got it fixed.*whew*
So data works, ROM is pretty good, for her anyways.
Now its the data for the internal storage, I am hoping its saved still.
I know about the /0 part but to have it not anywhere to be found even in es file explore has gone completly .
Well when we're near a PC I'll transfer the nandroid to it.
This ROM is pretty nice, Idk what it is exactly but its in goomanager the first "aokp" section, when it boots its like a unicorn or something,
Battery life though could be better.
v1ral said:
Thanks for the suggestions!!
Well I got the data situated.
What I did:*the gf did*
Apparently she had the no 4g issue with the ROM previously used, she called her carrier and in the networks settings she had to get the correct thing for it.
There was two choices, 1. Cingular and the other for something else, and for the third part she called her carrier again and she got it fixed.*whew*
So data works, ROM is pretty good, for her anyways.
Now its the data for the internal storage, I am hoping its saved still.
I know about the /0 part but to have it not anywhere to be found even in es file explore has gone completly .
Well when we're near a PC I'll transfer the nandroid to it.
This ROM is pretty nice, Idk what it is exactly but its in goomanager the first "aokp" section, when it boots its like a unicorn or something,
Battery life though could be better.
Click to expand...
Click to collapse
You can try to improve battery life by playing with the performance settings. I find I get good battery life by using ondemand for CPU and noop.for I/O.
Well, I'm glad you worked the data part out. Unfortunately, the kernel I believe for AOSP Roms also hides everything outside of that /0/ folder from computers, so your nandroid will be invisible on a computer as well. That's one reason why I always use an external SDcard for backups.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
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.