Database Users

[Q] TWRP: "custom recovery" not working anymore, TWRP not starting

Hi there,
I wanted to install latest CM10.1 coming from 0526 yesterday on my Defy+.
Did a backup with TWRP first.
Then the flashing failed, so I wanted to recover from backup.
Phone now is stuck at Motorola M not booting anymore.
When I enter bootloader (vol down) and want to enter "custom recover" he just jumps back to the same menu. TWRP is not starting.
Choosing "stock recovery" is possible, but if I choose a CM10.1 zip file it's not accepted.
RSD Lite does not recognize the phone when it's in the bootloader menu or in the stock recover menu.
Help is very much appreciated, what can I do?
Thanks and best regards.

are edianKa
[Idiot mode=on]
Okay, I found out why I couldn't enter flash mode by using Vol+ when starting.
The phone powered already up when I put in the battery, so I always pushed Vol+ too late.
Pressing Vol+ WHILE inserting the battery did the trick, phone went into flash mode and I could re-flash 2.3.6 sbf using RSD lite.
[Idiot mode=off]
Still not sure why TWRP was messed up just by recovering from a TWRP-made backup...
Best regards

Same situation to me.
I opened Terminal Emulator, gained root access
then type below command to get recovery mode
# reboot recovery

Custom recovery not running
I have a similar issue.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw

Can't boot into recovery using vol down+power but can boot normally

Hi,
I can't boot into recovery using vol down+power but I can boot normally into OS and from there I can boot into recovery through ADB or third party apps.
I was trying to update my OP2 with new OxygenOS 3.0.2. As my device was rooted so I had to do it manually using TWRP. Till now I was able to boot into recovery by vol down+power.
Before flashing I wiped everything(dalvik+cache+system+data), rebooted into recovery and flashed the OOS3.0.2 full ROM. At this point the installation was successfull but I was not able to boot the OS, it was stuck on the loading screen. After several attempts to boot OS, I finally tried to boot into recovery to flash again, but I was unable to. When I press vol down+power for few sec, the phone switches off with a vibration.
Later I found out that I was supposed to use a modified TWRP. So I flashed the modified TWRP via fastboot and flashed the OOS3.0.2 full ROM again, Now I can boot into OS normally but still I cannot boot into recovery by vol down+power. But the interesting thing is that I can boot into recovery through ADB or third party apps.
I tried flashing the TWRP recovery again with no luck. I thought this could be a problem with boot.img which is contained in ROM itself so I also flashed the ROM again with no luck. Also I am absolutely sure that this is not a hardware issue with by volume buttons as I can use them properly when I boot into OS.
A quick thought, is it possible that the boot.img of the ROM itself is broken? Seems unlikely as I am not seeing anyone else having this issue. But if it is, is it ok to flash the boot.img from OOS2.x version ROM, will that be compatible? Just wanted to be sure before doing this.
Any other thoughts are welcome.

Are you used this command for flashing twrp??
fastboot flash recovery recovery.img
You should add "flash", otherwise it won't install twrp in your mobile

yes I used that command only

Dreckk said:
yes I used that command only
Click to expand...
Click to collapse
After flash recovery use this command it will help to boot in twrp "fastboot boot recovery.img " without quotes

yes I know that, thats how I booted into recovery from fastboot for flashing the ROM. But I should be able to boot into recovery by vol down+power. That is why I posted this question.

Will you please send me screenshot of cmd?? after flash recover

a6000 shut down during MIUI flash, won't boot into recovery

Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?

Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.

Lenovo A6000 plus on DU with a peculiar problem!!!

First of all, i'm a noob so please don't mind any technical mistakes.
I recently flashed RR on my device with TWRP, and all was working quite fine.
But then, I decided to try out DU, and flashed it. But my phone was stuck on the lock screen with a "com.android.phone stopped working" message.
I used ADB to wipe my data ( for if there were any conflicts) using : fastboot -w
My phone now is working fine, But i've lost root access, My phone DOESN"T BOOT INTO RECOVERY.. Holding vol+ and power just ends up in a screen with the RR logo( yes RR, even after flashing DU).
I've tried to flash TWRP using ADB again but it's not working.
ROM manager says I've got TWRP and CWM installed.
Also Kingo and Framaroot aren't working.
I would really want to get back:
1.Root access
2.TWRP
Some help will really be appreciated....

Press vol up+down and power button simultaneously, to access recovery.

I've tried that, my phone just shows the RR logo screen and nothing else.

Alternate method
dude you just need a pc with adb driver installed then go to bootloader mode by pressing vol- and power button, then using adb command write (fastboot boot recovery.img).
Here recovery.img is ur twrp recovery or other,then it will flash recovery.img in ur phone and automatically go into the (twrp) recovery.
(u need to copy recovery.img in ur adb folder before u write that command)

I have done that... It does flash twrp onto my phone..but my still doesnt boot into twrp...

then use another recovery, sevenmax twrp recovery is the best.

cant get into download mode?only recovery mode works!!cant use ADB as it has no OS so

cant get into download mode?only recovery mode works!!cant use ADB as it has no OS so cant on USB debugg mode...tried flashing custom recoveries but says signature error!!tried CWM/TWRP doesn't work tried samsung 300k tool also says purgecomm function failed error 5...plz help stuck on recovery mode only and i want to flash stock rom

Holding Volume down and power should get you to the OS Warning screen, then a quick volume up press should get you to download mode. Those are very deliberate actions, and the fact ONLY your recovery works plus the fact you cannot install custom recoveries to your device tells me your S4 is a counterfeit chinaphone.
On the flip side, you need Odin to install a custom recovery, not the tool you mentioned. Some more detail from you might be helpful, such as where you got the phone from.