Database Info

[Q] Can`t flash recovery

Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?

n.N.n. said:
Before the 38R update I had my bootloader unlocked, TWRP recovery flashed and the device rooted. I did all of this via a toolkit and it worked fine. After I did the 38R OTA update my device lost its root (so far nothing unusual). So I tried to boot into recovery to just install the superuser zip again. But my custom recovery was gone. Instead there was just the standard cyanogenmod recovery. Back to my PC I tried to reinstall the TWRP but it just won`t work. I tried the toolkit, I tried the guide from here (command line and fastboot), I unlocked the bootloader again and repeated these steps, but so far I can`t install a custom recovery (tried TWRP and CWM). When using the command line there is no error message, it just finishes "successful"
Here is the log:
C:\tmp\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8570 KB)...
OKAY [ 0.271s]
writing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.411s
And before anyone asks, I did uncheck the update CM recovery option ^^
Does anyone have a solution to my problem ?
Click to expand...
Click to collapse
do you reboot into recovery when done or straight to OS

playya said:
do you reboot into recovery when done or straight to OS
Click to expand...
Click to collapse
The guide says to unlock bootloader, reboot to os, change settings, flash recovery, reboot, root.
But after your input, I did try it without the complete reboot and it worked. But shouldn`t a flashed recovery be persistant?
Edit: Did a second reboot, now there is the stock recovery again =/ But the root persisted.

[Q] Cannot enter recovery after flash of TWRP
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?

Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon

Have tried several recovery images
timmaaa said:
Have you tried an earlier build of TWRP, like 2.7.1.1 maybe?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes, I have tried both TWRP 2.7.1.0 and 2.7.1.1 and Stock-recovery.img from 2008-12-31 - they all freeze in Android prompt when I try to boot in recovery mode. The only difference being, that only TWRP 2.8.0.1 causes the prompt to tyrn blue and then fade away.

The device just displays the Android [1+ said:
logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.

Trie advanced reboot to recove - no luck
habnzrot said:
Try this to get to TWRP... with the TWRP installed, go to Setting, Developer Options then ticked the box on the "Advanced reboot". Long pressed "Power button" then "Reboot" this will give you option to reboot to "recovery". Hope this work for you. Goodluck.
Click to expand...
Click to collapse
When I select reboot - recovery, I just get a brief message that 1+1 is rebooting and then it freezes in the Android prompt as before.

Re: can't flash a recovery that will work
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.

Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....

Success, finally
driftt said:
Hey.
I've been trying to flash a recovery to my OPO ever since I got it a few days ago. None of those I'd see in these threads would work: I've tried all recent versions of TWRP, CWM and Philz's I could find but nothing.
Something came to my mind a bit later upon reading some other thread about rooting without wiping (which is mostly unrelated) in which I'd read that you should enter recovery by pressing VolDown+Power all the while you're on the fastboot low-light screen. It did ring a bell to me: I'd been entering recovery after booting normally at least once. I'd never been to recovery straight from the fastboot screen. So I tried flashing all those TWRP, CWM again and none worked.
Except that now the latest version of Philz's touch recovery worked this time: I flashed it through fastboot, and went straight from fastboot screen to recovery (I didn't try to reboot or shut it off) with VolDown+Power. It worked this time. And I can access recovery normally through the reboot section of the OS (with the advanced options). Tried to post the link to the specific recovery image that worked for me but it seems I don't have enough posts. Version is 6.57.8 bacon, you should find it in the philz touch goo.im website
I'm definitely not qualified enough to know what could cause this. And I wouldn't even know if this particular process will work with your device. Keep me posted in any case.
Click to expand...
Click to collapse
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
Thanks milesman, but as you can see from the post above, the using the Philz image was successful. However, your suggestions may help other people, since the process really seems not to be robust.

had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go

