Hi guys, so I've got this tablet for free with my new contract and I want to root it to play a bit with it . Do you guys have any idea how to do it ? I haven't managed to find any tutorials on the web .
Vonino Onyx QS root request
+1 on this issue.
I too have a Vonino Onyx QS tablet running on Android 4.4.2. The device is decent enough, but storage management is awful! Despite being advertised as an 8 GB tablet in terms of storage, the Onyx QS runs aground at about 900 MB of installed apps (including related data and cache) and starts yelling that there is "Insufficient storage available". This renders the tablet virtually unusable after installing just a few essential apps. Emails stop working, apps will no longer update and data-intensive apps such as Google Earth will simply refuse to run. The 32 GB external SD card I've added makes no difference. It's almost like the OS has no clue what to do with it.
I suck at Android. However, after a lot of digging for pieces of information I've come to undersand that these devices use separate partitions for the apps and other files. Some folks have also hinted towards the fact that the puny 0.9 GB app partition can be resized on a rooted device by means of a partition management app. Or apps could at least be moved to the SD card right before their installation (making use of an app such as Link2SD and, again, a rooted device).
This bring us full circle back to the OP's request: could someone please create and explain a rooting method for this tablet?
Just so you know, these are fresh screenshots of this fresh factory reset configuration. Thought it would fix the problem, but it didn't.
SilentGTX said:
Hi guys, so I've got this tablet for free with my new contract and I want to root it to play a bit with it . Do you guys have any idea how to do it ? I haven't managed to find any tutorials on the web .
Click to expand...
Click to collapse
Muravey said:
+1 on this issue.
I too have a Vonino Onyx QS tablet running on Android 4.4.2. The device is decent enough, but storage management is awful! Despite being advertised as an 8 GB tablet in terms of storage, the Onyx QS runs aground at about 900 MB of installed apps (including related data and cache) and starts yelling that there is "Insufficient storage available". This renders the tablet virtually unusable after installing just a few essential apps. Emails stop working, apps will no longer update and data-intensive apps such as Google Earth will simply refuse to run. The 32 GB external SD card I've added makes no difference. It's almost like the OS has no clue what to do with it.
I suck at Android. However, after a lot of digging for pieces of information I've come to undersand that these devices use separate partitions for the apps and other files. Some folks have also hinted towards the fact that the puny 0.9 GB app partition can be resized on a rooted device by means of a partition management app. Or apps could at least be moved to the SD card right before their installation (making use of an app such as Link2SD and, again, a rooted device).
This bring us full circle back to the OP's request: could someone please create and explain a rooting method for this tablet?
Just so you know, these are fresh screenshots of this fresh factory reset configuration. Thought it would fix the problem, but it didn't.
Click to expand...
Click to collapse
try with Kingo ROOT. You do it at you'r own risk.
Successful rooting of Vonino Onyx QS tablet
Paget96 said:
try with Kingo ROOT. You do it at you'r own risk.
Click to expand...
Click to collapse
Hi, Paget96! Thank you so much for the solution!
I'm writing this to let you, the OP and everybody else know that Kingo Root did it! I have succesfully rooted the tablet and the process itself was quick and merely a matter of installing the software on my PC, connecting the tablet via USB and clicking my way through.
Afterwards I installed Link2SD Plus to manage the transfer of apps from internal storage to the external SD card (32 GB in my case). The app is dirt cheap and truly what you need, because the free version does not allow you to move app data, only the app itself and its libraries. As I've come to know, data and cache build-up is what ends up killing storage space.
Before installing Link2SD however, one must prepare the SD card by means of a partitioning program. Highly recommend you do this via card reader on an actual PC. Use MiniTool Partition Wizard, it seems to be very popular these days. Delete whatever's already on the card and make two PRIMARY partitions: the first one will be FAT32 and will store the media you consume (like music, photos, videos etc.), while the second partition has to be ext4 (ext2 did not work for me on this tablet) and will hold the apps and their data. You can go ahead and name them "Media" and "Apps" respectively to avoid confusion. Remember: both must be primary partitions, the first one is FAT32 for media, the second is ext4 for apps. I made my app partition 10 GB big. Overkill, you say? Hey, I'm done with insufficient storage space errors, ok? :silly:
While you're at it, you might want to add a third partition for swap space to add more RAM to your device. There are tutorials for it on the web.
Once you're done formatting the card, reinstall it in the tablet, open up Link2SD and choose ext4 at the script mounting prompt. From there on, moving apps from internal to SD card space should be intuitive.
Prior to all this fiddling I suggest you perform a factory reset on your device so you can start clean. Can't tell you anythihg about custom ROMs or stuff like that because I didn't have a need for them. This thing works fine apart from that silly storage limitation.
Phew! I can finally enjoy using my tablet... :fingers-crossed:
Muravey said:
Hi, Paget96! Thank you so much for the solution!
I'm writing this to let you, the OP and everybody else know that Kingo Root did it! I have succesfully rooted the tablet and the process itself was quick and merely a matter of installing the software on my PC, connecting the tablet via USB and clicking my way through.
Afterwards I installed Link2SD Plus to manage the transfer of apps from internal storage to the external SD card (32 GB in my case). The app is dirt cheap and truly what you need, because the free version does not allow you to move app data, only the app itself and its libraries. As I've come to know, data and cache build-up is what ends up killing storage space.
Before installing Link2SD however, one must prepare the SD card by means of a partitioning program. Highly recommend you do this via card reader on an actual PC. Use MiniTool Partition Wizard, it seems to be very popular these days. Delete whatever's already on the card and make two PRIMARY partitions: the first one will be FAT32 and will store the media you consume (like music, photos, videos etc.), while the second partition has to be ext4 (ext2 did not work for me on this tablet) and will hold the apps and their data. You can go ahead and name them "Media" and "Apps" respectively to avoid confusion. Remember: both must be primary partitions, the first one is FAT32 for media, the second is ext4 for apps. I made my app partition 10 GB big. Overkill, you say? Hey, I'm done with insufficient storage space errors, ok? :silly:
While you're at it, you might want to add a third partition for swap space to add more RAM to your device. There are tutorials for it on the web.
Once you're done formatting the card, reinstall it in the tablet, open up Link2SD and choose ext4 at the script mounting prompt. From there on, moving apps from internal to SD card space should be intuitive.
Prior to all this fiddling I suggest you perform a factory reset on your device so you can start clean. Can't tell you anythihg about custom ROMs or stuff like that because I didn't have a need for them. This thing works fine apart from that silly storage limitation.
Phew! I can finally enjoy using my tablet... :fingers-crossed:
Click to expand...
Click to collapse
10gb is too big, you will broke your sd.
Better use 512mb.
Paget96 said:
10gb is too big, you will broke your sd.
Better use 512mb.
Click to expand...
Click to collapse
Could you expand on that one, please? Why am I at risk of ruining the SD card?
Muravey said:
Could you expand on that one, please? Why am I at risk of ruining the SD card?
Click to expand...
Click to collapse
Brcause sd work without stop, that is not good.
SD prob
Hi, i have the same tablet ... and i managed to root it ... but i cant manage to increse the storage . l've done the exact stepts ... installed micropartition deleted my sd card (2gb micro sd samasung) i did the first partition fat32 primary with a size of 800 gb and when i try to make the second one ext4 the program says that windows cant see the second partion on a removable device but i continuued anyways ,,, and created the second one with ext2 and then with ext4 as primary ... my windows and my tablet cant see the second partion ... need a little help ... thx
I heave installed the drivers, and nothing happens. Its not connecting to my pc. I changed the pc too. I heave the error: Unfortunately, Mobile data has stopped. I tryed to repair this with recovery -- Wipe data, factory reset. Not working.
I have this Atrix now for a few days and want to examine it. It is one of my favourite devices since it was released years ago.
I will start to tamper with it, and try custom Roms etc. But first of all i want to make a full backup of the device, so i can probably recover it fast and without hassle in the future. I also use Huawei Ideos X5 and i have full Raw backups of its 4GB emmc (2GB part is used as an internal SD originally). I backup and restore these images with the basic free program "Roadkil's Disk Image" in Windows.
As we all know, to use this program or similar disk backup programs, we have to reach the phone's whole disk (called emmc or internal card, i guess). In Ideos X5 the procedure is as follows;
1) Make sure the bootloader is unlocked.
2) Open the phone to reach the "pink screen" by pressing VolUP+VolDOWN+POWER buttons at the same time.
3) When you see the pink screen connect the phone to the PC via USB.
4) The disk is reachable now, use a sector based backup program such as "Roadkil's Disk Image" (sometimes called Forensic Copy).
OK, it's a brief explanation but clear enough, i guess. Now i want to do the same thing in Atrix, since i unlocked the bootloader and installed CM7.2 to it, 6-7 months ago, while my relative was using it.
I connect the phone to the PC in Fastboot and RSD modes, but i can't reach the disk itself. The adb and fastboot commands work, the connection is successful, but neither Windows, nor Linux Mint sees the 16GB disk. So, full Raw backup seems impossible in this manner!
I searched the Atrix forum widely, but couldn't find a solution. There are threads of making Nandroid backups or partition based backups with a different approach which i didn't try yet. For example:
"[INFO] Backup the pds partition of your Atrix!"
Link: http://forum.xda-developers.com/showthread.php?t=1138220
I can learn and apply this commandline method but 4GB Fat32 file limit will probably be the base problem. Taking the backup directly to the NTFS HDD on PC can be a solution but, has anyone tried it?
It seems that, important partitions are backed up using ADB /shell commands. But i believe that full disk backups may be the best way to recover a phone in some situations. I know that backing up the whole disk including also the 10,7 GB internal SD part is useless, time and space consuming. But recovering the phone totally to a previous state is sometimes fatally important or advantageous. ie:
* Recover the phone when the IMEI is gone somehow,
* Recover the phone when the partitions are resized
* Recover the phone when partition table is corrupted or partitions are lost
* Move between your installed Roms without worrying about all the procedure, wipes, resizes, bla bla...
* ......
Anyway, here comes my main question:
Is it possible to reach the 16GB disk of Atrix from PC? If so, how?
Thanks in advance.
Be-Mine said:
I have this Atrix now for a few days and want to examine it. It is one of my favourite devices since it was released years ago.
I will start to tamper with it, and try custom Roms etc. But first of all i want to make a full backup of the device, so i can probably recover it fast and without hassle in the future. I also use Huawei Ideos X5 and i have full Raw backups of its 4GB emmc (2GB part is used as an internal SD originally). I backup and restore these images with the basic free program "Roadkil's Disk Image" in Windows.
As we all know, to use this program or similar disk backup programs, we have to reach the phone's whole disk (called emmc or internal card, i guess). In Ideos X5 the procedure is as follows;
1) Make sure the bootloader is unlocked.
2) Open the phone to reach the "pink screen" by pressing VolUP+VolDOWN+POWER buttons at the same time.
3) When you see the pink screen connect the phone to the PC via USB.
4) The disk is reachable now, use a sector based backup program such as "Roadkil's Disk Image" (sometimes called Forensic Copy).
OK, it's a brief explanation but clear enough, i guess. Now i want to do the same thing in Atrix, since i unlocked the bootloader and installed CM7.2 to it, 6-7 months ago, while my relative was using it.
I connect the phone to the PC in Fastboot and RSD modes, but i can't reach the disk itself. The adb and fastboot commands work, the connection is successful, but neither Windows, nor Linux Mint sees the 16GB disk. So, full Raw backup seems impossible in this manner!
I searched the Atrix forum widely, but couldn't find a solution. There are threads of making Nandroid backups or partition based backups with a different approach which i didn't try yet. For example:
"[INFO] Backup the pds partition of your Atrix!"
Link: http://forum.xda-developers.com/showthread.php?t=1138220
I can learn and apply this commandline method but 4GB Fat32 file limit will probably be the base problem. Taking the backup directly to the NTFS HDD on PC can be a solution but, has anyone tried it?
It seems that, important partitions are backed up using ADB /shell commands. But i believe that full disk backups may be the best way to recover a phone in some situations. I know that backing up the whole disk including also the 10,7 GB internal SD part is useless, time and space consuming. But recovering the phone totally to a previous state is sometimes fatally important or advantageous. ie:
* Recover the phone when the IMEI is gone somehow,
* Recover the phone when the partitions are resized
* Recover the phone when partition table is corrupted or partitions are lost
* Move between your installed Roms without worrying about all the procedure, wipes, resizes, bla bla...
* ......
Anyway, here comes my main question:
Is it possible to reach the 16GB disk of Atrix from PC? If so, how?
Thanks in advance.
Click to expand...
Click to collapse
System + data (internal storage) is your 16GB. You'll backup system and your internal storage to get what you're looking for. And to the best of my knoledge, sbf'ing will do the rest. IMEI may be somewhere else, not sure. Afaik we don't have a tool to edit some advanced stuff like the latest qualcomm devices do.
Sent from my ATRIX HD using XDA Free mobile app
Sector by sector Raw image backup and restore options in Android devices!
I guess i couldn't explain the issue clearly.
The 16GB Atrix disk that i meant, is the main memory block which is exactly 15.914.762.240 bytes in total. This memory consists of 3 primary and 14 logical partitions. Some of these can be considered as the /recovery, /boot, /pds, /cdrom, /osh, /system, /cache, /data, /emmc(~11GB internal SD).... etc. partitions:
{
"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"
}
From what i've learned from the below links;
[DEV][REF] El Grande Partition Table Reference
[GUIDE] Making Dump Files Out of Android Device Partitions
[GUIDE] How to make a nandroid backup directly to your computer without using sdcard
these partitions can be backed-up and restored within terminal emulator or ADB, with the help of the so-called "dd method" (which i will research more)!
Backup of the whole 16GB memory block is also possible regarding to these links, but restore of this whole block image seems impossible, which is the main problem!
Now, let me explain the weird situation on my ancient Huawei Ideos X5 phone. If i connect the Ideos X5 to the PC with the "pink screen" (by pressing VolUP+VolDOWN+POWER buttons), the phone's whole 4GB memory block is reachable. Eventually i can do whatever i want with the phone, because the memory block is seen as a USB disk to the Windows,Linux,etc:
Here are the possibilities that i can do (and already did) with the Huawei Ideos X5:
1) Intelligent sector copy of the recognized partitions.
Only data blocks are backed up and restored on ext2/ext3/ext4,Fat32 partitions, so the backup files are small. But the other unknown partitions can't be backed up with this method.
2) Forensic copy of the partitions.
Sector by sector Raw copy is made, so the backup file is exactly the same as the partition size. All known and unknown partitions can be backed up and restored with this method.
3) Forensic copy of the whole disk (full memory block)
The whole memory block is copied (raw backup) and restored. The image file size is exactly the same as the disk size (But can be zipped afterwards to reduce the size.)
I checked the forum widely, now i understand that the "pink screen" property is unique to the Ideos X5! Most of the devices (if not all) seem to NOT support this option. The whole memory block is NOT reachable within the Windows, Linux, etc. It's only available with ADB or within the device from the terminal emulator.
As a result, i won't be able to make full Raw image backups and restores of the whole disk of Atrix, which also seems impossible on the other devices.
If we find a method to reach the memory blocks of the devices as a USB HDD within OSes (just like in Ideos X5), then we will be able to do full backup and restores which is important in some situations as i described before. (But we may brick the devices easier also )
But i believe that full disk backups may be the best way to recover a phone in some situations. I know that backing up the whole disk including also the 10,7 GB internal SD part is useless, time and space consuming. But recovering the phone totally to a previous state is sometimes fatally important or advantageous. ie:
* Recover the phone when the IMEI is gone somehow,
* Recover the phone when the partitions are resized
* Recover the phone when partition table is corrupted or partitions are lost
* Move between your (previously) installed Roms without worrying about all the procedures, wipes, resizes, bla bla...
* ......
Click to expand...
Click to collapse
Please share your opinions.
Be-Mine said:
I guess i couldn't explain the issue clearly.
The 16GB Atrix disk that i meant, is the main memory block which is exactly 15.914.762.240 bytes in total. This memory consists of 3 primary and 14 logical partitions. Some of these can be considered as the /recovery, /boot, /pds, /cdrom, /osh, /system, /cache, /data, /emmc(~11GB internal SD).... etc. partitions:
From what i've learned from the below links;
[DEV][REF] El Grande Partition Table Reference
[GUIDE] Making Dump Files Out of Android Device Partitions
[GUIDE] How to make a nandroid backup directly to your computer without using sdcard
these partitions can be backed-up and restored within terminal emulator or ADB, with the help of the so-called "dd method" (which i will research more)!
Backup of the whole 16GB memory block is also possible regarding to these links, but restore of this whole block image seems impossible, which is the main problem!
Now, let me explain the weird situation on my ancient Huawei Ideos X5 phone. If i connect the Ideos X5 to the PC with the "pink screen" (by pressing VolUP+VolDOWN+POWER buttons), the phone's whole 4GB memory block is reachable. Eventually i can do whatever i want with the phone, because the memory block is seen as a USB disk to the Windows,Linux,etc:
Here are the possibilities that i can do (and already did) with the Huawei Ideos X5:
1) Intelligent sector copy of the recognized partitions.
Only data blocks are backed up and restored on ext2/ext3/ext4,Fat32 partitions, so the backup files are small. But the other unknown partitions can't be backed up with this method.
2) Forensic copy of the partitions.
Sector by sector Raw copy is made, so the backup file is exactly the same as the partition size. All known and unknown partitions can be backed up and restored with this method.
3) Forensic copy of the whole disk (full memory block)
The whole memory block is copied (raw backup) and restored. The image file size is exactly the same as the disk size (But can be zipped afterwards to reduce the size.)
I checked the forum widely, now i understand that the "pink screen" property is unique to the Ideos X5! Most of the devices (if not all) seem to NOT support this option. The whole memory block is NOT reachable within the Windows, Linux, etc. It's only available with ADB or within the device from the terminal emulator.
As a result, i won't be able to make full Raw image backups and restores of the whole disk of Atrix, which also seems impossible on the other devices.
If we find a method to reach the memory blocks of the devices as a USB HDD within OSes (just like in Ideos X5), then we will be able to do full backup and restores which is important in some situations as i described before. (But we may brick the devices easier also )
Please share your opinions.
Click to expand...
Click to collapse
Ok, i'm getting the drift of what you are trying to do now. For that, there is a thread regarding dual booting. I'll dig that up and give you the link. For that, we dd'd via adb in recovery. I'll need to dig into my files for a bit more specifics, but hang tight and i'll get you the info i know
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
Ok, i'm getting the drift of what you are trying to do now. For that, there is a thread regarding dual booting. I'll dig that up and give you the link. For that, we dd'd via adb in recovery. I'll need to dig into my files for a bit more specifics, but hang tight and i'll get you the info i know
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Actually, my ultimate goal is not a multi-boot. I triple-boot in my PC but i was never eager of this in Android devices. If i had very large memory blocks (32GB,64GB) in my devices, i would try it already. But i think multi-booting may negatively effect the storage partitions on Ideos X5 and Atrix (especially the /system, /cache, /data partitions ?)
Anyway, i will check that link and informations based on dual booting Atrix, comparing CM7 vs CM10 easily on Atrix can be very interesting.
But my main concern is reaching the whole memory blocks of the devices within windows/linux directly as a USB-HDD, probably with the help of a hack or a patch.
Thanks for all :good:
Be-Mine said:
Actually, my ultimate goal is not a multi-boot. I triple-boot in my PC but i was never eager of this in Android devices. If i had very large memory blocks (32GB,64GB) in my devices, i would try it already. But i think multi-booting may negatively effect the storage partitions on Ideos X5 and Atrix (especially the /system, /cache, /data partitions ?)
Anyway, i will check that link and informations based on dual booting Atrix, comparing CM7 vs CM10 easily on Atrix can be very interesting.
But my main concern is reaching the whole memory blocks of the devices within windows/linux directly as a USB-HDD, probably with the help of a hack or a patch.
Thanks for all :good:
Click to expand...
Click to collapse
Well the dual boot mentioning ties into the dd method.
This might be more up the alley of your main concern http://www.paragon-drivers.com/extfs-windows/
On a side note, dual booting on this device can be done on a 16GB sd card, but for space reasons (compensation for space lost to do dual boot), a 32GB is a bit more recommended for this, plus it adds a bit more memory in the process.
palmbeach05 said:
Well the dual boot mentioning ties into the dd method.
This might be more up the alley of your main concern http://www.paragon-drivers.com/extfs-windows/
On a side note, dual booting on this device can be done on a 16GB sd card, but for space reasons (compensation for space lost to do dual boot), a 32GB is a bit more recommended for this, plus it adds a bit more memory in the process.
Click to expand...
Click to collapse
If only my issue was that simple, but unfortunately not.
The link you gave is of a basic software to work with linux file systems from Windows. I can already achieve this when needed, using similar software like Explore2fs, Ext2explore, etc.
But the case is very different. The whole memory block (disk) of the devices are not accessible as a USB disk within OSes (both Linux and windows, and also MacOS most probably) natively. The full disk is only accessible from ADB, or the phone itself. So native disk softwares can't be used, especially for full backup and restore purposes.
From what i understood from my researchs, "dd method" seems the Linux alternative to make sector based backups and restores. But even dd can't be used to restore the memory block. Because, to restore, we have to access the disk when the phone is not used , AFAIK.
That's why Huawei Ideos X5 "pink screen" option seems very rare, extreme and useful. Please take a look at the links i gave in my previous posts, you'll get what i mean.
Anyway, dual-booting Atrix is still another interesting issue to research for me.
AFAIK you can't directly map the raw Atrix eMMC to a block device on Atrix, at least not via USB, using standard tools. And you definitely wouldn't want to do this in write mode (The tegra2 on Atrix has a strict boot protocol. It's so strict that IIRC it even requires an encrypted/digitally signed boot loader which resides on the beginning of the drive. AFAIK you can't even mess with partition table).
I guess you could use a custom recovery mod for doing that if all you want is to read the eMMC as a block. The linux kernel has a mass storage gadget which can expose a block device as an usb drive. You'd need to point /dev/block/mmcblk0 to it and voila (see for instance http://www.linux-usb.org/gadget/file_storage.html). Old android uses it for mounting your storage areas when you plug it to a host usb. Newer uses other methods as you need exclusive device access for safely writing to the storage partitions.
And as you can't have read-write partitions mounted while you're playing with the same block device, and AFAIK a recovery is fine with read only mounts, contrary to a normal android boot, you could go with it. But check that e.g. /data is mounted ro, some recoveries mount it rw by default.
I think there's a way to use adb in recovery, if you can get a root console via adb then you may be able to use a standard recovery to command the usb mass storage gadget without need to customize a recovery.
Btw, I think the usb gadget only exposes the device in read-write mode, so there's nothing preventing you or some application of attempting to write to the device, and this would probably be a bad idea. So watch out if you want to do that, people got hurt for doing less hacking :silly:
@PolesApart
Thanks, you encourage me to research deeper.
But, as you already mentioned, this kind of backup/restore seems very tricky. I would check other sources and try to find a way to achieve, but i lost my ambition regarding that i have no backup phones. And i don't have time and experience to struggle with such dangerous issues.
I'm still using this Atrix as a main phone. I hope to get a Z5 Compact soon. Maybe i can go on seeking info and tests when this Atrix becomes totally idle afterwards. :laugh:
Thanks for your interest and the informations. :good:
Hello!
I have a somewhat unusual challenge on my hand and am hoping there is a solution, however after days of searching I am unable to come up with a clear or consistent answer. I got a shiny new SM-T580 around the holidays, and immediately set to work on installing twrp, rooting the device, etc. to be able to use it for my needs. My device is OEM unlocked, rooted, has Xposed installed, and has a ton of hard to come by apps installed, as well as a substantial amount of important personal files on it. On Saturday, I went to flash a zip file to install a tool pertaining to ROM modification and the install unexpectedly failed because TWRP couldn't mount my /data partition; I realized I had completely forgotten to format /data after disabling encryption back when I first did everything, and my /data partition was still encrypted.
That being said, I really do need to remove the encryption, but I really need to preserve my data also. To make matters more complicated, I have enabled adoptable storage, and am using a 64gb card formatted as internal storage, with about ~30gb data on it. I have backed up my personal files to the cloud, but now am trying to figure out how to move my apps and app data. Ideally I would like to preserve my entire existing directory structure, as well as home screen configurations, etc. I am left with a few questions that are preventing me from proceeding:
How do I determine which data is stored on the actual external SD card? From my own poking around, it looks as though the external SD is /mnt/expand/aa11a11a-blah-blah-blah/ but I am not positive. If that is my SD card, can I simply move it to a new install? I assume the SD card is also encrypted, as I am guessing the string following /mnt/expand/ is an encrypted serial number or something of the sort. If that is the case, can I simply copy the files from the above directory, and then copy them back in after formatting the card? Beyond this, as far as what is actually stored on my phone, is there a means of backing up and restoring the files and directory structure and having it all still work and point to the right places? I don't know how the system links the adopted storage and just feel like I'm in over my head when it comes to understanding the nitty-gritty of Android file system internals. I would simply backup the whole partition and then restore it but then I would be back to square one with the encryption. I am competent with TWRP, ADB, ODIN, etc and would be very, very happy if anyone could point me in the right direction on this, even if the solution is complex. If I am unable to figure this out before the weekend I am going to have to manually back up all apps and click through 300+ apk files. I do also have titanium backup but I am kind of in a bind with storage space vs backup size. Anyhow, if you made it this far thank you so much for reading and I am looking forward to your replies! :highfive
Edit: This was intended for the Galaxy Tab A forum. Mods, please move this thread to Samsung Galaxy Tab A series Questions & Answers if possible, though the question should pertain to both device series on 6.0+. Thank you!
I own a Nokia 6, never rooted, 8.1.0 with the latest security patch installed (1 August 2018).
I have 32 GB internal shared storage and 64 GB microSD card installed. Be it a good or bad idea, I have formatted the card as internal storage, and migrated data to it using options available in Android settings, no third party shenanigans.
When I look at apps' details, those that have the option to choose storage signify that they are on sdcard.
Now, to the problem: I approached about half of used space on the sdcard, that's a bit over 32 GB, and I'm closing in on about half on the internal shared storage, that's about 13.4 GB used at the moment.
However, even though it would look like I have lots of unused space left, the phone started to act as if I don't have any. But... Not always. Let me elaborate.
I can't make a picture or record video, all I get is: "there was a problem with saving your photo or video."
I can't download files using a browser. It instantly fails.
I can't install apps from Google Play Store like "Google" and many others, however, I can install some other apps, seemingly at random (but if it fails, of keeps failing).
I can - because I just did - download security patches from settings/system updates....
From the above I speculate without any specific Android knowledge that:
- the internal shared storage isn't a single partition spanning the whole of built-in memory but rather is partitioned into multiple... Well, parts, therefore:
- there's probably a /system, /data and /user partition (forgive the layman guesswork on the names). There's probably also a /swap like in *nix? Then again, I guess not because that would probably slowly kill internal storage flash memory...
Anyway, from the above I gather that the simplistic reporting on how much internal storage I used doesn't let me know that I might have ran out of space on one of those discrete partitions.
That might explain why some apps I can install (they can be installed in external storage, so they do) and some I can't (they need to be on internal storage for whatever reason).
I have tried looking at the app info to maybe move apps to SD card but any and all I check either don't have the option or they already are on SD.
I tried deleting files and removing apps with various results:
- some files I just can't remove, even though they don't appear to be in use (still, maybe they have handles open, I don't know how to check for that apart of forcing suspected apps close)
- some apps (HERE Maps) left a considerable amount of junk in Android/data after themselves, and none of my file managers seem to be able to delete these files.
- some files and apps deleted just fine and the used space indicator did reflect that, however...
I still can't save a photo or video, or download a file, and apps still either install or not, just like before.
That got me thinking that there may be a problem with file/directory permissions for some bizarre reason.
I'm stumped. I'm on the go, visiting Milan tomorrow and I won't be able to take a single photo. Not that Nokia 6 has a great camera, but it's there and I can't use it when I need it.
Halp?
A little bump
So, am I truly sentenced to factory reset?
Hidden Android dialer codes don't work at all... I think I'm out of options here.
Update: So I did end up doing the factory reset. Afterward, my phone started to work fine, with the exception of the microSD card that always showed up in the notification area as needing of attention. I tried formatting it as portable, and it would supposedly work if you went by the final "success" message, but it wouldn't change anything, and it would still not show up in file manager. The notification about it needing to be set up would still be there, no matter how many times I tried.
So I took the card out and connected it to a PC - tried formatting it, deleting and recreating all partitions, wiping it out, all supposedly would work in partition managers, but after the things were all done, it wouldn't reflect on the actual card.
Seems like it was dying already.... Fortunately, I had a 32GB card to spare, got it into the phone. Worked on the first try.
So that's all folks, my 64GB microSD card died on me, and that's the reason of all the anguish above. Now you know.