This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
[Update#1]
Today I have managed to install the Android Beta 3.1 [ is beta software and I don't recommend using it as your daily os]
https://sourceforge.net/projects/nippongsi/files/Pixel%20-%20Pixel4a_SBeta3.1%20-%20TBO42ZZ8IF/Pixel4a_SBeta3.1-AB-12-20210727-nippongsi.img.gz/download
you can download the ROM file from Nippon's Sourceforge
every step is the same and you just have to change the rom as this
there's a bug that developer setting crash the settings app and it is working but it does have some lots of bugs, and screen lock is not working but I'll try to fix it and upload the method
if your device get boot looped, press Bixby + power + vol down to boot into download mode and flash the stock AP file using Odin
[I was supposed to edit the upper one but accidentally created as a reply ]
Just go to UPDATE#2
Skuld Norniern said:
Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)
Click to expand...
Click to collapse
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
thongass000 said:
Hey I thought that A8 star is an A-only device. Does flashing A/B roms cause any problems?
Click to expand...
Click to collapse
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Skuld Norniern said:
thanks for the makemesar.zip we can install the A/B partition roms without any problems on the A only device and for me the A only roms won’t work on my phone
Click to expand...
Click to collapse
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
thongass000 said:
Hi I'm back. Do you have any issue with wired audio? I have a A9 2018 (same chipset) and audio still goes through speaker while headphones are plugged in.
If anything in Phh Treble Settings helps you, please tell me. Or if you don't need any settings for wired audio, can you send me a zip file containing any files that have the name "audio_policy" in /vendor/etc? Thanks.
Click to expand...
Click to collapse
Sorry for being late!!
for me, I do have the same issue with wired audio and I have not been able to find a way to fix it yet
if I manage to fix the issue I will fix the main article
Skuld Norniern said:
Skuld Norniern said:
This is my first post of this kind so bear with me, please
Info for Galaxy A8 Star:
CPU : SDM660 ( A only, 64bit )Support Project TrebleSupport System as root
※WARNING※
You will have to have OEM unlocked and this will void your warranty!!!
※also, I'm not responsible for the accident about you bricking your device※Step. 1
First of all, you will need to download two custom recoveries (TWRP, OrangeFox)
OrangeFox: https://forum.xda-developers.com/t/orange-fox-recovery-galaxy-a8-star-sm-g885f.4301055/
TWRP: https://github.com/sabpprook/android_device_samsung_astarqlte (test3 file does not work for me but you can try)
I want to finish it only using TWRP but the only TWRP that was working does NOT support flashing the system.img files
and also Orange Fox recovery has a bug that while in recovery you can't connect with the computer and push the files to the phone
so it was required to use two bootloader
Step. 2
Odin: https://odindownload.com/
I also recommend downloading the stock ROM for backup
1. after downloading the TWRP from the link (for Odin we will use the .tar file)
put your phone into download mode
Code:
adb reboot download
or just turn off the phone and press the power button, volume up, Bixby button at the same time
and use the volume button to boot into download mode
2. after the phone went to the download mode, go to Odin and at the ap section add the TWRP file then flash it
3. press the volume down, power button to turn off the device, and right after that press the power button, volume up, Bixby button at the same time
4. you will now see the TWRP recovery, press wipe, and format data
5. now we will download some files we needed
makemesar.zip: (at the attachment) or you can download it from https://drive.google.com/u/0/uc?export=download&confirm=P1-1&id=1F_f_tL4sEYFx5fa6AnwR0x1tlYhqarcT ( when you unzip it there is the zip file )Permissiver_5.zip: https://androidfilehost.com/?fid=6006931924117940902Disable_Dm-Verity_ForceEncrypt: https://drive.google.com/file/d/166texWJQhR1RgRoXiRSH_M2Q2mAyS2gC/viewCertification_Patch.zip: (at the attachment)Havoc Rom (you can use any rom you want but this is the one that I've managed to work) http://download.havoc-os.com/?dir=arm64-ab (download arm64 ab with gapps)most rooms with AB partition will be supportedMagisk: https://magiskmanager.com/ (download the apk and make it a zip file) - you could need for the phone to get the boot (makemesar will unroot it so don't worry)6. after downloading all the files that we need, we will push the files to our device using
Code:
adb push 'file dir' sdcard
※ also push TWRP .img file and the OrangeFox .img too!!
7. after pushing all the files we need to our phone, press install from the TWRP recovery and press flash from image
and select the Orange Fox .img as a recovery image, and reboot to bootloader
8. now you will boot to the Orange Fox recovery, (locate to data/media to find the files)
at the Orange Fox recovery wipe System, Dalvlk / ART Cache, Cache, Data
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
10. reboot to the system and you will see the new os setup process (sometimes you have to install the Certification Patch after setup the os )
10-1. if your device keeps going to download mode, reinstall the magisk and then reboot the phone, then it will work.
(after it boots, gently turns off the phone and install makemesar.zip first and install Dm-Verity to unroot) - some of you will be forced to use magisk but doing some wiping or reflashing the system.img sometimes makes the unrooted state work (or flash the stock system.img (extract from the stockrom) and flash the gsi ROM without wiping )
Screenshots: At Below
Currently, MTP does not work but I think this is the problem with the Havoc os, if you use another rom it could work
face unlock, fingerprint unlock works, the camera works.
if I manage to get other ROMs workingI will update the post
also at the first time I have made mine to boot without magisk but while doing again for this post I'm having trouble without magisk, if I found a way that works always I will add that to the post
[UPDATE#2]
you can download the Pixel 3 gsi rom from
(Thanks for Santa Duck providing this information!!!!)
with this files you can install the android 12 gsi rom in a usable state!!
and also ADB is working with this rom
there is still a bootlooping bug so do it with caution
Click to expand...
Click to collapse
Hello sir i can't find havoc os 4.5 in:https://download.havoc-os.com/?dir=arm64-ab
Click to expand...
Click to collapse
After flashing twrp on my sm g885f, cant get into terp,
mine shows volume down + power to restart, not to enter turn off
how can i enter into twrp
Skuld Norniern said:
9. after wiping now install the os.img file and reboot to the bootloader (before reboot you will see the warning that OS is not installed), go to the menu and mount system, vendor, and install Dm Verity.zip, Permissiver_5.zip, makemesar.zip then reboot to the bootloader again, (now we will not see the OS is not installed) and now install the Certification Patch.zip
Click to expand...
Click to collapse
'os.img file' where
, guess i fixed it
when installing Certification_Patch.zip, it shows command error
what i found- this patch is for G885FDXS5CUL1, mine is
G885FDXU5CUG1
Related
Hi folks,
I'm looking for advice to update to 23.1.A.1.28 Lollipop, I would prefer to do a nice fresh install with the 23.1.A.1.28 UK unbranded FTF file. I updated from 4.4.2 to 4.4.4 using the PRFCreator flashable zip. I have unlocked bootloader & would prefer to keep everything stock including kernel.
1. Can I do a full wipe in the dual recovery including wiping the entire internal SD & then flash the flashable zip? Or will the full wipe including formatting the internal SD wipe the recovery?
2. Just flash the 23.1.A.1.28 UK unbranded FTF file using flashtool & check all the wipe options before the flash & then use King root (even though Bitdefender flags it as possible virus when it has never ever flagged any other root exploit before) to root device & then run the latest NuT dual revovery?
3. I only use a couple of xposed modules that as far as I can read are compatible with xposed-sdk21-arm-20150430.zip & the correct steps to install xposed for Lollipop are
I. Flash xposed-sdk21-arm-20150430.zip in recovery after rooting with King root.
II. Install XposedInstaller_3.0-alpha2.apk to manage modules
III. Install Play store fixes & youtube adaway modules in the xposed app. I would like to use Lollipop Navigation Bar module but don't think it is compatible as yet.
The reason I want to do a fully clean install is due to the fact I have found the phone to run a bit slower since updating from 4.4.2 to 4.4.4 with the PRF creator flashable zip. This mainly shows in the apps screen which shows the loading bars for about 5-6 seconds & then takes another 10-15 seconds to list the apps & app sizes etc.
Sorry for all the questions, my previous devices were all Samsung so I'm used to full wipe including internal SD & then installing custom Rom.
Cheers in advance for any help given.
If you have unlouck bt you can just flash stock in flash tool and flash recovery after that because this best way you didn't have a problem
Cheers for the reply copra11
How would I flash recovery after flashing the FTF file with Flashtool? Can I use flashtool to flash recovery or just use the installer version of NuT's dual recovery?
Would I need to be rooted first before installing NuT recovery?
Another question I have is I still got app updates through the sony update centre app on 4.4.2 with unlocked bootloader but when I updated to 4.4.4 I never got any app updates through update centre at all, had to get them from here or xperiablog. Would relocking the bootloader allow me to get app updates again?
Can anyone else offer some advice? Would like to get this done today\tonight if possible.
Cheers.
on unlocked bootloader :
- Flash ftf using flashtool, once done unplug device
- Get twrp from here : http://dl.twrp.me/sirius, download *.img file - rename file to recovery.img for later use
- go in folder C:\Flashtool\x10flasher_lib (assuming you installed flashtools in the default place), paste recovery.img in this folder (from previous step)
- Put phone in fastboot mode (hold Vol-up while inserting usb cable)
- hold shift and right-click anywhere in folder (but not on any files) and choose "open command window here"
- in the cmd window that comes up type the following : fastboot flash recovery recovery.img
you'll get a short message about the flash being successful, then you can disconnect your phone.
Reboot your phone, once the let light is on during the first Sony screen press the power button multiple times, then you can enter recovery.
This is for Unlocked Bootloader ONLY, I also recommend using @AndroPlus awesome kernel, which includes its own recovery, in this case you can simply flash the kernel and not mess with the recovery, to do this :
- download latest @AndroPlus kernel from here http://dl.androplus.org/Xperia Z2 D6502_D6503_D6543/
- open zip file and extract boot.img from it
- copy boot.img to C:\Flashtool\x10flasher_lib
- Put phone in fastboot mode (hold Vol-up while inserting usb cable)
- hold shift and right-click anywhere in folder (but not on any files) and choose "open command window here"
- in the cmd window that comes up type the following : fastboot flash boot boot.img
Hope this helps
Cheers for the reply ticktock666
Thanks for the guide you posted, I assume once recovery is installed I can then just flash SuperSU or just flash the flashable zip I created with PRF Creator? Would just flashing SuperSU root the phone?
Again many thanks for your help
@ticktock666
Followed your first set of steps.
- Flash ftf using flashtool, once done unplug device
- Get twrp from here : http://dl.twrp.me/sirius, download *.img file - rename file to recovery.img for later use
- go in folder C:\Flashtool\x10flasher_lib (assuming you installed flashtools in the default place), paste recovery.img in this folder (from previous step)
- Put phone in fastboot mode (hold Vol-up while inserting usb cable)
- hold shift and right-click anywhere in folder (but not on any files) and choose "open command window here"
- in the cmd window that comes up type the following : fastboot flash recovery recovery.img
you'll get a short message about the flash being successful, then you can disconnect your phone.
Reboot your phone, once the let light is on during the first Sony screen press the power button multiple times, then you can enter recovery.
Click to expand...
Click to collapse
When I power on the phone there is no LED light & despite spamming the power button it just boots up normally into the first run wizard. The fastboot flash recovery recovery.img command says it flashed it ok as shown in image.
Do you have a D6503 model ? my friend does and his unit does not show the purple led light when booting like my unlocked D6502 one does, no idea why.
Have you tried spamming the vol-up OR vol-down button on reboot ? try this first then go down the kernel road, do the kernel steps, this way you'll 100% get the recovery (I never flashed the recovery image alone before). Once you install the kernel you simply need to press vol-up and you get the recovery.
a couple of things :
when flashing xposed, flash the zip from recovery, wipe cache/dalvik, boot into system, install apk, then from the xposed app do a Soft-reboot, and immediately enter recovery and do a cache/dalvik wipe, then reboot. This is how I usually do it and it's been working for me since .690, so I though I'd share, also I've tried the 2 navigation bar modules from the xposed repo at some point and they both worked, also gravitybox offers many navigation bar mods among other things.
just flashing SuperSU zip from recovery is enough for root, no need for the prerooted zip, you'll just just be reflashing the rom you already have.
@ticktock666
Yeah mate it's a D6503 model, have tried the steps several times & the cmd window shows the recovery as being installed but no LED light when booting & the power & volume up & down buttons have no effect either. Ended up flashing the Andro kernel you recommended & the LED was purple when booting & spamming power button got me into recovery.
Even tried adb reboot recovery before I flashed the kernel but still nothing, also for some reason when going through the first run wizard it didn't restore my google backup when I entered google account details.
Starting again from scratch using your guide so fingers crossed
BTW do you know a good sound boosting mod, I was using Sound Mod v3.1 For Z2 Normal.zip on 4.4.4 from this thread or this thread
Will follow your steps for installing xposed framework & app, bit surprised that dalvik would need to be wiped as Lollipop uses ART runtime instead but will play it safe
Cheers again for all the help mate, really appreciate it
guess the led thing is kernel related, but I have unlocked the bootloader only 3 days after getting the device, and have been using a custom kernel ever since, so this might be the issue.
I just wiped my device, since I somehow managed to royally fudge it up after the 1.28 update (maybe because I dirty flashed 690, 726, 1.28 on top of each other )
I did excatly what I told you, and i'm now doing a backup before testing some stuff (deodexing app & priv-app, bloatware removal script).
I never use any sound mods, since I mostly listen to audiobooks, so there's not much bass involved , as for dalvik I'm sure the folder exists (under "/", which is the root directory of the device), maybe to use with older apps that are not optimized for ART ? not sure really but better safe than sorry.
Also I recommend entering recovery using vol-up since you have Andro's kernel, since this one is optimized for our device (extra backup options and stuff)
Yeah mate, after flashing the FTF file & then going into fastboot mode & flashing the kernel the LED is purple & pressing volume up gets me into recovery.
I thought I had bricked the phone as I tried to use flashtool in fastboot mode to try & flash the recovery but phone was stuck on the sony logo screen, after panicking for a few mins I used the tiny reset button where the sim card goes & it vibrated a few times, was then able to reflash the FTF & use the Andro kernel
I needed the sound mod on 4.4.4 as I found the ringtone & notification volumes too low & kept missing calls etc when out & phone was in pocket. The mod added back xloud feature that helped boost the volume a good bit. From what I have read here about sony lollipop one of the biggest failings was volumes.
Sure I read somewhere that Lollipop removed the dalvik runtime completely but better to be safe than sorry & wipe cache & dalvik with xposed.
BTW is it ok to use streicson busybox installer to get the latest busybox installed, I know when I uses NuT's dual recovery you couldn't install it as it broke recovery?
Cheers again for all your help with this mate, hopefully I can help you out in future
All the best
The reboot button combination for the Z2 is Vol-up+power button, keep holding them until phone vibrates 3 times, better than looking around for something to push the tiny reset button with
as for busybox, I usually flash a zip, but the busybox app by streicson does the same thing.
I'm off to sleep now, and hope everything works for you nicely with no more issues
Rooting Samsung Galaxy M30s SM-M307F with Magisk v20.1 + Video. Magisk v20.1 works stable on SM-M307F with ASJ2 firmware and August 1, 2019 Security Path Level. Lock screen, Biometrics and security worked without any issue, there is not randoom bootloop. Follow these steps below:
1. Make sure the boot loader are unlocked ( OEM options is enabled with grey color ) unlock booloader video https://youtu.be/5juwDL0u_D4
2. Download the firmware Galaxy M30s SM-M307F that match with your region.
3. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager-v7.4.0.apk to your phone.
4. Install Magisk Manager ( MagiskManager-v7.4.0.apk ) on your phone.
5. In Magisk Manager: Install → Install → Select and Patch a File
6. Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
7. Reboot to Bootloader: Turn Power Off. Press and hold Volume Up key + Power Key, When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears. Select Wipe data / Factory reset. Select Reboot to bootloader. Connect the phone to PC using USB Cable.
8. Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files.
Important: check “Auto Reboot” and "F. Reset time" only in Options!
9. Magisk is now successfully flashed to your device!
10. After the device is booted up, do the usual initial setup. It need more time and patient.
11. Connect the phone to Internet, Then Copy Magisk Manager apk file to your phone and install it.
12. Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
13. Done! Your phone root with Magisk v20.1, Enjoy!
14. If you faced annoying OneDrive Pop-Up you can watch in the last video how to fix it
Rooting Video
Note: Rooting M30s is easy than A50s
What about recovery?
ashwin_tembhekar said:
What about recovery?
Click to expand...
Click to collapse
No body develop recovery for this model right now
You need to again wipe data after flashing magisk_patched.tar
I'm still on August security patch! Samsung wtf????
Thank you my friend it is a successful method
Everything done step by step sucessfully
No issues at all...AWESOME!
Everything done step by step sucessfully
But
Phone reboots
quite often while using...
Hritwik said:
You need to again wipe data after flashing magisk_patched.tar
Click to expand...
Click to collapse
***WHY sir???
Random reboots
Hello Team,
after rooting working smooth except of random reboots. removed root now no reboots. please help. i ant root access.
Graphic_Artist_Nik said:
But
Phone reboots
quite often while using...
Click to expand...
Click to collapse
tanweer17 said:
Hello Team,
after rooting working smooth except of random reboots. removed root now no reboots. please help. i ant root access.
Click to expand...
Click to collapse
you must clear magisk data/cache the steps:
1. Boot system without magisk
2. clear magisk data/cache ( don't run it after clear data/cache)
3. Boot system with magisk
Done!
Watch this video full video rooting M30s SM-M307F included how to fix the bootloop
https://youtu.be/Q7m_mUxQaZQ
Twrp for this phone, I don't want to flash any magisk patched rom, just needed twrp for flashing,
BootLoader Unlocking
Is BootLoader unlocking compulsory for flashing stock firmware?
I got an update notification for magisk. How to properly update magisk (not magisk manager) after it's already installed? I am afraid that it will bootloop my installation. I used magisk patched twrp method.
andreidi said:
I got an update notification for magisk. How to properly update magisk (not magisk manager) after it's already installed? I am afraid that it will bootloop my installation. I used magisk patched twrp method.
Click to expand...
Click to collapse
I suggest you to use TWRP, It was available. TWRP is safe and there is no bootloop issue. See this thread for TWRP https://forum.xda-developers.com/ga.../unofficial-twrp-3-3-1-0-galaxy-m30s-t4035019
For rooting video you can watch this video https://www.youtube.com/watch?v=7xyo0O_zuZA
I already rooted and installed twrp with magisk. But I get update norification from magisk. How to update? I have 3 options: direct install, patch a file or download zip.
help, where finishing the Odin stopped in modem or cache please help>>>
Hello everyone, my phone is samsung note 10 plus, I have twrp installed and rooted with magisk, I'm on Android 9, I somehow lost root, have no idea how, I'm very careful not to allow updates or google to install something there might affect my root.
when I go to magisk I'm getting the image that I've attached, when I click on install magisk, download the zip file and try to install it I get an an error as show in the 2nd image, saying unsupported/unknown image forma. I've also attached the log file. Is there any way for me to fix this without flashing the rom and start from scratch? Can I repair it somehow, maybe with TWRP?
Thank you all in advance
you have boot.img of the device?
i thought you can only install magisk in 2 way by flashing boot.img unto magisk or flashing magisk.zip unto TWRP as recovery partition
#edit how did you install magisk in the beginning? thats how you will install it again
there a chance you will get your device brick if you install magisk wrong way (A/B partition) but since you already install it previously just reinstall it back
Hmmm, where should I have the boot. Img you mean as if I backed it up on my pc? Or I can download it and use it?
Now I'm confused :/
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
ineedroot69 said:
Before i explain i don't take responsibility for any damages caused on your device if you decided to follow my tutorial .
So basically there's 2 way to install Magisk
• Image Patching - Basically this is what most people do they find stock boot.img and recovery.img for there devices
1. Copy the Stock boot.img or recovery.img to your device
2. Download and install the latest Magisk Manager
If you are patching a recovery image, manually check “Recovery Mode” in Advanced Settings!
Press Install → Install → Select and Patch a File, and select your stock boot or recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Now pull the magisk_patched.img with ADB:
adb pull /sdcard/Download/magisk_patched.img
Flash the patched boot.img or recovery.img to your device and reboot.
For most devices, here is the fastboot command:
fastboot flash boot magisk_patched.img or
fastboot flash recovery magisk_patched.img if you are patching a recovery image
Now you are rooted
•Custom Recovery - This is when you do not have Stock boot.img or recovery.img for your device
( High Chance Of Phone Getting Bricks )
1. Download and install the latest Magisk Manager
2. Download Magisk.zip (https://github.com/topjohnwu/Magisk/releases/) choose the Latest Release
3.Now reboot to recovery (TWRP, CWM ... ETC)
if you use stock recovery it should say "apply update via sdcard"
then just choose Magisk.zip
4. Now if you have TWRP just click Install and choose Magisk.zip
5. wait for the process
6. Now you are Rooted (hopefully xD :fingers-crossed
Click to expand...
Click to collapse
Thank you very much.
OK, I tried method 2 and didn't work. I downloaded my stock firmware and I have the image file, I can try the first one to place the image in the root of the phone, patch the file with magisk and reflesh it with Odin?
Will I lose all my stuff on the phone by doing this? Thank you
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
ineedroot69 said:
i remember using odin back in 2012 for my samsung galaxy y i didn't know people still using that thing
i search your device on google and it said samsung provide the kernel for it ( https://www.xda-developers.com/samsung-galaxy-note-10-kernel-source-code/amp/ ) thats a good start for rooting your device try looking for it
also visit https://forum.xda-developers.com/galaxy-note-10 it is dedicated section for your device model which means all threads and post are for your device model
Click to expand...
Click to collapse
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
drazenm said:
Im already rooted....
Im having issues how to fix the root as i somehow don't have it any more and i don't want to reflash my rom if I'll lose all my stuff on the phone. Im looking how to fix the root.
Click to expand...
Click to collapse
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
flash713 said:
He's just saying to re-root it... If you lost root it's more than likely gone and you'll have to do whatever you did to gain root in the beginning. I constantly backup all my apps, data, pictures and everything to my little USB OTG thumb drive and to my laptop. I do this daily because many times a factory reset is what has to happen depending on what's going on. You can grab a Samsung micro sdcard 128 GB for $18-$19 or so online or thumb drives like I have a SanDisk 128gb.. it was $14. Just some thoughts for moving ahead so you don't have to go through this again. Lots of good suggestions here. If I were you I'd hit the "thanks" button on whenever took time to stop and search for answers to your issue. That's what we do here on xda. I could care less about racking up "thanks" count just throwing that out there so that you know..
Good luck on getting her all fixed. The note 10 is a real gem!
Sent from my marlin using XDA Labs
Click to expand...
Click to collapse
I can re root it, that's not the problem, i can do it with the patched magisk boot image through Odin, im asking if that's gonna wipe off everything on my phone. Because i can't backup certain things without titanium backup, and titanium requires root access. Thank you for your help and everyone's else's im well aware and grateful for the attempts, suggestions etc.
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
ineedroot69 said:
no it's not gonna wipe anything thats why magisk is called "systemless" . It will essentially modify the system without actually modifying it.
if you flash magisk_patched.zip nothing noticeable will happen except you will have root access
all your installed application will be there
also i notice this some people actually copy magisk_patched.zip thats really bad idea you need to let Magisk generate it.
For example you have 2 phones same model and same build version .
You generate magisk_patched.zip on the phone A
then decided to copy magisk_patched.zip into phone B ofcourse it will still works
but since you just copy it and didnt let magisk generate it . It would not make backup for boot or recovery partition
if you uninstall Magisk on your phone B .There is really high super ultra mega chance of your phone getting bricks. Also it would not revert any changes done on the period while Magisk is installed
Click to expand...
Click to collapse
Thanks for the help, please correct me if im wrong.
Im supposed to copy the AP . md5 file to the root directory of my phone, patch it with magisk, get the patched file, copy it on the pc, connect phone to the pc, get it into download mode, flash the patched file with Odin and that should be it?
Or maybe i can do it with twrp?
Any suggestions?
drazenm said:
Any suggestions?
Click to expand...
Click to collapse
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
ineedroot69 said:
1. Install the latest Magisk Manager
2. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
3. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
4. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck "Auto Reboot" in Options!
5. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
6. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the S10 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
7. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
8. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
9. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
10. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
11. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
12. Voila! Enjoy Magisk
credit to @Magisk github
you can read the full tutorial here https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Click to expand...
Click to collapse
Thanks so much for your help, but i just want to get root back on my phone as i had it rooted already, i dont want to wipe off everything and lose my stuff. There are things that i can only backup with titanium backup, which i can't use now without root privileges :/ can i repair root somehow?
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
ineedroot69 said:
how did you lose your root anyway?
your Android OS updated?
you can try restoring apps with titanium backup but i don't think it will restore Magisk being installed again and gaining root access
Click to expand...
Click to collapse
I didn't do the update, but something did mess up the root aa you can see on the photos that I've attached at the beginning of the topic. I just want to reroot my phone again but not to loose all my current stuff on it.
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
thank you for taking your time to help me out, i appreciate it.
here is the link to the firmware file:
https://androidfilehost.com/?fid=6006931924117937015
inside are these files:
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_REV01_user_low_ship.tar.md5
CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
HOME_CSC_OMC_OXM_N975FOXM1ASH5_CL16618471_QB25349308_REV01_user_low_ship.tar.md5
ineedroot69 said:
if you have boot.img or recovery.img for your device you might not lose your stuff installing back magisk but i think you only have the whole firmware ".tar.md5" flashing thats is like factory reset for your phone
#edit i read about ".tar.md5" they say if you just extract it .It contains all stock .img file for your device such as boot.img, recovery.img , system.img ...etc
since i have too much free time can you upload the firmware ".tar.md5" of your device i will upload .boot.img and recovery.img for you
Click to expand...
Click to collapse
Any luck?
drazenm said:
Any luck?
Click to expand...
Click to collapse
sorry for late reply i'm kinda busy but to make it easier on my part (downloading 5GB file would take me 5 hours) can you just upload the following ?
AP_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship_meta_OS9.tar.md5
BL_N975FXXU1ASH5_CL16618471_QB25345699_REV01_user_ low_ship.tar.md5
CP_N975FXXU1ASH5_CP13587367_CL16618471_QB25409313_ REV01_user_low_ship.tar.md5
TWRP 3.5.0 One UI 3.1 for Samsung Galaxy A50 Android 11. How to Root Samsung Galaxy A50 Android 11 with TWRP 3.5.0 + Magisk. The TWRP Recovery support Galaxy A50 One UI 3.1 Android 11 firmware. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The TWRP 3.5.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET ME KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN
Manual Instructions for Flashing and Rooting
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing TWRP as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Install Magisk-v22.0.apk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions - Details
Download
TWRP 3.5.0 A11
Magisk22 app
Thanks to:
@neel0210 for Kernel Source
@Enzoaquino for OrangeFox
Good work
Thanks for twrp
Thank you
Flashing this @ A505GN. Hope it works
The twrp works but the multi disabler didn't work
This is a505gn
I reverted back to 3.4 because I encountered an issue. I'm stuck in bootloop, cannot access twrp nor download mode. Had to remove the back of my phone and unplug the ribbon connecting the battery to the phone just to power it off.
I already flashed the twrp via Odin but when I installed Magick on the phone this came up. Did I done something wrong?
q1pa said:
I already flashed the twrp via Odin but when I installed Magick on the phone this came up. Did I done something wrong?
Click to expand...
Click to collapse
it happens to me sometimes
just rebbot to revocery in twrp
Thank you @redymedan for the recovery. I'm glad to say that
your "how to android" channel is great.
I have a question Please clarify the following.
In this recovery Can we update magisk to latest? (When it released)
Sharath Mane said:
Thank you @redymedan for the recovery. I'm glad to say that
your "how to android" channel is great.
I have a question Please clarify the following.
In this recovery Can we update magisk to latest? (When it released)
Click to expand...
Click to collapse
Yes, you can update it from magisk apps
It worked!
I had to run a patched AP first for magisk to work
Im on a A505G/DS
It worked just fine on my A505FN! Thanks!
Worked perfectly on A505W !
Had to use Multidisabler 3.1 instead.
I have an A505FN and I'm not able to root it with Magisk. If I try to install the linked TWRP_v3.5.0_A505_A11_Magisk.tar with Odin, then I can't reboot into Recovery afterwards - instead the Download-Mode appears again.
With RR-TWRP_v3.4.0_A505_CUBC_OneUI.tar from another Thread, it's possible to start into TWRP after flashing it with Odin. But if I boot into System (LOS 18.1) and start the already preinstalled Magisk, Magisk updates itself and after restart of Magisk I can try to install Magisk and in the first screen "Recovery Mode" is checked. If I click on "Next step", the Option "Recovery Mode" disappears and I can choose a file to patch.
I don't know where I'm wrong.
IngolfN said:
I have an A505FN and I'm not able to root it with Magisk. If I try to install the linked TWRP_v3.5.0_A505_A11_Magisk.tar with Odin, then I can't reboot into Recovery afterwards - instead the Download-Mode appears again.
With RR-TWRP_v3.4.0_A505_CUBC_OneUI.tar from another Thread, it's possible to start into TWRP after flashing it with Odin. But if I boot into System (LOS 18.1) and start the already preinstalled Magisk, Magisk updates itself and after restart of Magisk I can try to install Magisk and in the first screen "Recovery Mode" is checked. If I click on "Next step", the Option "Recovery Mode" disappears and I can choose a file to patch.
I don't know where I'm wrong.
Click to expand...
Click to collapse
Flash stock rom with odin
Reboot. Do not login to google. Check oem grayed out.
Reboot to download mode
Select 3.5.0 twrp as ap. (You should Untick autorestart in options) . Start.
By connecting cable reboot into recovery by using button combo. Do not reboot to system. Do not remove cable.
After entering twrp.
Format data. Next flash multidisabler.
Now select reboot to recovery.
Wait for few minutes, if doesn't boot,force restart by using volume down and power buttons. It will bootup.
You can finish ur setup now.
You can flash other roms . To enter twrp you need to connect cable with pc and use buttons.
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
IngolfN said:
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
Click to expand...
Click to collapse
you will edit your ini.environ.rc
watch it in youtube
IngolfN said:
Thank you Sharath Mane,
I followed your steps again and I was able to install Magisk successfully in the Stock-Android
In the next step, I booted in TWRP again and
- Format Data
- Fomat Dalvik, Cache, System
- flashed Unofficial LOS 18.1 as System Image
after booting into System I started Magisk and after Download and Install there is - *no Magisk installed* - only the App
Is there an additional step neccessary and I have missed it? Or is it not possible with LOS?
Click to expand...
Click to collapse
Goto twrp and select reboot recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Thanks for this. Where is twrp.img for Note 20 Ultra 5G / N986B
Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards
Thanks, for this I'll keep for more year Note 20 Ultra. Time to wait or maybe make GSI for Note.
Yaayyyy
I m newbie to note 20 ultra...i want to flash root and twrp... What steps shld i follow.... Currently i m on stock non rooted.. Confused what to flash via odin..
@corsicanu
Many thanks for the latest update mate. It's working perfectly, as everything from you does
corsicanu said:
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
Click to expand...
Click to collapse
I notice I have bootloder on my device that I didn't install my self. I'm just a average user and have no clue how this was put on my phone. Also all of my apps are older versions an I'm unable to update them. I need help figuring out what's going on. Anyone please help!!!
@corsicanu
Many thanks for the latest update mate
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
monicaONxda said:
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
Click to expand...
Click to collapse
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Where's 2.8
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
monicaONxda said:
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
Click to expand...
Click to collapse
Fw as in firmware. Regarding plain android - search for AOSP based projects, i'm not aware of the active developement so i can't properly advice you in this matter.
Regards
corsicanu said:
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Click to expand...
Click to collapse
i am trying to root my note 20 u device. when all succesfully start from magisk module and twrp, i find the screen flicker for a second every 15 seconds. I'm trying to figure out which app the problem is from. looked in screen recorder and found the problem. apparently from system ui. then start again from the initial step one by one. and the cause of the problem is after installing twrp. I'm on Ui5.1 N986B exyns. i feel twrp has a bug
Now im use back stock recovery and problem has gone
Hi it's been a while since I last install TWRP on SS phone, it got complicated now I have few question, can you help answering?
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
Click to expand...
Click to collapse
- For this, do I have to press the key combo 1 time only after clicking Start Odin or I have to hold till the progress done?
2.
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Click to expand...
Click to collapse
- I never install TWRP on my phone, do I have to follow this step?
-If yes, do I have to install that file right after TWRP first boot (when odin completed flashing)
And finally, does it support android 13?
Thank you so much