TorkelJensen said:
My situation is similar to the one described by nNn. I have just received my 1+1 64GB which automatically updated to 38R. I have tried to use the following sequence to install the TWRP recovery image:
- Installed SDK Toolekit r23.0.2-windows
- Installed the SAMSUNG USB Driver v1.5.33.0
- adb reboot bootloader
- fastboot oem unlock
- Activated Developer options and unchecked 'Update CM recovery'
- adb reboot bootloader
- fastboot flash recovery openrecovery-twrp-2.8.0.1-bacon.img (the log looked OK)
- fastboot reboot (device opens normally)
- adb reboot recovery
The device just displays the Android [1+] logo, which turns blue and then fades away. There is no way I can enter into recovery mode - PowerOn + Volume down gives the same result.
I have also tried to flash other version of TWRP, Philtz, CWM, and Stock-recovery, but they all cause the phone to freeze in the Anroid [1+] logo when I try to enter recovery mode.
I have seen many reports about TWRP not replacing the Stock-recovery, but nobody seems to have exactly my problem.
Anybody any suggestions?
Click to expand...
Click to collapse
I've had my OPO for a couple of weeks now and have had this problem all along. It took until today that i found this thread with someone having the exact same problem as me. After flashing a LOT of different recoveries (and different versions) I too noticed the only recovery I could successfully enter is Philz (although not all versions). I would prefer TWRP as recovery, but as long as I have one that is working that's good enough! It does however annoy me that almost nobody else has this problem. It makes me believe there is something wrong with the device. Flashing recovery in fastboot is always successful according to the logs. Erasing recovery in fastboot before flashing new one did not solve the problem either.
Before unlocking the bootloader, installing recovery and rooting, I updated the device from 33R to 38R. I now regret not doing that before updating...
I uploaded two videos showing the artifacts. The videos were recorded right after installing openrecovery-twrp-2.8.1.0-bacon.img from goo.im.
Since I haven't posted that much on XDA before I wasn't allowed to post links, please copy and paste.
youtu.be/jYJUfOOjaUE
youtu.be/GYcSjUKpOaE
Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
As written in the first post by n.N.n. this problem is not related to this option. The checkbox is unticked and recovery doesn't get replaced by CMs stock, it fails to boot.

Couldn't flash any recovery until I unchecked the "update CM recovery" option in the developper, thanks for the tip ! I didn't think this was also protecting the recovery !

I've had same exact probem when flashing twrp 2.8.x.x from fastboot or twrp. As a last resort I gave Flashify a go and to my surprise, it worked.

I had the same problem, but PhilZ's lastest (6.58.8 as of now) worked for me. I wonder why this is happening to some of us, but I'm glad I sorted it.

Night5talker said:
had same issue
goto settings > dev options > uncheck update CM recovery
root phone from scratch again, if you have bootloader unlocked then just flash recovery and you are good to go
Click to expand...
Click to collapse
Thanks, that solved the problem for me! I've flashed TWRP and CWM, but after rebooting into recovery mode there was always the CM stock recovery. After unchecking this in the dev settings it worked as it should.

milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This worked for me thanks.

milesman said:
Try erasing the recovery before flashing it (see bellow).
fastboot erase recovery
fastboot flash recovery (filename).
If that fails try another usb cable/port. If all else fails try another pc....
Click to expand...
Click to collapse
This doesn't work for me.
erasing 'recovery'...
OKAY [ 0.026s]
finished. total time: 0.026s
Still stock recovery after flashing TWRP. Why is this so weird?
The Update thing in Developer is unchecked.
My other OPO was perfect
---------- Post added at 02:32 PM ---------- Previous post was at 02:19 PM ----------
TorkelJensen said:
Thanks a lot driftt - Finally I manged to boot into recovery following your recipe. First I tried with the TWRP-2.8.0.1, flashing it and directly trying to boot into revery via Power+Volume down - no luck. Then I flashed the Filz-6.57.8 image obtained from //goo.im/devs/philz_touch/CWM_Advanced_Edition/bacon/ and low and behold I could now boot into recovery as you had also experienced. I'm now the happy owner of a rooted 1+1, but it is still a mystery why the process is so shaky.
---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------
This works for me.
Click to expand...
Click to collapse

After installing Custom Recovery (mine id TWRP), turn off the handphone. After that, do directly the boot to recovery (On/Off Button + Volume Down). DO NOT do the normal start, since the system will erase the custom recovery (and instal the "standard" recovery)

[Q] Getting back recovery and root after OTA to CM12s

Hello,
I have recived the OTA today and I flashed it and now I dont have a custom recovery and root. What steps do I need to take to get those things back? I have tried to use this guide https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/ but after flashing recovery.img through ADB I still have normal CM recovery.

Go to Developer Options in Settings and disable the "update CM recovery" option.
Transmitted via Bacon

It has been disabled the whole time

