Database Users

[Tutorial] How to flash Ubuntu Phone, on Windows

Requied:
Custome recovery, working fastboot
First you need to download those files from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
quantal-preinstalled-system-armel+maguro.img
quantal-preinstalled-recovery-armel+maguro.img
quantal-preinstalled-system-armel+maguro.img
quantal-preinstalled-phablet-armhf.zip
While downloading, please do a full backup of your phone!
When you have files ready, first 3 IMG files, put then next to you fastboot.exe file, then copy the ZIP file to your phone.
Once that done, reboot you phone in to bootloader.
Chceck on you PC that you phone is connected and recognized: type fastboot devices
You should get line with bunch of number, that means that you phone is pluged in and ready to go.
Next type
fastboot.exe flash boot quantal-preinstalled-system-armel+maguro.img
next
fastboot.exe flash recovery quantal-preinstalled-recovery-armel+maguro.img
next
fastboot.exe flash system quantal-preinstalled-system-armel+maguro.img
Once that's done, reboot phone in to recovery, and in recovery flash quantal-preinstalled-phablet-armhf.zip, like normal rom.
That's it, reboot you phone and it will boot to UBUNTU (sometimes is stuck on black screen while booting for few seconds, and some people had to flash whole thing twice to boot properly).
Once you done playing with Ubuntu (It's not ready ad daily system by a long mile), boot in to recovery and restore you backup. That's it.
Above procedure should not wipe your memory (it didin't on my phone), but please do full backup before you start!

I think you missed the quantal-preinstalled-boot-armel+maguro.img for boot partition, there doesn't exist two system images.

iferlive said:
I think you missed the quantal-preinstalled-boot-armel+maguro.img for boot partition, there doesn't exist two system images.
Click to expand...
Click to collapse
Thought the same thing.
fastboot.exe flash boot quantal-preinstalled-system-armel+maguro.img
Should probably be
fastboot.exe flash boot quantal-preinstalled-boot-armel+maguro.img
I don't even think I installed some of these img files and it still worked for me...Must have got lucky. But went back to stock after about an hour.

zombie1991 said:
Thought the same thing.
fastboot.exe flash boot quantal-preinstalled-system-armel+maguro.img
Should probably be
fastboot.exe flash boot quantal-preinstalled-boot-armel+maguro.img
I don't even think I installed some of these img files and it still worked for me...Must have got lucky. But went back to stock after about an hour.
Click to expand...
Click to collapse
So?
It mean the tutorial need to edit?

Thanks for the guide but it didn't work for me, black boot screen every time
And yes I flash boot not system twice
At least I backed up and my data partition was not wiped.
Paito

ThePatio said:
Thanks for the guide but it didn't work for me, black boot screen every time
And yes I flash boot not system twice
At least I backed up and my data partition was not wiped.
Paito
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2159291
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"​

zombie1991 said:
Thought the same thing.
fastboot.exe flash boot quantal-preinstalled-system-armel+maguro.img
Should probably be
fastboot.exe flash boot quantal-preinstalled-boot-armel+maguro.img
I don't even think I installed some of these img files and it still worked for me...Must have got lucky. But went back to stock after about an hour.
Click to expand...
Click to collapse
You didn't get lucky the zips are all that is necessary if you have a custom recovery
Sent from my Nexus 4 using xda app-developers app

[HELP] Moto X 2013 seems to have no OS on it

Hi everyone,
tonight I was trying to install the Stagefright OTA using this guide: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
The only thing I got was an android with a red triangle on it. So I went back, did a total phone reset, reinstalled the TWRP (fastboot flash twrp.img) and restored my backup. Sadly, the phone keeps rebooting to the TWRP as if there's nothing on it except the TWRP.
I've got the eu model and I can't find any factory image (or image in general) to flash on the device.
EDIT:
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".

i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.

jco23 said:
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
Click to expand...
Click to collapse
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?

edmael said:
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
Click to expand...
Click to collapse
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.

jco23 said:
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
Click to expand...
Click to collapse
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.

edmael said:
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
Click to expand...
Click to collapse
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image

mastarifla said:
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
Click to expand...
Click to collapse
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it

edmael said:
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
Click to expand...
Click to collapse
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers

another thing I have noticed is that my phone kept getting stuck on the boot image screen (failed to proceed to the boot animation screen). to resolve this, I made sure to flash SU via TWRP after flashing my ROM via TWRP (or restoring a nandroid).

mastarifla said:
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
Click to expand...
Click to collapse
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this

edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
you may need to wipe internal storage and mfastboot everything from scratch...

jco23 said:
you may need to wipe internal storage and mfastboot everything from scratch...
Click to expand...
Click to collapse
Already did that (the first time I didn't even tried booting with BT Tools, but the effects were the same), but nothing new happened.

edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently

mastarifla said:
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
Click to expand...
Click to collapse
Yes, tried, but nothing happens (except that it boots when I go into BT Tools).
I think there's something wrong with my partition scheme because it always go straight to TWRP.
If I were on a GNU/Linux distro I'd check the grub config because it seems it boot from the wrong partition, but on Android I don't know if/how that's possible.

does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
did you happend to type "mfastboot flash boot twrp.img"? that could be the issue, as the command should be "mfastboot flash recovery twrp.img, right?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....

jco23 said:
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
Click to expand...
Click to collapse
Don't be sorry, you're helping me!
Also: I'm not much frustrated since I have a working phone right now, I just need do avoid rebooting it
I tried to flash the stock recovery (found here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628, used this: XT1052_GHOST_RETEU_5.1_LPA23.12-15_cid7_CFC.xml.zip) but if I'm not wrong (did that yesterday in the late night) it just booted to the Android with the red triangle on it (so, no booting for me).
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?

edmael said:
Don't be sorry, you're helping me!
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
Click to expand...
Click to collapse
You can revert it by taking the boot.img from the 5.1 zip and flashing that using the command...
mfastboot flash boot boot.img
The partitioning you are mentioning is probably the gpt.bin, but that is typically done near the very beginning of the flashing process

here's what I would do:
boot into recovery
connect phone to PC, copy your nandroid and any other files from the SDcard to your PC
within recovery, wipe cache/dalvik/data/internal storage
reboot to bootloader
run the mfastboot commands as shown (but use the getvar-download....) in place of editing the xml zip file
after running the mfastboot commands, let the phone boot up to stock and establish itself
reboot to bootloader and flash TWRP
again, just a suggestion on what I would do - seems like @mastarifla is a great resource and is more knowledgeable than me, so maybe you'll get some confirmation.
good luck!

Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.

edmael said:
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
Click to expand...
Click to collapse
So your phone thinks that the bootloader is your recovery?
That is actually pretty strange, you could take a look at the Linux kernel on Motorola's GitHub and see if it has any info on the partitioning structure or what happens when a reboot-bootloader command is sent to the phone
It sounds as if the recovery and the bootloader swapped places, as the fastboot menu is considered a part of the bootloader, and if you are not seeing that on the hardware key bootup, then there is something definitely wrong, if you do reboot-recovery does it take you to the bootloader/fastboot menu?

Need help getting to B27

I put back the B20 boot and recovery but it won't flash B27 because there was something wrong with the system. What do I do?

awsomjgp said:
I put back the B20 boot and recovery but it won't flash B27 because there was something wrong with the system. What do I do?
Click to expand...
Click to collapse
OK you are going to need the following;
http://d-h.st/dgWW Thanks To @Unjustified Dev
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy Thanks to @peramikic
http://forum.xda-developers.com/attachment.php?attachmentid=3845893&d=1471491841 Thanks to @tenfar
https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw Download the STOCK BOOT AND RECOVERY
Now do the following use AXONROOTTOOL to flash the 3.02.2
Code:
adb reboot edl
axon7root.exe -p4 -r
Boot into TWRP
Back up boot
Reboot to system
Now Extract the System image that you downloaded from cloud.swehes.com and copy the files
"1. system_image.emmc.win
2. system_image.emmc.win.md5"
Click to expand...
Click to collapse
into the TWRP folder that was created make sure it is in the SDCARD
reboot into TWRP
restore the system only wait for it to finish
reboot into the OS
use the AXONROOTTOOL to flash stock boot and recovery
Code:
adb reboot edl
axon7root.exe -p4 -r
do a Factory data reset/cache also
Then just update
Hope this help.
Remember
axon7root.exe -p4 -r
Click to expand...
Click to collapse
<---- p equals to port so check device manager to see what port you are on
FYI I was in the same boat lol but that's what I did to get back to stock and flash b27

awsomjgp said:
I put back the B20 boot and recovery but it won't flash B27 because there was something wrong with the system. What do I do?
Click to expand...
Click to collapse
Do you have TWRP installed? If so try a restore of my B27 system image + Boot + signed TWRP
Check this thread http://forum.xda-developers.com/axon-7/help/update-axon-7-a2017u-build-27-t3464517 it's post 51, if you are willing to test. Usual disclaimers apply.
Ignore that, since all my backup has is the system and boot partitions it's missing some of the firmware. The best method hands down is to flash the stock B20 system image

maxmotos said:
OK you are going to need the following;
http://d-h.st/dgWW Thanks To @Unjustified Dev
https://cloud.swehes.com/index.php/s/31V7GgihohBCdfy Thanks to @peramikic
http://forum.xda-developers.com/attachment.php?attachmentid=3845893&d=1471491841 Thanks to @tenfar
https://mega.nz/#F!rcFCQZ7C!vn457hU1zDwc0uVpvm5otw Download the STOCK BOOT AND RECOVERY
Now do the following use AXONROOTTOOL to flash the 3.02.2
Code:
adb reboot edl
axon7root.exe -p4 -r
Boot into TWRP
Back up boot
Reboot to system
Now Extract the System image that you downloaded from cloud.swehes.com and copy the filesinto the TWRP folder that was created make sure it is in the SDCARD
reboot into TWRP
restore the system only wait for it to finish
reboot into the OS
use the AXONROOTTOOL to flash stock boot and recovery
Code:
adb reboot edl
axon7root.exe -p4 -r
do a Factory data reset/cache also
Then just update
Hope this help.
Remember <---- p equals to port so check device manager to see what port you are on
FYI I was in the same boat lol but that's what I did to get back to stock and flash b27
Click to expand...
Click to collapse
What do I do if TWRP asks for a password?

I noticed that as well, TWRP wanted a password when I went in to it to decrypt the data partition, something I haven't seen before (note that I saw this before I tried flashing anything recently, I just went in to make a full backup first.) I tried using my phone lock pin number, no use. I tried "default_password" as well as google suggested but that also didn't work. /shrug , bedtime here, will work on it tomorrow.

awsomjgp said:
What do I do if TWRP asks for a password?
Click to expand...
Click to collapse
I pressed cancel and went straight to restore.

(WIP) Magisk/Root installation

So this morning, we finally got our hands on some factory images. That is the good news. The bad news is that so far I am unable to get Magisk to work. Anyone else get it to work yet?
Here is what I have done:
1) Download the latest (5.4) magisk manager apk [Thread | Direct Link]
2) Set the update channel to both stable (14.0) and beta (14.3)
3) Choose install from stock boot img (with and without keep dm-verity and force encryption)
4) Copy the patched boot img from your phone:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img .
4) Flash the modified boot.img in fastboot
Code:
fastboot flash boot patched_boot.img
Results:
1) With 14.0, the system boots up fine, but magisk isn't installed
2) With 14.3, I get bootloops, and have to reflash the stock boot.img in order to get it to boot.
Might be worth noting that the patched boot img is significantly smaller than the original one (about 25mb vs 40mb)

