Please!! This is normal on internal storage of SGS3? 'system data' - Galaxy S III Q&A, Help & Troubleshooting

I just installed a new rom formatting my phone, including the internal memory. It is normal to have a hidden folder called System Data? And this increase and decrease weight by installing or uninstalling apps??
I just see this with a playstore app called DiskUsage, because in Windows Explorer don't show this folder...this is very Annoying because Each time I have less storage space for each installed application ... is a bug in my phone only?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-I9300 using xda app-developers app

Factory reset and remove all apps .
Install no apps ever again and you have plenty of space .
jje

Hello,
This is pretty normal.
The internal storage is not only the "storage" you can see in windows explorer when you connect your phone, but also of the following:
Code:
ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx root root 2013-04-09 16:26 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-04-09 16:26 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-04-09 16:26 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-04-09 16:26 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-04-09 16:26 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-04-09 16:26 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-04-09 16:26 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-04-09 16:26 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-04-09 16:26 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-04-09 16:26 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-04-09 16:26 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-04-09 16:26 USERDATA -> /dev/block/mmcblk0p12
That means, that all of them are filling the internal storage.
And according to mount:
Code:
....
/dev/block/mmcblk0p12 /data ext4 ...
....
Every single App and Cache are located there, too.

JJEgan said:
Factory reset and remove all apps .
Install no apps ever again and you have plenty of space .
jje
Click to expand...
Click to collapse
That means it's normal? So always turn to fill that space to install applications?
Sent from my GT-I9300 using xda app-developers app

whitepaw said:
Hello,
This is pretty normal.
The internal storage is not only the "storage" you can see in windows explorer when you connect your phone, but also of the following:
Code:
ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx root root 2013-04-09 16:26 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-04-09 16:26 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-04-09 16:26 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-04-09 16:26 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-04-09 16:26 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-04-09 16:26 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-04-09 16:26 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-04-09 16:26 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-04-09 16:26 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-04-09 16:26 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-04-09 16:26 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-04-09 16:26 USERDATA -> /dev/block/mmcblk0p12
That means, that all of them are filling the internal storage.
And according to mount:
Code:
....
/dev/block/mmcblk0p12 /data ext4 ...
....
Every single App and Cache are located there, too.
Click to expand...
Click to collapse
So is normal xD thanks for your explain, There are ways to reduce the weight of that folder or partition? I have at most 20 applications installed and I think it exaggerated the size of this.
Sent from my GT-I9300 using xda app-developers app

someone can answer me please?

I'm not sure what exactly "System Data" is collecting.
On my phone System Data is 3GB (might be some zombie files in there which aren't used anymore).
It definitly is caused by apps you install.
The "System Data" part is not one explicit folder as far as I understand, but the collection of multiple folders.
Have you installed an android 4.2 ROM?
If yes:
I had a problem where my storage was nearly filled completly and I was not able to find where the data is.
I noticed, that after installing the 4.2 Leak, the MTP Mountpoint was moved to another folder inside the "normal" storage partition cause of the "emulated" multiuser support. (I don't have my phone connected right now, so the foldersmight be wrong) As far as I remember, the original /storage/sdcard was moved to /mnt/shell/legacy (which contained my previous sdcard files and a folder called "0") and the new /storage/emulated/legacy and /storage/emulated/0 (first and only user for mobilephone android 4.2) where linked to that folder "0".
That means the rest of the files in /mnt/shell/legacy where "hidden" and I was not able to find them via windows explorer and some android storage tools. After I moved the files from /mnt/shell/legacy to /mnt/shell/legacy/0/old via adb, I was able to detect them correctly and remove unwanted files for cleanup. However I'm not quiet sure if that folder counts, cause it is not part of /data.I tend to say, that it does not count.
If <4.2 or if the above is not the case:
I think 1GB isn't much. I might be wrong and maybe it's a good idea that someone else can share the "System Data" size of their diskusage result. I myself might not be digging deep enough into android filesystem management, but it depends on what "System Data" is showing. if it's really showing every little system data, then it contains the apps, the configurations, the databases, the recovery, the rom (which alone is around 500MB), the sounds, the wallpapers...etc.
I think it also depends on the device what data is shown here, you can't compare the result of your device with for example a HTC Device cause it might have a complete difference partition and mount table.
The best idea might be to connect the phone to the Computer, start an adb shell and get root (I hope your phone is rooted) by typing:
Code:
su
You might need to allow that on the phones screen.
Now type:
Code:
df -h
This will tell you which mountpoint takes how much space.
Example of another device:
/dev/block/mmcblk0p12 3.0G 958.2M 2.1G 31% /data
I'm not sure about the output on android, but it should show the mountpoint (a folder without /dev)
If you can only see something with "/dev" it's not the mountpoint but the device itself. You can find the according mountpoint by typing "mount".
Maybe you can find your 1GB here.
Change into each directory you want to check (type: "cd /data" for example) for the size and execute:
Code:
du -sh *
and you will get a list of each folder and file in there including it's size (not only the folder size (which will be displayed with "ls -la" to 4KB (cause the folder itself isn't big), but also the files within that folder).
Now go on and dig deeper and deeper until you find the big files.
That's the best way in my opinion to "hunt" down big files.
If that does not help you, then maybe you can post the result of "df -h" and "mount" here.

