Database Info

[GUIDE] HSTool for upgrading firmware of BL locked Huawei View 20 [LATEST FW: 248]

Ty to the folks over at the Honor Mate 20 Pro forum especially @mikeos we are now able to update our Honor View 20 to all available firmwares up to 9.1.0.248
Warning: Do not use this method to upgrade to Android 10, it will brick the device and there are currently no ways to unbrick!
Disclaimer:
Tested with PCT-L29C432, this method can cause SafetyNet check to fail, i.e. disable Google Pay, Pokemon Go if firmware higher than intended for a given region is flashed ***
This means if IMEI is not approved for installation in a certain region SafetyNet might fail, so make sure to enable "Show Only FUll-OTA and Show packages for current region" in FF settings to reduce the risk of flashing a firmware for a other region.
Would people that do not have PCT-L29C432 model please leave there model here so i can add them, many thanks!
Note that if your BL is unlocked, this method will lock it!
People without USB adapter can also use this method to upgrade to approved region firmware updates but make sure only to use Full OTA packages!
Cust partition (region) will stay original based on device oeminfo. C432 wil stay C432 after upgrade and so forth.
Usage:
Make sure to uninstall HiSuite first if installed.
1. Install HiSuite 301 (Do not run after install)
2. Install HiSuite patch
3. Replace XML file in (C:\Users\%UserName%\AppData\Local\HiSuite\userdata\UpdateDogDev)
4. Unzip HStool to c:\
4. Copy rom "update_full_base" to c:\
5. Disable Internet
6. Copy C:\Windows\System32\drivers\etc\host to desktop and remove or comment out 188.225.84.142 query.hicloud.com example https://pastebin.com/haquj6Tr
7. Copy host file back to C:\Windows\System32\drivers\etc\
8. Turn off the phone
9. Hold the volume down button
10. Plug-in the USB cable while still holding the volume down button until you see fastboot
Usage: run HSTool on c:\ and follow prompts.
Requirements
- HSTool
- HiSuite-9.0.2.301
- HiSuitePatchInstaller
- Modified XML to recover Honor View 20 using HiSuite
- Downloaded full firmware using huawei firmware finder (update_full_base) or Direct Download links
Dowloads:
- HSTool:
https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
- HiSuite
https://drive.google.com/open?id=1dgiAJG3kfqscbiutjZ28v6Do-i9lZJz0
- HiSuite XML
https://drive.google.com/open?id=1pajhXUe3th-lPRfBQex2UiyntoxUgL77
- HiSuite Patcher
https://drive.google.com/open?id=1GYpONCf8ci4UwIyBo0Z_1UsN3RBs5gvf
SafetyNet Test List:
PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.229 = CTS Pass
PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.235 = CTS Pass
PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.238 = CTS Pass

Hey, does it wipe data?

mchtt said:
Hey, does it wipe data?
Click to expand...
Click to collapse
No it does not wipe data but as always it's a good idea to back it up first

- Downloaded full firmware using huawei firmware finder (update_full_base)
Click to expand...
Click to collapse
Hi TerrorToetje
What Firmware have you Downloaded with Firmware Finder? I use http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full/changelog_base.xml
http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full//update_full_base.zip
But after flashing and booting in Recovery it stops at 5% with an error and restarts the Phone

Is app launch speed difference relevant with the improvement they made?

