Honda Connect 6VC9 won't boot after sw update - Security Discussion

Hi All!
I have a Honda Connect audio system (39100-TB9-G61-M1)
After a navigation issue I updated the firmware on the device. The device updated correctly and rebooted. But, never started again.
I can flash the two file from usb after the device starting (ADA_usbdl_V0C.091.01_TV0X_04.zip and ADA_usbdl_V0E094001123_sec_14ada.zip)
But I can't flashing a file (AUD31CF.bin). The navi wrote: "There was a problem during the update. Please switch off the vehicle then restart to retry."
I restarted many times but nothings happened. the navi wont flash the file (AUD31CF.bin) and won't start.
What can I do whit this navi system?
Can somebody help me to recovering this system?

Rocco said:
Hi All!
I have a Honda Connect audio system (39100-TB9-G61-M1)
After a navigation issue I updated the firmware on the device. The device updated correctly and rebooted. But, never started again.
I can flash the two file from usb after the device starting (ADA_usbdl_V0C.091.01_TV0X_04.zip and ADA_usbdl_V0E094001123_sec_14ada.zip)
But I can't flashing a file (AUD31CF.bin). The navi wrote: "There was a problem during the update. Please switch off the vehicle then restart to retry."
I restarted many times but nothings happened. the navi wont flash the file (AUD31CF.bin) and won't start.
What can I do whit this navi system?
Can somebody help me to recovering this system?
Click to expand...
Click to collapse
!!!Update more information!!!!
I have a Fujistu FT0056A device. This device its a sat-nav in a Honda Civic.
The device is frozen. After a usb firmware flashing won't startet. Its in boot-loop. I tryed many solutions, but not working.
http://oi68.tinypic.com/w9jjvt.jpg
First time I tried to flashing from usb stick. I have thre original Honda flash file to tis device:
- For SH USB1 - AUD31CF.bin - I can't extract the bin file. Maybe this contain the boot and recovery images. - I can't flash with via usb stick. Its a error message... Maybe
this bin file contain the boot and the recovery images.
- For tegra EC/NC USB2 - ADA_usbdl_VL0.FFF.04_EXT_HFT_param02.zip - Flash zip file loaded up correctly to the device via usb stick.
- For Tegra USB3 - ADA_usbdl_V10096001123_sec_14ada.zip - Flash zip file loaded up correctly to the device via usb stick. This zip file contain a
"ADA_usbdl_10.096.00.1123.enc" file. Can't decrypt or extract. Its a password protected file. I not know whats the password...
I tried to downgrade, with older and upgrade with newer wersions, but not working....
Now I tried flashing via OTG USB on the USB-B system port
I can't find any driver to the device. I found many driver (apx ; nvidia shield ; toradex_usbpcdriver_32_64 ; universal naked drivers ; etc.) but the ****usb.inf file not
contains any record of this device, what they call it:
USB_Install, USB\VID_0955&PID_7102
USB_Install, USB\VID_0955&PID_7102&REV_0232
After the inf editing and With forced install, i can connecting the driver to the device with many "name":
NVIDIA USB Boot-recovery driver for Mobile devices"
NVIDIA Android Fastboot Device
NVIDIA Android Composite Device
Android Debug Bridge Interface
etc....
I found thre diferent driver dll version too:
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
-------------------------
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01007.dll
------------------------
and
WUDFUpdate_01009.dll in another file size....
the device not aswered to the fastboot.
Fastboot devices
Cant find any device
Only the xiaomflash.exe can read a a devise serial:
015e8b67e833fc08
but, cant flash the device....
the virtualbox can read the device informations:
http://oi65.tinypic.com/jsjcys.jpg
After adding the usb and post settings in the virtualbox, i tried flashing the board wint ubuntu.
same as with windows. The device its in the ubuntu usb device list:
http://oi64.tinypic.com/2h2kqhg.jpg
but, if i like to flash the device, nothings happened. The flasher wait for the device...
http://oi63.tinypic.com/zwi52s.jpg
So.....
how can I find a solution for flashing this board?
Its any not public device driver to this device?
How can I flash the SH AUD31.bin?
Becouse i think the Tegra files loaded up correctly via USB stick. Now i must to give a "fastboot -w" command to the device, and then can booting correctly. I tried with
"fastboot -i 0x0955 -w command too". not working.
I think I must flashing the bin file with a eeprom félasher. I have eprom flasher, but the flasher can't flash this eeprom. find any eeprom flasher under 600$ for this
"25C512A" eeprom.
So.....
How can i unbrick tis device?
Any solution?
Thanks for the reply
Kind REgads,
Rocco

