Here is what I stand.
I have soft bricked my TF201 and I am trying to restore it using ADB per the recovery thread.
I am stuck in CWM recovery boot loop.
When I entered bootloop USB Debugging was not enabled and I dont have a computer that had/has the TF201 drivers previously installed.
Computer system is Windows Vista.
When the USB plugs into the computer it is recognized as "Transformer".
I have downloaded the drivers from the Asus site, from ADB repositories, and from other sites proportedly hosting drivers that work. None of those drivers have worked when attempting to manually install them (Device Manager > Update Driver Software).
How can I install drivers to get ADB to recognize my device if I cannot enable USB Debugging?
First i would install the recovery using fastboot again. Download drivers (link) and install it, download new cwm touch recovery (link), Restart your prime by holding the volume down button, wait, then press down to switch to the usb symbol, then press volume up. Now you are in fastboot mode. Enter the following command at the terminal or command prompt window : fastboot -i 0x0b05 flash recovery (path to cwm recovery img)
Thanks, Ive got USB working and was able to flash to CWM Touch Recovery.
Now when I try to push (adb push update.zip /sdcard/) I keep getting: Protocol Failure
This happens every 3rd or 4th time I try to push. The rest of the time I get a daemon failure.
Any suggestions on how to push a ROM so I can install it? (I dont have one on the internal SDCARD any longer)
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.
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"
Hi!
I'm still on my way ro root my Samsung Tab SM-T725, after upgrading to Android 11. Before Android 9 was on the device, succesfully rooted via Magisk. Updating and keeping the root status didn't work properly, the flashing process in Odin failed. Therfefore I had to flash the latest stock recovery, successfully. So now I have Android 11 on my device but no root. The bootloader is open and USB debugging enabled.
I tried the method described here. But the flashing in Odin failed again. So now I try to follow the instructions on the Magisk website. If I get everything right a processed recovery.img has to be flashed via ADB/Fastboot. That's new to me and I have questions.
- Is fastboot and download/recovery mode the same? Booting to the recovery and following "reboot to bootloader" leads to the turquois "Downloading" window. The same occurs when prompting "ADB reboot fastboot" e. g. Again the mentioned Downloading window shows up, nothing (special) with fastboot. Is that correct?
- Will therefore all fastboot commands not work? And only ADB is possible on my tablet? Is that common for Samsung devices?
- Can the flashing of the patched recovery.img (for Magisk) be done with ADB as well? Instructions always mention fastboot.
- My device doesn't show up in ADB when being in recovery mode. In normal mode it is listed when entering "ADB devices". Trying again in recovery mode the list stays empty - and all other commands have no effect. Current Samsung and Google USB drivers are installed. How could that be solved? Without ADB (perhaps fastbood) running in download mode I shouldn't be able to flash (and root the device) as planned.
I hope I described everything properly. I'm not that Android expert - but successfully managed to root a couple of devices over the years.
Samsung devices dont know of Fastboot mode. But you can run them in either Recovery or Odin / Download mode or Normal mode.
Running Samsung devices in Download mode you can flash ROM or update system in the Android device. When the Samsung device has entered Download mode, the device will boot from external sources. You can also make the stock ROM replaced in Download mode.
ADB mode is the Normal mode.
In Recovery mode ADB - with some exceptions - isn't working
Because your device is a Samsung one the Google USB drivers are senseless. Remove them to avoid conflicts.
Thanks for the quick and helpful response!
That makes clear why the tablet didn't show up in ADB. And that all rooting efforts for Samsung devices via that way should be obsolete. Strange enough that Magisk doesn't mention this on their instruction site.
So I'll have to try on with flashing a patched AP via Odin - and hope for a solution for my fail-problem.
Hi! I would like to mod my AC2003 upgraded to oxygenos 12.1 (android 12) version AC2003_11_F.13
Could you please tell me the steps to proceed? I can't find a guide that answers all my questions ... Do I need to unlock the bootloader first? Then the recovery and the rom? I would be oriented towards the pixel experience, can it be a good choice? Does it support 2 sims? How to do with the root for the bank's applications? Many questions, and nowhere to start ... Thanks in advance
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Be aware that you will miss some camera features with any custom rom... Full camera features are only available with the stock rom..
Thats why I moved back to stock rom and debloated all unuseable stuff...
But a custom rom offers many other opportunities that the stock rom doesn't have...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wan't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat, it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
Wow! You wrote the bible for the beginner ... I don't know how to thank you for your patience, now I have a great starting point
I've a problem, fastboot can't see my device... I've installed the oneplus drivers, but windows continues to use Microsoft's drivers. I tried to update the drivers from the device manager indicating as drivers those installed in the Oneplus folder, but windows keeps telling me not to find drivers compatible with an x64 system in that folder. I also tried to disable the digital signature check, without success. This is on both windows 11 and windows 10 PCs. I've also enabled debug usb...
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
dabyd64 said:
There's no problem using Windows drivers.
Isn't the phone recognized as fastboot device?
Attach device manager screenshot.
Click to expand...
Click to collapse
It seems you're not in fastboot Mode?
Do you see this screen?
dabyd64 said:
It seems you're not in fastboot Mode?
Do you see this screen?
Click to expand...
Click to collapse
The cable was the problem...Now i've tried with it's original cable and yes, i can see it! Thank you so much...
dabyd64 said:
Copy all important phone data, it will be wiped!
- Download adb platform tools here
- Download adb drivers here
- Enable developer settings -> Enable OEM unlock.
- Reboot into Fastbot mode: Turn off the phone, hold down vol+ and vol-, then power on the phone.
- Connect the phone to the computer, run "fastboot devices". If not recognized, ensure driver is installed in the device manager, install from downloaded adb drivers.
- Run "fastboot oem unlock", accept in the phone prompt, the phone will be wiped!
- Boot again in fastboot, flash the recovery: "fastboot flash recovery recovery_file".
- Unplug the USB, I found the recovery to not work properly if the usb was already plugged in before booting.
- Boot into recovery mode: Hold Vol+ and turn on the phone.
- Go to Update... Install from ADB, connect the USB.
- In the computer, run "adb sideload rom_file"
- I'd recommend issuing a factory reset after this, just in case.
- NEVER run "fastboot oem lock" with modded system, it'll brick your phone! (Can be fixed, but just don't do it)
- Enjoy
Ex. for Pixel rom:
- Recovery file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.img
- ROM file: PixelExperience_avicii-12.1-20220718-0624-OFFICIAL.zip
I wasn't happy with custom roms. Too many bugs. So I also post how to return to factory:
- Download fastboot ROM from here, unzip file.
- Boot the phone into fastboot mode, connect the USB, run "flash-all.bat", it'll take a while, it'll reboot afterwards
- You're now with stock system. You can upgrade to OOS11/12 using the zips from here, also check F.13, copying them to the phone, going to the updater and selecting "Local update".
- Better do OOS10->OOS11->OOS12, just in case! I'd stay with OOS 11.1.11.11, OOS12 is a battery drainer!
- Ensure to make a factory reset when done with updating.
- Now you're stock, you can also relock the bootloader by booting into fastboot and running "fastboot oem lock".
Click to expand...
Click to collapse
After flash recovery, when i go to the recovery mode, i see this mex:
"The current image (boot/recovery) have been destroted and can not boot. Please flash the correct image or contact customer service to fix"
Fortunately i have solved with msm....
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
gorro8 said:
It's a known thing that you can flash on any custom ROM only if you're on oxygenOS 10 or 11 version. Respectively, if you are on android 12, then you first need to flash with unbrick tool (msmtool) anroid 10 (EU/Global/India) or android 11 (India).
Click to expand...
Click to collapse
Hi,
I am on OS12 stock currently.
At which stage of the guide posted above I need to use the unbrick tool ?
Many thanks
Hi bro.
If you want to flash any custom ROM, then you need to go to unbrick tools thread, download drivers and MSM tool firmware and step by step flash it.
After that flash custom rom you need also with it instruction in the thread.