Database Info

[Q] Cannot install TWRP

I managed to root my TF101 using this thread:
http://forum.xda-developers.com/showthread.php?t=1689193
The problem is I TWRP is not installed.
When I press Volume Down + Power buttons and then The Volume Up, my device goes to a screen with 2 icons, "Wipe Data" and "Android" and after 10 seconds it boots to Android. I assume this is the stock recovery.
I Tried:
1) Both EasyFlashers (http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html)
2) Goo Manager
3) Terminal Mathod (http://teamw.in/project/twrp2/109)
All of them failed.
Is there anything else for me to try?

What were your steps when you tried using Easyflasher ?

I confirmed the device was in APX mode, through the device manager.
Run EasyFlasher.exe and chose the SBK1 (my TF101 is B60)
Chose "TWRP 2.2.1" and pressed Flash.
Everything seems to be working, since both in the command prompt and the device I get that the process was successful, but booting to recovery does not run TWRP, instead if goes to the screen I mentioned earlier.

lefterhs said:
I confirmed the device was in APX mode, through the device manager.
Run EasyFlasher.exe and chose the SBK1 (my TF101 is B60)
Chose "TWRP 2.2.1" and pressed Flash.
Everything seems to be working, since both in the command prompt and the device I get that the process was successful, but booting to recovery does not run TWRP, instead if goes to the screen I mentioned earlier.
Click to expand...
Click to collapse
Not sure it matters, but did you run Easyflasher as Admin ?
Ensure the correct APX drivers were installed ?
Reboot the TF once before trying to enter recovery ?
Held the Vol Down & Power from a powered off state until the white text appeared at the top of the screen, then hit volume up to enter RCK ?

*Detection* said:
Not sure it matters, but did you run Easyflasher as Admin ?
Ensure the correct APX drivers were installed ?
Reboot the TF once before trying to enter recovery ?
Held the Vol Down & Power from a powered off state until the white text appeared at the top of the screen, then hit volume up to enter RCK ?
Click to expand...
Click to collapse
1. Yes, I am administrator.
2. I used Universal Naked Drivers 0.72 from here:http://forum.xda-developers.com/showthread.php?t=1514942
3. Yes, after using any of the methods mentioned, I allowed it to reboot once normally.
4. Yes, I get the screen I mentioned with the Wipe Data/Android, when I press Vol Up after the Vol Down+Power combination.

When I say Run as Admin, I mean Right click the exe and choose Run as Administrator
I'd try using the drivers included in the Easyflasher bundle here (EDIT - Dev recommends the drivers you used anyway)
http://forum.xda-developers.com/showthread.php?t=1688012
As it uses APX this shouldn't matter, but make sure USB Debugging is enabled in Developer Options too and let it install the drivers while powered on and connected to the PC
I'd try another USB port too to rule that out
Which SBK/Serial is your TF?
EDIT -Another thought, are you running a stock ROM atm? Which one ?
You could try using Peri to flash TWRP
http://forum.xda-developers.com/showthread.php?t=1681155

I tried the Peri.
Continue? (Y/N) Y
Starting... This will take awhile...
9444+1 records in
9444+1 records out
4835404 bytes transferred in 2.385 secs (2027423 bytes/sec)
Done! You should see some reported #s above.
Now we reboot the TF again, you'll see a blue bar.
It will take awhile to fill, then you have recovery!
Click to expand...
Click to collapse
Unfortunately, I don't see any blue bar. The device just reboots to Android.
The serial is: B60KAS103665
Yes, I use the stock ROM, I never tried to install a custom ROM, until now.
IML74K.WW_epad-9.2.1.27-20120615
Actually, my goal is to install the KatKiss ROM using these instructions:
3w.transformerforums.com/forum/asus-transformer-tf101-development/33773-official-faq-katkiss-rom-formerly-teameos-4-android-4-2-x-tf101.html
Is there any other method, not using TWRP, to install KatKiss?
Update:
I also tried to install CM recovery, using the 3rd option of 1-Click Transformer Root. Again, I don't see anything to get installed (a blue bar is not showing) and it just reboots to Android.
Lately, I have a problem.
I get a "DMClient has stopped" error twice each time I turn the TF101 on. I think this is the ASUS update process. Can this be relevant?

lefterhs said:
I tried the Peri.
Unfortunately, I don't see any blue bar. The device just reboots to Android.
The serial is: B60KAS103665
Yes, I use the stock ROM, I never tried to install a custom ROM, until now.
IML74K.WW_epad-9.2.1.27-20120615
Actually, my goal is to install the KatKiss ROM using these instructions:
3w.transformerforums.com/forum/asus-transformer-tf101-development/33773-official-faq-katkiss-rom-formerly-teameos-4-android-4-2-x-tf101.html
Is there any other method, not using TWRP, to install KatKiss?
Click to expand...
Click to collapse
Your TF is SBK1, so should have no problem getting a custom recovery flashed to it, the only thing I'm wondering is if the stock ROM is causing problems, I seem to remember someone else with stock having problems getting a modern custom recovery flashed too
Unfortunately the only way to flash KatKiss is from custom recovery TWRP as the ROMs are released in flashable .zip format
Do you have another PC you could use to try and flash TWRP via Easyflasher ?
What OS are you running on your PC ?
At least one of the methods you have tried should have definitely worked, so long as the TF is in APX mode, the drivers are installed, and the PC can see the TF, Easyflasher should have done the job
I never recommend flashing CWM as it screws with JB ROMs, but it might be worth trying to flash that recovery first, then a custom ICS ROM, after that if you get that far, try installing TWRP again before trying to flash a JB ROM
Just make sure you don't flash a JB ROM with CWM recovery installed
---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------
lefterhs said:
Lately, I have a problem.
I get a "DMClient has stopped" error twice each time I turn the TF101 on. I think this is the ASUS update process. Can this be relevant?
Click to expand...
Click to collapse
Hmm, you could try clearing the data / cache from DMClient in Settings > Apps > All
Code:
1. Settings
2. Applications
3. Running services
4. All
5. DMClient
6. Clear data
7. Force stop
8. Shut down and restart the tablet
Maybe there is an old update file stuck in cache causing problems
Have you tried factory resetting it 100% ?

I did a few things, at the same time.
1. Changed USB port.
2. Used the original EasyFlasher.
3. Cleared and force stopped the DMClient, which I believe did the trick.
Now, TWRP got installed, although It also did a hard reset to my device. When it opened, I had to setup the device like it was the first time I turn it on.
Anyway, I think I will continue to Kat Kiss installation now.
Thanks for your help.

lefterhs said:
I did a few things, at the same time.
1. Changed USB port.
2. Used the original EasyFlasher.
3. Cleared and force stopped the DMClient, which I believe did the trick.
Now, TWRP got installed, although It also did a hard reset to my device. When it opened, I had to setup the device like it was the first time I turn it on.
Anyway, I think I will continue to Kat Kiss installation now.
Thanks for your help.
Click to expand...
Click to collapse
Ah good news, yea it does sound as if the DMClient was stopping the install, Im not sure exactly how it works, but possibly if the TF thinks there is a pending update, it won't allow the flash until its cleared
Good thing you mentioned it, I was almost at a loss as to what was causing the problem
And yep, now you have it installed, make sure you are up to date 2.3.2.3 (Use GooManager to install the latest version), and then you can install any custom ROM you like from TWRP

lefterhs said:
I managed to root my TF101 using this thread:
http://forum.xda-developers.com/showthread.php?t=1689193
The problem is I TWRP is not installed.
When I press Volume Down + Power buttons and then The Volume Up, my device goes to a screen with 2 icons, "Wipe Data" and "Android" and after 10 seconds it boots to Android. I assume this is the stock recovery.
I Tried:
1) Both EasyFlashers (http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html)
2) Goo Manager
3) Terminal Mathod (http://teamw.in/project/twrp2/109)
All of them failed.
Is there anything else for me to try?
Click to expand...
Click to collapse
this has a beta twrp zip that is flashable, maybe help? http://forum.xda-developers.com/showthread.php?t=2308565

Hello,
I'm trying to install the MarshMallow 6.0.1 Release on my TF101 (SBK2 -BBxxxxx) with stock rom IMLK74K.WW_epad-9.2.1.27-20120615 and easyflasher (universal naked drivers installed correctly on windows 10). I can flash it correctly but I have the same problem as lefterhs.
I have also tried different version of twrp, latest easyflasher, different USB ports, with USB debugging on the device, still same problem, only choice is android and wipe data.
I have also tried with CWM but I had the error can't mount SD card. Rooted with 1-click transformer root. I begin to believe I will not be able to change the ROM. Any idea?
Thanks,
EDIT: Problem solved, managed to flash Roach CWM 5.5.0.4 from EasyFlasher and flash TWRP 2.8.1.1 from zip inside Roach CWM 5.5.0.4 recovery. Then followed the procedure in https://forum.xda-developers.com/eee-pad-transformer/development/rom-t3318496. Katkiss is running on my tf101.
*Detection* said:
Ah good news, yea it does sound as if the DMClient was stopping the install, Im not sure exactly how it works, but possibly if the TF thinks there is a pending update, it won't allow the flash until its cleared
Good thing you mentioned it, I was almost at a loss as to what was causing the problem
And yep, now you have it installed, make sure you are up to date 2.3.2.3 (Use GooManager to install the latest version), and then you can install any custom ROM you like from TWRP
Click to expand...
Click to collapse

I need help with this tablet - few questions

Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?

stanglx said:
Background:
I attempted to root the device. so I installed CWM... Well it doesnt stick. once you boot it never stays. When I go into recovery mode from the boot loader it says "no command" But if I flash it and then reboot right into the bootloader then go into recovery it works fine.
First issue: CWM doesnt stick
which led me to another issue..
ADB doesnt work in CWM (which I thought). So I decided to flash PhilZ recovery and found it didnt work there either! So I figured it had to be my drivers - but they worked fine in Windows and when the device is booted normally in the OS. (I am using Nvidia latest drivers)
Then I figured let me restore the unit back to the original image (i signed up as a developer) downloaded the Nvidia 1.2 Image and reflashed everything using fastboot (system, boot, recovery, data, etc.)
Since I had never tried to go into the stock recovery maybe it was CWM or PhilZ...
Leads to my next issue:
The stock recovery doesnt work no matter how many times I flash it. When I go into the bootloader and click on recovery mode I get "no command" with the andorid guy dead.
1. How can I get back the stock recovery using Nvidia's image. The recovery is not working
2. How can I get CWM to stick?
3. Why isnt ADB working in recovery mode but working fine when booted in the device?
Click to expand...
Click to collapse
All has been fixed except for #2. Cant get CWM to stick... but for 1 and 3:
OK.. got the stock recovery - I didnt actually know you had to do volume up when at the "no command" screen..
and also I figured out how to fix the driver issue...
For anyone else having the issue you need to uninstall the driver until it shows up as Shield with the exclamation. You must be in the recovery in an area like sideload.. (Not in android OS)
Then Update Driver, Browser and then click on "Let Me Pick from a list on my computer"... find Android then select "Android Composite ADB Interface".
Now the driver works in ADB and in the OS

Same Problem
I'm having the same problem with CWM reverting to stock recovery after system boot. I didn't see your post until after I posted my own thread -- I probably should have titled it specifically about the stock recovery reversion so others will find it. Anyway, not that there's at least one other person besides me having this problem, I'm less worried that it's just me being stupid. Although that's always a possibility. Maybe someone will come along and help.

Recovery Reversion Problem Solved
Okay, I solved my recovery reversion problem -- I wasn't using either a custom boot.img or the Beta SuperSu (currently BETA-SuperSU-v2.42.zip), one of which is needed to keep root on Lollipop. (Apparently I knew this a month ago when I first went to 5.0.)

I can't root my OS12 !

And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please

MrSeler said:
And I have no idea why. Before I downloaded the newest update I upgraded my TWRP to the latest version. After the update I tried first to install SuperSU via google store but didnt work so i downloaded the installable zip and tried through TWRP. All I get is : E: failed to verify whole-file signature; E: signature verification failed.
Tried the old SuperSu that always worked (2.02) but I get the same bug.
I think the problem is that instead of TWRP when i start my phone with start button + vol down it gets into CYANOGEN recovery. I just installed TWRP ver 2.8.5.1 but its not working =/ dont know what to do, help please
Click to expand...
Click to collapse
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.

gsmyth said:
You need to resinstall TWRP, just after you have done so, reboot back to TWRP instead of rebooting the whole system. Once back in TWRP you can flash SuperSU again, then reboot and you should be fine. Also make sure you have the cyanogen recovery option unticked under developer settings.
Click to expand...
Click to collapse
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"

MrSeler said:
How do i reinstall TWRP? im pretty sure ive done it already but still when i turn on the phone I have the cyanogen recovery on, tried to do it with TWRP manager (at first i couldnt start it because but later it worked. However, when i click on "Reboot to Recovery" it does not work) I have recovery installed in TWRP manager (ver 2.8.6.0) maybe i can do sth with this ?
Edit: I was able to start TWRP manager, now I'm not again because it says "root is required for this app"
Click to expand...
Click to collapse
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off

gsmyth said:
You'll have to install it via PC fastboot or using a Tool, see below.
Install custom recovery via fastboot:
http://forum.xda-developers.com/showthread.php?t=2788632
Toolkit:
http://forum.xda-developers.com/oneplus-one/development/oneplus-one-toolkit-manudroid19-gui-t2807418
Make sure the following option is turned off.
Settings>Developer options>Update Cyanogen recovery - Off
Click to expand...
Click to collapse
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know

MrSeler said:
Tried via fastboot and seemingly it worked as you can see here http://i.imgur.com/vKTQUQ5.png
But when i turn on the phone i still get cyanogen recovery =/ will try the tool kit and let You know
Click to expand...
Click to collapse
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery

gsmyth said:
Once it flashes, are you rebooting back into recovery first (without switching off, fully rebooting, anything else)? You should boot into TWRP and then you can reboot fully, it should be fine. If you just reboot out of TWRP after flashing the it gets overwritten by the stock cyanogen recovery.
After completing the TWRP flash in ABD run the following command.
Code:
adb reboot recovery
Click to expand...
Click to collapse
Im doing what Im told, so - After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode.
Wish I wasnt so braindead on this field =/ and the cyanogen recovery welcomes me every time
okay so instead of fastboot reboot command i should write the one you gave me? gonna try
EDIT: ERROR, DEVICE NOT FOUND

yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?

MrSeler said:
yeah, i was doing it wrong but i did it right this time and it is still not working. Have my usb debugging on
Is it possible that after the update i dont have the bootloader anymore?
Click to expand...
Click to collapse
Your boot loader shouldn't be touched.

gsmyth said:
Your boot loader shouldn't be touched.
Click to expand...
Click to collapse
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.

MrSeler said:
Okay. I tried and tried but failed. I have no idea what to do anymore. Downloaded new drivers for pc and new fastboot, tried like 15times to flash twrp on my phone and seemingly it worked but when I rebooted, turned it off and on again with volume - it's always cyanogen recovery there, never twrp. I downloaded twrp manager but it won't work because it requires root and I can't root because manager won't work. Saw on oneplus forum that some people have exact same problem but there S been no solution so far and I have no idea what to do anymore. The only thing I haven't tried yet is to hold start+volume- keys after I flash twrp and reboot the phone using the code, so instead of having to turn it off and on again maybe I ll be able to get into the twrp instantly and it won't get overwritten by cyanogen recovery.
Click to expand...
Click to collapse
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.

oasisdave said:
OK so i am experiencing the EXACT same issues. When I go into Fastboot Mode all I get is a small cyanogen head forllowed by the words 'FASTBOOT MODE' I get no menu to navigate or anything. TWRP appears to install but I get Cyanogen recover every time. If I use the toolkit and go to fastboot mode it sees it as an unlocked fastboot device but will not allow me to root the device.
Click to expand...
Click to collapse
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/

MrSeler said:
After flashboot reboot do not let phone turn on again but use the start + volume- combination, it will take you to twrp. Found the solution finally but I still have some issues with graphics and Google account =/
Click to expand...
Click to collapse
Yeah, that's not working for me, still goes straight to Cyanogen Recovery.

See last question in FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Transmitted via Bacon

TWRP just won't install. EVEN when I do the "no fastboot reboot"

EDIT: IT FINALLY WORKED! I just flashed an older version of twrp. Pretty weird how that's working and the newer one isn't. Should I keep this post for people with the same problem?
I know about the problem with cm12s and with the cm recovery thing.
I tried everything. Searched and tried nearly all of the different recovery or root install tutorials. But it's still not working!
Every time I install a recovery (both twrp and cwm) it won't install even though it said it worked. When I do the "remove usb, vol down + power" trick after flashing it just won't boot. It just shows the logo and then it reboots. If I release everything it boots my phone up normally. Even clicking recovery reboot in the reboot menu doesn't work. Then it will bring me to the cyanogen recovery.
My debugging mode is on.
Cyanogen recovery update is OFF.
I'm now using cm12.1s but it didn't work on cm12s either.
ADB and Fastboot are working fine. I tested it and my phone reacts when I give it commands (like fastboot reboot or adb devices)
My bootloader is unlocked (confirmed with fastboot oem device-info)
I just got this phone yesterday. I didn't expect this much trouble with just rooting.
ps: this is one of those "it should work, but it doesn't" moments.

Yes. After cm12 the cyanogenmod is ignoring the cyanogen off recovery mark.
After flashing recovery twrp via fastboot, direct reboot to recovery manually via button. Try look at faq. See q22. http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136

Always keep a post like this, it's good for future reference (people having the same question will thank you for sure)!

Use Philz recovery. Many are facing same issues with TWRP

realbabilu said:
Yes. After cm12 the cyanogenmod is ignoring the cyanogen off recovery mark.
After flashing recovery twrp via fastboot, direct reboot to recovery manually via button. Try look at faq. See q22. http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Click to expand...
Click to collapse
Just like every other method I've tried, that method doesn't seem to work either.

Hi Benalimarwan,
Thanks for your post. I flashed openrecovery-twrp-2.8.5.0-bacon.img. but, it still didn't work. When I logged into recovery mode it still logged into cynogen recovery. Which version of twrp did you flash? Thanks!

lotherius said:
Just like every other method I've tried, that method doesn't seem to work either.
Click to expand...
Click to collapse
Works for me from latest stable CM12
1. Unlocking Bootloader via fastboot
fastboot oem unlock
fastboot reboot
2. USB Debugging -
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
3. Disable CM Recovery Protection -
On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
4. Installing a Custom Recovery
fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img
got it from http://techerrata.com/browse/twrp2/bacon (one recommends don't use 2.8.7)
reboot to system
5. Flash your custom recovery again, but after flashing don't do a normal reboot. (DONT FORGOT TO Disable CM Recovery Protection first in normal boot before)
After the flash has succeeded disconnect the usb cable, then power down the phone by holding the power button down, once it's powered off use the power + volume down button combo to boot directly into recovery. This first forced reboot into recovery somehow subverts what was keeping it from staying flashed and all subsequent normal reboots into recovery will boot into the custom recovery of your choice.

gawd i nearly went out of my mind last night trying to flash TWRP , everything was working fine , fastboot checked out , unlocked the OEM also but it refused to flash TWRP , threw up errors "cannot open recovery' then i remembered the "hide file extensions for known file types" in win7 which was checked and ran
fastboot flash recovery rec[TAB]
Click to expand...
Click to collapse
.i.e hit tab button before hitting enter and it flashed it like a charm !! and i was already to throw this new cell out of my window

Please help me understand Step 5.
Once 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img' is completed, I shouldn't do a 'fastboot reboot'. Instead of that disconnect USB, and then Poweroff using power button. Now use Power + Volume down to boot into recovery. This should allow me to use twrp recovery. Is my understanding correct?
Regards,
Kiran

Hi Guys,
Just did step 5 again.
Did 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img' and disconnected USB, Powered off the device and powered it on using Volume down + Power button. It logged into twrp recovery. I then selected 'Install' and phone automatically got rebooted. Not sure why. I powered it off and powered on again using volume down + Power buttons. It then logged into CM recovery.
Repeated above step again. Again faced same issue. Any ideas?
I unlocked boot loader 4/5 days back. Since twrp recovery was not working, I continued using phone. Installed several apps. Do you think this might be an issue? Do I have to unlock boot loader again and then do 'fastboot flash recovery openrecovery-twrp-2.8.5.1-bacon.img'??? Please suggest
Regards,
Kiran

Do it this way with fastboot:
fastboot flash recovery recovery.img (you know the drill...)
when this is completed type in fastboot reboot
BUT MOST IMPORTANT! hold the volume down button on your opo the whole time before you press enter to run the command and keep holding it until TWRP boots up.
This worked on 5 OPO's. (3 were mine, one was my brother's and one is a friend's)

im too on stock 12.1..So which twrp recovery version ll i flash????
1+1

Wug's Bacon Root Toolkit
I had this problem when I tried flashing the custom recovery (TWRP) manually. It didn't matter what I tried, I could never manage to make TWRP persist over CM Recovery after a reboot. After giving up and staying in stock for some time, I decided to try again after getting the OTA to CM 12.1S, but, as no surprise, the same thing still happened. So, as a last try, I downloaded Wug's Bacon Root Toolkit and voila... it finally worked, I had a TWRP that persisted over CM Recovery after a reboot. I don't know what the toolkit did different than me when I did it manually, but it managed to make it work! Hopefully it also works for you...

only used toolkit for Fastboot driver installation...Good step by step instructions...but flashed 2.8.7.0 twrp with adb commands as described by Heisenberb...finally installed recovery n rooted my opo...
1+1
---------- Post added at 11:48 AM ---------- Previous post was at 11:45 AM ----------
Never used cyanogenmod on my N4 N5...Flashing process ws easy on nexus devices
1+1

AcmE85, Your suggestion worked like a charm bro. Finally was able to fix the issue. Thanks much for your help!

moto g stuck in bootloop! rooted! unlocked bootloader! but usb debugging disabled!

the title would sum it up guys!. its a falcon! i have twrp installed, but even when i go to recovery it reboot before i can do anything! help please guys! when i go into fastboot mode (i think its called fastboot, idk i am a noob, by pressing power and volume down key) , all options are visible and its stable, i.e it does not reboot! however if i go to recovery, it starts rebooting! usb debugging is disabled! idk what to do! is there any way i can enable usb debugging via fastboot? help please!

got exactly the same problem. it would be a great help if someone could assist us @AndyCr15

Saadjamil36 said:
got exactly the same problem. it would be a great help if someone could assist us @AndyCr15
Click to expand...
Click to collapse
In case of a bootloop, I suggest you download a new rom and install it via twrp's file manager, using a pendrive/otg pendrive. Else,your can flash the stock motorola firmware using fastboot. that method always works in case of softbrick.

Tried to reflash twrp?

Debanka said:
In case of a bootloop, I suggest you download a new rom and install it via twrp's file manager, using a pendrive/otg pendrive. Else,your can flash the stock motorola firmware using fastboot. that method always works in case of softbrick.
Click to expand...
Click to collapse
Hey, thank you the problem was solved but then I installed CyanogenMod 13.0 on my moto g. After a day of use the phone automatically stopped working and i restarted it. Didnt display screen after CyanogenMod animation. I booted into TWRP recovery, was backing up data into a usb otg when the backup failed and the phone rebooted itself. Now it doesnt even display the CyanogenMod startup animation. I tried to enter twrp recovery again. It shows the main blue screen with twrp written on it but doesnt proceed further instead it restarts. I tried flashing twrp recovery again but the same problem persists. please help me out

Try flashing stock ROM, then again TWRP and CM13 via TWRP. I suggest this version of TWRP (NOTHEME version!).