Ok. So you say you're flashing the recovery through adb but that's impossible so I'm assuming you're flashing with fastboot, right?
Transmitted via Bacon

I'm not really good in those names.. I have isnerted a screenshot from this program.

xamilek555 said:
I'm not really good in those names.. [emoji14] I have isnerted a screenshot from this program.
Click to expand...
Click to collapse
Looks ok. Where are you getting the recovery from? Did you rename it to "recovery.img" for a reason?
Transmitted via Bacon

I've got that file from TWRP website and I renamed it to recovery.img. I have succesfully booted into this recovery with a command "fastboot boot recovery.img" which allowed me to flash root and xposed form it but after rebooting the phone the old recovery remains...

I have the same problem. Flash TWRP says it's flashed OK, but when I reboot to recovery it's still stock.

Linnyuk said:
I have the same problem. Flash TWRP says it's flashed OK, but when I reboot to recovery it's still stock.
Click to expand...
Click to collapse
Try updating the Android SDK. That's what worked for me. ?
Sent from my A0001 using Xparent BlueTapatalk 2

I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img

xamilek555 said:
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Same situation here...this solution isn't working for me, same problem, always Cyanogen based recovery...

After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.

mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
It works! I think it because of the dev settings into CM12S which force the recovery to be CM12S' one.
Thanks

Messatsu said:
It works! I think it because of the dev settings into CM12S which force the recovery to be CM12S' one.
Thanks
Click to expand...
Click to collapse
I'm having the same problem, can someone go over start to finish how they fixed this issue?

What worked for me
I previously had TWRP installed, wiped and did the C12S flash but didn't flash SuperSu before rebooting. This removed TWRP and brought me to Cynogen Recovery whenever going into recovery mode (Vol Dwn + Power). This also removed the root from my phone. To fix this took some digging and I came up with the following solutions as long as you had TWRP installed at one point. If not then unlock your boot loader and re install. I named my TWRP File Recovery just to keep things simple, but whatever your TWRP Filename is put that in at #5.
1) Enter Fastboot Mode (Vol Up + Power)
2) On your computer open command prompt (Ctrl R)
3) Plug your phone in
4) Type the following minus the quotes
"cd desktop/android-sdk-windows/platform-tools"
5) fastboot boot recovery.img
This will boot your TWRP, you can then go to flash your SuperSu file and you're done!

im having this issue too : /

mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
I've tried so many things today, this is the only thing that worked. Thank You!

mozyman said:
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
It works! I had the issue and this procedure solved it ! Thanks !!! :good::good::good:

Hi all,
I have just installed CM12s on my OPO and it was meant to install TWRP but each time i go into recovery to install SuperSU its still CM Recovery
1) Enter Fastboot Mode (Vol Up + Power)
2) On your computer open command prompt (Ctrl R)
3) Plug your phone in
4) Type the following minus the quotes
"cd desktop/android-sdk-windows/platform-tools"
5) fastboot boot recovery.img
Click to expand...
Click to collapse
I have done that and yey TWRP appeared and i Installed SuperUser but when i clicked on the app it said there was an issue with the binary, so i thought i would reboot into recovery and install it again...but CM recovery appeared again
Originally Posted by mozyman
After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
I thought i would give that a try but nothing seems to happen, the screen just goes black. Im reboting my OPO and when the white OPO logo appears im holding the buttons down....is this too soon or too late?
Originally Posted by xamilek555
I've downloaded fresh verison today so it isnt the solution in my case :/
Somebody gave me this solution and it worked!
fastboot erase recovery
fastboot reboot-bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I have even attempted to do that but it doesnt seem to work....
Can someone help me out here....

After flashing new recovery, when you go to reboot, hold down Vol-Down and Power before it boots into the OS and it should load the new recovery. Had this problem myself earlier today, if you let it boot to the OS, it flashes back the CM recovery.
Click to expand...
Click to collapse
it works thank you...!!

Unbrickable tf300t

