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.
Related
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??
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!
Recently @Captain_Throwback made a custom TWRP image. My 626s is very broken. I don't even have a system image. I really need someone to install the recovery and backup their system image and send me a link so i can fix my 626s.
Link to TWRP:https://basketbuild.com/devs/Captain_Throwback/Desire 626s/Recovery/TWRP
Will do this as soon as I get home and I'll post a link for you.
Bad news this TWRP build like my unreleased builds have the same issue the stock kernel disables the digitizer when booted to the Recovery partition. Good News HTC finally released the Kernel Source so we can fix this issue. I probably wont be able to work on this since I am currently now working 55 hours a week for the next two months and have very little free time on my hands
Never mind it works i'm just really tired
Can't backupvup system.IMG cause it won't mount external SD card or otg cable with a flash drive
EDIT: wiped data and internal storage to create enough space on internal sd. will post a link for twrp backup and a system.img as well
Piplup702 said:
Can't backupvup system.IMG cause it won't mount external SD card or otg cable with a flash drive
EDIT: wiped data and internal storage to create enough space on internal sd. will post a link for twrp backup and a system.img as well
Click to expand...
Click to collapse
Thanks - This is what I needed to know. I'm sure I can fix this in the recovery kernel. I'll rebuild it later today. Since I don't have the device, it's a bit . . . challenging.
Piplup702 said:
Can't backupvup system.IMG cause it won't mount external SD card or otg cable with a flash drive
EDIT: wiped data and internal storage to create enough space on internal sd. will post a link for twrp backup and a system.img as well
Click to expand...
Click to collapse
Please try the updated TWRP I posted at the same location as indicated in the OP. External SD *should* be accessible now. If not (or even if it is), if you could do Advanced -> Copy Log to SD and then upload that log for me, I'd greatly appreciate it .
Captain_Throwback said:
Please try the updated TWRP I posted at the same location as indicated in the OP. External SD *should* be accessible now. If not (or even if it is), if you could do Advanced -> Copy Log to SD and then upload that log for me, I'd greatly appreciate it .
Click to expand...
Click to collapse
it mounts external and internal and shows up on pc. the first one didnt. heres my recovery log.
dropbox. com/s/yl45s4y463m6fxp/recovery%5B1%5D.log?dl=0
itz me ry4n said:
it mounts external and internal and shows up on pc. the first one didnt. i did copy log to sd but its just a TWRPS file
Click to expand...
Click to collapse
Yes, I need a copy of the log that copied to SD. Please upload that recovery log.
Captain_Throwback said:
Yes, I need a copy of the log that copied to SD. Please upload that recovery log.
Click to expand...
Click to collapse
i found it. updated my pervious post
https://drive.google.com/folderview?id=0B_T4Zb3ybDQ7OWx3NWV3c28yQkU&usp=sharing
heres a link for twrp backup for the people who bricked. The one named 2015-11-12--02-41-03_LMY47O_release-keys is the regular backup, the other one is a system.img backup
Piplup702 said:
https://drive.google.com/folderview?id=0B_T4Zb3ybDQ7OWx3NWV3c28yQkU&usp=sharing
heres a link for twrp backup for the people who bricked. The one named 2015-11-12--02-41-03_LMY47O_release-keys is the regular backup, the other one is a system.img backup
Click to expand...
Click to collapse
will this work on the metro pcs phone?
itz me ry4n said:
will this work on the metro pcs phone?
Click to expand...
Click to collapse
Yes, it's a backup of my metro pcs desire 626s.
Piplup702 said:
Yes, it's a backup of my metro pcs desire 626s.
Click to expand...
Click to collapse
ok thanks. im flashing it now and will update when it is dont if it worked or not.
---------- Post added at 07:51 PM ---------- Previous post was at 07:23 PM ----------
itz me ry4n said:
ok thanks. im flashing it now and will update when it is dont if it worked or not.
Click to expand...
Click to collapse
its done but doesnt boot. just goes to the bootloader menu. i may need the boot.img file for it. if u could get that for me please.
---------- Post added at 08:01 PM ---------- Previous post was at 07:51 PM ----------
itz me ry4n said:
ok thanks. im flashing it now and will update when it is dont if it worked or not.
---------- Post added at 07:51 PM ---------- Previous post was at 07:23 PM ----------
its done but doesnt boot. just goes to the bootloader menu. i may need the boot.img file for it. if u could get that for me please.
Click to expand...
Click to collapse
yea the boot.img was the problem i found one and flashed it and now the phones is booting and android is starting.
itz me ry4n said:
ok thanks. im flashing it now and will update when it is dont if it worked or not.
---------- Post added at 07:51 PM ---------- Previous post was at 07:23 PM ----------
its done but doesnt boot. just goes to the bootloader menu. i may need the boot.img file for it. if u could get that for me please.
---------- Post added at 08:01 PM ---------- Previous post was at 07:51 PM ----------
yea the boot.img was the problem i found one and flashed it and now the phones is booting and android is starting.
Click to expand...
Click to collapse
There's a boot.IMG in my Google drive
https://drive.google.com/folder/d/0B_T4Zb3ybDQ7dEFJUEZxbzZTOEU/edit
Piplup702 said:
https://drive.google.com/folderview?id=0B_T4Zb3ybDQ7OWx3NWV3c28yQkU&usp=sharing
heres a link for twrp backup for the people who bricked. The one named 2015-11-12--02-41-03_LMY47O_release-keys is the regular backup, the other one is a system.img backup
Click to expand...
Click to collapse
Thank you so much downloading now but 2.5GB takes a little while. Will report back if it works
gingrbred said:
Thank you so much downloading now but 2.5GB takes a little while. Will report back if it works
Click to expand...
Click to collapse
Bad news. When I try to restore in twrp I get this error.
Code:
E:extractTarFork() process ended with ERROR=255
gingrbred said:
Bad news. When I try to restore in twrp I get this error.
Code:
E:extractTarFork() process ended with ERROR=255
Click to expand...
Click to collapse
Need the full log.
Captain_Throwback said:
Need the full log.
Click to expand...
Click to collapse
View attachment 3540274
Here you go
gingrbred said:
View attachment 3540274
Here you go
Click to expand...
Click to collapse
This log won't open for me.
View attachment recovery.log
Captain_Throwback said:
This log won't open for me.
Click to expand...
Click to collapse
this is a log from when i got the restore to work but the phone still wont boot
Can anyone help me? I have a moto G7+ running Android 10 with TWRP and root. It's working fine... I mean almost, I noticed that since Moto pushed another update for it, it downloads itself and takes up space on storage. It started with 13GB, now it's taking 25GB of system files. I can't find the folder to delete these files even with root. I tried wiping Dalvik Art Cache, it did nothing. Is there anyway to perform this without having to reset the whole phone? Thanks in advanced. I used Mixolorer to try to find the page and TWRP to wipe cache. Also there's no cache option in it, that's why I went with Dalvik.
Nhyphk said:
Can anyone help me? I have a moto G7+ running Android 10 with TWRP and root. It's working fine... I mean almost, I noticed that since Moto pushed another update for it, it downloads itself and takes up space on storage. It started with 13GB, now it's taking 25GB of system files. I can't find the folder to delete these files even with root. I tried wiping Dalvik Art Cache, it did nothing. Is there anyway to perform this without having to reset the whole phone? Thanks in advanced. I used Mixolorer to try to find the page and TWRP to wipe cache. Also there's no cache option in it, that's why I went with Dalvik.
Click to expand...
Click to collapse
It's a A/B device and there is no /cache on it.
The update file for an A/B device isn't stored on your device. It will be installed directly from Motorola's server.
Open a fileexplorer in search inside /data for the file or open a terminal command and type
Code:
du -m /data | sort -g
This command shows all sizes in MB.
WoKoschekk said:
It's a A/B device and there is no /cache on it.
The update file for an A/B device isn't stored on your device. It will be installed directly from Motorola's server.
Open a fileexplorer in search inside /data for the file or open a terminal command and type
Code:
du -m /data | sort -g
This command shows all sizes in MB.
Click to expand...
Click to collapse
Ok, if it's not stored in my device what's taking up so much space on "system"?
Nhyphk said:
Ok, if it's not stored in my device what's taking up so much space on "system"?
Click to expand...
Click to collapse
"System" are ALL system related partitions like /vendor, /system and so on. It doesn't matter which files are stored there. The size of each partition remains the same.
---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------
You can delete all files within /system, but /system is still 3GB.
---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------
Only single files on /data are important because that is your internal storage. You only use /data. If you delete files on /system then /data won't get more free storage.
WoKoschekk said:
It's a A/B device and there is no /cache on it.
The update file for an A/B device isn't stored on your device. It will be installed directly from Motorola's server.
Open a fileexplorer in search inside /data for the file or open a terminal command and type
Code:
du -m /data | sort -g
This command shows all sizes in MB.
Click to expand...
Click to collapse
WoKoschekk said:
"System" are ALL system related partitions like /vendor, /system and so on. It doesn't matter which files are stored there. The size of each partition remains the same.
---------- Post added at 12:39 AM ---------- Previous post was at 12:38 AM ----------
You can delete all files within /system, but /system is still 3GB.
---------- Post added at 12:45 AM ---------- Previous post was at 12:39 AM ----------
Only single files on /data are important because that is your internal storage. You only use /data. If you delete files on /system then /data won't get more free storage.
Click to expand...
Click to collapse
I got what you meant, but in my case something is taking up space on my internal memory and it's going to system. It's now on 27GB, yesterday it was 26gb, in March when I updated to Android 10, it was only about 10gb, and when I check data to see some files, there's nothing there to delete, that's what I'm asking.
Nhyphk said:
I got what you meant, but in my case something is taking up space on my internal memory and it's going to system. It's now on 27GB, yesterday it was 26gb, in March when I updated to Android 10, it was only about 10gb, and when I check data to see some files, there's nothing there to delete, that's what I'm asking.
Click to expand...
Click to collapse
Did u run the command obove? All you can do is to search for the file (or what ever it is).
Maybe a file explorer like FX would help you to find it. It shows you the usage of every directory you choose, always beginning with the greatest file/folder on top.
I'm sure it is only one special file/folder that causes your problem, so this method seems to be the best for you.
Example: /data/system/user/0/big_file.dat is what you are searching for, then you will find it by selecting "data". FX shows you that there is a very big file somewhere in "system" and like this you go further and further until you find "big_file.dat" .
WoKoschekk said:
Did u run the command obove? All you can do is to search for the file (or what ever it is).
Maybe a file explorer like FX would help you to find it. It shows you the usage of every directory you choose, always beginning with the greatest file/folder on top.
I'm sure it is only one special file/folder that causes your problem, so this method seems to be the best for you.
Example: /data/system/user/0/big_file.dat is what you are searching for, then you will find it by selecting "data". FX shows you that there is a very big file somewhere in "system" and like this you go further and further until you find "big_file.dat" .
Click to expand...
Click to collapse
Thanks for the tip, when I get to data and choose a folder, they all say access denied, even with root allowed. There must be something wrong with this freaking phone. Thanks anyways.
Anyone out there. I still need freaking help. I thought with the app I found, system storage would stop growing, but it hit 32GB of simply nothing. I've removed everything from the phone, moved vids, pictures. The folder says it's files needed to make android work, but why is it growing?
Nhyphk said:
The folder says it's files needed to make android work, but why is it growing?
Click to expand...
Click to collapse
Which folder told you that?
WoKoschekk said:
Which folder told you that?
Click to expand...
Click to collapse
System in Storage
Nhyphk said:
System in Storage
Click to expand...
Click to collapse
You should take a root fileexplorer... It's somewhere in /data, except /data/media
---------- Post added at 01:40 AM ---------- Previous post was at 01:33 AM ----------
You can also exclude
/data/app
/data/data
/data/user
/data/user_de
WoKoschekk said:
Which folder told you that?
Click to expand...
Click to collapse
WoKoschekk said:
You should take a root fileexplorer... It's somewhere in /data, except /data/media
---------- Post added at 01:40 AM ---------- Previous post was at 01:33 AM ----------
You can also exclude
/data/app
/data/data
/data/user
/data/user_de
Click to expand...
Click to collapse
This is the folder, there are so many things inside it. If I delete data/app, won't my apps restart? I'll have to login again, because banks apps won't work without authorization...
Nhyphk said:
This is the folder, there are so many things inside it. If I delete data/app, won't my apps restart? I'll have to login again, because banks apps won't work without authorization...
Click to expand...
Click to collapse
The file(s) you are searching for is/are stored in /data. You can EXCLUDE the following paths from your search:
/data/app/*
/data/data/*
/data/media/*
/data/user/*
/data/user_de/*
Do not search in above mentioned paths and do not delete them or something else!!!
---------- Post added at 04:43 AM ---------- Previous post was at 04:34 AM ----------
I don't know why it took so much time for you to find the problem. Open /data and get the size for each folder, one after another. First folder should be 'adb'. What is the size of this folder? Is it less than 20GB then go to the next one. The next one is called 'app' and should exclude it so take the next one. And so on and so on...
You have a maximum of 20 folders. This should take approx. 5-10 min. and your problem is solved!
---------- Post added at 05:12 AM ---------- Previous post was at 04:43 AM ----------
or open any terminal app and type
Code:
su
du -akd 1 /data | sort -n
in the last line of your output you find the folder with the highest size.
Thank you very much for your help and I'm sorry for bothering. I'm really not an expert on these things. I think the actual file is so hidden not even root will show it. The biggest folder in data is exactly apps. First I thought you said I could delete them, thank God I only deleted user_de and when the phone restarted, I only had to confirm my account and 2.5GB were cleared off memory. Then I did what you told me to and you can see what it says in the picture, biggest folders are app and data. Since I can't delete data/app, I think it's another file, or even more than one that are hidden. Or my phone is just buggy. Last resort is resetting it... Anyways, thanks again.
Nhyphk said:
Thank you very much for your help and I'm sorry for bothering. I'm really not an expert on these things. I think the actual file is so hidden not even root will show it. The biggest folder in data is exactly apps. First I thought you said I could delete them, thank God I only deleted user_de and when the phone restarted, I only had to confirm my account and 2.5GB were cleared off memory. Then I did what you told me to and you can see what it says in the picture, biggest folders are app and data. Since I can't delete data/app, I think it's another file, or even more than one that are hidden. Or my phone is just buggy. Last resort is resetting it... Anyways, thanks again.
Click to expand...
Click to collapse
Please have a look at /data/app. 25GB are too much for this path. Usually it contains less than 10GB.
Expand the command this way:
Code:
du -akd 1 /data[B]/app[/B] | sort -n
WoKoschekk said:
Please have a look at /data/app. 25GB are too much for this path. Usually it contains less than 10GB.
Expand the command this way:
Code:
du -akd 1 /data[B]/app[/B] | sort -n
Click to expand...
Click to collapse
Those are the biggest ones, but they're games (like pogo, Mario and HP) and they take about 2.5gb separately on Storage. I think musically is tik-tok, because that was its name before, I barely use it, it says 1.9GB, right? But the app itself says less than 300Mb. Also Google Port Camera looks huge and google quicksearchbox (is it the app or the widget?) and gms... Correct me if I'm wrong. Sorry once again.
Nhyphk said:
Those are the biggest ones, but they're games (like pogo, Mario and HP) and they take about 2.5gb separately on Storage. I think musically is tik-tok, because that was its name before, I barely use it, it says 1.9GB, right? But the app itself says less than 300Mb. Also Google Port Camera looks huge and google quicksearchbox (is it the app or the widget?) and gms... Correct me if I'm wrong. Sorry once again.
Click to expand...
Click to collapse
Numbers on the left side are sizes in KiB (Kibibyte).
1 KiB = 1024 Byte (binary, 2^10)
1 kB = 1000 Byte (decimal, 10^3)
/data/app/com.google.android.gms (Play Services) = 296.880 KiB = 289,92 MiB = 304,01 MB
All folders shown on your screenshot (YouTube - Play Services) are together almost exactly 4GB! But the total sum of '/data/app' is 25,79GB
What about the remaining 22GB??? The folders above 'YouTube' getting smaller and smaller. To get a total sum of 22GB you need hundreds of folders!
My advice: Do a factory reset! I don't know what it is, but your device (or storage) is really messed up.
WoKoschekk said:
Numbers on the left side are sizes in KiB (Kibibyte).
1 KiB = 1024 Byte (binary, 2^10)
1 kB = 1000 Byte (decimal, 10^3)
/data/app/com.google.android.gms (Play Services) = 296.880 KiB = 289,92 MiB = 304,01 MB
All folders shown on your screenshot (YouTube - Play Services) are together almost exactly 4GB! But the total sum of '/data/app' is 25,79GB
What about the remaining 22GB??? The folders above 'YouTube' getting smaller and smaller. To get a total sum of 22GB you need hundreds of folders!
My advice: Do a factory reset! I don't know what it is, but your device (or storage) is really messed up.
Click to expand...
Click to collapse
Thank you. I thought so, think it's actually the freaking update... I'll do it in some days, remove root and install a newer version of Android 10 from Motorola, then root it again. But thank you very much. God bless you.