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.
Related
Hello
Okay i flashed my mobile with new OTA
after i try to install magisk but getting error that "Magisk manager stopped" after zip downloaded
i dont know why that happening
after zip downloaded getting black window then pop up shown about error
i think it cant patch boot img properly
in my old rom it works properly, but after flashing it did not work
thank you....
Try installing it in recovery
I sometimes get that majisk stopped toast on just about any ROM and just about any majisk release. I just ignore it. I have no idea of the what or why. Haven't noticed it affecting anything.
Yes. It's happening to me too. Does it work if I flash this update with twrp?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
Did you read the responses above? It was already suggested to try that.
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
rabin69x said:
Yes. It's happening to me too. Does it work if I flash this update with twrp?
Click to expand...
Click to collapse
I always flash builds from TWRP.
Eng.Raman said:
After installing magisk 15.2, magisk manager 5.5.3 stuck at the splash screen for me. What's wrong ?
Click to expand...
Click to collapse
Having the exact same issue on a pixel xl. Tried on 7.1 and 8.1, both with the same result.
I never use manager. Always TWRP, and can people start searching and using the support thread for questions, logs, and bugs instead of keep making a hundred useless threads of the same thing, can't install, can't install modules, etc. That's what support thread for. Thanks.
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
hungragezone said:
I am using MIUI 7.12.28 (latest) on Redmid 3S and I can flash magisk 15.2 using TWRP normally but when the phone restart, i go to magisk manager and it shows that magisk is not installed
I tried flash many time but the same problem happen
When i tried to flash magisk 14.0, it works. what is the problem here o_o
Click to expand...
Click to collapse
If updating, why not use direct method?
madbat99 said:
If updating, why not use directethod?
Click to expand...
Click to collapse
No, i am flashing from start
I just flash new miui (full wipe, factory reset)
and i also try to update from Magisk manager but when the flash screen appear, magisk manager force close (I already tried to clear data of Magisk manager and tried to update again but no success)
Now i can have root with Magisk 14.0 but when i tried to update to 15.2 using TWRP, it just disappear lol
(Flashing normally, no error, restart phone, go to magisk manager -> magisk is not installed )
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
anykiel91 said:
I have installed the latest pie stable on my op 3t. However it would never boot when installing with Magisk.
So for now I have installed it without Magisk and got it to work ok. However now I'm having same problem installing Magisk.
I can install and uninstall it from twrp latest, however when it's installed, it is just stuck on the initial screen with oneplus logo. And never makes it to the circle/dots screen.
I tried using 19. 2, 19.0 Magisk and 18.1.
Is there any logs I can pull or did anyone else have this issue?
Are there any other safe root solutions to try instead?
Any help would be appreciated
Click to expand...
Click to collapse
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
I couldn't get it to boot up before firstboot. So I went with normal nonroot flash so I could use the phone.
I figured it would not matter if I installed Magisk later.
I might try to reflash everything over again
ast00 said:
I always flash Magisk BEFORE the first boot. Also no custom kernels, especially not AFTER Magisk flash.
Is this what you did as well?
Click to expand...
Click to collapse
topjohnwu says that you flash custom kernel after flashing Magisk
Immortalis said:
topjohnwu says that you flash custom kernel after flashing Magisk
Click to expand...
Click to collapse
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
ast00 said:
Never had this problem until today. So I did some testing.
Magisk 19.1 causes it to get stuck at the OP logo.
I flashed uninstaller, reflashed the ROM, flashed Magisk 19.2 and it worked.
Are you using the 19.2 zip?
Click to expand...
Click to collapse
Yes, I had problems with 19.1 too, that the phone sometimes (if not always) would boot itself into fastboot mode instead of system, so at that time I moved temporarily to canary builds
I used this zip instead and it worked. Not sure what's different but I'm good now
https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932
Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX
Why do need the boot.img for root ?
I never used it for root my device.
khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?
Since Jul 9, 2019.
Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Does this work for the global version??
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.
lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA
Flashing this on International breaks the WiFi. Does anyone have the international version?
Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..
Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".
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
We can root in an easy way without unlocking the bootloader
I think this method works with all versions realme
Don't forget to activate OEM unlocking From Developer options
1-You must install drivers:
Realme USB Driver - Realme Firmware
From here you can download USB driver for realme mobile phones. The given USB driver is supported only for the Windows operating system
realmefirmware.com
Realme USB Driver - Google Drive
drive.google.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download SPD Flash Tool R26.21.2801 - Official SPD/Unisoc Flash Tool
Download SPD Flash Tool R26.21.2801 to Flash Stock Firmware on Spreadtrum Smartphone and Tablets.
spdflashtool.com
2-You have to unpack the ROM using SPD_Upgrade_Tool
https://www.gsmmafia.com/ Here are the ROMs
After completing the extraction, make a patch for the boot With Magisk-v24.3
You will get a rooted boot file Replace it with the old boot
In the end, flash the device and you will notice that you have the root
I am attaching an explanatory video
not the group you looking for but thanks for sharing this
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
thanks.
gianonceu said:
not the group you looking for but thanks for sharing this
Click to expand...
Click to collapse
How can we create realme c25y group in xda
Excuse me I want to ask, will this delete all internal data?
Doly12 said:
Excuse me I want to ask, will this delete all internal data?
Click to expand...
Click to collapse
yes.
Yo, how did you flash it?
Biglet0w said:
Yo, how did you flash it?
Click to expand...
Click to collapse
spd flash tool
turn off the phone. After that, press and hold the Volume Down button and at the same time connect the phone to the PC using the USB cable. You will see that the Upgrade Download program was able to identify the phone and the flashing process will start automatically.
Hi
When I try to call the emergency numbers, I can't, it says that the credit is not enough to make the call
I rebooted and flashed according to the video you posted, but it didn't work
I changed the chip but the same problem remains
Can you give me a solution to this problem
my phone recognize sim but when call people it said cellular is not available, when i use my sim in other phone it work normal, i try flash the rom again but spd tool said error !!!GSM Cali in phone is not calibrated.Reserved[7]:0x00000000,[ID=0x2] pls help
i have rmx3269_11_A.18 and its not on gsmmafia this build number what i do please help
Can i install twrp from c25 or c25s
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Reyproject said:
Hello! I would like to ask for a few questions.
1) At the time of the post, the Magisk version is v24.3. Can I use the latest Magisk v25.2?
2) I've updated my phone to A.41, will downloading A.29 still work since the latest ones aren't downloadable?
Click to expand...
Click to collapse
1) I don't think so.
2)Yes.
JA sunny said:
1) I don't think so.
2)Yes.
Click to expand...
Click to collapse
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
I think you need to have the bootloader unlocked to boot into custom img
elokuba said:
Can i install twrp from c25 or c25s
Click to expand...
Click to collapse
Don't
Reyproject said:
Successfully rooted the phone. Not updating to Magisk v25.2.
This is my second time flashing since I went into a bootloop.
The first flash, I installed Audio Compatibility Patch Magisk Module, rebooted, speakers were now always on mono, installed Audio Mod Library module, still the same. Tried uninstalling ACP by going through the install prompts when flashing and updated Magisk to v25.2 at the same time. Once I rebooted, it went to bootloop.
Flashed the whole thing again, back with root again. I'll be installing stuff one by one so I can know the cause.
Too bad there's no custom recovery. TWRP or OFRP would be nice.
We can flash recovery using Flashify right? So why hasn't anyone build a custom recovery port yet?
Click to expand...
Click to collapse
Can you please check if this works
File
XDA forum
JA sunny said:
Can you please check if this works
File
XDA forum
Click to expand...
Click to collapse
What does it do?
Reyproject said:
What does it do?
Click to expand...
Click to collapse
removes the black bar on the notch/punchhole side that you see on some apps and games when the phone is in landscape. I'll root my phone if this works.