Hello Everyone, this is one of my first posts so go easy on me.
I used the method in this thread to flash JB onto my TF201, and now i cannot boot to recovery (get the android on his back/side with the red exclamation) and fastboot shows up as a device in device manager in windows, but when i run the "fastboot devices" command with the up to date SDK nothing is listed. ADB works, but for osme reason superuser was installed as a system process and will not uninstall, and will not issue any sort of root command to anything, including ADB. any ideas?
I boot my Acer Iconia Tab A200 into fastboot mode (robot lying down and RED exclamation mark over it). I plug it into my Windows 7 (64bit) desktop computer with SDK installed, and from the directory with fastboot.exe I type FASTBOOT DEVICES but the device is not being seen, it just goes back to the prompt, like the command executed but didn't do anything. I assume this is because the drivers aren't installed. But I don't know how to install the "adb drivers". How is this done?
Go to Acer support page, you'll get the drivers there.
This device will not fully boot. It gets stuck at an "encryption unsuccessful" message. I'm trying to flash a rom image from my desktop computer using fastboot, but when my tablet is in fastboot mode, my desktop computer won't recognize it. ie adb devices command doesn't show that there is any device connected, and I think it's because the drivers aren't installed. I think those Acer drivers only work if the tablet can be fully booted.
Installed the Google USB Drivers from the SDK Manager already. Don't know what's wrong.
Alright I figured out how to get fastboot to interface with my Android tablet. The problem was that I wasn't getting the tablet into fastboot mode to recieve commands.
But now it's working. However, I'm trying to unlock the bootloader and it gives me an errors that says:
SetUnlockedMode: Error occured while unlock the device ...
Fastboot: Failed to set unlock mode
I have to unlock the bootloader before I flash an image to the tablet, right ?
Yep, surely.
Hello everyone,
I opened this thread becasue of forum rules.
So I have got a Chinese tablet that internal name is C-712 and Usb Vendor is 1F3A:1010.
I tried to install a custom rom and my device isn't open now I have got only a white screen.
At first I can see with adb devices as
adb devices
xxxxx recovery
and I tried the
adb reboot-bootloader command
and rebooted...
After reboot my device don't seem in the device manager as "Android composite ADB Interface" but showing as "USB Developer"
So I tried to search alternative driver of this device in my computer and I found another one now I can see as "Android Bootloader Interface" in Windows 7's device manager.
But this device don't recogize by adb devices nor fastboot devices.
Is there any tool or way to reinstall my original img file into this device.
Best regards
Tr Escape
Ok. I solved my self...
So you need PHOENIXCARD V3.09 software and a sdcard.
And follow the instructions for formating of sdcard as production.
You may find that software in google.
Thanks for reading.
tr_escape said:
Hello everyone,
I opened this thread becasue of forum rules.
So I have got a Chinese tablet that internal name is C-712 and Usb Vendor is 1F3A:1010.
I tried to install a custom rom and my device isn't open now I have got only a white screen.
At first I can see with adb devices as
adb devices
xxxxx recovery
and I tried the
adb reboot-bootloader command
and rebooted...
After reboot my device don't seem in the device manager as "Android composite ADB Interface" but showing as "USB Developer"
So I tried to search alternative driver of this device in my computer and I found another one now I can see as "Android Bootloader Interface" in Windows 7's device manager.
But this device don't recogize by adb devices nor fastboot devices.
Is there any tool or way to reinstall my original img file into this device.
Best regards
Tr Escape
Click to expand...
Click to collapse
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Have you tried with another cable or diffrent USB port?
I did but same result. Any other advice I can follow?
TSKXDA said:
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
MobyDuhFreak said:
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
Click to expand...
Click to collapse
If I try to fastboot into recovery I still get the same error.
TSKXDA said:
If I try to fastboot into recovery I still get the same error.
Click to expand...
Click to collapse
Is your phone a redmi 5(codename Rosy) or a redmi 5 plus or a redmi note 5 in India (codename Vince)?