TerrorToetje said:
Ty to the folks over at the Honor Mate 20 Pro forum especially @mikeos we are now able to update our Honor View 20 to all available firmwares up to 9.1.0.229
Disclaimer:
Tested with PCT-L29C432, this method can cause SafetyNet check to fail, i.e. disable Google Pay, Pokemon Go if firmware higher than intended for a given region is flashed ***
This means if IMEI is not approved in certain region SafetyNet might fail. My IMEI was not approved but I still pass Safetynet on latest firmware.
People without USB adapter can also use this method to upgrade to approved region firmware updates but make sure only to use Full OTA packages!
Cust partition (region) will stay original based on device oeminfo. C432 wil stay C432 after upgrade and so forth.
Usage:
Make sure to uninstall HiSuite first if installed.
1. Install HiSuite 301 (Do not run after install)
2. Install HiSuite patch
3. Replace XML file in (C:\Users\%UserName%\AppData\Local\HiSuite\userdata\UpdateDogDev)
4. Unzip HStool to c:\
4. Copy rom "update_full_base" to c:\
5. Disable Internet
6. Copy C:\Windows\System32\drivers\etc\host to desktop and remove or comment out 188.225.84.142 query.hicloud.com example https://pastebin.com/haquj6Tr
7. Copy host file back to C:\Windows\System32\drivers\etc\
8. Turn off the phone
9. Hold the volume down button
10. Plug-in the USB cable while still holding the volume down button until you see fastboot
Usage: run HSTool on c:\ and follow prompts.
Requirements
- HSTool
- HiSuite-9.0.2.301
- HiSuitePatchInstaller
- Modified XML to recover Honor View 20 using HiSuite
- Downloaded full firmware using huawei firmware finder (update_full_base)
Dowloads:
- HSTool:
https://forum.xda-developers.com/mate-20-pro/how-to/manual-upgrading-mate-20-pro-bl-locked-t3905924
- HiSuite
https://drive.google.com/open?id=1dgiAJG3kfqscbiutjZ28v6Do-i9lZJz0
- HiSuite XML
https://drive.google.com/open?id=1pajhXUe3th-lPRfBQex2UiyntoxUgL77
- HiSuite Patcher
https://drive.google.com/open?id=1GYpONCf8ci4UwIyBo0Z_1UsN3RBs5gvf
Click to expand...
Click to collapse
finally the Honor view 20 works as fast as his big brother the Mate 20 PRO, it is a happiness

Kingkaktus said:
Hi TerrorToetje
What Firmware have you Downloaded with Firmware Finder? I use http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full/changelog_base.xml
http://update.dbankcdn.com/TDS/data/files/p3/s15/G4552/g1755/v281097/f1/full//update_full_base.zip
But after flashing and booting in Recovery it stops at 5% with an error and restarts the Phone
Click to expand...
Click to collapse
PCT-LGRP2-OVS 9.1.0.229
But make sure to download it using FF, and remember only FullOTA-MF packages.

mchtt said:
Is app launch speed difference relevant with the improvement they made?
Click to expand...
Click to collapse
The overall speed is better but also remember we got this:
https://www.xda-developers.com/huawei-honor-gpu-turbo-3/

TerrorToetje said:
This method can cause SafetyNet check to fail, i.e. disable Google Pay, Pokemon Go if firmware higher than intended for a given region is flashed
Click to expand...
Click to collapse
Is the SafetyNet check based solely on IMEI? I noticed you mentioned that your IMEI was not approved but SafetyNet was still fine after the update but I'm not sure about risking my own device.
My device is also a PCT-L29 C432, checking firmware access on FF for PCT-LGRP2-OVS 9.1.0.229 FULLOTA_MF says that the firmware is "not approved", so presumably I'm in the same situation.

NekoMichi said:
Is the SafetyNet check based solely on IMEI? I noticed you mentioned that your IMEI was not approved but SafetyNet was still fine after the update but I'm not sure about risking my own device.
My device is also a PCT-L29 C432, checking firmware access on FF for PCT-LGRP2-OVS 9.1.0.229 FULLOTA_MF says that the firmware is "not approved", so presumably I'm in the same situation.
Click to expand...
Click to collapse
No it's not really the IMEI but the device fingerprint, the device firmware needs to be Certified in order to pass. Sometimes certain firmwares are builded for internal testing with other fingerprints (Not approved by google), if you have the same device and and planning to go to 9.1.0.229 I cannot think of any reason why you would not pass saftynet. PCT-L29 C432 + PCT-LGRP2-OVS 9.1.0.229 FULLOTA_MF firmware is "not approved" for installation but you will pass saftynet. However if we would force flash a firmware from a other region well that might change things.
There is a setting in FF to only show packages for the current region, those should be fine.
Best Regards,

