Not really big news for anyone who's installed SDE and poked around a bit, but I thought I'd post this anyway.
Taken from a 16GB Archos 101. Your results may differ.
Code:
Disk /dev/mmcblk0: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 5 1605 51200+ 83 Linux
/dev/mmcblk0p2 1605 5511 125023 83 Linux
/dev/mmcblk0p3 5512 6489 31296 83 Linux
/dev/mmcblk0p4 6490 16384 316640 83 Linux
Disk /dev/mmcblk1: 15.3 GB, 15388901376 bytes
4 heads, 16 sectors/track, 469632 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/mmcblk1p1 1 469632 15028216 c Win95 FAT32 (LBA)
Being MMC rather than MTD devices, it ought to be possible to repartition to shuffle some space around, perhaps gaining as much as 50MB extra space for /data.
Additionally, for custom firmwares maybe even repartitioning mmcblk1 may be possible, to create an alternate partition to mount /data/ to.
Of course, for fear of ruining my 101 I have only used fdisk for read-only operations.
don't forget mmcblk2..
it's the external sdcard
Of course I was examining the internal flash storage of the device.
Having my 101 for just under 3 weeks I'm not quite brave enough to repartition mmcblk0, as it would be very difficult to recover an operational system if this were to not go as well as expected. :>
I'm hoping that someone with a little more insight or perhaps a little braver than I could chime in on the possibility.
why won't you repartition (shrink p1 and append other partitions) blk1? (8 / 16 GB storage)
don't touch blk0 when you don't have to
chulri said:
why won't you repartition (shrink p1 and append other partitions) blk1? (8 / 16 GB storage)
don't touch blk0 when you don't have to
Click to expand...
Click to collapse
This was of course my suggestion for alternate firmwares that can take advantage of this.
Moved to general as not android development
Hi all,
So I've made a few backup images of my nook and want to be able to access the files on there without problems. I'm not the most knowledgeable Linux guy but have a Kubuntu VirtualBox image lying around for when I decide to compile Rockbox and such. I've also got Cygwin installed, but never expect it to do anything correctly, really. I haven't really come across any Windows tools that'll do the trick for me, so I want to know what I'm doing wrong with my parameters for the 'mount' command in Linux. What I really want right now is to get into the the system partition (#5).
Now I don't really know how to use mount beyond a little bit of googling, so I likely missed something here, but anyway, this is what I did:
I ran
Code:
fdisk -l nook_1.0.0_backup.img
and got this:
Disk nook_1.0.0_backup.img: 1958 MB, 1958739968 bytes
128 heads, 32 sectors/track, 934 cylinders, total 3825664 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: 0x00000000
Device Boot Start End Blocks Id System
nook_1.0.0_backup.img1 * 32 155647 77808 c W95 FAT32 (LBA)
nook_1.0.0_backup.img2 155648 188415 16384 c W95 FAT32 (LBA)
nook_1.0.0_backup.img3 188416 577535 194560 83 Linux
nook_1.0.0_backup.img4 577536 3792895 1607680 5 Extended
nook_1.0.0_backup.img5 577568 1167359 294896 83 Linux
nook_1.0.0_backup.img6 1167392 1658879 245744 c W95 FAT32 (LBA)
nook_1.0.0_backup.img7 1658912 2150399 245744 83 Linux
nook_1.0.0_backup.img8 2150432 3792895 821232 83 Linux
I multiplied 577568 by 512 to get an offset of 295698432, and knew that the system partition uses ext2 by running 'mount' in the nook's shell, so then I ran:
Code:
mount -o loop,offset=295698432 -t ext2 nook_1.0.0_backup.img /media/n2e
and keep getting this error message:
wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases, useful info is found in syslog - try
dmesg | tail or so
trying dmesg | tail yielded this gibberish:
[ 6690.080964] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081015] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081081] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081131] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081181] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081231] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081286] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081337] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081387] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
[ 6690.081437] VbglR0HGCMInternalCall: vbglR0HGCMInternalPreprocessCall failed. rc=-2
I also tried using dd to extract that partition (which I also did correctly if you go by file size, which is identical to the file size listed when I extract it via 7-zip in Windows) and then tried to mount that, but got the same message. I'm thinking this is all a simple syntactical error...any ideas? roustabout? ros87?
Wait, so this piece of software does the trick in Windows:
http://www.diskinternals.com/linux-reader/
But I'd still like to know how to mount correctly.
Double posting will make you quite popular with the moderators,.. not!
I answered you here.
very simple bash script:
Code:
#!/bin/bash
if test $# -lt 2; then
echo "usage: $0 [image] [mount point] <partition number>"
exit
fi
if test -z $3
then
number=1
else
number=$3
fi
mount -o loop,ro,offset=$(parted $1 unit B print | grep "^ $number" | sed "s/\s$number\s*\([0-9]*\)B\s*.*/\1/") $1 $2
To run this commands you need a rooted device with BusyBox and parted. Using stock partition layout. You can change the partition layout to get more or less than 2GB of size for the data partition:
[MOD][GUIDE]Partition your internal memory for better App management (Pit Files)
List of devices by name:
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
Click to expand...
Click to collapse
List of fdisk for all given partitions:
Command (needs Superuser or equivalent and Busybox):
su
find /dev/block/platform/dw_mmc/ -name 'mmc*' -exec fdisk -l {} \; > /sdcard/list_of_sgs2_partitions.txt
Click to expand...
Click to collapse
Code:
Disk ./mmcblk0boot0: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot0 doesn't contain a valid partition table
Disk ./mmcblk0boot1: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0boot1 doesn't contain a valid partition table
Disk ./mmcblk0p12: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p12 doesn't contain a valid partition table
Disk ./mmcblk0p11: 12.3 GB, 12356419584 bytes
4 heads, 16 sectors/track, 377088 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
./mmcblk0p11p4 1 1 0 0 Empty
Partition 4 does not end on cylinder boundary
Disk ./mmcblk0p10: 2147 MB, 2147483648 bytes
4 heads, 16 sectors/track, 65536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p10 doesn't contain a valid partition table
Disk ./mmcblk0p9: 536 MB, 536870912 bytes
4 heads, 16 sectors/track, 16384 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p9 doesn't contain a valid partition table
Disk ./mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p8 doesn't contain a valid partition table
Disk ./mmcblk0p7: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p7 doesn't contain a valid partition table
Disk ./mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p6 doesn't contain a valid partition table
Disk ./mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p5 doesn't contain a valid partition table
Disk ./mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p4 doesn't contain a valid partition table
Disk ./mmcblk0p3: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p3 doesn't contain a valid partition table
Disk ./mmcblk0p2: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p2 doesn't contain a valid partition table
Disk ./mmcblk0p1: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p1 doesn't contain a valid partition table
Disk ./mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
./mmcblk0p1 1 1923456 15387647+ ee EFI GPT
Partition 1 does not end on cylinder boundary
Mounted filesystems:
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 415M 32K 415M 4096
/mnt/asec 415M 0K 415M 4096
/mnt/obb 415M 0K 415M 4096
/system 503M 429M 74M 4096
/cache 98M 4M 94M 4096
/efs 19M 8M 11M 4096
/data 1G 666M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 2G 9G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
/mnt/sdcard/external_sd 29G 24G 5G 32768
temporal fstab:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p9 on /system type ext4 (ro,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p4 on /mnt/.lfs type j4fs (rw,relatime)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/259:3 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
tmpfs on /mnt/sdcard/usbStorage type tmpfs (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000)
/dev/block/vold/179:25 on /mnt/sdcard/external_sd type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/external_sd/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/org.ais.archidroid-1 type vfat (ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
AdamOutler said:
Hey guys. I'm doing some work to figure out how to recover Galaxy Nexus devices which are hard-bricked.. ie.. they have a bad or no bootloader installed.
the boot sequence
1. IROM - the Internal ROM which cannot be rewritten on the device. This loads the XLoader.
2. XLoader/MLO - This completes the initialization of the processor and memory, and loads up the relatively huge U-Boot ( Samsung modified this and calls it SBL)
3. UBoot/SBL - This "Bootloader" is almost a complete operating system. The U-Boot initializes the screen, provides Odin mode, Fastboot Mode as well as loading the kernel/recovery and provides a UART debugging mode (Yet to be unlocked).
4. Kernel - Once we reach this point, it's all clear.. the kernel is linux which loads android and all sorts of other things.
The Problem
People are bricking their devices at stage 2 and 3 of this boot sequence... This leaves them unable to boot Fastboot or Odin. The device is 100% interchangable with a brick. These devices are ending up hard bricked.
The solution
We must come up with a way to undo the hard brick. Here are some things i'm looking at to use the native hardware to recover itself.
When you plug in the device (when off), you will immediately notice a Texas Instruments D010 device gets enumerated. This is a debug mode for the processor.
Code:
Bus 001 Device 023: ID 0451:d010 Texas Instruments, Inc.
We've started looking at some bootloader output here: http://forum.xda-developers.com/showthread.php?t=1461986
You can find information about the OMAP4 bootloaders here: http://omapedia.org/wiki/Bootloader_Project
Help
I need help locating drivers to initialize the 0451:d010 device and make it readable from within Linux or Windows.. Generally Linux is easier to find appropriate drivers.
I could use some help collecting more reading materials and resources.
I think together as a community we can take care of this problem.
Click to expand...
Click to collapse
AdamOutler said:
There's more to the boot then the OP mentioned... there's 6 partitions involved, not 4.
irom = hard coded
IBL/PBL = initial bootloader and primitive bootloader
SBL = Secondadary Bootloader finds linux
param = contains paramaters to run the phone and required for boot.
SBL2 = download mode (included in SBL)
PIT = Partiton Information Table
Don't touch any of these files.
If you touch the param.ifs, the phone can still boot, however you will see a black screen if something goes wrong.
Code:
BOOT 00000000 0000 0003FFFF 0001
PIT 00040000 0001 0003FFFF 0001
EFS 00080000 0002 009FFFFF 0028
SBL 00A80000 002A 0013FFFF 0005
SBL2 00BC0000 002F 0013FFFF 0005
PARAM 00D00000 0034 004FFFFF 0014
KERNEL 01200000 0048 0077FFFF 001E
RECOVERY 01980000 0066 0077FFFF 001E
FACTORYFS 02100000 0084 11E7FFFF 047A
DBDATAFS 13F80000 04FE 085FFFFF 0218
CACHE 1C580000 0716 022FFFFF 008C
MODEM 1E880000 07A2 00C7FFFF 0032
07D4 1F500000
Click to expand...
Click to collapse
Aditional links:
* Definitive guide to Bricking *
[Guide] Types of Android backups
[REF] GT-I9100 PIT v Flash Analysis
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
[GUIDE] Making Dump Files Out of Android Device Partitions
/sdcard
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?
gyurman said:
This is nice, thank.
But where is from block device the sdcard. How working the "vold"?
How can I partition sdcard with fdisk or with parted?
Click to expand...
Click to collapse
Partition the sdcard from clockworkmod recovery
Thanks, but I want use parted, or fdisk. But what mmcblk0? use sdcard? mmcblk0p11?
Good day to all...
I have reached a point where I need to ask for help, because I have been busy for days now.
This is my situation: I have a Samsung 860 evo 1TB ssd, which I want to put in my shield 2015 Pro.
I have already successfully placed a Samsung evo 860 500gb ssd in my shield 2017 Pro.
First I have removed the 500gb SSHD from the shield and dd for windows in accordance with
the well-known method:
dd if = \\? \ Device \ HarddiskX \ Partition0 or = firstpart.bin ount = 6899870 to created the firstpart.bin.bin file
With: dd if=\\?\Device\Harddisk2\Partition0 of=lastpart.bin skip=976773158 bs=512 I created the lastpart.bin file.
After this I write the firstpart.bin to the 1tb ssd. Then I patched the lastpart.bin on my synology using the command:
./shield_pro_new_disk_gpt_calculator lastpart.bin 1000204886016 new_lastpart.bin
Using following command to write the correct lastpart.bin to the new 1TB disk.
Code:
dd if=new_lastpart.bin of=\\?\Device\Harddisk3\Partition0 bs=512 seek=1953525158
But when I put the ssd in the shield and close the shield, I only get a black screen and windows shows "APX" in device manager.
What am I doing wrong? Can some maybe upload a working lastpart.bin file to "Mega or Google drive" for me to try please?
disk info:
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 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: dos
Disk identifier: 0x6318a3f8
kind regards,
yuseigachi said:
Good day to all...
I have reached a point where I need to ask for help, because I have been busy for days now.
This is my situation: I have a Samsung 860 evo 1TB ssd, which I want to put in my shield 2015 Pro.
I have already successfully placed a Samsung evo 860 500gb ssd in my shield 2017 Pro.
First I have removed the 500gb SSHD from the shield and dd for windows in accordance with
the well-known method:
dd if = \\? \ Device \ HarddiskX \ Partition0 or = firstpart.bin ount = 6899870 to created the firstpart.bin.bin file
With: dd if=\\?\Device\Harddisk2\Partition0 of=lastpart.bin skip=976773158 bs=512 I created the lastpart.bin file.
After this I write the firstpart.bin to the 1tb ssd. Then I patched the lastpart.bin on my synology using the command:
./shield_pro_new_disk_gpt_calculator lastpart.bin 1000204886016 new_lastpart.bin
Using following command to write the correct lastpart.bin to the new 1TB disk.
Code:
dd if=new_lastpart.bin of=\\?\Device\Harddisk3\Partition0 bs=512 seek=1953525158
But when I put the ssd in the shield and close the shield, I only get a black screen and windows shows "APX" in device manager.
What am I doing wrong? Can some maybe upload a working lastpart.bin file to "Mega or Google drive" for me to try please?
disk info:
Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 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: dos
Disk identifier: 0x6318a3f8
kind regards,
Click to expand...
Click to collapse
It worked, close thread.
yuseigachi said:
It worked, close thread.
Click to expand...
Click to collapse
What did you do to fix this? I have a 2TB 850 Evo I am trying to install and I have followed the instructions down to a T and am getting the black screen as well.
Thanks !
Is Netflix and Amazon Prime Video still outputs in 4k with the new drive?