XZ1 compact no bootloader - Sony Xperia XZ1 Compact Questions & Answers

Dear All,
My problems is that my xz1 compact has only TWRP working. (after badly installing lineage 15.1).
The file system seems ok, but I cant access the bootloader (not from the twrp neither from the button). Needless to say I cant install lineage as it fails and ends up in the TWRP.
Please Help, advise.
Thank you
Guy

guyxz1c said:
Dear All,
My problems is that my xz1 compact has only TWRP working. (after badly installing lineage 15.1).
The file system seems ok, but I cant access the bootloader (not from the twrp neither from the button). Needless to say I cant install lineage as it fails and ends up in the TWRP.
Please Help, advise.
Thank you
Guy
Click to expand...
Click to collapse
What firmware version did you have on the phone before you tried to flash Lineage?
The versions must match.
You could use newflasher and xperiafirm to reflash your phone to a working stock. Use Oreo firmware if you want to flash Lineage 15.
Then start from sctratch using the TWRP from the XZ1c thread.

Related

Magisk on z3 compact

Hello guys,
I have a problem installing magisk on my Sony Xperia z3 compact with android stock 6.0.1 in order to root my phone.
Today, for the first time, I unlocked the bootloader and I installed TWRP recovery.
I tried to install the latest version of magisk (v. 18.1) via TWRP, but it shows "Error 1".
I read in the XDA forum that I should flash the boot.img and then I should reinstall magisk.
What I don't understand is where I can find this file "boot.img". I have a stock rom.
Can someone help me?
Thanks!

TWRP install and magisk root xz3

So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update
Jharrisonkerr said:
So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update
Click to expand...
Click to collapse
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.
MartinX3 said:
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.
Click to expand...
Click to collapse
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.
Jharrisonkerr said:
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.
Click to expand...
Click to collapse
Hi Jharrison,
You did say it hangs
At twrp boot logo?
MartinX3 said:
Hi Jharrison,
You did say it hangs
At twrp boot logo?
Click to expand...
Click to collapse
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.
Jharrisonkerr said:
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.
Click to expand...
Click to collapse
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?
MartinX3 said:
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?
Click to expand...
Click to collapse
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?
Jharrisonkerr said:
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?
Click to expand...
Click to collapse
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log
MartinX3 said:
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log
Click to expand...
Click to collapse
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?
Jharrisonkerr said:
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?
Click to expand...
Click to collapse
The correct way is in the first post of the first page in the main twrp thread.
Managed to get it working, however once all installed it asks to update the magisk app to 19.3 which I have done however it is now stuck in a bootloop where it loads Sony and powered by android and then reboots every time.
What's the fix for this?
So far I've fixed it by reinstalling the previous version through twrp. Is there issues with magisk 19.3?
Alos now in the magisk manager I have the manager showing up to date(7.3.2) but magisk is showing not installed only able to install magisk 19.3?
Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]
MartinX3 said:
Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]
Click to expand...
Click to collapse
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?
Jharrisonkerr said:
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?
Click to expand...
Click to collapse
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Tried the magisk uninstaller but every time I do it comes up with error 1 and then never installs.
The flash boot.sin sounds a easy fix, I will try that and see. If not looks like a full firmware reinstall is on the cards. I'll stick with 18.1 when I do as that seemed to work until I updated. I'll wait till a stable release of 19.4 is released.
Many thanks for your help so far Martin.
MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?
Jharrisonkerr said:
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?
Click to expand...
Click to collapse
The app is fine
MartinX3 said:
The app is fine
Click to expand...
Click to collapse
Awesome I'll update the app to latest then and leave magisk at 18.1 as root is working fine so far.
Many thanks for your help with all this Martin. :good:
MartinX3 said:
The correct way is in the first post of the first page in the main twrp thread.
Click to expand...
Click to collapse
Can you share the link please? I visited your profile but did not found the that thread how to flash my sony xz3 using TWRP.

