Develop Bugs

[Q] How to flash CWM on Xperia S Stock JB?

Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I already did:
Root
Backup TA
Unlocked Bootloader (official way via Sony website)
What I already tried to install custom recovery:
RecoverX App on PlayStore -> Recovery not booting when tapping the sony logo while booting (black screen for some seconds then reboot to Android)
Xperia S Dual Recovery (Linux script) -> Installation successful but no chance to boot one of the recoveries via Vol +/-, no blue LED, boots directly to Android
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
EDIT 13:58
After further reading this looks like the way to go:
[RECOVERY] CWM-Based Recovery 6.0.2.7 for Xperia S (UnlockedBootLoader){JB}[20130824]
Correct? I don't want to end up bricking the device by trying different things. Can I flash CM11 ROMS using this recovery? The post says "do not use this for flashing CM10.1 (u will need to use the CM kernel for that)" which keeps confusing me ...
And how do I remove the recoveries already installed (list above) but not working?

real_sl4cker said:
Hi all,
I'm messing around with my girlfriends Xperia S and śtuck on installing a custom recovery (CWM seems to be the preferred one on the S).
The System:
Stock Sony JB
Build 6.2.B.1.96
What I'm trying to achieve:
Install CM 11 with root access
I'm kind of experienced with HTC phones and my OnePlus One so not a complete noob but it looks like Sony phones are a different thing.
I read about the need to flash a custom kernel which includes the recovery but there are seperate recovery threads on the other hand. The sticky role up threads seem out of date.
Been reading since yesterday but this only lead to more confusion.
I hope someone can help me out getting CWM (or any other recommended recovery) on this phone to install CM 11.
And how to remove the recoveries I already installed and don't work?
Click to expand...
Click to collapse
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.

Mirhawk said:
First copy the zip of CM11 ROM to the phone.
Then on PC, extract the boot.img (this is the custom kernel with recovery for the ROM) from the ROM zip and flash it via fastboot using the flashtool software. Then You will have a twrp installed in Your phone due to it. Now boot into twrp and flash the ROM.
Note, after You flash the boot.img, You won't be able to boot into stock firmware. You will have to flash the CM11 ROM.
Also, if the recovery are not accessible, they are probably not installed, so no need to remove them.
Click to expand...
Click to collapse
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S

real_sl4cker said:
Thank you very much for the instructions, now there's less confusion :good:
So let's see how it works with Paranoid Android. I'll report back afterwards.
Any Android 4.4 ROM recommendation as a stable daily driver?
Looks like there is no up to date standard CM11 build for the Xperia S
Click to expand...
Click to collapse
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.

Mirhawk said:
From what I have been reading, PA does seem to be stable enough to be a daily driver, just find the correct build of it. I don't know which one is as I don't use it much, do ask in the thread.
I would suggest Carbon ROM too, but it is currently having some battery drain issues, the battery works for hardly an entire day.
Click to expand...
Click to collapse
Thanks. I already found the current PA build in the thread (4.5 beta2) and apart from German translations missing in PA settings up to now it performs well [emoji3]

SM-T700 Bootloop after flash of customrom, again and again

Hallo everybody, greetings from germany.
I would need some support from you guys on a bootloop case for the sm-t700. I searched my ass off in google and xda but could not find a solution.
So now after hours of trying it myself I like to ask for help.
In the following I will describe what I have done to come to this point including everything I installed etc.
The stock rom was lollipop 5.0.2 and already installed.
- usb debug mode on
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- forgot to install busybox and rootchecker for verifying root.
- backup of IMEI/EMFS (data is now on pc)
- in recovery backup of Boot.img
- wipe data/cache/dalwik/system in one go
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls from 5 to 10 minutes.
Next I wanted to do it better by installing busybox and cheking for root, because
I thought first that this could be the main cause for the bootloop.
- downloadmode
- flashed succesfully "T700XXU1BOE5_T700DBT1BOD1_HOME.tar.md5" via odin v.3.10.7 to get to stockrom again
- usb debug mode on
- downloadmode
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- verifyied it with rootvalidator
- installed busybox
- deleted all knox stuff
- installed twrp app to get to v.2.8.7.0
- recoverymode
- backup of everything
- wipe data/cache/dalwik/system
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls again from 5 to 10 minutes.
Next I went into recovery and restored everything as before the flash of the customrom.
This happens in the same way with blisspop and liquidsmooth roms.
Hope anyone knows something.

Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
You need to flash the kernel provided in that thread or flash the whole rom again.
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.

ashyx said:
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
Click to expand...
Click to collapse
By "multi flash" do you mean the install procedure in twrp that automates the installation procedure? (add zip)
And how am I able to flash after each successful boot if there is nothing to boot left after wipe?
ashyx said:
You need to flash the kernel provided in that thread or flash the whole rom again.
Click to expand...
Click to collapse
I thought this Kernel would be great. So you do not recommend me to use it?
I will look up the roms now and the kernel they use.
ashyx said:
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
Click to expand...
Click to collapse
How do I do this or if already up to date where do I can look it up?

