Jump to content
AVIC411.com

Recommended Posts

Hi,

 

I need some help how to unpack the AVIC.img to a SD-Card.All attempts were without success. Is there any little tool to unpack the image to a SD-Card?

 

thanks in advance

 

You can use tools from this page, if you using windows. If you use *nix system - just use dd tool. https://help.ubuntu.com/community/Installation/FromImgFiles

 

 

I'm having problems getting my unit to recognize a NTFS USB drive for Internal SD Card backup but it recognizes a FAT32 USB no problem, anyone have any recommendations? I've tried formatting using Tuxera NTFS on my mac and I've tried using a windows VM. Neither time was it recognized after being formatted. the same USB drives work on FAT32, so i know it's not a hardware issue.

 

I just used two cards for backup. First card is microSD card (64GB SDXC, NTFS formatted in windows) - for backup image. Second is 2GB USB stick formatted using FAT32 with testmode key and copy script.

Link to post
Share on other sites
  • 2 months later...
  • Replies 55
  • Created
  • Last Reply

Top Posters In This Topic

I'm having the same issues with NTFS formatted cards not being recognized.

 

I just used two cards for backup. First card is microSD card (64GB SDXC, NTFS formatted in windows) - for backup image. Second is 2GB USB stick formatted using FAT32 with testmode key and copy script.

 

Can you elaborate on the two card method?  I tried booting a 4GB FAT32 in USB2 with a 64G NTFS in USB1, but the script refuses to run.  I also tried booting with the 4G in USB1, then just swapping in the 64G before pressing the home button the final time.  No luck.

 

I also have a 64G SD card, but I can't seem to get the script modifications right.  I tried "/sdcard/~", as indicated by e0x70i.  I also tried "/mnt/sdcard/~", "/mnt/external_sd/~" and a few other flavors, all with no luck.

 

I'm working on a 4100NEX.

 

Thanks for any help you can offer.

Link to post
Share on other sites

I'm having the same issues with NTFS formatted cards not being recognized.

 

Device in USB1 connector should be FAT32-formatted and should contain testmode key and copy_script.sh script. Device for backup file should be NTFS-formatted due to inability to write >2GB files into FAT32-formatted storage. Device for backup can be inserted into USB2 or SD card slot.

 

For SD card use following path in copy_script file:

dd bs=1048576 if=/dev/block/mmcblk0 of=/mnt/sdcard/full_backup_image.img

For USB2 flash use following path in copy_script file:

dd bs=1048576 if=/dev/block/mmcblk0 of=/mnt/udisk1/full_backup_image.img

/mnt/sdcard/ - SD card

/mnt/udisk/ - USB1

/mnt/udisk1/ - USB2

Link to post
Share on other sites

Thank you for the clear directions.  I attempted both methods, and both behave the same way.  In the progress indicator, I see one dot, then two dots, then "100%" after about 1 second.  Way too fast for the backup to have actually occurred, so I must be doing something else wrong.

 

I managed to backup the BSP/NOR Flash just fine.  It's just the internal SD that's giving me grief here.

 

Is it possible that the 4100NEX is different?  Or is there another step I need to perform before I can back up the internal SD?  I see mention of unlocking the SD in a couple posts...  Do I need to do that first?

Link to post
Share on other sites

I think I've obtained success, but it wasn't without several iterations.  Forgive the long post, but I'm hoping the information will help the project.

 

Details:

1) I was unable to get my unit to write to the sdcard (/mnt/sdcard) or USB2 (/mnt/udisk1), regardless of whether they were formatted as FAT32 or NTFS.  I was only able to get it to write to USB1 (/mnt/udisk).

2) My unit appears to only boot to FAT32 partitions.  NTFS does not seem to work.  This was covered in the directions, but I tried it anyway.

3) Here's the detail that'll probably rattle someone:  The order of the parameters passed to dd seems to matter. 

 

To clarify detail #3:

