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)

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

How to enter Recovery mode?

Hey, using the xperia m2, with lollipop 5.1.1 (18.6.A.0.182) and i cannot get into recovery mode.
i have unlocked the boot loader, and i have rooted the device, but no combination of any button presses will allow me to get into whatever recovery i have.
i have also got the mac versions of adb and fast boot, and flashed twrm / mutirecovery to the phone, all with confirmations that they have installed, but recovery simply doesn't load up!
helps!
Kelvins-MBP:android kelvinmead$ adb devices
List of devices attached
ZH80051094 device
Kelvins-MBP:android kelvinmead$ fastboot flash recovery /Users/kelvinmead/Downloads/android/RECOVERY-TWRP-3.0.2-D230X_D240X.img
< waiting for any device >
target didn't report max-download-size
sending 'recovery' (12498 KB)...
OKAY [ 0.395s]
writing 'recovery'...
OKAY [ 1.441s]
finished. total time: 1.836s

bootloader already updated before installing TWRP (not multirecovery)?
Hold volume (-) , then press power button & hold of both, after appearing Sony logo release the volume button but keep holding power button.

You may try using Quick Reboot app (Download from play store)
Sent from my Pixel using XDA-Developers Legacy app

FunSucker said:
bootloader already updated before installing TWRP (not multirecovery)?
Hold volume (-) , then press power button & hold of both, after appearing Sony logo release the volume button but keep holding power button.
Click to expand...
Click to collapse
bootloader was unlocked first so i could root. after root, i tried to install twrp, this is when i tried to get into recovery.
the sequence here, boots as normal and then does the android is starting, application optimising.

iamkevinhuang said:
You may try using Quick Reboot app (Download from play store)
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
there are about 100 apps with this description, and I've tried about 5 of them. all that I've tried just reboot the phone and pop into regular mode.

KelvinMead said:
bootloader was unlocked first so i could root. after root, i tried to install twrp, this is when i tried to get into recovery.
the sequence here, boots as normal and then does the android is starting, application optimising.
Click to expand...
Click to collapse
I asked to you about UPDATING bootloader, not UNLOCKING sir. If you want to install TWRP v3, you should updated your bootloader too..
Sorry for my bad english.

FunSucker said:
I asked to you about UPDATING bootloader, not UNLOCKING sir. If you want to install TWRP v3, you should updated your bootloader too..
Sorry for my bad english.
Click to expand...
Click to collapse
not your bad english, i missed the word upgrade. I'm not sure what boot loader i was running, but I've managed to upgrade (after downgrading flash tool!) and I'm running boot loader 1.716.
twrp can now be installed?

KelvinMead said:
not your bad english, i missed the word upgrade. I'm not sure what boot loader i was running, but I've managed to upgrade (after downgrading flash tool!) and I'm running boot loader 1.716.
twrp can now be installed?
Click to expand...
Click to collapse
OMG OMG OMG!!!! https://forum.xda-developers.com/xperia-m2/development/ubl-xperia-m2-bootloader-update-ftfs-t3288148
and i have the large sony logo (instead of the smaller version) and i can enter recovery!
UPGRADE! such a small word to miss!

KelvinMead said:
OMG OMG OMG!!!! https://forum.xda-developers.com/xperia-m2/development/ubl-xperia-m2-bootloader-update-ftfs-t3288148
and i have the large sony logo (instead of the smaller version) and i can enter recovery!
UPGRADE! such a small word to miss!
Click to expand...
Click to collapse
Thats what i mean

[GUIDE][RECOVERY][Z010D][Z010DD]How to install TWRP Recovery

Disclaimer
Code:
/*
*
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or recoverys, kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
*
*/
GUIDE OF HOW TO INSTALL TWRP RECOVERY ON ZENFONE MAX (Z010D & Z010DD)​1º Step:
- You need an Unlocked Bootloader:
- for SD410 (MSM8916/Z100D).
- for SD615 (MSM8939/Z10DD).
2º Step:
- You need minimal adb fastboot.
3º Step:
- You need to download TWRP Recovery:
- for SD410 (MSM8916/Z010D).
- for SD615 (MSM8939/Z100DD).
Put the recovery on the folder of minimal adb fastboot and rename it to recovery.
4º Step:
Run the Minimal Adb and Fastboot as adminstrator.
5º Step:
Go to Bootloader (CSC MODE) mode on your phone (Press and HOLD Volume Up Key+Power Key) enter the following commands:
Code:
[SIZE="2"]fastboot devices[/SIZE]
If you see a serial then you are you ready to flash the recovery to flash you need to do the follow command:
Code:
[SIZE="2"]fastboot flash recovery recovery.img[/SIZE]
6º Step:
After flashing the TWRP recovery, you should boot directly into recovery by holding Volume Down+Power Button do not allow device to boot into the stock rom at first boot, otherwise stock recovery will be restored!
Credits:
To the developers!

