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
Related
Any one know command to mtty for atom exec\orsio n725 or RoverPC G5.
Phone connect to pc by rs-232, standart command not work
PS sorry for my english
Sorry, just want to understand further, why you using a serial cable (RS-232) to connect to your PC. is your phone hanged at bootloader mode?
Winterice said:
Any one know command to mtty for atom exec\orsio n725 or RoverPC G5.
Phone connect to pc by rs-232, standart command not work
PS sorry for my english
Click to expand...
Click to collapse
mtty is made for HTC devices. Atom is made by Quanta. I've been looking for the same tool myself. have you tried putty? If I'm not mistaken, you are trying to reformat the DOC? or upgrade the device thru mtty?
I have looked into the things we can upgrade from SDCARD flashing, and DOC.IMG is one of the option. I think this will change the format of DOC. One way to get a copy of this DOC.IMG is to dump the ROM thru SDCard using buzz romdumper64.
Please let me know of your developments.
Phone in bootloader, i am try dump rom. if plug phone with USB mtty doesn't see phone. if use command 'r' phone write message Format DOC.OK
Sorry for my English.
This experiments with the MTTY.
This experiments to copy ROM to the SD card or file.
I'm Running MTTY.
connecting PC and the Rover G5 (Atom Exec/Orsio N725), using a serial cable (RS-232).
Run bootloader mode.
On the PC screen :
-----------------
*******Beginning System Initialization*******
Run Mode = 104 MHz
Turbo Mode = Run Mode
MemClk = 104 MHz
Bus Mode = NORMAL
SDCLK[1] = MemClk (SDRAM Clk)
SDCLK[0] = MemClk/2 (Sync. FLASH Clk)
Mode = RUN
Boot FLASH in Asynchronous mode
******************************************************
OEMInitDebugSerial using STUART888
Microsoft Windows CE Ethernet Bootloader built Jun 13 2006 20:41:44
Copyright © 2006 Microsoft Corporation
Portions copyright © 2006 Intel Corporation
Original MSC0 12801282
New MSC0 12807FF2
New MDREFR = 0x11E018
New SXCNFG 40044004
Flash type L18
main:InitDisplay()
InitLCDCtrl..
ClearFrameBuffer..0xA6000480
+Check LCM ID:
==PreBL_Ver = 0.0.0
==2nd_BL_Ver = 0.0.0
Ethernet Boot Loader Configuration:
0) IP address: 0.0.0.0
1) Subnet mask: 0.0.0.0
2) # bootme's: 0
3) Boot delay: 0 seconds
4) DHCP: Disabled
5) Reset to factory default configuration
6) Launch existing flash resident image at startup
7) Program RAM image into FLASH (Disabled)
8 ) Program SMSC MAC address
9) Boot device order: SMSC -> PCMCIA S0 -> PCMCIA S1
D) Download image now
E) Erase flash image
L) Launch existing flash resident image now
U) Download os image now (USB1.1)
O) Overwrite eboot image now (USB1.1)
H) Jump to DM
I) Sim Lock
------------------
But ...
There are undocumented commands.
If press "R" - a message on the screen
Formating DOC.
OK
So there are undocumented commands
we are interesting other command
It would help us if we get hold of Service Manual.
Winterice said:
Phone in bootloader, i am try dump rom. if plug phone with USB mtty doesn't see phone. if use command 'r' phone write message Format DOC.OK
Click to expand...
Click to collapse
Have you tried buzz grab_it ROM dumper? it worked perfectly well with the Atom. It dumped everything to SD Card. You just have to break it apart and identify the sections.
For the Atom:
diskimg.nb0
eboot.nb0
dm.nb0
flash.img
agent.mot
mot.mot
cpld.img
assetinf.img
extended.img
MDOC.img
what particularly interest me is MDOC.img because I believe we can change DOC format with this.
our device have 192 mb rom, i or Alex_beda try this dumper today
This dumper not working.
Message in the screen "cannot create file!"
Using the miniSD 2 GB Kingmax
May be need to use mini SD less 1 GB?
Or using any other dumper?
alex_beda said:
This dumper not working.
Message in the screen "cannot create file!"
Using the miniSD 2 GB Kingmax
May be need to use mini SD less 1 GB?
Or using any other dumper?
Click to expand...
Click to collapse
you have to modify the name of SDCard. It is named "memory card" in your device. the program looks for "Storage Card". Search this value using registry editor.
"Folder"="\Storage\Card"
jiggs said:
you have to modify the name of SDCard. It is named "memory card" in your device. the program looks for "Storage Card". Search this value using registry editor.
"Folder"="\Storage\Card"
Click to expand...
Click to collapse
Thank you!
I'm downloading dump in the miniSD card.
But...
Problem.
Dump size 128 MB maximum
ROM size in my divice 192 MB.
How downloading full size (192 mb)?
alex_beda said:
Thank you!
I'm downloading dump in the miniSD card.
But...
Problem.
Dump size 128 MB maximum
ROM size in my divice 192 MB.
How downloading full size (192 mb)?
Click to expand...
Click to collapse
Your ROM chip size is 192MB. BUT I think, your ROM system size is only 64mb. Same as ATOM. The rest is only persistent storage, extended partition, and checksum partition.
to verify, you can pdocread the memory layout of your device. don't forget to install the RAPI before pdocread; otherwise, it will not work.
my ELF's mac address may be lost
every times, when my elf restart,
a document named HTCExcpthLog_mmdd_hhmmss.txt will be build in SDcard at \storage card\HtcLog\
mmdd_hhmmss is the restart time.
hi all, i'm pretty new to android development.
i'm wondering if there is a method to boot up from "hard disk" instead of using the SD when using ubuntu on TF201.
there is some test made with stock rom and "dd" with /dev/zero and /dev/null.
Code:
From Gentoo chrooted into Android ( Stock TF201 ROM ) [ 16GB sd class 2 ]
sd read : 16.3 MB/s
sd write: 03.3 MB/s
hd read : 26.7 MB/s
hd write: 11.2 MB/s
i've extracted the initrd image of the 1st post and i think that modify the 'init' script ( and the scripts inside script/ folder ) can mount different partition on /root dependig on user choice.
so the question is 2:
is it possible to change the partition table of the TF201?
is it possible to ask which partition mount into /newroot (or /root) ??
Thanks in advance,
tux_mind.
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.