Hi all, I have through fastboot flashed a TWRP recovery to my Xperia Z5. But, It doesn't work. When I try to boot into recovery I just get a black screen with a blue LED at the top. I have tried also using adb to reboot into recovery but still no luck. It just boots into the OS. Any idea? Cheers
BlurredXDA said:
Hi all, I have through fastboot flashed a TWRP recovery to my Xperia Z5. But, It doesn't work. When I try to boot into recovery I just get a black screen with a blue LED at the top. I have tried also using adb to reboot into recovery but still no luck. It just boots into the OS. Any idea? Cheers
Click to expand...
Click to collapse
Bootloader Unlocked?
TWRP flashed to recovery partition?
Did you try patched kernel?
Built in patched kernel has TWRP, no need to flash TWRP separately.
https://forum.xda-developers.com/xperia-z5/general/ftf-e6603-33-53-83-google-drive-patched-t3581463
sceryavuz said:
Bootloader Unlocked?
TWRP flashed to recovery partition?
Did you try patched kernel?
Built in patched kernel has TWRP, no need to flash TWRP separately.
https://forum.xda-developers.com/xperia-z5/general/ftf-e6603-33-53-83-google-drive-patched-t3581463
Click to expand...
Click to collapse
So am I just meant to flash boot_E66xx_no_TWRP.img using fastboot flash boot and then the recovery should work?
BlurredXDA said:
So am I just meant to flash boot_E66xx_no_TWRP.img using fastboot flash boot and then the recovery should work?
Click to expand...
Click to collapse
no twrp for TWRP 3.1.0 (need flash recovery)
with twrp for TWRP 3.0.2 (built in, no need flash recovery)
Related
Hey there guys. I have recently flashed CWM-touch-6.0.4.7-falcon.img im able to go into recovery when i flash it, on reboot i selected yes for the fix install stock recovery, when back to recovery and it has an android with an exclamation mark coming out of it with it saying 'no command' at the bottom. How do i fix this? Moto G 3G 1st gen
You can try:
Code:
fastboot erase recovery
And then:
Code:
fastboot flash recovery recoveryname.img
After you flash the custom recovery boot into it right away and see if that works.
.:Dark:. said:
You can try:
Code:
fastboot erase recovery
And then:
Code:
fastboot flash recovery recoveryname.img
After you flash the custom recovery boot into it right away and see if that works.
Click to expand...
Click to collapse
I did that and it was all success but same thing happened
Also i tried flashing stock recovery but still no luck
An Android with an exclamation with 'no command' means you are on the stock recovery. Did you try the latest TWRP?
legolas06 said:
An Android with an exclamation with 'no command' means you are on the stock recovery. Did you try the latest TWRP?
Click to expand...
Click to collapse
Oh right ok. No i haven't used TWRP, i don't really like it. I tried CWM touch but i haven't tried normal CWM yet
You can also try philz recovery. Not sure why it won't stick after you flash but be sure go into recovery right after you finish flashing otherwise it will overwrite back to stock I believe.
.:Dark:. said:
You can also try philz recovery. Not sure why it won't stick after you flash but be sure go into recovery right after you finish flashing otherwise it will overwrite back to stock I believe.
Click to expand...
Click to collapse
I always go straight into recovery after i flash it but when i reboot it goes back to stock recovery :/
What message do you get after flashing the recovery? Previously I got 'partition size mismatch' indicating I flashed a recovery different from stock. Philz & TWRP worked fine for me.
legolas06 said:
What message do you get after flashing the recovery? Previously I got 'partition size mismatch' indicating I flashed a recovery different from stock. Philz & TWRP worked fine for me.
Click to expand...
Click to collapse
I forget, ill check it tomorrow as today i am a bit busy
I get a mismatch partition size (recovery) when i flash. I boot straight away to recovery, then say yes to disable flash stock recovery, reboot into recovery and stock recovery. I flashed the non touch CWM this time
bublz654 said:
I get a mismatch partition size (recovery) when i flash. I boot straight away to recovery, then say yes to disable flash stock recovery, reboot into recovery and stock recovery. I flashed the non touch CWM this time
Click to expand...
Click to collapse
Then sorry I'm not sure about the reason. May be you downloaded a wrong recovery or that recovery doesn't work with your bootloader. Just search the thread you downloaded this from to find any solution. Or if you don't like the TWRP try Philz touch as it is CWM based.
http://forum.xda-developers.com/showthread.php?t=2639583 .
Currently the only supported recovery for moto g is TWRP by h2o64.
legolas06 said:
Then sorry I'm not sure about the reason. May be you downloaded a wrong recovery or that recovery doesn't work with your bootloader. Just search the thread you downloaded this from to find any solution. Or if you don't like the TWRP try Philz touch as it is CWM based.
http://forum.xda-developers.com/showthread.php?t=2639583 .
Currently the only supported recovery for moto g is TWRP by h2o64.
Click to expand...
Click to collapse
I have flashed CWM-touch and normal CWM before until flashify came along and made my recovery screwed up
I suggest you try using mfastboot included here: https://www.androidfilehost.com/?fid=23578570567719065
NOTE: mfastboot erase recovery is not required. Simply use: mfastboot flash recovery recovery.img
lost101 said:
I suggest you try using mfastboot included here: https://www.androidfilehost.com/?fid=23578570567719065
NOTE: mfastboot erase recovery is not required. Simply use: mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
I just tried that and still the same issue occurs
bublz654 said:
I just tried that and still the same issue occurs
Click to expand...
Click to collapse
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
lost101 said:
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I'll try the philz recovery first as Im not a real big fan of twrp lol
lost101 said:
Could you try the latest TWRP just to rule out a bad recovery.img: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I flashed philz recovery. Rebooted again and went into recovery and it worked, the recovery was still there
But one more thing on reboot of recovery it didn't ask if i wanted to fix root. Am i rooted already or not? :/
Are you on stock or a custom rom? Certain custom roms may have built in root access for everything else you will have to flash SuperSU.
Glad to see you got the recovery issue sorted. I'm with you I don't particularly like TWRP so I pretty much use Philz exclusively.
Hi can someone help me
I fastboot installed twrp when I try to reboot to recovery I get a no command and tried the power and volume up but takes to me to stock recovery.
I flashed elemental kernel after install does that wipe twrp or something?
Using Magisk as well
did you do fastboot boot twrp.img and then flash the zip in twrp or did you just try to flash the image file using fastboot flash recovery twrp.zip?
r29 said:
Hi can someone help me
I fastboot installed twrp when I try to reboot to recovery I get a no command and tried the power and volume up but takes to me to stock recovery.
I flashed elemental kernel after install does that wipe twrp or something?
Click to expand...
Click to collapse
You need to fastboot boot twrp image, install twrp-pixel-installer-sailfish-3.0.2-0-RC1, reboot recovery, if you want root, then install SuperSU, reboot.
Tulsadiver said:
You need to fastboot boot twrp image, install twrp-pixel-installer-sailfish-3.0.2-0-RC1, reboot recovery, if you want root, then install SuperSU, reboot.
Click to expand...
Click to collapse
exad said:
did you do fastboot boot twrp.img and then flash the zip in twrp or did you just try to flash the image file using fastboot flash recovery twrp.zip?
Click to expand...
Click to collapse
Thanks for the help problem solved
I was reboot system after fastboot boot twrp.img and installing zip so it didnt give me the option to allow modification
Hello
I just installed Lineage, and it worked, installed it via fastboot boot recovery...
After installation, I wanted to install the recovery too, so i run the command fastboot flash recovery
Then I try it, and it's working. TWRP 3.0.2.0.
But, after reboot, it's booting directly to TWRP. Again and again. can't boot normally to system...
Anyone have a solution ?
Thank you
b-tzu said:
Hello
I just installed Lineage, and it worked, installed it via fastboot boot recovery...
After installation, I wanted to install the recovery too, so i run the command fastboot flash recovery
Then I try it, and it's working. TWRP 3.0.2.0.
But, after reboot, it's booting directly to TWRP. Again and again. can't boot normally to system...
Anyone have a solution ?
Thank you
Click to expand...
Click to collapse
It has to be done in this order:
fastboot flash twrp.img
boot TWRP
install LOS zip
Detailed instructions https://wiki.lineageos.org/devices/libra/install
Hello
Thank you for the answer
I tried tout reinstall all after my bug, just that way and still boot on recovery...
So now how to do this proper way ?
Try using newer version of TWRP.
[Deleted]
The flashing instruction makes no sense to me
Spookybear said:
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to your custom TWRP-based Recovery
2. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
3. Enjoy!
(Note: There is no zip file because this recovery is too big to fit in the ramdisk.
Click to expand...
Click to collapse
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
gorilla p said:
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
Click to expand...
Click to collapse
I tried that...no dice...
Flash to both _a and _b using trwp but recovery does not boot... so back to trwp til some future info...
I flashed via TWRP, via flash .img to ramdisk, rebooted to recovery and nothing.
Stuck at "Bootloader unlocked" screen
Tried to boot via fastboot and it failed.
Was this recovery tested on the OP7 Pro? If so, what ROM was being used and what was the flashing process?
Gungrave223 said:
The flashing instruction makes no sense to me
Click to expand...
Click to collapse
Sorry, fixed the instructions.
avid_droid said:
Yeah directions are honestly the worst I've seen on XDA yet.
Click to expand...
Click to collapse
Sorry, fixed the instructions.
I have a feeling these new instructions aren't going to work either, considering we don't have a recovery partition.
Spookybear said:
Sorry, fixed the instructions.
Click to expand...
Click to collapse
still no dice
HTML:
Writing 'recovery'
FAILED (remote: '(recovery_a)
No such partition'
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
insaneparnoid said:
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
Click to expand...
Click to collapse
He updated it with fastboot flash, indicating that this is to be installed, however it doesn't appear to work at all at this point.
For me is working , latest OOS beta. Just had to disable vbmeta in order to boot.
we need a flashble zip for this.
is OTG working with OrangeFox ?
otakutw said:
we need a flashble zip for this.
Click to expand...
Click to collapse
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Can this recovery be decreased in size so that it can be flashed to the ramdisk?
EDIT: It seems twrp is even bigger than this. Twrp img is 30.7mb while this is 29.4mb. Twrp does flash to the ramdisk. If this could be permanently flashed, it would be perfect. If the size needs to be decreased, certain graphics could be moved to the internal storage to save space on the ramdisk.
Hahaha wow what are you doing here it's like you didn't even test this at all. I'm tried to flash the installer in twrp and it tells me that this recovery is only for guacamole not OnePlus 7 pro. So it does not support custom roms clearly cause I'm on bliss
shadowikr said:
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Click to expand...
Click to collapse
There is no recovery partition on modern Android devices. The boot.img ramdisk contains the recovery
Hello,
I have unlocked my bootloader successfully.
When i try to flash recoveries:
TWRP-3.5.1-vayu-Nebrassy-1.img
PBRP-vayu-20210407-test-UNOFFICIAL.img
twrp-3.5.1_10-0-vayu-Nebrassy.img
OrangeFox-R11.0_5-Unofficial-vayu.img
The fastboot command is successfull, no errors whatsoever.
But when try to boot to recovery by vol up + power, i get to the fastboot screen only.
and fastboot boot recovery.img also does not boot to the recovery, rather just boots me to MIUI.
When i do a adb reboot recovery from within miui, i go to miui recovery.
So surely the recovery isint flashing.
Has anyone faced such issue?
Thanks.
Oh my goodness..
I was doing this on a windows m/c since the miflash is windows application.
I switched to linux, and flashing works.. i am on TWRP!
It will flash if you flash custom recovery. However, it will change the custom recovery back to Mi-recovery every time after booting, if your system is stock MIUI.
TWRP works better if you use
fastboot boot twrp.img
Click to expand...
Click to collapse
If you are flashing roms on bhima, don't use TWRP.
Use OrangeFox.
fastboot boot OrangeFox-R11.0_5-Unofficial-vayu.img
Click to expand...
Click to collapse