Database Users

CWM recovery wont flash after KRT16O -> KRT16S OTA.

Hi all. I flashed the full system image of KRT16O when it was released. I then flashed with fastboot the CWM 6.0.4.3 recovery image. I then got the OTA to update to KRT16S. I read online that I didnt have to unroot or go back to the stock recovery so I just let it update like normal. It updated fine, loaded up fine, etc. So I then went to use fastboot to reflash the CWM recovery image however all I get is the android on his back with the red triangle.
Am I doing something wrong? Could my recovery partition be screwed? How do I fix it. Thanks!

i should also mention that when I use fastboot to flash the recovery image, it says it was copied/flashed successfully - but it doesn't work.

You didn't flashed recovery or didn't do it correctly. What you saw is stock recovery.
And remember to flash recovery to the correct partition: fastboot flash recovery cwm.img

yea i dont think u flashed it correctly either.
go to clockworkmod, download the latest.... copy it to the platform tools folder. then fastboot flash it again...

thanks guys. Im familiar with the process - when I flashed the factory image KRT16O I then used fastboot to flash CWM just a few days prior without a hitch. But on Friday it just wouldnt "stick". I tried three times, each time it said successful but then after a reboot it would be gone. On the third time though after I flashed it, and it said success, I then went into recovery from the bootloader screen and it was there, so I rebooted and went back and this time it had stayed. strange.
Side note - does debugging need to be on to use fastboot?

I am having the same problem.
After the OTA, CWM won't stick. I get a red triangle.
fastboot screen shows that I have a secure boot, whereas the phone shows the lock as unlocked.

burnski said:
Side note - does debugging need to be on to use fastboot?
Click to expand...
Click to collapse
USB debugging box should be checked in order to use fastboot.
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
yaronkle said:
I am having the same problem.
After the OTA, CWM won't stick. I get a red triangle.
fastboot screen shows that I have a secure boot, whereas the phone shows the lock as unlocked.
Click to expand...
Click to collapse
try to root the phone again and making sure before flashing the CWM, you should erase the old one, use command in fastboot:
fastboot erase recovery
and then
fastboot flash recovery nameofrecovery.img

I got CWM working again. Not sure how.
I disabled ART, reboot and CWM worked.
Enabled ART and CWM still works, just that it asks if I want to install SU again before booting.

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode

You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it

Don't do what rosswaa said

Why not?

What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).

I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now

Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Obviously try what green says first, if it works then happy days

first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx

SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

"soft-brick" on Essential Phone PH-1

Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)

Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?

Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.

BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again

Azpre said:
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Click to expand...
Click to collapse
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

dirtyreturn said:
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
Click to expand...
Click to collapse
thanks for the thread man, helped alot
I managed to flash twrp by some miracle, I remember my device entering a bootloop once I tried to access the bootloader menu, but now its all good. I waited for the Essential run out of battery, then I plugged-in my pc the fastboot commands were working once again
going to try install a boot image now

dirtyreturn said:
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
oh my god Im such a dumbass, sorry

I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.

{root} Boot-loader unlock, TWRP flash and Magisk install after updating to Pie

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Needed tools : Backup your phone before following any steps
1. Minimal adb and fastboot
2. official TWRP 3.3 for jasmine_sprout Download img file from twrp website
3. latest magisk manager 19.2 zip file from magisk manager website
First step : Boot loader unlock
1) Tap on build number more than 7 times and unlock developer option in about phone.
2) turn on OEM Unlocking and USB debugging
Now open command windows in adb shell folder and connect your device to computer.
type : 1) adb devies (this should show your device after giving permission in your phone : conformation that your device is
connected)
2) adb reboot bootloader
3) fastboot devices ( conformation that your phone is coonected in fastboot mode)
4) fastboot oem unlock
( after that you need to follow according steps in your phone and grant to unlock phone)
keep in mind this will reset your phone. Afteer reboot again turn on developer options and usb debugging
5) fastboot flashing unlock_critical
( the warning and steps you need to follow again in your phone like in step 4)
this will again reset your phone.Afteer reboot again turn on developer options and usb debugging
Congratulations your bootloader is Unlocked now.
STEP 2. Flashing TWRP and Magisk Install
before that keep in mind As Mi A2 follows A/B boot partition system so DONT DIRECT FLASH TWRP FROM
FASTBOOT.
" Dont forget to turn on developer options and usb debugging "
open command window in adb shell folder and boot your phone in bootloader mode as told earlier and connect to computer.
Copy twrp-3.3.0-0-jasmine_sprout.img to minimal adb and fastboot folder. you can rename it to your convenient name
type : 1) fastboot boot twrp-3.3.0-0-jasmine_sprout.img
or if you renamed it
fastboot boot YourRenameName.img
this will temporarily boot twrp in your Device. As twrp is booted you will be able to see your phone connected in computer
(file transfer mode)
Copy and paste both magiskmanager.zip (current latest stable is 19.2 ) into phone
Flash your downloaded version of Magiskmanager.zip
Reboot your Phone.
Congratulations If nothing goes sideways Your phone is Magisk Rooted.
If you want to flash something using TWRP now is the time Otherwise as Mi A2 has A/B slot form and no Recovery Partition You Cannot flash TWRP permanently.
But You can always boot TWRP from adb and use it.

ROM flashing help
Can't flash ROM after using this method

Torque422 said:
Can't flash ROM after using this method
Click to expand...
Click to collapse
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

Failed
No such a directory problem, please help

Please elaborate more about the problem ? @shahidrok
shahidrok said:
No such a directory problem, please help
Click to expand...
Click to collapse
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
TYPHOON9055 said:
You May be facing some highly lag issues too. In that case flash stock rom using mi flash tool. In my steps i said that flash twrp.zip file after booting it. But flashing twrp.zip doesnt do anything. if you want to use TWRP you need to boot TWRP everytime from adb.
Also After flashing stock rom i am pretty sure that you will be able to flash custom rom.
follow this guide for flashing custom ROMs
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thanks ?, i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now?
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055

