is there any way to undo this? i tried to go to a 4.2.2(liquid) and had some issues so i went back to 4.2.1.
did some more looking into and decided to try it again. same problems plus some. now im yet again back on 4.2.1 and have 3 different "0" folders and its driving me crazy...i tried using my pc to just cut and paste everything to where it should be a merge all the like folders but that is taking absolutely forever on some folders(had to go one at a time so it would do anything) some are quick but some arent.
do i just need to stick with what ive been doing or is there an easier way?
this is all on the internal storage if that matters
I haven't had this problem yet since I haven't switched back/forth... but I wonder if you might get faster results by using the command prompt. If you're not familiar with linux commands then I don't recommend it, but if you are.. then ADB shell, su, and start mv'ing.
OMG_VTEC said:
is there any way to undo this? i tried to go to a 4.2.2(liquid) and had some issues so i went back to 4.2.1.
did some more looking into and decided to try it again. same problems plus some. now im yet again back on 4.2.1 and have 3 different "0" folders and its driving me crazy...i tried using my pc to just cut and paste everything to where it should be a merge all the like folders but that is taking absolutely forever on some folders(had to go one at a time so it would do anything) some are quick but some arent.
do i just need to stick with what ive been doing or is there an easier way?
this is all on the internal storage if that matters
Click to expand...
Click to collapse
since you are using a 4.2.2 capable recovery, EVEN if you are back onto a 4.1.2 ROM and still have the 0 folder, the recovery will still read the 0 folder regardless. lessen learned for me the hard way, always look before wiping to make sure the file u want to flash is there..
anyway, delete all the zero folders.. in fact if you don't have toooo much stuff on the internal, then do a quick format, this will remove all the 0 folders and then move what you want back.
what I do when I'm on a 4.2 and under ROM is rename my 0 folder to anything but 0, for me 00, and if I'm going to flash a nandroid of a 4.2 ROM or install one I just rename it back to 0 and all is well. make sure to always keep an extra 4tw ROM on in the 0 folder, in case your backup aren't showing up when in the 0 folder on 4.2 ROM.. u can however use the file manager built into TWRP, delete the TWRP folder, reboot recovery and you will be back in action...
yes, I've been doing a lot of testing with 4.2.2 lol so I learned it all the hard way. this should save you a good amount of time.
im just using drag and drop, but everytime i go to the original destination(root or int. storage) it takes FOREVER to load...:crying:
driving me bonkers since im at work and have limited time to devote to this increasingly menial task
OMG_VTEC said:
im just using drag and drop, but everytime i go to the original destination(root or int. storage) it takes FOREVER to load...:crying:
driving me bonkers since im at work and have limited time to devote to this increasingly menial task
Click to expand...
Click to collapse
This is the main reason I haven't left 4.1.2 yet. Pacman 19.3 running to good to fool with that mess. But that's just me
Hi. I flashed the CM 10.1 M1 rom (4.2) and decided to go back to a stock rooted TW rom (4.1). This left me with the issue mentioned in this thread.
After reading the above posts, I just want to clarify how to deal with the "0" folder issue, which remains after reverting back to a 4.1 rom. My understanding is there are 2 ways to deal with this:
1. cut and paste the files in the "0" folder (which was created when flashing the 4.2 rom) back into the original internal sdcard folder. this would result in merging some of the folders/files with the same name in the "0" folder with those with the same name in the internal sdcard folder. Might also take a while.
2. use adb...if a step by step guide on how to do it this way can be shared, it would be appreciated.
because of the hassle. i would up just copying the contents of the "0" folder which I needed onto my computer, and formatted the internal sdcard, but if the adb way is a simply way, i am willing to give it a shot.
thank you for any input.
Related
I've been doing a lot of reading lately and I am finally about to flash my first ROM. Below is a list of what I've done as far as backup and prep. What I want to know is if there is anything important that I missed?
Made a nandroid backup with CWM
Backed up apps with Titanium Backup
Backed up efs directory from the phone
I have a copy of settings.db on my compuer
I have Odin 1-click on my computer
I have a jig made up just in case
Also, since I am on stock 2.1(JH7), I assume I don't need to go through the odin 1-click step, right?
Thanks in advance for your help
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
i also put a copy of my sd card onto my computer in case something goes bad, but that's just my paranoia/ocd
and you should flash at 100% battery and reset the battery stats while flashing. you can even flash while the phone is plugged into the computer or ac outlet, so the flashing process doesn't drain from the phone battery. some ppl say this is voodoo, but i always flash at 100% and reset the battery stats while changing roms because its a convenient time to reset stats
sublimaze said:
looks like you have everything covered except one thing (maybe): if you have an unlocked phone, check the forums to learn how to get your unlock back *before* flashing
Click to expand...
Click to collapse
OK, thanks. I'm glad you mentioned that. I do have it unlocked and I didn't even think about it. I have to go to Thailand in a few weeks for work so I need it unlocked.
I think I remember reading that the unlock code is located in the nv_data.bin file and can be found by searching the file with a hex editor. I'll have to read a little more and play around with that before I flash.
I have been reading a lot lately, but could not find an answer to my noob question. I was just wondering if I flash an I9000 based ROM and lose my unlock or my product code gets messed up, can I just copy the original nv_data.bin file to the new ROM or will that cause me other problems. I know there are post as to how to fix this, but they are geared toward people who didn't make a backup and copying original would be much easier and quicker. Thanks.
^^^ Any help with above question?
I also have one other question. I've been poking around with Root Explorer and I see that all the sytem apps are naturally stored in /system/app folder, but I don't see the downloaded apps in there. I see what apperar to be my downloaded apps in /data/app folder. Is this where they are stored and if so, can I just copy them out and then copy them back after I flash a new ROM? If so, is there anything else I have to do with them to make them work again (like chown through adb)? I was wondering this because I have some paid apps and I don't know if they will automatically be available for download again once I sign on to the market and I don't want to lose them. Thanks for any help.
This is useful if one of your phones has root but say you break that and you upgrade to a phone without root. OH MY GOODNESS! What are you going to do!? Luckily, you ran my scripts and now you have a cool backup of all of your phones apps from the /data/app folder. You can just load those onto your sd and BANG you just get it back to how it was before (the data isn't restored.) So all you have now is a phone like your old one that you can toy with until you get root. The reason I made these was because I was pulling the system folder and I included that one for dev's that just wanna poke around the system folder. It creates the dump originally on the C:\ drive then it creates C:\Android\systemdump\apps or C:\Android\systemimage (for the system script.) This worked flawlessly after taking me an hour to perfect the script and have all of it working. Just load it into the folder where ADB is and let it do the work. If someone wants to re-archive them and allow it to be in the same .zip as the adb and needed dll's go for it. I just don't know what files you need and I've done alot of work on this already. Time for instructions.
How to use: What you're going to need is probably root on your phone for starters. You will HAVE to put these 2 or just 1 of the scripts into the folder where you use ADB. It will ask you if you want to continue just hit any key to do it. This really does nothing to your phone, just unplugging it might corrupt a few things if it is still in mid pull. I am just wanting to contribute and I know simplicity is really well liked by android users and I thought I would do this for all the devs or powerusers. I know you think if you have titanium backup, you will be fine but you need root for that on the new phone that you didn't break so this is probably your best bet. Just load onto your sd card when needed and go from there. Happy to help guys and remember, hit the thanks button if you like this.
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like movies, music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files (the installed apks will be gone though, but no biggie if you backed up them with Titanium).
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Edit:
I have a p6210, no idea whether it works on other models or not. I guess it does but who knows...
Give it a try if you feel like it, but don't forget to make a back up before in case it goes wrong.
After flashing, your files won't be in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
unclefab said:
Most of the time when one flashes a new ROM one has to do a data wipe (factory reset), and it erases all one's personal files like music, pictures etc, quite annoying to say the least.
I found a way to avoid this, and it's pretty simple:
1-in CWM go to mount,
2-mount both data and system,
3-format them both.
This will perform the factory reset without erasing our precious files.
Then you can wipe cache + dalvik and flash your new ROM.
I used this method to go from ICS to CM 10.1, from CM 10.1 to Paranoid Android, and finally back to ICS, without loosing a single kb of my files.
Give it a try if you feel like it...
Click to expand...
Click to collapse
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Re: Easy way to keep one's personal data after flasing a new ROM
ALWAYS create a backup before erasing/flashing ANYTHING!! It's always as a precaution, to avoid losing something that you don't want to. And it only takes like 5 seconds literally. I lost some stuff when I unlocked the bootloader on my nexus10 by factory resetting, and I must say I didn't have a smile on my face. But it happened, u live n learn. I'm afraid if u wiped without making a nandroid backup your probably out of luck. Unless your skilled in using forensics techniques to try to recover it. Can't think of any options tho.
Sent from my SCH-I535 using xda app-developers app
Balaram12 said:
Not cool man.Fu** lah.I lost everything.Around 7 GB of files.Fu** lah.I have no backup.I thought it would work.I was going from cm10.1 to cm10.What am I going to do?
Click to expand...
Click to collapse
What did you do?
Did you follow the exact procedure?
I flashed again some roms today and it worked again.
But one thing is that the files are not in the mnt/sdcard anymore but in a newly created folder in mnt/sdcard/0, or, depending the rom you are using, in storage/sdcard/0.
Or, some roms may create a file called legacy and stock everything there, or sometimes your files may be stocked before the sdcard folder, search for either /0 or /legacy.
Use a root browser and have a look, your files are still in your device (have a look as well at your storage in general settings, it will show how many gbs are in your tab).
Once you have found your files all what you have to do is to move them back where they belong, ie the /sdcard folder, it takes 10 seconds.
This said, meishkov is right, one should allways have a back up in case anything goes wrong, I should have mentioned it in the OP but I forgot, my bad...
Edit:
OP edited.
Oh well, noone tried?
Would be nice to hear some reports...
Balaram, it would be fair from you to detail a bit what happened and to tell if you found back your files.
Anyway, this method worked for me and I thought that it might have interested some people here, roms flashers and devs alike, but if that s not the case then no worries.
If someone feels that I should erase the whole thread just tell me and I ll do it...
Hi together,
earlier I wanted to finally give the L-Preview a shot so I downloaded it and installed it as it was mentioned in the thread's instructions. Everything was fine until I was forced to reinstall it because Wifi kept getting stuck at switching (which didn't fix itself after a reboot) and some other things. So I did everything again like I did before but after I booted it up again and set up everything I noticed that in ES-File manager I couldn't access my sdcard directory. So I booted back into my recovery and saw that even there my usual sdcard directory was nearly gone except for a few folders (0, clockwordmod, legacy, obb and TWRP) which I couldn't see in ES-File explorer before. Because I was a little confused (and angry because I never had something like this happening) I just rebooted my device and connected it to my pc to see what I can access from there. But it was the same result like with the manager, there were no folders at all . So I went back into my recovery and just looked a bit around and after a while I found out that the whole /sdcard files just moved to the "0" folder that is inside the "old" sdcard-directory. And this is kind of where I am at right now not knowing what to do to get everything back to normal. I hope there is a way I can recover all of my files or at least a way that I can move them to my pc (had a few backups on there that I was too lazy to move which I do regret now...). If there is someone who understood my post and knows a solution to my problem please help me! I am actually quite lost right now because I can't even use Whatsapp without loosing all of my messages
I am sorry that I can't give you any pictures of my phones status but I don't know how I could do a screenshot/video in TWRP :/
Edit: I found an older device of myself with which I was able to take some pictures (has very bad quality because it has a little crack in the camera)
On InternerSpeicherSeite1 you can see that on my pc it shows that storage is used up but on InternerSpeicherSeite2 you can see that it is empty if I open it.
In ES you can see that there is this /legacy instead of /sdcard.
In TWRP1 you can see that the whole /scard directory is nearly empty.
In TWRP2 is the /sdcard direcory that is now in /sdcard/0 but unaccesable from anywhere except TWRP.
R4gi3X said:
Hi together,
earlier I wanted to finally give the L-Preview a shot so I downloaded it and installed it as it was mentioned in the thread's instructions. Everything was fine until I was forced to reinstall it because Wifi kept getting stuck at switching (which didn't fix itself after a reboot) and some other things. So I did everything again like I did before but after I booted it up again and set up everything I noticed that in ES-File manager I couldn't access my sdcard directory. So I booted back into my recovery and saw that even there my usual sdcard directory was nearly gone except for a few folders (0, clockwordmod, legacy, obb and TWRP) which I couldn't see in ES-File explorer before. Because I was a little confused (and angry because I never had something like this happening) I just rebooted my device and connected it to my pc to see what I can access from there. But it was the same result like with the manager, there were no folders at all . So I went back into my recovery and just looked a bit around and after a while I found out that the whole /sdcard files just moved to the "0" folder that is inside the "old" sdcard-directory. And this is kind of where I am at right now not knowing what to do to get everything back to normal. I hope there is a way I can recover all of my files or at least a way that I can move them to my pc (had a few backups on there that I was too lazy to move which I do regret now...). If there is someone who understood my post and knows a solution to my problem please help me! I am actually quite lost right now because I can't even use Whatsapp without loosing all of my messages
I am sorry that I can't give you any pictures of my phones status but I don't know how I could do a screenshot/video in TWRP :/
Click to expand...
Click to collapse
Move all your folders and files back to the old place, or get them to your pc with adb pull (use google if you want to now how) and flash the factory image for safety
You can learn to adb pull by clicking the link in my signature and then locating the adb and fastboot thread
Don't adb push your data back though. Adb pushing your entire sdcard back will cause permissions problems so use MTP to transfer data back
Sent from my Nexus 5 using Tapatalk
its a common issue with L, i even experienced it myself. first, there is a short terminal emulator command you can use. i dont know what it is, but a search should find it for you. itll move all back to where it should be. or secondly, you can do what i did. i didnt know there was a terminal command, so i used root explorer to move everything back manually. took me about 15-20 minutes.
GtrCraft said:
Move all your folders and files back to the old place, or get them to your pc with adb pull (use google if you want to now how) and flash the factory image for safety
Click to expand...
Click to collapse
rootSU said:
You can learn to adb pull by clicking the link in my signature and then locating the adb and fastboot thread
Don't adb push your data back though. Adb pushing your entire sdcard back will cause permissions problems so use MTP to transfer data back
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I already know how to adb pull but it just gives me the output seen on the picture...
there appears to be 3 different terminal emulator scripts people have been using, one for for some but not for others. heres one that i found, try it out in a terminal emulator app..
su(press enter)
restorecon -r /data/media/0/*(press enter)
simms22 said:
there appears to be 3 different terminal emulator scripts people have been using, one for for some but not for others. heres one that i found, try it out in a terminal emulator app..
su(press enter)
restorecon -r /data/media/0/*(press enter)
Click to expand...
Click to collapse
I've tried your command but it did nothing.
But I found a way simpler solution now, as I could still access my data in TWRP I was able to flash a 4.4.4 Rom (that I luckily still had on my phone^^) and now I can access everything including the "0" Folder on my pc again. So I'll move everything on my pc now and then copy it to the /sdcard directory
Thanks though for your help, really appreciate the support from the xda-community!!
But I gotta say good night now as it is already 1am but I will update this post one more time tomorrow giving a final result.
You already know /sdcard isn't working properly. Pull /data/media/0
I am not a big Android tech, but my work in IT teached me some basic knowledge.
But this thing I have leaves me blinded, and I haven't had this ever before on any phone (and wasn't an issue before either).
Whenever I install Lollipop at this point (Cataclysm mostly) Im facing issues with files.
A lot of them just dont show, not even the ROM file I just used.
Gallery (Photo in L) pictures untill a certain date cant be found, but are showing (with errors when opening), a Wallpaper folder just completely vanishes with L, files in Download folder..
What is this? Storage file change? Format? I dont get it.
And as soon as I flash back KitKat, all files are back.
I even deleted the faulty pictures in L, but are showing again in KK.
Is it the kernel I flash right after the Lollipop ROM?
Does L install in a different partition like thing? lol
Happily using KitKat (ART) btw, no L for me so no biggy.
But I am really really wondering, if I ever decide to go Lollipop.
Here you go man. This will explain it to you. If the terminal commands don't work for you, just move the files manually.
/sdcard problems after upgrading Android
Woody said:
Here you go man. This will explain it to you. If the terminal commands don't work for you, just move the files manually.
/sdcard problems after upgrading Android
Click to expand...
Click to collapse
Different file locations used in Lollipop obviously.
If I'd ever to switch to Lollipop and I wouldn't get an answer here, I'd completely wipe the internal storage and start from scratch again, pretty sure that would solve it.
But this might aswell do the trick..
Thanks.
I'll keep that thread saved somewhere.
justiiin said:
Different file locations used in Lollipop obviously.
If I'd ever to switch to Lollipop and I wouldn't get an answer here, I'd completely wipe the internal storage and start from scratch again, pretty sure that would solve it.
But this might aswell do the trick..
Thanks.
I'll keep that thread saved somewhere.
Click to expand...
Click to collapse
The file location is the same in KitKat and Lollipop. The reason it has issues is unknown right now.