Related
I have just updated my rooted 4.3 i9505 to 4.4.2 using mobile odin Pro v4. Here are the steps i followed:
1) Download firmware for your region from sammobile.com
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
3) Use Mobile Odin Pro v4 to flash firmware from step 1 above. It will not update bootloader in firmware. Make sure you tick:
a) Enable Everoot
b) Inject Superuser (SuperSU)
c) Inject Mobile Odin
d) Download mode after flash (so that it will boot straight to download mode)
4) Use PC Odin 3.09 to flash bootloader tar file made in step 2 above. Tick Phone Bootloader Update. DO NOT tick Auto Reboot and F. Reset time.
5) Boot again into download mode to check Knox flag which should remain 0x0
6) Reboot device and wait up to 5mins.
Device will be updated to 4.4.2 and retains root and Knox remains 0x0.
Enjoy.
Edit: I used the information here to transform my S4 into S5:
www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Thanks for the post
I'm curious why it's a two step process. Does mobile Odin not flash the bootloader?
I guess you could do the whole thing with desktop Odin, would I be right in saying you use mobile odin as it does the root for you?
[hello
i have in my s4 i9505 a 4.4.2 rom , no root
is possible use this method to root without tripping knox?
karmac1970 said:
[hello
i have in my s4 i9505 a 4.4.2 rom , no root
is possible use this method to root without tripping knox?
Click to expand...
Click to collapse
you need root first because mobile odin requires root, you are late bro because the new 4.4.2 bootloader has already fix for root de la vega knox 0x0
Upgrading gt-i9505 from 4.2.2 to 4.4.2 WanamLite
I updated from 4.2.2 stock rooted to WanamLite (4.4.2 Touchwiz pre-rooted) yesterday. It was pretty easy:
0) Titanium backup and Nandroid backup. I forgot to back up text messages and a few little things, but no big loss.
1) Flash this from Odin 3.07 (GSM + LTE modem) (as Phone not PDA)
2) Flash XXUEMK9 from here.
3) Install TWRP via custom recovery
4) Flash Wanam as PDA in Odin.
Seemed to work fine
Confusion
To avoid confusion I think people should know this only works if you already have root on 4.3 prior to MKF, it allows you to keep root without tripping knox.
http://forum.xda-developers.com/showpost.php?p=51488982
commandonz said:
Thanks for the post
I'm curious why it's a two step process. Does mobile Odin not flash the bootloader?
I guess you could do the whole thing with desktop Odin, would I be right in saying you use mobile odin as it does the root for you?
Click to expand...
Click to collapse
Mobile Odin does not flash Bootloader. That's why the second step is necessary. Yes, you are right. If you are already rooted, then mobile odin allows you to update the firmware and keep root. You will lose root after updating with desktop odin.
Cheers
Bordo_Bereli51 said:
you need root first because mobile odin requires root, you are late bro because the new 4.4.2 bootloader has already fix for root de la vega knox 0x0
Click to expand...
Click to collapse
You are right. No root method for 4.4.2 (for now) without tripping Knox flag.
I went from 4.2.2 quite easily to 4.4.2 using the steps above. I guess most people are on 4.3 though, 4.2.2 made it easier as Knox isn't on the phone at all.
commandonz said:
I went from 4.2.2 quite easily to 4.4.2 using the steps above. I guess most people are on 4.3 though, 4.2.2 made it easier as Knox isn't on the phone at all.
Click to expand...
Click to collapse
What's your current Knox flag? 0x0?
shayind4 said:
What's your current Knox flag? 0x0?
Click to expand...
Click to collapse
I stayed on a pre-knox bootloader as I went from 4.2.2 to 4.4.2, so I have no knox flag.
commandonz said:
I stayed on a pre-knox bootloader as I went from 4.2.2 to 4.4.2, so I have no knox flag.
Click to expand...
Click to collapse
Lucky you. I'm on 4.4.2 bootloader, Knox flag 0x0, rooted.
shayind4 said:
Lucky you. I'm on 4.4.2 bootloader, Knox flag 0x0, rooted.
Click to expand...
Click to collapse
I deliberately didn't upgrade to 4.3 and held of on 4.4 purely to avoid Knox. It probably wouldn't matter much because I never plan to use Knox, and I think you can still do most things with the knox flag tripped, but it seemed better to avoid.
4.4.2 isn't much different from 4.2.2 really. I'm hoping for a stability increase, maybe a slight performance increase and battery savings. But I mostly just wanted to come up to date.
Hi, you wrote that we need to make .tar file from this files:
shayind4 said:
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
Click to expand...
Click to collapse
I found another tutorial for this and that user wrote this:
3. Package 2 Tar files, one with the bootloader ( aboot.mbn,sbl1.mbn,sbl2.mbn, sbl3.mbn), the second one with everything else.
Click to expand...
Click to collapse
Are this files- tz.mbn and rpm.mbn important too? Or it doesn't matter?
pRo_lama said:
Hi, you wrote that we need to make .tar file from this files:
I found another tutorial for this and that user wrote this:
Are this files- tz.mbn and rpm.mbn important too? Or it doesn't matter?
Click to expand...
Click to collapse
Hi
All the 6 mbn files are bootloader files needed for the bootloader tar file.
You need 2 tar files:
A) Downloaded firmware= tar file with all the contents (you dont have to open it). You can make a copy to use in step 2 below for extracting mbn files (bootloader files). You will notice that step 2 in OP says make a copy of downloaded firmware.
B) Bootloader tar = all the mbn files
Mobile odin (OP step 3) does not flash bootloader when you use the downloaded full firmware (in A above). That's why you need the bootloader tar to be flashed via PC odin (OP step 4).
Both tutorials are similar.
Cheers
shayind4 said:
I have just updated my rooted 4.3 i9505 to 4.4.2 using mobile odin Pro v4. Here are the steps i followed:
1) Download firmware for your region from sammobile.com
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
3) Use Mobile Odin Pro v4 to flash firmware from step 1 above. It will not update bootloader in firmware. Make sure you tick:
a) Enable Everoot
b) Inject Superuser (SuperSU)
c) Inject Mobile Odin
d) Download mode after flash (so that it will boot straight to download mode)
4) Use PC Odin 3.09 to flash bootloader tar file made in step 2 above. Tick Phone Bootloader Update. DO NOT tick Auto Reboot and F. Reset time.
5) Boot again into download mode to check Knox flag which should remain 0x0
6) Reboot device and wait up to 5mins.
Device will be updated to 4.4.2 and retains root and Knox remains 0x0.
Enjoy.
Edit: I used the information here to transform my S4 into S5:
www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Click to expand...
Click to collapse
Thank you for your explanation. But I have some questions:
1. Can you use the same method to update keeping root from a 4.3 rooted version to a more recent 4.3 not safe-rootable version (not rootable without triggering the knox)?
2. Can you first flash the new bootloader with PC Odin and then all the rest with Mobile Odin?
3. What happens if you only flash with Mobile Odin everything except the new bootloader (new firmware/old bootloader)? Does the device boot?
4. What happens instead if you only flash the new bootloader with the PC Odin (new bootloader/old firmware)? Does the device boot?
5. Can you use your method (adequately adapted) to downgrade the firmware? That is, after an update to 4.4.2 or a newer 4.3, can you just flash the old firmware with Mobile Odin, keeping the new bootloader so that you do not trigger the knox (new bootloader/older firmware)?
Thank in advance.
odicamillo said:
Thank you for your explanation. But I have some questions:
1. Can you use the same method to update keeping root from a 4.3 rooted version to a more recent 4.3 not safe-rootable version (not rootable without triggering the knox)?
2. Can you first flash the new bootloader with PC Odin and then all the rest with Mobile Odin?
3. What happens if you only flash with Mobile Odin everything except the new bootloader (new firmware/old bootloader)? Does the device boot?
4. What happens instead if you only flash the new bootloader with the PC Odin (new bootloader/old firmware)? Does the device boot?
5. Can you use your method (adequately adapted) to downgrade the firmware? That is, after an update to 4.4.2 or a newer 4.3, can you just flash the old firmware with Mobile Odin, keeping the new bootloader so that you do not trigger the knox (new bootloader/older firmware)?
Thank in advance.
Click to expand...
Click to collapse
Hi
1) Yes. Just update Supersu and disable Knox. I used it safely to update from rooted 4.3 to rooted 4.4.2, nox flag 0x0.
2) No. You need to flash firmware with Mobile odin first so that root can be injected at the same time (before flashing bootloader with PC Odin).
3) The device may boot but not sure with this tutorial. Some people have updated from 4.2.2 (no knox bootloader) to 4.4.2 keeping old bootloader, and they have no KNOX using a different method. Check post #5.
4) It may boot but you will lose root. You cannot safely root afterwards.
5) NO. Flashing older firmware or older bootloader will trigger Knox flag.
regards
nickp27 said:
To avoid confusion I think people should know this only works if you already have root on 4.3 prior to MKF, it allows you to keep root without tripping knox.
Click to expand...
Click to collapse
currently I have MKF, rooted via saferoot, knox 0x0.
spamtrash said:
currently I have MKF, rooted via saferoot, knox 0x0.
Click to expand...
Click to collapse
Hi ,
I wonder the same thing, if the tutorial is working from a MKF 4.3 with saferoot
Thanks for your answers
lukvdb78 said:
Hi ,
I wonder the same thing, if the tutorial is working from a MKF 4.3 with saferoot
Thanks for your answers
Click to expand...
Click to collapse
When I said prior to, I meant including. If you have knox 0x0 and root either through saferoot or kingo then this should work.
Howdy everyone-
I'm currently rooted with Android 5.0, PD1 firmware, and "unlocked" bootloader. I want to go to 6.0/PF1 and remain rooted. I've read muniz_ri's thread, but I want to make sure I'm understanding everything. I'm worried I'm not interpreting the instructions for "unlocked" phones correctly.
- If my bootloader is already "unlocked", all I need to do is wipe from within Recovery and then flash one of the two rooted ROMs, provided in the thread yes? I don't need to flash the G900V_PF4_Bootloader or anything else after, right?
- Is there anything wrong with using FlashFire to flash the rooted ROM?
-
No, you need to match bootloader and rom as same level, mm rom needs mm bootloader , lp rom needs lp bootloader. So in bootloader unlock method will install unlocked mm bootloader, and then flash mm rom as your choice
Win0416 said:
No, you need to match bootloader and rom as same level, mm rom needs mm bootloader , lp rom needs lp bootloader. So in bootloader unlock method will install unlocked mm bootloader, and then flash mm rom as your choice
Click to expand...
Click to collapse
Is there any way to upgrade if you have a locked bootloader? My emcc or whate very is 11xxx... so I can't unlock the bootloader.
Win0416 said:
No, you need to match bootloader and rom as same level, mm rom needs mm bootloader , lp rom needs lp bootloader. So in bootloader unlock method will install unlocked mm bootloader, and then flash mm rom as your choice
Click to expand...
Click to collapse
Appreciate the reply. So in other words... enter SafeStrap recovery, flash SafeStrap_PF4_Bootloader_Unlock_AIO.zip, wipe data, then flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip ?
bornbredndead said:
Appreciate the reply. So in other words... enter SafeStrap recovery, flash SafeStrap_PF4_Bootloader_Unlock_AIO.zip, wipe data, then flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip ?
Click to expand...
Click to collapse
I tried this but it doesn't boot past the Galaxy Custom screen...
Am I missing a kernel flash or something? I dont get it..
bornbredndead said:
Appreciate the reply. So in other words... enter SafeStrap recovery, flash SafeStrap_PF4_Bootloader_Unlock_AIO.zip, wipe data, then flash G900V_PF4_Stock_Deodexed_Debloated_Rooted_ROM.zip ?
Click to expand...
Click to collapse
Technically yes, but please follow exactly same procedure as 1st Easiest,
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Download and install VZW_BPB1_ODEX_DEODEX_V9.zip by TWRP or other Flashing tool
Reboot to Download Mode
In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
(And then do it again, if binary status is not official
After Phone reboots pull battery reboot to download mode (pwr+voldwn+home) and make sure current binary status is official
If not In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
If current binary is official reboot phone Setup Rom.
There is no need to setup any accounts unless you plan on running this rom
Download and install Bootloader_Unlock_Safestrap.apk
Open Safestrap app and install the safestrap recovery to the system
Open safetrap app and click Reboot To Recovery Button
Flash: (Choose 1 Whatever One You Choose Is The Firmware And Bootloader Version You Will Be On)
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter TWRP Recovery (volup+pwr+home) Wipe Data and System and Flash A Rom That matches Firmware For example PB1 would be a 5.0 rom PD1 Or PF4 would be 6.0.1 Rom
Win0416 said:
Technically yes, but please follow exactly same procedure as 1st Easiest,
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Download and install VZW_BPB1_ODEX_DEODEX_V9.zip by TWRP or other Flashing tool
Reboot to Download Mode
In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
(And then do it again, if binary status is not official
After Phone reboots pull battery reboot to download mode (pwr+voldwn+home) and make sure current binary status is official
If not In Odin Under AP slot load G900V_Firmware_PB1.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
If current binary is official reboot phone Setup Rom.
There is no need to setup any accounts unless you plan on running this rom
Download and install Bootloader_Unlock_Safestrap.apk
Open Safestrap app and install the safestrap recovery to the system
Open safetrap app and click Reboot To Recovery Button
Flash: (Choose 1 Whatever One You Choose Is The Firmware And Bootloader Version You Will Be On)
SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter TWRP Recovery (volup+pwr+home) Wipe Data and System and Flash A Rom That matches Firmware For example PB1 would be a 5.0 rom PD1 Or PF4 would be 6.0.1 Rom
Click to expand...
Click to collapse
I appreciate your reply. Unfortunately those instructions did not work for me. After flashing SafeStrap_PF4_Bootloader_Unlock_AIO.zip, the phone does not power off, and TWRP recovery is not installed at this point. Not sure where I'm going wrong.
Greetings.. I have problem rooting latest firmware g920fxxs4dpge. Is there any working root method? I wanna flash custom rom to improve battery life. Cf Auto root cause error in Odin. Thank you
Flash the latest TWRP recovery onto your phone and install supersu from the recovery.
I think there isn't stable supersu.zip file for my firmware.
Mpongr33 said:
I think there isn't stable supersu.zip file for my firmware.
Click to expand...
Click to collapse
It's universal;
http://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Yes, ok... but after flash twrp trough Odin .11, process pass but remain stock recovery on smartphone.
I think that problem is locked bootloader. How to check it if is it locked or unlocked?
This device uses dm-verity!
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
From https://twrp.me/devices/samsunggalaxys6.html
Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
DannySB1 said:
Hello,
I am attempting to downgrade from Android 8 to 7 on Galaxy S7. When I attempt to flash the old firmware I get the error 'Device 3 - Binary 2'. Does anyone know if there is a workaround for this yet?
Click to expand...
Click to collapse
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
cooltt said:
Odin will not let you flashback to a previous boot loader version, you have to do it through TWRP. So either flash the nougat firmware with TWRP first or any nougat based rom, then flash nougat via odin which will remove root and TWRP.
Click to expand...
Click to collapse
Are there any instructions for this?
Will secure apps (Banking etc) work again after removing root?
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
edit: As for banking, if you go root then flash back to stock you should have no issues. Even if you stay root, things like Magisk will hide root status from apps and pass safetynet. Your biggest issue would be the loss of Knox, which voids warranty and breaks some Samsung apps.
Beanvee7 said:
I was under the impression you could via Odin if OEM unlock was enabled, without needing TWRP or root. https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-downgrade-android-oreo-8-0-t3821495
Click to expand...
Click to collapse
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
DannySB1 said:
It is not possible as per some of the replies to that thread. I spent a few hours playing TWRP yesterday and it was not possible either.
Click to expand...
Click to collapse
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Bipnbarsha said:
plz tell me how to downgrade i upgraded my phone to oreo now there's no network i need to downgrade back to marshmellow i also installed marshmellow but it stuck on samsung bootloop plz help me
Click to expand...
Click to collapse
What device? What firmware? What Rom?
S7 edge on oreo and stock rom my network was working fine on marshmellow but after oreo update my mobile network not working unfortunatly my binary has been updated before update i back up everything with twrp but now when i restore using twrp my phone stuck on samsung logo plz help mee
downgrand note 9 N9600 ZTO
i need to downgrand my note 9 i pay for the service of someone who can help me. i'm on the last firmawre bdo android 9 and i want to downgrand to the latest firmware of android 8.1. My note 9 is the N9600 ZTO.
email
[email protected]
whatsapp and telegram
+5582994311001
cooltt said:
Ok so listen, it can be done as i said but it's not easy. The choice you have of course before attempting this is to just install a android 7 custom ROM? many nougat ROMs are just stock with the bloatware removed and the boot-loader version isn't checked during flash.
Here's another way to go back, i can't guarantee it will work though i haven't tried it on an S7.
Downgrade to an older firmware with an older bootloader even if one keeps the newer bootloader on his device.
So what's how's it done?
Download the firmware file (.tar) which you want to downgrade to and open it with an archiver application (7zip). Extracts all the files to a folder and repacks them again in a .tar file but leaving every file out which ends in .bin (e.g. sboot.bin etc.). This .tar file can now be flashed like any other firmware file via Odin and it should run through it without any problems.
Hope this helps.
Click to expand...
Click to collapse
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
laurentiudll said:
Hey man, can you please explain this better ? Im using a galaxy s7 edge, but my firmware doesnt have a TAR file. there are 4 .md5 files (AP,BL,CP,CSC) that are flashable through odin. I want to downgrade bootloader
Click to expand...
Click to collapse
Hello that method no longer works, you can't downgrade anymore
cooltt said:
Hello that method no longer works, you can't downgrade anymore
Click to expand...
Click to collapse
I can downgrade to 14.1 Lineage OS.
Edit: There is no way do downgrade the official firmware
Full credit to @googlephoneFKLenAsh for the guide for the s7/7+. Reposting here so y'all can see.
There are two ways to do this, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
Firmware can be downloaded here:
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
First and preferred method:1. Download firmware, extract it and move AP file to rooted tablet.
2. Use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
3. Move that patched Magisk.tar AP back to your computer.
4 Using Odin, flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot.
Second method:1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.
Is the guide still up to date?
noahthedominator said:
Full credit to @googlephoneFKLenAsh for the guide for the s7/7+. Reposting here so y'all can see.
There are two ways to do this, and the key is never flash stock AP without patching vbmeta at the same time. Never let the stock vbmeta.img flash to your device. The stock vbmeta.img in stock AP will enable Android verified boot and will lead to factory reset in the next boot.
Firmware can be downloaded here:
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download
Samsung Galaxy Tab S7 FE Firmware Download SM-T733 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
First and preferred method:1. Download firmware, extract it and move AP file to rooted tablet.
2. Use magisk to patch the whole AP file and magisk will patch both boot.img and vbmeta.img.
3. Move that patched Magisk.tar AP back to your computer.
4 Using Odin, flash magisk patched AP in AP slot and BL in BL slot and HOME_CSC in CSC slot.
Second method:1. Download vbmeta_disabled.tar from https://forum.xda-developers.com/t/...root-s20-series-and-upgrade-firmware.4079353/
2. Patch boot.img using magisk: extract boot.img.lz4 from stock AP, compress it to a tar file and patch the tar file in magisk.
3. Uncheck auto reboot in ODIN, flash stock AP in AP, BL in BL and HOME_CSC in CSC slot, and vbmeta_disabled.tar in USERDATA slot at the same time. With the vbmeta_disabled.tar, Android verified boot remains disabled. Remember to flash them at the same time in ODIN so that Android verified boot remains disabled. If you flash vbmeta_disabled.tar after flashing stock AP, Android verified boot will be re-enabled and it will ask for factory reset.
4. Check auto reboot in ODIN, flash magisk patched boot.img in AP slot.
Click to expand...
Click to collapse
SERGE4NT said:
Is the guide still up to date?
Click to expand...
Click to collapse
The first method works but step one should read un-rooted and not rooted.
No. This is supposed to say rooted. Read the title of the post. This is for those who want to keep root access and update the system without wiping data.
lewmur said:
The first method works but step one should read un-rooted and not rooted.
Click to expand...
Click to collapse
SERGE4NT said:
Is the guide still up to date?
Click to expand...
Click to collapse
Yes, up to date and latest firmware is available at Samfw
lewmur said:
The first method works but step one should read un-rooted and not rooted.
Click to expand...
Click to collapse
But once you flash to the latest stock, it is no longer rooted. The whole point of using Magisk to mod the AP file, is to get root back.
lewmur said:
But once you flash to the latest stock, it is no longer rooted. The whole point of using Magisk to mod the AP file, is to get root back.
Click to expand...
Click to collapse
Are you trolling? The entire point of the guide is to MAINTAIN root access and update the system. That is why the stock AP is moved to magisk and patched. As the instructions state, if the STOCK ap is flashed it will remove root / wipe the system. Hence why we need to patch it with magisk BEFORE it is flashed to the device.
noahthedominator said:
Are you trolling? The entire point of the guide is to MAINTAIN root access and update the system. That is why the stock AP is moved to magisk and patched. As the instructions state, if the STOCK ap is flashed it will remove root / wipe the system. Hence why we need to patch it with magisk BEFORE it is flashed to the device.
Click to expand...
Click to collapse
No, I'm not trolling. It was my honest belief that you needed to have the same version ROM already installed BEFORE you used Magisk. I have always done that and backed up everything before flashing.
edit: And why would flashing stock wipe anything more the first time, if you flash HOME in CSC? Your method does save having to flash twice but it seems both should work.