This command, obtained from the original script (downloaded from post #1), works, taking about 12 minutes to write a 3.9G file to USB1 (Windows reports 3,931,136 KB to be exact):

dd if=/dev/block/mmcblk0 of=/mnt/udisk/AVIC.img bs=1048576

But this command (order derived from post #18) does not work (it just reports "100%" after about 1 second without writing anything to the drive):

dd bs=1048576 if=/dev/block/mmcblk0 of=/mnt/udisk/AVIC.img

Note that the only difference is the location of the "bs=" parameter.  It seems like a bug in the dd implementation, but maybe I just don't understand dd. 

 

Anyway, because my drive was formatted as FAT32, I wanted to make sure I wasn't missing part of the image, so I rewrote the script to only pull 2G chunks at a time:

dd if=/dev/block/mmcblk0 of=/mnt/udisk/AVIC.pt1 bs=1048576 skip=0M count=2000M
dd if=/dev/block/mmcblk0 of=/mnt/udisk/AVIC.pt2 bs=1048576 skip=2000M count=2000M
dd if=/dev/block/mmcblk0 of=/mnt/udisk/AVIC.pt3 bs=1048576 skip=4000M count=2000M
dd if=/dev/block/mmcblk0 of=/mnt/udisk/AVIC.pt4 bs=1048576 skip=6000M count=2000M

After execution, ~.pt1 contained 2,048,000 KB, ~.pt2 contained 1,883,136 KB, ~.pt3 was empty (0 file length) and ~.pt4 had about 1.9G in it, though the HU spontaneously rebooted before reporting "100%", so I suspect dd was reading from someplace it wasn't supposed to and caused the device to panic.  Noting that ~.pt1 + ~.pt2 is exactly the same length as the original 3.9G image, I'm guessing that's the size of the SD image for this device, so I didn't bother pursuing things further.

 

Another note: I tried to modify the script to use split instead ("dd if=/dev/block/mmcblk0 bs=1048576 | split -d -b 2000M - /mnt/udisk/AVIC.pt"), but the unit doesn't seem to like "split".  After chewing on the command for a minute or so, it reports "100%" without writing anything to the disk.

 

I've attached pics of my unit's version information in the hopes it'll help make sense of this information.  Let me know if you'd like me to provide any other info that I've missed.  Thanks again for your patience and help.

 

post-134002-0-95063100-1448949000_thumb.jpgpost-134002-0-31121500-1448949023_thumb.jpg

Link to post
Share on other sites
  • 1 month later...

Hi, guys. I would ask you question about restore device from backup image. After i made some experiment with my avic-f960bt and i broke it. I tried to restore it by backup script, i just reverse the  "dd" command(dd bs=1048576 if=/mnt/udisk1/fullsd.img of=/dev/block/mmcblk0), but nothing's happened. Now, the device  shows a text "bla-bla-bla, go to the service center". is there any specific  features of restoring process? Thanks in advance and sorry for my bad english))

Link to post
Share on other sites

Hi, guys. I would ask you question about restore device from backup image. After i made some experiment with my avic-f960bt and i broke it. I tried to restore it by backup script, i just reverse the  "dd" command(dd bs=1048576 if=/mnt/udisk1/fullsd.img of=/dev/block/mmcblk0), but nothing's happened. Now, the device  shows a text "bla-bla-bla, go to the service center". is there any specific  features of restoring process? Thanks in advance and sorry for my bad english))

Try to write image directly into usb stick (using win32diskimager or dd command from *nix based systems), then insert this usb stick into your device and start Copy Device mode (using Copy Device menu item in testmode or corresponding testmode_n.key).

 

If this method isn't working for you - use "mode change" testmode_n.key to remove password from internal sd card, then insert this internal sd card into cardreader and write backup image directly into this card.

 

P.S. нормальный у Ñ‚ÐµÐ±Ñ Ð°Ð½Ð³Ð»Ð¸Ð¹Ñкий, у некоторых хуже :))

Link to post
Share on other sites

Big thanks for answer. Finally, i repaired my avic. It was a few things which interrupt my success. 1st - i was made sd image without disabled WARP mode(i used for recovery dd on Linux Mint desktop). 2nd - TestmodeN key - i thought about it after reading site https://github.com/bassrock/AVIC-NEX/(isuccessfully made code/decode keys, and found that testmodeA key has name XXTECHNICALXX ) but after a lot of  unsuccessful attempts to recover avic with testmodeA key i had a fear to try this key. Now i took a image from other avic and  "make it alive". Now it is all working

 

P. S. По поводу английÑкого: за что купил - за то и продаю))

Link to post
Share on other sites
  • 4 months later...

Hi,

can someone make me a Copy_Script.sh to restore my NOR flash backup?

 

I don't know linux and I want to restore those 3 files from another unit. 

 

Thanks in advance.

 

UPDATE: looks like my NOR was corrupted. Tried to run ModeChange with Testemode_n.key in order to unlock card and now is in reboot loop and nothing is working. So I need a tutorial on how to connect on UART and restore NOR. I have a NOR backup from another identical unit.

 

UPDATE2: found the UART connection.

 

post-113803-0-69071100-1464948773_thumb.jpg

Link to post
Share on other sites

any tip on how to connect?

 

I have connected directly on serial port and trough different usb2serial adapters using hyper terminal or putty, with different baudrates, but I'm receiving only ASCII chars?

 

Connect uart adapter to pins (as in your image), power on your device and you will see bootloader's boot log. Be sure you using 3.3-volt version of adapter, not 5V. If nothing happens try to exchange TX and RX pins.

 

Also, NOR flash contains bootloader code at the beginning, so if your device have corrupted NOR flash it will not boot. In this case you should reflash NOR flash using JTAG or by desoldering chip and using programmer.