can´t root with Magisk nor SU

Some days ago I got a brand new XZ2c (single sim) and from the past I know that this forum is the place to go for guides for rooting and for custom roms :good:
So I started a lot of reading articles and than tried this guide:
[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.1-0 [UNofficial] https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597 and for sure all tools I dl from the links from the guide
btw. my goal is the eXistenZ Pie rom and of course root
1. Update to newest stock firmware before unlocking!!!
Click to expand...
Click to collapse
I don´t know if it was a "fault" but I unlocked with the firmware with which I got the phone and it was the firmware before the latest one
so at my first rooting try I did no update to the latest firmware, but at all further tries I flashed the newest firmware 52.0.A.8.131 for my country and provider (H8314 Mobilkom A1, it´s for Austria)
I did every step from this guide:
2. FASTBOOT
(Optional; If you modify the system or need the camerafix.zip)fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
3. TWRP
Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
4. Reboot into installed TWRP
5. TWRP
(Optional; Root Part 1/2) Flash Magisk 19.4 or newer
Click to expand...
Click to collapse
booting into twrp never was a problem and also every time I did the fastboot command with the ...vbmeta.img (don´t know if this is still necessary but I did)
6. Reboot into SYSTEM
Click to expand...
Click to collapse
and here is always the same and first problem: a boot loop, so I rebooted into recovery: fix boot loop
after this no problem to boot into system and everything is working fine but no root (Magisk and root checker)
7. (Optional; Root Part 2/2) Install the official Magisk App to gain root.
Click to expand...
Click to collapse
after I installed this it shows me:
1) Magisk is not installed (new version 19.3)
2) a newer version of the app is available (7.3.2)
sure I updated both the app and installed from twrp the 19.3 zip but still no success (again boot loop and fixed the loop from twrp)
I tried the complete procedure a lot of times, always with flashtool flashed the latest firmware, booted into system, than twrp a.s.o., I tried some solutions from this forum like patching the twrp directly with Magisk: https://forum.xda-developers.com/showpost.php?p=74368287&postcount=23 but no success
at least I tried to install SU but also no root
...I have no idea what I should try next so I hope you have some advices?
Same problem for me.. maybe it has to do with the drm?
Same problem for me.. maybe it has to do with the drm?
b00rn said:
Some days ago I got a brand new XZ2c (single sim) and from the past I know that this forum is the place to go for guides for rooting and for custom roms :good:
So I started a lot of reading articles and than tried this guide:
[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.1-0 [UNofficial] https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597 and for sure all tools I dl from the links from the guide
btw. my goal is the eXistenZ Pie rom and of course root
I don´t know if it was a "fault" but I unlocked with the firmware with which I got the phone and it was the firmware before the latest one
so at my first rooting try I did no update to the latest firmware, but at all further tries I flashed the newest firmware 52.0.A.8.131 for my country and provider (H8314 Mobilkom A1, it´s for Austria)
I did every step from this guide:
booting into twrp never was a problem and also every time I did the fastboot command with the ...vbmeta.img (don´t know if this is still necessary but I did)
and here is always the same and first problem: a boot loop, so I rebooted into recovery: fix boot loop
after this no problem to boot into system and everything is working fine but no root (Magisk and root checker)
after I installed this it shows me:
1) Magisk is not installed (new version 19.3)
2) a newer version of the app is available (7.3.2)
sure I updated both the app and installed from twrp the 19.3 zip but still no success (again boot loop and fixed the loop from twrp)
I tried the complete procedure a lot of times, always with flashtool flashed the latest firmware, booted into system, than twrp a.s.o., I tried some solutions from this forum like patching the twrp directly with Magisk: https://forum.xda-developers.com/showpost.php?p=74368287&postcount=23 but no success
at least I tried to install SU but also no root
...I have no idea what I should try next so I hope you have some advices?
Click to expand...
Click to collapse
Luspuz said:
Same problem for me.. maybe it has to do with the drm?
Click to expand...
Click to collapse
b00rn said:
Some days ago I got a brand new XZ2c (single sim) and from the past I know that this forum is the place to go for guides for rooting and for custom roms :good:
So I started a lot of reading articles and than tried this guide:
[RECOVERY][Android 8 / 9][Stock/Custom ROM][XZ2/c/p, XZ3] TWRP 3.3.1-0 [UNofficial] https://forum.xda-developers.com/xp...recovery-twrp-3-2-2-0-touch-recovery-t3821597 and for sure all tools I dl from the links from the guide
btw. my goal is the eXistenZ Pie rom and of course root
I don´t know if it was a "fault" but I unlocked with the firmware with which I got the phone and it was the firmware before the latest one
so at my first rooting try I did no update to the latest firmware, but at all further tries I flashed the newest firmware 52.0.A.8.131 for my country and provider (H8314 Mobilkom A1, it´s for Austria)
I did every step from this guide:
booting into twrp never was a problem and also every time I did the fastboot command with the ...vbmeta.img (don´t know if this is still necessary but I did)
and here is always the same and first problem: a boot loop, so I rebooted into recovery: fix boot loop
after this no problem to boot into system and everything is working fine but no root (Magisk and root checker)
after I installed this it shows me:
1) Magisk is not installed (new version 19.3)
2) a newer version of the app is available (7.3.2)
sure I updated both the app and installed from twrp the 19.3 zip but still no success (again boot loop and fixed the loop from twrp)
I tried the complete procedure a lot of times, always with flashtool flashed the latest firmware, booted into system, than twrp a.s.o., I tried some solutions from this forum like patching the twrp directly with Magisk: https://forum.xda-developers.com/showpost.php?p=74368287&postcount=23 but no success
at least I tried to install SU but also no root
...I have no idea what I should try next so I hope you have some advices?
Click to expand...
Click to collapse
Magisk 19.3 is the issue, use 18.1 stable, or 19.4 beta
Beetle84 said:
Magisk 19.3 is the issue, use 18.1 stable, or 19.4 beta
Click to expand...
Click to collapse
:good:
1st try with 19.3 beta and its done, also first magisk version without boot loop - so much time wasted and so easy solution (if you know it)
...I am so happy, you don´t believe!
only one question: why is at the twrp dl location in the "package" where all the files in (linked in the twrp thread) a magisk version which is not working on xz2c?
b00rn said:
:good:
1st try with 19.3 beta and its done, also first magisk version without boot loop - so much time wasted and so easy solution (if you know it)
...I am so happy, you don´t believe!
only one question: why is at the twrp dl location in the "package" where all the files in (linked in the twrp thread) a magisk version which is not working on xz2c?
Click to expand...
Click to collapse
I did bundle 18.1 which should work and linked now 19.4 beta, which should work too.
Which bundled version didn't worked exactly?
MartinX3 said:
Which bundled version didn't worked exactly?
Click to expand...
Click to collapse
it was 18.1 also I tried a 14.x which was an advise in another thread with similar problems (boot loop) and the "new" 19.3
...so at least I tried with 3 different Magisk versions and thought the "failure" has to be an other reason, but I was wrong - I am only wondering that it seems nobody else had problems with the 18.1, I was not only searching in this forum also tried to find solutions with G, found some threads with the boot loop problem but close to nothing with rooting problems
b00rn said:
it was 18.1 also I tried a 14.x which was an advise in another thread with similar problems (boot loop) and the "new" 19.3
...so at least I tried with 3 different Magisk versions and thought the "failure" has to be an other reason, but I was wrong - I am only wondering that it seems nobody else had problems with the 18.1, I was not only searching in this forum also tried to find solutions with G, found some threads with the boot loop problem but close to nothing with rooting problems
Click to expand...
Click to collapse
At least 19.4 works at your side [emoji14]
That's the best case of possibilities