How will then I update from this firmware I think it's will not be working

jirka607 said:
How will then I update from this firmware I think it's will not be working
Click to expand...
Click to collapse
Please explain what does not work?

I have just started the update using this method, I will let you know later.
FYI last time I did something like this I bricked my Mate 9 haha so I am so nervous right now.

dlhak said:
I have just started the update using this method, I will let you know later.
FYI last time I did something like this I bricked my Mate 9 haha so I am so nervous right now.
Click to expand...
Click to collapse
Well you can't brick it if you followed all steps, if anything comes up i'm here

dlhak said:
I have just started the update using this method, I will let you know later.
FYI last time I did something like this I bricked my Mate 9 haha so I am so nervous right now.
Click to expand...
Click to collapse
I can help too

TerrorToetje said:
Well you can't brick it if you followed all steps, if anything comes up i'm here
Click to expand...
Click to collapse
I am having failed to decmpress the file error
after it finished downloading the recovery with HiSuite.

TerrorToetje said:
Please explain what does not work?
Click to expand...
Click to collapse
No what I'm asking is if I can then update to newer firmware by ota? Or how it will be done

Nevermind, I did two things and I don't know which one fixed my issue, I disabled my Antivirus and moved my "Documents" folder into its original location "C:"
Update is done.
I am now on Magic 2.1

dlhak said:
I am having failed to decmpress the file error
after it finished downloading the recovery with HiSuite.
Click to expand...
Click to collapse
Spaces in path maybe?

jirka607 said:
No what I'm asking is if I can then update to newer firmware by ota? Or how it will be done
Click to expand...
Click to collapse
Ota will work once the newer firmware gets approved for your region, otherwise using this method is an alternative method.

SM-A205U (MetroPCS) OEM Unlock

Hello,
Just wanted to share this with the community as I found this just yesterday. If you goto your settings and click connections then "More connection settings" towards the bottom there is an option for "Network Unlock". I did this like I said yesterday and it permanent unlocked the phone. I don't have any other SIM cards to try and see if it will go on a different network but just wanted to point this out to the community!
~DJ

djdeath15 said:
Hello,
Just wanted to share this with the community as I found this just yesterday. If you goto your settings and click connections then "More connection settings" towards the bottom there is an option for "Network Unlock". I did this like I said yesterday and it permanent unlocked the phone. I don't have any other SIM cards to try and see if it will go on a different network but just wanted to point this out to the community!
~DJ
Click to expand...
Click to collapse
That's not an OEM unlock, you've only unlocked the SIM card lock.

Into the sun you go

I wondered if this was either effecting, &or blocking or stopping oem unlock from showing or being visible? Just a thought.

ATGkompressor said:
I wondered if this was either effecting, &or blocking or stopping oem unlock from showing or being visible? Just a thought.
Click to expand...
Click to collapse
It's our specific model.
There are no 205u units in public domain that exist with an oem toggle.
It's disabled by default in the 205u source.

The only way this might be possible is with combination firmware but in all my searching so far i have yet to find bootloader 5 combination firmware ...
If anyone can find me a bootloader 5 android 10 combination firmware for the 205U varient i would be willing to see if there would be a way to get this rooted and bootloader unlocked

https://www.full-repair-firmware.com/2019/08/Combination-a205u.html

physwizz said:
https://www.full-repair-firmware.com/2019/08/Combination-a205u.html
Click to expand...
Click to collapse
Has everything except binary 5, probably gonna be waiting on that for a while

ninjasinabag said:
Has everything except binary 5, probably gonna be waiting on that for a while
Click to expand...
Click to collapse
Bin 4 won't work?

physwizz said:
Bin 4 won't work?
Click to expand...
Click to collapse
It would help for anyone still on pie if we could flash it.
Anyone who upgraded to Q would be in the cold for now.

i cant use bin 4 on my device because i upgragded to android 10 already on it so i couldnt even test to see if it was possible thats why im looking for combo firmware bootloader 5

