As my joying head unit only allows certain devices to connect due to Joying Bluetooth crippling, would adding a Bluetooth dongle allow other devices, or will the limitations still apply to the USB input?
looking for the same answer. Apparently older models could use Bluetooth dongle so long as it was the same exact Bluetooth chipset found inside the android head unit. Secondly, the Bluetooth config has to be altered to use the external dongle instead of the internal chipset. This was ~2017 era. So far nobody has fixed the Bluetooth exclusivity limitations. The only other way is if you have the FYT 7862 headunits and use custom firmware and rom to bring back bluetooth control thru the custom FYT mamager.
Tricky13 said:
As my joying head unit only allows certain devices to connect due to Joying Bluetooth crippling, would adding a Bluetooth dongle allow other devices, or will the limitations still apply to the USB input?
Click to expand...
Click to collapse
Does Bluetooth only reconnect to the last device used?
My unit allowed me to pair multiple phones (my wife and daughter also drive) but the Bluetooth system would only reconnect to the last phone used. So if I drove the car last, and then my wife drives, it won't connect to her phone without manually...
forum.xda-developers.com
Follow that thread, it might turn out useful
this is the best thing to happen to android HUs. You need YFT models for this firmware to work. https://forum.xda-developers.com/t/...dition-with-fmc.4542673/page-30#post-88513899
Unfortunately, nothing that would help my head unit in that thread.
Onkypig said:
looking for the same answer. Apparently older models could use Bluetooth dongle so long as it was the same exact Bluetooth chipset found inside the android head unit. Secondly, the Bluetooth config has to be altered to use the external dongle instead of the internal chipset. This was ~2017 era. So far nobody has fixed the Bluetooth exclusivity limitations. The only other way is if you have the FYT 7862 headunits and use custom firmware and rom to bring back bluetooth control thru the custom FYT mamager.
Click to expand...
Click to collapse
Thank you for that must be the first understandable and helpful comment I have had so far.
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Tricky13 said:
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Click to expand...
Click to collapse
So does a BT keyboard. I use that when I need to type a lot on my unit, for example when using the linux terminal.
But a Bluetooth dongle will not help at all.
But you are asking the same question again and again and do it by cross-posting in several threads. I already pointed you to the same thread as @louforgiveno did in post #3.
It DOES contain relevant information for your unit and it DOES contain the info you need to be able to pair more devices. I think it is because you only look at the title or because you don't understand it or did not read it completely, but it exactly gives the information you need.
It doesn't help to ignore that.
I do not understand either why you mention that the reply from @Onkypig is understandable. It leads to one of my posts explaining a flashing issue due to a corrupt USB-stick. There is no relevance at all to this question.
As I said before I am a newbie to doing anything to tweak Android head units or anything Android for that matter, and so far all I get is pointed to threads that apparently are supposed to be of some help but most of which I don't understand, but the end result is I just get criticised for not posting in the right place (this forum is bloody confusing to a newbie!) and not being able to understand the jargon instead of being offered help, so pardon me for being uneducated in Android.
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
surfer63 said:
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
Click to expand...
Click to collapse
Tricky13, for real this is the answer and it was in that thread. One thing you'll learn if you hang out here long enough, is that @surfer63 usually has the answer and there aren't many, if any, who know these units better than him.
surfer63 said:
Being new to "something" is OK. We all started that way. But you were saying that that thread that was mentioned by both @louforgiveno and myself was not (relevant) for your unit. By saying that you give a totally different impression to us.
Check what value your sys.fyt.bluetooth_type is.
- If you have your original firmware, check the config.txt
- If you don't have that, then check it yourself
- If you don't know how to do that, then download, install and run my HWGetInfo (from my signature below my posts). It will show you.
If the value is 1, create a config.txt containing sys.fyt.bluetooth_type=0
If the value is 0, create a config.txt containing sys.fyt.bluetooth_type=1
Save that text file onto a clean usb-stick and copy the lsec6315update from your Joying firmware also on that usb-stick, and nothing more than those two files.
Flash your unit with this and try again.
If it doesn't work, replace the value in your config.txt and put the original value back in. Flash that again.
Click to expand...
Click to collapse
Thank you for explaining, I have used the HWGetinfo and found the sys.fyt.bluetooth_type=1 however not sure what/where the lsec6315update is, and how do you flash this to the unit?
Does the USB stick need to be formatted to anything in particular?
Tricky13 said:
Thank you for explaining, I have used the HWGetinfo and found the sys.fyt.bluetooth_type=1 however not sure what/where the lsec6315update is, and how do you flash this to the unit?
Does the USB stick need to be formatted to anything in particular?
Click to expand...
Click to collapse
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
dishe2 said:
Tricky13, for real this is the answer and it was in that thread. One thing you'll learn if you hang out here long enough, is that @surfer63 usually has the answer and there aren't many, if any, who know these units better than him.
Click to expand...
Click to collapse
Must admit that I wish I understood coding, but I admire those that can write and understand it.
surfer63 said:
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
Click to expand...
Click to collapse
Many thanks for your help and patience, I will give it a try and report back.
Tricky13 said:
On a side note, I tried a Bluetooth mouse and that worked with its own dongle.
Click to expand...
Click to collapse
Any "Bluetooth mouse" with its own USB adapter is probably not actually Bluetooth.
It's simply a wireless mouse using the 2.4 GHz ISM band for communication.
To see if this is the case just plug the USB adapter into a desktop and look at the USB configuration descriptor.
That's lsusb -v in Linux or the usbview.exe utility in Windows.
What you'll see is what looks like a wired USB mouse, not a Bluetooth adapter.
surfer63 said:
The USB-stick must be formatted as FAT32.
Unzip below zip onto it.
Put it in your unit and it will flash automatically.
After reboot test your BT devices.
If it did not help, change the value in the config.txt back to 1 and flash again to "restore" to original state.
Click to expand...
Click to collapse
Just before I go ahead, I am using the latest update firmware ...
Here is the firmware for 10.1" 1920*1200:
Updated files please click Here.
Applicable Radio Models: UQS10N4G-H, UQS10N6G-H, UQD10N4G-H, UQD10N6G-H
Just wanted to check this is OK ?
Tricky13 said:
Just before I go ahead, I am using the latest update firmware ...
Here is the firmware for 10.1" 1920*1200:
Updated files please click Here.
Applicable Radio Models: UQS10N4G-H, UQS10N6G-H, UQD10N4G-H, UQD10N6G-H
Click to expand...
Click to collapse
I don't understand. Do you mean to use this as backup?
Or do you want to use it to flash? This you should not do. Only the files I put in that zip. The only thing is that if it doesn't flash, you take the lsec6315update out of the firmware and copy that onto the usb-stick.
surfer63 said:
I don't understand. Do you mean to use this as backup?
Or do you want to use it to flash? This you should not do. Only the files I put in that zip. The only thing is that if it doesn't flash, you take the lsec6315update out of the firmware and copy that onto the usb-stick.
Click to expand...
Click to collapse
No I mean that is the firmware I am currently using, I updated late last year, and I just wanted to check that it was OK to go ahead with using the one you provided as I know Joying use different for each display resolution.
Tricky13 said:
No I mean that is the firmware I am currently using, I updated late last year, and I just wanted to check that it was OK to go ahead with using the one you provided as I know Joying use different for each display resolution.
Click to expand...
Click to collapse
In the zip file surfer63 gave you is 2 files, not a firmware. An lsecupdate file that doesn't actually do anything other than tell the unit it is to be flashed. There's also a config.txt file with a single line, making only 1 change.
If it doesn't have the desired effect, change the 0 to a 1 in the config.txt, flash it again and everything will revert back to how it was.
It matters not what device you have or what firmware you are running.
j0hn83 said:
In the zip file surfer63 gave you is 2 files, not a firmware. An lsecupdate file that doesn't actually do anything other than tell the unit it is to be flashed. There's also a config.txt file with a single line, making only 1 change.
If it doesn't have the desired effect, change the 0 to a 1 in the config.txt, flash it again and everything will revert back to how it was.
It matters not what device you have or what firmware you are running.
Click to expand...
Click to collapse
Thank you! It always pays to double-check when you don't know exactly what you're doing.
Well, Bluetooth is still not connecting to the devices I want, but I now have an inverted screen!! Any ideas how to change this back?
I am going to revert the Bluetooth config back to as before, but no idea why the screen is now inverted?
At least being Joying, I can just spin it around on the mounts, but it's still very odd that It's become inverted?
Related
Hello, guys!
I've been using Odin for some time, I messed up my phone once, but then restored it...
Now what I'd like is to know exactly how it works, which files it writes (csc, pit, etc). I.e., I want to understand the internals.
After 10 minutes of googling, I didn't find absolutely anything about who makes this software and what's the official site and where can I find the docs.
Is there any chance that someone could point me to the right direction? At least the docs?
Thanks in advance!
Igor
I only know that's Samsung made. Google explains me that it was made by Jeong-Hwan Min Seung-Bum Kang.
http://www.faqs.org/patents/app/20080209201
it's a closed samsung software that no one fully understands
Thanks for the information.
c4manceph said:
Thanks for the information.
Click to expand...
Click to collapse
Well, no, I actually appreciate it
You see, I didn't even know that it was made by Samsung
It seemed to me that they used it to update apple devices as well, but obviously I was wrong.
Anyhow, my next question is: what every control in this program means? What are the files that you choose before the upload? PIT, Bootloader (is it like lilo or grub in linux?), PDA, Phone and CSC (heard that it is used for file allocation, but not sure). I guess, these should be more or less the same for every Android, not just a Samsung, right?
There are also the checkboxes: Re-partition (I kinda have a vague notion of what it does, but it's... vague), F. reset time, Phone EFS Clear?
Thanks in advance!
Igor
I would say you should hit up Benjamin Dobell, the creator of Heimdall. Since Heimdall is reverse-engineered from Odin, I would say he's a knowledgeable person concerning Odin.
Odin is a developer tool made by samsung that was leaked to the community to allow for flashing the modem and operating system with partitions to the compatible samsung phone.
It in conjunction with the drivers for your android device it will create a virtual serial com port , usually COM4 or COM5.
There are many posts on Odin on the forums, use search and you might be surprised what else you may pick up.
Hope this helps.
Thanks, guys!
It can be what you put back on your device after you bricked it. Or if you are rooting you can flash that on there to get root with a rom and Clockworkmod
tyvallely said:
It can be what you put back on your device after you bricked it. Or if you are rooting you can flash that on there to get root with a rom and Clockworkmod
Click to expand...
Click to collapse
Thanks, but it's a little... superficial. I know that you use it to upload some firmware stuff (new os, modded os, etc), I need more concrete info...
One down: csc
Just searched for "What is csc?"
http://forum.xda-developers.com/showthread.php?t=772201
Mithent said:
CSC is the Country/Carrier Specific Code (not sure exactly which it is, both kinda make sense). It contains the files for customisation for specific networks, so will have the APN settings, maybe custom ringtones or backgrounds, and can have programs too. Some CSC files contain a lot more than others, hence the file size differences.
Mixing different PDA/PHONE/CSC files is certainly possible, although it might be best not to stray too far on the PDA and PHONE side. The CSC isn't really very important in most cases - at worst you'll probably just have to set up the APN manually.
Click to expand...
Click to collapse
Found another one (.PIT files) here:
http://forum.xda-developers.com/showthread.php?t=771426
Richthofen said:
As far as I know .pit files are only used to tell Odin which file names to program to which "partition".
Even if separate images are used, Odin will treat them as a single image.
For example .pit file tells Odin to program modem.bin file to MODEM "partition", zImage to KERNEL "partition", etc.
If you use separate images (3-pack, CODE, MODEM, CSC), you can for example put CSC to CODE, MODEM to CSC and vice versa. Nothing odd will happen as long as you don´t tamper with the file names inside the tarballs.
Click to expand...
Click to collapse
Heimdall
A nice article on Heimdall:
http://forum.xda-developers.com/showthread.php?t=755265
i would suggest hemdall ... much better way to go about things
ROM for recovery G2X under the NVFLASH
This method necessary!
If the device is not loaded and not firmware in other ways! (If you downloaded the wrong firmware in the device)
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Download ROM: http://www.mediafire.com/?wfokxjxi7rfoaey
Mirror: http://www.megaupload.com/?d=C5LBU3DS
Download APX driver: http://www.mediafire.com/?k559zgjlqkd5ted
Installation Instructions:
Download both files
Unpack it to the C drive to their respective folder
Remove the battery
Hold Vol Up/Down (and keep them held)
Insert the USB cable
Install APX driver from the your APX folder
For windows 7(and vista? please confirm):
Open Device Manager in Windows and you should see "APX Device" listed with an error
Right click on the APX device
Select 'Update driver software'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory you extracted the APX Driver
Select the *entire* 'APX Driver' folder
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Unplug everything
Hold Vol Up/Down (and keep them held)
Insert USB cable
open your ROM folder:
Run Flash.bat file and wait for the process
After the logo appears on the LG phone
Unplug USB cable
Insert the battery
enjoy!
After that, I recommend to firmware device with help programms KDZ or LG Mobile Update
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Can't wait to check this out when I get home later. Regarding the kdz file, what exactly were you able to unpack from it? I've been able to extract 2 files (a very large .wbd file and a .dll file) but I couldn't figure out how to unpack them further, specifically the .wdb file.
ILUHA_89 said:
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Click to expand...
Click to collapse
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
Smallsmx3 said:
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
You described it right!
This method has helped resurrect my device!
ZeroT| Demented said:
So the point of this utility if it works is to make the g2x un f***able like even if u do u can fix?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes. It is almost as good as JTAG flashing the device. For Galaxy S devices using ODIN you still have to have the 'software download' mode working in the ROM and it is possible to brick a Galaxy S beyond the point of even getting this mode to be accessible leaving you the only way to fix the device through disassembling it and flashing via the JTAG pads. Using the NVFlash method you are flashing directly to the hardware through they Hynix flashing chip. I had another phone with a similar capability (I-Mobile i858 - Yuhua Touchstone device) and no matter how badly I F'd it up (I was developing custom roms for it) I had the similar low level flashing tool that could reflash the phone to stock so I could start over with a clean slate. If this method is legit, this is a big boon to the dev community for this device.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
After trying to firmware device with program KDZ or LG Mobile Update in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
ILUHA_89 said:
After trying to firmware device with program KDZ in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
Click to expand...
Click to collapse
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
jboxer said:
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
Click to expand...
Click to collapse
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
phburks said:
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
Click to expand...
Click to collapse
I won't be able to look at it until tomorrow as it is 11:31 p.m. here and time to go to bed. :-O ZZZzzzzz
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
i'll try it out and report back
........... Works like a charm
here mirror link
http://www.megaupload.com/?d=C5LBU3DS
What we really need is for someone to tell us how to create the config files for NVFlash so we can flash the baseband only. The new baseband is there and named 'P999_MDM.bin' if I am remembering correctly. No reason to flash an entire ROM when all someone wants is the updated baseband. If we can get the older baseband file also this tool could be used to revert the baseband also, if someone wanted to do that.
web_ninja said:
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
Click to expand...
Click to collapse
You don't have to buy anything. You just click on one sponsor site and it opens a new window. Thirty seconds later it will enable a download link. You need to click download two or three times if I remember correctly. I am at work now. I can mirror it in about ten hours if nobody else has done it yet. I looked at the files briefly and it looks legit.
Is this supposed to have a command interface? Or are you still typing in commands yourself?
I edited a cap!
Changed link to Mediafire
omarsalmin said:
Is this supposed to have a command interface? Or are you still typing in commands yourself?
Click to expand...
Click to collapse
Good question - that is what I am looking for rather then having to mess with the nvflash commands directly.
Update - this setup is similar to Paul's stock ROM recovery setup on modeco.com. As with his, you only have to "Run Flash.bat file and wait for the process". When I could not get off of the LGupdater screen by any other means, I ran this file from his post and it ran flawlessly - but of course I ended up with a 990's device. I tried to get back with other tools and firmware, but was never able to do it.
If this works OK, you would be able to restore your data, apps, or a nandroid and you are back in business.
I spent a week trying to restore my original (and best device as it turns out), so I am not going to fool with this right now myself. I did compare the config files from bot Paul's and this firmware and they are different - which looks real promising, as they are different.
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Did you run by using the flash.bat file? Did you hold volume up and down for the entire flash process?
Sent from my LG-P999 using Tapatalk
AimanF said:
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Click to expand...
Click to collapse
Did you have old of new baseband on before flashing? What was the state of your G2X before running this?
UPDATE: It appears that this works - but would like to 100% confirm. After all the disasters that occurred from running the LGupdater tool, this would be an important fix and should be stickied at some point. Current members know of the updater problems, but new buyers and member may not - so many may still have this problem down the road.
Therefore, I believe this is an important enough item to bring to closure and make readily available.
U saved my phone's life
THANK YOU THANK YOU
followed instructions restored completley to stock just like how i got phone out of box 2 weeks ago.
I was running eaglesblood v8 and had altered the vold.fstab file to switch mounts
from sdcard to internal and after that point i rebooted and media scanner said damaged sd card well i figured it just to be like an extension of a permission of sorts. and thought if formated it would the paths would switch no problem.
im actually kind of having a hard time rembering exactly what steps i did take to **** it up royally. but went into clockwork 5 to flash another rom from internal storage or same i cant rember now and did factory reset then all hell broke loose .
couldnt mount nothing except for system i tried formating sd card even though i dont have one probally ended up formating internal lol. formated system,
re flashed all recoverie versions including stock. i was getting so mad i called google HA by the way they got some pretty good music when u have to hold.
only thing i didnt try was to load up a rom on sd card and mount that but i really doubt it would have worked and plus i couldnt even use phone to do it lol
i need to go buy drive saved me some serious cash I would say this should be enough confirmation!!
I have an N8013 and I have been trying to go to 4.3 for a while. Like illusion rom... i've tried cwm a few versions even the latest, twrp, and even philz recovery as recommended and I even deleted the updater scripts as recommended. I for the life of me can not get past the zip file failing to flash. I've downloaded the rom multiple times, used odin to go back to completely stock, factory reset.... just about everything. There is one other dude tellin me to do this....
"I have a N8013, and deleting the assert and getprops works for me 100% of the time. However, it is important to note, two things. One you have to have the N8013 version of the ROM, which is labeled N80xx, and 2, when you go to install it after you have modified the file, you will get a validation error because the zip file will no longer match the MD5 validation, you have to install anyways. Other than that it works fine on my N8013, using CWM 6.0.3.1, running official CM 10.2."
But I dont know exactly what file he is talkin about. If ANYONE can help me out with this id be forever grateful.
First thing first. I'm guessing from what you don't understand is the MD5 validation.
So let me try to explain it. Doing an MD5 check, is basically checking the fingerprint of a file to the fingerprint posted. You get an MD5 sum by running it though a MD5 hashing program. Someone that knows the terms better then me will probably jump in and correct my terminology. But the best way of saying it is that by comparing MD5 sums, you are able to see if a file is unaltered.
Second, you'll want to make sure the file you download is compete and uncorrupted. So you run it though the hasher, and get the MD5 sum to check it against the posted numbers.
For "Illusion-v2.5.alpha-UNOFFICIAL-n8013.z" the MD5 Sum is: 95eb24cadc1a7721934a508e3ce97212
For "Illusion-v2.5.alpha-UNOFFICIAL-n8000.zip" the MD5 Sum is: 7789f71ca54647b43c352837702795a3
Now as for a hashing program, if you are on Windows, I would suggest a program called HashTab. http://implbits.com/
It puts the hashing into a tab so you can just right click the file, click Properties, and then "File Hashes"
So for the next thing that you need to do to make sure everything is good, is to check the MD5 sum of the file you download (unmodified) and make sure it is a good download. If all of that is good, then something else is going off.
I will note that right now I'm running the n8000 version on my n8013. Yes there are reasons I do that, even though the GSM hardware isn't in place. But using the n8000 version makes use of VoIP phones much easier.
Niscandia said:
First thing first. I'm guessing from what you don't understand is the MD5 validation.
So let me try to explain it. Doing an MD5 check, is basically checking the fingerprint of a file to the fingerprint posted. You get an MD5 sum by running it though a MD5 hashing program. Someone that knows the terms better then me will probably jump in and correct my terminology. But the best way of saying it is that by comparing MD5 sums, you are able to see if a file is unaltered.
Second, you'll want to make sure the file you download is compete and uncorrupted. So you run it though the hasher, and get the MD5 sum to check it against the posted numbers.
For "Illusion-v2.5.alpha-UNOFFICIAL-n8013.z" the MD5 Sum is: 95eb24cadc1a7721934a508e3ce97212
For "Illusion-v2.5.alpha-UNOFFICIAL-n8000.zip" the MD5 Sum is: 7789f71ca54647b43c352837702795a3
Now as for a hashing program, if you are on Windows, I would suggest a program called HashTab. http://implbits.com/
It puts the hashing into a tab so you can just right click the file, click Properties, and then "File Hashes"
So for the next thing that you need to do to make sure everything is good, is to check the MD5 sum of the file you download (unmodified) and make sure it is a good download. If all of that is good, then something else is going off.
I will note that right now I'm running the n8000 version on my n8013. Yes there are reasons I do that, even though the GSM hardware isn't in place. But using the n8000 version makes use of VoIP phones much easier.
Click to expand...
Click to collapse
Wow, thank you sir. No one has ever explained it to me like you did. I honestly appreciate it. I have a PC running windows 7 and I also have an iMac for my music. Not saying I completely understand how to do what your telling me but it puts in to a much greater perspective and for that, thank you. I know something is going wrong. This isn't my first rodeo but I definitely don't know how to change stuff around or dissect it yet. I started rooting and modifying about a year ago. Im a tech so in interests me. But I don't all that much time to dissect yet or understand what your saying exactly. I guess I just need a good download. Maybe I'll try the N8000 version instead. I don't care about the GPS and I use VOIP a lot more than I would GPS. I'll try that I guess. But thank you for the great response and for taking a moment to help a fellow androidian out.
Thought:
Could it be that im downloading the rom to my iMac, transferring to my pc via flash drive thats corrupting it somehow? I dont have hemidal or samsung drivers on my imac but it seems to download the files faster thats why im doing that. But when it finishes its a folder not a .zip so I transfer it to my pc and compress it with 7zip.
I think other people are getting the same error tho as well so maybe not..
RussellEstridge25 said:
Wow, thank you sir. No one has ever explained it to me like you did. I honestly appreciate it. I have a PC running windows 7 and I also have an iMac for my music. Not saying I completely understand how to do what your telling me but it puts in to a much greater perspective and for that, thank you. I know something is going wrong. This isn't my first rodeo but I definitely don't know how to change stuff around or dissect it yet. I started rooting and modifying about a year ago. Im a tech so in interests me. But I don't all that much time to dissect yet or understand what your saying exactly. I guess I just need a good download. Maybe I'll try the N8000 version instead. I don't care about the GPS and I use VOIP a lot more than I would GPS. I'll try that I guess. But thank you for the great response and for taking a moment to help a fellow androidian out.
Click to expand...
Click to collapse
Well to start, would be to download the Hashtab program and install it. That gives you easy access to the MD5 sums that you'll need so you can verify downloads.
Now on your Mac, I can only tell you how to do it from the command line. Open up a terminal window and type in without the quotes "md5 filename" replacing filename with the file you want the MD5 sum for.
Hashtab is a nice user friendly version, but it is a 3rd party program. Some people don't like those. So your choice there.
I can also tell you of the only real problem I have had so far with the Illusion Rom. Bluetooth Tethering doesn't work. Now what I mean by this is using Bluetooth on a Cell Phone to give Data to the Note is problematic. DHCP doesn't work til launched manually, and DNS servers don't work. So as long as you don't use Bluetooth Tethering for your Note you'll be fine. But if you use Bluetooth tethering ( a small group of people I know) might not want to upgrade quite yet.
RussellEstridge25 said:
Could it be that im downloading the rom to my iMac, transferring to my pc via flash drive thats corrupting it somehow? I dont have hemidal or samsung drivers on my imac but it seems to download the files faster thats why im doing that. But when it finishes its a folder not a .zip so I transfer it to my pc and compress it with 7zip.
I think other people are getting the same error tho as well so maybe not..
Click to expand...
Click to collapse
Now this explains the entire problem... Your Mac is unzipping the file, and probably destroying some of the symbolic links. Rezipping it still leaves the broken links and causes problems. I don't remember how to tell OSX (Mac) not to auto unzip files. But you'll need to do that or download it on your PC.
Niscandia said:
Well to start, would be to download the Hashtab program and install it. That gives you easy access to the MD5 sums that you'll need so you can verify downloads.
Now on your Mac, I can only tell you how to do it from the command line. Open up a terminal window and type in without the quotes "md5 filename" replacing filename with the file you want the MD5 sum for.
Hashtab is a nice user friendly version, but it is a 3rd party program. Some people don't like those. So your choice there.
I can also tell you of the only real problem I have had so far with the Illusion Rom. Bluetooth Tethering doesn't work. Now what I mean by this is using Bluetooth on a Cell Phone to give Data to the Note is problematic. DHCP doesn't work til launched manually, and DNS servers don't work. So as long as you don't use Bluetooth Tethering for your Note you'll be fine. But if you use Bluetooth tethering ( a small group of people I know) might not want to upgrade quite yet.
Now this explains the entire problem... Your Mac is unzipping the file, and probably destroying some of the symbolic links. Rezipping it still leaves the broken links and causes problems. I don't remember how to tell OSX (Mac) not to auto unzip files. But you'll need to do that or download it on your PC.
Click to expand...
Click to collapse
Dont you mean how to tell a mac how to autozip the files? But again thank you. That helps a lot.
RussellEstridge25 said:
Dont you mean how to tell a mac how to autozip the files? But again thank you. That helps a lot.
Click to expand...
Click to collapse
From how it sounds your Mac is auto-unzipping. You want the Mac to leave the downloaded zip file & leave it alone. Not to unzip & rezip it up. That is what is causing trouble, the unzipping and rezipping more then likely. So disable the "expand archives". Doing a quick search try reading up on it here to get Safari to behave. https://discussions.apple.com/thread/1483114?start=0&tstart=0
Niscandia said:
From how it sounds your Mac is auto-unzipping. You want the Mac to leave the downloaded zip file & leave it alone. Not to unzip & rezip it up. That is what is causing trouble, the unzipping and rezipping more then likely. So disable the "expand archives". Doing a quick search try reading up on it here to get Safari to behave. https://discussions.apple.com/thread/1483114?start=0&tstart=0
Click to expand...
Click to collapse
Thank you thank you thank you. You answered me exactly the way I needed to hear it. :good:
RussellEstridge25 said:
Thank you thank you thank you. You answered me exactly the way I needed to hear it. :good:
Click to expand...
Click to collapse
Just needed that key piece of info. That you where rezipping the file after using your Mac to download it.
Hope it installs this time around. But I would suggest learning how to check the MD5 sums as well. Doesn't hurt to be careful.
Niscandia said:
Just needed that key piece of info. That you where rezipping the file after using your Mac to download it.
Hope it installs this time around. But I would suggest learning how to check the MD5 sums as well. Doesn't hurt to be careful.
Click to expand...
Click to collapse
I completely agree. And I plan to. Didnt know it would be that easy. Again thanks man. But you completely helped me understand. I love learning about this when there is someone willing to teach.
I just downloaded the rom on my pc and its doing what it was before. I try putting the zip file in to my internal sd on my tablet and it says "CAN NOT COPY ITEM, The device has either stopped responding or has been disconnected"
It has not I can assure you. I've tried rebooting the tablet and pc when this happened before and still with no avail. I can copy other files to my tablet no problem. I've never ran into this before.
I cant even open the zip file or extract it to my desktop right now. Seriously, what the hell.
says windows cant open it cause the file is invalid. Must be that MD5 thing your tellin me to do. So now That im doing it on my windows pc should I install that program you mentioned?
RussellEstridge25 said:
I just downloaded the rom on my pc and its doing what it was before. I try putting the zip file in to my internal sd on my tablet and it says "CAN NOT COPY ITEM, The device has either stopped responding or has been disconnected"
It has not I can assure you. I've tried rebooting the tablet and pc when this happened before and still with no avail. I can copy other files to my tablet no problem. I've never ran into this before.
I cant even open the zip file or extract it to my desktop right now. Seriously, what the hell.
says windows cant open it cause the file is invalid. Must be that MD5 thing your tellin me to do. So now That im doing it on my windows pc should I install that program you mentioned?
Click to expand...
Click to collapse
I've had that problem before with windows. Not sure exactly what causes it, my guess is some data on the usb connection is causing it. Wrong driver or something.
When it happens changing USB ports, sometimes helps. Or you can use ADB to copy the file over. Not sure if you have used ADB before or not. The third way is to pull the Micro SD card out of your Note, and use an adapter (SD to USB) to put the file directly onto it from windows.
Only options I can think of off the top of my head for that problem. But it is one I've seen before.
Niscandia said:
I've had that problem before with windows. Not sure exactly what causes it, my guess is some data on the usb connection is causing it. Wrong driver or something.
When it happens changing USB ports, sometimes helps. Or you can use ADB to copy the file over. Not sure if you have used ADB before or not. The third way is to pull the Micro SD card out of your Note, and use an adapter (SD to USB) to put the file directly onto it from windows.
Only options I can think of off the top of my head for that problem. But it is one I've seen before.
Click to expand...
Click to collapse
Great ideas! I can try the sd one tomorrow. Day 3 lol. Wish Me luck
I may have missed this part, so I apologize. Is there any reason you can't just download it directly from the tablet, saving it to the sd card? It would assuredly cut down on the headache and potential file corruption during transfer between devices.
spycedtx said:
I may have missed this part, so I apologize. Is there any reason you can't just download it directly from the tablet, saving it to the sd card? It would assuredly cut down on the headache and potential file corruption during transfer between devices.
Click to expand...
Click to collapse
Already got cm10.3 up and running. The developer gave me a nightly build that had all the files taken out already. Had to download it twice but got it after putting it on my internal memory. Thank you for your help. The note 10.1 has a good community of people.
Hey all
I have bricked my t-mobile V20 trying to network unlock it.
Anyway, I have been investigating solutions to this problem, and well, let's say there is no easy solution for most people.
The problem as I see it, is that this chipset (msm8996), while not exactly super new, is for all intents and purposes VERY new indeed. Because of the widespread use of UFS NAND introduced with this cpu. Almost all phones based on these newer qualcomm chips use this modern storage, which works as a multi-LUN device. Meaning it will show as several independent logical storage devices depending on configuration. V20 has 7, or at least the H918 does.
In short, it means the storage device is no longer mounted in mmcblk0, but on /dev/sda sdb sdc... etc depending on how many LUN's.
So the community has not catched up yet to this new development. (Well I guess hard-brick has always been a pain for many phones, but this makes it worse)
Now there are, I think, 5 ways to approach the 9008 mode in this instance.
*JTAG: Bypass all this QC hodge-podge and program the darn NAND directly.
*USB with Box: Some type of box with the capability to program your specific phone. Proprietary, closed source, have to pay.
*USB with firehose: Program yourself with programs like QFIL. Need device specific "prog_ufs_firehose_8996*.elf" file. LG has not released this. Can probably only be leaked, which happens on occasion.
*Enter DL or 9006 mode: It may be possible to short certain test points on the motherboard, which will put the phone into 9006 or Download Mode. Would require instructions, or the Service Manual.
*SD-Card Rescue: Make an sdcard with the required partitions. Some say this can't be done on newer QC chips with UFS because of the aforementioned multi-LUN situation.
I have been looking into this SDCARD method, and I found some info on the DragonBoard 820C (which uses msm8996, with UFS). This board has 6 LUN's, so it's multi-lun just like V20.
If you see here: DragonBoard, there is listed a method of SD CARD rescue. The tools can be found here: db-boot-tools
Unfortunately I don't have a full dump of my partitions, so I only have the ones included in the TOT, or KDZ files. I tried making a image using those files, it didn't work, but something interesting happened. With this sd card inserted the phone does not show the qdloader 9008 port on my pc, actually nothing shows. I did double check using a normal card inserted, and yes with normal storage card qdloader 9008 mode appears.
So this is interesting and makes me think I should try some more with this, but I need someone with a T-Mobile H918 to dump their partitions. EFS is not needed (where the imei is).
Update: I currently don't need a dump (Except for engineering firmware).
Update2: I could not make the SD-Card boot work, see here (with normal firmware).
List partitions
Command: ls -l /dev/block/platform/soc/624000.ufshc/by-name/
Or this: ls -al /dev/block/bootdevice/by-name/
Then dd the relevant partitions not listed above: dd if=/dev/sd*1/2/3/4... etc of=/sdcard/"filename".img
As an example, maybe you can do it other ways, perhaps with an app.
You can also use the patched LGUP to dump partitions. Should be the simpler method.
In any case I will be grateful for your assistance, as I'm sure many others will if this pans out.
Engineering Rom: I got an idea, if I can't get this to work then maybe it's because the support isn't compiled in the bootloader. If I could get the eng-firmware (for H918) to test that it would be great. So please if you have an eng device or a dump of that, I would be thrilled try it out.
Update: Below I've attached a zip with a limited partition layout, and the commands to dump from adb. Use the patched LGUP for Engineering firmware. (actually, with engineering formware I need all, or most of the partitions. PM me if you have such a device)
Support your work. Lg
China user
I would certainly go the QPST/QFIL/Firehose method & my strategy would be to restore Download mode.
I'm sure once that has happened you can restore full firmware with the patched LGUP method here
Prowler_gr said:
I would certainly go the QPST/QFIL/Firehose method & my strategy would be to restore Download mode.
I'm sure once that has happened you can restore full firmware with the patched LGUP method here
Click to expand...
Click to collapse
Yes, but how would you go about doing that without the required firehose file? LG apparently uses certificate or some signing, so you can't use just any file.
Although that patched LGup is nice. If I had known about that tool before I messed up, I probably would not have messed up. Because then I wouldn't be afraid of loosing root, and just flashed H910pr with LGup, then flash back with the patched one later.
Edit: As I have later found out ^^this would not be a good idea. The result would be the same - BRICK Hard. Just as a precaution for anyone contemplating doing so. The H918 can not be flashed with any other V20 firmware, neither can you flash H918 firmware on any other V20.
askermk2000 said:
Yes, but how would you go about doing that without the required firehose file? LG apparently uses certificate or some signing, so you can't use just any file.
Although that patched LGup is nice. If I had known about that tool before I messed up, I probably would not have messed up. Because then I wouldn't be afraid of loosing root, and just flashed H910pr with LGup, then flash back with the patched one later.
Click to expand...
Click to collapse
I don't pretend to know the answer, but I believe that the firehose file is not any type of signed LG file, but just a partition layout (mbn or elf) file that can be generated from a .kdz file...
Make sure you use QPST_2.7.460 or later which supports MSM8996...
Google is your friend but you can start reading from here & here
Prowler_gr said:
I don't pretend to know the answer, but I believe that the firehose file is not any type of signed LG file, but just a partition layout (mbn or elf) file that can be generated from a .kdz file...
Make sure you use QPST_2.7.460 or later which supports MSM8996...
Google is your friend but you can start reading from here & here
Click to expand...
Click to collapse
Well, there is a difference between an MPRG and MSIMAGE/Singleimage. I believe you are thinking about the latter here. Those can be generated, but are of little use without a programmer file (mprg/firehose).
askermk2000 said:
Well, there is a difference between an MPRG and MSIMAGE/Singleimage. I believe you are thinking about the latter here. Those can be generated, but are of little use without a programmer file (mprg/firehose).
Click to expand...
Click to collapse
Remember we only aim to get bootloader mode, not the full layout...
Btw I probably wouldn't mind wasting $5 on this
Prowler_gr said:
Remember we only aim to get bootloader mode, not the full layout...
Click to expand...
Click to collapse
Yes I know. But Qualcomm and LG has made that very difficult for us. All the common info on the web so far is outdated, or doesn't work because of missing firehose file.
Except for possibly SDcard method.
Having read your OP again, of how you SD card affects how windows detects your phone, I believe this may be a good step to our solution. of getting the phone recognised in download mode
Prowler_gr said:
Having read your OP again, of how you SD card affects how windows detects your phone, I believe this may be a good step to our solution. of getting the phone recognised in download mode
Click to expand...
Click to collapse
Do you have brick as well?
I looked at that page, and pretty sure I've looked at it before. There is nothing there that can be of use.
askermk2000 said:
Do you have brick as well?
I looked at that page, and pretty sure I've looked at it before. There is nothing there that can be of use.
Also I'm very suspicious of that Aryk site. They don't seem to know what their talking about many times, their downloads dubious with viruses and the like. On the page you linked they claim QHSUSB_BULK is the same as 9008, while it is actually 9006.
It almost seems like that site was set up solely for the purpose of spreading malware or something. Just cobble up something random and presenting it like information, like with algorithms and bots or whatever.
I think there a lot of that stuff going on in the "gms" business. Like for example, on gsmarena I found a sticky thread which supposedly had files to repair a LG V20 which has been stuck in bootloop because of "use of cheap chinese usb-c cable". Anyway, that archive had some files, including a *prog_ufs_firehose_8996_lite.elf*. That file did not work, and there was an instructions file there also, in XLS format which contained virus.
Come to think about it. This whole crap with qualcomm "security" stuff seems like just a way to create the sub-market of gsm repair boxes. Well, who knows, just a guess on my part. But there's something fishy about the whole thing.
Click to expand...
Click to collapse
I was, I'm now unbricked (I worked out the method with the LGUP patch).
What I'm suggesting (as the website describes) is to write the v20 boot image to an SD card using Win32DiskImager/, & see if your device will boot with it, & then upgrade with LGUP.
I've got the H990DS variant (I can send you my boot image to try)
Prowler_gr said:
I was, I'm now unbricked (I worked out the method with the LGUP patch).
What I'm suggesting (as the website describes) is to write the v20 boot image to an SD card using Win32DiskImager/, & see if your device will boot with it, & then upgrade with LGUP.
I've got the H990DS variant (I can send you my boot image to try)
Click to expand...
Click to collapse
I would welcome a boot image, or images of partitions. That's why I started this thread mostly.
askermk2000 said:
I would welcome a boot image, or images of partitions. That's why I started this thread mostly.
Click to expand...
Click to collapse
link removed
Prowler_gr said:
...removed
Click to expand...
Click to collapse
Ok, I got it. Thx
Will try with this. Did you get it with LGUP ?
I extracted it from my phone
Prowler_gr said:
I extracted it from my phone
Click to expand...
Click to collapse
Im in this to but i have a lg g5 msm8996 board
me and him have been trying to work very closely to get a fix for msm8996 in gen of coarse he is worried about v20 me g5 but common interests.
i dont wanna knock any v20 discussions off track so im here but im sitting in the corner most quietly
he is def on the right track i have dealt with many hardbricks in the past
and the no reconition on pc is most def a good step
my problem is being a new moderator plus my job plus after hours work i dont have time to test a lot of stuff any more he has bought a lot of info to my eyes and am trying to work on what i can.
look and 8994 g4 it took 2 years for a hardbrick fix to come about only from people doing the same as we are
TheMadScientist420 said:
Im in this to but i have a lg g5 msm8996 board
me and him have been trying to work very closely to get a fix for msm8996 in gen of coarse he is worried about v20 me g5 but common interests.
i dont wanna knock any v20 discussions off track so im here but im sitting in the corner most quietly
he is def on the right track i have dealt with many hardbricks in the past
and the no reconition on pc is most def a good step
my problem is being a new moderator plus my job plus after hours work i dont have time to test a lot of stuff any more he has bought a lot of info to my eyes and am trying to work on what i can.
look and 8994 g4 it took 2 years for a hardbrick fix to come about only from people doing the same as we are
Click to expand...
Click to collapse
We agree he's on the right path (about SD method), that's why I sent him my boot image & suggested he burns it into an sd card. I'm hoping he only needs to boot with it & everything else would be straight forward
I burned the *.img file directly onto a 64gb uSDXC card. It creates a single 63gb fat mbr partition on the card. So it seems you managed to make a single complete image of your entire UFS chip. Have no idea how though, but I've not exactly had the chance to look into that myself because of brick.
The image, burned this way did not work, it's not even recognized by the phone as a boot image. I will see if I can perhaps extract the file from within the img-file and split that somehow.
Because windows can't edit/remove partitions on external devices, I used linux, since ubuntu's standard tools there can simply burn the image directly onto the device, automatically removing any partition scheme in the process.
That win32diskimager program is strange because it can not target device directly, but only mountpoint, and because my card was already formatted with numerous partitions from before, I could not use that program.
Prowler_gr said:
We agree he's on the right path (about SD method), that's why I sent him my boot image & suggested he burns it into an sd card. I'm hoping he only needs to boot with it & everything else would be straight forward
Click to expand...
Click to collapse
That has always been the rite track just to get to download mode.
I thank you for providing the files. Its always stressful when dealing with owns hardbrick. ive spent hours of burning images to mine lol even fried a couple sd cards
but most def seems as if you are knowledgeable also in this area so id love to keep you in this loop
If we all can pull this off. We will be the next heros of the day lol also if u are interested in reading some suposedly the s8+ also has same boards so even may be able to piece stuff from there
and i know sammys have been booted of sd in the past.
the more people we can get the better
Hi All,
I wanted to find the file that I need to use to update my Head Unit, had an issue and it displays an error saying "Canbus Serial port:/dev/ttyS1 was used! !" and unabled my steering buttons.
Does anybody knows which file or where can I look for it?
Thanks in advance!
MCU Version: 2021.03.16 18:42:45 NOR_812_F2N_G23P32f32_Ver: 1.0(FYT)
Device: sp7731e_1h10
And what did your reseller say?
I would not simply write another MCU firmware over my head unit.
And how did this happen? Did you already flash it with another firmware?
I chated with the reseller and indeed told me that I had reload the can Box files, for such thing, unfortunately after many atempts asking for such file the reseller simply would not provide such file, thats why I try to research for an alternative download.
being completly new to this I was playing around with the configurations and tried to upload a new firmware without having selected any , so I guess the configurations messed up afterwards.
I have seen many different firmwares for the head unit , but the head unit works fine excepting the steering controls , so I am not sure if I have to update the firmware of the entire headunit, or the MCU or the CAB Box configurations.
Is there any known library or repository for many known versions of such firmwares so I can take the closest one to it? and hope to not trash the entire head unit?
Thanks in advance!
Your s7731 is less wide spread than the uis7862 or uis8514. There are not so many and not so many in this forum. In this case you might take a look on 4pda.
did you find any solution ?
i think have same radio as you
Where did you get your ?
Any luck finding a newer MCU update ?
royo210 said:
I chated with the reseller and indeed told me that I had reload the can Box files, for such thing, unfortunately after many atempts asking for such file the reseller simply would not provide such file, thats why I try to research for an alternative download.
being completly new to this I was playing around with the configurations and tried to upload a new firmware without having selected any , so I guess the configurations messed up afterwards.
I have seen many different firmwares for the head unit , but the head unit works fine excepting the steering controls , so I am not sure if I have to update the firmware of the entire headunit, or the MCU or the CAB Box configurations.
Is there any known library or repository for many known versions of such firmwares so I can take the closest one to it? and hope to not trash the entire head unit?
Thanks in advance!
Click to expand...
Click to collapse
Have u found mcu file ?
ghannaiem said:
Have u found mcu file ?
Click to expand...
Click to collapse
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
royo210 said:
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
Click to expand...
Click to collapse
Thanks for sharing .
File is old and does not contain MCU.
MCU unlikely to be issue
marchnz said:
Thanks for sharing .
File is old and does not contain MCU.
MCU unlikely to be issue
Click to expand...
Click to collapse
Then what does that File contains?
How can you tell?
royo210 said:
I got this file from the seller after asking a lot, but unfortunately I haven't been able to execute the file, if anyone can execute this correctly can u give advice on how to proceed?
Click to expand...
Click to collapse
Mcu file should be named as "mcuall.bin "
Unfortunately they do not provide it with firmware update . any way thanks so much for the link and i'll use the firmware you provide hoping it will fix the problem
ghannaiem said:
Mcu file should be named as "mcuall.bin "
Unfortunately they do not provide it with firmware update . any way thanks so much for the link and i'll use the firmware you provide hoping it will fix the problem
Click to expand...
Click to collapse
What Issue you have and are trying to solve with this firmware?
royo210 said:
What Issue you have and are trying to solve with this firmware?
Click to expand...
Click to collapse
If car is parcked for more than 48 hours headunit goes to deep sleep then when start using and ignition is on it stuck on boot logo and it wont boot until i force restart it with reset button
ghannaiem said:
Mcu file should be named as "mcuall.bin "
Click to expand...
Click to collapse
Are you sure?
I believe the OP's device uses an MCU file named stm32ud.bin, just like other FYT devices.
Hi me also with this device is there any update or can the android be changed thanks
j0hn83 said:
Are you sure?
I believe the OP's device uses an MCU file named stm32ud.bin, just like other FYT devices.
Click to expand...
Click to collapse
Stm32ud is for Gd32f-------- mcu types like in teyes cc2l/plus
While my device and also @royo210 's device use another type mcu chip here below is a picture for
And it is named in the system info as
NOR_812_F2N_G23P32f32_Ver: 1.0(FYT)
royo210 said:
Canbus Serial port:/dev/ttyS1 was used!
Click to expand...
Click to collapse
this is caused by BSP Serial Debug option in Developers Settings. Disable it and never enable again
do not try to flash any mcu firmware just for fun, you might not be able to revert this back and i think 100% this won't help you with steering wheel buttons
Does someone who can help me to find the firmware and the MCU for this one?
Intel Sofia3gr Rockchip RK30SDK
MCU: FY_90_C9_7703_18EM_JY2009B
Security patch level: 01-06-2016