whitepaw said:
I'm not sure what exactly "System Data" is collecting.
On my phone System Data is 3GB (might be some zombie files in there which aren't used anymore).
It definitly is caused by apps you install.
The "System Data" part is not one explicit folder as far as I understand, but the collection of multiple folders.
Have you installed an android 4.2 ROM?
If yes:
I had a problem where my storage was nearly filled completly and I was not able to find where the data is.
I noticed, that after installing the 4.2 Leak, the MTP Mountpoint was moved to another folder inside the "normal" storage partition cause of the "emulated" multiuser support. (I don't have my phone connected right now, so the foldersmight be wrong) As far as I remember, the original /storage/sdcard was moved to /mnt/shell/legacy (which contained my previous sdcard files and a folder called "0") and the new /storage/emulated/legacy and /storage/emulated/0 (first and only user for mobilephone android 4.2) where linked to that folder "0".
That means the rest of the files in /mnt/shell/legacy where "hidden" and I was not able to find them via windows explorer and some android storage tools. After I moved the files from /mnt/shell/legacy to /mnt/shell/legacy/0/old via adb, I was able to detect them correctly and remove unwanted files for cleanup. However I'm not quiet sure if that folder counts, cause it is not part of /data.I tend to say, that it does not count.
If <4.2 or if the above is not the case:
I think 1GB isn't much. I might be wrong and maybe it's a good idea that someone else can share the "System Data" size of their diskusage result. I myself might not be digging deep enough into android filesystem management, but it depends on what "System Data" is showing. if it's really showing every little system data, then it contains the apps, the configurations, the databases, the recovery, the rom (which alone is around 500MB), the sounds, the wallpapers...etc.
I think it also depends on the device what data is shown here, you can't compare the result of your device with for example a HTC Device cause it might have a complete difference partition and mount table.
The best idea might be to connect the phone to the Computer, start an adb shell and get root (I hope your phone is rooted) by typing:
Code:
su
You might need to allow that on the phones screen.
Now type:
Code:
df -h
This will tell you which mountpoint takes how much space.
Example of another device:
/dev/block/mmcblk0p12 3.0G 958.2M 2.1G 31% /data
I'm not sure about the output on android, but it should show the mountpoint (a folder without /dev)
If you can only see something with "/dev" it's not the mountpoint but the device itself. You can find the according mountpoint by typing "mount".
Maybe you can find your 1GB here.
Change into each directory you want to check (type: "cd /data" for example) for the size and execute:
Code:
du -sh *
and you will get a list of each folder and file in there including it's size (not only the folder size (which will be displayed with "ls -la" to 4KB (cause the folder itself isn't big), but also the files within that folder).
Now go on and dig deeper and deeper until you find the big files.
That's the best way in my opinion to "hunt" down big files.
If that does not help you, then maybe you can post the result of "df -h" and "mount" here.
Click to expand...
Click to collapse
You are the best! simply the best!! thanks for your support!, i install a new rom (Based on android 4.1), making a'' full'' factory wipe, the system data folder space was reduced to approximately 500MB, here I leave the command catches you explained, (i never update my phone to android 4.2)
Then, you also have this folder or partition? (as comets, would be nice if someone could pass a screenshot of System Data folder space with DiskUsage)

Never touched it, a hundred apps installed. Using _null Rom.

Striatum_bdr said:
Never touched it, a hundred apps installed. Using _null Rom.
Click to expand...
Click to collapse
Thanks! but, the directory is different, in the application DiskUsage, if I use the first option at first (sd card space) the size of the System Data folder is very small, but if you use the path /storage/sdcard0 (with root) is where this System Data folder that greatly increases its size...
could you post a screenshot of your / storage/sdcard0 please?

Any? Please, upload a screenshot of your phone in DiskUsage ^^/
Sent from my GT-I9300 using xda app-developers app

Do not bump a thread before 24 hours has passed. Next time I will report you.
Why does this even matter? There are hidden partitions. Oh well. Use your phone and move on with life.

b-eock said:
Do not bump a thread before 24 hours has passed. Next time I will report you.
Why does this even matter? There are hidden partitions. Oh well. Use your phone and move on with life.
Click to expand...
Click to collapse
24hs after, bump... any?

Bumps mean that no one is interested.
Actually you're right, but you're wrong.
Size is not the same (much bigger in the second case) but you're wrong (the folder didn't increase, as the free disk space is the same).
It just means you're not seeing the same thing. And you can't do anything for that, as it's part of jelly bean filesystem design.
You can try to play a little with terminal emulator to understand why.

I would like to bring this back up. All my pictures, Titanium Backups, etc are on this internal card, but I cannot find them. I flashed a ROM and did a factory reset, but for some reason it only backed up some old files in the 0 folder in my internal storage. That folder was actually one level down from the root-below the card's default storage spot, so not sure how it happened. When the OS loaded up and I saw everything was gone, I had a tiny heart attack. Couldn't find it with Solid Explorer, but saw that there was only 3GB of space left on the internal card, and this was a clean flash with literally no apps installed or data on the internal storage card. I knew my data must be somewhere on it! I installed Disk Usage and sure enough, there was a huge amount of data in a System folder. Can anyone help figure out how to access this data? I know the stuff is there, just not sure how to get to it.