Hello everyone. I am new around here and totally new with android devices. I got my tf300t, installed twrp and flashed to the newest android version. Then my dad suddendly pressed something like restore to the manufactory setting and after that it rebooted and just keep booting with teamwin logo. I can not access twrp recovery mod, it is just in boot loop. I managed to get adb to work, but no fastboot since it does not boot into recovery mode. When I am in adb I can browse the device but the adb reboot bootloader does not work at all. It just hangs there. I can not power off the device because it does not let me, I can not boot into recovery mode with powerbutton and volume down button. After a long power button press it only reboots. I even tried with hard reset button but still the same. Could You please help me somehow? I really need that device for school and I would like to get back into the stock android. Thank you so much for any help.
//edit : I also forget to mention, when I execute adb deviced it shows:
List of devices attached
0123456789ABCDEF recovery
Also the device is unlocked.

Did you tried: adb reboot recovery ?
Did you tried to flash recovery again?
Be sure to use the right recovery for your bootloader. Did you upgraded bootloader to latest ASUS one? One then you're able to flash current recoveries like TWRP like 2.8.5.0 oder 2.8.7.0.
Edit: Also take a look here -> http://droidmodderx.com/prime/?page_id=74

Hello sir. Thank you for answering. I tried adb reboot recovery and it just hangs to be executed... But the tablet is still flashing the teamwin logo. I have the same bootloop as the guy on youtube called Francis Domingo and video called Samsung s5 stuck at TWRP Recovery boot loop (unfortunately I can not add link here).
//edit: Thank you for the link. It look like I have to use option 1a. Is it safe to use that command and I will not make it even more bricked? Thank you so much
//edit2: Now I just realized how to turn off the device to stop from rebooting. I just long pressed power button and up volume button and after the screen went black I kept holding the up volume button. I didn't work with down volume button or if I stopped holding the up volume button after black screen it rebooted again.
//edit3 : Let's say if I get to the twrp mode with option 1a from the link, what do I have to do next to get back to the stock rom (I think it was something like 4.0.3) ? Thank you

What the guy does in 1a is wiping mmcblk0p3.
Afaik mmcblk0p3 is the staging partition. That would be my guess anyway if you had access to fastboot. Usally when you can't boot into recovery, something is wrong in staging. I got the same problem 2 days ago. In this case you usually wipe staging partition via fastboot.
Since you got no fastboot access, you have to try with adb.
After cleaning the staging partition you can flash any recovery you want back again.
The recovery must be flashed to mmcblk0p4 <- 4!!! is the recovery partition. (but you should wipe mmcblk0p3 (3!!!) before)
So I would say, try what solution 1a suggests.
Edit: You can go back to stock android if you want, but there is no reason for this. My advice would be to unlock and root your device, upgrade to latest boot loader (which is done by upgrading to latest stock rom), then flash TWRP 2.8.5.0 and then a useful ROM on top. I'm using the one from timduru which is very nice. You can find it here: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783

Thank you for the answer. Could you please write a step by step to get out of brick and to get the stock version, because the newer one I installed was many times slower. The reason why I would like to have step by step is because I don't wanna mess it even more than it is. Thank you so much.
//the stock rom was much more faster than the one I have installed, I mean... the boot time wad unbelievable slow, same with responses and wifi problem. If there is any other faster rom than stock I would be happy but I don't wanna mess with any bugs or slow boot speed and I can not wait minutes until it boots.

Hm, try the Option 1a from the link.
If done, boot into current recovery. Tell me which version and which recovery do you have.
Top on this we can decide what to do to flash a good ROM.

I had the exact same thing happen to me yesterday. Option #1 worked for me.
I did the steps from option #1 and powered down using the volume up + power. I then tried to boot into TWRP recovery, which only reproduced the same issue.
I redid the option #1 steps, and this time powered down using the power + volume down. I powered back up normally, and it rebooted normally into the ROM.
The tablet now works normally, and I can also boot back into TWRP recovery with no issues.
Thanks for the thread and the link.

Thank you so much Catscratch! After I executed both command from option 1a I can get into the screen, where it shows three options: RCK, Android, Wipe Data
In the top left corner, there is written:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
The tablet can boot into the last ROM but as I said, I would like to have the faster and less buggy rom than this. When I open the settings and click about button there is written: CyanongenMod: 12.1-20150814-NIGHTLY-tf300t and Android version 5.1.1.
If I start RCK it just brings me back to the loop, but now I have fastboot available as it said above and I can list the fastboot devices on computer, which I couldn't before. Should I just execute this command from the computer "fastboot -i 0x0B05 flash system blob" and then "fastboot reboot" or should I download ROM from asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/ -> OS Android -> Firmware and now I don't know which should I choose: If JP or CN or WW or US or TW (Probably US right?). After that should I execute "fastboot -i 0x0B05 flash recovery firmware.img" and then "fastboot reboot" ? Or which ROM should I download to make it even faster and less buggy than stock ROM? Thank you so much again, You saved my tablet
//After I unzipped downloaded US ROM there is no img file. If I remember right the img file is only recovery to reflash the actual one and then when I start the twrp recovery I will select zip file with rom right?

