Database Info

Can't flash/access TWRP CM12.1/CM13

Hi there,
Yesterday I decided to upgrade from 5.1.1 (Sultan unofficial) to 6.0.1 (Sultan unofficial). :good:
Sh*t went down because I was running TWRP 2.8.6.1 and OP stated you must run 2.8.6.0.
So I got stuck into bootloot, hence I booted into recovery, put image of 2.8.6.0 into my phone and then flashed the img file through the appropriate menu.
Sh*t went down once again (And I'm not sure of why, but maybe because you cannot downgrade that way). Now I have a messed up recovery.
Well then, I get into fastboot, use Wugfresh's one-click-tool to flash back to 5.1.1. Everything goes well : my phone boots up :good:.
I disable update recovery with system updates in developers options (even though I am aware that this switch doesn't work on Lollipop)
Then I decide to root again and install TWRP 2.8.6.0 and the process fails : not that I get errors, but the command :
fastboot boot recovery.img
isn't doing its thing, hence I never boot into recovery
I'm quite surprised, but well I try to flash recovery :
fastboot flash recovery twrp-2.8.6.0.img
command executes without errors
I reboot into cm, try to boot into recovery and :
"Surprise Motherf*cker !" CM recovery shows.
I read that I must clear cache before (or after) flashing recovery
fastboot erase cache
Then shut the phone down holding Vol-down and power buttons and then boot into recovery holding Vol-down once again.
No luck, this time, every time I try to boot into recovery with this method, 1+ logo shows, phone vibrates, and 1+ logo shows etc. indefinitely
I abandoned... flashed 4.4.4 used wugfresh tool to root and flash twrp, then flashed marshmallow
Now I am rooted and running Marshmallow, but TWRP has been erased... Tried to flash through Flashify and Rashr, no luck.
(I disabled update cm recovery under developer settings)
Does someone understand why I don't manage to get TWRP under Android 5 and 6, and could explain me why ? :fingers-crossed:
Thank you !

debilausaure said:
Hi there,
Yesterday I decided to upgrade from 5.1.1 (Sultan unofficial) to 6.0.1 (Sultan unofficial). :good:
Sh*t went down because I was running TWRP 2.8.6.1 and OP stated you must run 2.8.6.0.
So I got stuck into bootloot, hence I booted into recovery, put image of 2.8.6.0 into my phone and then flashed the img file through the appropriate menu.
Sh*t went down once again (And I'm not sure of why, but maybe because you cannot downgrade that way). Now I have a messed up recovery.
Well then, I get into fastboot, use Wugfresh's one-click-tool to flash back to 5.1.1. Everything goes well : my phone boots up :good:.
I disable update recovery with system updates in developers options (even though I am aware that this switch doesn't work on Lollipop)
Then I decide to root again and install TWRP 2.8.6.0 and the process fails : not that I get errors, but the command :
fastboot boot recovery.img
isn't doing its thing, hence I never boot into recovery
I'm quite surprised, but well I try to flash recovery :
fastboot flash recovery twrp-2.8.6.0.img
command executes without errors
I reboot into cm, try to boot into recovery and :
"Surprise Motherf*cker !" CM recovery shows.
I read that I must clear cache before (or after) flashing recovery
fastboot erase cache
Then shut the phone down holding Vol-down and power buttons and then boot into recovery holding Vol-down once again.
No luck, this time, every time I try to boot into recovery with this method, 1+ logo shows, phone vibrates, and 1+ logo shows etc. indefinitely
I abandoned... flashed 4.4.4 used wugfresh tool to root and flash twrp, then flashed marshmallow
Now I am rooted and running Marshmallow, but TWRP has been erased... Tried to flash through Flashify and Rashr, no luck.
(I disabled update cm recovery under developer settings)
Does someone understand why I don't manage to get TWRP under Android 5 and 6, and could explain me why ? :fingers-crossed:
Thank you !
Click to expand...
Click to collapse
Normally when you flash TWRP via fastboot, if you boot to the OS it will replace your recovery so the workaround is to flash recovery via fastboot. Turn off phone via long pressing power button then volume down + power button and you should have TWRP. That's how I've always done it
Sent from my A0001 using Tapatalk

Renosh said:
Normally when you flash TWRP via fastboot, if you boot to the OS it will replace your recovery so the workaround is to flash recovery via fastboot. Turn off phone via long pressing power button then volume down + power button and you should have TWRP. That's how I've always done it
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thank you for your answer
As I mentionned, I have already tried the method you described, I just ran through the process again to confirm you this isn't working
The commands I used :
Code:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery twrp-2.8.6.0-bacon.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10180 KB)...
OKAY [ 0.313s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.469s
Then I unplug my phone, then long press power button, and when the phone is off I press power button + volume down
With this process 1+ logo shows up for 7~8 secs, then the phone vibrates and the screen goes dark, and then the 1+ logo shows up again indefinitely like there's no recovery to be found...
If I release vol-down, phone ends up booting system

Yuphoria stuck at YU LOGO while flashing Resurrection Remix 5.8.2

Hello Everyone
I use YU Yuphoria 5010 since more than a year with original cyanogenmod updated via updater to 12.1 without root and locked bootloader.
Since a month i have been facing force closure in many apps so i downloaded the cyanogenmod 12.1 reovery rom and did dirty flash via recovery solved settings app force closure but not all FC. Then I decided to clean flash a custom rom since cyanogenmod is closed now and also lineage and Yuos have no Volte support.
For this i read many posts forum properly unlocked my Yuphoria with Doomlord's method then rooted it and then flashed TWRP 3.0.0.0 on it and then did clean install of MIUI by Gaggu,and then Rohan successfully and used them but volte was not working. Then flashed stock rom by Yukick and everything (volte + vilte) was working fine exceptfor phone shutting down at 40% of battery.
Then decided for resurrection remix (5.8.1) and flashed it successfully. Tested it for three days some force closure were there also Vilte (not Volte) also not woking. Then saw a RR update (5.8.2) on resurrection remix download page for Yuphoria downloaded it and first time done a dirty flash (every previous flash was a clean flash this time I thought i am already on RR so no problem should be there).
There starts my problem the phone stuck at YU logo then tried to enter the Twrp recovery but could not. So flashed twrp via fastboot again and then wiped cache, delvik cache but no use could not start the phone. so tried to clean flash original cyanogenmod 12.1 rom ( that i used as for dirty flash many times to rectify some fc before) but could not.
Then read many threads on Yu forum and XDA forum and tried many things but no use.
Now the present condition is i can enter Fastboot mode by pressing vol up + power button with
cyanogen fastboot written on screen and can execute various fastoot commands but cannot flash rom as
Fastboot -i 0x2a96 flash system system.img
fail to write system.
I can't enter recovery with vol down + power button (after i entered the command Fastboot erase recovery previously i can enter the recovery by pressing vol down + power button, I did so to replace the TWRP with CWM recovery but no success) Phone starts YU logo appears for some time and then Blank screen.
But i can enter recovery via Fastboot with command
Fastboot -i 0x2a96 boot twrp_3.0.0.0_lettuce.img
but in twrp cannot mount system, data and cache partition tried various things like full wipe and repair file system change file system but no use. Twrp shows intenal storage 0 mb. also cannot flash other custom recovery if i try to flash other custom recovery via fastboot it says ok but cannot boot into recovery but when tried to enter via fastboot command phone enters in cyanogenmod recovery. it can also boot in recovery of Fastboot stock rom via fastboot command.
Fastboot -i 0x2a96 oem device-info
shows
device tampered false,
device unlocked true,
Charger screen enabled true.
I can lock the bootloader also by command
Fastbbot -i 0x2a96 oem lock
then device-info shows
device unlocked false
(without bootloader restart if restarted it shows device
unlocked true).
when enetered in TWRP 3.0.0.0 via fastboot command the phone is also shown as MTP device in Windows but only memory card is shown as storage no internal storage.
if i try to start the phone by pressing power button it stucks at YU logo.
if i connect the phone to computer while it is poweroff it is shown as Android Phone (Android
bootloader interface) in Device manager on my windows 7 laptop.
any other information or screen shot if needed I will provide.
Thanks in advance

For me also same error, possibly because of Flash memory life cycle end.

Honor 4C Fastboot Flash OK But nothing changes

Hi guys, I have an Honour 4C wich reading through forums i managed to update it to most recent AOKP 7.1.2 version (https://forum.xda-developers.com/p8lite/development/rom-t3717536) for P8Lite Alice and everything was ok.
I can recall some years ago I had to change my model from CHC-U01 to CMH-U01 to update to 6.0 if my memory is right and recently flashed P8 Lite firmware (B896) in order to flash AOKP and device was running without problems.
I was running my phone in performance governor for gaming , forgot turn it off, My phone complety run out of battery while asleep i woke up put it to charge.
It charged a little and after it powered on by itself bootlooping into OS.
I'm now facing a bootloop, phone auto turns on when charging and bootloops.
If I enter fastboot and exit into a shutdown its stays charging ok. (Just to turn on by itself at some point)
PC detects fastboot just fine and I can fastboot, however, no matter what I Flash i can't get sytem to boot up properly NOR can i boot TWRP recovery.
I flash twrp into recovery, IT says it was flashed OK but when i boot into recovery it just open that EMUI menu with reboot into system , wipe cache/ and system restore (wich takes 1sec , says system restored but it doesnt).
I've tried to flash B896_Update.zip used HuaweiUpdateExtractor and flashed BOOT RECOVERY AND SYSTEM OK , but again, no changes... it boots into AOKP Logo when it should boot into Huawei logo if any changes took efect.
If boot into fastboot and press KeyvolumeUP, other eRecovery EMUI appears now with restart , wifi update and shutdown.
When I try this Wifi method it bootloops right after it says connecting..
Also I can't do a fastboot erase (cache...userdata..any) because it gives FAILED (remote: Command not allowed) ... my bootloader is UNLOCKED and command prompt is running in administrator mode.
Same happens if i try to run fastboot boot twrp_Recovery.img , download OK but FAILED remote: Command not allowed.
I have no way to do an ADB sideload and try to go from that because system doesnt boot.
Is it just HardBricked even so I can boot into bootloader and fastboot?
It is driving me crazy it feels like fastboot just "fake flashes" or something . Nothing takes effect ....

Fastboot Flashes but dont doesn't persist.

Hi guys, I have an Honour 4C wich reading through forums i managed to update it to most recent AOKP 7.1.2 version (https://forum.xda-developers.com/p8l...t/rom-t3717536) for P8Lite Alice and everything was ok.
I can recall some years ago I had to change my model from CHC-U01 to CMH-U01 to update to 6.0 if my memory is right and recently flashed P8 Lite firmware (B896) in order to flash AOKP and device was running without problems.
I was running my phone in performance governor for gaming , forgot turn it off, My phone complety run out of battery while asleep i woke up put it to charge.
It charged a little and after it powered on by itself bootlooping into OS.
I'm now facing a bootloop, phone auto turns on when charging and bootloops.
If I enter fastboot and exit into a shutdown its stays charging ok. (Just to turn on by itself at some point)
PC detects fastboot just fine and I can fastboot, however, no matter what I Flash i can't get sytem to boot up properly NOR can i boot TWRP recovery.
I flash twrp into recovery, IT says it was flashed OK but when i boot into recovery it just open that EMUI menu with reboot into system , wipe cache/ and system restore (wich takes 1sec , says system restored but it doesnt).
I've tried to flash B896_Update.zip used HuaweiUpdateExtractor and flashed BOOT RECOVERY AND SYSTEM OK , but again, no changes... it boots into AOKP Logo when it should boot into Huawei logo if any changes took efect.
If boot into fastboot and press KeyvolumeUP, other eRecovery EMUI appears now with restart , wifi update and shutdown.
When I try this Wifi method it bootloops right after it says connecting..
Also I can't do a fastboot erase (cache...userdata..any) because it gives FAILED (remote: Command not allowed) ... my bootloader is UNLOCKED and command prompt is running in administrator mode.
Same happens if i try to run fastboot boot twrp_Recovery.img , download OK but FAILED remote: Command not allowed.
I have no way to do an ADB sideload and try to go from that because system doesnt boot.
Is it just HardBricked even so I can boot into bootloader and fastboot?
It is driving me crazy it feels like fastboot just "fake flashes" or something . Nothing takes effect ....

Hi Korreya,
Once I to had ended up in a boot loop when I had messed up during twrp (that was 1st time I had tried flashing it into a phone).
I eventually tried many methods, few of which you have also mentioned, and finally succeeded but I exactly don't remember what I had did so I'm not sure if this works.
Download the stock Honor4C ROM (I'm not able to post the link so you could just Google it) and copy the file named UPDATE.APP into a folder named "dload" (without the " , if there's no such folder just create one) on your SD card and then try going into the eRecovery EMUI and updating the system.
PS: Note that this would install the official stock ROM on the device.
Try it and do let me know if that helps.
Peace

Redmi Note 11 bootloop after custom ROM install

Hi, this is my first post in XDA, so sorry if I'm posting in the wrong section.
I recently got a Redmi Note 11 and today I was going to install KomodoOS in it. I did as follows:
First thing I did was to unlock the bootloader, which seems to have worked fine (I can see the open lock icon alongside the Mi logo when it powers on).
I then flashed TWRP (from here https://www.getdroidtips.com/twrp-recovery-redmi-note-11/). When I first tried the command fastboot flash recovery_a twrp.img, I got an error telling me that recovery_a_a doesn't exist, same for recovery_b (which gave me error that partition recovery_b_a didn't exist). I found on Google I could boot into twrp (fastboot boot twrp.img) and then flash twrp itself (Advanced->Flash recovery), which I did and got no error messages. I booted up the system just normal, rebooted into recovery by issuing adb reboot recovery and it got me back into TWRP. So it seems it was installed successfully.
Lastly, while the phone was on TWRP I copied the rom file into the root directory with adb push komodo-version.zip komodo.zip, clicked on Install, selected komodo.zip then confirmed the installation. It took a few minutes (file is 1.3GB) and it completed with a few errors, but at the top there was the message Install successful.
Then I wiped Dalvik and rebooted the system, but now I'm stuck at a bootloop where it goes to the "No command" screen and reboots. I tried holding volume up+power and volume up while reconnecting the USB but to no avail, can't seem to get out of the loop. Also tried spamming adb devices and fastboot devices on pc but can't connect to the phone.
I'm now a bit desperate, since there's (surprisingly?) not much about this phone out there, and I don't know anything that could be done. Is there still hope?
Links/tutorials I used:
Download and Install AOSP Android 12 on Xiaomi Redmi Note 11
Xiaomi Redmi Note 11 launched in January 2022. The handset came with Android 11. In this tutorial, we will guide you to install Android 12 Custom ROM on
www.getdroidtips.com
Download TWRP Recovery for Xiaomi Redmi Note 11 | Root Using It
On this page, we will guide you to install the TWRP Recovery on Xiaomi Redmi Note 11 (spes). This guide contains both the written instruction and a video
www.getdroidtips.com
[4 Methods] How to Fix TWRP Error: FAILED (remote: No such partition)
In this guide, we will show you four different methods to fix the FAILED (remote: No such partition) error while flashing the TWRP Recovery.
www.droidwin.com

Draining battery and directly going into fastboot as soon as plugging in works or not?

.

dont trust getdroidtip , search rom on xda instead

In Shaomi "No Command" error means system partition has been destroyed. You most likely need to Reflash MIUI using >Mi Flash Tool<.
So your issue is that you cant boot into TWRP? Also, have you tried Power + Vol(-) to get into Fastboot mode. You can also try PC softwares like >Reiboot-For-Android.exe< to boot to recovery or bootloader.
>If you have TWRP no need to use ADB push, just use USB OTG to flash ZIP<