According to your post you flashed rom, gapps and kernel in one go.
Any one of those could have caused a bootloop or hang.
As for SkyHigh kernel, it is a great kernel but probably not suitable for an aosp rom as it's built from stock sources intended for stock roms.
Use the kernel provided.
To update the bootloader flash the latest firmware or pull it out and flash it separately.

Okay I will do the following now.
First find the appropiate Kernel if Skyhigh is a nogo. sadly.
Then flash in recovery at first the kernel of the rom. boot. recovery, flash the customrom + gapps. Right?
And before all that flash a new bootloader.
Further, is there a Kernel beside the one of the roms that you would recommend me?

Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.

ashyx said:
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
Click to expand...
Click to collapse
Okay worked well.
Left out the kernel because I could not find any custom ones.
Now I have euphoria on it and want to change between blisspop and liquidsmooth until I have the one I like most.
It is kinda hard to get the difference. I just know that euphoria and liquid are faster, smoother?
Thanks a lot without your input I would still be searching for an answer.
Happy day to you.

skyhigh and iron kernel are mean for touchwiz. Its not mean for cyanogen/aosp/aokp.
currently there is no one cook a custom kernel for cyanogen/aosp/aokp rom. so we stuck with the kernel that come with the rom.

Kernels :
https://www.androidfilehost.com/?w=files&flid=37193

Okay, did not know about this kernel.could you give me some info about the "deathly signed"?
My browser here is not loading the xda thread where I found people talking about it.

New to this and think I broke my phone.

Well let me explain. I wanted to tether, so I thought I would try and root and install a custom rom. I used Odin to install TWRP, downloaded NobleRom, thinking that it should work, flashed it and all it does it sit at the android screen when I boot up. I did a wipe and tried to install a "stock" rom that is apparently incompatible. My phone is a 920P. Currently lost and looking for direction for a slim, compatible rom that works.
HELP!

mrcookjr said:
Well let me explain. I wanted to tether, so I thought I would try and root and install a custom rom. I used Odin to install TWRP, downloaded NobleRom, thinking that it should work, flashed it and all it does it sit at the android screen when I boot up. I did a wipe and tried to install a "stock" rom that is apparently incompatible. My phone is a 920P. Currently lost and looking for direction for a slim, compatible rom that works.
HELP!
Click to expand...
Click to collapse
im using this with no issues flash in recovery
http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417

I download and give this a try! Thank you!

The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.

1619415 said:
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
Click to expand...
Click to collapse
That's what the post above suggested. Thank you for explaining why. So from what you're saying, each rom is based on a particular Kernel? What other factors must be the same? I'm sorry if this is a dead horse, just new to me.

1619415 said:
The reason your phone won't boot is due to the wrong kernel and even then won't boot (as I've tried). What I recommend you doing is booting into TWRP and installing Renegade ROM its is currently one of the only stable ROMs for our phone.
Click to expand...
Click to collapse
OK, I just installed Renegade and it's sitting on the boot screen with Andy holding a dragonball and a phone. Did I do something wrong?

mrcookjr said:
OK, I just installed Renegade and it's sitting on the boot screen with Andy holding a dragonball and a phone. Did I do something wrong?
Click to expand...
Click to collapse
Wait what?
Upload a screenshot

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!

bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.

SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.

bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.

Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?

bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1

All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!

You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.

TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!

bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?

have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.

bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.

noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

General Switch from Parnaoid Topaz to other roms

I have tried Paranoid TopaZ but found that the bluetooth headset doesn't work, so I have to switch to other roms.
But I found that I can't boot to recovery images from fastboot. I tried TWRP and OrangeFox recovery both can't be booted by
fastboot boot recovery.img
Finally I turned to flash miui eu rom which can be flashed under fastboot mode then boot to the recovery then flash other roms. I think this issue is caused by that Paranoid TopaZ is CAF based rom so I post this thread for anyone who maybe need this infomation.

I wish I could have read this earlier... I literally spent a night wondering why I could not flash a custom recovery. It could be great to inform people in the rom thread that you need to reflash the whole MIUI rom before you can boot custom recovery.

ShinoYasx said:
I wish I could have read this earlier... I literally spent a night wondering why I could not flash a custom recovery. It could be great to inform people in the rom thread that you need to reflash the whole MIUI rom before you can boot custom recovery.
Click to expand...
Click to collapse
Maybe the developer don't care about this issue.

I haven't read the aospa source, but the issue could be related to this https://forum.xda-developers.com/t/vendor_boot-roms.4575777/

x3r0.13urn said:
I haven't read the aospa source, but the issue could be related to this https://forum.xda-developers.com/t/vendor_boot-roms.4575777/
Click to expand...
Click to collapse
Seems related.