OK, first of all to continue...I assume you got root access. (I think you should have, because you already got CM installed)
Next. Downloads.
Download: https://twrp.me/devices/asusTF300T.html
Also Download ROM+SuperSU: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
And GApps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Push all files to sdcard with "adp push" or in CM. Like you want.
Flash TWRP. (you can skip this step if you already got TWRP 2.8.5.0 or higher version). You don't need latest one.
fastboot -i 0x0b05 flash recovery twrp.img
fastboot reboot
- or -
adb reboot recovery
Now, go into recovery and wipe everything:
- cache
- dalvik
- system
- data
After that flash ZIPs from sdcard. (use "add more zips" option)
1. ROM
2. Gapps
3. SuperSU
Next: Wipe cache and dalvik again (only these two).
Reboot and wait. First boot can take some minutes.

Thank you so much again. Everything work perfectly The rom looks a lot faster than the older one I had there. No issues yet at all. Just awesome. Thank you so much. Really appreciate your kindness and help. You have a nice day !

Thanks. Have fun with your tf300.

Stuck in boot

Hi! My Oneplus One is stuck in boot (the oneplus logo).
I can get into fastboot but not recovery. I have followed some softbrick guides and the problem that I have is that even after flashing twrp as recovery I cant get into recovery. when I try to start it to recovery (volume up + power) I only get to the oneplus logo again. and when I use "fastboot boot twrp.img" the backlight comes on but the fastboot image stays, fastboot doesnt recognize it from this point so i have to restart it into fastboot mode again.
i have tried to flash the factory images, but nothing seems to change.
I dont know what to do, pls help..

After flashing recovery from fastboot, do NOT issue the reboot command. Press and hold the power button till phone powers off. If you issue the reboot command from fastboot, custom recovery will be lost. Also, don't know which twrp version you are trying to flash, but I would suggest flashing 2.8.6.0 first, then after you know you can get into recovery, you can flash another version.

Additionally, to boot to recovery you have to hold
volume down + power
volume up + power brings you to fastboot
Last but not least,
fastboot boot twrp.img
does not boot the recovery which is on your device, but the recovery image which is located inside your fastboot folder on your pc.

kenboyles72 said:
After flashing recovery from fastboot, do NOT issue the reboot command. Press and hold the power button till phone powers off. If you issue the reboot command from fastboot, custom recovery will be lost. Also, don't know which twrp version you are trying to flash, but I would suggest flashing 2.8.6.0 first, then after you know you can get into recovery, you can flash another version.
Click to expand...
Click to collapse
Ok, I did not know that the reboot command removes the custom recovery. Im almost certain that i've tried just powering down and trying recovery before too tho.
I was trying to flash twrp 3.0.0.0 so i'll try 2.8.6.0 asap
AcmE85 said:
Additionally, to boot to recovery you have to hold
volume down + power
volume up + power brings you to fastboot
Last but not least,
fastboot boot twrp.img
does not boot the recovery which is on your device, but the recovery image which is located inside your fastboot folder on your pc.
Click to expand...
Click to collapse
oops, i ofcourse ment that i try to get to recovery by volume down+power, and i know fastboot boot twrp.img boots from the .img on the computer, i just think its peculiar that nothing happens.

nothing has really happend after this, so i still need help.
summary: bump

I don't really get what you say. Perhaps i don't experiences before. @kenboyles72 is correct, official ROM may delete custom recovery (you can change the setting). Then @AcmE85 gives you an option, but it does not work.
Here is my option:
1. download any custom rom. The best idea is as minimum MB as possible. (Flash ROM directly from your PC)
2. flash your recovery, do NOT reboot. (fastboot flash recovery rec.img)
3. flash your ROM. (fastboot flash zip rom.zip)
Let's see if this would help you.