Rocco said:
!!!Update more information!!!!
I have a Fujistu FT0056A device. This device its a sat-nav in a Honda Civic.
The device is frozen. After a usb firmware flashing won't startet. Its in boot-loop. I tryed many solutions, but not working.
http://oi68.tinypic.com/w9jjvt.jpg
First time I tried to flashing from usb stick. I have thre original Honda flash file to tis device:
- For SH USB1 - AUD31CF.bin - I can't extract the bin file. Maybe this contain the boot and recovery images. - I can't flash with via usb stick. Its a error message... Maybe
this bin file contain the boot and the recovery images.
- For tegra EC/NC USB2 - ADA_usbdl_VL0.FFF.04_EXT_HFT_param02.zip - Flash zip file loaded up correctly to the device via usb stick.
- For Tegra USB3 - ADA_usbdl_V10096001123_sec_14ada.zip - Flash zip file loaded up correctly to the device via usb stick. This zip file contain a
"ADA_usbdl_10.096.00.1123.enc" file. Can't decrypt or extract. Its a password protected file. I not know whats the password...
I tried to downgrade, with older and upgrade with newer wersions, but not working....
Now I tried flashing via OTG USB on the USB-B system port
I can't find any driver to the device. I found many driver (apx ; nvidia shield ; toradex_usbpcdriver_32_64 ; universal naked drivers ; etc.) but the ****usb.inf file not
contains any record of this device, what they call it:
USB_Install, USB\VID_0955&PID_7102
USB_Install, USB\VID_0955&PID_7102&REV_0232
After the inf editing and With forced install, i can connecting the driver to the device with many "name":
NVIDIA USB Boot-recovery driver for Mobile devices"
NVIDIA Android Fastboot Device
NVIDIA Android Composite Device
Android Debug Bridge Interface
etc....
I found thre diferent driver dll version too:
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01009.dll
-------------------------
WdfCoInstaller01009.dll
winusbcoinstaller2.dll
WUDFUpdate_01007.dll
------------------------
and
WUDFUpdate_01009.dll in another file size....
the device not aswered to the fastboot.
Fastboot devices
Cant find any device
Only the xiaomflash.exe can read a a devise serial:
015e8b67e833fc08
but, cant flash the device....
the virtualbox can read the device informations:
http://oi65.tinypic.com/jsjcys.jpg
After adding the usb and post settings in the virtualbox, i tried flashing the board wint ubuntu.
same as with windows. The device its in the ubuntu usb device list:
http://oi64.tinypic.com/2h2kqhg.jpg
but, if i like to flash the device, nothings happened. The flasher wait for the device...
http://oi63.tinypic.com/zwi52s.jpg
So.....
how can I find a solution for flashing this board?
Its any not public device driver to this device?
How can I flash the SH AUD31.bin?
Becouse i think the Tegra files loaded up correctly via USB stick. Now i must to give a "fastboot -w" command to the device, and then can booting correctly. I tried with
"fastboot -i 0x0955 -w command too". not working.
I think I must flashing the bin file with a eeprom félasher. I have eprom flasher, but the flasher can't flash this eeprom. find any eeprom flasher under 600$ for this
"25C512A" eeprom.
So.....
How can i unbrick tis device?
Any solution?
Thanks for the reply
Kind REgads,
Rocco
Click to expand...
Click to collapse
Hi there...
Did you ever manage to solve your issue ?
just wondering ^^ (I have a device that has the same issue, and trying to recover it see if I can hack it later... )
Thanks.

Related

[Q] ROOT Smartpad ep750