I tried the same thing with 14.3 only and it says it patches the boot.img that I pulled from the image. I then reboot and I am not rooted. Is there suppose to be an option to patch the second slot?

Once you patch the stock boot.img it should tell you where it placed the patched img. For me it was /sdcard/MagiskManager/patched_boot.img
You need to pull that img file, reboot to bootloader and fastboot flash that.

skaforey said:
Once you patch the stock boot.img it should tell you where it placed the patched img. For me it was /sdcard/MagiskManager/patched_boot.img
You need to pull that img file, reboot to bootloader and fastboot flash that.
Click to expand...
Click to collapse
Ok, I see you have to manually apply the patched boot img. This is my first Pixel, came from a 6P where I just used twrp to install magisk. Guess we need to wait for a newer Magisk.

stevetrooper said:
Ok, I see you have to manually apply the patched boot img. This is my first Pixel, came from a 6P where I just used twrp to install magisk. Guess we need to wait for a newer Magisk.
Click to expand...
Click to collapse
Can you try flashing the patched boot.img? If you get into a bootloop, simply hold power and volume down to get back into bootloader mode and reflash the stock boot img

skaforey said:
Can you try flashing the patched boot.img? If you get into a bootloop, simply hold power and volume down to get back into bootloader mode and reflash the stock boot img
Click to expand...
Click to collapse
My PC is at home, will have to try later tonight. I suspect that it will boot loop like yours, since the patched img is only 25 megs and the original was 40.

