Database Develop

[HOWTO]Change SD with app2sd

Upgrading/Changing of memory/SD cards while using App2SD?
Here's how.
What you need:
-Rooted
-Drellisdee's ThunderG custom recovery(preferably v1.2)
-Card Reader(Optional)
Steps:
-Boot into recovery
-In recovery menu, select "Backup/Restore" then "Nand + ext backup".(If you are using an ext4 app2sd partition, ThunderG v1.2 is a MUST)
-Now with any means suitable to you, transfer the "nandroid" folder found on your SD to your PC.(the easiest way is to mount USB-ms via recovery, but for some reason this option doesn't work for me)
-Now turn off your phone and insert the NEW SD.
-Boot into recovery again and partition your new SD(for app2sd).
-Now again, with any means suitable to you, transfer the "nandroid" folder you just copied to your PC back to the new SD.
-In recovery menu, select "Backup/Restore" then "Nand restore", choose the file to restore(in most cases, there is only one option)
-Wait for it, now reboot.
-Enjoy!
Custom Recovery
ThunderG v1.2

man! you woke up early for this?
kudos!!!! now everyone can happily change/upgrade their cards...
(the easiest way is to mount USB-ms via recovery, but for some reason this option doesn't work for me)
Click to expand...
Click to collapse
now this doesnt seem right... i mean, it has to work.
hhmm.. mine does. im on thunderG too.
maybe youre lacking drivers for it.... have you checked you device manager?
------------------
EDIT ok i get it. i dont have the V1.2 will try to install later on.
maybe the new recovery has the problem.. and not your PC...
---------------------------------
more EDIT
ok ive just installed V1.2 and yes i can confirm that the USB toggle under recovery works for me.
now the next thing to try is upgarade to a higher capacity card... *lol*
nice one Ungaze!

lol, up late seems more like it.
usb-toggle issue might be usb driver related.
havent flashed the firmware yet so i didnt have the need to install the drivers as well.
i also used this method to revert my app2sd partition from ext4 to ext2. so it also works with different partition filesystem, someone can maybe test if it also works with different partition size.

thats backing up and restoring right?
maybe ill try it on ext4...
anyway, why convert back to ext2? is there any significance?

bluviper said:
thats backing up and restoring right?
maybe ill try it on ext4...
anyway, why convert back to ext2? is there any significance?
Click to expand...
Click to collapse
was doing a test, and speed-wise there is a slight improvement. about 50 - 80 points on I/O using quadrant. Although really unnoticeable and I don't really rely on quadrant that much, performance seems to be just the same.(OptimusXrom maker domenic_s also uses ext2).

i see.. maybe one time ill try to do ext2.. hehehe
theres not much happening with our O1 today ei?!
so i need to do something... hehehe errr experiment on something...
*lol*

now thats weird.. after rebooting the second time to recovery...
i cant find my files under Flash zip files...
seems like only system folders are installed....

I just used EASEUS Todo Backup to clone old sd card (with partition ext 4, i think) to new sd card.
It copied everything on the old sd card to new sd card and it works flawlessly.
The software is free for home user.

bluviper said:
now thats weird.. after rebooting the second time to recovery...
i cant find my files under Flash zip files...
seems like only system folders are installed....
Click to expand...
Click to collapse
are you refering to this step?
-Boot into recovery again and partition your new SD(for app2sd).
which i highly doubt. please explain.
I just used EASEUS Todo Backup to clone old sd card (with partition ext 4, i think) to new sd card.
It copied everything on the old sd card to new sd card and it works flawlessly.
The software is free for home user.
Click to expand...
Click to collapse
good for you. just sharing how I did it since changing SDs are becoming pretty common nowadays.

ungaze, after installing the recovery...
and rebooting it via adb, i can still access the files on my sd card. like for example i want to install a new theme etc etc using Flash ZIP menu on V1.2
but after rebooting the second time.
i cant see the files anymore... just folders....
im not into changing cards. but i just want to install something using V1.2 recovery.
and somehow i cannot see my zip files inside Flash ZIP menu.
thats the place to look for when i want to install flashable zips right?

I see, I think I know what you mean.
One of the new features of ThunderG v1.2 recovery is the ability to recognize folders when choosing a zip file to flash. Well that's good, but the problem is that it still doesn't have the option to scroll down when the screen/list is full(or maybe I just havent found out yet). I also had this problem before, so what I did was to make a new folder with a higher alphabetical priority name, eg: "aaflash", "aflashfiles", "1flash" etc so that the folder will always appear at the top. Then I placed all my zip files into that folder and just open the folder when I need to apply something. Try it, the files should appear.

yap. someone told me that too... and so i did.. and yes it can be read...
but we can still consider that a bug.
and i think the author needs to edit that part.
anyhow. its working fine....

What does this do? Is this the way we can move all our apps to sd card??? Please im desperate
Sent from my LG-P500 using XDA App

ungaze said:
lol, up late seems more like it.
usb-toggle issue might be usb driver related.
havent flashed the firmware yet so i didnt have the need to install the drivers as well.
i also used this method to revert my app2sd partition from ext4 to ext2. so it also works with different partition filesystem, someone can maybe test if it also works with different partition size.
Click to expand...
Click to collapse
could you explain how you converted the ext4 partition into ext2?

victortangocharlie said:
could you explain how you converted the ext4 partition into ext2?
Click to expand...
Click to collapse
Actually, I can't really call it a convertion, I just backed up the SD contents, format it, repartition ext2 than put the old contents back in place. Update: Ext2 on optimusXrom's app2sd doesnt seem to work, didn't checked thoroughly and app2sd got disabled. Need to contact domenic on how he did this.
domenic_s said:
No, actually ext2 is faster than ext3 ... i don't know how it is to ext4 but i'm using ext2 at the moment.
Click to expand...
Click to collapse

Hey ungaze,
Could you tell me how to use apps2sd to move an app to the ext4 partition i have on my phone.

Sony Xperia ZR – Mount ExternalSD2InternalSD

Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card(EDIT: PS: both partitions should be Primary). Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Edit:
Simplified installation if you do not care for easy accessibility to your orig internal memory:
Use this video tutorial by ashwin123:
The only exceptions are that, you need to partition your card,
and you have to use the file 'mountSdFailSafe.txt' instead of the file in the package mentioned by him.

Nice
Waiting for someone to test it n confirm it successfully works
Still here
N!geR -> E!ch0

NisJ said:
Hi,
This is my first android device, so am pretty much a newbie for android.
Have created this mod to mount external SD card partition as internal partition.
I took pointers from a lot of threads on xda forums to get this working, so I feel bound to share it.
Note: Have only tested it with Android 4.1.
(I'm not responsible for any Damage to your phone. Use at your own risk.)
Note: This will likely result in data loss. Backup!
Required :
1. Root Access
2. init.d support click here
3. Root Browser click here
4. SManager click here
5. An sd card (duh!) (with class 10 SD cards preferable)
6. Some way to partition your SD Card (like MiniTool Partition Manager)
Install instructions:
1. Create two ‘fat32’ partitions on SD card. Your first partition will be mounted as normal extSd card, and your second partition will be mounted as internal SD Card for your apps. (I partitioned my 64GB(10^9 bytes) sd card with ~16 GB 1st partition and ~42 GB 2nd partition)
2. Copy and paste “mountSd” to etc/init.d folder. (If you don’t have such a folder, means you lack init.d support. click here and follow instructions to enable it) This script creates another mount point called ‘sdcard2’ and mounts current internal sd card there. It also tries to mount second partition to ‘sdcard0’ location, but seems to fail some times (as fat32 is not natively supported linux partition it seems, but could be wrong), so step 3 is required.
3. Copy ‘mountSdFailSafe.txt’ to your phone’s ‘/data’ folder. Now with ‘SManager’, register this file as script with ‘su’ and ‘boot’ selected. (click and hold script -> in context menu click ‘Open As..’ -> ‘Script/Executable’ -> Is Script = true, select ‘su’ and ‘boot’ buttons)
4. Restart.
This should do it. Once restarted, second partition will be shown as internal memory.
Note:
You will lose all app data and other app related customizations. You may be able to restore it by simply copy pasting ‘Android’ folder from ‘/storage/sdcard2’ to ‘/storage/sdcard0’. This has not been tested by me but should work theoretically (as I started with a blank phone, and so did not need to back up my app data). Or you could use Titanium Backup.
Some Issues that occur due to this mod:
I have been using this mod since the past 2 weeks, and the phone is quite stable with this mod.
The only issue I have faced is that when connected to PC (Windows 8) through USB, ‘My Computer’ keeps crashing unless and until you disconnect the phone. Otherwise it seems to be working fine. To circumvent this issue I have been using Samba to share files between PC and my phone.
Please share how it works out for you guys.
Other Notes:
I tried to get this working with ext4 partition, which has a +ves that it will not require step ‘3’ of install instructions and supports file sizes >4GB, but there are loads of permission issues happening, which I could not solve.
(Thought of setting “set GID” bit and then finding and adding all users to root group but failed. Also tried to set owner group ‘sdcard_rw’ without much success. May be someone who knows linux better may know how to solve this, Could not find much help on the forums as it seems others are facing a similar problem see more)
Thanks to:
For basic idea (PS: do not use the given method exactly as you will end up in a boot loop. For some reason, ‘sdcard1’ mount point has to be mounted by system only and can’t be mounted any other way, it seems.)
http://forum.xda-developers.com/showthread.php?t=2180733
Click to expand...
Click to collapse
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks

grim_ripper said:
Am interested to try this but before I do, just wanted to check when you say data is lost, is it due to the lost of the original /data partition? Or just due to the sd card's partition?
What's the outcome when this is done, I mean do we have two data partitions one from the original phone's memory and another with the sdcard? And in the settings menu, will we get to choose to send apps over to sd? Thanks
Click to expand...
Click to collapse
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?

NisJ said:
Your application data will be lost in a way, as orig internal sd card will be mounted to 'sdcard2' mount point(newly created). All your app data will be installed to your memory card's second partition, which is now the new internal sdcard. To access your orig data, you will have to go to it through a file manager, and apps or media scanner will not be able to access this memory any more.
The scripts provided will not format your internal memory.
Still apk files, dalvik cache etc, will still take up your original internal memory's space.
Partitioning your sd card will probably format it as well unless you take special precaution (ie. through shrink volume).
Hope it makes sense...?
Click to expand...
Click to collapse
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?

grim_ripper said:
It makes sense, just am confused on how the system will still recognize the original storage when the sd card's storage is supposingly replacing it. Could you post a screen shot of your storage from settings?
Click to expand...
Click to collapse
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...

NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0

NisJ said:
Here you go....
PS: third image shows that internal storage is still accessible, just not to apps. Only apk files, and other android files go there go there. sdcard2 in 4th image is newly created mount point for your orig internal storage, but is ignored by most of the apps...
Click to expand...
Click to collapse
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.

grim_ripper said:
Phone keeps rebooting now, couldn't copy it to /etc/init.d
I think it has something to do with having data running in the background, now I don't know what to do with my phone
EDIT: Ok, manage to recover from the reboot state, had to deny root access to my file explorer. I think the reboot was caused when I set permission to write for /system. Anyway, everytime I keep trying to copy to /etc/init.d, I get a permission denied so am not sure what I should do now.
Click to expand...
Click to collapse
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.

E!ch0 said:
Can u do a tutorial video how to install this script bro?
Cuz the installation steps r bit complicated
Still here
N!geR -> E!ch0
Click to expand...
Click to collapse
Creating a video will take time at least til sat... prob more.
Will see if I can create a simplified install instructions once i reach home.

NisJ said:
When ever you copy something to init.d it will reboot, or does it go into boot loop?
To check if it worked correctly, see if new mount point storage/sdcard2 was created..
EDIT: If it worked correctly, then you could move to next step.
else you could also skip it, and goto the next step of SManager, but in that case you will lose access to your original internal storage as it wont be mounted to sdcard2.
Click to expand...
Click to collapse
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical

grim_ripper said:
What happens is that everytime I try to mount /system as writable, it reboots and hence I can't copy either files to their designated location
EDIT: Also, now everytime I reboot, there's a popup that says USB connectivity has stopped, and if I go under settings->storage, settings fc. I'm thinking this has something to do with two partitions on the sd card so I hope it all goes away when this works or I revert back to as it was.
EDIT 2: So I managed to get all the files to the appropriate place using terminal and managed to get the script to run at boot. Alas, the phone doesn't detect my sdcard at all now and still throws the USB connectivity error at boot. Once I removed the sdcard, everything works alright. Also, I figured the solution to the reboot (haven't tested it yet as I wanted to resolve my sdcard first):
http://forum.xda-developers.com/showthread.php?t=2317432
EDIT 3: Got the reboot solve, but the sdcard can't be read and I tried plugging it into my other phone, the first partition is only read. I can't get minitool to even find the 2nd partition. I am thinking I need to get a card reader to plug it into my laptop. Anyway, I went through your script and open the log file it used, says that there's an invalid argument for mount. Any idea?
Click to expand...
Click to collapse
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
grim_ripper said:
Final Edit: Got it working! I had to re-partition my sdcard and made both partitions primary so maybe you might want to add that in OP as MiniTool by default selected the 2nd partition as logical
Click to expand...
Click to collapse
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.

NisJ said:
Why are you trying to mount /system as rw?
for getting init.d support you just have to download the apk from mentioned thread and install it, and then fallow instruction in app.
you can mount root as rw with the foll command if you want, and that is exactly what is done in he scripts as well if you will check:
Code:
mount -o remount,rw /
also to check if partition is created on sd card, type the command:
Code:
blkid
and see if
Code:
/dev/block/vold/179:34
is listed
if not post the output and i'll see what i can do.
EDIT: Correct, you need both the partitions to be primary. got out of my mind when posting the tutorial.
Click to expand...
Click to collapse
For whatever reason, my /etc folder is actually a link from /system/etc

Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!

grim_ripper said:
Could you post a way to revert back? I think my apps are acting all funny now and just want to revert back to before. Thanks!
Click to expand...
Click to collapse
The apps are behaving funny because you have lost their data as I had warned in the original post.
To fix do either of the foll:
1. reinstall app, and start fresh.
or
2. restore from Titanium backup if you had created...
or
3. copy paste 'Android' folder from sdcard2 if it is created to 'sdcard0'
To remove and revert, just delete the files from int.d, and stop scheduling it in SManger.
Note: to un schedule it from smanager, you first have to remove memory card, un schedule and then put in your memory card (this is coz when phone boots up, it is in standard way, with 8gb internal but, after script is executed SManager looses its data too.

How complicated will it be to make this compatible with 4.2.2?

grim_ripper said:
How complicated will it be to make this compatible with 4.2.2?
Click to expand...
Click to collapse
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.

NisJ said:
Ideally should be possible, unless something has changed majorly, but I haven't tried it, as am waiting for OTA update. If it is not forth coming in 2-3 weeks, may be tempted to flash nordic rom and try.
Click to expand...
Click to collapse
I did try but nothing happened, am guessing it has permission issues or something on those lines

grim_ripper said:
I did try but nothing happened, am guessing it has permission issues or something on those lines
Click to expand...
Click to collapse
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks

NisJ said:
Could you be more specific? Like system restarts etc...
Else in terminal try out what I Gave in post no 12 and give me what the output is for both the commands in the terminal.
Note: execute them with super user credentials.
Thanks
Click to expand...
Click to collapse
on the 4.2.2 update, it doesnt recognize the second partition even if it is formatted to primary and set to active. there r definitely some updates done in that field and plus i cant get the init.d rights on the phone as the test.log file is absent in the data folder..no matter what i do i just cant get it straight with the present procedure. please try it on 4.2 and there r more frequent updates on the nordiac then the local version. so i decided to flash it rather than waiting for ota update

[Q] Transerring files through CRM

I currently have no rom installed due to me wiping the cache and data. I'm trying to put the cyanogenmod 11 zip on the sd card by mounting usb storage, however it doesn't allow to copy it over to the sd and just says "discovering items". Upon mounting the usb storage it recommends me to fix the device as there are some problems with files, I tried the scan and fix options but it did not help.
Any help would be appreciated, thanks.

Azykk said:
I currently have no rom installed due to me wiping the cache and data. I'm trying to put the cyanogenmod 11 zip on the sd card by mounting usb storage, however it doesn't allow to copy it over to the sd and just says "discovering items". Upon mounting the usb storage it recommends me to fix the device as there are some problems with files, I tried the scan and fix options but it did not help.
Any help would be appreciated, thanks.
Click to expand...
Click to collapse
On some kernels you can use connection to PC when you are in recovery, on some not. I do not know on what kernel and recovery you are now. But it seems it is not working. So solution is to do nandroid restore if you made a nandroid backup in recovery. I suppose you did not, so now your option is to flash stock JB from Download Mode with Odin, and copy ROM while you are in system. Or use some other phone and put SD card in it and copy like that.

shut_down said:
On some kernels you can use connection to PC when you are in recovery, on some not. I do not know on what kernel and recovery you are now. But it seems it is not working. So solution is to do nandroid restore if you made a nandroid backup in recovery. I suppose you did not, so now your option is to flash stock JB from Download Mode with Odin, and copy ROM while you are in system. Or use some other phone and put SD card in it and copy like that.
Click to expand...
Click to collapse
Mmmhh ... I'm so shocked and curious. Turns, to move files in CWM could be done to the PC. Is it possible in CM11, senior? (noob quetions) Maybe one day I'll need it.
Thanks In Advance..
Sorry, quota "thanks" I have exhausted, a senior. :angel:

TPD-21 said:
Mmmhh ... I'm so shocked and curious. Turns, to move files in CWM could be done to the PC. Is it possible in CM11, senior? (noob quetions) Maybe one day I'll need it.
Thanks In Advance..
Sorry, quota "thanks" I have exhausted, a senior. :angel:
Click to expand...
Click to collapse
Some of it has, some do not. I am not sure what version has it and what do not. I remember some version, maybe CoCore opens internal and external storage on PC automatically. But I can't remember was it CoCore or some else.

shut_down said:
Some of it has, some do not. I am not sure what version has it and what do not. I remember some version, maybe CoCore opens internal and external storage on PC automatically. But I can't remember was it CoCore or some else.
Click to expand...
Click to collapse
Actually it's something interesting, a senior. Like when Windows95 new entry in our country. At that time the system "DOS For Windows" is still very familiar in computer lessons in our education. (Developing Countries). So we can still do "Copy" and "Paste" via diskette in the system "DOS". I think CWM is almost similar to the DOS system. I mean, CWM will be very useful if a time on the android main system can not be done. Of course may be done through CWM. cmiiw.

[Q]Supersu issue, re-rooting and other questions

Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1

Okkvltist said:
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Click to expand...
Click to collapse
Hello and welcome to xda,
Where exactly did you get the back-up from that you used to restore?
You were close it is TWRP or Team Win Recovery Project.
I believe the reason you can't install SuperSU is because you don't have a write protect removed kernel installed. You can find one here. Check out their related forums and see which one you like best. They are pretty much all great. Some aren't being supported anymore as a heads up. To flash a kernel, in case you didn't know how:
Go into Settings-About-Software information-More-Kernel version and write down the name of the Kernel
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button, until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your fastboot.exe from Android Studio or wherever you obtained it from (Mine is in C:\Users\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like:
Code:
HT42PXU89475 fastboot
if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Make sure your recovery.img or whatever the name of the recovery is, is in the folder you are currently in
11. Type
Code:
fastboot flash boot boot.img
in the command window
You should see something like:
Code:
C:\Users\yourusername\Android\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (12932 KB)...
OKAY [ 1.350s]
writing 'boot'...
OKAY [ 1.030s]
finished. total time: 2.385s
Your phone will still be in FASTBOOT USB mode
To test it out to see it was correctly flashed, reboot the phone
Go into Settings-About-Software information-More-Kernel version and see that the version changed
You can follow my little guide to use SD as Internal memory. Let me know if you need any help.

I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.

Okkvltist said:
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Click to expand...
Click to collapse
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.

blaqueknight said:
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
Click to expand...
Click to collapse
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.

Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
Click to expand...
Click to collapse
I'm sorry, please disregard that last comment. I was posting like your only problem was the Play Store. lol Sorry. But yea, check out those things I mentioned to you and you should be able to get SuperSU back up, if not I'll help you with anything else.

Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Click to expand...
Click to collapse
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"

Okkvltist said:
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Click to expand...
Click to collapse
Are you using Aparted? What was the method you used to partition? You should partition as ext4.

Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?

Okkvltist said:
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Click to expand...
Click to collapse
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.

blaqueknight said:
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
Click to expand...
Click to collapse
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2

Okkvltist said:
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Click to expand...
Click to collapse
Are you trying to partition the whole SDcard as ext4? To properly partition the card to be used with Link2SD you have to:
1. Delete the sdcard
2. Create a FAT32 partition of any size of your choosing
3. Format the FAT32 partition
4. Create an ext4 partition of any size of your choosing
5. Format the ext4 partition (this will take a long time, as it will create journals that are used to recover from an error such as removing the device while files are being copied)
After following those steps, Link2SD should properly create the script/mount and you should be able to link to your sdcard
If you are doing those steps perfectly and you still have an error, we have to find out another solution

Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.

Okkvltist said:
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Click to expand...
Click to collapse
I just made a couple of very simple tutorials to use Aparted and Link2SD and they are both working for me. Check them out: Aparted tutorial, Link2SD tutorial. I believe the ext2 that you are talking about is around the 10 second mark in the Link2SD video. Do you mean the /data/sdext2? That is just the name of the second sdcard partition.
If you can, you should buy the full copy of Link2SD to link external data and whatever other options become available.
The class of sdcard shouldn't have anything to do with the partition. That's just a classification of the speed of the card.
If needed, I'll make more videos to show exactly how everything is done. I think sometimes it is better to show than simply explain how something is done.
Hope this helps.

Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much

Okkvltist said:
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Click to expand...
Click to collapse
I'm happy it worked out good for you.
Yes, you are able to remove your sdcard. Be aware that your apps are on your sdcard so if you remove it, you remove them. They are placed on your sdcard and symlinked so Android thinks they are still on your phone in the place they would normally be. Nothing should crash, they just shouldn't show up. There is some great info about Link2SD here.

@blaqueknight..
nice videos man.

[Help Request] OS wiped

Dear community,
About a year after i really wanted to root my htc one mini 2, i decided I wanted to factory reset my phone.
So after this year I forgot everything i knew, and managed to wipe the whole OS...
I would really appreciate any hints that might help me to fix my phone again.
Info on where i'm standing with the problem:
1. I tried to find my stock ROM on this site and couldn't because under "firmware" i can only find 2.18.161.2, though mine is 2.18.166.1 - does this matter? It's the vodafone one, and they even have a nandroid backup for my version, but not the stock firmware.
2. I have TWRP installed, and the site tells me i need to have my bootloader locked to flash stock roms. I have no problem relocking or unlocking it, but in the relocked state, i can not access TWRP recovery and use the sideload feature to flash the rom. The phone always goes back to the bootloader screen and the title says " **security warning** ".
3. i would really like to get my phone back as close to it's stock state as possible.
I am kind of afraid of flashing the available stock firmware, as I don't know how to proceed from there without TWRP.
I read a lot about this topic, but i'm kind of loosing it right now...
Can some kind soul lend me their wisdom and help me out?
Would be much appreciated
mfG Montor

Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.

TryllZ said:
Hi,
You can either get put back everything to stock, as in flash stock recovery, relock the bootloader, get the available version from their site but the version number should be higher than the one already installed, however with S-Off you can flash any version.
Or
Leave everything as it is and perform a Nandroid restore.
What file are you getting from the website, is it RUU file, ROM, is it exe or zip ?, RUU will be beneficial to put back to complete stock with proper conditions met ?
WITH CUSTOM RECOVERY YOU CANNOT FLASH STOCK ROM.
Click to expand...
Click to collapse
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x

Montor said:
I would actually really like to put everything back to stock, because the reason for the root is somewhat gone now.
As already mentioned, I sadly can not find the stock recovery that i need.
I need the Vodafone x.xx.166.x format, and the closest i get would be the Vodafone x.xx.161.x format of the stock recovery.
What happens if i try to flash the available one? Do I brick my phone once again, or does it say something like "recovery version not matching device version" ?
Also, if by any chance the flash is successfull and the stock recovery x.xx.161.x is on my phone, how can i flash the stock firmware without TWRP?
Though I really like the idea of a more or less complete stock phone, I could totally go with the nandroid backup too.
The problem is, I already downloaded the files but as my OS is gone and i didn't turn on usb-debugging, i can not move a single file onto my device. (I assume that's the issue, because my adb push file /sdcard/TWRP/Backups didn't quite work...
Edit: Because you asked, I don't actually know what would be the best solution right now, but the only file fitting my device version is the nandroid backup, but there are RUUs for x.xx.161.x - which, as already mentioned, is the closest i can get to x.xx.166.x
Click to expand...
Click to collapse
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For RUU (zip file)
- Download the available RUU and rename it to 0P8BIMG.zip (I'm assuming its the same a normal HTC One Mini 2)
- Copy the file into the root of the MMC
- Insert MMC into device
- Boot up device and enter boot loader
- As the device enters bootloader it will automatically start flashing, if all conditions are met.
NB: I frankly can't remember if this will work with TWRP installed.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck

TryllZ said:
Here's how you can do it without developer option enabled.
- Make sure device is 100% charged, if you don't know how much charge exists, leave the device on charge for about 1-2 hours.
- Find an MMC of 4GB (Hoping your MMC slot is working)
- You will need Serial Number of your device for Nandroid restore, you can get it from the device box with IMEI stickers.
For Nandroid restore.
- THIS STEP NEEDS BE DONE FROM A PC, Extract all files from the Nandroid restore zip, connect the MMC to the PC.
- In the root folder of the MMC create a TWRP folder and inside it create a folder named BACKUPS and inside this create a folder named YOUR DEVICE SERIAL NUMBER (I haven't tested it with a different named folder so I don't know) inside this folder create a folder with the OS version number of your device and inside this folder place all extracted files.
- Put the MMC into the device.
- Enter TWRP and choose restore
- Locate the folder created in the earlier step, the TWRP Backup folder with files extracted in it.
- Let TWRP restore.
- As far as my knowledge goes it should work fine.
I will advise that you do a restore from Nandroid, because you have TWRP working this is the easiest method, to get the phone up and running then you can decide to go for RUU by enabling developer options and more.
I'm using a Nnadroid restore more than 6 months now, no problem whatsoever.
Good Luck
Click to expand...
Click to collapse
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow

Montor said:
That is exactly where I'm stuck with my nandroid backup.
I just can't seem to find a way to push the folder with all the files onto my sd-card.
I tried with "adb push \myfolder /sdcard/TWRP/Backups/myphonesnumberthingy", but it gives me "Device not found" error.
The device is connected, and with "fastboot devices" it shows in the list.
Did I miss something important here?
All the drivers are installed, and I shouldn't be able to lock and unlock the bootloader if the device wasn't properly connected right?
Edit: Nevermind, it seems I can't read. I will try to put my sd-card out of my phone and connect it to my pc somehow
Click to expand...
Click to collapse
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.

TryllZ said:
Use an MMC reader for working your MMC with a PC.
Your device connecting to your PC in the bootloader does not mean your commands will work, ADB works with device switched on, in bootloader its fastboot and NOT ADB.
Click to expand...
Click to collapse
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...

Montor said:
So i have an adapter for connecting the MMC to my PC.
I plug it in, and it shows me THIS.
Inside my recovery, if I use the file manager, I can't seem to access/find a single set of directories that looks like the one above...
Click to expand...
Click to collapse
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.

TryllZ said:
Have you extracted files from the Nandroid Backup zip and placed them into TWRP>Backups>Phone Serial Number>OS Version Number folder
Now, in TWRP choose Restore from the main screen, and locate the folder where your files are placed.
When in Restore, make sure you choose Storage: Micro SDCard at the top below Time, Battery and CPU.
Click to expand...
Click to collapse
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/

Montor said:
Yes i did extract the files in the zip, and placed them in TWRP/BACKUPS/serial/osversion.
But there is no way to locate it or access it.
When i open the file manager in TWRP, i see directories like "boot, cache, data, dev, devlog" etc, and also sdcard and external_sd.
External_sd is empty, and opening sdcard gives me only the directory created by my own nandroid backup, with the path /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32.
Edit: Okay now we are getting closer to solving this.
I tried to change TWRP backup from internal storage to micro sdCard - but it shows (0MB) beside it.
Choosing it either way, does nothing. The checkbox internal storage stays checked.
I'm going to restart my phone and see if something changes...
Edit2: Did nothing, unfortunately.
If i remove the card, the box can't be checked.
If i insert it again and tap on it, it stays highlighted for about 4 seconds and then internal storage is still checked :/
Click to expand...
Click to collapse
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.

TryllZ said:
Firstly it shouldn't show you 0MB for SDCard, anyway, place the extracted Nandroid files in the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder and then try again, if this folder is accessible then it should work.
MB: YOUR CONSTANT USE OF THE TERM FILE MANAGER IN TWRP IS GIVING ME AN IMPRESSION THAT YOU ARE ACCESSING THE FILE MANAGER IN TWRP WHERE AS YOU HAD TO PRESS THE RESTORE BUTTON FROM THE MAIN SCREEN, THE FILE MANAGER BUTTON IS DIFFERENT ALTOGETHER IN TWRP.
Click to expand...
Click to collapse
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?

Montor said:
Oh it appears I didn't mention this.
The folder i CAN see, is inside the internal storage under "/sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32" - and I can't access the internal storage, i would have pushed the files if that was possible.
No no, I use the backup function to locate my nandroid backup files.
But with the backup function, I couldn't change directories and look for files so I used the file manager to do that.
The file manager doesn't allow me to change to sd card either way, so that doesn't work.
Edit:
The sd-card i have inside my phone right now is 64gb big - is it possible that this is too big to be recognized?
I also have a 32gb one, would that make a difference?
Click to expand...
Click to collapse
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.

TryllZ said:
As per spec, this device supports 64GB too but I myself use a 32GB one, so yes you can try that and again you will need to access TWRP restore through the RESTORE button in TWRP main screen and NOT BACKUP button.
What you can do is copy the /sdcard/TWRP/BACKUPS/HT533WR02324/2016-07-17--08-52-32 folder into you SDCard TWRP folder and place the extracted files in this folder and try a restore.
Click to expand...
Click to collapse
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?

Montor said:
Okay it seems my 32gb one is broken, it's showing up but not as a mass storage.
Well if I could access the sd card with twrp at all, that would really help me - but I can't.
Backup botton and restore button behave the same when choosing the Micro SDcard (0MB).
And with the file manager, accessing the sd card gives me an empty directory...
Edit: Googling this problem tells me I need to format my card, as TWRP doesn't recognize it.
I read FAT32 somewhere, I read exFAT somewhere, what format does TWRP work with?
Click to expand...
Click to collapse
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
You mentioned its not showing as Mass Storage, what is it showing up as ?

TryllZ said:
First can I know if you can see any file/folder in SD when accessing it through Restore in TWRP ?
Format it as exFat, hopefully it should work..
Click to expand...
Click to collapse
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"

Montor said:
First, through restore I can't navigate to other folders at all.
All I can do there, is tapping on Internal storage and choosing micro SDcard - which doesn't work.
It's like TWRP knows there is a sd card in my phone, but somehow can't access it.
That's why I assume it's due to it's formatting.
Switching folders/directories is only possible with the file manager with the advanced button - but this only shows me two things.
1. External_sd --> shows me an empty directory
2. sdcard --> shows me the folder where TWRP created the backup folder when I did the backup myself. (I assume that's the internal storage because under the restore button, this is the only thing that i shows up)
I read somewhere, that exFAT is only recognized by TWRP if you have a newer version of the recovery installed.
I don't know exactly but the version i'm using is definitely on of the first versions that came out.
Also, I checked my SD-card on my laptop, and apparently it allready is exFAT.
Edit: I was talking about the 32gb card not showing up.
I don't think it really matters, but my description wasn't very accurate.
The SD-card (32gb) is shown as the SD-card like it should, but the PC doesn't show any kind of used/free space bar underneath it.
Also, opening it gives a message like "There is no card connected"
Click to expand...
Click to collapse
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.

TryllZ said:
The SDCard not showing free space bars is windows could possibly mean SDCard error.
FAT, FAT32 and exFAT work for Android so yes if you format it in any of these it ought to work. exFAT format is most commonly used in mobile devices in terms of SDCard.
Card disconnecting in Windows, I am guessing your card is having I/O issues, what this means is that if you try and format it and the MMC disconnects during the format process there is a chance it will be permanently damaged.
What you can do is just use Quick Format, this will not check for any errors, however if there is any sector errors in the MMC, flasing through TWRP could cause unexpected problems if that sector is accessed.
Advisably get a working 4GB SDcard to avoid any hiccups.
Click to expand...
Click to collapse
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.

Montor said:
I have the 64gb one i was always using, and the not working 32gb one.
Both are exFat.
I just wanted to know if it might work formatting the 64gb one
Edit: Concerning formatting, this is the thread I was referring to.
Click to expand...
Click to collapse
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.

TryllZ said:
The device supports 64GB and so does TWRP, now concerning your SDCard, yes it would work (as long as its hardware-error free)..
I'm using TWRP version 2.8.5.0 and my SDCard is exFAT and works fine with TWRP..could be that older versions of TWRP might not support exFAT but I personally can't confirm that as which is the older version that you are using.
Click to expand...
Click to collapse
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?

Montor said:
Update!
I realized, it's probably really the 64gb sd card, that's the issue here.
I took the 4gb one out of my fathers phone - bam.
TWRP recognized it immediately and restore is in progress!!!
Will keep updating!
Edit: IT F*ING WORKED!
Thank you SO much for your help!!!
Is there any way I can give you somethign in return?
Click to expand...
Click to collapse
Great...:good::good::good:
Frankly I never imagined it could be the 64GB, I was purely under the assumption TWRP would accept 64GB MMC, anyway I lacked that information but now I know.
Nope, its working now is more than enough for me.