Hi, does anybody have any idea on how to root this? On their website they have an updater tool which says to get it into recovery you must push power and volume button only there is no volume button.. only physical button is a power button and then there is a reset hole in the back of the tablet. http://www.easypix.eu/smartpad750_en.html
I would like to at least root it and then see if there are any developers for this model.
Thanks.
I found a question from someone who has broken their same model tablet which was rooted, so it is possible.
You can get the proper windows drivers and connect to it through ADB. Using this method you can push clockwork mod touch, and the touch interface should work fine. You might have to use ADB terminals for keypresses as it starts though, I'm not sure how you would boot into recovery without a rom. But once in a rom, you can always select the reboot into recovery option.
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
bump
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Kevinjs said:
do you have any guide for this, Im more just interesting in rooting it to start with. I think I figured out how to get it into some sort of recovery mode but windows wont let me install the recovery mode drivers so I cant do anything
Click to expand...
Click to collapse
Hi there. Do you mind sharing the info how to get it into some sort of recovery mode . And with the tool from that web site. Was it difficult to do?
ADB does not find Easypix Smartpad EP750
Kevinjs said:
I just rooted it with unlockroot.com , It works for any tablet with the rockchip 2906 (Rk29).
Click to expand...
Click to collapse
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
ProJerem said:
It seems impossible for me, I installed the driver, now in the Windows device-manager you can find a "Class for rockusb devices" and there a "RK29 Device" but adb seems not fo find it.
While I see the device in my Windows device manager I pushed the Root-button from the unlockroot.com - tool, but after it tried to check via ADB there comes a popup "not detected any device ..."
Checking it with Ubuntu-Linux with the lsusb - command, this tablet has NO NAME, I can find the VendorID and the ModelID but after that, there is NOTHING , all other USB-Devices do have a name after its IDs, and trying to check via Davlik Debugging Monitor (ddms) you have to chose the name of your device,
but it is impossible to me, because I cannot chose NOTHING to use NOTHING with ADB ... has anybody an idea, how it may work, or has anybody a working ROM on his Easypix Smartpad EP750 which has root or at least a name ?
Maybe anybody has a working udev - entry for Linux ... pls post it here !!!
Under Windows I am able to flash the device with its own flashing-tool (RKBatchTool) but since now I did not find any ROM which I can flash instead of the original ROM - the latest I downloaded from Easypix-WebSite = 750_20120621 with Android 4.04 but no root-access,
I tried to flash a CM9, but the RKBatchTool told, that was no possible ROM for that device .....
Click to expand...
Click to collapse
How did u manage to flash through windows? i have one of these tablets that was handed out with some ****ty program that has been installed by a medical company to give out to patients , with a load of information about certain medical conditions, a load of ****e basically, i want to flash the original rom in order to wipe this crap program from it to allow me to use it as a normal tab . I managed to install the driver but cannot get it into any form of recovery mode in order for the device to show in the flashing program . Any help appreciated
hi i was wondering if you could let us no if it worked for you as i have 3 of them with pattern key lock and its saying im putting in the wrong email address which is the correct 1 and i can find any information to help me remove them.

[Q] Installing USB Drivers for ADB in Recovery

It's been bugging me for a while that I can't use ADB while in recovery. It's a matter of getting the drivers installed correctly, I think, I just don't know exactly how to do it. When the phone is booted I can use ADB and MTP just fine. Odin sees my phone in download mode as well. The only problem is in recovery. I'm using TWRP 2.3.3.0, but I've had the problem on previous version of TWRP and CWM. I have the Samsung USB drivers installed, and when the phone is booted Device Manager (in Windows 7) says the drivers being used are from Samsung. However, when in recovery Device Manager shows SAMSUNG_Android_SCH-I535 with the yellow '!' and says no drivers are installed. I can try to choose the drivers to install manually, but if I point to the Samsung USB Drivers folder, Windows can't find the right drivers automatically and there are 25 subfolders with somewhat cryptic names, so I don't know which to choose.
Does anyone know how to get ADB working in recovery?
EDIT: Got it working. I don't know anything about how drivers work, but I dug around a little and it turns out the device shows different Hardware IDs when booted versus when in recovery. The drivers .inf has to contain one of the Hardware IDs given by the device so after finding the driver being used by Windows (by searching for the Class GUID given in the driver details when the phone was booted and searching through all the .infs in the Samsung drivers folder for the matching string) I just added a line with one of the Hardware IDs given in recovery so Windows would install the driver. I tested with adb devices, adb shell and adb pull default.prop and each worked fine.
For anyone interested the driver being used is in 25_escape. In the file ssudadb.inf just add the line
Code:
%CompositeAdbInterface% = ssud.Install, <Hardware ID>
under [Google.NTx86] and [Google.NTamd64], where <Hardware ID> is one of the Hardware IDs given by your phone when in recovery. In Windows, go to the Device Manger > right click your phone > Properties > Details tab > Hardware IDs in the drop down. Mine was
Code:
%CompositeAdbInterface% = ssud.Install, USB\VID_18D1&PID_D001
Then update the driver, browse for drivers, pick the 25_escape folder, and you're good to go. The driver will fail a security check because you've modified it, I ignored it.
I imagine this could cause a problem if some other device uses the same Hardware ID (e.g. if it's some sort of generic or default one that's given in recovery) but I'll cross the bridge if I come to it. There may be some safer way to force driver installation.
EDIT: After doing this you'll get a warning when you plug your phone while it's booted. It will say something to the effect of Hardware ID missing or not being able to identify the device plugged in. This isn't a problem though, ADB and MTP still work fine and the device is identified properly in Device Manager.

