Database Info

[Q] TWRP Stuck in Recovery Bootloop

Hey guys, got myself in bit of a bind. I just recently rooted using the 1 click tool and also installed CWM with it. Later, I tried to install TWRP through goomanager on top of that. It rebooted to recovery, and the recovery seems to not have installed properly. It just stays stuck at the TEAMWIN screen and flashes. Even after powering it off and back on, it goes straight to the teamwin screen. The only way for it to boot properly is to voldown+power and then let it cold boot.
So, I tried installing TWRP 2.5.0.0 over that, but instead of rebooting properly (after I follow the instructions from the twrp website) it reboots straight into the recovery still.
I tried using the 1 click tool to try to reinstall CWM, but now it no longer works. The command prompt just disappears after the driver installation part. After that, I tried easy flasher. Wasn't able to install Rogue or TWRP. They state that they have been installed correctly, but when I boot up the tablet it goes straight to the teamwin screen and stays stuck there.
Anyone else have any ideas? I honestly feel like I've tried everything. I haven't tried wiping it yet, but only because I don't feel safe wiping it without a recovery installed.

Using EasyFlasher, did you see any text on the screen? If not, it did not install.
Also, do you know how to use ADB?
If so, run try this:
Plug tablet to PC via USB
After the device was detected, Settings - Developer Options - Debugging (tick the box).
It should install new hardware and show 2 devices, an MTP and an ADB device.
Update the driver in the Device Manager on the windows machine to the Naked Drivers
Once that is updated, I downloaded ADB from the Android SDK. You really only need three files, available here: https://www.dropbox.com/s/h61zwmzaynouc1k/adb.zip
Unzip these files to a folder called c:\adb
Open a command prompt and type the following:
Code:
c:
cd c:\adb
adb devices
It should show a device connected. It may error out when restarting the daemon, but keep trying and see if it can find your tablet.
If you cannot get the ADB driver installed or updated, my guess is that you have a bad USB cable. Yes, it IS possible to have a bad cable for data transfer that STILL charges your tablet. I have even had that happen to me.
If you got this far, then here is what to do next:
Download your favorite recovery. I strongly recommend TWRP. The latest official release is here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob
Save this at c:\adb\TWRP.blob. You can use a different recovery method if you have the blob file (such as CWM) but TWRP is far superior unless you are looking to install Android Revolution HD.
Code:
adb push TWRP.blob /sdcard/
adb shell
dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
Wait until you see it succesfully transfer data.
Then:
Code:
adb reboot
exit
Once it reboots, you should see a progress bar at the ASUS screen. Once this completes you will have TWRP (or some other custom recovery installed)

With easyflasher I just hit flash and it says it worked correctly. Nothing appears on the tablet or anything.
I'm a newbie at adb, but I spent mostly all of yesterday learning it. After looking at your guide, I can say I was doing everything correct yesterday. I followed these same steps and still was sent back to the teamwin flashing screen after the reboot. There was no loading bar asus screen. I'm not sure what the problem is. Adb is working fine, it recognizes the device, it pushes the TWRP.blob, it goes through all the commands without error. Should I not be in a cold boot when entering this? Should I be in APX mode?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wasn't able to get it working with your adb download however, I'm using the adb provided with the SDK manager. Not sure if that makes a difference. And could it be my drivers? I believe I installed the asus sync for my drivers, so when trying to update to naked drivers it just says it's already up to date. Also, I really appreciate the guide you wrote up, it really helped me cement that I'm doing everything right.

Very very weird.... I just fixed it, I think. I guess my drivers were bad, because I was able to update them to the naked drivers when in APX mode. Then I was able to use easy flash to reflash rogueCWM. After rebooting however, TWRP 2.5.0.0 was installed! Very very weird.

Trying to root my OPO, but ADB doesn't recognize my device.

I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the device manager I get a yellow flag on the ADB interface:
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.

Seleuco said:
I've been trying to root for ages, but no matter what I do I can't get ADB to recognize my device. I've tried reinstalling the drivers from I don't know how many sources as well as adb/fastboot several times, but I always get the same result:
?
In the device manager I get a yellow flag on the ADB interface:
In the device manager I get a yellow flag on the ADB interface:
?
I honestly don't think there's any way I can do it unless I get some help from you guys. So please? How do I get my computer to recognize my OPO once and for all?
I'm following this guide FYI (must be the fifth I try): http://android.stackexchange.com/questions/106856/how-to-root-oneplus-one
Thanks to the kind souls willing to give a hand.
Click to expand...
Click to collapse
Honestly you don't need adb portion working to do this. Have you tried seeing if your computer recognizes your opo in fastboot mode?
Turn your phone off hold volume up and power button it will boot into fastboot. Then plug your phone into your computer let it install drivers then open command prompt where your fastboot file is and type fastboot devices if it shows something your good to go follow the rest of the guide unlock bootloader and install a custom recovery and SuperSU to root.
Also if its me I would install twrp recovery.

