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
Related
Scroll down over this post to see anwer!
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
gulp79 said:
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
Click to expand...
Click to collapse
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Padlite said:
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Click to expand...
Click to collapse
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
gulp79 said:
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
Click to expand...
Click to collapse
If I only flash Magisk 16.4, then phone shows "Powered by Android" and instantly reboots into stock recovery.
Only way to get it back booting, is performing fastboot flash boot boot.img from stock dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global image
I read somewhere about official and unofficial bootloader unlock. I didn't unlock the bootloader myself. Maybe it has something to do with it?
PS: Anyone had any luck using Magisk with MIUI 9.5.13?
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
punk84z said:
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Click to expand...
Click to collapse
I just tried that. Uninstalling and re-installing v16.7. Although it seems now it's doing a few more steps, I'm still getting the recovery bootloop.
Install log screenshot attached.
gulp79 said:
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
Click to expand...
Click to collapse
Exactly that. Maybe we'll need to wait for a supported Magisk version. I'm still wondering what's the difference between our Mi8's that some can get Magisk working and some not. ?
I am running Magisk stable and tmiui 10 from Xiaomi. Eu without any problems.
I have a Mi 8 se and i install the eu rom boot the phone , reboot to twrp wipe and factory reset and installed magisk 16.4 .this is how works for me
i have the same problem too..when using china stable rom 16.7 magisk can be installed successfully tried many times...
flashing global version seems to have this issue...
tried all this steps too but no luck in global rom...
Padlite said:
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
Click to expand...
Click to collapse
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
-fluffy- said:
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
Click to expand...
Click to collapse
Well maybe the critical step is to wipe everything, including System.
Did you Format anything instead of Wipe this last try?
Also, could you please share a link from that working MIUI rom?
Thank you!
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
Is Google Assistant ("OK Google") working for you now as well?
I just flashed magisk v16.0 over the Miui 8.7.26 build and it booted without issues.
japancakes said:
Is Google Assistant ("OK Google") working for you now as well?
Click to expand...
Click to collapse
I just checked and no. If I go to Google Settings -> Voice, Voice Match is disabled because "This feature is currently unavailable for this language". Even though it's set to English UK. Maybe there is some Magisk Module to enable it?
Thanks, followed these steps and it got magisk going on the recent global release. Only difference was i had to use fastboot erase userdata.
Padlite said:
Scroll down over this post to see anwer!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
Click to expand...
Click to collapse
Hey guys im a toal newbie to this whole flash theme but Ive purchased a mi8 and i would like to use GooglePay and so on, could someone give me a step by step tutorial , how to install all this stuff on my device ?
Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
well i didt not flash dm-verity an mine pass saftynet
Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Nuzzlet said:
Here is what I have done:
1. Boot into TWRP recovery
2. Flash OOS 9.0.3 Beta 11 followed by TWRP and Wipe Dalvik Cache
3. Reboot Successfully to android
4. Boot back into TWRP and flash Magisk 18.0 (I also tried 18.1, same result)
5. Bootloop
I've done this multiple times, each time I was able to get back into android before flashing Magisk.
Thank You for your help, much appreciated.
Click to expand...
Click to collapse
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
TLX317 said:
This might go without saying but after flashing Magisk are you also wiping Dalvik?
Click to expand...
Click to collapse
Yes I am
mixlex said:
I could be wrong but I do it slightly differently.
1. Boot into TWRP.
2. Flash rom, flash TWRP
3. Reboot TWRP, flash magisk.
4. Reboot system
Works for me.
Click to expand...
Click to collapse
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Nuzzlet said:
Yes I am
So I finally made it work by flashing with "Blue" TWRP. I still don't really understand the difference between the official TWRP. Whiel in loop looping after installing magisk, I went back to TWRP, flashed Blue TWRP and it booted. Wen't back intro Blue TWRP and flashed Magisk 18 (Not 18.1, thought that might have been why) and it worked. It confused me because I have successfully flashed magisk with the other TWRP before so I really don't know what fixed this.
Thank you for your help. I think I flashed me rom over 30 times yesterday getting this to work.
Click to expand...
Click to collapse
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
a4abbas said:
Hi could you please provide me the link to the blue TWRP you have used? I'm stuck in the same situation as you. Pls help
Click to expand...
Click to collapse
At the moment I'm just using regular TWRP actually. Havnt used blue since I switched the beta builds. I actually remember having trouble finding a download for Blu spark. What are your issues?
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.
Hi all, as the title implies, I'm a newbie to all this. I tried to root my phone using an online guide on how to root xiaomi mi 9 using TWRP and Magisk. I faced some problems but eventually everything was done as the tutorial said.
Here are the exact steps I've done...
- unlocked the phone via Mi unlocking tool
- started fastboot and installed TWRP 3.3.1-0 ( I installed a version first that didn't start when I pressed both power and volume up, then installed the 331-0 version that worked)
- inside TWRP i installed Magisk 20.4
- The phone restarted but never reach the system. It hangs for sometime on android screen then restarts again and then brings me again to TWRP
I spent quiet sometimes reading online solutions but nothing worked for me...
I tried installing Magisk uninstaller.zip nothing changed. tried wiping cache. Tried installing magisk 20 and 20.3
some solutions recommended installing Magisk 19 0r 17 but they both ended up with error for me.
Please help. I'm on Android 10 with MIUI 11
Never had any problems with magisk What TWRP version have you used?
The steps are the same:
-Unlocked phone.
-TWRP.
-Flash magisk zip (you can install magisk manager, then download latest official magisk zip from it and then flash downloaded zip from TWRP).
-reboot.
Anyway you can fix your system by:
-wipe cache/dalvik.
-FORMAT data (with yes).
I don't think you need this 2 first steps for flashing fastboot ROM but it won't hurt.
-Flash official fastboot ROM in fastboot mod, using mi flash tool or included batch/bash scripts (don't lock your device if you don't want to, choose the right option when you flash, with or without "lock").
Mi 9 Fastboot V11.0.5.0.QFAMIXM Global
Mi 9 Fastboot V11.0.8.0.QFAEUXM EEA
You will loose all your data, apps and settings.
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
F.Ashour said:
Thanks for your help mate...
I'm using this TWRP version..
----//dl.twrp.me/cepheus/
Strangely enough, my phone started after flashing Magisk-uninstaller-20191011.zip I'm sure i tried this before and it doesn't work.
Anyway, all my app and data are gone. I still want to root though, can you help me? what version of TWRP and Magisk i should use?
Click to expand...
Click to collapse
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
antonio52 said:
Use twrp-3.3.1-62-cepheus-mauronofrio.img.
Magisk-v20.4.zip
Click to expand...
Click to collapse
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
F.Ashour said:
Thanks for your time mate...
I tried this twrp and magisk your mentioned. same issue. boots back to twrp never to system. Any solutions?
Click to expand...
Click to collapse
I would try flash latest fastboot ROM as i said before it will reflash almost everything And then flash magisk by installing magisk manager and download latest magisk zip through it and flash it with twrp-3.3.1-62-cepheus-mauronofrio TWRP
Sometimes first flash of TWRP don't work, just flash it ones more by fastboot flash twrp twrp-3.3.1-62-cepheus-mauronofrio.img from your pc.
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Lemmy554 said:
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Click to expand...
Click to collapse
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Almasd said:
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Click to expand...
Click to collapse
In Magisk Manager you have to "Tap to start SafetyNet check".
Oh I see. Thanks. It's ctsProfile: true. (Now I'm on stock rom with root)
Almasd said:
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Click to expand...
Click to collapse
How to unlock ur bootloader plz suggest me.
Risul49 said:
How to unlock ur bootloader plz suggest me.
Click to expand...
Click to collapse
I don't have RMX1993(EX) anymore. But below might help you.
If you are on ColorOS (Android 9) or RUI1 (Android 10) then you can directly follow the bootloader unlock tutorials on the internet. But if you are on RUI2 (Android 11) then you need to downgrade to RUI1 first.
I also did the same procedure.
But below is for RMX1901CN Realme X device procedure. I believe it would give you a hint.
1. I found Rollback_RMX1901_11_OTA_1190_all_EyyIUd8KYxPI.ozip (for Chinese version) firmware from Realme X Official Telegram group.
2. Then I opened it from the file manager and the device rebooted automatically and the downgrade firmware was installed. After that, I unlocked it with the DeepTesting app for RUI1 with instructions that I found on the internet.
Also, you might try this method: https://c.realme.com/in/post-details/1476520599785316352
Also, comments on this post might help (I have no idea Realme X2 Pro instruction is works for your device but JFYI): https://c.realme.com/in/post-details/1478098096796815360