How To Guide Rooting the SM-F711B (on Version F711BXXU2AUI4) working

Search This thread
For me it does not necessarily have to be a flip phone. Just f*** compact, but without hardware restriction. That's why I loved the Xperia Z3 Compact. Unfortunately there are no reasonable compact phones on the market right now in my opinion. The Z Flip 3 was the best compromise for me at the moment. Would love to see a Xiaomi compact phone 😂 but that's off topic.
 
  • Like
Reactions: FFW

FFW

Senior Member
May 24, 2020
74
48
For me it does not necessarily have to be a flip phone. Just f*** compact, but without hardware restriction. That's why I loved the Xperia Z3 Compact. Unfortunately there are no reasonable compact phones on the market right now in my opinion. The Z Flip 3 was the best compromise for me at the moment. Would love to see a Xiaomi compact phone 😂 but that's off topic.
This is *exactly* why I bought his phone :ROFLMAO:

I want something that works decently fast and reliably (which seems to exclude those otherwise nifty Cubot phones) and fits into my trouser front pocket without bothering me - which means for me that I don't care much about thickness, but 10..12cm total height would be nice and anything above 13cm is simply inacceptable.

That being said, the battery of my XZ1 compact is beginning to get unusable (sadly, as I must note - LOS on that phone is running really great and Flamefire is even planning to upgrade the XZ1 Compact LOS version to Android 12), and as good as that phone is - battery replacement is a royal pain for that one and something I would not dare to do as long as it is my main phone.

Hence the Flip :)

But back to topic here: could someone add a brief explanation on how he installed Magisk with some more explanations (e.g. phone freshly reset and just minimal setup made or with completed setup prior to letting Magisk do its task?

When I tried to install the rooted bootloader, my Flip ended in a bootloop and I had to reflash it with Odin.

My setup was:
  • no SIM installed
  • skipped what I could during setup
  • connected it to the PC
  • just uploaded Magisk and the boot.img extracted from the Frija image - the image had the same version as what was installed on the phone
  • let Magisk prepare the boot file
  • uploaded the changed bootloader with Odin as described above (at least I hope so...)
  • cursed and reset everything.
Since this is my first Samsung and my first attempt to root without TWRP I most probably have missed something. For now, I stay unrooted until I get more information on what might have happened, especially since the procedure described here differs a bit from what the manual for Magisk says (they use the complete AP file). But I feel I want to replace Netguard with my trusted AfWall+ and Wireguard always-on VPN to my PiHole sooner or later again.

Any directions or links to information are appreciated. I have to admit I feel a bit overwhelmed from the various ways rooting needs to be done on Samsung devices my search yielded until now...
 
  • Like
Reactions: david.siebauer

d0x360

Senior Member
Mar 11, 2009
94
17
Soooo... You're still the only person to make this "work". Seems kinda strange. I've tried it on 3 snapdragon z Flip3's and your "method" hasn't done anything.
 

FFW

Senior Member
May 24, 2020
74
48
Soooo... You're still the only person to make this "work". Seems kinda strange. I've tried it on 3 snapdragon z Flip3's and your "method" hasn't done anything.
You might want to look closer - https://forum.xda-developers.com/t/just-tweak-it-zflip3-debloat-root-plugins-battery.4356335/ . Admittedly, the process is described in greater detail there, but I don't think that justifies implying that it does not work at all.

Seems to me that Flip3 users are simply lazy when it comes to rooing at the moment. Since AFAIK there is no working custom ROM for the Flip3 available at the moment, the Flip3 is currently missing one of the main reasons for rooting. :rolleyes:
 

m3nt10n

New member
May 12, 2012
1
0
Hello, I rooted the phone, you can somehow remove these screens at startup:
20211126_201104.jpg
20211126_201120.jpg
analogue up_param for Galaxy S20, S21
 
Last edited:

FFW

Senior Member
May 24, 2020
74
48
Hello, I rooted the phone, you can somehow remove these screens at startup:
analogue up_param for Galaxy S20, S21
AFAIK no. If I am not mistaken, these screens are generated by the phone firmware itself, so the only way to get rid of them is to get Samsung to remove them - good luck with that :)
Apart from that, at least the first of these screens fulfils a safety function. They tell the user (albeit in a very coloured way, both from the optics and from the content) that he ought to take care what he does. A rooted phone is like your computer at home - don't blindly do stupid things.