Reserved

shirofficial said:
After flashing the TWRP recovery, you should boot directly into recovery by holding Volume Down+Power Button do not allow device to boot into the stock rom at first boot, otherwise stock recovery will be restored!
Click to expand...
Click to collapse
So what to do after I booted into Recovery first. Can I go back to stock rom afterwards?

Sayan44 said:
So what to do after I booted into Recovery first. Can I go back to stock rom afterwards?
Click to expand...
Click to collapse
Yes you can. :good:

bro my device is asus zenfone max asus z010d snapdragon 410 version
https://androidfilehost.com/?fid=745849072291687209
is the above linked recovery correct for my device??

krishna8691 said:
bro my device is asus zenfone max asus z010d snapdragon 410 version
https://androidfilehost.com/?fid=745849072291687209
is the above linked recovery correct for my device??
Click to expand...
Click to collapse
Yes it is :good:

I have already rooted can i just flash the recovery through app

hi sir.. i just wanna adk the solution for the error 404? i can't install the twrp in my unit.. what i need to do? the adb can't detect my phone..

shirofficial said:
Yes it is :good:
Click to expand...
Click to collapse
Hi bro I am tharun twrp is not installing properly in my ASUS...what to do for that?

Hy Sir
After Twrp Flash
When I try to boot into Twrp ,phone freezes at Asus logo & next time when I try to boot into Twrp by restarting boots into stock recovery
Tried a lot of time ,did lot's of attempts
Please help me

Hello can anyone please help me,
I followed every thing but it's asking for password when I boot into recovery then press cancel and wipe the phone (factory reset). Via twrp as I saw in one website but next time when I reboot it's I "Qualcomm diagnostic mode 9006" please help me to come out of this it's my friend phone
Thank you

how do I boot into recovery from CSC mose ..power up + vol. down donot lead anywhere ..lomg pressing power buttton results in rebooot

I cant go to twrp after done flash img from adb
After done flash twrp img file through adb on asus z010d by pressing vol up and power key i cant go to twrp . My screen goes of the exact time twrp open. What should i do?
Anybody help me please
My watsapp number is
+917012088399

Is it necessary to root the device first before flashing twrp ?
Because as I flashed twrp image, and then booted firstly into it, and when I tried to reboot my device in stock ROM, it got stuck in Asus logo, I can't start my device anymore ... Please help devs

