bass_rock

So without anything attached the following script: #! /system/bin/sh out="/mnt/udisk/log.txt" echo "--ifconfig-- eth0" 2>&1 >>$out ifconfig eth0 2>&1 >>$out echo "--ifconfig-- eth1" >>$out ifconfig eth1 2>&1 >>$out echo "--ifconfig-- usb0">>$out ifconfig usb0 2>&1 >>$out echo "--ifconfig-- usb1" >>$out ifconfig usb1 2>&1 >>$out echo "--ifconfig-- wlan0" >>$out ifconfig wlan0 >>$out echo "--ifconfig-- wlan1" >>$out ifconfig wlan1 2>&1 >>$out echo "--id--">>$out netcfg 2>

Not yet. But that is one of the end end goals.

Thats great to hear!!!

You should be able to but you will need a USB-A to USB-A cable. I bought one but when I switch my Radio to Device mode my computer does not detect it. As for the ethernet, I have noticed the device as network drivers of some sort, have you tried connecting it and then running a scan of your network and seeing if the network lights turn on?

As we start acquiring system images, is there a collective place we can store these for all? I tried uploading mine to mega but it kept failing. So uploading to google drive right now.

Nope didn't work. Just got the u-boot error screen

Gotcha. Dding and will try in the morning. Also I am convinced on this USB_OTG_ID function under usb test making it a device for adb. Looking at the board there is no other pin and if my research is correct, Regular OTG devices have a sense pin that tell the device which mode. I think the nex has this except it is virtual somehow and is this setting. Changing it changed the first usb in the test mode settings to switch to function (or Device) mode. However the usb pin still sends 5v which I don't believe is correct. If anyone has some thoughts here I'm open to them.

Also it turns out the 4000's have 4GB internal sd cards so a single dd on an ntfs usb stick succeeded in about an hour. I verified I could mount the partition and I am uploading now and will share a link when it is available.

Not sure what you mean here. Are you suggesting to dd an image to a usb, remove the internal and see if it boots? Yes I have tried that before. When looking through the update files, the BTL (Bootloader) .ver exists but it does not contain the .PRG which houses the real image.

I went there but you get a screen of bits that it looks like you have to manually dump 1 by 1.

So interesting note, on at least getting Bluetooth to work. I just had the opportunity to swap the sd cards of a 4000 and a 4100. It behaved just like if we did a cross-upgrade. One thing to note is that the bootloader version did not change. This leads us to know 2 things, the bootloader is not on the SD Card (Which may have been known, but not to me), and that the boot loader seems to be the only item that doesn't get updated or swapped, indicating it may be the item preventing Bluetooth Audio in the system. Other interesting note is that paired bluetooth devices persisted across the swa

@whatisbypass can you post up the decompiled libTestmode.so and libTestmodeProxy.so somewhere?

It is in libTestModeProxy.so in the system img i believe

So not sure if this will work, but i wonder if we may be able to access adb over bluetooth http://stackoverflow.com/questions/11129817/adb-over-bluetooth-android and the logs I dumped from @AdamOutlers original info script mentions: <6>[ 1.017995] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 <6>[ 1.018003] Bluetooth: BNEP filters: protocol multicast <6>[ 1.018012] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Not sure if that is standard, but adb over bluetooth would make sense from a development perspective.

No i have not. @whatisbypass you have the firmware for this section mostly decompiled, have you seen anything?

I have gone in and seen the menu, but the wording on it makes me think it is to image from a usb to the internal sd. Which would make sense from a dev perspective.

Im scared that it goes USB -> Internal not Internal -> USB

Right now the current even broader goal is to be able to modify the deck's software with a firmware update and get adb working. This will give us the ability to install other android apps, launchers, etc that will go even more into fixing the Android Auto issue and even maybe giving us the ability to write code for Wireless Carplay using an adapter etc.. The current task we are doing right now is creating a backup image of the internal SD card so that there is a full-proof way to restore a bricked unit, using a sd backup. The one issue we are having with the software update modifica

Yep did/will do the same. However I ended up stopping it as it went past an hour. Any idea how long with these units a dd should take? Stopped mine after about an hour and only got 3.95gb.

Yea I noticed my attempt following your approach one of the files was completely 0 bytes. Also a heads up, I believe the 8x units have 16gb internal cards.

@whatisbypass yes that should work. I just read up and looks like the NEX line supports NTFS so that should dump the whole image in 1 command. Will try tonight as well as work interfered yesterday.

Oh dang cool! Is this from your bricked unit or an anonymous source? I will wait then for the script to image my 8000 and my 4100, I also have access to a 4000 but not till the weekend.

@AdamOutler the script worked fine. The dump of mine is located here: http://pastebin.com/BE7EELvh I plan to do a dd of my 8000 later tonight. I also have a 4100 I will do as well, hopefully a dd works and will help you unbrick. Is the internal sdcard just /sdcard?

Just tried 10 bytes after the first 1. Still a no go.