ninjasinabag said:
It would help for anyone still on pie if we could flash it.
Anyone who upgraded to Q would be in the cold for now.
Click to expand...
Click to collapse
Yo I got this phone and figured it's a paperweight until root aka on Android 9 installed magisk manager , zarchiver and combination file matching numbers. Here is where I'm at a lack of expertise cuz magisk won't install enough to feed it the boot.img. Please Help Anyone:silly:

ddougg said:
Yo I got this phone and figured it's a paperweight until root aka on Android 9 installed magisk manager , zarchiver and combination file matching numbers. Here is where I'm at a lack of expertise cuz magisk won't install enough to feed it the boot.img. Please Help Anyone:silly:
Click to expand...
Click to collapse
The combination file is from an older bootloader, so it retains the most recent bootloader to maintain integrity of the Qfuse.
That's kinda why we want the combination file for 10, the bootloader hasn't changed which means the file would be universal for anyone who updates.

ninjasinabag said:
The combination file is from an older bootloader, so it retains the most recent bootloader to maintain integrity of the Qfuse.
That's kinda why we want the combination file for 10, the bootloader hasn't changed which means the file would be universal for anyone who updates.
Click to expand...
Click to collapse
yo Ninja I found the latest firmware with the u5 bootloader . It won't let me upload , bummer. I'll try again tonight. help

ddougg said:
yo Ninja I found the latest firmware with the u5 bootloader . It won't let me upload , bummer. I'll try again tonight. help
Click to expand...
Click to collapse
Do you have a link or anything to the source? I'll check it out and test when home

Ninja Do you have an email I could send the files to? Mega is being itchy bout an account from 3years ago and drive wants to copy my entire laptop,

I have the 205U as well I never could get antything to work I tried Odin and Magisk did not work I do have Android 10 as well I just look at the fix website I dont know what to do there or it would work with my latest vversion of my phone willl shoud I try to use it and would it be done it hasd 5 fixes that need to be installed ?

U is Unrootable

techmanc said:
I have the 205U as well I never could get antything to work I tried Odin and Magisk did not work I do have Android 10 as well I just look at the fix website I dont know what to do there or it would work with my latest vversion of my phone willl shoud I try to use it and would it be done it hasd 5 fixes that need to be installed ?
Click to expand...
Click to collapse
At the moment, all U devices are unrootable.

Try this
https://forum.xda-developers.com/galaxy-a20/how-to/a205-bootloader-unlock-twrp-root-t4189197

Question Oneplus 9 LE2117 root process(T-Mobile)

With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?

Follow the steps to install magisk.

Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Thanks for the response. I believe that's the last step I have to complete to be done, but that is where I seem to be getting lost. I can't find a boot image for the specific model and software numbers I have. From the threads I have read I think I could use the boot image for software version 11.2.2.2 but I am uncertain.

I went ahead and used the boot.img for 11.2.2.2 and it looks like it worked.

captain_howdy said:
With the differences between the EU, Global variants, and software versions listed in the threads I've gone through, I am having trouble finding a guide that I am sure would be applicable to root my Oneplus 9 LE2117 11.2.5.5-LE54CB. (T-Mobile)(US)
My device is SIM unlocked, and the bootloader is unlocked, but I am unsure of the best method to root.
Could anyone point me in the right direction?
Click to expand...
Click to collapse
You need 11.2.5.5 boot.img from any region. Then follow the instructions install magisk.

just use the AA image for tmobile. patch the image with magisk the file will go to your download file then fastboot boot the img file from the one get from magisk after patching and you will gain temp root. direct install with magisk and reboot. if you get into a bootloop. reset devices from recovery and you will still retain root after the reset. i have installed empty slot ota and direct install. bootlooped on ota empty slot but reset from recover fixed problem instantly and retained root. direct install no bootloop retained root.

Does anyone care to comment with insights or experiences in regards
to Rooting with Magisk which will allow for the installation on a Custom ROM at a later time -
that is, when a stable Lineage OS for example is available for the OP-9 (t-Mobile) ?
Thank You in Advance !

I doubt it but anything is possible. with the process to convert to different variants being fairly simple and accessible there will be very little focus on that particular software. It is compatible with gloabal pathched boot image to gain root and from there your pretty much able to customize to do what ever your heart desires.