I had some issues a while back, where I was caught in a bootloop and flashing another rom. So I followed this guide, https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s . You can skip flashing the userdata.img to keep all data on sdcard. Also you can substitute flashing twrp recovery img for stock recovery. I myself went ahead and flashed all stock just to make sure everything booted correctly, then went into dev options and disabled update cm recovery, booted back to fastboot and flashed twrp 2.8.6.0. Evey thing worked like a charm.

Flasing stock rom did not affect anything noticeably.. phone is still stuck in boot/fastboot

Just to confirm, have you tried either/both of these:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

I have followed the return to stock guide, but not the unbrick, since my phone is softbricked, not hardbricked.
I have followed this guide tho, to no avail https://m.reddit.com/r/oneplus/wiki/devices/one/brickguide
the strange thing is that i didnt cause this. The phone started randomly overheating and one time it just never booted up.

Can't flash TWRP [Oxygen OS & OnePlus recovery]

I am on Oxygen OS (2.1.4) with OnePlus recovery and am trying to install TWRP recovery without any success.
I followed the fastboot method rather than the stupid toolkit
All the steps go through easily with success messages but every time after completion I boot into recovery, it still is OnePlus Recovery and not TWRP
Note - There's not option called "Update Cyanogen recovery" to uncheck under developer options because as I said, I'm on OnePlus Recovery
P.S - I have a Mac and followed the tutorial via terminal under the path ~/Library/Android/sdk/platform-tools

Nimsrules said:
I am on Oxygen OS (2.1.4) with OnePlus recovery and am trying to install TWRP recovery without any success.
I followed the fastboot method rather than the stupid toolkit
All the steps go through easily with success messages but every time after completion I boot into recovery, it still is OnePlus Recovery and not TWRP
Note - There's not option called "Update Cyanogen recovery" to uncheck under developer options because as I said, I'm on OnePlus Recovery
P.S - I have a Mac and followed the tutorial via terminal under the path ~/Library/Android/sdk/platform-tools
Click to expand...
Click to collapse
After it successfully flashes TWRP
Turn off the phone by long pressing button, do not fastboot reboot
Then use power button + volume up combo and it should boot to TWRP

Renosh said:
After it successfully flashes TWRP
Turn off the phone by long pressing button, do not fastboot reboot
Then use power button + volume up combo and it should boot to TWRP
Click to expand...
Click to collapse
I think you missed the entire premise. I'm not able to flash TWRP over the OnePlus Recovery in the first place let alone boot into it.

Nimsrules said:
I think you missed the entire premise. I'm not able to flash TWRP over the OnePlus Recovery in the first place let alone boot into it.
Click to expand...
Click to collapse
He was correct. Try that.

drmuruga said:
He was correct. Try that.
Click to expand...
Click to collapse
I'm afraid he wasn't. However, instead of keep trying to install TWRP, I simply booted into its image via
Code:
./fastboot boot recovery.img
and flashed Paranoid Android.

Nimsrules said:
I'm afraid he wasn't. However, instead of keep trying to install TWRP, I simply booted into its image via and flashed Paranoid Android.
Click to expand...
Click to collapse
You claimed all the steps went through successfully which can only mean you fastboot flashed TWRP (fastboot flash recovery recovery.img) and it showed success but if you reboot to recovery its still Oxygen recovery.
Your wording was misleading. My advise only applies if the flash was successful.

Do not reboot after flashing twrp, you have to shutdown, off the phone after flashing twrp...If you reboot, stock recovery will overwrite twrp..All you have to do is very simple, fastboot twrp, off the phone, enter twrp ( power + volume down) and done!...twrp will forever be your recovery..
Sent from my A0001 using Tapatalk

Did it worked?
Nimsrules said:
I'm afraid he wasn't. However, instead of keep trying to install TWRP, I simply booted into its image via
Code:
./fastboot boot recovery.img
and flashed Paranoid Android.
Click to expand...
Click to collapse
Did it worked? I'm in the same situation.
I own a Oneplus one with OxygenOs and I'm trying to change it to lineage but the new flashed TWRP is not showing up when entering at recovery mode.
Where did you enter the code? In your abd path by terminal or at the phone's path by x?

It works!
Renosh said:
After it successfully flashes TWRP
Turn off the phone by long pressing button, do not fastboot reboot
Then use power button + volume up combo and it should boot to TWRP
Click to expand...
Click to collapse
It works for me using volume down+power button. Thank you!