Related
Hi guys. I am trying to update a very old IPAQ H3850 pocket pc. The Rom version on the mobile windows says ROM 1.15, version 3.0.11171 (Build 11178). I managed to find the proper Rom file for my unit which is 1.20. Now I followed the installation instructions until it came to the part where you have to hold 3 buttons at the same time until a usb window pops up. I came this far until I I mounted my unit onto the cradle and the installation tells me it cannot find my unit. Weird. When i soft started the unit and mounted it without preparing for the new ROM upgrade the computer found my device. It seems when I put the unit into 'prepare to install new ROM' mode it looses contact with the device manager. I have read about others having this issue.
I have tried all usb ports and others and still no connection when I put the unit in 'remote usb update'. I am reaching the end of my wits with this darn unit
I have been reading else where on the net of people using a utility program called multi-port / usb tty to install the rom update from a sd card. Where can i download this file? I have been searching for this download and have been very unlucky. Now only if I can get a step by step instructions on how to install the ROM from a SD card. Otherwise I am going to throw this worthless piece of crap out the window. I am really getting fed up.
Thanks for any help helps. I've been at this for about 3 days now and I'm tired.
Hi guys,
I hope i am in the right place...
I have an android system installed in my Mitsubishi, but the local importer of the system, has "locked" the system by removing the Google play app, file manager and all ability to make any changes.
Is there a way I can add back the Google play so i can add a few apps to the system? The system has a USB port.
FLY AUDIO MODEL G8023H19
Thanks,
goamir said:
Hi guys,
I hope i am in the right place...
I have an android system installed in my Mitsubishi, but the local importer of the system, has "locked" the system by removing the Google play app, file manager and all ability to make any changes.
Is there a way I can add back the Google play so i can add a few apps to the system? The system has a USB port.
FLY AUDIO MODEL G8023H19
Thanks,
Click to expand...
Click to collapse
no not really
without a file manager
I was going to say - put a file manager app on to the usb - I would have provided you with a file manager app
wait for usb files to show up and install app but
a file manager would be needed to show the USB and install an app manually anyway
I mod android and I have my own rom but I can't think of anyway other than....
having another type of app store on there
This unit has a full thread on 4pda.
http://4pda.ru/forum/index.php?showtopic=671390
You should find all your answers there. Since googling it only returns results in Russian I presume it is a unit only sold there.
Installing APK
Hi,
Did you manage to install an APK?? Or did you get any answers regarding this issue?
Just an idea because I don't have this in my car:
connect it to a laptop, and use "adb" tool to install the APK files you wish.
Question is, how would you root it after that, and whether converting apps into system apps would work in order to install play-services and play-store.
In order to fetch the APK files from a normal device, you can use my app :
https://play.google.com/store/apps/details?id=com.lb.app_manager
Can I reply here?
Sent from my MI 2S using Tapatalk
goamir said:
Hi guys,
I hope i am in the right place...
I have an android system installed in my Mitsubishi, but the local importer of the system, has "locked" the system by removing the Google play app, file manager and all ability to make any changes.
Is there a way I can add back the Google play so i can add a few apps to the system? The system has a USB port.
FLY AUDIO MODEL G8023H19
Thanks,
Click to expand...
Click to collapse
have you managed to do something with it?
alicenir said:
have you managed to do something with it?
Click to expand...
Click to collapse
Hello Goamir,
Does this android work properly with the 2016 mitsubishi outlander can you use your original gps antenna, rear & side view camera are you able to get your cars A/c settings etc on the screen? If not can anyone recommend a proper android system?
I managed to activate developer options
Today I managed to activate developer options in my car (Mitsubishi Outlander) by going to input devices -> Voice input, I played a bit with it, I set the default to English and downloaded offline recognition, afterwards I pressed the small question mark in the upper corner and there it tells you that you don't have google services, there's a button there that suggest to install it, I pressed it and later I noticed that I have developer options (not sure which step actually enabled it, If someone can repeat it step-by-step and tell it will be great).
Anyhow now i'm stuck again since I can't connect usb and push apk, I tried with male-male usb but it didn't worked.
If anyone got any idea please share.
Details I have on the device:
When you reboot it and long press the screen it takes you to fastboot mode, when you hold volume up in the steering wheel it takes you to recovery .
The model I have is Flyaudio G8508
jon
hi, did you find a solution for the flyaudio g8 in the outlander here in israel? i am looking to root or flash a rooted firmware
thanks so much
jon
Solution for Israel's flyaudio
We have a solution to unlock FlyAudio G8 for Mitsubishi and hyundai from Israel.
If you want to unlock contact with me by PM.
FlyAudio for Israel Hyundai and Mitsubishi v.2016-06-04.
Hello,
For Israel Hyundai and Mitsubishi.
Firmware includes :
Amaze filemanager v3.0.1
Waze v4.7.0.1
AC3 Video Player v3.0.0
Chrome Browser Google v51.0.2704.81
SWE Browser
SpotifyMusic v5.7.0.781
Nobex
1. Download firmware from: h**ps://ufile.io/ac836 ( download link expires on 13 October 2016 )
2. Copy the file to USB flash.
3. Restart Android and press Home + Back buttons together.
4. Do an auto update.
Do it on your own risk !
eNjOy.
not working on outlander. recovery mode don't see a rom file on usb flash
The same issue for me.
When try to load from USB i get message "Ensure the storage Device Have Package"
you can use this one(haven't tested it) - h**ps://uploadfiles.io/07b58
But keep in mind that it's quite old one.
Today I managed to fetch the latest fup update file, it seems like the vendor update utility fetch it from some dropbox account but I didn't managed to get the url just to get the downloaded file.
You can find it here - h**ps://ufile.io/1cf01 , you can follow 4pda guide on how to add apk files.
The same issue for me.
When try to load from USB i get message "Ensure the storage Device Have Package"
16th September 2016 03:15 PM
Click to expand...
Click to collapse
The unit is "Pickey" when it comes to the use of different DOK's
please make sure you format the DOK to FAT32 first
than if not working please try another DOK it should identify and work.
Unfortunately not working. Disk-On-Key formatted with different cluster sizes, tried use different flash devices - FLyAudio don't see the firmwares
try this 4pda.ru*forum*index.php?showtopic=671390&st=980
.
replace * by /
I am trying to contact someone from Russian forum for the solution they already have experience. Will update.
I saw today how tech entering the recovery mode. I think it was like that:
long press on power - after blink press home then touch on screen when it is green , then enter the code :1630
I will try to update today.
Any news?
Hi,
I got my system on my Mitsubishi updated - unfortunately i payed for it...
Still if I could help in this forum I will.
I can install any app and have full access to google play.
However some option are still missing.
e.g. when i connect my PC to the system it is not show at all.
i was thinking i could somehow create a full system backup (image) and then turn the backup to an update file.
If anyone can offer a way to enable the use option, that is that my system would appear on my pc i could try it.
I have developer option and usb debugging on via an app i downloaded.
If i can do it in any other way I can try.
Another thing i was thinking of is to create a full backup and later restore, from the recovery mode but there are only option for update in the recovery mode.
Is it possible to allow/add the restore/backup option ?
Recently bought a used Nexus 7 LTE for my son to use after he broke his tablet. Trying to get Lineage OS on it but I cannot see it via USB on anything...
Windows 8 - Doesn't see the device at all, nothing listed in Device Manager. Device is charging off USB cable.
Tried 5 known good cables. Same cable on same computer with different devices works.
Ubuntu - Nothing shows in lsusb - Same as above, tried many cables and all charge the device but nothing will connect.
Device has USB Debugging enabled, I've also tried it disabled.
MTP is enabled, also tried the PTP with same results.
I have tried the official Google drivers as well as older drivers found within these forums.
Not even a generic or invalid device shows in Device Manager on Windows.
Used Android Studio to install Google Drivers, still nothing.
I've tried factory reset and wipe cache partitions. Never shows up.
I am assuming at this point the device has a bad USB port. I am hoping perhaps I missed something and someone knows what that is. I've culled the forums and a LOT of these had similar issues but mostly driver related. I cannot even see it to try different drivers. Some were cable but I've tried many cables that work in other devices.
Are there any other ways to connect to the device to do the OEM unlock and install TWRP and Lineage?
Device is bone stock with Android 5.1 (BUILD LMY470) - Connects to WiFi and LTE network just fine.
Fixed
RESOLVED:
Installed a Root app (KingRoot) and rooted device.
Installed official TWRP app, downloaded and installed TWRP bootloader
Downloaded latest Nightly of Lineage OS, used Astro File manager to move to root
Rebooted into TWRP, Wiped System/Data/Cache/Dalvik
Installed Lineage OS ROM.
Rebooted.
Profit.
compnird said:
RESOLVED:
Installed a Root app (KingRoot) and rooted device.
Click to expand...
Click to collapse
It is an interesting workaround but the main issue is not resolved. It looks like a hardware fault, there are 3 possibilities:
1 broken data contacts of the USB port
2 unsoldered data lines between the USB port and the PCB
3 disconnected USB data lines between the daughterboard and motherboard
Most likely is #2 but the easiest is #3 which can be fixed by re-seating of the wide, silver cable interconnecting the PCBs. All you have to do:
- disconnect the battery
- unlock the cable's connectors
- pull out and push it back in
- relock
- reconnect the battery
Good luck.
Hi all,
Apologies in advance for using this post but I have a similar issue with my device. I accidentally ejected the device while I was transferring some data to my computer instead of a memory stick. Usually the computer should say operation is invalid since the device is in use however without any prompts it ejected the device.
So now when I plug my Nexus into my laptop via USB the device is recognised for a second and disconnects and then reconnects and carries on this pattern. I've tried a number of different methods that I researched online including:
Deleting the drivers and reinstalling them
Changing USB power settings
None of the above and fixed the issue of being unable to connect to my computer via USB. Has anyone come across this problem before and if so can you recommend a potential fix?
B3.mach said:
...so can you recommend a potential fix?
Click to expand...
Click to collapse
Hi, while it appears that your PC is responsible for the issue, please check the N7 on another PC or with a OTG drive. When you're sure your N7 and USB cable are OK, we can fix the PC but what OS is on it? If it is Windows then do the following:
- disconnect N7
- run "regedit.exe"
- delete these keys
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_18d1&Pid_4ee1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_18d1&Pid_4ee2- reboot PC
- reboot N7
- connect N7
OK?
k23m said:
Hi, while it appears that your PC is responsible for the issue, please check the N7 on another PC or with a OTG drive. When you're sure your N7 and USB cable are OK, we can fix the PC but what OS is on it? If it is Windows then do the following:
- disconnect N7
- run "regedit.exe"
- delete these keys
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_18d1&Pid_4ee1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_18d1&Pid_4ee2- reboot PC
- reboot N7
- connect N7
OK?
Click to expand...
Click to collapse
Hi k23m,
Thank you the reply. I can confirm one of the first things I tried was connecting the device to a different laptop - where it connected properly. Both laptops are using Windows 10 and I've tried different USB cables to confirm that the wire isn't at fault either - so know my original laptop has the issue.
So I've attempted your the instructions you mentioned and the first thing I noticed was when I was in the Registry Editor there was no 4ee1 and just 4ee2. I attempted to delete the registry files for 4ee2 and came across the error messaged that states, 'Cannot delete VID_18D1&PID_4EE2: Error while deleting key.'. I had a look on the internet to see if there was a solution to deleting the files and it mentioned to modify the permissions as well as using a few programs to delete them. However after attempting these instructions still luck in deleting them.
Any further suggestions?
Thanks
B3.mach said:
there was no 4ee1 and just 4ee2.
....
I attempted to delete the registry files for 4ee2 and came across the error messaged that states, 'Cannot delete VID_18D1&PID_4EE2: Error while deleting key.'. I had a look on the internet to see if there was a solution to deleting the files and it mentioned to modify the permissions as well as using a few programs to delete them. However after attempting these instructions still luck in deleting them.
Click to expand...
Click to collapse
Please get https://github.com/jschicht/RunAsTI and extract it, then...
- right-click RunAsTI64.exe and run it as admin
- in the newly created command window type and run "regedit"
- delete the VID_18D1&PID_4EE2 key
- search the entire registry for ALL "VID_18D1&PID_4EE1" keys and delete them (if found any)
- reboot PC!
Also, can you confirm that a different device connects properly to the faulty PC using the MTP protocol? If not, then deleting 4EE1/4EE2 will not help and the issue will have to be further explored.
k23m said:
- right-click RunAsTI64.exe and run it as admin
- in the newly created command window type and run "regedit"
- delete the VID_18D1&PID_4EE2 key
- search the entire registry for ALL "VID_18D1&PID_4EE1" keys and delete them (if found any)
- reboot PC!
Also, can you confirm that a different device connects properly to the faulty PC using the MTP protocol? If not, then deleting 4EE1/4EE2 will not help and the issue will have to be further explored.
Click to expand...
Click to collapse
Hi k23m,
Once more thank you for the instructions. I can confirm my mobile connects to my laptop fine through a MTP protocol connection with no issues. I've downloaded the files as deleted the keys and values as mentioned but still no success.
Thanks
B3.mach said:
Hi k23m,
Once more thank you for the instructions. I can confirm my mobile connects to my laptop fine through a MTP protocol connection with no issues. I've downloaded the files as deleted the keys and values as mentioned but still no success.
Thanks
Click to expand...
Click to collapse
Hello B3.mach, let's summarize:
N7-MTP --> PC1 /NO
N7-MTP --> PC2 /OK
phone-MTP --> PC1 /OK
Re-confirmed?
Can you see any meaningful logs in Windows Event Viewer around the time of N7-MTP --> PC1? If so, quote them. To stimulate more logs kill the MTP-responsible WudfHost.exe process while you attempt N7-MTP --> PC1 and re-connect N7.
Next, please try these:
N7-fastboot --> PC1?
N7-TWRP-MTP --> PC1?
N7-PTP --> PC1?
Finally, let's do a total clean-up of all N7's traces in the system:
- disconnect N7
- delete all "VID_18D1&PID_4EE1" keys from the registry yet again
- delete all *.inf files which contain "VID_18D1&PID_4EE1" from C:\Windows\inf\ folder
- reboot
- connect N7
It has to work now
k23m said:
Hello B3.mach, let's summarize:
N7-MTP --> PC1 /NO
N7-MTP --> PC2 /OK
phone-MTP --> PC1 /OK
Re-confirmed?
Can you see any meaningful logs in Windows Event Viewer around the time of N7-MTP --> PC1? If so, quote them. To stimulate more logs kill the MTP-responsible WudfHost.exe process while you attempt N7-MTP --> PC1 and re-connect N7.
Next, please try these:
N7-fastboot --> PC1?
N7-TWRP-MTP --> PC1?
N7-PTP --> PC1?
Finally, let's do a total clean-up of all N7's traces in the system:
- disconnect N7
- delete all "VID_18D1&PID_4EE1" keys from the registry yet again
- delete all *.inf files which contain "VID_18D1&PID_4EE1" from C:\Windows\inf\ folder
- reboot
- connect N7
It has to work now
Click to expand...
Click to collapse
Hi k23m,
It seems by doing a fastboot connection it fixed the issue - not sure as to why it did it but thank you!
But to confirm as I was going through your instructions -
N7-MTP --> PC1 /NO
N7-MTP --> PC2 /OK
phone-MTP --> PC1 /OK
Correct
I had a look in the event viewer during the time of the mishap and couldn't see any useful logs that related to the any errors.
So as I was working my way down to your instructions, I did a fastboot and the issue seemed to have stopped and the N7 connects to my laptop without disconnecting.
Thank you for your helpful instructions and your patience with helping me resolve the issue.
Best regards,
b3
I was posting some questions in the "Rooted Jeep Cherokee '14 Uconnect" thread but I've started this new thread for the 17.xx versions because the methods (if we are able to identify them) aren't the same as the 16.33.29 and earlier firmwares...
I am still trying to crack into that unit with the 17.11.07 software. I have a D-Link USB Ethernet but its a HW revision D and I believe I would need a B if we can get ethernet enabled at all.
Also, if we can get Ethernet enabled we will still need to get SSH password or key.
devmihkel said:
For good or for bad NOT everything appears correct, except the running 17.x version... As of now neither the "commercial jailbreak" supports new versions (well yes they were using exactly the same file to start with Also 16.51.x or newer appears to be no go: uconnect-8-4-8-4an-update
EDIT: haven't got 17.09.07 to try, but on 17.11.07 manifest.lua has changed and the last block/ search keyword is "ota_update" instead. Otherwise all the same, image valid after the edit and script.sh gets fired - at least on 16.33.29 that is @HanJ67 Did you actually try to mount installer.iso after the edit and checked /etc/manifest.lua for the end result before?
Click to expand...
Click to collapse
devmihkel said:
Yeah, 2nd attempt is much better as last lua block is correctly terminated and your script might actually run, but unfortunately no successful 17.x runs have been reported so far SWF scripts are not involved in update/jail-breaking run, these ones become relevant only once you are in (and need to enable some app or wifi or navi features etc). Afaik 17.x blocks ethernet dongle usage as well, but let's see if even the USB driver/link gets activated at all?
Click to expand...
Click to collapse
Do you have a 16.33.29 version I can try this on? I'm wondering if it will get me far enough to execute the "manifest.lua HD_Update" hack you and @HanJ67 were discussing.
I've used the 17.43.01, then finally found a 17.11.07 and had no luck there either.
In my latest attempts on the 17.11.07, I was able to hex edit the "ifs-cmc.bin" on the UPD and replaced the SSH-RSA key with my own. I think this bin will be flashed to the MMC during an update.
That SWDL.UPD got past the initial check and rebooted into update mode, but then it fails the second ISO check and loops. I had to use an unmodified image to finish the update and get back up and running.
I keep reading about making changes only after the 2048 Byte mark in the older versions with the "S" at 0x80. Is this still relevant
in later ISO/UPD images and to the second ISO check?
Right now, I'm looking to find a way to disable that check so that my modified .bin will be written to disk? I think this route would work to also modifying and getting WiFi enabled after a flash of the edited image.
If I had I 16.33.29 or similar older UPD version to attempt the HD_UPDATE hack in the Manifest.lua file I would give that a shot to be thorough.
Do You have an idea how to connect by USB2LAN adapter to uConnect ?
Do You know if there is an UART pins on the mainboard ?
itsJRod said:
I was posting some questions in the "Rooted Jeep Cherokee '14 Uconnect" thread but I've started this new thread for the 17.xx versions because the methods (if we are able to identify them) aren't the same as the 16.33.29 and earlier firmwares...
I am still trying to crack into that unit with the 17.11.07 software. I have a D-Link USB Ethernet but its a HW revision D and I believe I would need a B if we can get ethernet enabled at all.
Also, if we can get Ethernet enabled we will still need to get SSH password or key.
Do you have a 16.33.29 version I can try this on? I'm wondering if it will get me far enough to execute the "manifest.lua HD_Update" hack you and @HanJ67 were discussing.
I've used the 17.43.01, then finally found a 17.11.07 and had no luck there either.
In my latest attempts on the 17.11.07, I was able to hex edit the "ifs-cmc.bin" on the UPD and replaced the SSH-RSA key with my own. I think this bin will be flashed to the MMC during an update.
That SWDL.UPD got past the initial check and rebooted into update mode, but then it fails the second ISO check and loops. I had to use an unmodified image to finish the update and get back up and running.
I keep reading about making changes only after the 2048 Byte mark in the older versions with the "S" at 0x80. Is this still relevant
in later ISO/UPD images and to the second ISO check?
Right now, I'm looking to find a way to disable that check so that my modified .bin will be written to disk? I think this route would work to also modifying and getting WiFi enabled after a flash of the edited image.
If I had I 16.33.29 or similar older UPD version to attempt the HD_UPDATE hack in the Manifest.lua file I would give that a shot to be thorough.
Click to expand...
Click to collapse
Hello, any news about it?
hi,
can you explain how to change SSH key in "ifs-cmc.bin" file?
thanks a lot
itsJRod said:
I was posting some questions in the "Rooted Jeep Cherokee '14 Uconnect" thread but I've started this new thread for the 17.xx versions because the methods (if we are able to identify them) aren't the same as the 16.33.29 and earlier firmwares...
I am still trying to crack into that unit with the 17.11.07 software. I have a D-Link USB Ethernet but its a HW revision D and I believe I would need a B if we can get ethernet enabled at all.
Also, if we can get Ethernet enabled we will still need to get SSH password or key.
Do you have a 16.33.29 version I can try this on? I'm wondering if it will get me far enough to execute the "manifest.lua HD_Update" hack you and @HanJ67 were discussing.
I've used the 17.43.01, then finally found a 17.11.07 and had no luck there either.
In my latest attempts on the 17.11.07, I was able to hex edit the "ifs-cmc.bin" on the UPD and replaced the SSH-RSA key with my own. I think this bin will be flashed to the MMC during an update.
That SWDL.UPD got past the initial check and rebooted into update mode, but then it fails the second ISO check and loops. I had to use an unmodified image to finish the update and get back up and running.
I keep reading about making changes only after the 2048 Byte mark in the older versions with the "S" at 0x80. Is this still relevant
in later ISO/UPD images and to the second ISO check?
Right now, I'm looking to find a way to disable that check so that my modified .bin will be written to disk? I think this route would work to also modifying and getting WiFi enabled after a flash of the edited image.
If I had I 16.33.29 or similar older UPD version to attempt the HD_UPDATE hack in the Manifest.lua file I would give that a shot to be thorough.
Click to expand...
Click to collapse
sofro1988 said:
Hello, any news about it?
Click to expand...
Click to collapse
I have not had had much time to work on this.
I actually had an idea last week that brought me back to this. I plan to use a custom flash drive to present an unmodified ISO for verification, then swap nand to an identical image that has been he's edited to enable usb Ethernet and add a custom key for ssh access.
I thought to stack a NAND on top of the original on a is flash drive, then breakout the Chip Enable pin to a switch. I've seen this done for with guys modifying game consoles to be able to run modified firmware.
Once the 2nd NAND is in place I will restore an image of the original nand containing the unmodified update, then hex edit the required portions to allow access after updating.
If this method works, I should be able to pass the verification with the original nand chip, then switch it (hopefully there's a big enough window to do this by hand) then present the modified nand before it begins the flash procedure.
Hopefully someone more intimately familiar with the update scripts can verify I'm not missing anything in the process
Tajadela said:
hi,
can you explain how to change SSH key in "ifs-cmc.bin" file?
thanks a lot
Click to expand...
Click to collapse
I used a hex editor to find the Ssh RSA key and replace it. This passed the initial check to reboot into update mode, but wouldn't pass the full check in update mode. I'm hoping my attempt below will pass that check and still update with the modifications.
itsJRod said:
I used a hex editor to find the Ssh RSA key and replace it. This passed the initial check to reboot into update mode, but wouldn't pass the full check in update mode. I'm hoping my attempt below will pass that check and still update with the modifications.
Click to expand...
Click to collapse
thanks for answer.
I saw an ssh key with the hex editor, but I would like to see exactly what you have replaced.
if it's not too much trouble, it would be interesting to see with some screenshots the changes you've made.
So we could work on two fronts. The idea of the double nand is good, but not very simple to make ...
Just thinking out loud here, when you say it passes the initial check, does it then give you any confirmation of that or any message on the screen before rebooting to upgrade mode?
Sent from my CLT-L09 using Tapatalk
SquithyX said:
Just thinking out loud here, when you say it passes the initial check, does it then give you any confirmation of that or any message on the screen before rebooting to upgrade mode?
Sent from my CLT-L09 using Tapatalk
Click to expand...
Click to collapse
I tried much the same thing -- the swdl.upd is another CDROM filesystem:
martinb$ file swdl.upd
swdl.upd: ISO 9660 CD-ROM filesystem data 'CDROM'
It contains three more .iso files : installer.iso, primary.iso, and secondary.iso
installer.iso is a CDROM image, but is not mountable on my linux system
primary.iso is a CDROM image, and has the usual /bin, /etc/, and /usr filesystem for an install
the /bin directory has one file - update_nand
the /etc directory has the usual mfgVersiontxt, nand_partion.txt, system_etfs_postinstall.txt, system_mmc_postinstall.txt and version.txt
the /usr/share directory is all the firmware for various components - EQ, HD_FIRMWARE, IFS, MMC_IFS_EXTENSION,OTA,SIERRA_WIRELESS,V850, and XM_FIRMWARE
What's interesting to me is that they did update the SIERRA_WIRELESS firmware -- and have done some housecleaning:
Code:
#---------------------------------
# sierra_wireless_disable_flowcontrol.file
# \d == 1 second delay
SAY " Send AT \n"
'' AT\r
OK \d
SAY "Disable flow control\n"
'' at+ifc=0,0\r
OK \d
SAY "Send SMS command CNMI\n"
'' at+cnmi=2,1,0,1,0\r
OK \d
SAY "Clear emergency number list\n"
'' AT!NVENUM=0\r
OK \d
SAY "Set emergency number to 911\n"
'' AT!NVENUM=1,"911"\r
OK \d
SAY "Save Setting\n"
'' at&w\r
OK \d
#---------------------------------
Also in the IFS directory, when you hexedit the ifs-cmc.bin file it reveals another little treat... an SSH root public key ( not as nice as a private key, but hey )
(Sorry about the formatting, this is cut/paste right out of the hex editor)
Code:
ssh-rsa [email protected]
2E..IwU.Q....njle8r9nrJ7h8atg4WfqswU0C0Rk/Ezs/sQs5ZA6ES82MQONjHBd7mw
uo8h0xfj3KeeSHMXCEBpmU26guNE4EqfvdioLFCDUxtvMYswlUZjsvd/NYz9lnUZg2hy
pwzFQjXgSzmHVrHjkKKvq7Rak/85vGZrJKxlvHnowA8JIl1tVNVQjPMNgDDJabaETtfw
LL1KlvAzI81cKOG/3IRn9lU6qyYqyG+zYoza0nN\..7/AtxdL481k81Go5c3NQTnkl2U
68lbu8CpnwrYCU098owLmxdI4kF5UOL4R61ItJuwz30JSESgT..!8RDgM6XEiHUpK9yW
vvRg+vbGWT/oQn0GQ== [email protected]
in /usr/share/MMC_IFS_EXTENSION/bin/cisco.sh and dlink.sh there's another good hint - what adapter you need for USB ethernet
Code:
#!/bin/sh
# Handle an Ethernet connection via the CISCO Linksys USB300M adapter
or
Code:
#!/bin/sh
# Handle an Ethernet connection via the D-Link DUB-E100 adapter
The static IP it brings up if no DHCP is offered is : 192.168.6.1
There's tons more in there -- like the V850 chip has access to the Sierra Wireless CDMA modem, but can configure it for voice calls through the car speakers:
"AT!AVSETPROFILE=8,1,1,0,5" ( embedded in the cmcioc.bin update file )
secondary.iso is a CDROM image and only has /etc/ and /usr
the /etc/ directory has speech_mmc_preinstall.txt and xlets_mmc1_preinstall.txt
the /usr/ directory has /usr/share/speech and /usr/share/xlets ( tons of information about sensors in the car, etc in xlets )
martinbogo1 said:
I tried much the same thing -- the swdl.upd is another CDROM filesystem:
martinb$ file swdl.upd
swdl.upd: ISO 9660 CD-ROM filesystem data 'CDROM'
It contains three more .iso files : installer.iso, primary.iso, and secondary.iso
installer.iso is a CDROM image, but is not mountable on my linux system
primary.iso is a CDROM image, and has the usual /bin, /etc/, and /usr filesystem for an install
the /bin directory has one file - update_nand
the /etc directory has the usual mfgVersiontxt, nand_partion.txt, system_etfs_postinstall.txt, system_mmc_postinstall.txt and version.txt
the /usr/share directory is all the firmware for various components - EQ, HD_FIRMWARE, IFS, MMC_IFS_EXTENSION,OTA,SIERRA_WIRELESS,V850, and XM_FIRMWARE
What's interesting to me is that they did update the SIERRA_WIRELESS firmware -- and have done some housecleaning:
Code:
#---------------------------------
# sierra_wireless_disable_flowcontrol.file
# \d == 1 second delay
SAY " Send AT \n"
'' AT\r
OK \d
SAY "Disable flow control\n"
'' at+ifc=0,0\r
OK \d
SAY "Send SMS command CNMI\n"
'' at+cnmi=2,1,0,1,0\r
OK \d
SAY "Clear emergency number list\n"
'' AT!NVENUM=0\r
OK \d
SAY "Set emergency number to 911\n"
'' AT!NVENUM=1,"911"\r
OK \d
SAY "Save Setting\n"
'' at&w\r
OK \d
#---------------------------------
Also in the IFS directory, when you hexedit the ifs-cmc.bin file it reveals another little treat... an SSH root public key ( not as nice as a private key, but hey )
(Sorry about the formatting, this is cut/paste right out of the hex editor)
Code:
ssh-rsa [email protected]
2E..IwU.Q....njle8r9nrJ7h8atg4WfqswU0C0Rk/Ezs/sQs5ZA6ES82MQONjHBd7mw
uo8h0xfj3KeeSHMXCEBpmU26guNE4EqfvdioLFCDUxtvMYswlUZjsvd/NYz9lnUZg2hy
pwzFQjXgSzmHVrHjkKKvq7Rak/85vGZrJKxlvHnowA8JIl1tVNVQjPMNgDDJabaETtfw
LL1KlvAzI81cKOG/3IRn9lU6qyYqyG+zYoza0nN\..7/AtxdL481k81Go5c3NQTnkl2U
68lbu8CpnwrYCU098owLmxdI4kF5UOL4R61ItJuwz30JSESgT..!8RDgM6XEiHUpK9yW
vvRg+vbGWT/oQn0GQ== [email protected]
in /usr/share/MMC_IFS_EXTENSION/bin/cisco.sh and dlink.sh there's another good hint - what adapter you need for USB ethernet
Code:
#!/bin/sh
# Handle an Ethernet connection via the CISCO Linksys USB300M adapter
or
Code:
#!/bin/sh
# Handle an Ethernet connection via the D-Link DUB-E100 adapter
The static IP it brings up if no DHCP is offered is : 192.168.6.1
There's tons more in there -- like the V850 chip has access to the Sierra Wireless CDMA modem, but can configure it for voice calls through the car speakers:
"AT!AVSETPROFILE=8,1,1,0,5" ( embedded in the cmcioc.bin update file )
secondary.iso is a CDROM image and only has /etc/ and /usr
the /etc/ directory has speech_mmc_preinstall.txt and xlets_mmc1_preinstall.txt
the /usr/ directory has /usr/share/speech and /usr/share/xlets ( tons of information about sensors in the car, etc in xlets )
Click to expand...
Click to collapse
Have you tried connecting to it?
Sent from my iPhone using Tapatalk
sofro1988 said:
Have you tried connecting to it?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I managed to connect with the cisco adapter (usb / ethernet), but I don't know the root password. is the problem at the moment insurmountable ..
Using a cisco connector, I have gotten the ethernet to come up, but that's it. At the moment, there doesn't seem to be anything I can connect to.
@Tajadela - sounds like you at least were able to either SSH or telnet in to a port... I'm on software version 17.43.01 .. which are you on, and what year vehicle? ( Jeep Grand Cherokee, 2015, Uconnect 8.4AN with the 3G Sierra Aircard modem for Sprint )
martinbogo1 said:
Using a cisco connector, I have gotten the ethernet to come up, but that's it. At the moment, there doesn't seem to be anything I can connect to.
@Tajadela - sounds like you at least were able to either SSH or telnet in to a port... I'm on software version 17.43.01 .. which are you on, and what year vehicle? ( Jeep Grand Cherokee, 2015, Uconnect 8.4AN with the 3G Sierra Aircard modem for Sprint )
Click to expand...
Click to collapse
I connected in telnet on a uconnect 6.5 with firmware 15.xx.xx. You can connect to Uconnect with static IP it brings up if no DHCP is offered is: 192.168.6.1
itsJRod said:
I used a hex editor to find the Ssh RSA key and replace it. This passed the initial check to reboot into update mode, but wouldn't pass the full check in update mode. I'm hoping my attempt below will pass that check and still update with the modifications.
Click to expand...
Click to collapse
after rsa key replaced, do you have recalculate the checksum of UPD file?
have you replaced the first 64 bytes of the file?
thanks
@itsJRod, isn't it that you would like to explain the procedure to replace the RSA key in the swdl file? thank you
Hello,
have you made any progress? I am a bit lost. I put the EU uconnect MY15 to US dodge charger MY16 and Perf Pages were working fine even on 16.16.13, although after upgrade to 17.x (17.46.0.1 right now) I am meeting the problem of expired subscription (which is not possible to have on EU radio).
I am considering basically three solutions:
a) going back to US radio, but modify the language pack/nav/FM frequencies (it is doable, but I do not know how, although I can pay for it relatively less than time invested)
b) downgrade to 16.16.13 - I have no clue how to do it, I tried to put swdl.upd with swdl.iso as and installer.iso with no luck of course.
c) take xlets from KIM2/ of 16.16.13 to KIM23 of 17.46.0.1 secondary.iso - this is probably preferred way but I do not know how to make it to pass ISO validation.
Of course root on uconnect is extremely nice to have but I will be fully satisfied with Perf Pages working again.
Hello.
I'm hoping the community can help me out. I have a RAM 1500 with the RA4 (was running the 17.11.07 software that I got pushed to me OTS style a couple years ago. Since them problems, radio turn on delay, no GPS and cellular phone warning popup.
I was told to do the 18.45 update which I got from driveuconnect.com, but this has essentially bricked my radio with the "bolo update failed" error and it is looping continuously
I have tried many ways to modify the update software's manifest.lua script to try to get rid of the sierra wireless portion by manually editing, hex editing, etc but always get the "please insert the USB card" screen.
Uconnect is obviously completely worthless to help me and the dealer wants me to pay them money to tell me what I already know. I know I can pay 300 and send my radio to infotainemnt.com to get it repaired, but I would like to solve this on my own is possible, because I would like to further modify the software to make it more custom and unique.
From my reading the 17x version keeps you from downgrading to a version that can be hacked easily.
Everything seems like it should be pretty straight forward as I have a lot of experience in programming and embedded devices.
It seems they are validating the ISOs using some mechanism, I believe I have tried all of tricks/methods
I have searched the code to see if I can find the iso MD5 or SHA256 hashes that ioc_check is probably using to figure out I changed somethign but nothing work.
I have even tried the swapping the flash drives after validation but it seems they are using the ISos they already copied to continue the process, I then end u getting some invalid errors or the update just crashes out
I got other updates from the link: http://www.mydrive.ch/
http://www.mydrive.ch/http://www.mydrive.ch/
username: [email protected]
Password: gasolio
Havent tried all of them yet, but pretty sure they wont work, due to the 17x security changes.
Any help would be appreciated grealty, I really dont want to shell out any cash for something a company told me to to and due to their screw up with bricking modems, this is now bricking my radio.
Thanks to all in advance !!!
djmjr77 said:
Hello.
I'm hoping the community can help me out. I have a RAM 1500 with the RA4 (was running the 17.11.07 software that I got pushed to me OTS style a couple years ago. Since them problems, radio turn on delay, no GPS and cellular phone warning popup.
I was told to do the 18.45 update which I got from driveuconnect.com, but this has essentially bricked my radio with the "bolo update failed" error and it is looping continuously
I have tried many ways to modify the update software's manifest.lua script to try to get rid of the sierra wireless portion by manually editing, hex editing, etc but always get the "please insert the USB card" screen.
Uconnect is obviously completely worthless to help me and the dealer wants me to pay them money to tell me what I already know. I know I can pay 300 and send my radio to infotainemnt.com to get it repaired, but I would like to solve this on my own is possible, because I would like to further modify the software to make it more custom and unique.
From my reading the 17x version keeps you from downgrading to a version that can be hacked easily.
Everything seems like it should be pretty straight forward as I have a lot of experience in programming and embedded devices.
It seems they are validating the ISOs using some mechanism, I believe I have tried all of tricks/methods
I have searched the code to see if I can find the iso MD5 or SHA256 hashes that ioc_check is probably using to figure out I changed somethign but nothing work.
I have even tried the swapping the flash drives after validation but it seems they are using the ISos they already copied to continue the process, I then end u getting some invalid errors or the update just crashes out
I got other updates from the link: http://www.mydrive.ch/
http://www.mydrive.ch/http://www.mydrive.ch/
username: [email protected]
Password: gasolio
Havent tried all of them yet, but pretty sure they wont work, due to the 17x security changes.
Any help would be appreciated grealty, I really dont want to shell out any cash for something a company told me to to and due to their screw up with bricking modems, this is now bricking my radio.
Thanks to all in advance !!!
Click to expand...
Click to collapse
Just to follow up for anyone who reads this in the future.
I was able to get my uconnect working again a few minutes ago.
As my previous post stated I got stuck in the "bolo update failed" loop.
I downloaded the UCONNECT_8.4AN_RA4_16.33.29_MY16.exe update from the url posted in my previous comment.
I did the S Byte HEX Mod to the swdl.iso file, loaded it and the swdl.upd file on a thumb drive. Used Hxd on windows. Followed the section in the Uconnect exploitation PDF:
https://www.google.com/url?sa=t&source=web&rct=j&url=http://illmatics.com/Remote%2520Car%2520Hacking.pdf&ved=2ahUKEwjZsOGNl5nyAhWhGVkFHZy2AnAQFnoECAcQAg&usg=AOvVaw0NAi3a1eh-IRd3n1VHv-ys
When I plugged it in, it started with the update process, after the first unit, the screen said the Uconnect had to restart, please wait..
And whalaa my radio worked again!!! It even says it has the 18.45 firmware on it.. go figure.. Navigation still does not work, but thats most likely because the sierra wireless card is bad.
I cannot say for sure the S Byte thing did anything, because I'm not messing with this anymore, almost had to buy a new radio.
I would say try it with out, then with it if it doesn't work.
This could also be a fluke with my particular unit, but at least its something else to try than pay 600+ dollars!!
Good luck to anyone else who goes through this mess!!!
djmjr77 said:
Just to follow up for anyone who reads this in the future.
I was able to get my uconnect working again a few minutes ago.
As my previous post stated I got stuck in the "bolo update failed" loop.
I downloaded the UCONNECT_8.4AN_RA4_16.33.29_MY16.exe update from the url posted in my previous comment.
I did the S Byte HEX Mod to the swdl.iso file, loaded it and the swdl.upd file on a thumb drive. Used Hxd on windows. Followed the section in the Uconnect exploitation PDF:
https://www.google.com/url?sa=t&source=web&rct=j&url=http://illmatics.com/Remote%2520Car%2520Hacking.pdf&ved=2ahUKEwjZsOGNl5nyAhWhGVkFHZy2AnAQFnoECAcQAg&usg=AOvVaw0NAi3a1eh-IRd3n1VHv-ys
When I plugged it in, it started with the update process, after the first unit, the screen said the Uconnect had to restart, please wait..
And whalaa my radio worked again!!! It even says it has the 18.45 firmware on it.. go figure.. Navigation still does not work, but thats most likely because the sierra wireless card is bad.
I cannot say for sure the S Byte thing did anything, because I'm not messing with this anymore, almost had to buy a new radio.
I would say try it with out, then with it if it doesn't work.
This could also be a fluke with my particular unit, but at least its something else to try than pay 600+ dollars!!
Good luck to anyone else who goes through this mess!!!
Click to expand...
Click to collapse
I created an account just to reply to this and All I have to say is you're literally an absolute life saver. I've been working on this every day for two weeks now, trying every trick people said, trying every USB, every format, every version and nothing ever worked from me. Uconnect support was absolutely no help and it was a lot of back-and-forth finger pointing and no you need to reach out to this person between them and the dealership. Dealership tried to charge me for a Proxy Alignment when I asked to just update my damn radio stuck in this loop.
I have a 2015 Jeep Cherokee 8.4AN VP4 NA Head Unit 68238619AJ. I was updating from 17.11.07 to 18.45.01 and got stuck at the step 11 1% and would get a failed sierra wireless every time and then got in that "bolo update failed" loop..Well to fix it just now all I did was download the UCONNECT_8.4AN_RA4_16.33.29_MY16.exe update from the url posted in the previous comment and quick format to FAT32 on a 16GB Micro Center USB extracted the files from 16.33.29 to the USB with 7ZIP, plugged in like normal and BOOM it ran the first step restarted and I had a working radio again showing update 18.45.01.
(So i'm assuming you don't have to do the S Byte thing I didn't even mess with it I just used the 16.33.29 to bypass step 11 since that version only has 14 steps and 18.45.01 was already preloaded from attempting before. My navigation still is the wrong address but I don't care about all that just thankful to have my radio back before my wife killed me for trying to update it by myself. )
I hope this helps someone else one day because it took some deep research and hours on hours of forum hoping to finally find the solution. <3
djmjr77 said:
Just to follow up for anyone who reads this in the future.
I was able to get my uconnect working again a few minutes ago.
As my previous post stated I got stuck in the "bolo update failed" loop.
I downloaded the UCONNECT_8.4AN_RA4_16.33.29_MY16.exe update from the url posted in my previous comment.
I did the S Byte HEX Mod to the swdl.iso file, loaded it and the swdl.upd file on a thumb drive. Used Hxd on windows. Followed the section in the Uconnect exploitation PDF:
https://www.google.com/url?sa=t&source=web&rct=j&url=http://illmatics.com/Remote%2520Car%2520Hacking.pdf&ved=2ahUKEwjZsOGNl5nyAhWhGVkFHZy2AnAQFnoECAcQAg&usg=AOvVaw0NAi3a1eh-IRd3n1VHv-ys
When I plugged it in, it started with the update process, after the first unit, the screen said the Uconnect had to restart, please wait..
And whalaa my radio worked again!!! It even says it has the 18.45 firmware on it.. go figure.. Navigation still does not work, but thats most likely because the sierra wireless card is bad.
I cannot say for sure the S Byte thing did anything, because I'm not messing with this anymore, almost had to buy a new radio.
I would say try it with out, then with it if it doesn't work.
This could also be a fluke with my particular unit, but at least its something else to try than pay 600+ dollars!!
Good luck to anyone else who goes through this mess!!!
Click to expand...
Click to collapse
Do you have another link to download the UCONNECT_8.4AN_RA4_16.33.29_MY16.exe files? I am trying to help a friend of mine they way this helped me. Thank you again for this!
Hi,
My problem is with 65P815. Fabric software was v084, i tried to update to V191 official version from TCL page, but after update and turning off TV, there is nothing shows on screen. I hear only sounds, and remote clicks, menu gone etc.
I search for info, and go back to v083 software, that helped and fixed TV. But now I don't know what to do to fix my TV. Tried to update with factory reset, nothing helped. Any tips how to deal with it ?
Next thing is concerned with soundbar thing, I have LG soundbar, is it possible to control soundbar over TCL's remote ? On my old Samsung TV it worked normally.
Here in TCL I don't see option to choose sound sourec (tv speaker/optical/hdmi), there is no option to mute TV speaker and move sound to soundbar. For now I use 2 remotes, but I want to use only one like in Samsung. I connected soundbar with optical cable to my TV.
Hi there. Trapped into same thing. After flash, I can hear 'bing' when you navigating in menu, backlight is working, but screen still black. Tried to flash V191(Inserted stick to USB2.0 with Update.img and plugged in with power button pressed). But got same thing. Led is blinking during i suppose flashing, but after that - nothing. Can it be somehow reset to stock or whatever?
you have to go back to 0.83
Turn off the TV, plug out the cable. put the drive into usb 2.0, press power button on TV's back and plug in power cord, if led start blinking wait about 10 mins to finish flashing. Sometimes you have to do this twice and TV will be ok.
Write to TCL support about your problem, let them prepare patch
Hmm... I have couple of questions then.
Does that mean v083 firmware didn't published somewhere?
And does that mean that we can't update 65p815 to any new firmware with Android 11?
what was your native FW ?
I tried to update to V191 which is on android 9, and update was failure. There is something wrong with the FW
File upload and sharing. Large file transfers. Free online cloud storage.
Visit this link to download: V8-R51MT02-LF1V083.zip
files.fm
here you can find v0.83
Android 11 is in beta now, we have to wait for official final update
I didn't check my original fware version. I know that was very stupid, but i supposed that just platform is matter.
Thanks for link. Will try this fware. Hope that will help, because i don't like to waste time with support, that usually just redirects to another operator...
it should, try second time if the first will failure
Ok, i just finish downloading and i'll start bring that baby to life. Thanks for help. Will report if suceed.
report it to TCL support to make technical request, and to fix that firmware
Ok. Just flashed twice. God damn, you have been right! All works like charm!
If someone will be as "lucky" as me, steps are next:
1. Load to local pc zip from above.
2. Format flash stick with FAT32 and copy it to root.
3. Insertt stick into USB 2.0 port.
4. Turn off TV power physycally.
5. Press and hold On/Off button on a TV's back and plug TV holding button pressed.
6. Hold for 10 secs, the led in front of TV will start blinking - it is ok.
7. Wait till it will stop blinking and wait some 5 mins after that.
8. Repeat steps 4-7. After TV restart it will show TCL logo and Android welcome screen will appear.
Ok now we should think about how to flash properly new version of FW,
latest official firmware is
https://www.mediacenter.tcl.eu/uploads/common/R51M_Android_P_V191.zip
When I try to flash with it, from menu update/local it works but only first time. When I turn off TV, then screen is black
I found such instruction, what to do after installation
Press the Settings button in the remote control:
Press OK on the icon: Picture.
Then go to the line Advanced settings.
Scroll down to the line: Brightness settings.
Scroll down to the line: Contrast.
With the remote control, do the key sequence: 6 4 2 5
The special menu appears.
Go to the line “Reset All” and press OK.
Go to the line “Reset Shop” and press OK.
Now unplug the main power cord.
Wait for ~2 minutes.
Plug back the main power cord and perform complete installation.
Click to expand...
Click to collapse
but haven't tested it yet.
Guys, can you post "Project ID" of your P815?
As ,for firmware V191 supose to be as attached....
50P815.....285
55P815.....284
65P815.....283,305
TV panel type can be found in service menu.....Main menu (1950)...
Just grabbed my panel name.
stasiof said:
Guys, can you post "Project ID" of your P815?
As ,for firmware V191 supose to be as attached....
50P815.....285
55P815.....284
65P815.....283,305
TV panel type can be found in service menu.....Main menu (1950)...
Click to expand...
Click to collapse
Seems on mine 65P815 by your table, the code should be ST6451D02-3 (code 305), but i have ST6451D02-H (code 283).
I have flashed v272 (img file) from v084 to my 65P815. Flashing went smoothly with no black screen ecountered. v272 works nicely with no problem.
TCL Android TV model 55p8m / Android Recovery TCL/BeyondTV/BeyondTV
My TCL Android TV model 55p8m has stuck and can't press any key in remote. The screen gives options to - Try Again - Factory data reset, but do not know how to select one of this option and continue without a keyboard or remote connected to the...
forum.xda-developers.com
@ancifil said:- "Did you reboot your TV after that?"
Sure I had rebooted it after flashing as I have been using this firmware for about a month.
I remembered flashing it 2 times. The first time was not successful (can't remember due to what). The second time reflash (same as what you did as in post #10) was smooth and without any problem.
jngiag, looks like it should, as for me... Maybe, i shall try 272 one more time.
superfly86, did you try 272?
jngiag said:
I remembered flashing it 2 times. The first time was not successful (can't remember due to what). The second time reflash (same as what you did as in post #10) was smooth and without any problem.
Click to expand...
Click to collapse
Btw, one thing. Can you remember, after you had flashed 272 first time and after that launched flash menu, to flash second time, was you able to see menu?
ancifil said:
Btw, one thing. Can you remember, after you had flashed 272 first time and after that launched flash menu, to flash second time, was you able to see menu?
Click to expand...
Click to collapse
I think it was due to a request to input pin while I was trying to setup live TV. I did not know the pin so I powered it off and reflashed as in post #10. Sorry, I can't remember it exactly.
ancifil said:
Seems on mine 65P815 by your table, the code should be ST6451D02-3 (code 283), but i have ST6451D02-H (code 305).
Click to expand...
Click to collapse
Your 65P815 with panel ST6451D02-H...... Project ID MUST be 283.
This is your problem with firmware (black screen ) !
So you need to change ID number from 305 to 283.
To modify the project ID, when TV is ‘ON’, with the remote control do the key sequence
0 6 2 5 9 8 .....MENU.... 283.
At the end of the key sequence the TV must reboots alone if the project ID has been understood by the TV. If it doesn’t, update the product with the last software available and try again.
Sometimes several tries can be necessary for successful project ID modification.
stasiof said:
Your 65P815 with panel ST6451D02-H...... Project ID MUST be 283.
This is your problem with firmware (black screen ) !
Click to expand...
Click to collapse
I've got that. But the hard thing is that i will not see this manipulation... I have to do that blindly. Risky stuff, right?