Question Flash the Fold 3 with TWRP - Samsung Galaxy Z Fold3

Hello,
I want to update my phone, but it's rooted with Magisk. I know I can download the update and patch the new image with Magisk but, what I do not know is if I can flash the new patched image via TWRP ?
Is Odin the ONLY way or would TWRP do the exact same job ?
Thanks

Allmightyusfame said:
Hello,
I want to update my phone, but it's rooted with Magisk. I know I can download the update and patch the new image with Magisk but, what I do not know is if I can flash the new patched image via TWRP ?
Is Odin the ONLY way or would TWRP do the exact same job ?
Thanks
Click to expand...
Click to collapse
You can flash Magisk.zip via TWRP

.

Related

Root without custom recovery?

Is it possible to unlock the bootloader and flash via adb magisk in order to root the phone but still able to mentain the oem recovery so i can flash the updates that are coming more easily?
if u r rooted u cannot flash OTA's, so no u can't
Yes it's possible, however when you install the update you will lose root and have to root it all over again.
Sent from my ONEPLUS A5010 using Tapatalk
I'm new to Oneplus, but Flashfire has worked for me when twrp cannot be installed.
Bradl79 said:
if u r rooted u cannot flash OTA's, so no u can't
Click to expand...
Click to collapse
How?
bkeaver said:
Yes it's possible, however when you install the update you will lose root and have to root it all over again.
Click to expand...
Click to collapse
The process will only be to flash magisk via fastboot, right ?
prologikus said:
Is it possible to unlock the bootloader and flash via adb magisk in order to root the phone but still able to mentain the oem recovery so i can flash the updates that are coming more easily?
Click to expand...
Click to collapse
You don't use adb... Patch the boot image with the Magisk Manager and then flash it with fastboot. There are instructions for it in the Magisk release thread.
When updating the OS you'll have to do it again.
In my opinion, the only reason to do it this way is if you've got limited bandwidth and can't download the full OTA zips. Using the full zip is way, way easier... Just download the full OTA file, flash in TWRP and then flash the Magisk zip right after. Done. You don't need a computer at all...
Didgeridoohan said:
You don't use adb... Patch the boot image with the Magisk Manager and then flash it with fastboot. There are instructions for it in the Magisk release thread.
When updating the OS you'll have to do it again.
In my opinion, the only reason to do it this way is if you've got limited bandwidth and can't download the full OTA zips. Using the full zip is way, way easier... Just download the full OTA file, flash in TWRP and then flash the Magisk zip right after. Done. You don't need a computer at all...
Click to expand...
Click to collapse
Can you give precise instruction hot to flash full ota over twrp???
I Have files... Than... Am on Honor View 10C432B130 wanna go to b140

Nova Plus MLA-L11 meafnaf

I have received an OTA update for may Nova Plus from B332 to B341
here is the "dataversion.txt" file:
"ro.confg.hw_userdataversion=MLA-L11C185B341_DATA_MLA-L11_hw_meafnaf"
My phone is rooted and i have a TWRP recovery 3.2.1.0
the update contains 3 files ( update_data_public.zip, update.zip and update_MLA-L11_hw_meafnaf.zip )
Can i install updates with TWRP, or i have to go back to stock recovery ?
Now i'm uploading "update_MLA-L11_hw_meafnaf.zip" to mega, and i thing it's a patch file for Cust meaf and Naf Region
for MLA-L11 ( I will post link for who update fail to use it, but on your only risk )
zaabolla said:
I have received an OTA update for may Nova Plus from B332 to B341
here is the "dataversion.txt" file:
"ro.confg.hw_userdataversion=MLA-L11C185B341_DATA_MLA-L11_hw_meafnaf"
My phone is rooted and i have a TWRP recovery 3.2.1.0
the update contains 3 files ( update_data_public.zip, update.zip and update_MLA-L11_hw_meafnaf.zip )
Can i install updates with TWRP, or i have to go back to stock recovery ?
Now i'm uploading "update_MLA-L11_hw_meafnaf.zip" to mega, and i thing it's a patch file for Cust meaf and Naf Region
for MLA-L11 ( I will post link for who update fail to use it, but on your only risk )
Click to expand...
Click to collapse
I don't think it will work with twrp, but you can try if you want.
And what root method you have there? If it is a systemless one, it will somesort of persist, but probably you will have to apply it again, as your boot.img will be modified. If it isn't a systemless one, then you must remove root first
Vinnom said:
I don't think it will work with twrp, but you can try if you want.
And what root method you have there? If it is a systemless one, it will somesort of persist, but probably you will have to apply it again, as your boot.img will be modified. If it isn't a systemless one, then you must remove root first
Click to expand...
Click to collapse
phh Superuser method,
then i have to flash boot file or use "addonsu-remove-14.1-arm64-signed.zip" to unroot it
flash stock recovery and after all update the phone.
and if i want root again i have to unlock again the bootloader, flash TWRP recovery again and PHH root
i think i will keep my phone like that untill someone do an oreo rom 4 it, i'm not interested with security patches
and thanks 4 ur replay