I have an error
adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (18036 KB)...
OKAY [ 0.570s]
writing 'recovery'...
FAILED (remote: can't flash unsigned image)
finished. total time: 0.731s
i don't know what to do, please..

tuananhtd09 said:
I have an error
adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (18036 KB)...
OKAY [ 0.570s]
writing 'recovery'...
FAILED (remote: can't flash unsigned image)
finished. total time: 0.731s
i don't know what to do, please..
Click to expand...
Click to collapse
This is probably because you didn't do step one first. Step one unlocks the bootloader so you shouldn't receive this error when you try to flash recovery. If you can't do step one because android is out of date then you need to update android first. If you can't update android then welcome to the club, you probably have a cn recovery and need to update to ww. This can be down following these instructions assuming you have a z010d/sd410/8916 https://ainotech.com/how-to-flash-firmware-asus-zenfone-max-zc550kl-root-custom-twrp-recovery/ Follow the instructions for AFT.
However now I'm stuck on the bit everyone else is stuck on. Once TWRP is flashed, how to boot directly to that instead of android first??
EDIT: I figured it out. It's because this build of twrp 3.2 and even 3.1 is broken for this device. Flashing twrp 3.0 works fine but of course that doesn't support many modern custom roms so it doesn't really help.

Sharft 6 said:
This is probably because you didn't do step one first. Step one unlocks the bootloader so you shouldn't receive this error when you try to flash recovery. If you can't do step one because android is out of date then you need to update android first. If you can't update android then welcome to the club, you probably have a cn recovery and need to update to ww. This can be down following these instructions assuming you have a z010d/sd410/8916 https://ainotech.com/how-to-flash-firmware-asus-zenfone-max-zc550kl-root-custom-twrp-recovery/ Follow the instructions for AFT.
However now I'm stuck on the bit everyone else is stuck on. Once TWRP is flashed, how to boot directly to that instead of android first??
EDIT: I figured it out. It's because this build of twrp 3.2 and even 3.1 is broken for this device. Flashing twrp 3.0 works fine but of course that doesn't support many modern custom roms so it doesn't really help.
Click to expand...
Click to collapse
oh, thanks. because i didn't do step one first
and now i had a problem bigger @@
https://forum.xda-developers.com/as...ow-to-fix-updating-partition-details-t3867714

you should install the downloaded app on the step number 1 in order to get along with the other steps.

:good:

[RECOVERY][discovery] TWRP Touch Recovery [OFFICIAL]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD: https://twrp.me/sony/sonyxperiaxa2ultra.html
BUGS:
If you have found a bug, please consider posting it to our github issues log and then I'll report to Dess_Troy. If you have a significant problem that cannot be answered in this thread, your best bet is to PM Dees_Troy directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY][discovery] TWRP Touch Recovery [OFFICIAL], ROM for the Sony XA2 Ultra
Contributors
LuK1337
Source Code: https://github.com/TeamWin
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2018-10-30
Last Updated 2020-06-25

Thank you for this. I was able to boot the recovery and install magisk on my device. Is there any way to make the recovery permanent or do we have to fastboot the recovery every time?

Aklenz07 said:
Thank you for this. I was able to boot the recovery and install magisk on my device. Is there any way to make the recovery permanent or do we have to fastboot the recovery every time?
Click to expand...
Click to collapse
Not yet. Thought I don't think it's worth to /install/ it anyway.

Error flash
Hi,
I installed LineageOS but when I want to flash the "recovery", I am in error...
"target reported max download size of 536870912 bytes
sending 'recovery' (57720 KB)...
OKAY [ 1.281s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.284s"
Why ?

GunnarZX said:
Hi,
I installed LineageOS but when I want to flash the "recovery", I am in error...
"target reported max download size of 536870912 bytes
sending 'recovery' (57720 KB)...
OKAY [ 1.281s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.284s"
Why ?
Click to expand...
Click to collapse
You don't flash it.

LuK1337 said:
You don't flash it.
Click to expand...
Click to collapse
Just boot only ?

GunnarZX said:
Just boot only ?
Click to expand...
Click to collapse
That's all you need.

Done
It messed up (bootloop) at first, but second time worked fine.

Messed up my Xperia XA2 ultra
Hi i tried to use twrp 3 to install lineage OS.
Unlocked bootloader.
Fastboot boot the twrp.img
Backed up the device
Installed lineage os 15.1 and got an error
So decided to roll back to stock os
Restored the backup files.
It failed to restore it: device in bootloop.
I tried to use sony flashtool got an error; usb debug off
Can anybody help me?

bsbrfb said:
Hi i tried to use twrp 3 to install lineage OS.
Unlocked bootloader.
Fastboot boot the twrp.img
Backed up the device
Installed lineage os 15.1 and got an error
So decided to roll back to stock os
Restored the backup files.
It failed to restore it: device in bootloop.
I tried to use sony flashtool got an error; usb debug off
Can anybody help me?
Click to expand...
Click to collapse
Restore phone with Sony flash tool
https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Install Lineage properly
https://wiki.lineageos.org/devices/discovery/install

Hi
Will this work on H3223 ?
Can this h3223 be rooted

mchlbenner said:
Hi
Will this work on H3223 ?
Can this h3223 be rooted
Click to expand...
Click to collapse
Unsure about root... Yet... But if you are bootloader unlocked you should at least be able to boot to twrp...

mchlbenner said:
Hi
Will this work on H3223 ?
Can this h3223 be rooted
Click to expand...
Click to collapse
Yes it roots

appleknight said:
Yes it roots
Click to expand...
Click to collapse
Magisk, and patch n flash boot.img?
Sorry mate, i'm coming from a device where kernel and ramdisk were separate partitions...
EDIT: Yes. Exactly

Aklenz07 said:
Restore phone with Sony flash tool
How Do I unlock the device?
I get an error saying my device is locked
Click to expand...
Click to collapse

tournelhenry said:
Aklenz07 said:
Restore phone with Sony flash tool
How Do I unlock the device?
I get an error saying my device is locked
Click to expand...
Click to collapse
https://wiki.lineageos.org/devices/discovery/install it tells you how to unlock
Click to expand...
Click to collapse

bootloader enter your imei it will give a key following all instructions precisely. it tells you the rxact command to use for unlocking the bootloader. after its unlocked, open your command prompt in your adb /fastboot folder. then adb reboot bootloader. after reboot phone will be blank screen. you have to download twrp 3.3.0.0 .img its the most updated. do that before the adb thing. then after adb thing, when you are booted into bootloader.....fastboot boot twrpxxxxx.img
this will boot into recovery. make sure you have magisk 19.zip doenloaded to your phone. then just flash magisk from the recovery, after reboot install magisk apk. there you go. sorry all of this is not in order. ive done it so many times im skipping ahead. i can give a better detailed and precise instructions if needed, litterally walk you thru it, if you need it. but the instructions provided by all the download sites are great. its easy peasy. if you need bettrr instructions youre more than welcome to get in contact with me. [email protected]
---------- Post added at 09:37 PM ---------- Previous post was at 09:31 PM ----------
sorry about that ****ty message, this goddamn site is retarded on mobile. im not going thru all that **** again but yes it can be rooted and its easy, if you need some clear instructions you can hit me up at the email i provided in that ****ty short bus post i left.
---------- Post added at 09:49 PM ---------- Previous post was at 09:37 PM ----------
you can keep the stock rom fyi. and theres an updated android 9.0 pie stock rom floating around too. im using it, no problems. you have to use xperifirm and flashtool to flash it tho. its simple unless its your first time doing, after you do it once youll ask yourself why it seemed so hard to get to that point. also, fyi, this particular is almost brick proof not saying it cant be bricked because, i did, several times boot looped it, everything, **** right now i dont even have a stock recovery because of some errors i made learning how to do all of this, but its up and running, its not buggy, magisk works great, stock android 9.0 firmware, just no recovery, but good ole twrp works just fine when you boot it for recovery. great phone to learn how to do all of this on. like i said its almost brick proof.

Sony Xperia XA2 Ultra - ROOT and Stock Rom 9.0
enter 192_161_227_73 in ip address format with the ftp header ftp://
should make rooting a little easier, need unlocked bootloader
simple interactive root process
also contains android 9.0 stock for Sony Xperia XA2 Ultra H3223

thanks Luk1337 for your work.
A) I get a stuck boot on SONY white screen when trying to reboot after a boot to twrp using fastboot (swipe to allow modifications and nothing else). Fastboot boot to TWRP was after a clean installation of Android Pie.
B) I even made a TWRP backup of the Android Pie rom but restoring backup runs into same issue of stuck on SONY logo). (well if just a twrp boot to resulted in a stuck boot (as in A) rebooting after a twrp backup restore would not have a chance either but just mentioning)
I am guessing we need a disable verity to avoid this?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://forum.xda-developers.com/showpost.php?p=77177197&postcount=3
Do we have a vbmeta.img for the XA2 Ultra? (from stock kernel) sorry if a noob question. Thanks.

mac231us said:
thanks Luk1337 for your work.
A) I get a stuck boot on SONY white screen when trying to reboot after a boot to twrp using fastboot (swipe to allow modifications and nothing else). Fastboot boot to TWRP was after a clean installation of Android Pie.
B) I even made a TWRP backup of the Android Pie rom but restoring backup runs into same issue of stuck on SONY logo). (well if just a twrp boot to resulted in a stuck boot (as in A) rebooting after a twrp backup restore would not have a chance either but just mentioning)
I am guessing we need a disable verity to avoid this?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
https://forum.xda-developers.com/showpost.php?p=77177197&postcount=3
Do we have a vbmeta.img for the XA2 Ultra? (from stock kernel) sorry if a noob question. Thanks.
Click to expand...
Click to collapse
Flash magisk or something, it'll disable verity.
Also we don't have vbmeta partition.