can't flash TWRP 3.3.1 - 3.0.2 works just fine

I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
RNZL3R said:
I'm having difficulty getting TWRP 3.3 working on my z3c. I'm not new to the process, and have done it a few times on a few phones. Right now my z3c has TWRP 3.0.2-1-z3c. I'm wanting to try the new Android 10 ROM that came out, but it requires TWRP 3.3 to work. So I got the TWRP provided in the thread. I'm flashing from Linux, so I did run
Code:
./fastboot flash recovery twrp 3.3.1-1-A10.0-z3c.img
When I reboot and hold the power down button it skips over TWRP and just boots the ROM I have installed.
Okay, so I downgrade to TWRP 3.0.2-1 and reboot...hold volume down...TWRP boots just fine.
Flash TWRP 3.3 again....no joy. It just boots straight to ROM.
Click to expand...
Click to collapse
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
Screwed badly with the systems to the point where I softbricked the phone, and had to revert to stock. Will try going straight to 3.3.1 instead now.
Edit: I used adb to go to fastboot (adb reboot bootloader), from there I tried all the different twrp images I have, including latest Android 10 one using the fastboot boot image.img (replace image by name of image, I name them A8, A9, A10 to match android version).
All of them booted, which means I can flash them without issues. I don't know which version I want to install though for now, and I don't want to be stuck again on a version that I won't be able to upgrade later on... so will probably go straight to A10 and Lineage 17 even if it's quite buggy.
liberteus said:
Same. Couldnt find a proper answer to this. Still have trouble with this? I'm on CR6.1, that's android 8.1 and I'd like to try later versions (lineage os or maybe CR7.0)
Click to expand...
Click to collapse
did you found a solution? i have the same issue...