you sure you got the right drivers?

@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere

You need to install divers first, look at your screenshot, you have no driver installed for adb device.

giaur said:
You need to install divers first, look at your screenshot, you have no driver installed for adb device.
Click to expand...
Click to collapse
Honestly I don't even know at this point, I tried deleting and installing them a dozen times from different sources, but it doesn't recognize them. Do you know any idiot-proow way of installing the drivers?

wulsic said:
@Seleuco try this tutorial and also check Y for install adb drivers
http://forum.xda-developers.com/showthread.php?p=48915118
the easiest method for having adb everywhere
Click to expand...
Click to collapse
Thanks, but I actually took the screenshots right after running that program

Seleuco said:
Thanks, but I actually took the screenshots right after running that program
Click to expand...
Click to collapse
Did you also tried to install the driver manually in device manager?
See this link how you can do that:
http://www.technobuzz.net/install-nexus-5-driver-adb-fastboot-unlock-bootloader/
If these drivers don't work and or can't install then just extract Snoop05's adb installer and use those drivers :good: hope this would work now,
the issue is probably that there are so many drivers installed that they are conflicting with each other and windows is just deciding which one is better, so manually overriding it should fix it and else I guess you have to remove the old adb drivers with an program but first try these easy methods

Totally n00b question - from not-a-n00b

I just received the Pixel 2. Connected it to a Windows 10 box. Windows installed Microsoft drivers. I can't install Google drivers because Winblows says that the best drivers for my device are already installed. So I open an Explorer window, and there's the Pixel 2. I open that and it's a totally blank window. No, it's not the phone - ES shows directories in internal storage. (To make sure, I took a picture. It's in /DCIM/Camera.)
Enable debugging. Enable unlock. adb devices. No devices.
Okay, manually reboot to the bootloader. (The last line is Device State: locked) Fastboot sees the device.
fastboot boot twrp.img (I renamed it to make it easier). "FAILED (remote: Operation is not allowed in Lock State)"
I've owned Samsungs for so long I forgot that there were other manufacturers. What am I doing wrong? (I know it's got to be me, not the phone.)
How do I force Windows to replace the drivers (or do I really have to boot into Linux?) And how do I get the thing unlocked? Yes, I googled it. I searched here. I'm still stumped.

Maybe try this all in one tool
https://forum.xda-developers.com/pixel-2/development/tool-tool-one-driversunlocktwrpfactory-t3730228

Then check this out:
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417

flashing unlock did it. Thanks. Now to see if I can install everything (TWRP, Magisk, etc.) then a day of reinstalling all my apps and data.

Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)

Rukbat said:
Okay, TWRP and Magisk installed - thank you. Now only one thing is driving me crazy - plugging the Pixel into the PC doesn't show the Pixel. I hear the USB recognizing the phone, Device Manager sees the phone, but I can't find it as a drive, so I can copy data to it.
Oh, and when it's time to update to the next monthly, do I have to back my data up, flash stock, restore my data and reinstall Magisk? Or how does it work every month with a Pixel? (One update says it failed - I'm on the January update.)
Click to expand...
Click to collapse
To get your device to show up you have to pull the notification shade down and then change the device mode to mtp storage mode. As for updating to new security patchs I usually just use the factory image from Google and the flash-all script with the -w option removed in order to keep my data. Then flash my kernal and magisk.

I already had it set - I guess unlocking the bootloader resets it.

Rukbat said:
I already had it set - I guess unlocking the bootloader resets it.
Click to expand...
Click to collapse
It resets Everytime you disconnect the device or reboot for some dumb reason. It gets annoying.

Maybe in an update far away ...

Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank You

_satish_ said:
Hi, I may be wrong and silly. I want you to check this option when you connected your mobile to PC.
As in attached screen shot when you connect your mobile to pc there will be a notification "Android system" (Not USB debugging connected one) click it and will provide you options screen "Use USB to.." from there select "Transfer files" option instead of "charge this device"
Thank You
Click to expand...
Click to collapse
Attaching Screen shot

Trying to install /e/OS on FP3, but it hangs on fastboot on Windows 10

Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone point me into the right direction?

