Jump to content
AVIC411.com

bass_rock

Members
  • Content Count

    166
  • Joined

  • Last visited

Everything posted by bass_rock

  1. @whatisbypass is the .rar an image to restore or is something inside of it?
  2. @whatisbypass, where did you upload the sd card image, I would be curious to look at it as well
  3. So based on that picture. It looks like you were doing a cross upgrade to the new 1.03 for the x100 series units. To put it into context the x000 units are currently at 1.08 and the x100 units are at 1.03. I'm curious what firmware you dedoxed and then what modifications you tried.
  4. @AdamOutler I completely agree. The only person I know that has been able to get the sdcard password is Busching on his failoverfl0w blog but he has been unresponsive and has not shared the password. From what I can tell is that the update files are basically the whole Rom that gets flashed to the sdcard (correct me if I am wrong here). And let me know how I can help. I have a 8000NEX and a 4100NEX. Would love to be able to see these decks get new features since Pioneer has basically screwed us.
  5. You also have to be careful. Because you need to be able to relaunch settings to get to the update firmware
  6. Sweet looking forward to what you come up with!
  7. It probably is, but like I said before we need a ROM expert, because for instance, if we add an app how can we access it. We would need a launcher of some kind.
  8. Hell probably could start an IndieGogo or something
  9. Yea probably and I would be willing to chip in.
  10. I think the next phase is getting someone involved that is familiar with Android ROMs, since that is essentially what this is. Its basically a ROM we need to decompile and modify to suit our needs and sadly that ain't me.
  11. So tried a modified update on my deck and confirmed this process of repacking the update does work! So that means we now have an easy way to modify the update, repackage it and install it.
  12. For those curious or with development experience, I just created a shell script that opens up the PRG file, waits for modifications and then merges it back together with the correct CRC32 checks and sizes. It is located here: https://gist.github.com/bassrock/8053d22493785b92958f The only issue is it uses ext4fuse which is read-only, so just change that to whatever ext4 mounting program you have that allows write access and then code away. I updated the gist to instead use http://www.paragon-software.com/home/extfs-mac/ which has write support.
  13. Problem is it doesn't seem to be just an apk. It looks like it is baked into Pioneer's MediaPlayer APK and the settings etc. I believe it is defiantly doable, we just need an Android System developer which I am not. And then a script to auto-repack the PRG (doable, just haven't had as much time as I would like)
  14. @PaisanNYC thats awesome. Unfortunately you would need to do what Bushing did on https://fail0verflow.com/blog/2014/enhancing-the-avic-5000nex.html to get the sd card password, and unlock it before you can dump it. Another thing though that could be done to help is to try and put your decks internal sd card into an 8000 NEX and see if it works (assuming the password lock doesn't cause an issue) That would tell us if it is an update issue or something else.
  15. posting the links for the logs here for others to examine: 8000 Bluetooth Playing Then CarPlay Playing https://drive.google.com/folderview?id=0B4lCZip0ewUYd3owNzlOeG5vN0U&usp=sharing 8100 Bluetooth Playing Then CarPlay Playing https://drive.google.com/folderview?id=0B4lCZip0ewUYSFE0ekRfX3psQ0U&usp=sharing
  16. Ok update time. So I just gathered the logs from the 8000 vs 8100 when playing bluetooth and then using CarPlay. They both have the bluetooth errors as seen above. The main difference I can see is that the 8100 has long lists of this error: 01-02 00:02:13.400 2459 2459 E SettingServer: BnSettingServer::onTransact failed when settingserver is resume. cmd 468 Looking into what this really is but hoping this one is the issue. Also tried reinitializing the bluetooth and user cache after the upgrade to the 8100, but after I got the logs.
  17. Its not dead necessarily. We are just in need of a full sd dump
  18. Well looking at testmode and dumping the logs you can see the following: 1-02 00:00:11.010 2724 2876 E BinaryDictionaryGetter: Could not find a dictionary pack 01-02 00:00:11.700 2581 2626 E BluetoothManagerService: fail to bind to: android.bluetooth.IBluetooth 01-02 00:00:11.720 2581 2594 E BluetoothHeadset: Could not bind to Bluetooth Headset Service 01-02 00:00:11.720 2581 2594 E BluetoothA2dp: Could not bind to Bluetooth A2DP Service 01-02 00:02:28.177 2501 2501 E datalink: [frameworks/extend/Sources/iDataLinkServer/src/DataLinkManager.cpp:201][0x20b00006][read error for mUse
  19. In order to continue it looks like the 8100 update is delta and may not contain the need pieces. Is there anyone here that can image their sd card from their 4100,5100,6100,7100,8100?
  20. Hmm. Well I tried a variety of things in this order: Updating to 8100 by just renaming files (but first updated bluetooth firmware)All but bluetooth audio and carplay audio worked. Updated to 8100 straight upgrade (no modified files) after updating to the 8100 by aboveAll but bluetooth audio and carplay audio worked. Updated to 8100 with the old 8000 Bluetooth filesAll but bluetooth audio and carplay audio worked. Click the bluetooth firmware update (which had the 8000 bluetooth files)bluetooth firmware downgraded Carplay and usb iPod stopped working with a 02-60 error. Downgraded back to 1.
  21. Also for those of you that were curious about the bluetooth setting, like I was to understand here is an image of the Bluetooth Audio Setting.
  22. So I updated my 8000NEX to the 81000 NEX software just to verify what does and does not work. Some notes for this as well: Did the map update for the 8000NEX that is available beforehand with navitoolbox Did the 81000 bluetooth update beforehand The navigation does work after an initial long load time (5-10min), so not sure why some are seeing a white screen. I can confirm that the bluetooth audio, carplay audio and phone audio; do not play, while the controls and song title do show up. An interesting note, if you turn carplay off and plug the phone in, the regular Pioneer usb
  23. I'm working on it. As of right now I need to figure out how to turn the system img back into a .prg. My plan is to do that without modifications, verify it flashes then start with small string changes to the apks. But I'm planning on this being my next hobby project. So we shall see if I progress.
  24. We would need the settings api as well. However I haven't figured out which one is the Android Auto APK. I'm actually starting to look into it more and more. If we can start and get the bluetooth working, then we could create an Open Source alternative based on the original system and start adding more features. It looks like the base system is based on Android 4.4 and the Pioneer OSS says how to get a base system running.
  25. Yea same. The first step is figuring out why the bluetooth behaves the way it does. Do we have confirmation it is the exact same bluetooth chip?
×
×
  • Create New...