Try the app One Click Auto Brick. ?

I tried it and it did the same bootlooping you described.

Were you guys able to flash the factory image and get it to boot past the google screen?

I've been through the same process. I manually flashed the patched_boot.img and got stuck in a bootloop. Had to flash the factory boot to get back up and going. @topjohnwu do you have any insight on this?

Just wondering, have you run
Code:
fastboot flashing unlock_critical
? Just saw it in this post: https://forum.xda-developers.com/showpost.php?p=74271129&postcount=6

gakio12 said:
Just wondering, have you run
Code:
fastboot flashing unlock_critical
? Just saw it in this post: https://forum.xda-developers.com/showpost.php?p=74271129&postcount=6
Click to expand...
Click to collapse
This might pertain to flashing an updated bootloader. The boot image flashed fine, just bootlooped, so I don't think that's the problem.

teshxx said:
Were you guys able to flash the factory image and get it to boot past the google screen?
Click to expand...
Click to collapse
I had to re-extract the boot.img from the factory image and flash it manually again to get it to boot. A flash-all did not seem to get it.
Code:
Fastboot flash boot boot.img

I dont have my 2XL yet, but I grabbed the factory image and yanked the boot out of it then used Magisk Manager on my MXPE to patch the img. I've unpacked both images to compare them and it's definitely patching it and the patched one doesn't seem to be missing anything so I'm fairly certain the size difference is due to the patched image not being padded to the 40MB size of the boot partition. So probably not something to worry about.
It looks like my device will be here wednesday. If nobody else has cracked this case by then I'll start poking around. If anyone else is poking around and looking for ideas. I would start by unpacking and repacking the normal boot.img and flashing it just to make sure it boots. Assuming it does then modify the default.prop on the patched_boot.img to enable insecure adb during boot so that adb logcat can be run while it's booting and maybe get an idea of what's going on.

