Acer Iconia tab A510 Booting problem - Acer Iconia A700 and A510

Hi everyone!
Before everything else congratulations for this amazing big forum.
Well i'm new around here and i hope i am in the right place posting this question.
I have an Acer IconiaTab A510 and after turn it on the tab displays :
Booting failed
Bootloader vJB-d0ca683: Starting Fastboot USB download protocol
I had dig around the forum about a solution and still i could not enter in recovery mode.
I am highly inclined to follow the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1866378&nocache=1
I have already followed some instructions but still can not unlock the bootloader properly.
Using minimal adb and fastboot and performing fastboot device command it shows the device, however if use the adb devices command it shows nothing in liested devices.
Its confusing and since the the tablet cant boot i can not put it in usb debug mode.
I have already installed universal adb drivers for the acer a510.
When i plug it using usb cable the computer detects the acer in fastboot interface and also in apx driver. But if i use the adb devices command nothing is listed. Any thoughts?
Said all of this i still dont know how i can force a recovery into the tablet and after that installing the jelly bean os from the acer site.
Is the tablet beyond repair?
Anyone can help?
Thanks in advance.

Related

Stuck in fastboot - device not recognized

I can't seem to get the fastboot usb drivers to install....i tried:
a) downloaded the asus android usb drivers but can't install manually because they won't do it on x64?!
b) installed asus pc sync (should install drivers also right?)
now i'm in fastboot usb download and when i connect the cable, it says USB device not recognized.
what can be done?
installed the SDK and now i see the device recognized in ADB, but i can't get it to be recognized in fastboot mode ???!!!!!! same error about unrecognized device...
// EDIT: WELL ****ING HELL, it was the USB port!!! I tried 3 of them (front panel) and same result
Switched to a backpanel port and it flashed TWRP straight away....
**** this, pls close thread.

Usb drivers for your android phone