Link to post
Share on other sites

Connect uart adapter to pins (as in your image), power on your device and you will see bootloader's boot log. Be sure you using 3.3-volt version of adapter, not 5V. If nothing happens try to exchange TX and RX pins.

 

Also, NOR flash contains bootloader code at the beginning, so if your device have corrupted NOR flash it will not boot. In this case you should reflash NOR flash using JTAG or by desoldering chip and using programmer.

I;m getting this and after 20sec it's restarting

U-Boot 2009.08 ( 3月 19 2014 - 10:34:06)

CPU: Freescale i.MX6 family TO1.1 at 792 MHz
Thermal sensor with ratio = 175
Temperature:   46 C, calibration data 0x5534a27d
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 99000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
nfc clock     : 24000000Hz
Board: i.MX6DL/Solo-JUPITER: unknown-board Board: 0x61011 [POR ]
Boot Device: NOR
I2C:   ready
DRAM:   1 GB
Flash:  8 MB
MMC:   FSL_USDHC: 0,FSL_USDHC: 1,FSL_USDHC: 2
Using default environment

In:    serial
Out:   serial
Err:   serial
***** display DDR calibration result *****
***************************************
Display result(register) of WriteLeveling

   MMDC registers updated from WriteLeveling
   MPWLDECTRL0 (0x021b080c) = 0x0045004C
   MPWLDECTRL1 (0x021b0810) = 0x001B001D
***************************************
Display result(register) of DDR calibration

   MMDC registers updated from calibration

   Read DQS Gating calibration
   MPDGCTRL0 PHY0 (0x021b083c) = 0x42470224
   MPDGCTRL1 PHY0 (0x021b0840) = 0x01790203

   Read calibration
   MPRDDLCTL PHY0 (0x021b0848) = 0x45474B44

   Write calibration
   MPWRDLCTL PHY0 (0x021b0850) = 0x413D413F
***************************************


Net:   got MAC address from IIM: 00:00:00:00:00:00
FEC0 [PRIME]
BSP A is valid
BSP B is valid
imx6 core num: 2
BSP A is valid
BSP B is valid
match invalid password 1.
boot easyrecovery !!
main loop boot env = run bootargs;booti ${bootaddr}
Hit any key to stop autoboot:  0
kernel   @ 10808000 (2827328)
ramdisk  @ 11800000 (877933)
kernel cmdline:
        use uboot command line:
        console=ttymxc0,115200 init=/init androidboot.console=ttymxc0 video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=ak8814,BT656-NTSC,if=BT656,bpp=32 video=mxcfb2:off fbmem=6M,6M vmalloc=400M androidboot.hardware=freescale arm_freq=800 printk.time=1 printk_console=off

Starting kernel ...

MX6SDL JUPITER KT 4.2.2 U-Boot > help
?       - alias for 'help'
autoscr - DEPRECATED - use "source" command instead
base    - print or set address offset
bdinfo  - print Board Info structure
bmp     - manipulate BMP image data
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
booti   - booti   - boot android bootimg from memory

bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
bsp     - get bsp info, or set bsp info

clear_bootf- clear Warp!! bootflag
clk     - Clock sub system
cls     - clear screen
cmp     - memory compare
coninfo - print console devices and information
cp      - memory copy
crc32   - checksum calculation
dhcp    - boot image via network using DHCP/TFTP protocol
download_mode- download_mode - enter i.MX serial/usb download mode
echo    - echo args to console
erase   - erase FLASH memory
ext2load- load binary file from a Ext2 filesystem
ext2ls  - list files in a directory (default /)
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
flinfo  - print FLASH memory information
go      - start application at address 'addr'
help    - print online help
i2c     - I2C sub-system
iminfo  - print header information for application image
imxotp  - One-Time Programable sub-system
imxtract- extract a part of a multi-image
itest   - return true/false on integer compare
loadb   - load binary file over serial line (kermit mode)
loads   - load S-Record file over serial line
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
md      - memory display
memchk  - memory check
mii     - MII utility commands
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
model   - get model info, or set model info.

mtest   - simple RAM read/write test
mw      - memory write (fill)
nfs     - boot image via network using NFS protocol
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
protect - enable or disable FLASH write protection
rarpboot- boot image via network using RARP/TFTP protocol
regul   - Regulator sub system
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
sf      - SPI flash sub-system
sleep   - delay execution for some time
source  - run script from memory
sspi    - SPI utility commands
tftpboot- boot image via network using TFTP protocol
version - print monitor version
warp    - Warp!! boot

