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
Related
I think I may have successfully created my first nandroid but am unsure due to what I saw. To borrow from another dev thread to which I cannot post:
Installed - started backup, Got message: No/sdcard/.android_secure found. Skipping backup of applications on ext storage. Same thing happened with cache..
Maybe I'll uninstall.
---------- Post added at 04:48 PM ---------- Previous post was at 04:45 PM ----------
[/COLOR]
Originally Posted by bigfooot
the only thing I find is the progress bar does not progress.
but everything seems to work.
Also the time stamp is off.
I have the same issue
I have the following files in my clockwork backup folder:
cache.img
data.img
nandroid.md5
system.img
Am I missing anything?
Thanks,
looks right as to what i have seen man
Wonder if it has anything to do with apps i have on sdcard...
I'm greatly relieved if I have actually successfully created my first nandroid.
Now if i could only look at somebodies udev rules file for XT875, i could feel even safer having adb around. I dont think i'll load any roms without the adb safety net.
Sent from my DROID BIONIC using XDA App
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 my wifi isn't working and my phone wont activate (profile update failed errorcode is COMMS_SOCKET_ERROR) I have the sprint model and I just flashed stock with this method to try to fix but to no avail. Any ideas? I saw this in the moto g forums... maybe a similar fix for the moto x? I am running 4.4.2 btw.
Oh and I don't know the history on this device. I bought it used with an unlocked bootloader and philz installed with stock
blu422 said:
So my wifi isn't working and my phone wont activate (profile update failed errorcode is COMMS_SOCKET_ERROR) I have the sprint model and I just flashed stock with this method to try to fix but to no avail. Any ideas? I saw this in the moto g forums... maybe a similar fix for the moto x? I am running 4.4.2 btw.
Oh and I don't know the history on this device. I bought it used with an unlocked bootloader and philz installed with stock
Click to expand...
Click to collapse
It is, most likely, /persist. Search XDA from Google. I could up mine. It is only on the phone not the XML.
Here is persist, I think it is the same for all x variants. Backup your's first, in case you have hardware issues.
Permissions rwxrwx--x
aviwdoowks said:
Here is persist, I think it is the same for all x variants. Backup your's first, in case you have hardware issues.
Permissions rwxrwx--x
Click to expand...
Click to collapse
Will I have to edit the bin file and add my mac address first? if so could you suggest an editor for a bin file?
Actually, I'm not sure I know what I'm doing so just to make sure I dont screw things up could you walk me through what to do with the files you gave me? just copy them to said persist folder? when you say permissions rwxrwx--x what does that mean? sorry i just wanna make sure i do things right
blu422 said:
Will I have to edit the bin file and add my mac address first? if so could you suggest an editor for a bin file?
Actually, I'm not sure I know what I'm doing so just to make sure I dont screw things up could you walk me through what to do with the files you gave me? just copy them to said persist folder? when you say permissions rwxrwx--x what does that mean? sorry i just wanna make sure i do things right
Click to expand...
Click to collapse
Install http://forum.xda-developers.com/attachment.php?attachmentid=2696050&d=1397913555
go settings, general, access mode, choose root.
Save your current persist :
Press back all the way to root. Long press on persist, copy, paste to your SD.
Go download, long press on the zip file, extract, long press on xt1060persist, copy.
Paste it to your root dir. Overwrite.
Set perms: long press on persist, properties, permissions.....
Does that help?
aviwdoowks said:
Install http://forum.xda-developers.com/attachment.php?attachmentid=2696050&d=1397913555
go settings, general, access mode, choose root.
Save your current persist :
Press back all the way to root. Long press on persist, copy, paste to your SD.
Go download, long press on the zip file, extract, long press on xt1060persist, copy.
Paste it to your root dir. Overwrite.
Set perms: long press on persist, properties, permissions.....
Does that help?
Click to expand...
Click to collapse
Yeah that's what I was guessing but I was just making sure I didn't have to convert to IMG and fastboot flash. What about adding my Mac address? I don't think its a hardware problem because it can still detect signal just fine sometimes even 4g
It didn't work :/
blu422 said:
Yeah that's what I was guessing but I was just making sure I didn't have to convert to IMG and fastboot flash. What about adding my Mac address? I don't think its a hardware problem because it can still detect signal just fine sometimes even 4g
It didn't work :/
Click to expand...
Click to collapse
So RSD of your proper XML ( which would have renewed yout boot.img) & this did not fix then it may be a HW failure.
---------- Post added at 02:47 PM ---------- Previous post was at 02:43 PM ----------
blu422 said:
Yeah that's what I was guessing but I was just making sure I didn't have to convert to IMG and fastboot flash. What about adding my Mac address? I don't think its a hardware problem because it can still detect signal just fine sometimes even 4g
It didn't work :/
Click to expand...
Click to collapse
Wait Wait Wait
I forgot you need to set all perms in all folders & files
http://forum.xda-developers.com/showthread.php?t=2589790
These perms should be the same.
---------- Post added at 03:00 PM ---------- Previous post was at 02:47 PM ----------
aviwdoowks said:
So RSD of your proper XML ( which would have renewed yout boot.img) & this did not fix then it may be a HW failure.
---------- Post added at 02:47 PM ---------- Previous post was at 02:43 PM ----------
Wait Wait Wait
I forgot you need to set all perms in all folders & files
http://forum.xda-developers.com/showthread.php?t=2589790
These perms should be the same.
Click to expand...
Click to collapse
from my X:
.bt_... rw-rw----
data rwx------; & all contents same.
prov rwx------ same as above
usf empty
wcncc...nv.bin rw-rw----
...calibration_presist.bin rwxrwxrwx
...regulatory_presist.bin rwxrwxrwx
aviwdoowks said:
---------- Post added at 03:00 PM ---------- Previous post was at 02:47 PM ----------
[/COLOR]
from my X:
.bt_... rw-rw----
data rwx------; & all contents same.
prov rwx------ same as above
usf empty
wcncc...nv.bin rw-rw----
...calibration_presist.bin rwxrwxrwx
...regulatory_presist.bin rwxrwxrwx
Click to expand...
Click to collapse
when you say all contents same you mean in data and prov, both data and prov and all their folders inside and all the folder's folders and all the folders folders files all rwx------?
Thanks a ton for all this continued help
blu422 said:
when you say all contents same you mean in data and prov, both data and prov and all their folders inside and all the folder's folders and all the folders folders files all rwx------?
Thanks a ton for all this continued help
Click to expand...
Click to collapse
Yes
aviwdoowks said:
Yes
Click to expand...
Click to collapse
Okay I've done all that but still nothing... Do I need to replace your mac address from your file with my mac address? Or something?
blu422 said:
Okay I've done all that but still nothing... Do I need to replace your mac address from your file with my mac address? Or something?
Click to expand...
Click to collapse
I opened that zip and looked at WCNSS_qcom_wlan_nv.bin with a HEX editor.
I couldn't find a MAC address inside that file. Either I'm missing it, or its encrypted, or its not in there.
Any idea how this happened? Have you preformed any of the root or write protect exploits?
EDIT: Also checked the regulatory, calibration, and bt files. None of them appear to have a MAC address inside. Not even the bluetooth nv persist file.
samwathegreat said:
I opened that zip and looked at WCNSS_qcom_wlan_nv.bin with a HEX editor.
I couldn't find a MAC address inside that file. Either I'm missing it, or its encrypted, or its not in there.
Any idea how this happened? Have you preformed any of the root or write protect exploits?
EDIT: Also checked the regulatory, calibration, and bt files. None of them appear to have a MAC address inside. Not even the bluetooth nv persist file.
Click to expand...
Click to collapse
Thank you for all the time you've put into it. I suspected a mac address because they talk about it in the posts I linked to in the op. I don't know the history of the device I just got it on stock with an unlocked bootloader and I again flashed it to stock with RSD to try to eliminate these problems I dont think its the hard ware because it can sense cell reception just fine. Again thank you for your time.
samwathegreat said:
I opened that zip and looked at WCNSS_qcom_wlan_nv.bin with a HEX editor.
I couldn't find a MAC address inside that file. Either I'm missing it, or its encrypted, or its not in there.
Any idea how this happened? Have you preformed any of the root or write protect exploits?
EDIT: Also checked the regulatory, calibration, and bt files. None of them appear to have a MAC address inside. Not even the bluetooth nv persist file.
Click to expand...
Click to collapse
blu422 said:
Thank you for all the time you've put into it. I suspected a mac address because they talk about it in the posts I linked to in the op. I don't know the history of the device I just got it on stock with an unlocked bootloader and I again flashed it to stock with RSD to try to eliminate these problems I dont think its the hard ware because it can sense cell reception just fine. Again thank you for your time.
Click to expand...
Click to collapse
TiagoPeixoto said:
So, I got it working again. The problem was indeed in the persist folder, it was missing a file named WCNSS_qcom_wlan_factory_nv.bin. So I managed to extract it from the persist.img and moved it to persist folder again. After that I edited the bin file and inserted my MAC address. Finally I have flashed my phone to stock ROM again and it worked just fine.
Here's the file:
Click to expand...
Click to collapse
Like TiagoPeixoto said
aviwdoowks said:
Here is persist, I think it is the same for all x variants. Backup your's first, in case you have hardware issues.
Permissions rwxrwx--x
Click to expand...
Click to collapse
got the same issue. tried the files and permission. didn't work.
damn it.
any more help?
R3dbeaver said:
got the same issue. tried the files and permission. didn't work.
damn it.
any more help?
Click to expand...
Click to collapse
Did you see post 7?
aviwdoowks said:
Did you see post 7?
Click to expand...
Click to collapse
Yes and I made sure the permission is correct. Also, i got the wcn....nv.bin from the Moto G thread and it is an empty 70k file...
WiFi toggle still doesn't work.
R3dbeaver said:
Yes and I made sure the permission is correct. Also, i got the wcn....nv.bin from the Moto G thread and it is an empty 70k file...
WiFi toggle still doesn't work.
Click to expand...
Click to collapse
Does Philz recovery still let you choose a custom backup that includes persist?
You could, with the help of another unlocked X user, save your phone. Are you unlocked?
aviwdoowks said:
Does Philz recovery still let you choose a custom backup that includes persist?
You could, with the help of another unlocked X user, save your phone. Are you unlocked?
Click to expand...
Click to collapse
whaaa.... ok 90% of that just went over my head.
I use TWRP.... whats "Philz"?
Also, i dont have any recovery backup....
Unlocked? Rooted yes, unlocked I dont think so. It's a Rogers XT1058.
A mis matched boot & modem can also do the same
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
R3dbeaver said:
whaaa.... ok 90% of that just went over my head.
I use TWRP.... whats "Philz"?
Also, i dont have any recovery backup....
Unlocked? Rooted yes, unlocked I dont think so. It's a Rogers XT1058.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/fyi-online-nandroid-backup-ready-t2762382
Ok I'm unlocked and can install Philz. Anyone had a Moto X xt1058 copy me their /persist folder??
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!
I screwed up and backed up the wrong file.
Can anyone grab me libjni_latinimegoogle.so for me please.
Install the apk, then get it from /data, or just pull it out of the apk...
Sent from my Moto X
It isn't in the apk
Any help please?
Where it located in the phone?
Slapped my Moto
/system/lib
I may not have that file...I'm in the USA. I found libjni file..but mine doesn't say latinmegoogle.so
Slapped my Moto
Are you stock?
Rooted but yes
Slapped my Moto
Umm.. What does it say?
Everything urs says but take out google
Slapped my Moto
Hmm
Seems like a lot of time spent on this.
You could just flash your stock firmware... Same exact version, don't try to downgrade or you may brick.
http://forum.xda-developers.com/showthread.php?t=2603358
See "returning to stock" section in the guide.
Just don't do fastboot erase userdata. Though I'd backup all your stuff first just in case.
?
---------- Post added at 09:11 AM ---------- Previous post was at 09:10 AM ----------
Actually only flashing the system image should fix it.
I have a TWRP backup, just really didn't want to go that direction.
Why not? You've been over a week on this issue. You could be fixed in 5 minutes. ?
Yes, the backup would work. Just restore system and you should not lose anything. Texts maybe. Use sms backup for that. Have to restore some system settings maybe, but it won't take 8 days. ?
Because, if I don't want any loss, I have to free up a few gig for a backup.
But now that I'm thinking about it, Google keyboard wasn't on this phone as a stock keyboard and I should be able to revert with just deleting the new file that I put in there for the 4.0 keyboard
Then it should simply install from the play store.
And if it wasn't a system app, you don't have a titanium backup of it?
Grr. I guess it was a system app
You don't need free space to flash your firmware system image only. It'll just overwrite what's there and add anything missing. ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:55 AM ----------
With mfastboot I'm talking. And it won't touch your internal SD or data partitions.
---------- Post added at 09:56 AM ---------- Previous post was at 09:55 AM ----------
Only sms might be affected, but I can't remember.
But, if you want to back it up, you need to free up space