Develop Bugs

My complete bootloader unlock and root guide.

So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted.
I want to thank everyone who made different threads about rooting and installing Magisk on this phone, i have read so many guides now so i cant remember their names!.
BUT THANK YOU!.
Let's get to it
Here is what I did for to unlock the bootloader, install magisk and root my Huawei P20 Lite ANE-LX1
First you need to install HiSuite: https://consumer.huawei.com/minisite/HiSuite_en/
and then install ADB and Fastboot drivers: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
(extract the platform-tools folder to the root of your C: drive)
Plug in your phone and let it install drivers.
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
I used "Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.146(C432) Firmware Android 8.0.0 EMUI 8.0.0 05014YXX androidhost.ru.zip" (https://androidhost.ru/6ti)
When finished downloading, open the zip file, open software and copy the folder "Dload" to the root of your EXTERNAL SD CARD, not internal storage!.
Now take your phone and "dial" *#*#2846579#*#* go to Software Upgrade -> SdCard Upgrade and click OK.
Your phone should now begin installing the old firmware, when the phone first boots up, dont set it up, turn it off and hold Volume up + Power and select Wipe Data/Factory Reset, Wipe Cache, and then reboot.
With the phone booted, enable USB Debugging (Settings > System > About Phone > version number > Tap it 7 times to become developer, AND click OEM-Unlock, then go to Settings > System > Developer Options > USB Debugging).
Now we need to buy 4 credits from DC-Unlocker (4 Euro) ( https://www.dc-unlocker.com/buy ) when you have 4 credits on your account, go and download https://hcu-client.com/download/hcu-client-v1-0-0-0287/ Password: hcu
extract the contents of the zip to a folder called HCU in the root of your C: drive
Open up HCU.exe, type in your username and password (check your mail, the info will be there).
Grab your phone and dial *#*#2846579#*#*, go to Background Settings -> USB Port Settings -> Manufacture Mode and press close.
Plug in your phone and let it install drivers.
Open up HCU client, select Unlock, and then Read Bootloader Code.
when you have the code, save it!
Turn off your phone
Hold volume down and power, now we are in fastboot mode.
Open CMD and write:
CD C:\platform-tools
fastboot oem unlock YOUR UNLOCK KEY HERE
Accept the stuff and unlock your bootloader, your phone will be factory reset, and all your data lost if you dont have a backup.
Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)
Now re-enable USB Debugging option in Developer Options.
install Magisk Manager (https://github.com/topjohnwu/Magisk/releases/download/v18.0/Magisk-v18.0.zip)
Download patched_ramdisk.img (https://mega.nz/#!GWp1ia6R!xUcg_T_17v1ktlFQPq-Ujo4DRKfAg8E4-_k2J2zLO60)
and place it in the root of your phones internal storage
Open up Magisk Manager, press install -> install -> Patch Boot Image File -> find the patched_ramdisk.img and click OK.
Now open CMD and write:
CD C:\platform-tools>
adb pull /storage/emulated/0/download/patched_boot.img
Now you should have the patched_boot.img in your platform tools folder.
Turn off your phone, hold volume down and power to get to fastboot mode.
in CMD write:
CD C:\platform-tools>
fastboot flash ramdisk patched_boot.img
reboot your phone and check if magisk was installed correctly and check if you have root.
Hope this works for you!

Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time

Thank you for this, but I have a question about this part:
Then you need to downgrade your firmware to 146 using Dload method, as DCU Client can't read the bootloader unlock code on newer firmwares.
Click to expand...
Click to collapse
Mine is ANE-LX3, what would be the equivalent to 146 so that DC-unlocker can read it?

Yes, you just need to find a firmware for LX3, i dont think flashing a 64gb firmware on a 32gb device is smart.

dcduartee said:
Great guide. Just a tip instead of using cd C:\platform-tools you can shift+right click on the adb folder and click "open powershell here". Saves some time
Click to expand...
Click to collapse
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.

Where could i find the correct firmware of ANE-LX1

Just use the address bar
brugernavn said:
I have tried that and PowerShell doesnt Work on my pc(i have replaced shift click shortcut so its CMD indtraf) and i wanted a noob proof way to make this work
And thanks.
Click to expand...
Click to collapse
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/

LLoTE said:
Where could i find the correct firmware of ANE-LX1
Click to expand...
Click to collapse
Use the link in my guide.
lalovzg said:
Maybe you already know but I learned that you can just clic the address bar in a Windo(w)s system and write 'cmd' which is exactly the same as 'open a command prompt that starts in this very specific folder'.
E.g. in attachments.
Now I just want to know what firmware to downgrade to :/
Click to expand...
Click to collapse
Sweet thanks!.
Try and use this firmware:.
https://androidhost.ru/9V2

Using that as a reference I found one for my region I think (C69) that says:
Integrates Google security patches released in Apr 2018 for improved system security.
Click to expand...
Click to collapse
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?

lalovzg said:
Using that as a reference I found one for my region I think (C69) that says:
Is this April FullOTA a safe security patch to work with DC-u?
ANE-LX3C69CUSTC69
An another one big question: I am in the believe that my P20 lite is Single-SIM. Does it matter if that FullOTA (or any ROM/Update.app/etc) says DUAL-SIM? Should I look for the oldest Single-SIM??? or a Dual-SIM file would work just fine?
Click to expand...
Click to collapse
If its single sim, you need a single sim firmware and just use a firmware under 150, you should be okay

Would someone like to pay for me cuz I don't got a way to pay i don't have any credit cards..i know this is stupid but im just a teenager and my parents wouldn't pay for it so here i am lol

@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like This post forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad

HEKER510 said:
@brugernavn
Bro your instructions are super perfect tuttorial very very BIG thankx
would know exactly the firmware that would go without a bootloader unlock hunger everywhere this Huawei P20 Lite firmware ANE-L21 Anne-L21 8.0.0.166 (C432)
The only thing is that which one is right where the dam to sdcard firmware into the dload folder and installs without problems
because of what I was looking for and so I made a mistake to link to the Huawei P20 Lite ANE-L21 Anne-L21 8.0.0.166 (C432) in format like aky maš na forum
what i found for dual sim so all su with unlocked bootloader hurts me
PLEASE REPLY will be glad
Click to expand...
Click to collapse
Im sorry, i dont understand what you are writing

brugernavn said:
Im sorry, i dont understand what you are writing
Click to expand...
Click to collapse
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?

HEKER510 said:
i flashnig for sdcard firmware 146 for you link
i have must firmware 166 for sdcard
you helping my for firmware 166 for huawei p20 lite dual firmware 166(c432) flashing install sdcard for servis menu upgrade
identic 146 for 166 firmware
you understand my brother ?
Click to expand...
Click to collapse
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu

brugernavn said:
You first flash 146 firmware with Service menu.
Then unlock bootloader
Then update via the settings menu
Click to expand...
Click to collapse
Bro 166 firmware for servis menu yes ? thankx you very much

thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again

Hey, to root my p20, flashing magisk via recovery, don't need ramimage, all works fine

how to do it
how to flashing magisk via recovery? (whit TWRP or not??) you can explain the passage?

cirovi said:
thank you very much for your guide, brugernavn.:good:
I arrived without problems at the point: "Turn the phone off and on again, set it up, and go to settings -> System -> System update, and update, mine was ANE-LX1 8.0.0.162(C432)"
but the phone can not find updates ... (i before was in 150) but this isn't a problem.
My doubt is on how to install Magisk Manager (https://github.com/topjohnwu/Magisk/...gisk-v18.0.zip) .... with TWRP ?
Thank you again
Click to expand...
Click to collapse
what software are you running now?

root for SM-R820 (help needed)

Good day everyone.
Can anybody gove me a good step-by-step-guide and the files to root my GWA2. I'm on Softwareversion R820XXU1CTJ5. After some reading here in the forum i'm unable to find a proper firmware to root the device.
Sincereley CrazyMA90

SM-R820 CTI4 Root is here:
https://forum.xda-developers.com/showpost.php?p=83640791&postcount=937
netOdin is here:
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
OXA CSC for SM-R820 CTI4 is here:
https://www.file-upload.net/download-14355243/CSC_OXA_R820OXA1CTI4_usr.tar.md5.7z.html
It is possible to reach CTJ5 via FOTA update from rooted CTI4... with ADDITIONAL Steps with SDB Tool...
Because restore of Original RAMDISK required to make FOTA Delta valid...
Later more...
SDB Tool is here:
https://forum.xda-developers.com/showpost.php?p=74585286&postcount=330
Best Regards

Okay i tried it like you said but now my watch only shows that the firmware update encountered an issue. I think i made a mistake on that sercity-disable-step. this could be the source of my issue or it is related to the newer firmware version that was installed.
After flashing the firmware from this thread:
Firmware r820- r830 (can't posting links sorry)
my watch now boots normaly. So far so good. Now its on a lower Tizen version but for now its okay. I'm going to wait for your reply now^^

Sorry, less time...
Did the way last day... because still no CTJ5 leak...
The short info...
A
Root CTI4 allready on SM-R820... this is mandatory to have later Root also in CTJ5...
B
Code:
sdb root on
sdb push ramdisk.img /tmp
sdb shell dd if=/tmp/ramdisk.img of=/dev/mmcblk0p8
ramdisk.img is from CTI4 ... to have valid file for FOTA update process...
Looks like this:
D:\SDB\SDB260>sdb root on
Switched to 'root' account mode
D:\SDB\SDB260>sdb push ramdisk.img /tmp
pushed ramdisk.img 100% 7MB
1 file(s) pushed. 0 file(s) skipped.
ramdisk.img 476 KB/s (7340304 bytes in 15.050s)
D:\SDB\SDB260>sdb shell dd if=/tmp/ramdisk.img of=/dev/mmcblk0p8
14336+1 records in
14336+1 records out
7340304 bytes (7.3 MB) copied, 1.42445 s, 5.2 MB/s
Click to expand...
Click to collapse
C
Now you can go to Galaxy Wearable App on Phone... search for Update CTJ5 and start...
D
After FOTA Update you see Kernel Panic Screen... because ramdisk now allow su Binary...
So netOdin Action to flash ramdisk from ROOT package again... done.
ramdisk_only_smR500_ASL2_FT40.tar
Click to expand...
Click to collapse
IMHO sounds harder as it really is.
Best Regards

@adfree I switched on debugging, switched my watch to reboot mode. Chose the wireless AP option. Connected my laptop to my Watch WiFi. Net-Odin detected my watch. Uploaded the AP in the AP tab and started the process. After this step, when my watch restarts, it's as if everything got factory reset. Then I have to connect to my phone from beginning to at least get into the watch face. I guess this might not be common or is it? Cause after this step, I connected my watch to my home WiFi, restarted, then turned on sdb command prompt. I typed sdb connect (watch WiFi IP address). But when i wrote sdb root on, it's saying permission denied.
GWA3 45mm BLT SMR840 model

I need help to delete or bypass Samsung account (reactivation locK) Galaxy Watch Active 2 SM-R820
flash combination but there is still an account

How to go back to official firmware

Hii. I am ankit.
I have downloaded custom rom and twrp recovery.
Now i want to get back to stock rom and stock recovery in my phone.
And also wants to use official updates of phone's software.
Can anyone help?

1.Download the odin
2.Download rome orginal a50

Windows
The easiest way for Windows is to just use Odin. This is a nice tutorial on how to restore to stock with it.
Linux
If you use Linux and don't want to bother with trying to use something like Wine to run Odin, the following steps are for you.
Get the firmware
You can use something like updato.com, but from my experience it failed 2 separate 4 hour downloads, and the download speeds are abysmal, so I can't recommend.
I use samloader, the only caveat with it is that you can only get the latest firmware for a region (because Samsung only saves the latest one), you'll need to use something else for older versions.
1.1 Install samloader, following their instructions
1.2 Get your Model number, it should look something similar to GT-I8190N, if you don't know it, here is a link on how to find it (it's made for stock firmware, but it should still point you in the right direction)
1.3 Get your region (you might be able to install from any region, but I think it's safest if it's the region from which the phone is bought), here you can find a good list of available regions
1.4 Check the latest firmware version available. Use the following command, and replace the model and region with your values
Code:
$ samloader -m GT-I8190N -r BTU checkupdate
The output should be something like this:
Code:
I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2
1.5 Download the firmware, whose name you got from step 1.4. Use the following command, again replacing the values with your own
Code:
$ samloader -m GT-I8190N -r BTU download -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -O .
After it has finished downloading, the output should look something like this:
Code:
downloading GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2
[################################] 10570/10570 - 00:02:02
1.6 Final step is to decrypt the downloaded firmware. To do so, use the following command, while again, changing your values. Important: after the -V, you put in a number, that number is dependent on the file you downloaded from step 1.5. If the file ends with .enc4, replace the number 2 with the number 4, if it ends with .enc2, leave it at 2.
Code:
$ samloader -m GT-I8190N -r BTU decrypt -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -V 2 -i GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2 -o GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Unzip the firmware archive. You should do so in a new folder, as a lot of files will be extracted.
Code:
unzip GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Extract the files from the files, you got in step 2 (yeah, there are archived files inside an archive). The following command does just that, you can simply copy-paste it
Code:
for file in *.tar.md5; do tar -xvf $file done
Finally, flash all of the resulting .img and .bin files. On how to find which file goes where, use these instructions. If you use Heimdall for flashing, in that link you can also instructions for it.

Syndamia said:
Windows
The easiest way for Windows is to just use Odin. This is a nice tutorial on how to restore to stock with it.
Linux
If you use Linux and don't want to bother with trying to use something like Wine to run Odin, the following steps are for you.
Get the firmware
You can use something like updato.com, but from my experience it failed 2 separate 4 hour downloads, and the download speeds are abysmal, so I can't recommend.
I use samloader, the only caveat with it is that you can only get the latest firmware for a region (because Samsung only saves the latest one), you'll need to use something else for older versions.
1.1 Install samloader, following their instructions
1.2 Get your Model number, it should look something similar to GT-I8190N, if you don't know it, here is a link on how to find it (it's made for stock firmware, but it should still point you in the right direction)
1.3 Get your region (you might be able to install from any region, but I think it's safest if it's the region from which the phone is bought), here you can find a good list of available regions
1.4 Check the latest firmware version available. Use the following command, and replace the model and region with your values
Code:
$ samloader -m GT-I8190N -r BTU checkupdate
The output should be something like this:
Code:
I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2
1.5 Download the firmware, whose name you got from step 1.4. Use the following command, again replacing the values with your own
Code:
$ samloader -m GT-I8190N -r BTU download -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -O .
After it has finished downloading, the output should look something like this:
Code:
downloading GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2
[################################] 10570/10570 - 00:02:02
1.6 Final step is to decrypt the downloaded firmware. To do so, use the following command, while again, changing your values. Important: after the -V, you put in a number, that number is dependent on the file you downloaded from step 1.5. If the file ends with .enc4, replace the number 2 with the number 4, if it ends with .enc2, leave it at 2.
Code:
$ samloader -m GT-I8190N -r BTU decrypt -v I8190NXXAMJ2/I8190NBTUAMJ1/I8190NXXAMJ2/I8190NXXAMJ2 -V 2 -i GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip.enc2 -o GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Unzip the firmware archive. You should do so in a new folder, as a lot of files will be extracted.
Code:
unzip GT-I8190N_BTU_1_20131118100230_9ae3yzkqmu_fac.zip
Extract the files from the files, you got in step 2 (yeah, there are archived files inside an archive). The following command does just that, you can simply copy-paste it
Code:
for file in *.tar.md5; do tar -xvf $file done
Finally, flash all of the resulting .img and .bin files. On how to find which file goes where, use these instructions. If you use Heimdall for flashing, in that link you can also instructions for it.
Click to expand...
Click to collapse
Sorry sir but I don't know how to use linux.
Could you tell me easy way.

_Ankit_Chahar said:
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
Click to expand...
Click to collapse
Do you have a Windows PC if so download latest Odin an latest firmware file for your phone also download Samsung USB Drives install USB Drives on you PC extract Odin an extract file's from firmware zip place file's in Odin folder start Odin click on where it says AP in Odin the file will pop up click on AP file an repeat for BL ,CP, an CSC files an click on start . Should be all good .

_Ankit_Chahar said:
Sorry sir but I don't know how to use linux.
Could you tell me easy way.
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/guide-how-to-downgrade-to-android-9.4096323/ Same procedure, just use newest Android version.

Watch this video How to Flash Samsung Galaxy ROM ( Firmware ) with ODIN

Hey there. I'm also having kinda same problem. I recently upgraded my Galaxy A50 to latest January 2021 updates but after that my touch is not working. I tried to install old firmware : 'A505FDDU5BTF1 INS' which helps me to fix the problem in past but now I can't install it. I tried it with odin many times but it keeps saying "SW REV. CHECK FAIL (BOOTLOADER) DEVICE 6, BINARY 5" something like that. Can anyone help me out here???
Details of my Galaxy A50 :
Model number : SM-A505F/DS
Serial number RZ8M51R73AE
One UI version 2.5
Android version 10
Baseband version A505FXXS6BUA6
AP : A505FDDS6BUA6
CP : A505FXXS6BUA6
CSC : A505FOLM6BUA6
Model : SM-A505F/DS
Please inform me if anyone can on [email protected]
Any help will be really appreciated. Thank you in advance.

SudanTmz said:
Hey there. I'm also having kinda same problem. I recently upgraded my Galaxy A50 to latest January 2021 updates but after that my touch is not working. I tried to install old firmware : 'A505FDDU5BTF1 INS' which helps me to fix the problem in past but now I can't install it. I tried it with odin many times but it keeps saying "SW REV. CHECK FAIL (BOOTLOADER) DEVICE 6, BINARY 5" something like that. Can anyone help me out here???
Details of my Galaxy A50 :
Model number : SM-A505F/DS
Serial number RZ8M51R73AE
One UI version 2.5
Android version 10
Baseband version A505FXXS6BUA6
AP : A505FDDS6BUA6
CP : A505FXXS6BUA6
CSC : A505FOLM6BUA6
Model : SM-A505F/DS
Please inform me if anyone can on [email protected]
Any help will be really appreciated. Thank you in advance.
Click to expand...
Click to collapse
Make u sure to use Binary 6 rom, U cannot flash binary 5 rom... thats why it didnt work. u wanted to use binary 5 rom

peter couniaz said:
Do you have a Windows PC if so download latest Odin an latest firmware file for your phone also download Samsung USB Drives install USB Drives on you PC extract Odin an extract file's from firmware zip place file's in Odin folder start Odin click on where it says AP in Odin the file will pop up click on AP file an repeat for BL ,CP, an CSC files an click on start . Should be all good .
Click to expand...
Click to collapse
After that could I use knox services like secure folder etc.

_Ankit_Chahar said:
After that could I use knox services like secure folder etc.
Click to expand...
Click to collapse
Yes you should be able to use secure folder after going back to official firmware .

kisvagen said:
Make u sure to use Binary 6 rom, U cannot flash binary 5 rom... thats why it didnt work. u wanted to use binary 5 rom
Click to expand...
Click to collapse
And if for example, I want to go back to Android 9, which is binary 5 and my A50 is Android 11, binary 7, is there any way I can ignore the binary or something?

How to Change CSC of a non-rooted Note10+? Is there any working way?

I've recently bought an SM-N975F Note 10+, which has an OXM multi-CSC ROM and a current CSC set as: SER/SER, SER/XXV. The security patch level is August 2021. The device is not rooted, Knox is 0x0, which I'd like it to stay for a while.
I'm looking for a way to change the current CSC to some value supporting native call recording, like XXV.
So far, I've tried:
* Dialer codes (both *#272*IMEI# and *#*#28262726#*#*, or whatever they are) – no luck opening the preconfig menu;
* Opening the preconfig menu with some other way, like launching it via adb using am start-activity – it seems like the device is missing the com.android.Preconfig package altogether;
* Changing CSC with Samkey: I disabled lock screen security and ejected the SIM card as per the instruction, and despite the tool having said that the operation was successful, the phone rebooted with the same SER/SER, SER/XXV CSC.
Is it possible that flashing a non-multi-CSC firmware (like the XXV one) might help here? Is it possible that I did something wrong with Samkey?
Do you know about any other working way to change CSC in modern Note10+ devices? I consider paid solutions as well (like Samkey I mentioned above).
Thanks.

Whats your android version and binary version ?

The Android version is 11, 7FUH3 OneUI 3.1 firmware.

h0tkey said:
* Dialer codes (both *#272*IMEI# and *#*#28262726#*#*, or whatever they are) – no luck opening the preconfig menu;
Click to expand...
Click to collapse
as I remember this only works with the Google dialer - make a search for this - and you can choose a CSC from there;
when you do this, be ready to loose all data, the phone will factory reset
you can also choose a stock firmware from samfirm.com and flash it with Odin - you need to choose CSC to change it and not HOME_CSC
CSC or HOME CSC? Which CSC File to Flash in Samsung Odin?
Should you flash CSC or HOME CSC in Odin? Using our list of CSC codes, you can easily change it on your Samsung Galaxy phone or tablet.
technastic.com

How To Guide Installing OneUI 4 Beta / Android 12 on US Galaxy Z Fold 3 F926U/1

Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"

Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?

shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again

Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.

Haven't logged in to XDA in years. Just wanted to say THANK YOU.

mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.

Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!

AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.

Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.

Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload

erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?

I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop

zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1

Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.

ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...

I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?

I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?