bootloader is wiped|

hello, i am in a bootloop with my oneplus 6. wiped everything.
since then i tried using the msmdownload tool, but it's not recognizing the phone.
in the device manager the phone is currently being recognized under "kedacom usb device" as android bootloader interface. I tried doing an update to the drive and installing a quallcom drive, but always get an error message "The folder you specified doesn't contain a compatible software driver for your device. if the folder contains a driver, make sure it is designed to work with your computer". i downloaded a few windows program to force installation with no success. tried signing the .inf file of quallcom driver - same errorwhen i try again. when i write in cmd 'fastboot oem unlock' - it says that the device is already unlocked. when i try the command 'fastboot twrp.img' or fastboot boot it also fails. i even downloaded tool-all-in-one - doesn't help. when im making an uninstall of the android bootloader interface, after connecting the phone again - it automatically installs this driver again, even though i marked in the settings not to do that. all i get is a bootloader screen, nothing else.
p.s. new here so sorry if the thread is in the wrong place or something.

delete don't work

Thread Closed Per OP Request
Don't work,
I give up
Thanks in advanced. All comments can help!
I have a tablet I can depure via USB and where I can root the tablet. But if I connect to the internet, the "registration and password" of university program enters and is saved (even after formatting it is stuck on this screen) blocking the tablet, I believe that after the internet loads, it installs this locking program ... What would be the name of this type of application? I'd like to know, how remove this app, to If connect in internet, we can block (and try install TWRP via internet with TWRP Management)...
C.Modica said:
Hello everyone !
I've been trying to resolve this issue for weeks. I have a tablet that I can't unlock (it's super hard, it's like Dark Souls of tablets). Well let's start.
He has a program that blocks asking for password and user (this a old from a university), where you request access via wireless or 2G/3G. without it you can't access it, so I believe I have to change his firmware instaled in, but I'm having a hard time to make it.
• Let's go to basic product information:
The chip is a RK3066 (same from TV BOX based on rockchip).
The model is YPY L1050 from POSITIVO (it's from Brazil).
- Software and Items
I have the drivers installed (correctly);
I have adb installed;
I have SD_Card;
I have acess from PC;
The tablet is unroot;
• Back to the items:
So, the good news is that I have the same tablet model, unlocked (with another type of ROM that I am unaware of). That works normally, without problems. Well, I saw a procedure that basically it is possible to extract this image from the good tablet, to the locked tablet. I did that, I ended up extracting a series of .img files from the unlocked tablet: boot, cache, kernel, system, etc... ok.
• Trying a extract from unlock same tablet:
I try transfer the copied files from "good unlock tablet" (extrated with AndroidTool), and put in (with the same tool) in the lock tablet... There is a problem, even before starting the operation, I have the error "Test Device Fail ", in the last is not possible to transfer files via USB (I can only do commands like" ResetDevice ", or export the images from the blocked tablet via AndroidTool... and yes I have the drivers instaled, commands like adb sideloader in the fastboot works).
• Trying a firmware found in internet:
Well, I tryed to download the firmware found on the internet corresponding to the device model, but unfortunately I have the same error as above. I download the .img firware original and using the RKBatchTool and have the same error (the operation don't start, give "Test Device Fail" in "Upgrade" and "Restore").
I believe that both operations do not accept transferring via USB.
PS: The tablet unlocked the command of "TestDevice" works fine.
• What I was thinking of doing:
1 - I think I need to take the all .img(s) files extracted from the unlocked device, put it in a single image (.img), put it in a SD_Card and in the "fastboot" take the option "update rkimage from external storage". But I don't know how to do this. (I try search for it);
2 - Somehow being able to do "apply update from external storage", maybe doing the same procedure above with an "update.img", but I also don't know how to do that (put all img. files together in the form of a one update.img).
3 - Have anothers options, like "apply update from ADB", the PC response this conection with tablet, (I can see the device with ''adb device'' cmds in sideload mode in PC). The problem is that I don't know how I'm going to send the .img file, if I send it inside a .zip (I even tried that, send all the .img files inside a .zip to see if it works. The tablet arrives to read the files but in the end the operation aborts). So my knowledge is lacking in this part.
4 - Another would be such a "ROM Dump." I'd like to do a "ROM dump" with an SD card, I even researched it on the internet but I didn't find this procedure to rockchip (only for Amlogic).
With SD Card:
There was a youtube that managed to unlock a tablet like that, but it was a previous model that I'd like to unlock (and different version of firmware, android etc). His method was to put a bootable sd_card, but he doesn't explain how he does it (he only gives the file done) and looking at the files internally, I just think they were converted to linux formats (system.tar.gz, userdata.tar.gz, some .sh .so files, and a bootenv.img, uImage etc) and with completely different names from .img... It is a pity that it is not for my Tablet model .
Well, that's it in the end, I need to change the firmware and I don't know how to do it.
PS: I tried other operations/methods as well, but I will not comment so that this post doesn't get big.
Thanks in advanced. All comments can help!
Click to expand...
Click to collapse
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Instead of trying to package the .img files into one file, you should try flashing each .img individually via fastboot using commands with the following structure:
fastboot flash <name of partition> <name of partition.img>
The following commands are examples.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash kernel kernel.img
You will need to use a separate command for each individual .img.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
C.Modica said:
Hi, thanks for the reply. Well I can make it via adb sideload? I can't use the command "adb reboot fastboot". Because this command "adb reboot fastboot" only turns off the tablet don't restarting into fastboot/download mode (just turns off). But If I manually enter on the bootloader, I can access the adb sideload option, where the adb install on computer can detects the device via the "adb devices command" with sideload.
Click to expand...
Click to collapse
It isn't going to work via adb unless the device is rooted and then it won't be via adb sideload, it would be done by using dd commands to dd the .img files directly to their partitions.
Sent from my SM-S767VL using Tapatalk
I just found a solution. It requires some tinkering, though.
I had to use a machine running windows 7, because that's the only OS that the drivers worked.
Download the firmware for the Ypy L1050F here: https://www.stockrom.net/2018/07/l1050.html
It comes with the drivers, the ROM, and a tool called RKBatchtool 1.8
You'll have to decompress everything, open RKBatchtool and choose the firmware that is in the ROM folder (Not the DEMO one).
Now comes the tricky part: You gotta undo the 3 screws aroud the tablet, then pry it open with your fingers(remember to remove microSD and SIM first, to avoid breaking stuff!). I recommend startind by the side with the usb, hdmi and power ports to get some leverage. The back cover should pop right off. Then you have to locate the NAND chip in it. Should be a Micron one with 48 pins. The small circle at one of the corners of the chip represents pin 1. Plug your usb cable to the tablet. With the tablet TURNED OFF, use a SIM removal tool or very fine tip metallic screwdriver to short pins 17 and 18 on the NAND chip and plug the power jack into the tablet. RKBatchtool should show that a device was connected. You can release the screwdriver now and just click the "Upgrade" button in RKBatchtool. Now this is very important: DO NOT UNPLUG your tablet until everything is done. It'll tell you when it's done uploading the firmware and checking it. Enjoy your new usable tablet!
I scoured the internet and found this procedure being used for TV Boxes with the same RK3066 SoC. AFAIK, nobody else managed to do it so far, so spread the word.
You are awesome. Broke the internet! I will follow your procedures to try to unlock it. Many thanks again xmas for you.
[edit] don't work

My OPPO A5s (MT6765) were Bricked

I have a phone which is Oppo A5s, where my cousin change the password and forgot it, so I tried to search how to format it, and after several days of searching I found SP Flash tool, Miracle Box and other Software like DrFone etch, but only SP FLASH TOOL has progressed, so I watch videos on youtube and download compatible ROM then I stuck on a problem (enabled-verified-boot opporeserve2).
So I found a youtube video that needed an SGPT file, but since there was nothing SGPT file in extracted OFP, I search again how to generate it, then Youtuber said that I just need to use the WWW MTK tool and do READBACK and Format it on Format Tab in SP FLASH TOOL, which is the cause of my problem now. So as of now my Phone doesn't open, so when I try to connect it via USB it says - Unknown USB Device (Device Descriptor Request Failed). hope there is someone who can help me with my problem, I will really really appreciate it. Thank you in Advance.
If USB debugging is enabled on your device and suitable correct ADB driver is installed on your PC, then your PC should recognize your Android device as an ADB device:
NOTE: Usually, the ADB entry will show under the heading "ADB Interface", or "Android Phone" (or similar), but sometimes it will show under the manufacturer name instead (e.g. "Samsung", "HTC", etc).
xXx yYy said:
If USB debugging is enabled on your device and suitable correct ADB driver is installed on your PC, then your PC should recognize your Android device as an ADB device:
NOTE: Usually, the ADB entry will show under the heading "ADB Interface", or "Android Phone" (or similar), but sometimes it will show under the manufacturer name instead (e.g. "Samsung", "HTC", etc).
Click to expand...
Click to collapse
But ADB Interface is not showing even I installed ADB driver or Universal ADB Drivers not showing at all. It's just saying "Unknown SB Device".

Categories

Resources