Hve done everything but when i try to reboot to twrp it gets stuck on twrp logo,dont know what im doing wrong.

Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks

I get error 1 during flashing

Amnvlad said:
Twrp only working when flashing via adb, and when I try to boot into twrp recovery it gets stuck twrp logo. Flashed magisk patched but unable to flash any magisk module or if I try to flash and reboot device it always get stucks in bootloop.. unable to find the problem.. a little help would be highly appreciated. Thanks
Click to expand...
Click to collapse
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Alucard said:
I get error 1 during flashing
Click to expand...
Click to collapse
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic ?

Torque422 said:
Reflash the latest twrp again through fastboot , And flash only .img file of twrp
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Follow the flashing custom rom guide, i flashed successfully, Havoc rom is fantastic
Click to expand...
Click to collapse
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
Available custom roms are for Oreo versions if you have updated ur device to pie , it won't work.

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
I was on stock pie + may update (10.0.9)
Follow this way , unlock the bootloader via fastboot oem unlock, fastboot flashing unlock it will reboot here, goto developer settings Enable usb debugging
Then do this fastboot flashing unlock_critical It will again reboot
Now, install the magisk app And download the patched boot image from internet Whatever your build no is, mine was 10.0.9 so i downloaded version 10.0.9_boot.img
Open the magisk app, click on install , select and patch a file, Then choose this downloaded patched image, it will flash it successfully, if it don't Then you have mistaken something..
After this there will be a patched.img in download folder Which is just created by magisk, copy this img to pc, Through fastboot Flash it "fastboot boot patched.img"
Now, flash TwrpImage3.3.img through fastboot
When you boot in , Copy and paste your rom, gapps
Now flash twrpVersion3.2.img via fastboot
Clear system,data,caches, Flash the rom in slot B
Now flash the twrp3.2.zip through installed twrp, click on recovery And it will boot to twrp
Now Flash the gapps in slot a (i used nano)
Now flash magisk.zip through twrp
Reboot , That's it!
(Twrp 3.2 is stable for flashing rom and gapps , Just for first time When we coming from stock
Twrp 3.3 latest Gives us MTP transfer, The difference is this in using both of these)
Installation of magisk is the last process, it is part of rom, First installed ur desired rom and then magisk
You said, You installed twrp, as i mentioned above You forgot to do some steps as about patched boot + installation of magisk through patched file etc..
Though you can try to search on google for your next step
patched supported magisk Version x.x.x for mi a2
If you got the file, You are lucky.. otherwise flash the stock rom with mi flash tool
And Start from unlocking bootloader

Magisk Module available.
Torque422 said:
Please elaborate more about the problem ? @shahidrok
---------- Post added at 03:16 PM ---------- Previous post was at 03:08 PM ----------
Thanks , i have successfully installed havoc rom, i read that link many times But this time i read more carefully, I have installed everything now
Do you know, If we can install nethunter in our mi a2 @TYPHOON9055
Click to expand...
Click to collapse
There is a magisk module available for installing kali nethunter in this device. i never tried installing it but it should work fine. Read proper descriptions before installing it though.

Alucard said:
I unlock bootloader perfectly,then boot twrp ,then wipe all except internal storage then trying flash but doesnt work,so do i have to flash magisk first then reboot and trying flash rom?
Click to expand...
Click to collapse
the adb recognized my phone but fastboot do not, help me out please

Andrew.kathy said:
the adb recognized my phone but fastboot do not, help me out please
Click to expand...
Click to collapse
Probably a problem with drivers, check and reinstall drivers

Can i use this method to flash magisk on Mi 9T pro?

I can't boot into twrp
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs

Topper8118 said:
The command u said to enter fastboot boot twrp.img it says booting and then the bootloader message and then shut downs
Click to expand...
Click to collapse
Checklist:
- there is file of <compatible TWRP recovery> in ADB/Fastboot directory with the name you are typing in fastboot command
- ADB drivers installed correctly (both "adb devices -l" and "fastboot devices" return valid results in corresponding phone states)
- only one phone (namely MiA2) is connected to PC
- phone fully unlocked (OEM debugging enabled and PC was previously approved for ADB in phone)
- USB port on MB of PC is USB-2.x or USB-3.x-compatible-with-Mi-A2<which is not true in general>

Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you

HTCDevil said:
Several guys says that command "fastboot oem unlock" is old and now we have to write "fastboot flashing unlock" instead, then "critical".
Which is the best way now?
Thank you
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical

boot loop / stuck after installing TWRP

hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?

shikaji said:
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
Click to expand...
Click to collapse
I had a very difficult time rooting my Xperia X Compact (F5321) using the method you describe above. I had exactly the same problem with bootloop and sticking on the Sony screen. My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
So I opened up ADB and flashed the renamed boot.img file, followed by Twrp. Then I booted into TWRP recovery (power button + volume down) and installed the supersu (or magisk if you prefer) and drmfix.
Then I rebooted to system and after a few minutes it booted normally into the Xperia homescreen.
Regards,
Dave

funkoot said:
My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
Click to expand...
Click to collapse
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!

shikaji said:
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
Click to expand...
Click to collapse
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.

shikaji said:
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
Click to expand...
Click to collapse
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app

Bluestar01 said:
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Click to expand...
Click to collapse
unfortunately i've tried that as well already. same thing - stuck at sony screen or bootloop.

Hello, any updates ? I have the same problem, after flashing my F5321 with Flashtool to update from android 6 to 8...