Read the sdcard on 4.2 link in my signature
Sent from my GT-I9300 using Tapatalk 2

rootSU said:
Read the sdcard on 4.2 link in my signature
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'm sorry, but I don't see how this applies for me? I don't have the 0 folder now, there's nothing in the data/media folder, & all my data is in some hidden System folder, where I cannot access it via file manager. It's like some blocked off partition. Do you have some way I can find/get into that data?

you need to read it once again. your data is in /data/media

Glebun said:
you need to read it once again. your data is in /data/media
Click to expand...
Click to collapse
You are right...I had accidentally denied Solid Explorer root privileges earlier, and didn't realize it wasn't going into the root folder, I am in there now, thank you so much!
Quick question, once I get my stuff out of there, can I delete that folder without causing any system harm?

tlogank said:
You are right...I had accidentally denied Solid Explorer root privileges earlier, and didn't realize it wasn't going into the root folder, I am in there now, thank you so much!
Quick question, once I get my stuff out of there, can I delete that folder without causing any system harm?
Click to expand...
Click to collapse
no, you can't. your internal SD right now is /data/media/0, so deleting /data/media will delete the sdcard. you can remove the contents, but don't touch the 0 folder

Related

Impossible to update xperia s after using prerooted 4.1

Hello,
I used the condi's flasher to get jelly bean a long time ago.
Now I wanted to have the last update from sony (R3 it seems) however the tablet says that there is no new updates (which is false). I have noticed that for my version number (or something like that, last info on the tablet ) I have "UNKNOWN (FR)".
Can you help me to update it?
Thanks
griotte said:
Hello,
I used the condi's flasher to get jelly bean a long time ago.
Now I wanted to have the last update from sony (R3 it seems) however the tablet says that there is no new updates (which is false). I have noticed that for my version number (or something like that, last info on the tablet ) I have "UNKNOWN (FR)".
Can you help me to update it?
Thanks
Click to expand...
Click to collapse
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Thanks for your help bg_man, I will try and update the post is everything is OK.
:good:
bg_man said:
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Click to expand...
Click to collapse
Hi,
In fact I have a strange situation :
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
I don't have this symlink. How can I create it?
Thanks
bg_man said:
Download the latest version R3 for your region from:
http://forum.xda-developers.com/showthread.php?t=1687429
Copy the update to the root of the external SD card.
Now become the tricky part. To update successfully you will need to create some symlinks.
If this sounds like chinese to you, stop right here.
Use jappaj guide (I don't remember the correct post):
"
So, in order to create this symlink:
- Connect your Xperia to computer
- Start Command Prompt
- Start shell by typing in command "adb shell" (you need Xperia drivers installed and adb.exe from somewhere!)
- Then request root priviledges by typing in "su" - you should get prompt to your Xperia device which you need to accept
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
- Then you need to create this symlink to OTHER system partition if it is missing. To do this you need to figure out what partition is currently mount as /system, type in "mount |grep -i /system", mine:
/dev/block/mmcblk0p3 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
There are two partitions which contains system, /dev/block/mmcblk0p3 and /dev/block/mmcblk0p4. One is currently mounted and used, I refer this as CURRENT and another is unused, I refer this as OTHER. My CURRENT is /dev/block/mmcblk0p3 and OTHER will then be /dev/block/mmcblk0p4. Yours may be reversed.
- So create folder for OTHER system partition, type in "mkdir /data/local/tmp/sysother"
- Them mount OTHER to that folder, type in "mount -t ext4 /dev/block/mmcblk0pX /data/local/tmp/sysother" where X is of course correct number for OTHER
- Go to folder to which OTHER was mounted, type in "cd vendor
"
- Check what you have, type in "ls -l"
- Do you have vendor folder or symlink? I think flasher will create folder (first letter is d) while out-of-the-box we have symlink (first letter is l). At least I had symlink in CURRENT when I got my Xperia back from service. Some kind soul who has not used flasher could check this for us, what do you have in CUR*RENT and OTHER, please! If you do not have vendor folder or symlink, trying to flash OTA from recovery will fail (at least it fails for me)!
- If you do not have anything, just create symlink, type in "ln -s /datapp/vendor/vendor1/FI vendor". Copy region code from symlink within CURRENT partition, mine is FI as Finland, yours will depend on your region! Also use vendor0 for mmcblk0p3 and vendor1 for mmcblk0p4 (other words use vendor0 if your CURRENT had vendor1 and vice versa)!
- Shut down, reboot to recovery and try to flash JB.
"
Then boot to recovery and flash the R3:
"
Volume + (hold it down forever) press power ... when you turn it loose screen when sony logo appears (this is fast) press again and holding down ... if you've done well ... sony logo disappears and leaves as distorted, loose then you press power and repeatedly! Now you should see the recovery menu
"
Click to expand...
Click to collapse
griotte said:
Hi,
In fact I have a strange situation :
- Check vendor symlink from CURRENT system partition by typing in "ls -l /system", ie. mine:
lrwxrwxrwx root root 2013-05-03 23:54 vendor -> /datapp/vendor/vendor0/FI
I don't have this symlink. How can I create it?
Thanks
Click to expand...
Click to collapse
You have a directory or a symlink to other folder instead?
Delete it and create symlink to right folder. "FI" stands for Finland. Put a correct one for your location.
Symlinks are remover with "rm", dir with "rmdir". I'd rename if it's a directory, rather remove it.
bg_man said:
You have a directory or a symlink to other folder instead?
Delete it and create symlink to right folder. "FI" stands for Finland. Put a correct one for your location.
Symlinks are remover with "rm", dir with "rmdir". I'd rename if it's a directory, rather remove it.
Click to expand...
Click to collapse
Yes that the point. The symlink is on the OTHER partition.
Thank you for your help, can you help me for the instructions? Especially the symlink is in read-only mode.
griotte said:
Yes that the point. The symlink is on the OTHER partition.
Thank you for your help, can you help me for the instructions? Especially the symlink is in read-only mode.
Click to expand...
Click to collapse
You have to mount system R/W:
/data/local/tmp/busybox mount -o rw,remount /system
Hi,
i have the same problem than Griotte.
Isn't it possible to flash directly the last firmware (downloaded on the SD card ) by using the condy "all in one" ?
In fact i just want to update because i have the Sony sound dock SGP-SPK1, everything work except that the sound don't pass from the tablet to the dock... great Sony !
So i suppose that maybe if i update the tablet, the dock will work...
Sorry for my English and thanks for your help

[Q] New phone can not boot! after titanium backup. Help

Hi.
Thanks to everyone who might give me some help.
I have a new quad-core phone with android 4.2.1, that is now useless. It can not boot, it freeze at second bootlogo, before animation.
It is rooted, and i have made some changes to build.prop. It worked fine, but after some time i realized the gallery and camera app was gone.
Then i did following:
Installed updated standard gallery+camera apk found online, both in the same app. from here http://forum.xda-developers.com/showthread.php?t=2341080
Works great, but i wanted to make it a system app, so did that with titanium backup.
After that, the camera app is gone. Gallery app is still working.
So i tried to change it back to user app, again with titanium, but did not stop working. After some time i took out the battery.
Now it freeze before boot animation.
I tried "wipe data/factory reset" and "wipe cache partition", in system recovery but still not booting!
I tried to backup user data from another phone, same model, and restore on this one but says "Error: checksum compare fail".
Do i need to flash a new rom to the phone with my pc? I have not tried this before, and i want to keep stock rom.
I have read this page:
http://www.chargeforums.com/forum/d...-flashing-roms-return-stock-odin-picture.html
But i can not get it in download mode, with those hotkeys?
If it is to any help, i have acces to other working phones of the same model.
Flashing new? It's look like this. How? I don't know because I have no information over ur phone.
Gesendet von meinem Xperia SP
joke19 said:
Flashing new? It's look like this. How? I don't know because I have no information over ur phone.
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
Its a noname phone imported from China.
The model is called A999M or Android Grand 1.
I can go in system recovery with volume up + power. But not helping. The only other boot menu i can acces, is only sometimes with volume down + power, i will get a menu but all en chinese.
I managed to get the bad build.prop file from the phone with adb, and see the error in it. But i can not get write acces to change/replace the file.
I compared the build.prop i modified on crashed phone, with working phone and the difference is following all changed to a OEM name (with Capial first letter, that gives problems):
ro.product.name=hexing89_we_jb2
ro.product.device=hexing89_we_jb2
ro.product.board=hexing89_we_jb2
ro.build.product=hexing89_we_jb2
"adb root" returns "adbd cannot run as root in production builds" and all other options like remount for r/w acces gives "remount failed: Operation not permitted"
The phone was rooted with framaroot:
http://forum.xda-developers.com/showthread.php?t=2130276
Would be very glad for some help. If you have the answer to fix it, i might even pay a little for your time.
So adb connects right?
Try this
adb shell
ls -l /dev/block/partitions
And from here keep searching and try to find by name (we are looking for system partition here)
If you can't find it from a shell try
cat /proc/partitions
Or just simply
Mount
If you find system then run this
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
Or whatever path to /system is
Then
You can simply push or use dd commands to push new build.prop and then chmod permissions to 644
Let me know what comes of this, as I know nothing about your phone but it sounds very fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So adb connects right?
Try this
adb shell
ls -l /dev/block/partitions
And from here keep searching and try to find by name (we are looking for system partition here)
If you can't find it from a shell try
cat /proc/partitions
Or just simply
Mount
If you find system then run this
adb shell
su
mount -o rw,remount /dev/block/mtdblock3 /system
Or whatever path to /system is
Then
You can simply push or use dd commands to push new build.prop and then chmod permissions to 644
Let me know what comes of this, as I know nothing about your phone but it sounds very fixable
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
I can not do that. First i already found the build.prop file. I can simply put "adb shell", and "cd /system", and "ls -all", and then i see the build.prop file.
I can also go youre way and do "mount -o rw,remount /dev/block/mmcblk0p5 /system", but it says "mount: Operation not permitted"
Remember i can not do adb root. I get "adbd cannot run as root in production builds".
I can also not do "su" inside adb shell. Everytime i do, prompt freezes. I think my phone is suposed to prompt me for Su acces, but shows nothing but the boot logo.
So for now, the problem is i have only read acces. No write acces.
Were not looking to list everything in system partition, rather trying to fin the block, I just wrote some random block that I'm sure is not yours unless you have some old mtd phone
In other words don't ls /system but rather /dev/block..... Until you find the block or use cat or mount or whatever to find it so you know what to mount
Also can you get to recovery and use adb there? If so I would recommend this as your system is already goofed up
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Were not looking to list everything in system partition, rather trying to fin the block, I just wrote some random block that I'm sure is not yours unless you have some old mtd phone
In other words don't ls /system but rather /dev/block..... Until you find the block or use cat or mount or whatever to find it so you know what to mount
Also can you get to recovery and use adb there? If so I would recommend this as your system is already goofed up
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi.
If i just write "mount" i get:
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
If i just write "ls -all" i get:
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 01:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 01:00 [email protected] -> /dev/block/mmcblk0p7
I hope i got the info you wanted. What should i write next?
Well we know its ext4 file system but we still don't have the block location
Try
ls -l -a /dev/block/platform
And see what you get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Not near a PC so just ran a terminal emulator so I can show you what we hope to find
If you have a by-name directory you're golden, if not we will keep looking
(Hit __ twice by accident in screen shot)
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Well we know its ext4 file system but we still don't have the block location
Try
ls -l -a /dev/block/platform
And see what you get
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Inside "block" i get:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk1
mmcblk1p1
platform
vold
Inside "platform" i get:
mtk-msdc.0
mtk-msdc.1
Inside "mtk-msdc.0" i get:
by-num
mmcblk0 -> /dev/block/mmcblk0
mmcblk0boot0 -> /dev/block/mmcblk0boot0
mmcblk0boot1 -> /dev/block/mmcblk0boot1
mmcblk0p1 -> /dev/block/mmcblk0p1
mmcblk0p2 -> /dev/block/mmcblk0p2
mmcblk0p3 -> /dev/block/mmcblk0p3
mmcblk0p4 -> /dev/block/mmcblk0p4
mmcblk0p5 -> /dev/block/mmcblk0p5
mmcblk0p6 -> /dev/block/mmcblk0p6
mmcblk0p7 -> /dev/block/mmcblk0p7
mmcblk0p8 -> /dev/block/mmcblk0p8
Inside "mtk-msdc.1" i get:
by-num
mmcblk1 -> /dev/block/mmcblk1
mmcblk1p1 -> /dev/block/mmcblk1p1
Sorry I'm blind, your mount showed /system is being called android, so you need to change the mount command from earlier to mmcblk0p5 from mtd....
Also did you try running adb from recovery mode?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Sorry I'm blind, your mount showed /system is being called android, so you need to change the mount command from earlier to mmcblk0p5 from mtd....
Also did you try running adb from recovery mode?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried:
[email protected]:/ $ mount -o rw,remount /dev/block/mmcblk0p5 /system
mount -o rw,remount /dev/block/mmcblk0p5 /system
mount: Operation not permitted
I think its because i can not do "su". Its just stops when i write it, and waiting on an empty line.
In system recovery i tried "wipe data/factory reset" and "wipe cache partition". But it does not help, since it will not recover system files like build.prop that is faulty. I also tried to "apply update" from zip and adb with the correct build.prop. But it can not apply it.
What recovery do you have? Stock? Custom?
Have you tried adb through recovery?
After you hit su does the prompt change from $ to # ?
Actually if you copy and paste all input/output from cmd/terminal when you try them out it is easier to help fix
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
What recovery do you have? Stock? Custom?
Have you tried adb through recovery?
After you hit su does the prompt change from $ to # ?
Actually if you copy and paste all input/output from cmd/terminal when you try them out it is easier to help fix
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe its just stock recovery. When im in recovery menu, i can not connect with adb.
C:\Users\Dennis>adb shell
[email protected]:/ $ su
su
-waiting on this empty line-
Mmm.... Does the oem have a website, often if you can find it there will be stock firmware/software with instructions on how to flash it. Like through fastboot or some download mode (maybe that Chinese writing screen - try getting a photo of it and see if someone will be nice and translate it for you)
Often there is some flash suite for these no-name devices like rockchips have as well as some well known OEMS
But without root access and no oem software this may be more difficult than I hoped, check around a bit and let me know what you find
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Mmm.... Does the oem have a website, often if you can find it there will be stock firmware/software with instructions on how to flash it. Like through fastboot or some download mode (maybe that Chinese writing screen - try getting a photo of it and see if someone will be nice and translate it for you)
Often there is some flash suite for these no-name devices like rockchips have as well as some well known OEMS
But without root access and no oem software this may be more difficult than I hoped, check around a bit and let me know what you find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay thank you. Im thinking if its possible to take a nandroid backup from a working phone (my girlfriend have one too), and recover on this one. But dont know if i can recover without root acces?
No worries, does your recovery have a nandroid backup and install function? If so then this would be ideal! The other option maybe to use dd commands to take her system.img and restore to yours through dd, but to me this is always a last resort as dd didn't get/the nickname disk destroyer for nothing! (_although it is safe so long as you don't mistype)
But start by looking for oem software and a flash mode if your recovery doesn't have backup restore options
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
No worries, does your recovery have a nandroid backup and install function? If so then this would be ideal! The other option maybe to use dd commands to take her system.img and restore to yours through dd, but to me this is always a last resort as dd didn't get/the nickname disk destroyer for nothing! (_although it is safe so long as you don't mistype)
But start by looking for oem software and a flash mode if your recovery doesn't have backup restore options
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There is no oem software, i have to work it out myself. The stock recovery only have options to backup and restore "user date". Not the system. But still i already tried to restore a backup from another phone, but get checksum error. I tried a few workaround for this, but didnt help.
I think i need to learn how to do a full nandroid copy. But i just hoped it was possible to just copy the one file i need, and not everything.
...if its just data partition then this won't help. The only ways I know how to do a nandroid is with a custom recovery (you don't have)
Adb http://forum.xda-developers.com/showthread.php?t=1021625
But as you can see requires root
Some apps - you have no os
Utilities like android commander or droid explorer -_ need root
So this leaves dd commands, but maybe keep digging for stock website or getting someone to translate that screen for you (may be what you're after)
Best of luck!
Sent from my Nexus 7 using XDA Premium 4 mobile app

[Q] Android L, external_SD no permissions, mounted

Running BarePOP rom, a lollipop, Android 5
My external sdcard is using ext4 filesystem, in BarRin rom I had no issues.
I think is a fuse problem, I've tried to unmount and remount card
I can access /mnt/media_rw/external_SD
I see it's mounted properly
Code:
/dev/block/vold/179:65 /mnt/media_rw/external_SD ext4 rw,dirsync,seclabel,relatime,data=ordered 0 0
/dev/fuse /storage/external_SD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I've tried messing with sdcard command. changed uid & gid to 1015,1023,1035
SDCARD_RW 1015 /* external storage write access */
MEDIA_RW 1023 /* internal media storage write access */
SDCARD_ALL 1035 /* access all users external storage */
Code:
[1]+ sdcard /mnt/media_rw/external_SD /storage/external_SD 1023 1023 &
tmp-mksh-4.3# ls -la /storage/
drwx------ root root 1970-01-18 21:43 USBstorage1
drwx------ root root 1970-01-18 21:43 USBstorage2
drwx------ root root 1970-01-18 21:43 USBstorage3
drwx------ root root 1970-01-18 21:43 USBstorage4
drwx------ root root 1970-01-18 21:43 USBstorage5
drwx------ root root 1970-01-18 21:43 USBstorage6
dr-xr-xr-x root root 1970-01-18 21:43 emulated
lstat '/storage//external_SD' failed: Permission denied
lrwxrwxrwx root root 1970-01-18 21:43 sdcard0 -> /storage/emulated/legacy
I'm surprised your sd even worked! We've all had to format on a computer fat32. No matter the size.
If you're on V1, install the sd card fix in the first 3 posts. Any other version it's already installed.
Selinux mode changer, also mentioned in those posts, is another option.
If neither of those work, then you may have corrupted one or both sd's.
engine95 said:
I'm surprised your sd even worked! We've all had to format on a computer fat32. No matter the size.
If you're on V1, install the sd card fix in the first 3 posts. Any other version it's already installed.
Selinux mode changer, also mentioned in those posts, is another option.
If neither of those work, then you may have corrupted one or both sd's.
Click to expand...
Click to collapse
Version TEv1, and if I didn't know to look at /mnt/media_rw/external_SD I would say it didn't work. /storage/external_SD only can be seen in terminal. All other apps don't even see it. Even root doesn't have permission to read. SElinux set to permissive. I'm wondering if it's a kernel issue. The mount looks correct. I really don't know.
Just connected to computer, sdcard show but not accessable
jcfunk said:
Just connected to computer, sdcard show but not accessable
Click to expand...
Click to collapse
Well, this is your answer. If the card doesn't work in two different devices, it is defective.
stopeject said:
Well, this is your answer. If the card doesn't work in two different devices, it is defective.
Click to expand...
Click to collapse
Lol, I connected usb to phone, mtp
sdcard is fine, if to blame the card it would be that it's formatted to ext4.
jcfunk said:
Lol, I connected usb to phone, mtp
sdcard is fine, if to blame the card it would be that it's formatted to ext4.
Click to expand...
Click to collapse
Sorry, I didn't notice that your card was formatted to ext4. However, when connected to a Windows PC you had to get a message that the card needs formatting. It shouldn't be identified as "not accessible".
stopeject said:
Sorry, I didn't notice that your card was formatted to ext4. However, when connected to a Windows PC you had to get a message that the card needs formatting. It shouldn't be identified as "not accessible".
Click to expand...
Click to collapse
Yes, so true, windows sucks. I use linux.
I binded /mnt/media_rw/external_SD to /data/media/0/sd-ext
Same thing, fuse issue. I thinking it might be selinux lable issue,
ls -Z shows unlabled. Going to look into labling, googled but didn't see any info on android
Ok, compiled stock kernel with configured with selinux user disable. Also boot disable, but if disabled at boot get security warring.
Selinux, no labels was the issue. Once diabled, the /storage/external_SD became readable
I am not familiar with a fair amount of what I've read in this thread (particularly the Linux commands and the mount points). That said, I'm in bliss pop ROM, and tried to get my podcast app o save my shows to external SD. No go. I got a toast that said android doesn't have permission to write to ext SD. Is anything listed here a fix for that?
TIA
scottspa74 said:
I am not familiar with a fair amount of what I've read in this thread (particularly the Linux commands and the mount points). That said, I'm in bliss pop ROM, and tried to get my podcast app o save my shows to external SD. No go. I got a toast that said android doesn't have permission to write to ext SD. Is anything listed here a fix for that?
TIA
Click to expand...
Click to collapse
Much of this is specific to ext4 filesystem on external sd. But is useful to understand, for the mount should be same, or at less for ex-fat.
I'm willing to help, I need some info.
What filedystem does your card have?
If you can, in terminal emulator run this command.
mount | grep SD
Then put output here. Could need to sdcard fix, depends on version of Barepop

SD Card permissions trouble

This thing has been a thorn in modding my phone ever since I rooted it - root has no read access to sdcard0 at all.
Whenever the external sdcard is mounted, root can only access sdcard1 after adding media_rw group to android.permission.WRITE_EXTERNAL_STORAGE, which works OK most of the times but there are some apps that rely on working with an external sdcard and root together unfortunately. Whenever the external sdcard is unmounted, same things happen with it - no access as root whatsoever. (user has full access)
Something of particular interest is the output of ls -l:
Code:
[email protected]_M3:/storage $ ls -l
drwxrwx--x root sdcard_r 1970-01-01 01:00 sdcard0
drwxrwx--x root sdcard_r 2015-08-10 02:48 sdcard1
[email protected]_M3:/storage $ su
[email protected]_M3:/storage # ls -l
drwx------ root root 2015-08-10 02:47 sdcard0
drwxrwx--x root sdcard_r 2015-08-10 02:48 sdcard1
[email protected]_M3:/storage #
and I don't really know where to begin to fix it. The stock ROM is doomed from the start with this it seems...
For the record; I'm using SuperSU and I have tried formatting my (2GB) sdcard to FAT32 and it didn't work.
Just restore the file tonoriginal data and use an app to do this.
Foldermount will work best.
Try this with thd help of this app ypu can read both sd cards at same time and keep game heavy data on sdcard as well
Sent from my SM-G355H using XDA Free mobile app
lolwhat file are you even talking about? Nothing has been touched there and that output of ls -l shows the permissions aren't as they're supposed to be for root.
FolderMount isn't exactly the thing I'm looking for. I need to fix permissions for root's access to the sdcard0 folder, plain and simple. For instance - I can't install Viper4Android because of this (though oddly I did manage to do it earlier, some black magic I did and don't remember lol). It wouldn't bother me if the sdcard folder in the ramdisk wasn't linked to the sdcard0 folder or if the permissions weren't tampered with and they were it seems.
I feel like as if I would have an easier time porting Cyanogenmod to my device than figuring this out...

Full backup over WiFi or Ethernet for X96 and maybe others

Ever wanted to backup your device without the hassle of flipping SD cards or USB sticks?
Maybe there is no TWRP recovery available for your device but you still want to make a backup?
Why not use the computer directly over your network?
All you need is a rooted device, might work without root but I never tried.
I always disliked that TWRP does not include user data in a backup.
And at some stage I got sick and tired of botting into recovery and flipping SD cards, so I tried this:
Connect a USB cable to the box and use ADB to make a backup.
As you guessed it the box does not really support this
No fastboot either
Then I remembered that ADB works over the network too and to my surprise the box agreed to let me use it.
As said I only test on my X96 but the same should work on most if not all Amlogic boxes.
Please see this as a work in progress as I would like to encourage more people to use this way of making backups.
It could also be a very easy way to provide modded firmwares as there is no need for a custom recovery.
Simply create your firmware and then make a backup, if you want even with all userdate included - just make sure to remove account, network and other personal settings first
I think you know hat I mean
But how exactly do we make use of this now?
Download the supplied archive and unpack to a folder on your PC - I named it tools so we have a reference here..
I have a fully working SDK, Java and all on my system but assume the tools should work as standalone versions too.
Start your box and check your IP in the network settings - you need it.
Open a command prompt with Admin rights in the Tools folder.
Now type adb connect YOURIP where YOURIP is the IP address of the box.
For example adb connect 192.168.1.9
The deamon will start and connect to your box, you can confirm by typing adb devices.
It will show the IP as a connected device.
Now, of course we could use some weird commands and type them into our command prompt...
I suggest to simply type backup and press enter
This will start the batch file that creates images of the following partitions:
Boot
Bootloader
Recovery
System
After this it will create a folder "sdcard" in the Tools folder and copy your userdata from the internal memory there.
The backup is complete now.
I inlcuded another batch file (backup_all) which tries to create images of all accessible partitions that I find on the OTA firmware.
Here the loop and mmcblk partitions are excluded as I assume there should be no real need for them.
With this you have full backup to restore a messed up device assuming the mount points and partitions were not changed by your modded rom.
The last (backup_all_full) includes all available partitions and some might not be fully accessible, so only try if you must and have enough space on your drive.
Again, not all partitions might work, try at your own discretion.
If you only want to backup and restore the userdate then please use the userbackup and restore files.
Restore:
I only included a restore.bat to write the following partitions:
Boot
Bootloader
Recovery
System
Plus the created userdata.
This will only work if the rom you tried out did not change vital parts of the system layout.
For example if the device tree blob, partition sizes, mount points were not changed from the original.
As long as you use roms designed for your device it will always get you back and running.
Of course you need to be able to get an IP connection through ADB - if that no longer works you have to flash the original firmware with the Amlogic tools.
The backup of the internal memory can laways be copied back to a working device.
What to expect from all this?
Nothing really! It is a simple creation with no additional checks, you could say "quick and dirty".
It should work for all X96 models that run the OTA firmware or one of my mods.
For other devices you might have to change the partition names in the batch files.
In my case they are found in /dev/block/, so a simple ls /dev/block from the ADB shell will give you these names.
IMHO the real benefit apart from having a complete backup directly on the computer is for people without a TWRP recovery.
Not only can you get all you need to port one but you can also modify your system by using the image files in a ROM kitchen (or do it manually).
If you like the idea then please check your system and try it out!
Upload or post your modifications to the batch files together with the device name and type so other can benefit too.
Let me know how it works!
Edit:
Changed the batch files a bit to get the best possible speed and added Testdisk for those who want to check the created image files.
All batch files starting with X96 are the current ones, the old ones are still included for reference.
Download the backup tools here.
Hello man, quite an interesting tool you've developed!! Lemme bother you with an issue I'm having please
I have the x96, a newer version, I suppose, than the one you have. Its running on Android 7.1. I'm trying to backup using your method, thing is, when I type backup in the console, after successfully connecting through adb to my box, I get the message "Simple ADB backup for the X96 by Downunder35m" , no logs in the console nor nothing(its been like that for half an hour). Am I doing something wrong there? adb devices echoes my device correctly. The device in stake is normally powered on, not in recovery mode, should it be on recovery mode?? should I be seeing logs in the console? what is the usual approximate time it should take? I know it depends on the local network speed and all, but It'd be cool to have an estimate...
Thanks!!!
ismasasoel said:
Hello man, quite an interesting tool you've developed!! Lemme bother you with an issue I'm having please
I have the x96, a newer version, I suppose, than the one you have. Its running on Android 7.1. I'm trying to backup using your method, thing is, when I type backup in the console, after successfully connecting through adb to my box, I get the message "Simple ADB backup for the X96 by Downunder35m" , no logs in the console nor nothing(its been like that for half an hour). Am I doing something wrong there? adb devices echoes my device correctly. The device in stake is normally powered on, not in recovery mode, should it be on recovery mode?? should I be seeing logs in the console? what is the usual approximate time it should take? I know it depends on the local network speed and all, but It'd be cool to have an estimate...
Thanks!!!
Click to expand...
Click to collapse
i havent checked his batch file but im assuming your device has different partitions.
just do it manually. heres a couple links and some simple directions.
This link covers it all: https://forum.xda-developers.com/showthread.php?t=2450045
simply get Adb, connect with IP. Adb shell, then su.
The key is to find your directory with your partitions by name.
Try looking in these directory with this command
Code:
ls -al /dev/block/platform/*
Your looking for output like this
Code:
drwxr-xr-x 3 root root 400 2014-12-31 19:00 .
drwxr-xr-x 3 root root 60 2014-12-31 19:00 ..
lrwxrwxrwx 1 root root 15 2014-12-31 19:00 boot -> /dev/block/boot
lrwxrwxrwx 1 root root 21 2014-12-31 19:00 bootloader -> /dev/block/bootloader
drwxr-xr-x 2 root root 300 2014-12-31 19:00 by-num
lrwxrwxrwx 1 root root 16 2014-12-31 19:00 cache -> /dev/block/cache
lrwxrwxrwx 1 root root 16 2014-12-31 19:00 crypt -> /dev/block/crypt
lrwxrwxrwx 1 root root 15 2014-12-31 19:00 data -> /dev/block/data
lrwxrwxrwx 1 root root 14 2014-12-31 19:00 env -> /dev/block/env
lrwxrwxrwx 1 root root 15 2014-12-31 19:00 logo -> /dev/block/logo
lrwxrwxrwx 1 root root 15 2014-12-31 19:00 misc -> /dev/block/misc
lrwxrwxrwx 1 root root 18 2014-12-31 19:00 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx 1 root root 23 2014-12-31 19:00 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx 1 root root 23 2014-12-31 19:00 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx 1 root root 22 2014-12-31 19:00 mmcblk0rpmb -> /dev/block/mmcblk0rpmb
lrwxrwxrwx 1 root root 19 2014-12-31 19:00 recovery -> /dev/block/recovery
lrwxrwxrwx 1 root root 19 2014-12-31 19:00 reserved -> /dev/block/reserved
lrwxrwxrwx 1 root root 14 2014-12-31 19:00 rsv -> /dev/block/rsv
lrwxrwxrwx 1 root root 17 2014-12-31 19:00 system -> /dev/block/system
lrwxrwxrwx 1 root root 14 2014-12-31 19:00 tee -> /dev/block/tee
In that example my system is /dev/block/system
so I use this to copy it to internal sd card
Code:
dd if=/dev/block/system of=/sdcard/system.img
This isnt detailed, read that link. Good Luck!
X96 mini backup problem
Hello! The following problem arises with me: When writing on the console "adb connect 192.168.3.194", it says the following
D: \ X96 ADB Backup Restore> adb connect 192.168.3.194
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.3.194:5555: can not connect to 192.168.3.194:5555: H
a connection could be established because the target computer actively denied it. (10
061)
and I can not bind to boxing. What does this mean. Is boxing any protection set up?

Categories

Resources