Im a long time xiaomi user and recently return to samsung device. Just asking, if i update my phone through odin will it wipe my internal storage? As i got the 1tb version and so many precious data in it, its such a hassle and will take more time to backup my data to pc as this device is my current daily driver.
Second question, if i back up my data to pc, and then after updating phone, i transfer back those file such as images to the phone, will it change the date of the image to a new transfer date(pc to phone transfer)? I dont wanna ruin my gallery because it will be sorted as the new transfer file date. Im sorry if i explained it wrong but i hope you get the image for what i really want to explain. Is there any software backup or restore the image to a original date or a file to a storage? thanks.
#1- NO. It wont wipe your data, but is highly recommended to wipe data after flahing odin, becausw if not it will probably mix the files. Give it a try.
---------- Post added at 08:50 AM ---------- Previous post was at 08:49 AM ----------
#2-NO, it will be exactly the same if you copy pasta the same fomder because the date is written in the photo archive. So dont worry. Use Smart Switch btw.
Related
old Droid 3 (5.6) broke... screen went dark= screen not back lite ( I can see see boot menu but not bptools font in blue)
some how I made a Nandroid backup by booting into bptools (showed actually backing up in white= visible) everything looked good except g5 sums no idea what that means
Rooted the new Droid 3 (5.7) with motofail
used the (5.6) Nandroid to restore everything. most everything was back to the old except I was missing things that were on the phone (not on SD card) like Bloat freezing folder for script manager, pictures. Rom folder for emulator.. etc...
I assumed the stuff was missing, maybe that's what the g5 sums was all about ( i dont know i couldnt really see much)
dragged missing **** over and everything is cool, EXCEPT MY GALLERY WONT SHOT MY PHOTOS not the ones i moved and not the ones I took with the phone to see where they go.
I can see them with astro file manager but the gallery just says offers two choices "wait" or "force close" iv'e waited and it doesn't do anything but let my phone over heat.
HELP PLEASE
That's probably because you restored 5.6.890 OVER 5.7.906. You slapped old over new and that's probably causing issues. Did you pull the info from the old phones internal 11 some gigabytes of memory? A nandroid wouldn't back up EITHER memory location (internal 11ish GB or removable sd card). Did you change the name of the nandroid backup to include spaces or characters? This can cause an MD5 mismatch. Use periods "." for spaces and only numbers and letters.
---------- Post added at 10:09 PM ---------- Previous post was at 09:55 PM ----------
kayelemenohpee said:
OHHH I gotcha INTERNAL SD card still dosnt get backed up... "i learned something new" =)
but by issues of components you mean.... my PHOTO GALLERY?!?!?!
What can I do to fix this problem.??? unroot and let the phone re update the latest 5.7 and then reROOT???
Click to expand...
Click to collapse
In my opinion, what you need to do is flash the 5.7.906 to 5.6.890 SBF (this is an incomplete SBF and will not revert all things like the bootloader, but it will flash /system to 5.6.890), then go to Settings > About Phone > Updates and get the 5.7.906 update again. Root this and DO NOT restore and old nandroid. Restore apps from the Play Store and then sync the phone from your Google account. Plug the old phone into the computer and try to view it's internal memory, then pull all of your info from the memory. You can then put folders like DCIM, downloads, playlists, etc. that contain items that wouldn't influence the system data of the phone, such as android_secure.
I accidentally messed up the root folder(/), which contains system, cache, data, lta-label etc folders
Now how can I make the whole root folder back to the original state?
To solve this, can I flash a firmware by Flashtool with "Exclude Partition" unticked?
Will every folder and file under the root folder come back to the original state?
By the way, can lta-label folder be deleted?
Thank you!
Can you elaborate on messing up the root folder? What exactly is messed up?
DevShaft said:
Can you elaborate on messing up the root folder? What exactly is messed up?
Click to expand...
Click to collapse
I wrongly created and moved some files and folders just under the Android root folder(/)(PS not sdcard root folder)
so now the root folder has been messed up and i want to make the whole root directory go back to factory state.
thanks
....cant you just delete them?
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
Just reflash using flashtool
flytomars said:
I wrongly created and moved some files and folders just under the Android root folder(/)(PS not sdcard root folder)
so now the root folder has been messed up and i want to make the whole root directory go back to factory state.
thanks
Click to expand...
Click to collapse
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
Michealtbh said:
Just reflash using flashtool
Click to expand...
Click to collapse
May not help in this case.
tangosierra_ said:
....cant you just delete them?
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
Click to expand...
Click to collapse
after a reboot the wrongly created files and folders disappear and i don't know where they have gone
i worry that they still exist but cannot be found
DevShaft said:
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
May not help in this case.
Click to expand...
Click to collapse
If flashing a FTF can clear every partition then it will help
DevShaft said:
Which folders are you referring to exactly?
---------- Post added at 04:51 PM ---------- Previous post was at 04:51 PM ----------
May not help in this case.
Click to expand...
Click to collapse
i wrongly copied TitaniumBackup folder just to the root folder
after a reboot it disappeared i don't know where it is
flytomars said:
If flashing a FTF can clear every partition then it will help
Click to expand...
Click to collapse
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
flytomars said:
i wrongly copied TitaniumBackup folder just to the root folder
after a reboot it disappeared i don't know where it is
Click to expand...
Click to collapse
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
DevShaft said:
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
Click to expand...
Click to collapse
what you said makes me stop worrying.
Besides TB folder I also wrongly copied some files just under the root folder.
I once worried that after a reboot they will not be deleted and just be hidden and be nowhere to be found so that they will permanently exist in a unknown place on my phone.
Now I know that they can be simply 'killed' by completely flashing a ftf.
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
DevShaft said:
Flashing a FTF can clear most partitions, but not everything like TA. So no 100% clean slade I'm afraid. However this can solve problems such as yours.
---------- Post added at 05:37 AM ---------- Previous post was at 05:26 AM ----------
I believe / is a ramdisk mounting everything together. This means that on every boot this ramdisk is recreated and all adjustments you made to / before will be gone. So your TB folder is actually nowhere, so nothing for you to worry about. It's like it was before you wrongly copied the folder. No need to flash an ftf, but if it makes you feel good .
Click to expand...
Click to collapse
:good:
flytomars said:
what you said makes me stop worrying.
Besides TB folder I also wrongly copied some files just under the root folder.
I once worried that after a reboot they will not be deleted and just be hidden and be nowhere to be found so that they will permanently exist in a unknown place on my phone.
Now I know that they can be simply 'killed' by completely flashing a ftf.
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
Click to expand...
Click to collapse
just reflash FTF or if you have custom rom reflash the rom in recovery...
G1_enthusiast said:
just reflash FTF or if you have custom rom reflash the rom in recovery...
Click to expand...
Click to collapse
flashing a custom rom won't format partitions so i think it's better to flash ftf
flytomars said:
flashing a custom rom won't format partitions so i think it's better to flash ftf
Click to expand...
Click to collapse
if you wipe system, data and cache it will...worth a try it takes 5 minute to know if it work..
G1_enthusiast said:
if you wipe system, data and cache it will...worth a try it takes 5 minute to know if it work..
Click to expand...
Click to collapse
i messed up the root folder /
not data, system etc which are under the root folder
flytomars said:
flashing a custom rom won't format partitions so i think it's better to flash ftf
Click to expand...
Click to collapse
Yes, only you don't have to because of the fact you wrote to ram, so nothing is messed up .
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
flytomars said:
So can I get a conclusion:
If the root folder is messed up, for example, saving files and folders under lta-lable folder or under any other folder in the root folder or just under the root folder(/), everything that shouldn't exist will be deleted and everything under the root folder will be back to the factory state by flashing the whole ftf.
Is this right?
Thank you!
Click to expand...
Click to collapse
No, that's not right .
When you write anything to / (not further down!), it will be gone like it never existed. This is because writing to / is actually to RAM. RAM is cleared on reboot.
So conclusion is, you don't have a messed up /, since it is restored after a reboot. This is only the case when you write directly to /. So not necessarily when you write to a folder called /foo or /bar. You don't have to do anything, since there is no mess and all is fine.
A RAM disk is an area in memory which is mounted as disk, as if it is disk space while it actually is RAM space which is cleared when the device reboots or shuts down. When the device boots it recreates this RAM disk and copies the necessary files and folders to it. It also mounts certain partitions under aliases like /system and /data. When the RAM disk is removed from memory - at a shutdown or reboot - it will only clear the files and folders copied to / and the aliases of the partitions mounted, not the content of the partitions themselves. So when you write to /system/ it will not be gone at next boot while something written to / directly will. I hope it makes a bit more sense now .
DevShaft said:
Yes, only you don't have to because of the fact you wrote to ram, so nothing is messed up .
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
No, that's not right .
When you write anything to / (not further down!), it will be gone like it never existed. This is because writing to / is actually to RAM. RAM is cleared on reboot.
So conclusion is, you don't have a messed up /, since it is restored after a reboot. This is only the case when you write directly to /. So not necessarily when you write to a folder called /foo or /bar. You don't have to do anything, since there is no mess and all is fine.
A RAM disk is an area in memory which is mounted as disk, as if it is disk space while it actually is RAM space which is cleared when the device reboots or shuts down. When the device boots it recreates this RAM disk and copies the necessary files and folders to it. It also mounts certain partitions under aliases like /system and /data. When the RAM disk is removed from memory - at a shutdown or reboot - it will only clear the files and folders copied to / and the aliases of the partitions mounted, not the content of the partitions themselves. So when you write to /system/ it will not be gone at next boot while something written to / directly will. I hope it makes a bit more sense now .
Click to expand...
Click to collapse
now i understand
and i did a test.
i created a folder and a file under / whose permissions were set the same as the permission of other files under /
after a reboot the created folder and file disappear
so i think what you said is undoubtly right
but if i write something further down then i have to flash a ftf because flashing a ftf can wipe every partition mounted under /
is this right?
thank you!
Most, not every. Partitions like TA cannot be wiped by flashing a ftf.
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
flytomars said:
but if i write something further down then i have to flash a ftf because flashing a ftf can wipe every partition mounted under /
is this right?
thank you!
Click to expand...
Click to collapse
As said not every partition, like the TA for instance. However in most cases flashing ftf will do.
So things were going well... I had rooted my S5 thanks to Geohot, was able to install and run Titanium Backup and see my old backups from my last phone. Then when I tried to backup my S5 I ran into the "insufficient space error". A quick Google searched revealed that I needed to edit my platform.xml file to be able to write to my entire External SD. So I did edit platform.xml, reboot the phone and voila.... I can't access either my internal or my external SD card! Far as I can tell, I screwed up my permission in platform.xml.
Can someone please send me their original so that I can hopefully get my phone fixed?
If that doesn't work I may just have to reformat and lose all my data since I can't find any other way to fix permission since I can't run most of the programs on my phone (I can, however, use Solid Explorer).
Where is the file located? And you need it from a non rooted phone? Just did this for another member today.... I suppose I could do this for you as well.... don't want you to lose all your data bro.
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
What I did with titanium Bu was use the sdfix https://play.google.com/store/apps/details?id=nextapp.sdfix and went into preferences in TBU and changed Backup Folder Location to /storage/extSdCard/TitaniumBackUp
This of course assuming you have a micro sd card in the phone. Give me the path to where the file is and I'll grab it for you from my wife's non rooted phone.
---------- Post added at 04:17 PM ---------- Previous post was at 04:00 PM ----------
Pm sent with the file from my rooted phone that has working permissions... good luck!
nicetucu said:
Where is the file located? And you need it from a non rooted phone? Just did this for another member today.... I suppose I could do this for you as well.... don't want you to lose all your data bro.
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
What I did with titanium Bu was use the sdfix https://play.google.com/store/apps/details?id=nextapp.sdfix and went into preferences in TBU and changed Backup Folder Location to /storage/extSdCard/TitaniumBackUp
This of course assuming you have a micro sd card in the phone. Give me the path to where the file is and I'll grab it for you from my wife's non rooted phone.
---------- Post added at 04:17 PM ---------- Previous post was at 04:00 PM ----------
Pm sent with the file from my rooted phone that has working permissions... good luck!
Click to expand...
Click to collapse
You're a life saver! The platform.xml file it located in /system/etc/permissions . As I said, I really hope this is all I need to get back to normal...
morockin said:
You're a life saver! The platform.xml file it located in /system/etc/permissions . As I said, I really hope this is all I need to get back to normal...
Click to expand...
Click to collapse
Thanks again for the file, however it does not seem to have done the trick. As far as I can tell, something is happening where the mapping is incorrect for my internal and external SD. I can still access the files for the internal SD through /data/media/0 and the external SD through the media_rw directory, but the "normal" mappings lead to an empty folder. This is a real problem because most of my apps can't run without access to these folders (I have about 6 apps continously FC'ing when I boot up the phone). What do I do?!?!
morockin said:
Thanks again for the file, however it does not seem to have done the trick. As far as I can tell, something is happening where the mapping is incorrect for my internal and external SD. I can still access the files for the internal SD through /data/media/0 and the external SD through the media_rw directory, but the "normal" mappings lead to an empty folder. This is a real problem because most of my apps can't run without access to these folders (I have about 6 apps continously FC'ing when I boot up the phone). What do I do?!?!
Click to expand...
Click to collapse
I had the same issue. First try a factory reset. If that does not work, then you will need to downgrade, with a factory reset. Just resetting the platform.xml file doesn't work without a factory reset, neither does a factory reset without resetting the platform.xml file. Once you screw up the permissions, then your phone is screwed pretty good. I have a guide in the general section.
shortydoggg said:
I had the same issue. First try a factory reset. If that does not work, then you will need to downgrade, with a factory reset. Just resetting the platform.xml file doesn't work without a factory reset, neither does a factory reset without resetting the platform.xml file. Once you screw up the permissions, then your phone is screwed pretty good. I have a guide in the general section.
Click to expand...
Click to collapse
Could you please direct me to it? I have f'ed my phone in a similar manner and would really like to be able to use it again.
Superfish1000 said:
Could you please direct me to it? I have f'ed my phone in a similar manner and would really like to be able to use it again.
Click to expand...
Click to collapse
Here
http://forum.xda-developers.com/showthread.php?t=2785185
I have a 32gb locked bootloader att moto x.
I've got it rooted on 4.4 with write protection off, and i've safestrapped a rooted 4.4.2 stock rom to it.
Recently I wanted to upgrade to 4.4.3 with the Krypton rom, so I was cleaning up my sdcard at the same time to get some more space. I guess I made a mistake somewhere along the line because shortly after deleting a couple files, my sdcard came up blank and I lost all my files. The thing is, my phone still shows up with about 15gb of used space, and I know that the rom and system files themselves can't take up that much space. Furthermore, if I go in the google play music app, it's able to play certain songs that were previously on my sdcard, despite it seeming empty to me.
Is it possible the files were relocated somewhere? Kind of like what happens when the sdcard files end up in an 'emulated' folder? (it's not the case here, at least not in /sdcard)
I appreciate your time and help!
frenchie007 said:
I have a 32gb locked bootloader att moto x.
I've got it rooted on 4.4 with write protection off, and i've safestrapped a rooted 4.4.2 stock rom to it.
Recently I wanted to upgrade to 4.4.3 with the Krypton rom, so I was cleaning up my sdcard at the same time to get some more space. I guess I made a mistake somewhere along the line because shortly after deleting a couple files, my sdcard came up blank and I lost all my files. The thing is, my phone still shows up with about 15gb of used space, and I know that the rom and system files themselves can't take up that much space. Furthermore, if I go in the google play music app, it's able to play certain songs that were previously on my sdcard, despite it seeming empty to me.
Is it possible the files were relocated somewhere? Kind of like what happens when the sdcard files end up in an 'emulated' folder? (it's not the case here, at least not in /sdcard)
I appreciate your time and help!
Click to expand...
Click to collapse
Look for a folder called LOST.DIR in the emulated storage.
There are chances that your lost files are present there.This usually happens when you mount the SD card as opposed to connecting it to a PC vai MTP mode.
Do post your findings!
Bhargav4591 said:
Look for a folder called LOST.DIR in the emulated storage.
There are chances that your lost files are present there.This usually happens when you mount the SD card as opposed to connecting it to a PC vai MTP mode.
Do post your findings!
Click to expand...
Click to collapse
Unfortunately it was really wiped clean. It was done via MTP mode. Nothing other than the android folder and download folder, which were both empty.
What I don't understand is what kind of file on my sdcard could have erased all others when deleted? Could it be safestrap related? I'm quite certain the cable was nicely plugged in and didn't move.
And why is some of my music still present? :/
Pretty sure you're flash was corrupt.
I would flash 4.4 again with fastboot and as long as you don't erase anything with fast boot.... I bet all you're files turn back up.
I'm not sure what special steps, if any you need to take with safestrap and that.... But refreshing stock will likely fix it.
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
Of course you'll need to do the whole root and safestrap stuff again after.
---------- Post added at 12:29 PM ---------- Previous post was at 12:19 PM ----------
Here is a guide with a return to stock section. In fact, since you are on 4.4....correct? You could flash 4.2.2 post camera update... Not pre camera.... Cause I think you need that version to root again....
http://forum.xda-developers.com/showthread.php?t=2603358
Basically whatever you did to root and safestrap, you need to do again.
KJ said:
Pretty sure you're flash was corrupt.
I would flash 4.4 again with fastboot and as long as you don't erase anything with fast boot.... I bet all you're files turn back up.
I'm not sure what special steps, if any you need to take with safestrap and that.... But refreshing stock will likely fix it.
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
Of course you'll need to do the whole root and safestrap stuff again after.
---------- Post added at 12:29 PM ---------- Previous post was at 12:19 PM ----------
Here is a guide with a return to stock section. In fact, since you are on 4.4....correct? You could flash 4.2.2 post camera update... Not pre camera.... Cause I think you need that version to root again....
http://forum.xda-developers.com/showthread.php?t=2603358
Basically whatever you did to root and safestrap, you need to do again.
Click to expand...
Click to collapse
The thing is, I've been running this rom just fine for at least 2 months now... And I've connected it to my pc using MTP in the past and it worked without a problem, so I don't see what would be causing one now. That being said I may RSD back to post camera just to make sure, who knows maybe it will fix this. I'll probably do that tomorrow and I'll be sure to post my results. In the meantime if anyone has a less time-consuming method feel free to let me know! haha
Won't hurt to try. ?
Just a follow up: I wiped data via safestrap recovery and installed Krypton. Works fine and now my storage shows about 3 gigs of used space, so my sdcard files are lost for good. How it happened is still a mystery! All I can say is be careful what files you delete from your sdcards!
Any ideas on how to get One Touch Nav feature on the Android One device? Maybe someone can post the Moto APK or port it over to the Android One device.
Edit: Someone figured this out. imgur . com/a/lL1ZO#nsbPp4p
This don't work for me, I'm on 8.1 looking for a fix.
Kevinreid1 said:
This don't work for me, I'm on 8.1 looking for a fix.
Click to expand...
Click to collapse
I fastboot flashed 8.1 and lost the one button nav from my 8.0. What I ended up doing was flashing back to 8.0, enabling the one button nav using nova launcher or QuickShortCutMaker, then OTA updated all the way to July security patch. As long as you don't wipe data, or factory reset, you won't lose the one button nav.
I have however been trying to figure out where it is stored in data so I can just save the files to my external SD and in the event I wipe data or factory reset, I can just drop the files back where they need to be and reboot. (So if anyone knows where these are stored, please help. It's not in root\data\data\com.motorola.actions like one would think. There is also a symlink in there on the lib folder to root\data\app\com.motorola.actions................ , but wiping out both of those folders does not wipe out the one button navigation that I have.)
If you go the downgrade route then OTA back up to current, as long as you are rooted, you can back up your userdata (data) partition so you can just restore if needed. Just be sure to remove any security before doing the backup otherwise the partition will be encrypted and likely give you grief when restoring. Once the backup is complete, you can reboot, and set up your password, pin, fingerprint etc again.
Hope this helps.
---------- Post added at 04:47 PM ---------- Previous post was at 04:42 PM ----------
If I could find the correct files and knew how to package them up as an APK, I would post it on the forums for others to install.