MX6SDL JUPITER KT 4.2.2 U-Boot > printenv
bootdelay=0
baudrate=115200
ipaddr=192.168.1.103
serverip=192.168.1.101
netmask=255.255.255.0
loadaddr=0x10800000
rd_loadaddr=0x11000000
netdev=eth0
ethprime=FEC0
bootfile=uImage
splashimage=0x8130000
splashpos=0,0
lvds_num=0
stdin=serial
stdout=serial
stderr=serial
ethact=FEC0
printk.console=off
console_kernel=ttymxc0,115200
console_android=ttymxc0
printk.time=1
bootargs=setenv bootargs console=${console_kernel} init=/init androidboot.console=${console_android} ${smp} video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:dev=ak8814,BT656-NTSC,if=BT656,bpp=32 video=mxcfb2:off fbmem=6M,6M vmalloc=400M androidboot.hardware=freescale arm_freq=800 printk.time=${printk.time} printk_console=${printk.console}
bootaddr=0x08370000

Environment size: 719/8188 bytes

Link to post
Share on other sites


MX6SDL JUPITER KT 4.2.2 U-Boot > bsp get
BSP A is valid
BSP B is valid
## A Side BSP Information:
Magic Number :0xa55a5aa5(a55a5aa5:Valid, other:Invalid)
Boot Mode :0x00000002(0:Normal,
1:Recovery,
2:EasyRecovery,
3:Re-EasyRecovery,
default:Normal)
Launch Mode :0x00000003(0:APL,
1:TestMode.apk,
2:Slave TestMode,
3:Boot Error,
default:APL)
TestMode Sub-Mode :0x00000000(0:TextMode_A.key, 1:Serv Mode, 2:Tech Mode, default:Tech Mode)
Bootimage Side :0x00000000(0:Side A, 1:Side B, default:Side A)
Recoveryimage Side :0x00000000(0:Side A, 1:Side B, default:Side A)
Debug Switch :0x00000000(0:OFF, 1:ON, default:OFF)
Usb OTG Switch :0x00000000(0:Host, 1:Device, default:Host)
Memchk flag :0x00000000(0:No, 1:Yes, default:No)
Warp boot :0x00000000(0:Side A, 1:Side B, default:Side A)
Boot Sub-Mode :0x00000002(0:Normal, 1:Catch snapshot, 2:Warp, default:Normal)
Update flag :0x0000000c(0:Recovery-Update,
1:uboot update,
2:boot.img update,
3:recovery.img update,
4:system.img update,
5:opening data update,
6:UI update,
7:All image update,
8:TESTMODE_N.KEY,
9:easyrecovery copy,
a:easyrecovery copy&verify,
b:password key copy&verify,
c:easyrecovery mode change,
default:Recovery-Update)
Update sub-flag :0x00000000(0:SD Card, 1:USB1, 2:USB2 default:SD Card)
UI Update flag :0x00000000(0:non-updating, 1:updating, default:non-updating)
Reserved1 flag :0xffffffff(default:0xFFFFFFFF)
Reserved2 flag :0xffffffff(default:0xFFFFFFFF)
## B Side BSP Information:
Magic Number :0xa55a5aa5(a55a5aa5:Valid, other:Invalid)
Boot Mode :0x00000002(0:Normal,
1:Recovery,
2:EasyRecovery,
3:Re-EasyRecovery,
default:Normal)
Launch Mode :0x00000003(0:APL,
1:TestMode.apk,
2:Slave TestMode,
3:Boot Error,
default:APL)
TestMode Sub-Mode :0x00000000(0:TextMode_A.key, 1:Serv Mode, 2:Tech Mode, default:Tech Mode)
Bootimage Side :0x00000000(0:Side A, 1:Side B, default:Side A)
Recoveryimage Side :0x00000000(0:Side A, 1:Side B, default:Side A)
Debug Switch :0x00000000(0:OFF, 1:ON, default:OFF)
Usb OTG Switch :0x00000000(0:Host, 1:Device, default:Host)
Memchk flag :0x00000000(0:No, 1:Yes, default:No)
Warp boot :0x00000000(0:Side A, 1:Side B, default:Side A)
Boot Sub-Mode :0x00000002(0:Normal, 1:Catch snapshot, 2:Warp, default:Normal)
Update flag :0x0000000c(0:Recovery-Update,
1:uboot update,
2:boot.img update,
3:recovery.img update,
4:system.img update,
5:opening data update,
6:UI update,
7:All image update,
8:TESTMODE_N.KEY,
9:easyrecovery copy,
a:easyrecovery copy&verify,
b:password key copy&verify,
c:easyrecovery mode change,
default:Recovery-Update)
Update sub-flag :0x00000000(0:SD Card, 1:USB1, 2:USB2, default:SD Card)
UI Update flag :0x00000000(0:non-updating, 1:updating, default:non-updating)
Reserved1 flag :0xffffffff(default:0xFFFFFFFF)
Reserved2 flag :0xffffffff(default:0xFFFFFFFF)

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...



×
×
  • Create New...