How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
xxsen said:
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
Click to expand...
Click to collapse
I have used the method on a Samsung Galaxy Xcover 4s with new firmware.
However I don't know if it will work with Samsung Galaxy S9 due to the need for "dm-verity and force encryption disabler".
Have you rooted?
Related
I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks
There is no update. 5.0.2 is the latest.
ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?
MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:
If you want to go back to stock just flash the latest firmware with odin.
Stock rom downloaded from oneplus. net cannot be rooted.
Super su cannot be pushed via Twrp. Zip file fails. Any way to root the pure stock....?
sibikallikkat said:
Stock rom downloaded from oneplus. net cannot be rooted.
Super su cannot be pushed via Twrp. Zip file fails. Any way to root the pure stock....?
Click to expand...
Click to collapse
either try a different zip file or simply flash a rooted stock rom. More than likely there is something going on your end.
In these situations you have to search and also ask yourself am I the only one with this problem and if so then what am I doing differently. Then start from scratch and work it out. There are multiple TWRP's different zip files check md5, I mean its more than just posting a question on xda.
I used this tool without any problem
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
You managed to have twrp so it may be supersu files. Supersu is included in the tool.
Le_Zouave said:
I used this tool without any problem
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
You managed to have twrp so it may be supersu files. Supersu is included in the tool.
Click to expand...
Click to collapse
This tool I tried.It says SuperSu is pushed and turns green...But after I boot the phone no supersu is found in app drawer...
This problem is with the latest stock 3.2.1 downloaded from oneplus.net
playya said:
either try a different zip file or simply flash a rooted stock rom. More than likely there is something going on your end.
In these situations you have to search and also ask yourself am I the only one with this problem and if so then what am I doing differently. Then start from scratch and work it out. There are multiple TWRP's different zip files check md5, I mean its more than just posting a question on xda.
Click to expand...
Click to collapse
Sorry sir,
Tried different zips of Supersu including the latest 2.76 stable...But no success. I switched to Freedom Os ,the rooted rom.
But many prefer to use the pure stock rooted...Thats 3.2.1 from oneplus.net. This is stubborn and prevents rooting.SuperSu can be flashed via TWRP but no SuperSU icon found in APP drawer..Also the system stands unrooted...
After the tool says the zip is pushed to the phone, you need to go in twrp and flash the zip. I have the latest stock too and the supersu included in this tool worked just fine in twrp.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
Yeah it has to be a step your missing your not telling us about. Hopefully you sort it out but if not start from scratch and follow directions exactly and let us know
Hi all,
I have flashed a pre-rooted 14.6.A.0.368 on my phone with Locked Bootloader, and that is the firmware version on my phone at the moment.
Sony is offering me an OTA update, but I do not want to lose root, so I downloaded FlashFire but the app does not automatically detect the OTA file. I have managed to track the file down to /sdcard/recovery/update_package but FlashFire does not recognise the file as an OTA package (presumably because it doesn't have a file extension). Adding a .zip extension to the file reveals that it is not a ZIP.
What options are available for me to upgrade to the latest official firmware and retain root? (Or lose and regain it?)
kha1rul said:
Hi all,
I have flashed a pre-rooted 14.6.A.0.368 on my phone with Locked Bootloader, and that is the firmware version on my phone at the moment.
Sony is offering me an OTA update, but I do not want to lose root, so I downloaded FlashFire but the app does not automatically detect the OTA file. I have managed to track the file down to /sdcard/recovery/update_package but FlashFire does not recognise the file as an OTA package (presumably because it doesn't have a file extension). Adding a .zip extension to the file reveals that it is not a ZIP.
What options are available for me to upgrade to the latest official firmware and retain root? (Or lose and regain it?)
Click to expand...
Click to collapse
Personally, I would try making a backup, and dirty flash a pre-rooted .236, (if you're trying to save data, if not, just wipe everything and flash 236) If that didn't work, use Titanium to backup, then flash 236, then restore.
levone1 said:
Personally, I would try making a backup, and dirty flash a pre-rooted .236, (if you're trying to save data, if not, just wipe everything and flash 236) If that didn't work, use Titanium to backup, then flash 236, then restore.
Click to expand...
Click to collapse
Lol, I only just realised how stupid my question was! Managed to easily find the 236 PRF here from the same dev @Mirhawk.
Thanks for the help!
Hello,
I have an Exynos SM-N975F rooted with Magisk. I'd like to update the firmware. Is there any way to do it with odin without data loss? I thought of downloading the full new FW, patching the AP with Magisk and then just using Odin for everything, but won't that delete everything (ie lots) that I have already installed, even if I use HOME_CSC?
Does anyone know how to do it? I've searched and searched and found no proper guide, except "make a Titanium backup and restore", which really never worked exactly for me.
Thanks,
wafna
Download the newest firmware with frija
You can just flash the new firmware with Odin and homecsc to not lose your data
You may need to reflash magisk to keep root
Thanks, I'd think so too. However, with the new Android Pie protections on the 10+, the procedure to install Magisk includes having Magisk patch the AP file, rebooting in recovery, doing a factory reset and then rebooting. So IDK if just getting the files from Freya and patching the AP and using HOME_CSC will be enough to keep the data. I haven't found any guide/how-to/instructions on firmware update with the Note 10/10+, so I'm a little wary of following your procedure unless someone has tried before.
If anyone has found a confirmed guide or how-to please help. Installing the OTA with Freja/Odin and HOME_CSC also seems logical to me, but with Magisk on the recovery partition now and the install procedure mentioning a factory reset idk about using that.
If you are using stock recovery, follow this
Download new firmware and extract AP_*.tar.md5
Patch Extracted file with magisk
Flash patched file with odin - AP tab + BL, CP and Home_csc files from new firmware with respective tab of odin
Done.
If you are on TWRP, follow above procedure and then
Flash TWRP (tar file with three file combo) with AP tab of odin. But remember, twrp you need to use based on same firmware આ cording your new base. Older one may or may not work.
Above instruction is for update base who already using rooted device. For new users, wipe data is must.
worked perfectly, many thanks one can always count on Dr Ketan...
Hi there,
I just dared to try and root my new S20 FE...and it worked.
I basically followed the steps in the S20 root Thread or the Link from the S10 root thread.
I didn't use vbmeta_disabled.tar, seems like it is not needed anymore.
Was also curious if we could just use TWRP from S20...but I ended up with a soft brick...so doesn't seem to be so easy :crying::crying:
danjac said:
Was also curious if we could just use TWRP from S20...but I ended up with a soft brick...so doesn't seem to be so easy :crying::crying:
Click to expand...
Click to collapse
what is the worst way you can brick it?
Sp8ky said:
what is the worst way you can brick it?
Click to expand...
Click to collapse
Hard brick where you are stuck with a phone that never boot again. Very hard to do though
I would attempt it but I couldn’t find an Australian firmware...
danjac said:
Hi there,
I just dared to try and root my new S20 FE...and it worked.
I basically followed the steps in the S20 root Thread or the Link from the S10 root thread.
I didn't use vbmeta_disabled.tar, seems like it is not needed anymore.
Click to expand...
Click to collapse
Just managed to root my 5G SD version as well following the S20 link. It’s even easier now using the latest magisk manager to directly install magisk rather than patching tar file.
Edit: I didn’t use vbmeta either.
tadasu said:
Just managed to root my 5G SD version as well following the S20 link. It’s even easier now using the latest magisk manager to directly install magisk rather than patching tar file.
Edit: I didn’t use vbmeta either.
Click to expand...
Click to collapse
Can you please summarize the steps performed?
Btw on the S20 forum section [RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon) a recovery is ready to test.
bognik said:
Can you please summarize the steps performed?
Btw on the S20 forum section [RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon) a recovery is ready to test.
Click to expand...
Click to collapse
As per the S20 link by OP, here's a very quick summary of what I did:
1. Unlocked my bootloader.
2. Skipped "Stage 3: Disable Android Verified Boot" in the link.
3. Searched and downloaded latest official firmware from sammobile specific for my australian model.
4. Used Odin to upgrade. I put CSC instead of HOME_CSC to erase all my data (not much data on my phone anyway) wanting a clean upgrade, and left "USERDATA" blank.
5. Skipped "Stage 5 and 6" in the link.
6. Downloaded and installed Magisk Manager from Magisk official website.
7. Installed Magisk in Magisk Manager using its "Direct Install (recommended)" option (can't remember the exact words).
And my phone was rooted.
Note I did not do any backup while rooting my phone because it's pretty new and nothing much was on it (and it's not my primary phone), so it's a high risk procedure if it's your primary phone and if something went very wrong.
Hope this helps.
Can I flash European firmware to.my hong Kong version?
So the the U.S. At&t Snapdragon version can't be rooted?
ı just twrp please
tadasu said:
As per the S20 link by OP, here's a very quick summary of what I did:
1. Unlocked my bootloader.
2. Skipped "Stage 3: Disable Android Verified Boot" in the link.
3. Searched and downloaded latest official firmware from sammobile specific for my australian model.
4. Used Odin to upgrade. I put CSC instead of HOME_CSC to erase all my data (not much data on my phone anyway) wanting a clean upgrade, and left "USERDATA" blank.
5. Skipped "Stage 5 and 6" in the link.
6. Downloaded and installed Magisk Manager from Magisk official website.
7. Installed Magisk in Magisk Manager using its "Direct Install (recommended)" option (can't remember the exact words).
Click to expand...
Click to collapse
I don't get how you were able to utilize direct install.
Direct install would only appear if you already had root access isn't it?
If I follow steps
1 - unlocked bootloader
2 - skip stage 3
3 - skip stage 4 (due to already being on latest firmware.)
4 - skip stagr 5, 6 (your step)
5 - install magisk
6 - no direct install option.
?-?
everlasting207 said:
I don't get how you were able to utilize direct install.
Direct install would only appear if you already had root access isn't it?
If I follow steps
1 - unlocked bootloader
2 - skip stage 3
3 - skip stage 4 (due to already being on latest firmware.)
4 - skip stagr 5, 6 (your step)
5 - install magisk
6 - no direct install option.
?-?
Click to expand...
Click to collapse
I'm not sure why I was able to do direct install on my unrooted phone, noob here just following guides
I haven't had a samsung phone before, if I root it am I going to have problerms with warranty later?
I was able to install magisk root using instructions here: https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
Used Frija for getting the FW.
edit: It seems magisk on this device breaks Tidal? Can anyone else confirm? Flashed back to stock, Tidal works, but with magisk patched tidal stops playback of all songs at 0:19.
I have some problems with rooting my device:
I tried to flash vbmeta_disabled.tar but ODIN fails to flash it
I used magisk to patch the boot.img and then flashed the image using ODIN, root works and I can access the system, but I can't change system to read-write, so I can't make any changes to files in system (or any other folder in root). Any apps I have get root access from magisk, but fail when attempting to make any changes to system files, so they are useless.
Does anyone else have these issues? Is there a step I should have done to be able to write to system/root?
So what's the process of root on Android 11?
cyyy said:
I have some problems with rooting my device:
I tried to flash vbmeta_disabled.tar but ODIN fails to flash it
I used magisk to patch the boot.img and then flashed the image using ODIN, root works and I can access the system, but I can't change system to read-write, so I can't make any changes to files in system (or any other folder in root). Any apps I have get root access from magisk, but fail when attempting to make any changes to system files, so they are useless.
Does anyone else have these issues? Is there a step I should have done to be able to write to system/root?
Click to expand...
Click to collapse
in my limited understanding android 10+ has a strictly read only system partition. any changes have to made via magisk overlays like systemless host files in adaway for example. EDIT: also there's ADB that can edit / write.
Has anyone got the full steps for rooting a new s20 fe? Lets say I buy the phone and upgrade using ota to Android 11 straight away...then what?
danjac said:
Hi there,
I just dared to try and root my new S20 FE...and it worked.
I basically followed the steps in the S20 root Thread or the Link from the S10 root thread.
I didn't use vbmeta_disabled.tar, seems like it is not needed anymore.
Click to expand...
Click to collapse
que al me podría indicar el proceso de instalación que usaste?
Translation: Could you tell me the installation process you used?