Jump to content
AVIC411.com

Upgrading NEX4000 to NEX4100 - Work in Progress


Recommended Posts

So tried to get into the test mode on the error screen and no go. 

 

And that 5000NEX sdcard looks like it may not be anything. It does not have a valid partition table (assuming ubuntu can read android partition tables). Which could explain the issues AdamOutler and I are having trying to boot from it.

 

Has anyone successfully used that image or the image on the different sites?

Link to post
Share on other sites
  • Replies 623
  • Created
  • Last Reply

Top Posters In This Topic

Are you speaking about avic_5000nex_sd.img?

$ fdisk -l avic_5000nex_sd.img

Disk avic_5000nex_sd.img: 7,5 GiB, 8068792320 bytes, 15759360 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: 0x00000000

Device               Boot   Start      End  Sectors  Size Id Type
avic_5000nex_sd.img1      1050624  1071103    20480   10M 83 Linux
avic_5000nex_sd.img2      1071104  1091583    20480   10M 83 Linux
avic_5000nex_sd.img3      1091584  3573759  2482176  1,2G  5 Extended
avic_5000nex_sd.img4      3573760 15042559 11468800  5,5G 83 Linux
avic_5000nex_sd.img5      1091585  1153023    61439   30M 83 Linux
avic_5000nex_sd.img6      1153025  1214463    61439   30M 83 Linux
avic_5000nex_sd.img7      1214465  2263039  1048575  512M 83 Linux
avic_5000nex_sd.img8      2263041  2525183   262143  128M 83 Linux
avic_5000nex_sd.img9      2525185  3573759  1048575  512M 83 Linux

Partition table entries are not in disk order.

If yes, you can use kpartx or mount original image using fdisk + mount offset: http://askubuntu.com/questions/445979/mount-sd-card-image-created-using-dd

 

I don't have a .img the file that I have is a .rar from you that I cannot extract. So i ended up dd'd that to the sdcard.

Link to post
Share on other sites


$ sudo fdisk avic_5000nex_sd.img
Disk: avic_5000nex_sd.img geometry: 980/255/63 [15759360 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 513 0 1 - 522 127 16 [ 1050624 - 20480] Linux files*
2: 83 523 0 1 - 532 127 16 [ 1071104 - 20480] Linux files*
3: 05 533 0 1 - 1023 127 16 [ 1091584 - 2482176] Extended DOS
4: 83 1023 127 16 - 1023 127 16 [ 3573760 - 11468800] Linux files*
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 533 0 2 - 562 127 16 [ 1091585 - 61439] Linux files*
2: 05 563 0 1 - 1023 127 16 [ 1153024 - 2420736] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 563 0 2 - 592 127 16 [ 1153025 - 61439] Linux files*
2: 05 593 0 1 - 1023 127 16 [ 1214464 - 2359296] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 593 0 2 - 1023 127 16 [ 1214465 - 1048575] Linux files*
2: 05 1023 127 16 - 1023 127 16 [ 2263040 - 1310720] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 127 16 - 1023 127 16 [ 2263041 - 262143] Linux files*
2: 05 1023 127 16 - 1023 127 16 [ 2525184 - 1048576] Extended DOS
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
------------------------------------------------------------------------
1: 83 1023 127 16 - 1023 127 16 [ 2525185 - 1048575] Linux files*
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused


 

osx output

Link to post
Share on other sites

try unrar e /path-to/file.rar

 

here's the layout.

post-131243-0-97088500-1437657347_thumb.png

 

adamoutler@adamoutler-desktop:~/Desktop/avic$ fdisk -l ./avic_5000nex_sd.img 
 
Disk ./avic_5000nex_sd.img: 8068 MB, 8068792320 bytes
128 heads, 16 sectors/track, 7695 cylinders, total 15759360 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
./avic_5000nex_sd.img1         1050624     1071103       10240   83  Linux
./avic_5000nex_sd.img2         1071104     1091583       10240   83  Linux
./avic_5000nex_sd.img3         1091584     3573759     1241088    5  Extended
./avic_5000nex_sd.img4         3573760    15042559     5734400   83  Linux
./avic_5000nex_sd.img5         1091585     1153023       30719+  83  Linux
./avic_5000nex_sd.img6         1153025     1214463       30719+  83  Linux
./avic_5000nex_sd.img7         1214465     2263039      524287+  83  Linux
./avic_5000nex_sd.img8         2263041     2525183      131071+  83  Linux
./avic_5000nex_sd.img9         2525185     3573759      524287+  83  Linux
 
Link to post
Share on other sites

Ok good news!

 

I was able to successfully dd that sd card img after i got it to unrar.

 

I then popped it into my unit and it went to the Updating screen. At this stage nothing would happen and it sat on Update 0.00 -> 0.00, so I went to my computer loaded the 8000 1.10 onto a usb, unplugged the other sdcard and popped it into the USB 1. The deck then recognized the 1.10 update and began updating. 

 

The deck now boots normally and I can resume where I was! (Carefully modifying the init.rc).

 

 

One thing to note with this is that on the first boot with the sd card I didn't realize I still had my usb with the Testmode key in it. However on subsequent boots I removed that key and still got the Updating 0.00->0.00 screen.

Link to post
Share on other sites

Ok good news!

 

I was able to successfully dd that sd card img after i got it to unrar.

 

I then popped it into my unit and it went to the Updating screen. At this stage nothing would happen and it sat on Update 0.00 -> 0.00, so I went to my computer loaded the 8000 1.10 onto a usb, unplugged the other sdcard and popped it into the USB 1. The deck then recognized the 1.10 update and began updating.

 

The deck now boots normally and I can resume where I was! (Carefully modifying the init.rc).

 

 

One thing to note with this is that on the first boot with the sd card I didn't realize I still had my usb with the Testmode key in it. However on subsequent boots I removed that key and still got the Updating 0.00->0.00 screen.

Please share the sha256 of your rar and image for quality purposes.
Link to post
Share on other sites

So whats also interesting is that I now get a map license error and my motorized screen will not work. The options are there for the cd and sdcard, clicking on them does nothing, and the options for the motorized screen are greyed out. 

 

It's like there is something saved from the sdcard image (which was not a 8000). 

Link to post
Share on other sites

So whats also interesting is that I now get a map license error and my motorized screen will not work. The options are there for the cd and sdcard, clicking on them does nothing, and the options for the motorized screen are greyed out.

 

It's like there is something saved from the sdcard image (which was not a 8000).

Sounds like DRM. The deck is likely initialized with some special keys from the factory.

 

Try flashing the original SD Image once again, then perform all available updates even if they are redundant. It's possible one could contain a default DRM.

 

Also, ensure you flash a totally stock image and not modified.

Link to post
Share on other sites

Yep. I did the updates a few times. Now I am trying a force write with the Testmode keys. 

 

The next idea if that that does not work is to try and dd the right images from the update to the right partitions to on the SD which mean we need to know the right mappings

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...