Hi all I need a little help, I completed everything above without much problem, but when I flashed the newest twrp recovery, I did a backup first thing then when it was completed every file is in my internal storage and it's not showing up an sd card when I have a 16gb installed and I'm sure twrp is the step that caused this. I am still on OF1 rom. Thanks for any help!
The unlocking step overwrites the external (removable) SD card with a copy of the first 256 MB of your flash memory chip before it modifies the "aboot" partition.
A side effect of this is that the card won't mount correctly any longer without re-formatting it.
To be completely safe (you'll probably never need it), do a "raw copy" of the first 256 MB of the external SD card device to save the "debrick image", e.g. (as root)
Code:
dd bs=131072 count=2048 if=/dev/block/mmcblk1 of=/sdcard/SMN900V_debrick.img
This might take 20-30 seconds or so as you are reading and writing 256 MB of data.
Then, reformat the external SD card.
Separately, TWRP has a menu that allows you to choose between the output location for backups - either the internal memory, the external memory (SD Card), or - if you have an OTG cable, on an external USB device.
TWRP also has a file explorer if you want to move your saved backups to the external SD card. It's a little clunky, but it works. (You can also do this with a file explorer app with the phone normally booted as well if you prefer).
cheers
maybe you have to install sdfix since phones of the past couple years don't use sdcards, the system updates don't recognize cards
pltctytc said:
maybe you have to install sdfix since phones of the past couple years don't use sdcards, the system updates don't recognize cards
Click to expand...
Click to collapse
Nope, you just have to reformat the card and it'll be fine.
Sent from my SM-N900V using Tapatalk
Related
Hi,
I have a nexus one with Rom MIUI.
I have a sd card with these partitions:
3.16 GB -> FAT32
488 MB -> EXT 4
61 MB -> SWAP
I would like to migrate the sd card to one that I have of 16GB. What steps should I do to can migrate all.
Many thanks and sorry for my english!
Copy the contents of the card to a computer, partition new card and copy the backups to the appropriate partitions.
I'm going to assume your are running a custom ROM here, if your not, these directions may not work for you.
I actually just did this yesterday myself, so I can give you instructions on how I did it. I use CM7 with Apps2SD, and I'm assuming your MIUI is usind Apps2SD as well.
**With original SD card installed**1. Boot into recovery
2. Make a full backup (SYSTEM+SD-ext). The backup is stored on the SD card.
3. Now hook the phone up to your computer and copy the entire contents of the SD card to a folder on your computer (this can be done while in recovery or while booted into OS, it doesn't matter)
4. Shut down phone and remove original SD card and install new SD card
**With new SD card installed**5. Boot into recovery
6. Partition SD card the same as it was before (most common is SD-ext=1024, Swap=0, rest as USB storage, or whatever it's called)
7. While still in Recovery, mount the SD card as USB storage and hook the phone up to your PC
8. Take the files that you copied from your original SD card and copy them to the root of your new SD card (don't just drag and drop the fold you put the files in, but rather open up the folder and copy the contents of the folder over so that it looks just as it did when you had the original SD card installed)
9. This step can probably be skipped, but I did it anyway out of habit more than anything, but wipe and format SYSTEM, all CACHE options, and SD-ext, and BATTERY.
10. Still in RECOVERY, you'll want to select the option to RESTORE. It'll list all previous restores, just pick the latest one.
11. Once that is done, REBOOT SYSTEM and you should be up and running.
I have a nook color with dual boot from sd card. The sd card having an android 3.0 version.
After I got the 1.4.1 update, I noticed that I was able to access the sd card( the boot partition alone) from the stock OS boot of nook.
But now, dont know how, I dont see that anymore.
Was this a flawed update that was fixed or am I missing something.
Do help please.
I could really use the advantage of using the bootable sd card as a regular storage card when using the stock OS of nook. I prefer reading on the stock OS of nook.
Not sure why you're not seeing the SD card anymore, does it still boot?
SD card installs create multiple partitions on the SD card and the Nook will only be able to access the first one (boot). It should be accessible with any version of the Nook default OS.
You should have a media partition with a decent amount of room (1-5gb depending on NC version). That would give you more room than the 100-or-so mb on the boot partition.
Just found out that you can point the emmc install to see the "sdcard" partition of the sd card using the following info:
racks11479 said:
use root explorer and edit vold.fstab to "4" instead of "auto" for sdcard mount
Click to expand...
Click to collapse
Yes, I can boot from it. Every time I plug in the SD card, the notification already says that it is safe to remove the SD card. In the device Info part of the setting, the "Unmount SD card" is already greyed, though it does say that the SD card is found.
It is however useful for me to know that the boot partition should always be accessible.
I did remove the SD card a couple of times without unmounting it first, could this possibly have corrupted the card?
srn_28 said:
Yes, I can boot from it. Every time I plug in the SD card, the notification already says that it is safe to remove the SD card. In the device Info part of the setting, the "Unmount SD card" is already greyed, though it does say that the SD card is found.
It is however useful for me to know that the boot partition should always be accessible.
I did remove the SD card a couple of times without unmounting it first, could this possibly have corrupted the card?
Click to expand...
Click to collapse
Try to boot the uSD card (the one with Android 3.0 on it) and see what happens.
If it can, then it's good, if not, you can say it's corrupted.
Yes, I can boot from it. So I assume the card is OK
I plugged in other uSD cards and they get recognized fine. So I assume the Nook stock OS device recognition is OK.
I should probably recreate the boot partition as a last ditch effort
I had the same problem at first, but now I have mounted the correct sdcard partition that I wanted to mount.
I couldn't get it to work with editing the vold.fstab file at first. Then at some point after I manually mounted the correct partition through adb shell and edited the vold.fstab it now works.
Hello,
Will try to explain the situation to my best possible knowledge :
1. Was running Crash ROM 4.4.2 on Galaxy S4 i9500 , have got all the required apps installed and configured the way I wanted.
2. Running the stock kernel which comes with the Crash ROM installation.
3. Running Phillz touch recovery 6.3.xx
4. Have external micro sd card (16GB UHC SanDisk) . Crated 1st primary partition as FAT32 and 2nd primary as Ext3 for moving apps.
5. Did install Link2SD and correctly moved all apps linked to the 2nd external SD card partition.
6. Was able to connect a USB flash drive via female USB connector (host mode) and take titanium backup of all apps.
7. Everything mounted correctly and automatically, with correct permissions to read/write without me worrying or fixing any setting or changing anything.
Since I had everything in order, I thought of making a nandroid backup via Phillz recovery . The problem when I tried taking a nandroid baclup which presents custom backup option to either "/sdcard" or "/storage/sdcard1 (which i assume refers to external microSD card".
I tried taking a backup at both locations and was informed that I am short of space , the backup needed 4+GB whereas I had 2+GB on internal SD and 3+ GB on external microSD available.
So i thought to reboot and try making some space anywhere, thats when the nightmare started.
After reboot, now there was
1. A message for low space remaining
2. Google play store continually crashing and giving a "stopped" message.
I fixed the error no. 2 temporarily by uninstalling google play store (updates, cache and then the app itself).
However error no.1 persists, now when try running any app to see what and how much space is left in the internal and external SD cards, it seems that the internal SD card is not mounted somehow.
I have tried runnning ES explorer and it says no SD card found. Even though I can browse to the root partition. Then I tried Link2SD (which has an option of seeing storage info nicely) and I can that the bar for SD card is blank and all other places or mount points are mounted.
Even the apps residing on my external microSD 2nd partition are working fine, however I noticed that earlier the external microSD card, when seen from inside a booted and loaded ROM was mounted at the location " /storage/extSDcard , but now it is mounted at "/mnt/media_rw/extSDcard"
But my internal SD card is vanished, I cannot find any contents of the "internal SD" in any of the locations at /storage , /storage/emulated/legacy, /storage/emulated/0, /sdcard, /mnt/sdcard, /mnt/obb and possibly any other location I can think of.
I believe the mount points and logical links are different as seen by the phillz recovery (as there is no /storage/sdcard1 when seen from Es explorer) , and as seen when the ROM is fully booted and loaded, so when trying to take a nandroid backup via Phillz recovery, it might have messed up with the mount points and/or permissions.
I hate doing a complete re-flash of the ROM again and spending hours to get all the apps customized my desired way, with all widget settings.
I am not an expert or pro at android, hence I request your help to sort out the issue, and maybe send or guide me the default way the S4 handles mount points, so I can get back the SD card and also guide me how to make a the nandroid backup to avoid this fiasco again.
Thanks for reading.
I'm on a Redmi 3S with 16 GB internal storage which runs on unofficial version of LineageOS by Fedosis. I was not using an SD card, hence everything was in the internal memory itself.
As the app and app data is getting huge, I wanted to move this to an external storage. So I got a 32 gig SD card. While setting up the card, I used the option "as internal memory". After installation I could not access my phone memory. And when I rebooted to recovery via TWRP, I cannot see this SD card. Only thing I could see was phone memory. So it's kind of a complication to flash apps.
So I again formatted the SD card and set it up "as portable memory". Now I can access the phone memory normally and in TWRP also. But when I try to move the apps, [eg: Hearthstone, Flamingo, etc] it says, it's not possible.
So, how should I set up my new SD card, so that I can move the existing apps into it and also install new apps to the same SD card?
format as internal storage and then go to appsettings and manually move them to external memory. but this isnt supported by all apps.
to flash something with twrp than, you have to put the file you want to flash into /data/media/0/TWRP
merlin.berlin said:
format as internal storage and then go to appsettings and manually move them to external memory. but this isnt supported by all apps.
to flash something with twrp than, you have to put the file you want to flash into /data/media/0/TWRP
Click to expand...
Click to collapse
Thank you.
Are these files safe to delete? I was under the impression that with this being a 16gb phone I wouldn't be fighting for internal storage space after owning the phone just a few days and less than 10 installed apps.
Looks like your own backups... your internal storage wouldn't be full if you bothered to use a sd card.
If one does have an external SD card, I don't recall if TWRP defaults to storing there or if you need to select external SD - something to check on for TWRP newbies.
-n0cturne- said:
Looks like your own backups... your internal storage wouldn't be full if you bothered to use a sd card.
Click to expand...
Click to collapse
I've found TWRP to usually default to internal storage on every run, but once you set up the path/naming for your backups it usually sticks.
It seems like you are toying around with TWRP, possibly attempting to get ready to flash a custom rom. Given half the storage is system files, you'd barely be able to backup said default files to internal storage without running out of space.
You could always backup these files to a computer, delete them from the phone to free up enough space to download a rom (of which you should verify the md5 checksum), and hope everything goes perfectly.
If anything goes wrong, you'll need access to a computer and either use some advanced fastboot commands or.. an sd card, which you can easily swap on to a computer to download custom roms or backup files.
I would recommend getting a micro SD card for TWRP backups to avoid being fully dependent on a PC or internal storage. I like to have at least two TWRP backups on my micro SD. I know this phone works with 128GB - not sure about larger.