Redmi Note 9 Bootloop to recovery - help needed

Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
ajadamjones87 said:
Hi all,
I have a rooted redmit note 9 that was running the stock rom (EU version i believe as i am UK based) perfectly well for several months until today when then latest over the air update installed and my phone is now stuck in a bootloop where i can only access the custom PBRP recovery (installed from when i rooted previously). I can also access fastboot. I have tried wiping all data and cache etc, i have tried reflashing the magisk patched stock rom that previously worked, i have also tried flashing vbmeta that i flashed previously but still no luck. This is my only phone so I really need to get it working again.
I was about to try re-flashing the stock rom with SP tool but it tells me the scatter file is invalid.
Not sure what else to try now. I also note that when i PBRP loads up it always asks for a password however i dont have a password on the device.
Please could someone suggest something i could try?
Click to expand...
Click to collapse
your devices is encrypted try flash other custom rom first then try revert to stock hope it help u out
Thanks very much for your response. Based on your advice i tried to flash the latest Kraken 11 Vanilla rom from this fourm, however after installing via TWRP now i can't even get into recovery anymore, just goes straight to fastboot.
Any other suggestions please?
I have now managed to get back in to TWRP and tried flashing lineage latest rom but still i am stuck in a boot loop taking me to fastboot this time.
Please can someone help suggest hwo i can get my phone working agian. At this point i dont care which rom i end up (custom or stock) with as long as i can get it to function again
If your device is rooted, you can NOT update the system using the OTA (over-the-air), or the device will be stucked in bootloop.
If your device is rooted, you need to update the system MANUALLY, using the fastboot or spflashtool.
I suggest to update the system using the fastboot.
Now, you need to flash the whole MIUI again, except userdata and you will have your device back.
For anyone with a asimilar problem i eventually managed to fix my issue by using miflash tool version 20180528 and flashing merlin_eea_global_images_V12.0.10.0.QJOEUXM_20210413.0000.00_10.0_eea_c4a9d5d7fc fastboot version which i downloaded from the xiami site.
I had to try this multiple times because the extraction of the file did not seem to be correct on the first attempts.

Categories

Resources