USB Drivers are let your PC communicate with your device.
If you are executing some ADB Commands, you will need USB Drivers installed which will let the ADB server on your PC communicate with the ADB client on your device. If there are no USB Drivers installed on your PC, you will not be able to perform activities on your device via the PC.
First of All I would recommend you to install Universal ADB Driver Installer.The Universal ADB Driver installer detects your phone and installs the ADB drivers for it.This tool developed by drsmart is your solution to the “device not found” error you might get on executing ADB commands.
Universal ADB Driver Installer Download Link - http://adbdriver.com/downloads/
USB DRIVERS
1.SAMSUNG:
--- http://www.samsung.com/us/support/downloads
2.LG
---http://www.lg.com/us/support/mobile-support
3.HTC
---https://support.htc.com/en
4.SONY
---http://developer.sonymobile.com/downloads/drivers/
5.ASUS
---http://support.asus.com/download/options.aspx?SLanguage=en&type=1
6.MOTOROLA
---http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
MORE DEVICES WILL BE UPDATED
Thanks for the info. I tried the univ adb driver installer but it showed I already had the right driver installed. Windows explorer can see my phone but other apps like HTC Sync or myphoneexplorer can't. This only happened after I rooted & installed a new rom. Maybe the rom is faulty...
I want Google nexus driver
any one can help me ?
mt6572 driver
Please add driver for mt6572 device
thx. very usefull!
thanks for the updated links.
Gole Maryam said:
I want Google nexus driver
any one can help me ?
Click to expand...
Click to collapse
an universal driver for all Nexus Devices (Phones and Tablets) can be found here:
http://forum.xda-developers.com/showthread.php?t=2513339
No access to USB debug
I give up and need some professional help...Ya both kinds.
Here we go, I have the Galaxy 3 d2att I747
Rooted
I was running CM 10.2 with latest nightly, I think 20131208 and decided to update to CM11 via my Cyanogenmod updater but before I did I had read somewhere I should change from CWM recovery to TWRP so I downloaded Goomanager and updated to the TWRP version for my phone then went for the KitKat update and thats when the trouble began.
I am now stuck in a boot loop even if I try to boot into TWRP all I get is the TWRP boot logo then straight into boot loop again. I am almost positive I did a factory wipe as well as cache/dalvik.
Not being able to use TWRP to get into recovery I thought I would just use Odin but I can't get any of my laptops to recognize the phones USB, I just get the windows usb driver error and have tried to install the drivers manually via device manager using my samsung 7 chronos with windows 8.1 and my acer with windows 7. I updated drivers using Samsung Kies and from the website, no luck.
I also ventured into an area that I have no expertise in but I guess thats how we learn so I downloaded the Android SDK thinking I could use it to download and install the google USB drivers that way, but I can't get out of boot loop to make sure USB debugging is checked. The only thing I can access is the stock download mode which would be great if I could use the USB connection.
What am I missing? Any suggestions?
USB Not Recognized Error
I noticed that my phone suddenly stopped being recognized on both my Windows 7 and Win8 laptops. I have been trying to fix it with the drivers but to no avail. However, I plugged my phone in with a different USB cord and voila it was recognized and working. Maybe this could possibly be a simple fix.
My computer stopped recognizing my Skyrocket
Hi Everyone,
I also am having trouble with my win 7 computer recognizing my Skyrocket suddenly. I have been using several KitKat roms and they have been working just fine, except for some reported bugs that the CM devs are working on. I even was able to connect to the computer and explore both my internal and external drives. Then suddenly that stopped and the computer gave me a need to get drivers warning. I've tried to download drivers from Samsung and the computer says they are already installed. I also tried the universal driver download and got the same message. Any help would be appreciated. Like the others on this forum, I wouldn't be able to odin if I got in trouble.
Thanks for your concideration,
drewfs7270
I switched to a different rom and now it's working again !
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Thanks.. :good: usefull
Also, any mobile manufacturer website has guides or direct downloads for drivers. Otherwise uni drivers suffice.....
Sent from my Nexus 5 using xda app-developers app
mtk preloader driver unable to install/unplugged appears
mt65xx unplugged when I try installing my device, I tried uninstalling all preloader vcom drivers in my laptop then restart and when I try to connect my device mtk mt65xx preloader just pops up in device manager then suddenly disappears and unknown device shows instead. I also tried manually update driver for unknown device then select the folder where my mtk driver is saved still unsuccessful? I've also searched and tried many other ways out there still no luck. Can anybody give me a solution? By the way i'm using windows 7 x64.
Delted
Edit: Deleted
soft brick
I face bad experienced, the tablet can not boot ( after install TWRP ) but enable to enter the fastboot mode and can be detected by the computer as android adb interface but adb can't communicated with the tablet. (list of devices atached)
I do have a backup file ( I make it before soft brick, I make backup using dd command, because I don't have cwm/twrp recovery ).... but how to flash it ? Tablet chipset is wonder media 8980 OS android 4.2.2
I can not flash it by adb/fastboot.
Maybe someone here can give me a little guide for how to....
I really appreciate for your kindness
Hey, I made an expirience, which might help other users as well.
I have a Sony device (Z1C) and use Windows 10, maybe this will help for other brands and for other Windows 10 users.
I installed drivers for my device and was able to use adb. When I put the phone into fastboot mode, it was not recognized anymore. I found out, Sony has a seperate (updated, maybe?) driver for fastboot mode. When I tried to install this, the driver was not signed and Windows refused to install it. However, you can enter the UEFI (successor of BIOS) and enable installation of unsigned drivers (at own risk). Then I was able to install the fastboot driver and controll my phone in fastboot mode as well as in adb mode.
In conclusion: You might think you installed drivers, because you did, but maybe you did not.
Even on LineageOS page, many people fail to mention that, you DON'T and SHOULDN'T install any generic or universal ADB driver if you have Samsung device. As you can just install Samsung USB Drivers officially from Samsung site. Samsung USB Drivers already contain ABD interface driver just fine so Universal ADB driver is redundant for Samsung phones.

a500 USB DRIVER VANISHES

I need a little help my device is stuck in apx mode (blank screen with power led on) i have uid (cpuid) and sbk i have read a lot fom this forum and have all the tool to root, flash, load.. But my main problem is that when i reset my acer a500 and the usb is attached the windows 7 recognizes the driver and (sound pops up) and the driver (acer picasso usb boot recovery driver) is there but no tool e.g apxtool or fastflash or ics rooting nothing works or regocznies the device coz when i press any option or press the key to continue the drive drops and vanishes from the window usb list in device manager and i have to manually reset acer again to get the driver back but still no use as command prompt tells me that no device is attached or found. Please help as this acer is my wifes gift to me and im trying hard to get it back its totally dead

[Q] Recovery Help

Ok here is my problem and I will try including all the relevant information that I am aware of. I can't see my TF300T when I enable fastboot mode on the tablet.
1. I turned on usb debugging in tf300t settings
1. I unlocked the tf300t using tool from ASUS
2. I installed the android sdk kit
3. turned off tablet
4. Plugged tablet into usb
5. Held power off and volume down ( boots up with 3 icons. RCK Android Wipe ) pc comes up with failed usb device. I go into device manager and
under usb controllers it shows unknown device. I click update driver select the naked driver winsub and it says it is not compatible. I tried deleting device and rebooting etc but no matter what I do or what driver I use I can't get the computer to recognize the tf300t in fastboot mode. It will work fine when it is not in fastboot mode I can transfer files all day long. but no matter what I do I can't get computer to recognize the device in fastboot mode.
Computer.
asus H87-pro motherboard
8gb ram
Intel I5 Haswell
OS
Windows 7 Home Premium Service pack 1
I am really befuddled and could use a hand.
Moose66 said:
Ok here is my problem and I will try including all the relevant information that I am aware of. I can't see my TF300T when I enable fastboot mode on the tablet.
1. I turned on usb debugging in tf300t settings
1. I unlocked the tf300t using tool from ASUS
2. I installed the android sdk kit
3. turned off tablet
4. Plugged tablet into usb
5. Held power off and volume down ( boots up with 3 icons. RCK Android Wipe ) pc comes up with failed usb device. I go into device manager and
under usb controllers it shows unknown device. I click update driver select the naked driver winsub and it says it is not compatible. I tried deleting device and rebooting etc but no matter what I do or what driver I use I can't get the computer to recognize the tf300t in fastboot mode. It will work fine when it is not in fastboot mode I can transfer files all day long. but no matter what I do I can't get computer to recognize the device in fastboot mode.
Computer.
asus H87-pro motherboard
8gb ram
Intel I5 Haswell
OS
Windows 7 Home Premium Service pack 1
I am really befuddled and could use a hand.
Click to expand...
Click to collapse
Try using this guide:
http://forum.xda-developers.com/showthread.php?t=2139767
Thanks
Just a quick update. I used a different computer that I had never plugged the tf300t in and before I plugged it in, booted it into fastboot, It showed up as a fastboot device and installed the naked driver. So that problem is solved.
(solved)

"Unkown device" on bootloader mode for both J4+ and J4 core

I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
anonimazu said:
I turned USB debugging and OEM on, installed ADB drivers on my computer and plugged my J4 core (J410F). The "adb devices" command shows that my device is recognized by ADB, and I can reach my files problemless. But when I reboot into bootloader (adb reboot-bootloader) My device appears to be "unknown device". It's literally same problem in this thread: https://forum.xda-developers.com/showthread.php?t=2182437
To summarize: Adb recognized my device, can command my device, PC also recognized my device, can explore the files, but fastboot and Odin can't.
I also tried it with J4+, same problem occured. Tried to use another computer and swapped from windows 10 to windows 7, same problem occured. Dealing with this problem for 3 days, I'm about to give up.
My both devices are Turkey versions. Could that be the problem? , is something is broken on Turkish kernels?
I want to be able to use bootloader so I can root my device or be able to recover it when neccessary. Since some other users had same problem, it might be an universal problem, and since both devices are Turkish variations, it might be the problem of Samsung Developers, so primarily to the Samsung developers, after all developers, I'm asking for your help.
Click to expand...
Click to collapse
Not sure what you expected?
ADB requires the adb binary to be run at boot via the kernel ramdisk.
Neither FASTBOOT(which isn't supported on Samsung devices) nor ODIN(download mode) run the kernel.
In short ADB does not function in download mode.

Categories

Resources