Superguy said:
Follow the steps to install magisk.
Click to expand...
Click to collapse
Can you direct me where to find that ?
I'm having difficulties getting anything to work...
If you are on the latest Tmobile update,you can use 11.2.8.8.img from either AA,BA or DA. the boot.img are all the same.
Click to expand...
Click to collapse
I'm on 11.2.6.6.LE54CB - and I thought the end two letters were Important ?

avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
See, the thing is, I was so accustomed to having an Un-Locked device from t-Mo, I didn't realize that the Awesome Dude who un-locks the SIM, does not actually un-lock the Phone. So Much Bull**** from t-Mo...
ANy-Hoo... I just applied thru the OP site to get my 9 completely un-locked.
Thank You for Your Time and Response!

avid_droid said:
Negative. Letters don't matter. The latest update from T-Mobile normally correlates with the latest of AA,BA,DA. If you are on the 11.2.6.6 it's 11.2.8.8. any of the boot.img will work.
Click to expand...
Click to collapse
Quick little bump, but I'm on 11.2.7.7.LE54CB. Has anything still changed or would I still be good to go to use the 11.2.8.8. boot.img to root or the latest 11.2.9.9.LE25AA from OnePlus's site directly?

I have managed to install the Eurepean 11.2.9.9.LE15BA for the 9 PRO le2117
I have the tmobile 9 5g version not the pro. camera doesnt pull up but otherwise runs fine

Need help here! I forgot to backup my oneplus 9 pro LE2127 when I tried to root my phone using TWRP，and I installed TWRP in my phone's boot partition which wiped out all data in that partition. I used TWRP side loaded Global ROM to recover my phone but the phone doesn't have any signal with sim card in. Used MSM tool backe to T-Mobile 11.2.5.5 and still same problem, sim card can be read but no signal. Flashed T-Mobile modem but modem b failed, it says no such partition.
Bought this phone from third party. Any suggestion is appreciated.

General [HELP THREAD] Ask any questions, noob friendly.

Help thread for people that have the Samsung galaxy a12 (any model)​​Anyone can ask and help others here, but please don't be abusive towards others.​
No abuse tolerated here! That means:
NO TROLLING
NO NAME CALLING
NO RIDICULING
NO FLAMING

Is there a possible fix for the touchscreen not working after screen gets turned off?

James 144 said:
Is there a possible fix for the touchscreen not working after screen gets turned off?
Click to expand...
Click to collapse
I haven't found a way yet because of twrp problems, but you can try outjusting some kernel settings and deep sleep options with kernel managers. I recomend SmartPack, free and open source kernel manager avaible on F-droid.
SmartPack-Kernel Manager | F-Droid - Free and Open Source Android App Repository
The Ultimate Tool to Manage your Kernel!
f-droid.org

LAST_krypton said:
I haven't found a way yet because of twrp problems, but you can try outjusting some kernel settings and deep sleep options with kernel managers. I recomend SmartPack, free and open source kernel manager avaible on F-droid.
SmartPack-Kernel Manager | F-Droid - Free and Open Source Android App Repository
The Ultimate Tool to Manage your Kernel!
f-droid.org
Click to expand...
Click to collapse
Which TWRP problems do you have?

James 144 said:
Which TWRP problems do you have?
Click to expand...
Click to collapse
Crashes when trying to install aosp or gsi images, sideload not working, wipeing problems, etc. It is something in the new build, I wasn't getting does on the old build.

@James 144
Try disabeling force doze in smart pack.

And try copying these settings

LAST_krypton said:
Crashes when trying to install aosp or gsi images, sideload not working, wipeing problems, etc. It is something in the new build, I wasn't getting does on the old build.
Click to expand...
Click to collapse
I still have the old build. You want it?

James 144 said:
I still have the old build. You want it?
Click to expand...
Click to collapse
If you could, dm me it.

LAST_krypton said:
And try copying these settings
Click to expand...
Click to collapse
Still not working :/

how to flash twrp without losing the system?