Nijs said:
Hi!
Yesterday, I received my brand new Fairphone 3 and I wanted to install /e/OS on it. However, I have some struggles with enabling fastboot on Windows 10. Hopefully someone can help me.
First, it is important to state that I was able to unlock the bootloader with fastboot on Windows 10, by following the official Fairphone guideluines; I unlocked dev settings and enabled usb debugging properly.
Next, after resetting everything to factory settings, I was able to boot in fastboot mode, whereafter I was trying to run ‘fastboot -w’ (which is the first step in order to flash /e/OS, according to the docs). After this, the terminal session hanged on ‘< waiting for any devices >’. Also, ‘fastboot devices’ did not reveal anything.
The following things I have tried to fix fastboot -w (all without success):
- Install Universal ADB Drivers
- Trying to change the driver in device settings. Even after removing the driver and rebooting Windows 10, the driver pops up as ‘FP3’ when I plug in the phone by usb (I do not understand why, maybe Windows is installing drivers in the background?)
- Installed the SDK 9.0 via Android Studio. After this, the phone is known as Samsung device (?)
- Toggling USB Preferences in Android between File Transfer and PTP
- Tried all USB ports on my computer
- Full phone factory reset
Can someone point me into the right direction?
Click to expand...
Click to collapse
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
When you boot into fastboot mode and connect to PC, open device manager and see if it lists the driver as "Android Bootloader interface".
If it isn't showing android bootloader interface, you will have to manually select the bootloader interface driver by right clicking on the driver showing for your device. Then select update driver. Then choose the options that let choose drivers from resources already installed on your PC, when you get to where it shows a list of drivers to choose from, find the bootloader interface driver and select it then see if the PC recognizes the device while in fastboot mode.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I do not see the interface you mention, however, I see 'Android' under 'other devices' and 'FP3' under 'portable devices' and 'Google Nexus ADB Interface' under SAMSUNG Android Phone (I did not install this, I assume Windows did this in the background).
Which option should I select to install the driver manually? Or none of them?

Question ROG phone 5s not recognized in fastboot mode, but ADB works... Windows driver issue?

Hi All,
I bought a ROG phone 5s (ZS676KS) direct from ASUS and I've been trying to root it all week. The firmware version is WW_18.1220.2111.160.
So far, I have been able to unlock the bootloader using Asus' app. My phone displays the unlocked bootloader warning on every boot.
I can't make fastboot work... the "adb reboot bootloader" command does work. I can also boot using the power + volume up button. But the "fastboot devices" command always comes up empty.
I found two possible reasons why fastboot doesn't work. So far I failed to fix either one.
First, the "OEM unlocking" option is missing in my developer options menu. I have the "USB debugging" option checked off. But many of the guides I read online say to allow OEM unlocking and I can't do that. But I've also seen people say that it doesn't matter. So, I don't know if this is a real problem. I can't find any reference to this problem except in Samsung phones. I tried the recommended fix but it didn't work.
Second, something's wrong with the fastboot driver on my computer. When get my phone into fastboot mode and plug it into the computer, device manager shows a device called "ASUS_I005D" with an orange caution icon on it. The error message in the properties menu says "The drivers for this device are not installed. (code 28)". This is probably the real problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Windows isn't finding a driver with its online driver search. I spent a few hours playing with Windows drivers to no avail. But maybe I missed something. I did find "ASUS_Android_USB_drivers_for_Windows_20150212" online and it didn't help.
I have tried different wires and USB ports and I'm using the side port of the phone instead of the bottom (although I tried the bottom port too). I tried another computer and that didn't work. But this was before I realized what was happening with windows drivers so I didn't check the device manager. I'm away from home now so I just have access to the one computer for now.
Does anyone know where I can find the correct driver? Or is there another approach I haven't considered? I hope there's nothing fundamentally wrong with the phone. I kind of just bought it without explicitly verifying, assuming the 5s is rootable since the 5 is...
Thanks Everybody,

Success is disgusted by some people, and will not share any files for free in the future.

It's not your device but likely Win 10 playing games with you. First completely uninstall the device driver to clean things up. Reboot your pc into Safe Mode. Plug in your phone from the side connector with a good data capable USB cable. From Device Manager choose "Add Legacy Hardware" from the menu and point the location to where you have saved the latest official Android USB drivers and install. Reboot Windows normally. If things have gone well, you should be able to both ADB & Fastboot into your device.

What a relief.
I am now able to flash my patched boot.img.
Thanks to both of you. I'm off to the races...

For me I just get a Ubuntu iso, boot your computer off a USB stick, install adb and fastboot via apt, and boom, no crappy drivers needed