But why do you care? They pop up and disappear again by themselves.
 

Darkeligos

Senior Member
Jul 22, 2010
83
4
I have to admit I don't really get what brings you to this conclusion.

If you search for a more detailed explanation of the rooting process, take a look at the link to the other XDA thread I posted above.
But nobody but the OP has done it, with minimal pictures. And people in this thread are having issues after rooting.
 

beanbean50

Senior Member
Jul 9, 2008
3,360
1,587
London
Flash Android 12 Serbia thru Odin while patched the AP using magisk since I'm on root previously... somehow couldn't boot.. I have to factory reset and reflash the firmware.. need advise if I try to root back the device.. will it boot without any issue?
Any luck rooting with Android 12 yet? the nearest I can get is booting up to a white screen with the patched AP file ..hmmm
 

TarikVaineTree

Senior Member
Dec 7, 2012
98
15
First of all:
I'm no Dev...just someone who likes to play lego.
From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.

I've read a good startup here.
Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.

(https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
(1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)

Anyways...here are maybe small hints to avoid a few traps.

a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
There appears a possibility of choice.
Press VolUp short: get the mobile on standby to flash the rom via odin.
Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
Of course this can possibly be done via adb/fastboot commands.
Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.

b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
Flashing the tar back to the mobile via odin was little bit tricky.
It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
I had to patch it to BL too.

Cheers
MikGx
Thanks for your tips. I have a very odd problem: I just can't activate my Wifi after rooting. Everything else works, even the camera, that was reported not to work after rooting, but not the Wifi. Any ideas?
 

beanbean50

Senior Member
Jul 9, 2008
3,360
1,587
London
I'm waiting for latest A12 OTA - XME Malaysia. Once it release, will give a try to root it. As of now on previous Serbia A12. Will let you know anything.
just managed to root A12 tonight after weeks of trying. Yippee! It was all to do with which Magisk version is used to patch the stock AP file. I found a random tutorial and downloaded the Magisk version 'app-release ' and Bingo rooted and booted ! very bagus 😁

 
  • Like
Reactions: Clusco and FFW

FFW

Senior Member
May 24, 2020
74
48
just managed to root A12 tonight after weeks of trying. Yippee! It was all to do with which Magisk version is used to patch the stock AP file. I found a random tutorial and downloaded the Magisk version 'app-release ' and Bingo rooted and booted ! very bagus 😁

This is great to read! Let's see when a new official Magisk version will be there that has these changes included. Did you follow the A52s 5G process in the link 1:1?
 

beanbean50

Senior Member
Jul 9, 2008
3,360
1,587
London
This is great to read! Let's see when a new official Magisk version will be there that has these changes included. Did you follow the A52s 5G process in the link 1:1?
I read through the guide and it's more or less the same as what I've been trying for the past few weeks, but downloading the Magisk apk provided (app-release) made all the difference which flashes the AP file correctly without bootloop when flashing in odin.
 
  • Like
Reactions: FFW

beanbean50

Senior Member
Jul 9, 2008
3,360
1,587
London
Did you had any issue such as Wi-Fi not working? Camera having issue?

Currently what Magisk version you're on? Kindly advice as I want to root it too...

Wifi & camera are working just fine as for rooting I did this...


Flashed the stock firmware, booted up and installed the experimental version of Magisk v1 from the link I posted above (there's 3 Magisk files in the download, choose 'app-release' version)

Then patched the whole AP file in the new Magisk and flashed that in Odin and it should boot up rooted, but remember to cancel any Magisk updates otherwise bootloop and it wiped my data along the way.

Edit:
there's an update to the alpha Magisk app ...

 
Last edited:
  • Like
Reactions: Clusco

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    First of all:
    I'm no Dev...just someone who likes to play lego.
    From this point of view everything I post here is taken from somewhere else in the Internet and used by your own risk.

    I've read a good startup here.
    Hopefully this makes this thread clear enough so that i dont need to describe the whole procedure step by step.

    (https://www.naldotech.com/root-samsung-galaxy-z-flip-3-5g-magisk/)
    (1.OEM-Unlock,2.BL-Unlock,3.extract boot.img,4.patch boot.img via magisk on the unrooted mobile,5.patch boot.img.tar to AP&BL via Odin, 6.pray)

    Anyways...here are maybe small hints to avoid a few traps.

    a) Just do the oem-unlock in the dev-options (enabled by tapping buildnumber 5 times) is just half of the rent.
    Afterwards i had to go in Download-mode (switch of mobile, press volUp+volDown and connect PC-cable.)
    There appears a possibility of choice.
    Press VolUp short: get the mobile on standby to flash the rom via odin.
    Press VolUp LOONG: get the mobile to the menu where the bootloader can finally get unlocked. (Otherwhise every try to patch a rooted img will be blocked by bootloader-protection.)
    Of course this can possibly be done via adb/fastboot commands.
    Funny side note: OEM-Unlock-option will completely disappear from Dev-options and waranty is lost. Also the mobile stops to get Updates OTA which means that you have to update manually whenever a new version will appear in the net.

    b) patching boot.img via magisk should work as described in many other magisk-rooting-manuals.
    Flashing the tar back to the mobile via odin was little bit tricky.
    It doesnt reach out just to provide the magisk_patched.tar to Odin just on the AB-line.
    I had to patch it to BL too.

    Cheers
    MikGx
    2
    I'm waiting for latest A12 OTA - XME Malaysia. Once it release, will give a try to root it. As of now on previous Serbia A12. Will let you know anything.
    just managed to root A12 tonight after weeks of trying. Yippee! It was all to do with which Magisk version is used to patch the stock AP file. I found a random tutorial and downloaded the Magisk version 'app-release ' and Bingo rooted and booted ! very bagus 😁

    1
    I have to be a little skeptical when my rooted Note 8 came out a year after the S7. There are other reasons, but they tend to make the trolls restless. We'll skip them.
    Ok I might be off by a year or 2 but I can say with 100% certainty that the note 9, 10, 10+ and flip3 don't have an unlock bootloader option.

    I bought all 4 from Samsung all unlocked and not tied to any carrier. First boot with no sim I checked dev options and there was no option to unlock the bootloader. My note 9 might have had the option in the menu but it was grayed out and I couldn't find anyway to make it work.

    A quick Google search for rooting the snapdragon version of any of these devices essentially says "NOPE".

    The only way to root one is to buy a non US version. If it has a snapdragon soc you're out of luck.
    1
    You got where I said "I guess the disclaimer is misleading" right?
    I didn't see that sentence in any of the posts but perhaps I just missed it.

    It doesn't change anything either way. Anything is possible, even you somehow getting a device with this setting. That being said you also seem to be the only person ever to receive a USA device with said option.

    It's hard to believe because it would mean the wrong firmware was installed (which makes no sense in itself) but with that firmware the device should have been a brick. The soc is completely different. It would be somewhat like trying to use Nvidia drivers on an AMD GPU... It just wouldn't work.

    I dunno... I don't disbelieve you but I don't believe you either. It's just so far fetched for many reasons
    1
    For me it does not necessarily have to be a flip phone. Just f*** compact, but without hardware restriction. That's why I loved the Xperia Z3 Compact. Unfortunately there are no reasonable compact phones on the market right now in my opinion. The Z Flip 3 was the best compromise for me at the moment. Would love to see a Xiaomi compact phone 😂 but that's off topic.