Rooting latest Pie builds

Hi
Anyone tried rooting latest Pie builds with Magisk or SuperSU? Cannot manage to make it working. I'm on ZRKN from this topic (https://forum.xda-developers.com/ga...f-sm-g965f-t3867627/post78170460#post78170460). Please share some tutorial. Thanks.
4timepi said:
Hi
Anyone tried rooting latest Pie builds with Magisk or SuperSU? Cannot manage to make it working. I'm on ZRKN from this topic (https://forum.xda-developers.com/ga...f-sm-g965f-t3867627/post78170460#post78170460). Please share some tutorial. Thanks.
Click to expand...
Click to collapse
You must flash the oreo Bootloader BRJ6 (only Bootloader BL!) with Odin, restart into system. After that go into Downloader modus and flash the TWRP Image with Odin.
Works everytime on my S9.
Oel said:
You must flash the oreo Bootloader BRJ6 (only Bootloader BL!) with Odin, restart into system. After that go into Downloader modus and flash the TWRP Image with Odin.
Works everytime on my S9.
Click to expand...
Click to collapse
Thanks for suggestion. Please tell me, do I need to flash dm-verify disabler, antyroot etc.? Or BRJ6 Bootloader, TWRP and Magisk only?
4timepi said:
Thanks for suggestion. Please tell me, do I need to flash dm-verify disabler, antyroot etc.? Or BRJ6 Bootloader, TWRP and Magisk only?
Click to expand...
Click to collapse
Im pretty sure you will need dm-verify still then twrp then magisk
Is here anybody who rooted pie build? Please share with us files you use to complete this task with some short tutorial. Now I'm waiting 7 days to unlock option appear again. As markyc25 said:
1. downgrade bootloader to Oreo BRJ6
2. unlock bootloader & go straight (without full reboot) to download mode
3. flash TWRP (twrp-3.2.3-0-starlte ?) with ODIN & go straight (without full reboot) to recovery mode
4. do not allow modification ?
5. wipe data
6. flash No Verify Encrypt zip ? (which version ?)
7. flash RMM Bypass zip ? (which version ?)
8. flash Magisk (latest 18.0 build ?)
Could somebody answer my question marks and post working files? I don't want to wait 7 days more
I'll appreciate your help.
after 14 days someone did anything? a guide to root pie with attached files???

Root pie Dec update (v10.0.2)

I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..
This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.
Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?
Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.

Issues with lastest OTA update

Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Jpigas said:
Hi,
I use a RMX2063 since last month, rooted with the TWRP method I found in this forum since day 0. I tried to install the lastest OTA update, that was released last week (RMX2063 _11_A.22), but I have issues to keep magisk working.
Either I do a clean install or a dirty flash, I enter into a bootloop every time I flash lastest magisk version (20.4). Otherwise, the phone works OK if I reflash the OTA and use it without rooting.
Any solutions to that, so I don´t have to downgrade the phone?
Click to expand...
Click to collapse
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
mepadiernos said:
It doesn't work. In order for me to get root afterwards is to flash the latest for rmx2061, extract the boot.img, modify it with magisk and flash the modified boot.img afterwards
Click to expand...
Click to collapse
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Jpigas said:
First of all, thx for the quick response.
I think I already tried that, you mean flashing the modified boot.img via TWRP? (install -> install image -> "boot")?
After that I had another bootloop ("system image is destroyed" realme message)
Click to expand...
Click to collapse
I was actually referring to flashing via fastboot.
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
mepadiernos said:
I was actually referring to flashing via fastboot.
Click to expand...
Click to collapse
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Jpigas said:
The phone enters bootloop anyway (system destroyed), but thank you anyway @mepadiernos. Any other idea?
Click to expand...
Click to collapse
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
mepadiernos said:
Hmmm, I do remember that the twrp provided here for the Realme 6 Pro breaks encryption after I upgraded to .27 so I had to flash the .20 for rmx2061 via stock recovery. I had to put the ozip in the microsd. I believe that will factory reset the phone. When it does I went through the process of setting up my phone sans root. I installed magisk manager and proceeded to patch the extracted boot image from the ozip, the update for the rmx2061, and flashing via fastboot. So, I have root but no twrp.
Click to expand...
Click to collapse
It doesn´t worked for me, buy, anyway, I´m planning to downgrade due to the very high power consumption. Nowadays the phone struggles to reach 3-4h screen on, versus the 6h I managed to reach on previous version. What do you guys think about it?

Categories

Resources