Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
root
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
Click to expand...
Click to collapse
Hey can you please guide me how did you root this device? I am having the same and I need to root it. Thanks.
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
... [CUT FOR SPACE] ...
Thanks a lot,
badday
Click to expand...
Click to collapse
I have the exact problem badday has, but with the Ainol Novo7 Paladin. Any help will be appreciated in my corner as well!
Unable to root Zync z930
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If anyone of you manages to crack it please let me know, thanks!
---------- Post added at 08:27 PM ---------- Previous post was at 08:22 PM ----------
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If you managed to crack it please let me know, thanks!
To clarify things: I did not root my device so far.
Some additional information I found out:
Try to reboot in adb via "reboot-bootloader" results in normal startup. Furthermore, booting to fastboot mode (with vol-up-button down) with Micro-SD-Card inserted makes the device not to appear any more in lsusb.
Anyway, that made me having even less clues than more :crying:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
abdulmomin said:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
Click to expand...
Click to collapse
Anyone found any method to root z930?
I'm not sure for linux but I think you will have to download drivers ,,,,,,,I had to do this for my computer (running win 7) to read my phone in fast boot
I downloaded an app called driver tools and that fixed it ....hope this helps
Ps : It maybe that your running 64 bit Os
@abdulmomin, jaydeepkhalpada: Rooting thread can be found here: http://forum.xda-developers.com/showthread.php?t=2028740
@fredworxz: Yes, I use a 64bit OS. However, for GNU/Linux drivers should not be needed as adb runs out of the box (please correct me if I am wrong).
Resolved! - See my post! http://forum.xda-developers.com/showthread.php?t=2045173
I've not only installed JB in Z930 but also successfully ADB'd it to root it
Here:
http://forum.xda-developers.com/showthread.php?t=2045173
Actually I cannot install the driver which might be some problem as I use 64bit OS and have no 32bit available. Anyhow, according to the name scheme, there should also be a 64bit version included.
Apart from that I have also problems with this Chinese software, does it need adb drivers to be installed? Actually when I boot in this mode with vol-up-button, there appears absolutely nothing in the device manager.
Would be great if you could help me out as I need this tablet for some sort of NGO project.
Greetings from Delhi,
badday
This is not fastboot mode
as your trying to unlock fastboot ,but this is not fastboot mode
this is for flashing firmware through G+massprotection tool..
There is no fastboot mode in Z930..
but you can goto recovery menu by pressing
1st press & release Power button then press and hold vol+ button
How your razr hd (in AP Fastboot Mode) look in Windows 7 x64 device manager? I need the screenshot with device ID. Maybe wrong driver were installed cause device dont show correct usb device id (for example in BP Tools, ADB interface not install driver, before i edit the INF file of drivers). Mine as default installed it as Mot Single ADB Interface in the Fastboot Mode (!!!) looks like there is the problem why it not flashed correctly. Help please!
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.
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.
Good evening I have read all the messages of the forum, and I have tried the various solutions to solve the problem.
It tells me "Invalid boot image!" and does nothing else even when restarting. Connecting it to the PC I can see the code of the tablet with ADB and command fastbot devices.
The tablet is recognized in peripheral management as Asus Android Device / Asus Bootloader Interface
I downloaded this firmware ... ME302KL-OPEN_epad-eng-900M-hdpi-H00_0.16.F_0521-10.10.0.52.4.8-20130731-1422-Rawdata.rar but it doesn't work.
I ran the flashall.cmd file as administrator (Right click on the file and choose: run it as administrator)., The command "debrick-flashall.cmd", and also the commands flashall-ME302KL-1GMEM.cmd or if you also have the brick debrick-flashall-ME302KL-1GMEM.cmd without the tablet exiting FASTBOOT mode. Is it possible that it doesn't work because my operating system is WIN 10 ?? ... is there any firmware that works with windows 10 or some other indication to solve the problem.
Thank you