Jayke770 said:
how to flash twrp without losing the system?
Click to expand...
Click to collapse
Follow this guide and make sure to start with a clean flash first. https://forum.xda-developers.com/t/installing-twrp-and-linageos.4334465/

I just got one of these basically free from AT&T that I plan to use only for hotspotting, my main device is an S21+.
I have sm-a125u, the only firmware I can find online for ATT is sm-a125u1
What's the difference? Is it the same? Can I flash it? Or can I just flash any other carrier's firmware instead?
I'm not even going to use this thing for anything other than a hotspot, I just want to root it so I can hotspot while tricking the carrier into thinking it's just mobile data use (since I'm on Unlimited Elite plan).
I don't have the OEM Unlock option in my dev settings, tried the time/date trick. So I read somewhere that I needed to flash an Android 10 firmware to it to get that option back, then go ahead and root, then update back to A11, if that's even possible. I don't care about the firmware being a different carrier's as long as mobile data will still work on ATT's network for hotspotting.

cjxsutton said:
I just got one of these basically free from AT&T that I plan to use only for hotspotting, my main device is an S21+.
I have sm-a125u, the only firmware I can find online for ATT is sm-a125u1
What's the difference? Is it the same? Can I flash it? Or can I just flash any other carrier's firmware instead?
I'm not even going to use this thing for anything other than a hotspot, I just want to root it so I can hotspot while tricking the carrier into thinking it's just mobile data use (since I'm on Unlimited Elite plan).
I don't have the OEM Unlock option in my dev settings, tried the time/date trick. So I read somewhere that I needed to flash an Android 10 firmware to it to get that option back, then go ahead and root, then update back to A11, if that's even possible. I don't care about the firmware being a different carrier's as long as mobile data will still work on ATT's network for hotspotting.
Click to expand...
Click to collapse
Don't look at the countury reagons, If the sim card doesn't work after flashing another reagons fimware you have to SIM unlock you phone.

LAST_krypton said:
Don't look at the countury reagons, If the sim card doesn't work after flashing another reagons fimware you have to SIM unlock you phone.
Click to expand...
Click to collapse
Okay so does this mean the u1 firmware will be fine to flash on my u?

cjxsutton said:
Okay so does this mean the u1 firmware will be fine to flash on my u?
Click to expand...
Click to collapse
You still need to find fimware with the same SW REV value or you will have to go through hell to trick the Rollback prevention (RP)

I want to root my Samsung Galaxy A12 (2020) Firmware A125USQU2BUG2 with Magisk.. I don't the oem option of developer's settings.. can someone tell me how to get oem option on my phone

Smil3yWulf said:
I want to root my Samsung Galaxy A12 (2020) Firmware A125USQU2BUG2 with Magisk.. I don't the oem option of developer's settings.. can someone tell me how to get oem option on my phoneView attachment 5420929
Click to expand...
Click to collapse
try changing the date and time to something old, if that doesn't work take software updates and they should apear.
1. Disable dev options
2. go to date and time and set the date to something very old
3. Enable dev options
4. Oem unlocking should apear now and you can change date and time back to it's origin.

Smil3yWulf said:
I want to root my Samsung Galaxy A12 (2020) Firmware A125USQU2BUG2 with Magisk.. I don't the oem option of developer's settings.. can someone tell me how to get oem option on my phoneView attachment 5420929
Click to expand...
Click to collapse
Do you still have the same issue? If you do, try to possibly downgrade fimware. Flashing older fimware will work without unlocking PBL if it's smasung's official fimware. After flashing older fimware OEM unlocking should appear, and you will be able to flash unofficial fimware images after unlocking PBL.

What's the best way to make my A12 as private as possible without losing Samsung and Google features? I want to have most of the features from my Samsung Galaxy Watch4 and Google apps without any spyware.
And also, is it possible to install apps such as Netflix and ASB Mobile Banking on a rooted Samsung phone?
Thanks in advance!

Question No Wifi after rooting (EUX)

Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
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...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!

TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
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...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Good news! so you've manged to root Android 12? if so, what steps did you take?

beanbean50 said:
Good news! so you've manged to root Android 12? if so, what steps did you take?
Click to expand...
Click to collapse
Android 12? No, I'm on 11.

TarikVaineTree said:
Android 12? No, I'm on 11.
Click to expand...
Click to collapse
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore

TarikVaineTree said:
Update: Fixed (see edit 2)!
Original post:
I rooted many phones (especially Samsung ones) so I won't consider myself to be something of a "beginner".
However, I just got my Z Flip 3 today and (of course) straight went on to root it, using this thread and the guide that was linked there:
Rooting the SM-F711B (on Version F711BXXU2AUI4) working
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...
forum.xda-developers.com
However, no matter if I flash the patched (by Magisk) bootfile with Odin to AP (like in the linked guide) or to AP and BL (like the OP in the thread hinted), I can't get Wifi to work.
Of course it worked before rooting so it's not a hardware issue.
Should I flash more parts of the firmware that I downloaded with Frija?
Because according to the guide I just downloaded a stock firmware (probably the newest one) but only used the boot.img.lz4 from within the AP*.tar.md5, let Magisk on the phone patch it and then flashed the patched tar to AP (and BT) with Odin.
Everything else seems to work just fine, even the camera that is reportedly broken after rooting on some devices:
Samsung kills the cameras on the Galaxy Z Fold 3 if you unlock the bootloader
Unlocking the bootloader of the Samsung Galaxy Z Fold 3 reportedly breaks all the camera-related functionalities. Read on to know more!
www.xda-developers.com
Nevermind, the camera issue is on the Fold, not the Flip.
Edit:
It's probably because Frija got the newest FW while I have an older one and now there's a mismatch in the modem module. Oh man. Why won't the guide mention this?
I'm downloading the exact firmware that I already have on the phone right now, patch the boot from it again and repeat the process to hopefully end up fixing it this way. Wish me luck!
Edit 2:
Just did that and I have Wifi now. So everything's fine!
Click to expand...
Click to collapse
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.

VerdandiAmine said:
Hai. I got a Z Flip 3 a week ago and I am having the same issue here. Ive followed the same steps as you and ended up with wifi not working. Also my screen seems to go a weird magenta (for a few seconds) when I turn on the screen.
I am in Australia so my phone could be one of two CSC options: VAU or XSA. I tried VAU boot.img first and this caused the problem. I flashed with the XSA boot.img and the same problem.
I tried to follow this guide (https://www.droidwin.com/fix-no-wifi-calls-network-after-root-custom-rom/) but at the step 5 (boot to fastboot mode) my phone will only adb command into recovery mode when I use the command "adb reboot fastboot" and with the command "adb reboot bootloader" it will just boot loop the phone once and boot back into android.
In Odin, I tried to flash CP with the CP.tar file and this didnt change anything.
Click to expand...
Click to collapse
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.

beanbean50 said:
Oh I see 11...
good luck when trying to upgrade & rooting to 12 as something has changed and none of the guides work anymore
Click to expand...
Click to collapse
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.

TarikVaineTree said:
I don't mind staying here for a while honestly and I'm pretty sure someone will find out soon how to root Android 12 on the Flip. Thanks for the warning though.
Click to expand...
Click to collapse
I've finally managed to root Android 12 after weeks of trying.. Yippee..!

TarikVaineTree said:
You have to use the phone info app (don't remember the correct name) of the guide to get your correct CSC. That's very important. Also use the very same app to check your current (!) firmware and get exactly that one from the internet.
From there do the steps to alter the boot file according to the guide, then flash it with Odin while also at the same time clicking on BL and choose the (untouched) BL file from the complete firmware you just downloaded that fits your currently installed firmware. That's the most important step to make sure your modem stuff is working according to your current firmware.
Click to expand...
Click to collapse
Using phone info my correct CSC is VAU. The software I used to get firmware is Frija and I deployed it with Odin.
So flash the magisk patched boot.img file to AP via Odin as well as flash the firmware BL file to BL? Okay I will try this with VAU firmware and report back with what happens.