Oneplus X E1001 running the latest nightly
I receive this message when trying to make the SD card into internal storage;
179_64 private failed with 400
I understand from perusal of other phones that this may be a flaw with marshmallow rather than the phone itself. Can someone clarify? Ive tried two different sd cards each on two X's, was not in issue with the stock release OOS when I bought near the initial chinese release
Much belatedly, I ran into this problem as well. logcat says:
03-11 13:40:55.441 222 233 I sgdisk : ***************************************************************
03-11 13:40:55.441 222 233 I sgdisk : Found invalid GPT and valid MBR; converting MBR to GPT format
03-11 13:40:55.441 222 233 I sgdisk : in memory.
03-11 13:40:55.441 222 233 I sgdisk : ***************************************************************
03-11 13:40:55.441 222 233 I sgdisk : Warning! Secondary partition table overlaps the last partition by
03-11 13:40:55.441 222 233 I sgdisk : 33 blocks!
03-11 13:40:55.441 222 233 I sgdisk : You will need to delete this partition or resize it in another utility.
Click to expand...
Click to collapse
I tried formatting it in windows using a card reader, but the problem continued. Finally, I gave up and downloaded a partition manager for android - Parted4Android, on the play store. This was able to format the sd card and create a new partition, but that only got me back to square one - the sd card was formatted for "portable storage" again, and I was never asked to set up the card.
Related
Please can someone help me to resize the system partition of an Android JB 4.2.2 on cubieboard?
Image: sun7i_android_sugar-cubieboard2-8192cu.img
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204
2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2)
3) To burn to flash: PhoenixSuit1.0.6
unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 1048576
user_type = 0x2
so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
but :
1) In installed android, the system has only 512MB and not 1GB as show.
2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )
Here is my devices list and size:
Code:
NAME SIZE MOUNTPOINT LABEL
nand 3.8G
|-nand1 16M Volumn
|-nand2 16M
|-nand3 16M
|-nand4 512M
|-nand5 512M
|-nand6 16M
|-nand7 32M
|-nand8 320M
|-nand9 16M PRIVATE
|-nand10 256M
`-nand11 2.1G
mmcblk0 14.4G
|-mmcblk0p1 900M /
`-mmcblk0p2 13.5G EXTRA
icemagno said:
Please can someone help me to resize the system partition of an Android JB 4.2.2 on cubieboard?
Image: sun7i_android_sugar-cubieboard2-8192cu.img
I need more room (it's only 512MB) to install apps.
Well, the APP disk space (nand partition) is very small and the internal "sdcard" too big.
When I install a few applications the space runs out and the system becomes unstable.
I need to increase the nand and decrease internal sdcard to gain more room to my apps...
Well, I started the process by using the tools:
1) To unpack/repack: imgRePacker_204
2) The image ROM: sun7i_android_sugar-cubieboard2-8192cu.img (Android 4.2.2)
3) To burn to flash: PhoenixSuit1.0.6
unpacking the ROM creates a folder named sun7i_android_sugar-cubieboard2-8192cu.img.dump
So, somewhere in internet I see to change the sys_partition.fex file, and search the system nand partition:
Code:
;------------------------------>mmcblk0p8/nande
[partition]
name = data
size = 1048576
user_type = 0x2
so, I change 1048576 to 2097152 (2097152 * 1024 = 2GB)
but :
1) In installed android, the system has only 512MB and not 1GB as show.
2) By increasing this value, nothing happens when I repack back to IMG and flash to the nand.
(all unpak, change, pack, flash process is fine ! )
Here is my devices list and size:
Code:
NAME SIZE MOUNTPOINT LABEL
nand 3.8G
|-nand1 16M Volumn
|-nand2 16M
|-nand3 16M
|-nand4 512M
|-nand5 512M
|-nand6 16M
|-nand7 32M
|-nand8 320M
|-nand9 16M PRIVATE
|-nand10 256M
`-nand11 2.1G
mmcblk0 14.4G
|-mmcblk0p1 900M /
`-mmcblk0p2 13.5G EXTRA
Click to expand...
Click to collapse
Use this software, search it on google and install it on your PC, then partition you SD
MiniTool Partition Wizard Pro v7.1
azithro said:
Use this software, search it on google and install it on your PC, then partition you SD
MiniTool Partition Wizard Pro v7.1
Click to expand...
Click to collapse
"3) To burn to flash: PhoenixSuit1.0.6"
This implies using NAND .... SD is not in the context.
Thanks anyway!
I have a NOOK tablet 16GB that is somehow locked from modifying partitions
I have tried
the repart image , which has worked many times for me in the past
the AdamOutler Ubuntu Disk
formatting / wiping options in various versions of CWM and TWRP
fastboot erases
fastboot formats
dd'ing /zero to various partitions
parted
sgdisk
a zillion scripts
something at a low level is preventing modifications to the partitions
Im wasting far too much time on this , but I hate being beat (-:
I have a backup of rom and factory , and dd images of stock parttions so I am 100% comfortable with something that
will COMPLETELY ZAP the device
if I boot a known good CM10 image from SD card, it fails to boot , I was assuming if I could get a running android from the card, I'd have access to lots of tools... , but it just fails to tun CM10
any help appreciated.
Thanks
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
sagirfahmid3 said:
To completely zap the device, erase the partition table. That will leave you one, giant, unallocated space.
From there, you need to recreate all partitions from scratch.
You will not be able to boot without a bootable CWM SD, so have that handy.
Click to expand...
Click to collapse
Thanks for responding, Yes, I have tried multiple ways to to zap the table and it doesnt stick.
sgdisk -Z, sgdisk -z parted,
no matter what I do the partitions remain untouched.
I reboot and it still boots into an old stock OS that has a FC shortly after startup, and the internal recovery (factory) , which I can not overwrite, gives the please restart and try again message.
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
mikeataol said:
hmm,
I WAS able to get a CM7 SD card image to boot and run
appears to work "normally" , but Internal storage shows as "not available" in settings
Click to expand...
Click to collapse
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
sagirfahmid3 said:
You're supposed to do:
# gdisk
# o
# w
# q
That will for sure give you an empty partition table. You probably forgot to write the changes before exiting.
Click to expand...
Click to collapse
Hi, no, I didnt forget to "write" after the "o"
/tmp # ./gdisk /dev/block/mmcblk0
./gdisk /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
Caution: invalid backup GPT header, but valid main header; regenerating
backup header from main header.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.
Warning! One or more CRCs don't match. You should repair the disk!
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: damaged
****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Command (? for help): o
o
This option deletes all partitions and creates a new protective MBR.
Proceed? (Y/N): y
y
Command (? for help): w
w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
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.
/tmp # q
/tmp #
after reboot
Command (? for help): p
p
Disk /dev/block/mmcblk0: 31105024 sectors, 14.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): CE21388C-B927-4A5C-91CE-DBD1DE4AB3BC
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30535678
Partitions will be aligned on 256-sector boundaries
Total free space is 1285 sectors (642.5 KiB)
Number Start (sector) End (sector) Size Code Name
1 256 511 128.0 KiB 8300 xloader
2 512 1023 256.0 KiB 8300 bootloader
3 1024 31743 15.0 MiB 8300 recovery
4 32768 65535 16.0 MiB 8300 boot
5 65536 163839 48.0 MiB 8300 rom
6 163840 262143 48.0 MiB 8300 bootdata
7 262144 1019903 370.0 MiB 8300 factory
8 1019904 2273279 612.0 MiB 8300 system
9 2273280 3145727 426.0 MiB 8300 cache
10 3145728 5242879 1024.0 MiB 8300 media
11 5242880 30535639 12.1 GiB 8300 userdata
Humm...wow, that's pretty crazy. Try writing zeroes to your emmc and then retrying.
# dd if=/dev/zero of=/dev/block/mmcblk0
I attempted to install Jasmine rom, after it failed twice I tried to recover and failed at that. Then after trying to resinstall twrp i got it into a bootloop and no recovery and no download and no recovery.
I need the following .img for the LG G3 vs985 to try to use the method in the link below:
NEED THESE FILES:
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
http://forum.xda-developers.com/showthread.php?t=2582142
Here are the files from 10b:
http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/stock_partitions/10B
Be careful (those are things that mere mortals like I wouldn't mess with )
THANK YOU!!
markfm said:
Here are the files from 10b:
http://downloads.codefi.re/autoprime/LG/LG_G3/VS985/stock_partitions/10B
Be careful (those are things that mere mortals like I wouldn't mess with )
Click to expand...
Click to collapse
Thank you very much. now i just need to figure out why It wont show me the locations of all those files when i enter the terminal in linux... I'm getting something like this:
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 Microsoft Basic data
2 52430848 314632191 125.0 GiB 0700 Microsoft Basic data
Only this was copied from another post. I am using linux.
Any suggestions?
No idea. What you posted doesn't make sense to me. Hopefully someone else will pop in.
I copied from another post but I am getting roughly the same response when I rum the gdisk Dev command in Linux terminal. It does recognize the device as lg. But it doesn't appear to find the device while running the command to see the list of img files.
Also having trouble coding the file extension to push the img files with dd command.
Hello!
Today I flashed the official CyanogenMod 12.1 Nightly Build (cm-12.1-20150902-NIGHTLY) ROM on my SII.
I am happy about the stagefright fixes but I can't encrypt the device anymore.
Logcat:
Code:
I/Cryptfs ( 1851): Check if PFE is activated on Boot
E/Cryptfs ( 1851): Cannot open footer file /efs/metadata for get
E/Cryptfs ( 1851): Error getting crypt footer and key
D/VoldCmdListener( 1851): cryptfs getpw
D/VoldCmdListener( 1851): cryptfs clearpw
E/Cryptfs ( 1851): Cannot open footer file /efs/metadata for get
D/Cryptfs ( 1851): Just asked init to shut down class main
D/Cryptfs ( 1851): unmounting /data succeeded
I/Cryptfs ( 1851): keymaster version is 2
I/Cryptfs ( 1851): Using scrypt for cryptfs KDF
E/Cryptfs ( 1851): Cannot open footer file /efs/metadata for put
E/Cryptfs ( 1851): Error writing the key to the end of the partition
E/Cryptfs ( 1851): Error enabling encryption after framework is shutdown, no data changed, restarting system
I checked the efs partition. It's good. I can even find my "old" metadata file since the phone was encrypted before.
When I set SELinux to permissive it's looks good till the reboot.
Logcat before the reboot:
Code:
E/Cryptfs ( 1850): not running with encryption, aborting
W/Cryptfs ( 1850): upgrading crypto footer to 1.3
D/Cryptfs ( 1850): Just asked init to shut down class main
D/Cryptfs ( 1850): unmounting /data succeeded
I/Cryptfs ( 1850): keymaster version is 2
I/Cryptfs ( 1850): Using scrypt for cryptfs KDF
D/Cryptfs ( 1850): Just triggered post_fs_data
D/Cryptfs ( 1850): post_fs_data done
D/Cryptfs ( 1850): Just triggered restart_min_framework
I/Cryptfs ( 1850): Using scrypt for cryptfs KDF
I/Cryptfs ( 1850): Enabling support for allow_discards in dmcrypt.
I/Cryptfs ( 1850): load_crypto_mapping_table: target_type = crypt
I/Cryptfs ( 1850): load_crypto_mapping_table: real_blk_name = /dev/block/mmcblk0p10, extra_params = 1 allow_discards
I/Cryptfs ( 1850): Encrypting ext4 filesystem in place...
I/Cryptfs ( 1850): Encrypting group 0
I/Cryptfs ( 1850): Encrypting from sector 0
I/Cryptfs ( 1850): Encrypted to sector 4526080
I/Cryptfs ( 1850): Encrypting from sector 4538368
I/Cryptfs ( 1850): Encrypted to sector 4579328
I/Cryptfs ( 1850): Encrypting from sector 4587008
...
I/Cryptfs ( 1850): Encrypting group 1
I/Cryptfs ( 1850): Encrypted to sector 16763904
I/Cryptfs ( 1850): Encrypting from sector 16777216
...
I/Cryptfs ( 1850): Encrypting group 2
I/Cryptfs ( 1850): Encrypted to sector 33861632
I/Cryptfs ( 1850): Encrypting from sector 33865728
...
I/Cryptfs ( 1850): Encrypting group 15
I/Cryptfs ( 1850): Encrypted to sector 235502592
I/Cryptfs ( 1850): Encrypting from sector 251658240
I/Cryptfs ( 1850): Encrypted to sector 251923456
Code:
D/CryptKeeper( 5706): Going into airplane mode.
D/CryptKeeper( 5706): Encryption progress screen initializing.
D/CryptKeeper( 5706): Acquiring wakelock.
V/CryptKeeper( 5706): Encryption progress: 100
After the reboot the device wants to be unlocked but after entering the password it tells me "your password is correct but your data is corrupt, you need to reset".
Am I right about SELinux being the problem?
How can I fix this?
Cheers s0r3_x
Update:
Same errors with cm-12.1-20150903-NIGHTLY.
Works with cm-12.1-20150904-NIGHTLY!
Maybe it's better post the problem in the developer thread. Lysergic and others developer can see the log. The link is: http://forum.xda-developers.com/galaxy-s2/orig-development/rom-cyanogenmod-12-1-nightly-builds-t3147661
@Lysergic Acid
minghi1 said:
Maybe it's better post the problem in the developer thread. Lysergic and others developer can see the log. The link is: http://forum.xda-developers.com/galaxy-s2/orig-development/rom-cyanogenmod-12-1-nightly-builds-t3147661
Click to expand...
Click to collapse
I made this account to post in that thread but the forum tells me that I need ten post before I am allowed to post in a developer thread.
But yes I agree it would be better to post there...
s0r3_x said:
I made this account to post in that thread but the forum tells me that I need ten post before I am allowed to post in a developer thread.
But yes I agree it would be better to post there...
Click to expand...
Click to collapse
No problem to post here, @king_ahmed already mentioned me to call my attention. Sir, if SELinux is blocking encryption I need a full logcat of the issue to see what's happening.
No problem to post here, @king_ahmed already mentioned me to call my attention. Sir, if SELinux is blocking encryption I need a full logcat of the issue to see what's happening.
Click to expand...
Click to collapse
Then a thanks @king_ahmed for getting @Lysergic Acid attention an thanks @Lysergic Acid for not ignoring me .
Here are the logs:
logcat_SELinux_enforce.log: pastebin.com/whxG3qTR
logcat_SELinux_permissive.log: pastebin.com/0FSYqRcc
s0r3_x said:
Then a thanks @king_ahmed for getting @Lysergic Acid attention an thanks @Lysergic Acid for not ignoring me .
Here are the logs:
logcat_SELinux_enforce.log: pastebin.com/whxG3qTR
logcat_SELinux_permissive.log: pastebin.com/0FSYqRcc
Click to expand...
Click to collapse
I've already fixed the SELinux issues present in your logs. Please try the latest nightly and report if the issue persists.
Lysergic Acid said:
I've already fixed the SELinux issues present in your logs. Please try the latest nightly and report if the issue persists.
Click to expand...
Click to collapse
The build installed on my SII is cm-12.1-20150903-NIGHTLY-i9100.
s0r3_x said:
The build installed on my SII is cm-12.1-20150903-NIGHTLY-i9100.
Click to expand...
Click to collapse
The denial present in your log is that: denied { search } for name="/" dev=mmcblk0p1 ino=2 scontext=u:r:vold:s0 tcontext=ubject_r:efs_device_file:s0 tclass=dir
On this commit: http://review.cyanogenmod.org/#/c/107862/ you can see me allowing vold to search in the /efs. It was merged on September 2nd. So how's that possible?
Lysergic Acid said:
The denial present in your log is that: denied { search } for name="/" dev=mmcblk0p1 ino=2 scontext=u:r:vold:s0 tcontext=ubject_r:efs_device_file:s0 tclass=dir
On this commit: review.cyanogenmod.org/#/c/107862/ you can see me allowing vold to search in the /efs. It was merged on September 2nd. So how's that possible?
Click to expand...
Click to collapse
I don't know sorry I really don't that is why I am posting here.
If you look at line 40 in the logcat_SELinux_enforce.log you see the build installed is cm-12.1-20150903.:
Code:
I/cm ( 1884): Welcome to Android 5.1.1 / CyanogenMod-12.1-20150903-NIGHTLY-i9100
Or line 13 in the logcat_SELinux_permissive.log:
Code:
I/cm ( 1880): Welcome to Android 5.1.1 / CyanogenMod-12.1-20150903-NIGHTLY-i9100
Update:
I flashed the new nightly (CyanogenMod-12.1-20150904-NIGHTLY-i9100) and tried again.
It worked!!!
Big thanks @Lysergic Acid !
Still I don't get it. It should have worked with yesterdays nightly.
@Lysergic Acid: Do you want the new logs?
Not sure where to write this, but i tried to encrypt phone several times and it failed, with todays night build (cm-12.1-20150905-NIGHTLY-i9100).
Same error: Cannot open footer file /efs/metadata. Tried both CWM and TWRP, also resized partition, to give it space for encryption key.
Code:
setprop vold.decrypt trigger_shutdown_framework
e2fsck -f /dev/block/mmcblk0p10
resize2fs /dev/block/mmcblk0p10 740000
Tried to give it 16kb and 180MB, it failed... goes into reboot. Same if done via adb
Code:
vdc cryptfs enablecrypto inplace password mypass
Any ideas?
Thank you
s0r3_x said:
Update:
I flashed the new nightly (CyanogenMod-12.1-20150904-NIGHTLY-i9100) and tried again.
It worked!!!
Big thanks @Lysergic Acid !
Still I don't get it. It should have worked with yesterdays nightly.
@Lysergic Acid: Do you want the new logs?
Click to expand...
Click to collapse
I'm glad it worked, no need for more logs then.
potentia said:
Not sure where to write this, but i tried to encrypt phone several times and it failed, with todays night build (cm-12.1-20150905-NIGHTLY-i9100).
Same error: Cannot open footer file /efs/metadata. Tried both CWM and TWRP, also resized partition, to give it space for encryption key.
Code:
setprop vold.decrypt trigger_shutdown_framework
e2fsck -f /dev/block/mmcblk0p10
resize2fs /dev/block/mmcblk0p10 740000
Tried to give it 16kb and 180MB, it failed... goes into reboot. Same if done via adb
Code:
vdc cryptfs enablecrypto inplace password mypass
Any ideas?
Thank you
Click to expand...
Click to collapse
Do you have anything under /efs/metadata? If not, this error is acceptable. Also, you don't need to resize the block of it, this is all wrong man, you're not resizing the /efs partition to be bigger, just the block of it, probably even making it smaller than the default.
Please give me a logcat of the problem when you try to encrypt the phone.
Lysergic Acid said:
Do you have anything under /efs/metadata? If not, this error is acceptable. Also, you don't need to resize the block of it, this is all wrong man, you're not resizing the /efs partition to be bigger, just the block of it, probably even making it smaller than the default.
Please give me a logcat of the problem when you try to encrypt the phone.
Click to expand...
Click to collapse
I was under impression that key was residing in the last 16KB of data partition, that's why I decreased mmcblk0p10 from 786432 to 786428 blocks, leaving 4 blocks (16KB) free.
There is no /efs/metadata file
logcat: s3.amazonaws.com/xda-share/logcat.txt
Thank you
@Lysergic Acid
Had a chance to look at log?
Thank you
Still cannot encrypt @Lysergic Acid
Updated to cm 13
adb log:
Code:
02-13 17:21:12.809 1844 1894 E Cryptfs : Bad magic for real block device /dev/block/mmcblk0p10
02-13 17:21:12.815 1844 1894 E Cryptfs : Orig filesystem overlaps crypto footer region. Cannot encrypt in place.
This is my first post, please bear with me if I'm asking an obvious question. I am trying to update my WinCE 6.0 sat nav to an Android OS (I believe my current version is known as S100 and (I think) I am upgrading to S150)
Here's what I have been supplied by the manufacturer of my sat nav:
SD Boot Fusing Tool
2 x BIN files to be fused to the SD card; SD-bl1-8k.bin and u-boot_sdboot.bin
A Panasonic SD card formatter
I have followed their rough instructions which are converted from Chinese:
1. Format SD card to FAT32 format performing complete erase
2. Add the 2 x BIN files to the tool for fusing to the SD card. This is where I am stuck.
I am receiving the following error message "Can't Read MBR Sector from Drive"
To confirm the SD card is not the issue I have swapped SD cards, run chkdsk /f against the drive and used the Rufus tool to obtain the following log output:
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Windows 7 MBR
Found volume GUID \\?\Volume{d9671328-5dee-11e5-825a-5442490c7ece}\
Successfully remounted Volume{d9671328-5dee-11e5-825a-5442490c7ece}\ on G:\
Found USB 2.0 device 'HSDPA MMC Storage USB Device' (1C9E:6061)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 483, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x065A8C2D
Drive has a Windows 7 Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 3.7 GB (3979345920 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Can anyone help me as I do not understand what the issue is. This is the first time I have attempted this type of thing.
Cheers
Chris
This is the error I am seeing:
66chrisscott99 said:
This is my first post, please bear with me if I'm asking an obvious question. I am trying to update my WinCE 6.0 sat nav to an Android OS (I believe my current version is known as S100 and (I think) I am upgrading to S150)
Here's what I have been supplied by the manufacturer of my sat nav:
SD Boot Fusing Tool
2 x BIN files to be fused to the SD card; SD-bl1-8k.bin and u-boot_sdboot.bin
A Panasonic SD card formatter
I have followed their rough instructions which are converted from Chinese:
1. Format SD card to FAT32 format performing complete erase
2. Add the 2 x BIN files to the tool for fusing to the SD card. This is where I am stuck.
I am receiving the following error message "Can't Read MBR Sector from Drive"
To confirm the SD card is not the issue I have swapped SD cards, run chkdsk /f against the drive and used the Rufus tool to obtain the following log output:
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (FAT32)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Using Windows 7 MBR
Found volume GUID \\?\Volume{d9671328-5dee-11e5-825a-5442490c7ece}\
Successfully remounted Volume{d9671328-5dee-11e5-825a-5442490c7ece}\ on G:\
Found USB 2.0 device 'HSDPA MMC Storage USB Device' (1C9E:6061)
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 483, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x065A8C2D
Drive has a Windows 7 Master Boot Record
Partition 1:
Type: FAT32 LBA (0x0c)
Size: 3.7 GB (3979345920 bytes)
Start Sector: 2048, Boot: No, Recognized: Yes
Can anyone help me as I do not understand what the issue is. This is the first time I have attempted this type of thing.
Cheers
Chris
This is the error I am seeing:
Click to expand...
Click to collapse
Might help you to provide a pic of the unit itself. There are literally hundreds of these devices.
Sent from my SGH-I337M using Tapatalk
Flukester69 said:
Might help you to provide a pic of the unit itself. There are literally hundreds of these devices.
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Good shout. Here it is:
m.alibaba.com/product/1447649060/ZESTECH-2-DIN-CAR-DVD-STEREO.html
And the spec:
m.alibaba.com/product/1447649060/ZESTECH-2-DIN-CAR-DVD-STEREO/specifications.html
Sorry, I'm too new to post urls ?
Sent from my D6603 using Tapatalk
Bump. Anyone? Ty
Sent from my D6603 using Tapatalk
Solved. It appears that you cannot write to that sector unless you run the application as an administrator
Sent from my D6603 using Tapatalk