When trying to push new files to my LG G3 to fix the issue outlined here:
http://forum.xda-developers.com/showthread.php?t=2582142&page=178
Basically, can't get to recovery, or download and won't boot.
Terminal returns this instead of list of .img files:
ls /dev/sd *
TERMINAL RESPONSE: / dev / sda / dev / sda1 / dev / sda2 / dev / sda3
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
************************************************** *****************************************
Found invalid GPT and MBR valid; Converting MBR to GPT format in memory.
************************************************** *****************************************
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4746570D-B91E-4A91-917C-D94BCEBD34F3
Partitions table holds up to 128 entries
First usable sector in 34, last usable sector is 625142414
Partitions will be aligned on 2048-sector boundaries
Total free space is 310512237 sectors (148.1 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 52430847 25.0 GiB 0700 Linux data
2 52430848 314632191 125.0 GiB 0700 Linux data
^^^^ here is where the list of img files and their respective locations should be according to the guide. However, it does not show.
Any ideas?
Related
Hi everyone,
I have 16GB ADATA microSD card. After reformating through the recovery image to ext2,swapm and fat 14GB i used apps2sd for a while now. Today i wanted to wip my phone and all data on the microsd, so booted up recovery image and used Part SD to only fat32. I wanted to use the whole 16GB as a Fat32 drive again. But then I only got 14GB recognized in windows.
So i Tried to reformat again to swap,ext2 and Fat 12GB. But after trying to format back to 16GB FAT32 i lost another 2GB. I cant get the card to work in Windows anymore the only way i can access is through ADB.
Can someone help me to get my 16GB back?
j_love
update: i get the following when using parted
/dev/block # parted mmcblk0 print
parted mmcblk0 print
Model: SD SD (sd/mmc)
Disk /dev/block/mmcblk0: 12.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 12.0GB 12.0GB primary fat32 lba
What is the output of
Code:
parted -l
parted -l doesnt give me any output.
/ # parted -l
parted -l
/ #
Sounds like you have a corrupt partition table on your card. It's probably best to delete all the partitions on this card and start over BUT you should use a decent partitioning tool. Without meaning to be rude, it sounds like you are using Windows' built in (i.e. very basic) drive formatting tools and that you probably aren't that familiar with using parted on the command line. I would recommend using gparted, a graphical tool. You can use this either from a USB key http://gparted.sourceforge.net/liveusb.php or an Ubuntu live cd (appears as 'partition editor'). I find that disc partitioning is a great deal easier with graphics, i.e. in this case you can see what you are doing.
Thanks but I already used the liveCD of gparted. The main problem here is that my SDCARD is not recognized in Windows or in Linux. Also tryed Ubuntu and knoppix. I am not very familiar with linux but have some experience with command line tools.
The only way i can access the SDCARD is via adb on my Hero. Do you know any commands i could test? I already wiped the partition table and tried to make new partitions. But im stuck at 12GB.
The thing is that in Linux, you don't mount a device, you mount a file system. In this case that would translate to partitions (there are other cases but they are not relevant here). I would ask: if you cannot 'see' the card in windows or in linux and parted -l gives no output, where is this 12GB figure coming from?
Windows typically won't show a drive in 'my computer' if it doesn't recognise the partition format so you won't see any ext2 or ext3 partitions. You won't get any pop-ups on your desktop for unformatted space in Ubuntu either. Please could you confirm that you have tried the following:
In Ubuntu connect phone via USB to PC via (on phone) 'USB/ USB connected/ mount'. This won't affect adb.
Bring up Gparted and do 'gparted/refresh devices'
Select '/dev/sdb' or whatever your memory card appears as there- your main hard drive will be shown by default.
Tell us what you see now
I am attaching a screenshot of my SD card in my phone seen like this. It shows as sdc because I have two hard drives on my PC
ok done that. I got the following
/dev/sdf1 11.21GiB
/dev/sdf1 fat32 /media/disk 11.21GiB 11.26MiB 11.20GiB lba
/dev/sdf1 11.21GiB
/dev/sdf1 fat32 /media/disk 11.21GiB 11.26MiB 11.20GiB lba
Click to expand...
Click to collapse
If I understand correctly the above appears to show a single FAT32 partition on this device of 11.21GiB with 11.26MiB used. My suggestion is to use Gparted to delete all the partitions on this card (don't forget to hit 'apply') and then see how much unformatted space you have. Bear in mind that you must unmount your filesystem (mounting/unmounting can be done within gparted) before playing around with any of the partitions on it. You can then create new partitions on the card (again, don't forget to 'apply changes'). You will likely have to reboot your phone to seem them there.
Does this work?
ok. I can delete create resize partitions but the diskspace is still 11.21GiB
If you delete all the partitions on the device, how much 'unallocated space do you have after 'apply changes'? when you unmount and the remount the card?
unallocated space is 11.21GiB
okay try creating a single new partition on the card and then using the 'check' option in gparted. What happens then?
Created a ext2 partition and checked it. Check was fine without errors but space is still 11.21GiB
Okay, assuming your card is still on /dev/sdf1 please try the following:
Code:
sudo fdisk /dev/sdf
This enters the fdisk shell. Then type
Code:
p
and paste the output here. You can exit fdisk with the command
Code:
quit
Got the following output
[email protected]:~$ sudo fdisk /dev/sdf
The number of cylinders for this disk is set to 1463.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065e4e
Device Boot Start End Blocks Id System
/dev/sdf1 1 1463 11751516 83 Linux
Command (m for help): quit
does anyone have the output of fdisk->p of there ADATA 16GB microSD CARD???
I tried to change the clyinders but need the correct value
Code:
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00065e4e
Device Boot Start End Blocks Id System
/dev/sdf1 1 1463 11751516 83 Linux
Click to expand...
Click to collapse
Well that's interesting. This appears to show a single ext3 partition toward the end of the card (unless I've got this completely wrong). What do you get for
Code:
parted
print
with the same partion(s)?
for reference on my 8GB card I get (on laptop):
Code:
sudo fdisk
p
gives
Code:
Disk /dev/sdb: 7948 MB, 7948206080 bytes
255 heads, 63 sectors/track, 966 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000beb03
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 902 7245283+ c W95 FAT32 (LBA)
/dev/sdb2 903 966 514080 83 Linux
and
Code:
sudo parted /dev/sdb
print
gives
Code:
Model: HTC Android Phone (scsi)
Disk /dev/sdb: 7948MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 7419MB 7419MB primary fat32 boot, lba
2 7419MB 7946MB 526MB primary ext2
Im Not at home right now but will post the Output tomorrow.
But I think you got it wrong. The start cylinder is 1 and the end is at 1463.
I can use fdisk to manipulate the cylinders but the size stays the same. This is really a big problem. There ar3 more users on the net with similar problems but without a solution. Hope we can get this back to normal.
I get the following for :
[email protected]:/# parted /dev/sdf
GNU Parted 1.8.8
Using /dev/sdf
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: SD/MMC Card Reader (scsi)
Disk /dev/sdf: 12.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 12.0GB 12.0GB primary fat32 lba
(parted)
(parted) quit
and the following for
[email protected]:/# fdisk /dev/sdf
The number of cylinders for this disk is set to 1463.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdf: 12.0 GB, 12035555328 bytes
255 heads, 63 sectors/track, 1463 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005c05a
Device Boot Start End Blocks Id System
/dev/sdf1 1 1464 11753440 c W95 FAT32 (LBA)
Cheers, any chance of posting that again and using the 'code' tags in the message editor? It's a bit hard to read in the body of your post like this
thanks
I think after running wrong exit_recovery.zip, I managed to trash partition table/GPT - or some other combination of stupidity - hoping someone can help..
CWM Recovery Log
Starting recovery on Mon Jun 25 21:11:17 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v5.8.2.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /staging ext3 /dev/block/mmcblk0p4 (null) 0
5 /data ext4 /dev/block/mmcblk0p8 (null) 0
6 /boot emmc /dev/block/mmcblk0p10 (null) 0
7 /recovery emmc /dev/block/mmcblk0p9 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
...
[recovery session] Fdisk
/tmp # fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 63.5 GB, 63577260032 bytes
4 heads, 16 sectors/track, 1940224 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
[recovery session] Parted
/tmp # ./parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Error: /dev/block/mmcblk0: unrecognised disk label
Hypothesis
By doing exit recovery opt 1a http://forum.xda-developers.com/showthread.php?t=1514088 I was able to bring up the virtuousprime ROM boot, but virtuous failed (reboot) after trying to format /data.
I dd'd the first 8096 bytes of mmcblk0 and they are all zeros?
From CWM, I am able to mount partitions mmcblk0p1, mmcblk0p3, mmcblk0p5.
So from all that, I am thinking I need to flash MBR, replace GPT on LBA 1? If this is correct, does anyone have a stock GPT for the tf201?
I can then format /data (mmcblk0p8) and I think my ROMs will then work.
kind regs,
Based on the information here: https:// en.wikipedia.org/wiki/GUID_Partition_Table#Partition_table_header_.28LBA_1.29, replacing LBA 1 will only fix the GPT header. Since you said that the first 8096 bytes were all zeros, it would seem that those would fall into LBA 2, 3, etc., corrupting the partition table.
But since you said that CWM can mount your partitions, you might be able to use GPT fdisk's recovery features to fix the problem. I don't know if anyone has compiled it for Android though Please note that the regular fdisk cannot handle GPT, only MBR.
When you said "flash MBR", what exactly do you mean? GPT and MBR are two different partition structures and if you replace either one with the other, the partition table will be lost and you won't be able to mount any partition.
Was thinking about building LBA0 and LBA 1 separately, was going from that Wikipedia article, "...Legacy MBR information is contained in LBA 0, the GPT header is in LBA 1.." and I thought - perhaps naively - that an fdisk command with /mbr option would sort out LBA0, then I worry about GPT in LBA1, but maybe I am confusing fdisk /mbr option with another command (old DOS)?
I have all the partition offsets and disk size from backup (/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001/block/mmcblk0/..) and know what the partition table should look like; there was no "Partition 9", I made this up because there was 1024 unaccounted bytes after mmcblk0p8 (/data) ends:
Disk size: 1241744336 bytes
Partition 1 (/system): start 74752; End 1123328; Size 1048576
Partition 2 (/cache): start 1123328; End 1999872; Size 876544
Partition 3 (/misc): start 1999872; End 2003968; Size 4096
Partition 4 (/staging): start 2003968; End 3096576; Size 1092608
Partition 5 (/btmac): start 3096576; End 3106816; Size 10240
Partition 6 (/?): start 3106816; End 3107840; Size 1024
Partition 7 (/?): start 3107840; End 3118080; Size 10240
Partition 8 (/data): start 3118080; End 124173312; Size 121055232
Partition 9: start 124173312; End 124174336; Size 1024
Given that /system mounts, I think if I had a stock dump from a tf201 of bytes 0-74752 might also be an alternative - I could verify the GPT table against above before I put it in.
Another option I can think of, comes from reference I see to a "backup GPT" held in last sector of GPT disks? If you look at partition offsets above, there is 1024 bytes at the end where I may get this information - but I think injecting in a dump of those first 74k bytes into mmcblk0 - as above - would be safer.
damonbrisbane said:
Was thinking about building LBA0 and LBA 1 separately, was going from that Wikipedia article, "...Legacy MBR information is contained in LBA 0, the GPT header is in LBA 1.." and I thought - perhaps naively - that an fdisk command with /mbr option would sort out LBA0, then I worry about GPT in LBA1, but maybe I am confusing fdisk /mbr option with another command (old DOS)?
Click to expand...
Click to collapse
I wouldn't suggest doing that. That would create a hybrid MBR. When a hybrid MBR disk is read using MBR, only the first four partitions can be visible (after redefining the partition table in LBA0). If the disk is read using GPT, all the partitions will be visible. I don't know if Android and Linux prefer MBR over GPT, but if they do, you might lose access to partitions 5-8.
By the way, the '/mbr' option is for the diskpart tool from MSDOS and Windows
damonbrisbane said:
Another option I can think of, comes from reference I see to a "backup GPT" held in last sector of GPT disks? If you look at partition offsets above, there is 1024 bytes at the end where I may get this information - but I think injecting in a dump of those first 74k bytes into mmcblk0 - as above - would be safer.
Click to expand...
Click to collapse
You're absolutely right. I had forgotten about this. Do you happen to know if those mmcblk0p# partitions are visible when the tablet is plugged into a Linux computer? If so, GPT fdisk can restore the partition table and GPT header from the backup GPT.
You would run something like this to restore the backup GPT:
http://paste.kde.org/488054/
EDIT: I found a version of gdisk compiled for Android by meghd00t (http://forum.xda-developers.com/showpost.php?p=24805392&postcount=74). You may be able to restore the backup GPT directly from the tablet
Download link from the post: http://dl.dropbox.com/u/64885133/gptfdisk.zip
Thanks Chen, i plan to try the gptfdisk tonight when I get home from work and can post the result.
One thing i'm not sure about is access mmcblk0 from linux - does this mean I can access the internal mmcblk0 of the tf201 directly through a linux device? Right now I access mmcblk0 solely through adb shell to CWM recovery.
damonbrisbane said:
Thanks Chen, i plan to try the gptfdisk tonight when I get home from work and can post the result.
One thing i'm not sure about is access mmcblk0 from linux - does this mean I can access the internal mmcblk0 of the tf201 directly through a linux device? Right now I access mmcblk0 solely through adb shell to CWM recovery.
Click to expand...
Click to collapse
No problem There's also an option to backup the GPT header and partition table to file. I'd suggest doing that just in case anything goes wrong.
I'm not entirely sure if the internal memory can be accessed directly from Linux. But from what I've been reading in the forums today, it seems that it might not possible (I'm pretty new to Android).
Hopefully gptfdisk will work via adb shell
Whew, we're off life support! and more importantly - my wife wont kill me for an Unauthorised Brick to The Birthday Device
Steps Performed
ADB - Write backup GPT to LBA1 mmcblk0
~ # ./gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Unsupported GPT version in backup header; read 0x00000000, should be
0x00010000
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: not present
Creating new GPT entries.
Command (? for help): r
Recovery/transformation command (? for help): ?
b use backup GPT header (rebuilding main)
c load backup partition table from disk (rebuilding main)
…
? b
Recovery/transformation command (? for help):
? c
Warning! This will probably do weird things if you've converted an MBR to
GPT form and haven't yet saved the GPT! Proceed? (Y/N): Y
Caution! After loading partitions, the CRC doesn't check out!
Recovery/transformation command (? for help): p
Disk /dev/block/mmcblk0: 124174336 sectors, 59.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 2E8491CC-AFFC-43B9-B1C4-97D2F258BE1C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 124174302
Partitions will be aligned on 2048-sector boundaries
Total free space is 75709 sectors (37.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 74752 1123327 512.0 MiB 0700 AP
2 1123328 1999871 428.0 MiB 0700 CC
3 1999872 2003967 2.0 MiB 0700 MC
4 2003968 3096575 533.5 MiB 0700 UP
5 3096576 3106815 5.0 MiB 0700 PR
6 3106816 3107839 512.0 KiB 0700 YU
7 3107840 3118079 5.0 MiB 0700 CA
8 3118080 124173311 57.7 GiB 0700 UA
Recovery/transformation command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): Y
OK; writing new GUID partition table (GPT) to /dev/block/mmcblk0.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
~ #
ADB/CWM - Exit recovery and attempt Virtuousprime ROM install
I then did exit recovery as per 1a http://forum.xda-developers.com/showthread.php?t=1514088
Upon reboot Virtuousprime wouldn't go as far as it got before. I went back into adb shell and did wipe data:
Wipe data/factory reset
Formatting /data
Error mounting /data !
Skipping format...
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Note the error on /data. Could not format /data either using the CWM mounts and storage menu. I named the partitions I knew about and formatted /data (mmcblk0p8) from adb shell:
Number Start End Size File system Name Flags
1 38.3MB 575MB 537MB ext4 system
2 575MB 1024MB 449MB ext4 cache
3 1024MB 1026MB 2097kB misc
4 1026MB 1585MB 559MB ext3 staging
5 1585MB 1591MB 5243kB fat32 btmac
...
8 1596MB 63.6GB 62.0GB ext4 data
mke2fs -t ext4 /dev/block/mmcblk0p8
I then found that CWM data/factory reset went through without errors:
Wipe data/factory reset
Formatting /data
Formatting /cache
..
Data wipe complete
And subsequently exit recovery and virtuous prime rom have installed OK, tested across reboot and shutdown
Cheers!
damonbrisbane said:
Whew, we're off life support! and more importantly - my wife wont kill me for an Unauthorised Brick to The Birthday Device
Click to expand...
Click to collapse
Haha, I'm glad I was able to help
There is an issue with my SDcard, I don't know how it happened, I did nothing special on it.
It appears as unformatted BUT, I know that the data is still there because the CWM manages to browse files if I get into the menu "install zip from /sdcard1", but it can't see anything if I try a "restore from sdcard1"...
Weird huh ?
So I have an ubuntu build and I'd like to try to repair the "masterboot" with your help
I never did this before so I don't really know what I need, SDCard is 32 GB class 10.
When I plug my phone from CWM and enable the mount the SDcard on usb I got this error message :
Error mounting: mount: /dev/sdb1: can't read superblock
Here is the result of the "fdisk -l" command :
Code:
Disk /dev/sdb: 32.0 GB, 32018268160 bytes
32 heads, 63 sectors/track, 31019 cylinders, total 62535680 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4d544f4f
Device Boot Start End Blocks Id System
/dev/sdb1 2048 62535679 31266816 b W95 FAT32
Which actually looks weird, I thought that my sdcard were ext4 formated, well but I am not 100% sure about that...
Here the result of the command "fsck -y /dev/sdb1"
Code:
fsck from util-linux 2.20.1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
/
Contains a free cluster (2). Assuming EOF.
FAT32 root dir starts with a bad cluster!
What else can I do ?
Ok great...
Thanks anyway...
For information, I managed to backup data from the SDcard using testdisk, then using again testdisk I tried a repair, and it actually rewrote the superblock and the card is alive again without wiping
hi,
I completed Android OS porting on Wandboard Quad successfully.
I done Porting of Android on SD card & run Hello World program by Android Studio in Wandboard.
I check these SD cards by 6 different way of disk partitioning functions
1. fdisk
2. gdisk
3 parted
4. df
5. GParted
6. Disk utility
I cant see same info.
example.
Precompiled with gdisk
[email protected]:/# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Disk /dev/sdb: 31116288 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): B7F3D463-C2C3-4559-85BF-CFAC7156E521
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31116254
Partitions will be aligned on 1-sector boundaries
Total free space is 23363125 sectors (11.1 GiB)
Number Start (sector) End (sector) Size Code Name
1 15128 151279 66.5 MiB 0700 Microsoft basic data
2 151280 347943 96.0 MiB 8300 Linux filesystem
4 3086112 7836303 2.3 GiB 8300 Linux filesystem
5 347945 1921255 768.2 MiB 8300 Linux filesystem
6 1921257 2972651 513.4 MiB 8300 Linux filesystem
7 2972653 2995343 11.1 MiB 8300 Linux filesystem
8 2995345 3018035 11.1 MiB 8300 Linux filesystem
Click to expand...
Click to collapse
gdisk for source which i compiled
[email protected]:~# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.8
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Warning! Secondary partition table overlaps the last partition by
80929 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 31116288 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): FA423ED4-626A-48B6-9387-0EB1AB1A680D
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31116254
Partitions will be aligned on 1-sector boundaries
Total free space is 98274 sectors (48.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 16384 147455 64.0 MiB 0700 Microsoft basic data
2 147456 344063 96.0 MiB 8300 Linux filesystem
4 2555904 31197183 13.7 GiB 8300 Linux filesystem
5 344065 1392639 512.0 MiB 8300 Linux filesystem
6 1392641 2441215 512.0 MiB 8300 Linux filesystem
7 2441217 2457599 8.0 MiB 8300 Linux filesystem
8 2457601 2473983 8.0 MiB 8300 Linux filesystem
Click to expand...
Click to collapse
I try to change shell script which do partitioning but no success.
Does anyone face same problem?
Howdy. Just a question: if I select "use as internal memory" for my 128 GB SD card I inserted in my Nokia 1, does that mean I won't be able to access the said SD card if I try to plug the Nokia 1 to a PC?
Jem2291 said:
Howdy. Just a question: if I select "use as internal memory" for my 128 GB SD card I inserted in my Nokia 1, does that mean I won't be able to access the said SD card if I try to plug the Nokia 1 to a PC?
Click to expand...
Click to collapse
Hi,
I've used an 8 Gig SanDisk MicroSD card as internal memory on my Nokia 1.
The short answer to your question is no, probably not. at least not without a bit of effort.
I just plugged the SD card into a Linux box, which give me the below data
Code:
[[email protected] ~]$ sudo fdisk -l /dev/sdc
Disk /dev/sdc: 7.4 GiB, 7948206080 bytes, 15523840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 98FA1F61-0482-4F31-A074-73550CC9B369
Device Start End Sectors Size Type
/dev/sdc1 2048 34815 32768 16M unknown
/dev/sdc2 34816 15523806 15488991 7.4G unknown
[[email protected] ~]$
[[email protected] ~]$
[[email protected] ~]$
[[email protected] ~]$ sudo gdisk -l /dev/sdc
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 15523840 sectors, 7.4 GiB
Model: USB3.0 CRW -SD
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 98FA1F61-0482-4F31-A074-73550CC9B369
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 15523806
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 34815 16.0 MiB FFFF android_meta
2 34816 15523806 7.4 GiB FFFF android_expand
When I plugged it into one of my Win10 boxes and it just offered to format it for me.
I'm not sure what file system is in use as it was reported as unknown. You'll need to figure out what file system is in use and install whatever tools your PC OS needs to work with that file system.