The only problem I see with your process is patching it in another device will likely cause problems because it was patched using the wrong vendor image.

northmendo said:
The only problem I see with your process is patching it in another device will likely cause problems because it was patched using the wrong vendor image.
Click to expand...
Click to collapse
Oh yeah, I wouldn't try to flash what I made from another device. I mainly wanted to see what, if anything magisk manager would do with it. If someone wants to upload a patched_boot.img they made on their 2XL so I can look into it when I get home from work tomorrow that would be appreciated.
Maybe I'll get lucky and get mine tomorrow.

I can do that. I'll create one first thing in the morning.

What's the best way to look at the contents of the img files? Preferably on Windows

update:
I mounted both the stock boot.img file and patched boot.img files and it does appear that changes are being made.
Here are the files that are different between the 2:
Code:
ramdisk/init
The patched boot img contains additional files that seem normal:
Code:
ramdisk/overlay/sbin/magisk (binary file)
ramdisk/overlay/init.magisk.rc
In addition, I found the backup of the main init file that was changed in ramdisk/.backup/init
Here are the contents of the init.magisk.rc file
Code:
# Triggers
on post-fs
start logd
start magisk_daemon
wait /dev/.magisk.unblock 5
rm /dev/.magisk.unblock
start magisk_pfs
wait /dev/.magisk.unblock 10
on post-fs-data
load_persist_props
rm /dev/.magisk.unblock
start magisk_pfsd
wait /dev/.magisk.unblock 10
# Services
# Self recoverable service
service magisk_daemon /sbin/magisk --daemon
user root
seclabel u:r:su:s0
# launch post-fs script
service magisk_pfs /sbin/magisk --post-fs
user root
seclabel u:r:su:s0
oneshot
# launch post-fs-data script
service magisk_pfsd /sbin/magisk --post-fs-data
user root
seclabel u:r:su:s0
oneshot
# launch late_start script
service magisk_service /sbin/magisk --service
class late_start
user root
seclabel u:r:su:s0
oneshot
# STOCKSHA1=6d4d920f9d0b6eee52de8a95614a9884ef80d732
Not sure if this is useful to anyone, but maybe it will be.
One thing I noticed was the the . rc file contained references to /dev/.magisk and /sbin/magisk but I do not see those files in the patched boot img (only in the overlay folder, and maybe that's all that's needed, I don't know nearly enough about this to say for sure).
But, perhaps that's part of the problem?

Could the title of this thread be changed? Very clearly not a guide or even a WIP.. It's a question/discussion on what might work to get Magisk working.

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...