Related
Hi.
This is my first post, I hope i'm in the correct forum.
I have a friend whom I requested to Root, Flash TWRP and Install LineagOS and GAAP on my OnePlus One phone.
He successfully flashed TWRP and installed LineagOS & GAAP but could not root my OnePlus One using SuperSu. He mentioned permission issue trying to root.
He went back to his country, so I am stuck trying to root my phone.
I would like to root my LineagOS (formally OnePlus One) using SuperSU.
I have downloaded/copied the latest SuperSu zip file into the Phone Sd/Download folder.
I went into custom recovery (TWRP).
Click on the Install button and verified I can see my SuperSu zip file.
Since this is my first time performing a phone root, I did not click SuperSu zip to install, until some experts can assist. me.
Just a few (Q's).
Questions:
a) Should I run any preliminary steps prior to clicking install SuperSu.zip?
b) Since I have LineagOS, GAAP apps already installed, will they be wiped after rooting SuperSu. If (Yes), any software available to backup/restore LineagOS & GAAP prior to the root process?
c) My friend mention “Permission problems with OPO”. Are there some options to open OPO and allow rooting SuperSu?
BTW: I do have the adb & fastboot installed if I need to enter some commands to get this done.
Thanks.
Tom.
a) No.
Download flashable supersu zip and flash it from here and flash it via TWRP https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
b) No.
But you can take nandroid backup through twrp in case something goes wrong.
c) As far as I know there is no problem with "permission" for rooting.
Happy flashing
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
tomx2x said:
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
Click to expand...
Click to collapse
I think I'm missing something. Did you tried any other method to root? I recommend a clean flash.
1. Download Sultanxda's unofficial lineageOS from here
2. Download Gapps from here. ( ARM-7.1-nano)
3.Download SuperSU from here
4. [Optional] take back up of your apps (No need to back up medias like photo,video,etc)
5.Got Recovery>wipe>advanced wipe
select system,data,cache and dalvik cache (DO NOT SELECT INTERNAL)
6.flash the zips you already downloaded in this order - ROM- Gapps - SuperSU
do not wipe anything after this step
7.Reboot
1st reboot will take some time (10-20 min ). Do not interrupt this process.
PS: I totally recommend Sultan's LineageOS over official LOS. You can actually feel the difference in smoothness and performance. Especially the Camera.
Feel free to check device specific forum for OnePlus One
Happy flashing!
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
tomx2x said:
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
Click to expand...
Click to collapse
Yes. Copy all 3 zip (rom,gapps,supersu) to you phone.
Let me know how it goes..
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
tomx2x said:
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
Click to expand...
Click to collapse
Can you send me a screenshot of supersu app?
I'm using the exact settings and I don't have any problem at all.
Do not let TWRP install supersu.
@psxda97
As you know the Supersu is a zip file. When I open/ then extract, the display will show folders & their contents.
I have attached all the folders & contents from supersu extract for your review.
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Here is the website link where I downloaded SuperSu 2 days ago.
" https://download.chainfire.eu/1114/...r&utm_medium=referral&utm_source=DonanimHaber “
tomx2x said:
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Click to expand...
Click to collapse
I meant this
Edit : So you've no supersu app on you phone?
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
tomx2x said:
[MENTION=7046372]
Should supersu app be on my phone after installation/rebooting?
Tom.
Click to expand...
Click to collapse
Yes.
Go to recover and flash it one more time
Then go to Advanced on twrp and select copy log (without kernel log).
Log will be on root folder of internal. attach the log in your next post
Also send me the screenshot of your about phone settings.
You're still missing something.
tomx2x said:
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
Click to expand...
Click to collapse
Go to system settings>developer options>root access and set it to "apps and adb"
If you flash the SuperSU.zip in TWRP on your device then you should have root.
I think you misunderstood from the beginning, did you download the SuperSU.zip and then extract it on PC and then try to install it? If so, that was completely the wrong thing to do. You might have to remove what you've done so far and then try again from a clean start, you might gave to flash your stock firmware to get a clean start.
Have you looked into whether you need normal SuperSU or whether you need systemless SuperSU?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Additional info provided - Anyone with advice.
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
The problem might be in the LineageOS ROM that you're using, I've seen others have this issue on other devices using LineageOS.
I don't recall what some of the solutions were.
@Sam Nakamura is pretty knowledgeable about the OnePlus devices, maybe he has some useful input.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
I haven't used LineageOS yet so I'm not familiar with its details, I was pretty sure you'd know though. [emoji106]
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Sam Nakamura.
Thanks for the info.
I have previously executed the steps in the order you posted. I was just asking if other sequences to flash these apps were plausible.
With the help of member psxda97, he documented similar steps 1-7 for me. (Please read Post #4 on this thread and my results in Post #7). It's basically a snapshot of what you posted regarding the order seq.
Unfortunately, my phone still did not root after applying the ROM, GAAP & Supersu in this order. I'm not sure why the root is declared successful in TWRP, and the phone remain un-rooted.
Do you suggest I rerun steps1-7 from Post#4 and include your echo statement before installing supersu?
The LineageOS extras, (you mentioned) has a built-in root.
I now have LineagOS from Sultanxda's installed on my phone. It is highly recommended by XDA members over the official LOS, for it's smoothness and camera enhancements. Sultanxda' release is 06/25/2017.
LOS extras has a release date of 06/21/2017. My only issues, whether to choose LOS extras. I will subsequently get the next “Official” LOS release for 6/25 and loose LOS Sultanxda installation.
Tom.
Tried Installing LOS extras 14.1
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
tomx2x said:
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
Click to expand...
Click to collapse
Did you choose the correct arm(32) version of lineageOS su? I'd try the following:
Backup all partitions with twrp so you can return to your set-up later on..
Wipe everything except internal storage
Flash rom, (custom kernel), gapps and su
Boot up and check if it's working now
If not restore your backup and check next point
Alternatively:
Have you tried superSU with forced systemless via twrp terminal (by the way, if done correctly there shouldn't fallow a output with this command line..)
Flash supersu from here:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I never had issues with the beta but you can also use the stable version, downloads on post 1
Using Magisk as root and root management tool
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashable zip via twrp, if successful go to magisk settings, and check superuser and read the rest of Magisk's potential on the linked thread, my preferred method as it allows you to hide root from certain apps which deny service to rooted devices..
Important, it's not a good idea to flash lineageOS su, then supersu, then magisk after each fails, at least restore your clean boot partition from twrp or flash the boot.img from within your rom zip... Best would be clean of course - but as you have a backup of your previous system you can play around and make errors...
Sent from my OnePlus 2 using XDA Labs
Hey all,
Just purchased a LG U2 and now trying to make it work in the way i want it.
All informations here seem very old, so I wanted to open an update thread, with all what is possible on th lgu2, while
I found only very outdated informations...:crying:
So far:
First I setup the watch with AW2.0, after that flashed twrp 3.1.1.0 and supersu wear 2.82
I managed to get busybox installed and wanted further add Xposed.
There my problem starts, flashing xposed didn't work out.
So right after that, I switchd to Magisk root, to try work with the modules supplied.
(Steps -> use script UnSU, after that flash boot.img again, than flash MAgisk through twrp)
But after that the same with the modules. I try to install busybox, magisk tell me its no magisk module (i've downloaded the module and pushed it on the sd through adb, while the download button isn't reachable in magisk dialogue menu)
in twrp the module tells me there is no magisk installed.
so how can we go on from here? is there a way to make it all work?
did somebody try to change dpi and download the module directly through magisk? does it work?
also if somebody could help with an updated list of sideload able full android apps?
would need an email that can handle at least two accounts directly on the watch (please not advice outlook, its working from the phone i know)
thanks to all in advance
sebj84 said:
Hey all,
Just purchased a LG U2 and now trying to make it work in the way i want it.
All informations here seem very old, so I wanted to open an update thread, with all what is possible on th lgu2, while
I found only very outdated informations...:crying:
So far:
First I setup the watch with AW2.0, after that flashed twrp 3.1.1.0 and supersu wear 2.82
I managed to get busybox installed and wanted further add Xposed.
There my problem starts, flashing xposed didn't work out.
So right after that, I switchd to Magisk root, to try work with the modules supplied.
(Steps -> use script UnSU, after that flash boot.img again, than flash MAgisk through twrp)
But after that the same with the modules. I try to install busybox, magisk tell me its no magisk module (i've downloaded the module and pushed it on the sd through adb, while the download button isn't reachable in magisk dialogue menu)
in twrp the module tells me there is no magisk installed.
so how can we go on from here? is there a way to make it all work?
did somebody try to change dpi and download the module directly through magisk? does it work?
also if somebody could help with an updated list of sideload able full android apps?
would need an email that can handle at least two accounts directly on the watch (please not advice outlook, its working from the phone i know)
thanks to all in advance
Click to expand...
Click to collapse
Ok i did a fresh flash.
i see my fault was to install busybox the first time after installing supersu.
did it this time without and mgisk works so far fine. granting access for total commander no problem.
but now another thing. i installed now busybox from the repos in magisk, he say installation successful, but the module isn't there after reboot?
anyone got the same?
sebj84 said:
Ok i did a fresh flash.
i see my fault was to install busybox the first time after installing supersu.
did it this time without and mgisk works so far fine. granting access for total commander no problem.
but now another thing. i installed now busybox from the repos in magisk, he say installation successful, but the module isn't there after reboot?
anyone got the same?
Click to expand...
Click to collapse
another try. i switched back to supersu wear 2.82, installed stericsons busybox. works.
installed xposed sdk25 via twrp, says success, but after reboot xposed installer says no active framework.
i used a systemless framework... will search for the link again.
anybody got it done this way?
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Ahh... Me too. I'm sure this somewhere in the extensive Magisk coverage here. Is it too lazy to ask for a pointer to how to
--- downgrade the manager? That's probably easy if I know where to get the apk. Which version should I go for?
--- install the new magisk over the existing version, preferably without wiping the phone?
Sure, I'll search. But it is quite a while since I did anything with magisk, or anything that involved flashing, and I feel a bit lost.
Thad E Ginathom said:
Sure, I'll search. ... ... ...
Click to expand...
Click to collapse
OK, so there's a wiki and stuff. Whilst being babied would be nice, people have better things to do, and I guess I'll just start in reading that wiki and... stuff.
SOLUTION
Deathnes said:
I got my phone (SM-G950F a.k.a Samsung Galaxy S8) rooted about a year ago or so...and since, i update MM whenever needed but this time when i tried to update it, it says this:
Unsupported Magisk Version
This versio of Magisk Manager does not support Magisk version lower than v18.0
You can either manually upgrade Magisk, or downgrade the app to an older version.
I cannot go into the app cause that message will pop up and after i press ok it closes by itself!
Any ideea on how to fix this? If i have to re-root the phone please do explain..even then i didn't knew for sure how i did it, but i did it..
Thanks in advance!
Click to expand...
Click to collapse
Delete the Magisk Manager app as you would do with any other, download the proper version in .apk (check the official thread) and install it.
In the thread, under Sources, you have the link to the GitHub repo. Scrolling down you will find the README.MD file and the link to the Downloads page where all past releases are available.
From https://www.xda-developers.com/how-to-install-magisk/ you can read:
The Magisk framework is now installed on your device. To manage it, you’ll need the aptly named Magisk Manager. This is what will allow you to install modules. Download the latest Magisk Manager APK here and make sure you have “Unknown sources” enabled in the Settings. Install the app and open it up.
The Manager app allows you to adjust root settings and also install modules, which are installable mods. The app doubles as a repository for a bunch of great modules that can easily extend the functionality of your device. Using the Manager app is an important part of getting the most out of this root method.
Click to expand...
Click to collapse
That is, the app Magisk Manager is independent from the Magisk framework you have installed. Deleting the app does not affect Magisk.
vomae said:
... ... ... the Downloads page where all past releases are available.
Click to expand...
Click to collapse
I'd reached there, although not done it yet. As you say, my phone is still working, Magisk is still working, it is just the manager app that needs dealing with. None the less, I appreciate your time and effort. You paint a clear picture for others who come this way.
Thanks.
Open the updated app & ignore the error, then checkout the option showing update magisk(not manager), go for it, dont select any preservations & click on direct install(which is recommended by app itself).
Flashing of the update will begin, then after reboot your problem is solved.
Magisk Manager has many improvements and features over the last year...
"Can't load Android system" and "Factory data reset" tried and does not work
Hi all,
I bought a Pixel 3a, unlocked the bootloader, upgraded it to Android 10, and then tried to root it with Magisk. I must somehow have missed a step because now the phone only boots to:
Android Recovery
google/sargo/sargo
9/PQ3B.190801.002/5674421
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
If I "Try again" I end up in the same place after a long time with the Google logo and a reboot. If I "Factory data reset" I also end up in the same place.
My desktop has adb and fastboot, and was able to access the phone until the failed attempt at rooting. Now it does not detect the phone despite the system "bleeping" as if it has found a new device:
>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
>adb devices
List of devices attached
Is there a way out of this mess?
FD
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Uzephi said:
You're still on P by what recovery says. 0801 image. PQ3B is P. You want QP1A. Please try downloading the recent Q image and follow the official instructions from Google in the link and try again.
https://developers.google.com/android/images
Click to expand...
Click to collapse
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Frederick Davies said:
Thank you very much! Using the flash-all script I have managed to get my phone back. I have flashed the original Android 9 the phone came with.
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I followed this guide. it's for a pixel 3 but it's exactly the same for a 3a. There is no TWRP for 10 so doing it this way is the only way for now.
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Just use magisk to patch Android 10 boot IMG and Flash it and your rooted on Android 10
Frederick Davies said:
Now, one further question, are there some good (as in unlikely to brick my phone again) instructions on how to root my Pixel 3a? I believe that Android 9 is preferred when using Magisk to Android 10, and I do not mind staying with Android 9, but I would like some instructions on how to root it without bricking it again.
Again, thanks for your prompt reply.
Yours,
FD
Click to expand...
Click to collapse
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Watch this video and you shouldn't have any problems
sic0048 said:
I have created a (IMHO) very thorough quide on how to root your Pixel 3a. It walks you through rooting with both Android Pie and Android 10 with very clear and precise steps. If you have any questions about it, feel free to post in that thread or reach out to me via a direct message.
Click to expand...
Click to collapse
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
sic0048 said:
There is no limitation on using Magisk or rooting under Android 10. The only thing you cannot do with Android 10 is use TWRP, but that isn't a deal breaker. TWRP is good for making backups of your OS, but as you have found you can still recover from just about any situation using the Google factory images, so while a backup might be beneficial at times, it isn't a necessity. Personally I would definitely recommend using Android 10 because Pie isn't being updated by Google anymore, so you are going to be behind on security updates, etc if you stick with Pie.
Click to expand...
Click to collapse
I am going through all this rigmarole to be able to install XPrivacyLua through the Xposed Framework, but the instructions for Xposed (https://www.xda-developers.com/xposed-framework-hub/) seem to indicate you need TWRP as a requisite, hence I think am stuck with Android P (9.0).
On the other hand, I get conflicting information as to whether Xposed for Magisk does (https://www.xda-developers.com/xposed-framework-hub/) or does not (https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) pass SafetyNet. Most confusing...
FD
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
AndDiSa said:
There is no need to install or boot into TWRP (btw. there is even no working TWRP for Android 10 yet) to install Magisk. It's sufficents to install Magisk Manager on your phone and patch the boot.img extracted from the factory image. Just follow the instructions which have been quoted here in the thread already.
Click to expand...
Click to collapse
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
TWRP doesn't work on Android 10 at this point so you can't flash it.
Frederick Davies said:
Dear AndDisa,
As I said, I am rooting my Pixel 3a because I want to install XPrivacyLua, which requires the Xposed Framework; and to install Xposed with Magisk, it lists TWRP as a pre-requisite (see "Method 2: Magisk" in https://www.xda-developers.com/xposed-framework-hub/). Since it seems there is some kind of reluctance to use/install TWRP in this thread, I am asking why that is so. I understand it is possible to install Magisk without TWRP, I am just asking "why?"
Again, thank you all for your help.
FD
Click to expand...
Click to collapse
If you read closely in the guide sic linked, he does state the TWRP method is only for P because you can't use TWRP on 10. It is the way partitions are handled in 10 where you really can't read your internal storage and it would have to require a code rework. Until that's done, no TWRP.
Edit: quote from twrp developer about it. https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
https://github.com/ElderDrivers/EdXposed/pull/354
https://github.com/ElderDrivers/EdXposedManager/releases
You can flash xposed without TWRP. Just install edxposed by downloading and installing through magisk and install the edxposed manager. You don't need TWRP
Frederick Davies said:
Very detailed indeed, but I still have a question: in your instructions you seem to boot into TWRP to install Magisk, but you do NOT install TWRP itself, just boot it for the installation of Magisk. Is that correct? Why?
FD
Click to expand...
Click to collapse
As other have noted, TWRP does not work with Android 10. However, I also wanted to answer your question because it is valid.....
With Android Pie (9), you cannot permanently install TWRP unless you first flash a custom kernel that supports LZMA compression. Using the stock kernel, you can load TWRP using ADB and use it just like normal, but when you reboot the phone TWRP will not be loaded anymore. My instructions are about rooting the phone and not about installing TWRP permanently on the phone and therefore I provided the simplest method to accomplish that goal.
Most custom kernels have been updated with LZMA support, but you should really read the TWRP thread for more information on how to permanently install TWRP on Android Pie
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Frederick Davies said:
Dear All,
Thank you for all your help and explanations concerning my questions.
I have now rooted my Pixel 3a running Android 9 following the instructions supplied (no TWRP installation), and It seems that Magisk is installed and happy (at least it thinks it is and FX has root access), but I am afraid that EdXposed and XPrivacyLua are not working as expected.
After Magisk, I installed the "Riru - Core" and "Riru - EdXposed (YAHFA)" modules. I then installed the "EdXposed Framework (YAHFA)" (giving the EdXposed Installer superuser privileges; EdExposed reports it is installed and active), and the XprivacyLua module inside it. But now Magisk complains that the SafetyNet checks are failing (this coincides with installing XPrivacyLua, but it is the only module I have in EdXposed), and XPrivacyLua is not actually blocking anything at all (that is, even when I supposedly block access to some functions, the apps just go ahead and use them).
Why do I get the impression Google does not want people to root their phones?
Yours,
FD
Click to expand...
Click to collapse
It is most certainly the things you have installed that are breaking the SafetyNet check. I don't know anything about XprivacyLua, but I would assume there is a support thread here on XDA for it. I would read that support thread and see if there is a solution to the Safetynet issue.
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Frederick Davies said:
Dear All,
OK, I have now rooted my Pixel 3a: I am running Android 9, and I flashed Magisk (Magisk Manager version 7.4.0; Magisk version 20.1) without installing TWRP as per the instructions. Then I installed the Riru - Core (version 10) and Riru - Ed Exposed (version 0.2.8_beta) modules, which allowed me to install EdXposedInstaller (version 2.2.5). I am currently running Xposed Framework (version 90.0-0.2.8) with XPrivacyLua (version 1.25).
The result is that XPrivacyLua is working with a few caveats: the SafetyNet Check fails both the ctsProfile and basicIntegrity checks (this is triggered by XPrivacyLua, not (Ed)Xposed), and when I limit access of WhatsApp to the Contacts list, there are constant errors whenever WhatsApp tries to read it (though it seems to work as expected). Also, the Contacts list keeps disappearing from the Contacts app itself, despite WhatsApp actually seeing those contacts in there (go figure).
Other apps that require root (like FX) are working as expected.
In the end, I have decided that since I am not interested in using my mobile for Google Pay, I will have to live with it as it is now, but I have a couple of points for others that may want to follow in my footsteps (this is not necessarily related to the method of rooting; those who helped me here are certainly not at fault for the following):
1. XPrivacyLua is in no way as capable and easy to use as XPrivacy was (XPrivacy is the main reason why I am rooting my phone). If I could install Android 4 on my Pixel 3a, I would do so and go back to XPrivacy (my venerable Nexus 5's second battery is shot, so I had to get new hardware). There is nothing in Android 9 that I actually need that was not there in Android 4.
2. We really need a Nexus Toot Toolkit for Pixel phones. The multitude of versions and steps required in rooting them successfully is too much for those like me who will root their phone for one or two apps and then leave it as it is. I know that these forums are really for tinkerers who want to extract the maximum from their hardware, and hence my point of view is not representative here, but I just want a mobile that will not spy on me, the rest is irrelevant to me.
I guess I will have to open a thread in the XPrivacyLua forums to see if I can sort out my problems, but I would like to thank you all for your help in getting me here and answering my questions (no matter how pointless they may have seemed).
Yours,
FD
Click to expand...
Click to collapse
Cool story bro
My phone is rooted with Magisk after installing TWRP recovery and it's working fine except banking apps which do not run due to rooted phone
I don't use functions of rooted phone so much, only in extracting whatsapp keys to backup my whatsapp chats etc
1) Can I uninstall/unroot Magisk anytime and reinstall/root again smoothly whenever the need arises?
2) Does installing/uninstalling root wipe data?
3) I saw following para in https://magiskmanager.com/uninstall-magisk
Your phone will be rebooted automatically. Don’t worry it is normal
That’s it! You have successfully uninstalled Magisk from your phone.
This process will completely delete all the files from your phone, and you don’t need to worry about anything.
Click to expand...
Click to collapse
What's meaning of "This process will completely delete all the files from your phone" here?
Thanks & regards,
Maria.
AFAIK any tampering of a phone's Stock ROM can get detectected by banking / payment apps - if they want to. IMO the very only method to remove all traces of modifcations applied to phone's Stock ROM is to re-flash phone's Stock what in turn causes the loss of all user data stored on phone.
1) Can I uninstall/unroot Magisk anytime and reinstall/root again smoothly whenever the need arises?
Yes.
2) Does installing/uninstalling root wipe data?
No. As long as you're not locking/unlocking your bootloader, you should be fine. Always a good idea to back up your data and system bacakup since you have TWRP anyway.
3) I saw following para in https://magiskmanager.com/uninstall-magisk
I believe this is reffering to all the MAgisk data only.
Andrologic said:
1) Can I uninstall/unroot Magisk anytime and reinstall/root again smoothly whenever the need arises?
Yes.
2) Does installing/uninstalling root wipe data?
No. As long as you're not locking/unlocking your bootloader, you should be fine. Always a good idea to back up your data and system bacakup since you have TWRP anyway.
3) I saw following para in https://magiskmanager.com/uninstall-magisk
I believe this is reffering to all the MAgisk data only.
Click to expand...
Click to collapse
Thank you very much for your reply
Maria2014 said:
I am having the same problem. I want to ask if you tried uninstall magisk ? What happened ?
Click to expand...
Click to collapse
My dear, I install and uninstall Magisk all the time. Legitimately speaking, never once did it wipe my data ever. Unless you unlock or relock your bootloader, you will be completely fine.
Shabeeh Manappurath said:
My dear, I install and uninstall Magisk all the time. Legitimately speaking, never once did it wipe my data ever. Unless you unlock or relock your bootloader, you will be completely fine.
Click to expand...
Click to collapse
Hi,
Could you advice pls.
After updating magisk it stopped working..
Shuld I uninstall it and then reinstall?
Will my modouls be earased? I am very worried taking this step..
Thanks in advance
tuvia_g123 said:
Hi,
Could you advice pls.
After updating magisk it stopped working..
Shuld I uninstall it and then reinstall?
Will my modouls be earased? I am very worried taking this step..
Thanks in advance
Click to expand...
Click to collapse
My advise is, Incase you feel your modules will be erased, just take a screenshot of ur magisk Modules. Screenshot which you can use to later download the exact same modules. Or u can keep magisk module downloaded before hand. Now if magisk is not working, magisk Modules will not show for you.
If magisk is not working, you don't need to uninstall it. Just go to recovery and reflash the magisk.zip or magisk.apk. both will work, bcos that is how it is. Magisk.apk can be directly flashed from recovery menu. Once you reinstall magisk from recovery and it should start working. If after reboot, it is still not working, then just install magisk.apk while you are in android. (Not in recovery, but normal mode) and then open it and see what it says.
If I can help, I will surely. Let me know how it goes. Usually no data is erased. Don't worry. Magisk Modules or magisk, don't effect the system. U can also download magisk uninstaller.zip if you want to completely uninstall magisk.
Shabeeh Manappurath said:
My advise is, Incase you feel your modules will be erased, just take a screenshot of ur magisk Modules. Screenshot which you can use to later download the exact same modules. Or u can keep magisk module downloaded before hand. Now if magisk is not working, magisk Modules will not show for you.
If magisk is not working, you don't need to uninstall it. Just go to recovery and reflash the magisk.zip or magisk.apk. both will work, bcos that is how it is. Magisk.apk can be directly flashed from recovery menu. Once you reinstall magisk from recovery and it should start working. If after reboot, it is still not working, then just install magisk.apk while you are in android. (Not in recovery, but normal mode) and then open it and see what it says.
If I can help, I will surely. Let me know how it goes. Usually no data is erased. Don't worry. Magisk Modules or magisk, don't effect the system. U can also download magisk uninstaller.zip if you want to completely uninstall magisk.
Click to expand...
Click to collapse
Thank you very much for your detailed and clear answer.
In the next few days I will find time and try.
Of course I will update you.
tuvia_g123 said:
Thank you very much for your detailed and clear answer.
In the next few days I will find time and try.
Of course I will update you.
Click to expand...
Click to collapse
Alright Dear, take your time, and let me know, I hope everything works out for you. And Your Welcome
Shabeeh Manappurath said:
Alright Dear, take your time, and let me know, I hope everything works out for you. And Your Welcome
Click to expand...
Click to collapse
Hello dear friend,
Looks like I deleted the original zip file.
Can you pls. attach a link that wont be malware of a magisk zip?
Thanks a lot
tuvia_g123 said:
Hello dear friend,
Looks like I deleted the original zip file.
Can you pls. attach a link that wont be malware of a magisk zip?
Thanks a lot
Click to expand...
Click to collapse
The best, and only official place to download magisk from is GitHub. At least I think. And well there is one another website I download it from, it's not malware, but I will provide you with the GitHub link itself.
For Magisk v23.0 (One with MagiskHide)(This release also has online module repo, where you can download extra supported modules for your device from online repo of magisk)
https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
For Magisk v25.2 (It does not have MagiskHide, but this is much more better, and there are more effective ways to hide root using Zygisk (new feature in Magisk v24 onwards I believe) (This one does not have Online Repo for Magisk modules, it was also removed in a previous version of Magisk, and you can use Fox's Magisk Modules manager if you want to access and download magisk Modules for any of the future releases for Magisk) If you want the link for Magisk v25.2 then here it is:
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Just if u face any difficulty in flashing the apk file in recovery, just rename it to magisk v23/v25.2 (whichever u choose, I kinda recommend using the latest version) and rename it into . Zip. And if u plan on going with v25.2 and want to access the latest online repo and some of their own Magisk modules, then here is the link for the latest version of Fox's Magisk Modules manager:
Release 0.6.1 - Maintenance Update · Fox2Code/FoxMagiskModuleManager
Add Androidacy test-mode fix to non test-mode Update Brazilian translations by @DanGLES3
github.com
I am currently using the latest Magisk v25.2 on my phone, and currently running on the latest version of Fox's Magisk Modules manager as well. And also, using the method for hiding root that I mentioned before, I am completely successful in covering my root, and my safety net is passed. Completely Passed. Play store or any other app I don't want it detecting root, does not detect root. So we all good if you want to flash the latest update of Magisk.
Shabeeh Manappurath said:
The best, and only official place to download magisk from is GitHub. At least I think. And well there is one another website I download it from, it's not malware, but I will provide you with the GitHub link itself.
For Magisk v23.0 (One with MagiskHide)(This release also has online module repo, where you can download extra supported modules for your device from online repo of magisk)
https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
For Magisk v25.2 (It does not have MagiskHide, but this is much more better, and there are more effective ways to hide root using Zygisk (new feature in Magisk v24 onwards I believe) (This one does not have Online Repo for Magisk modules, it was also removed in a previous version of Magisk, and you can use Fox's Magisk Modules manager if you want to access and download magisk Modules for any of the future releases for Magisk) If you want the link for Magisk v25.2 then here it is:
https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk
Just if u face any difficulty in flashing the apk file in recovery, just rename it to magisk v23/v25.2 (whichever u choose, I kinda recommend using the latest version) and rename it into . Zip. And if u plan on going with v25.2 and want to access the latest online repo and some of their own Magisk modules, then here is the link for the latest version of Fox's Magisk Modules manager:
Release 0.6.1 - Maintenance Update · Fox2Code/FoxMagiskModuleManager
Add Androidacy test-mode fix to non test-mode Update Brazilian translations by @DanGLES3
github.com
I am currently using the latest Magisk v25.2 on my phone, and currently running on the latest version of Fox's Magisk Modules manager as well. And also, using the method for hiding root that I mentioned before, I am completely successful in covering my root, and my safety net is passed. Completely Passed. Play store or any other app I don't want it detecting root, does not detect root. So we all good if you want to flash the latest update of Magisk.
Click to expand...
Click to collapse
Hi,
I prefer v 23 because it has the hide option builtin.
However after flashing it(i think succesfuli) i do not find any new app in my fhone..
tuvia_g123 said:
Hi,
I prefer v 23 because it has the hide option builtin.
However after flashing it(i think succesfuli) i do not find any new app in my fhone..
Click to expand...
Click to collapse
Alright your preference is your own, but maybe hear me out, v23 will soon become outdated, as in some magisk Modules will stop working for it. And the magisk hide, according to the founder of Magisk @topjohnwu, he said that magisk hide is become really ineffective in blocking root, or stopping apps from detecting root. If you want a more powerful version of Magisk hide, update to v25.2 and I will show you how to activate it step by step. It's not built-in, rather it is a new module. So yeah.
Alright and about your question; if you don't find the app in your phone, in your apps drawer, just open file explorer, go to the location where u have kept the magisk.zip file or magisk.apk file. If u have the apk file then just install it once more, from android while in normal mode. If you have the zip file, then just rename to .APK and install it same like above. Then open magisk to continue (mostly after proper install, magisk will reboot your phone once more). Any steps you are stuck in, pls sent me a screenshot, so that I can help.
Shabeeh Manappurath said:
Alright your preference is your own, but maybe hear me out, v23 will soon become outdated, as in some magisk Modules will stop working for it. And the magisk hide, according to the founder of Magisk @topjohnwu, he said that magisk hide is become really ineffective in blocking root, or stopping apps from detecting root. If you want a more powerful version of Magisk hide, update to v25.2 and I will show you how to activate it step by step. It's not built-in, rather it is a new module. So yeah.
Alright and about your question; if you don't find the app in your phone, in your apps drawer, just open file explorer, go to the location where u have kept the magisk.zip file or magisk.apk file. If u have the apk file then just install it once more, from android while in normal mode. If you have the zip file, then just rename to .APK and install it same like above. Then open magisk to continue (mostly after proper install, magisk will reboot your phone once more). Any steps you are stuck in, pls sent me a screenshot, so that I can help.
Click to expand...
Click to collapse
Hi,i took your advice and flashed v. 25.2, however i think that the installation failed..
tuvia_g123 said:
Hi,i took your advice and flashed v. 25.2, however i think that the installation failed..
Click to expand...
Click to collapse
Hey, I see, okay use magisk uninstaller to completely remove v23 first, and then flash v25.2 afterwards.
From what I researched, it seems u can easily uninstall magisk by renaming magisk v25.2.apk (the file we downloaded) rename it into uninstall.zip
And then reboot to recovery, flash it from recovery to completely uninstall magisk v23. (Make a copy of the file before renaming into uninstall.zip.) that way we can flash v25.2.apk /v25.2.zip directly.
Hope everything works for you.
Shabeeh Manappurath said:
Hey, I see, okay use magisk uninstaller to completely remove v23 first, and then flash v25.2 afterwards.
Just to be sure,v. 23 that I want to uninstall not to rename?
From what I researched, it seems u can easily uninstall magisk by renaming magisk v25.2.apk (the file we downloaded) rename it into uninstall.zip
And then reboot to recovery, flash it from recovery to completely uninstall magisk v23. (Make a copy of the file before renaming into Uninstall.zip.) that waysure that I understood.. we can flash v25.2.apk /v25.2.zip directly.
not sure that i understands.
Click to expand...
Click to collapse
Shabeeh Manappurath said:
Not
Hope everything workNs for you.
Hey, I see, okay use magisk uninstaller to completely remove v23 first, and then flash v25.2 afterwards.
N
From what I researched, it seems u can easily uninstall magisk by renaming magisk v25.2.apk (the file we downloaded) rename it into uninstall.zip
And then reboot to recovery, flash it from recovery to completely uninstall magisk v23. (Make a copy of the file before renaming into uninstall.zip.) that way we can flash v25.2.apk /v25.2.zip directly.
Hope everything works for you.
Click to expand...
Click to collapse
Not sure that I understood.
Not to rename Version 23 that I want to uninstall?
Rename v25 that we want to keep?
https://drive.google.com/uc?export=download&id=1XvA2wCzCfSgQGJRgzJ-yklOYn99DDjBQ
Just Flash that, in order to uninstall Magisk from your device. And then, install the latest Magisk v25.2
Shabeeh Manappurath said:
https://drive.google.com/uc?export=download&id=1XvA2wCzCfSgQGJRgzJ-yklOYn99DDjBQ
Just Flash that, in order to uninstall Magisk from your device. And then, install the latest Magisk v25.2
Click to expand...
Click to collapse
Hi dear,
First of all thank you again.
After flashing this when i am entering again to recovery I don't get the screen of twarp as before.
However installation of v. 25.2 (in recovery)failed again..
Atached screen shots.