Bricked/Stuck in fastboot - A3000 Android Development

I managed to brick my lenovo a3000 tablet! I destoryed the os and the recovery partition accidently, all thats left working is fastboot but I can't find the fastboot drivers for PC, ive tried loads of different adb drivers but none detect the tab in fastboot mode.
Does anyone know the correct usb driver to use? I'm running windows 10 x64

Related

soft bricked m7, computer wont recognize phone

I have adb fastboot on but I Cant get anything working. have tried reinstalling drivers but still nothing. NEED HELP
Autiger11 said:
I have adb fastboot on but I Cant get anything working. have tried reinstalling drivers but still nothing. NEED HELP
Click to expand...
Click to collapse
What is your bootloader (hboot) version?
What is your computer OS version?
What are your drivers version?
What adb version are you using?
Make sure you have everything up to date and you should be able to have fastboot connectivity when booted in bootloader / fastboot usb mode. If you have hboot 1.44, you will need Windows 7, Linux or MacOS to use fastboot since its not working correctly with Windows 8/10 (not a problem with newer hboot versions).
Also make sure you are using the original usb cable and not only a usb power cable (without data connectivity). Only use usb 2.0 ports directly on your computer (no external hub). Make sure HTC Sync is NOT installed on your computer.

No devices in fastboot

So i am using the latest stable global rom and have updated windows 10 on both my computers and both won't recognize the phone as a device in fastboot. Had already used it in the past. The phone has usb debbuging activated and the phone recognises the device when not in fastboot.
Any ideas how to fix this? Or anyway to install TWRP without fastboot?
are you sure you have properly installed fastboot driver ?
Happened to me also... What I did was I used old fastboot drivers... The new 2016 drivers won't recognise in fastboot...
Connect your phone in fastboot...
In device manager manually update it to old drivers
can you upload that Old driver?

CC9 in Fastboot mode not recognized in any computer

Hi,
I have a CC9 with Chinese version, and I want to flash the global ROM.
I've tried to unlock the bootloader with no success.
I have adb support on many computers (I've tried windows, Mac and Linux)
but in fastboot mode, no computer recognize the device, like the USB in disconnected in this mode.
Code:
C:\Users\User>adb devices
List of devices attached
f102f099 device
C:\Users\User>adb reboot bootloader
C:\Users\User>fastboot devices
C:\Users\User>
I've tried any usb driver for windows, with no success.
Does anyone have an idea? what could be problem?
same here , its is frustrating :\
ekrako said:
Hi,
I have a CC9 with Chinese version, and I want to flash the global ROM.
I've tried to unlock the bootloader with no success.
I have adb support on many computers (I've tried windows, Mac and Linux)
but in fastboot mode, no computer recognize the device, like the USB in disconnected in this mode.
Code:
C:\Users\User>adb devices
List of devices attached
f102f099 device
C:\Users\User>adb reboot bootloader
C:\Users\User>fastboot devices
C:\Users\User>
I've tried any usb driver for windows, with no success.
Does anyone have an idea? what could be problem?
Click to expand...
Click to collapse
I had this issue when trying to unlock my bootloader. Solved by using a USB 2.0 Hub. It has something to do with Xiaomi driver compatibility in Windows 10.

Fastboot not detecting

Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Quaczi said:
Hi,
I have a problem with my device, when I connect it to pc adb can see it easily but when i type "adb reboot-bootloader" it boots to fastboot but my pc doesnt see the device anymore and there is no device detected when I use "fastboot devices" command.
It used to work before windows update but now it does what I said.
Is it because of the drivers? if so can anyone send me a link to proper windows 10 drivers for china k20 pro.
I'm not rooted and no twrp. Just the stock firmware (10.3.16).
Click to expand...
Click to collapse
I had this problem in my Nokia 7 Plus, then i used and installed "minimal adb and fastboot" file which detected my phone in fastboot. It installs in program file with a folder named "minimal adb and fastboot"
Sent from my Redmi K20 Pro using Tapatalk
You need to enable "USB debugging" in the developper options
ImEraaz said:
You need to enable "USB debugging" in the developper options
Click to expand...
Click to collapse
It is enabled.
And ill try with the minimal adb option
Update:
Still not working
I have same problem, there is no way to recognize my 9t pro in fastboot mode... i cant do anything
First it should be intel pc
Try to install Xiaomi drivers and adb
Boot to recovery and fastboot while connecting to usb to install the drivers
Then check again
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
simpn said:
Did anyone solve this? I'm experiencing the same issue. ADB works fine, but no device is listed at all (device manager in win7 or syslog in linux) when connecting the phone in fastboot mode. It's like it wasn't physically connected at all.
Click to expand...
Click to collapse
Try changing ports / connect to another pc
Install proper drivers .
Is your bl unlocked now ?
Got it to work under win7 with great help from this post.
What I did was:
Update to the latest miui version (to MIUI Global 11.0.3, as prompted in system settings, I hadn't bothered to update because I just want to throw miui out)
Disable OEM unlock
Reboot
Enable OEM unlock again
Reboot into fastboot
Then the phone showed up as an unknown device in Device Manager
Right clicked the device and updated the driver, chose to search for drivers in the miflash_unlock-en-3.5.1108.44\driver\xp-win7-win8 folder
The device now lists as an Android Bootloader Interface device
And now:
$ fastboot devices
e150445 fastboot
MiFlash unlock detects the phone, and I could proceed with unlocking. Still have to wait though. Tried the older-version-trick as suggested here, but that just told me to update to the latest version. Guess I'll have to wait a week then...
Hope this helps someone. This is the most tedious unlocking procedure I've encountered so far...

Can't unlock bootloader, due to can't connect to fastboot

Hi guys,
I want to unlock the bootloader to flash a new recovery image and to flash lineageos on my device.
But connection to fastboot will not be established whatever approach I follow.
Stock Android is updated to the last version through update function.
I followed instruction on lineageos.org and on Sony side for my device to unlock bootloader,
I installed XZ2 device driver,
I used several versions of adb and fastboot (old and new versions)#
I tried Windows 7 prof. 32 bit, 64 bit, Windows 10 64 bit Prof.
I tried USB 2 and USB 3.0 ports
Don't know anymore what I should do to get things done.
If my XZ2 is running in normal Android mode, I'm able to access the internal memory via file explorer as well as
adb devices and
adb reboot bootloader is working.
Result: LED is almost not on, maybe one can detect a little bit of blue color and screen ist black.
Then
fastboot devices or
fastboot print-pit
will not give any answer. :-(
Does anyone have a good idea to proceed before I just give up?
Many thanks in advance
Illo
strange.
had the same issues with Windows 10. had to disable Win10 driver signature enforcement to install the correct Fastboot drivers for the Xz2.
So if it doesn't work in Windows 7 either you seem to have a different problem.
A. Try using different cable
B. Install 15sec adb installer
C. Reinstall the driver again after "adb reboot bootloader"
i had the same issue and tried various method. The thing that did for me was A. Weird, since the working cable was a cheap bundle one..

Categories

Resources