Database Users

Trying to fix Vibrant with Heimdall... could REALLY use some help, tried everything.

So I was trying to flash the ICS alpha and it cut short and went to a bootloop and would not go into recovery via button presses or adb commands.
Here's what I did...
- Put phone into download only mode and with s1_odin_20100512 pit and T959UVJFD.tar tried to flash with Odin. It repeatedly kept getting stuck on different parts of the flash, so I gave up and tried Heimdall.
- Now with Heimdall, I use the same packages and get a firmware.xml error. For the life of my I can't find a Heimdall package for Vibrant back to stock, nor do I even know how any of that works...
Would really appreciate any help I can get trying to get this phone back! It gets to download mode no problem each time... is there hope?

If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.

amburator said:
If I were you I would try to:
1. Download any CM7 ROM and put it on external SD card (I hope you have one, or perhaps you have already on your phone any ROM that can be installed via recovery, but doesn't require stock ROM)
2. flash kernel with CWM via heimdall
3. to be sure wipe system and cache
4. Install respective ROM via recovery
It helped me many times after bad flash. Perhaps after that you could odin it to stock without problems.
Click to expand...
Click to collapse
could you be super duper helpful and provide me a download for flashing kernel with CWM via heimdall? no luck so far

I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.

amburator said:
I was using this: http://goo.gl/g9rc9
from this thread: http://forum.xda-developers.com/showthread.php?t=967861&highlight=overstock
You'll have to pull out file 'zImage' from zip file.
Edit: what I meant is you'll have to load zImage to heimdall. It's in the first folder in zip file. Do not put whole folder in heimdall, only singe file: zImage.
Click to expand...
Click to collapse
I'm using Heimdall 1.3. I've extracted the zImage and packed it into a .tar and loaded it into Heimdall but I get a firmware.xml missing error... any ideas?
Thanks so much for your help.
EDIT: Nevermind, figured out how to do it. Now I'm getting a ERROR: Failed to received response. Searching google tells me I should install libusb drivers, gonna try that.

Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.

amburator said:
Have you used heimdall before? If you haven't you have to do this first:
Put your USB cable in another USB slot in your PC, after that follow instructions from heimdall's readme file:
Driver Installation Instructions:
1. Put your Samsung Galaxy S into download mode and plug it in.
2. Run zadig.exe included in the Drivers subdirectory.
3. From the menu chose Options -> List All Devices.
4. From the USB Device list chose "Samsung USB Composite DEvice".
5. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
6. Done
Now the kernel. You must not put zImage into any package. The file goes into heimdall as it is. When you open heimdall, press "browse" right to the Kernel (zImage) field and locate "zImage". After that press start.
That's the procedure that helped me to install CM7 and ICS ROMs without having to go back to stock. I hope it will help you.
One more note: when you use ODIN put the usb cable in the first USB slot, if you want to use heimdall, use the second USB slot.
Click to expand...
Click to collapse
First off, thank you so much for your help. This is my first time using Heimdall, just got done finishing the README.
Here's where I'm at... I figured out what you just said a few minutes before you sent it, haha.
Oh, important side note.. I'm on a MAC. I think I'm experiencing a driver issue right now, given this:
-------------------------------------------------------
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:6601
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
ERROR: libusb error 1032320 whilst receiving packet.
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
-------------------------------------------------------
Thoughts? I reinstalled Heimdall and went to customize and tried just the libusb package. I'm going to restart and try diff USB port now.

Fuuuuuck yeah, I got it. Thanks SO much for your help. How can I ever repay you?
EDIT: To be helpful to any googlers in the future - it was fixed by reinstalling libusb from the Heimdall 1.3 installer, restarting, and repeatedly trying alternate usb ports and putting it into download mode over and over again.

Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.

amburator said:
Sorry, I presumed you're on windows pc. I have no experience with mac.
What I know for sure, on windows heimdall won't work until you install those drivers.
Good luck anyway!
Edit: now I've seen your new post. Good news regarding drivers.
Now the kernel and ROM
Ask if you got stuck somewhere.
Click to expand...
Click to collapse
I found a package on the forms but was getting a firmware.xml error. Manually downloaded/created PIT file from phone, then extracted package, and loaded up each component (modem, param, kernel, etc) indivudally and flashed without a hitch. Huzzah!

Allright!
Congrats!

"System software not authorized by Verizon Wireless has been found on your phone"

"System software not authorized by Verizon Wireless has been found on your phone"
I have a note 3 sm-n900v Verizon on lollipop
I recently tried to install a custom recovery but got a message at boot and now I cant use my phone anymore I need help on how to find a way to restore it
message: "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."

You should be able to flash only the stock recovery.img file in Odin to restore your phone back to working condition without wiping anything or losing your rooted ROM, so long as you did not (also) flash a custom boot partition to your phone.(*1)
To do this, you:
1) download from Sammobile the (matching firmware version) Odin bundle for your phone (OB6? OF1?) (*2)
2) Extract the "recovery.img" file out of the .tar.md5 file (it is just a "tar" file - 7zip can do that)
3) Create a new Odin file with only the recovery.img file in it. It needs to be a "ustar"-format tar file, and have an appended MD5 signature. Use the commands exactly as they appear here (*3 ):
Code:
tar -H ustar -c -f MyOdinFile.tar recovery.img
md5sum MyOdinFile.tar >> MyOdinFile.tar
mv MyOdinFile.tar MyOdinFile.tar.md5
4) Flash the MyOdinFile.tar.md5 file in the Odin (3.0.9) "AP" slot
It is possible that you can simply flash the entire Odin stock firmware file without erasing anything; but you will certainly lose root doing it this way however. If you want to start all over from scratch, you can flash the entire stock Odin Firmware file without steps 2-4, and perform a factory reset - this will result in erasure of your user data.
(*1) If you also flashed a custom boot image a.k.a "kernel", you simply extend this method by including "boot.img" along with "recovery.img" from the same stock firmware.
(*2) It is vital that the firmware version that you use matches the rest of the firmware that was on the phone; hopefully you remember which (stock) firmware version you had before your mishap.
(*3) Yes these are Linux commands. If you are screwing around with Android rooting, you should know a thing or two about Linux. You can even do the above simple operations in Windows using Cygwin, as it turns out that Cygwin tar supports the "-H" option. No virtual machines are needed, although that is certainly just as good an alternative.
.

[GUIDE] Flashing unapproved firmwares (online FullOTA-MF firmwares)

WARNING: Flashing an unapproved firmware can cause unexpected issues. The OP will not be liable for any bricked device which resulted because of the use of this method. Everything is done at user's discretion. Also, ensure that you're using the correct firmware file (matches your model and is not corrupt).
Important notes for updating from Oreo -> Oreo
If you're on Oreo, don't download the recoveries mentioned in the guide below. Instead grab the one below (thanks to TeamMT for the patched recovery):
Code:
https://drive.google.com/open?id=1HmFAMYm1pU7RdKkOq_TMdthCxZJflzv9
Note that this is only 1 recovery. So whenever you see the command:
Code:
fastboot flash recovery FRD_RECOVERY_NoCheck.img
Replace it with:
Code:
fastboot flash recovery_ramdisk FRD_RECOVERY_RAMDISK_NoCheck.img
For recovery2:
Code:
fastboot flash erecovery_ramdisk FRD_RECOVERY_RAMDISK_NoCheck.img
I know it's the same recovery being flashed on two different partitions but it doesn't matters
Happy flashing !
What will you achieve...
With this guide you can flash FullOTA-MF firmwares which are unapproved for installation (also called 'online firmwares', shows errors when flashing in TWRP or authentication errors when using Firmware Finder proxy) on your device by bypassing the authentication checks at stock recovery. PV (Point Version) firmwares should not be flashed by this method since they can be already flashed via TWRP.
I successfully updated my FRD-L09 from B392SP01 to B394. I'm writing down two methods, you can use any
Method 1 Using RedLotus
RedLotus is an open source huawei proxy that allows you to push any update to your device through HiSuite.
A) PREPARATION / Device
Download the modified (NoCheck, authentication removed) stock recovery:
Code:
Recovery 1: https://drive.google.com/file/d/0B4SPRmBNsTefSWZLSWxpWGd6QkE/view?usp=drivesdk&resourcekey=0-cZTB6Ze_tUOaJsTPPvErYQ
Recovery 2: https://drive.google.com/file/d/0B4SPRmBNsTefSVhxMWFoa01wams/view?usp=drivesdk&resourcekey=0-DuV9zTB1sSKCYrCGgMv0_Q
These recoveries have authentication checks removed allowing you to flash any firmware.
Flash both recoveries via fastboot:
Code:
fastboot flash recovery FRD_RECOVERY_NoCheck.img
fastboot flash recovery2 FRD_RECOVERY2_NoCheck.img
Reboot your device.
B) PREPARATION / Setting up HiSuite and RedLotus
Download and install HiSuite and nodejs:
Code:
HiSuite: consumer.huawei.com/minisite/HiSuite_en/
nodejs: https://nodejs.org/en/download/
Visit RedLotus Github repository and download it (find the green Clone / Download button)
Code:
https://github.com/lukx/redlotus
Extract the downloaded file to any directory. Inside that directory, hold down left Shift button and click right mouse button. In the context menu that appears select Open Command Window / Powershell Window here. Do not close this window till the end of the instructions.
Execute the following command inside the CMD / Powershell window.
Code:
npm install
You will now download the firmware you want to flash (for example FRD-L09C432B394, only FullOTA-MF supported). Goto TeamMT Firmware Finder and search for the firmware you wish to download. Copy the link to the filelist.xml of that firmware (for example filelist of FRD-L09C432B394: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/filelist.xml)
Execute the following command inside the CMD / Powershell window.
Code:
npm run download path-to-firmware-xml (replace last part with actual link)
Wait for the download to complete.
Navigate to C:\Windows\system32\drivers\etc. Open hosts file as Administrator and add this line at the end of it:
Code:
127.0.0.1 query.hicloud.com
This will set up a redirection resolving all hicloud queries to your localhost server.
Execute the following command inside the CMD / Powershell window:
Code:
npm run listen-hisuite
C) INSTALLATION
Connect the device to computer and ensure that HiSuite is recognizing the attached device. If it isn't go to Settings -> Developer Options and ensure ADB Debugging is enabled.
Hit the Update button in HiSuite. You'll see a message reading a new update is available and the update will be named RedLotus-OTA.
Start the update process and wait patiently.
Your device will eventually reboot to stock recovery and update will start installing. The update might seem to stuck at some percentage. It's normal, wait patiently for the update to install.
You're now updated to the firmware you chose.
OPTIONAL: In case of bootloops, factory reset the device and also unlock bootloader if the device automatically relocked.
Method 2 Using Root
A) PREPARATION / Downloading the required files
Download the modified (NoCheck, authentication removed) stock recovery:
Code:
Recovery 1: https://drive.google.com/open?id=0B4SPRmBNsTefSWZLSWxpWGd6QkE
Recovery 2: https://drive.google.com/open?id=0B4SPRmBNsTefSVhxMWFoa01wams
These recoveries have authentication checks removed allowing you to flash any firmware. Move both recovery files to internal storage or any path of your choice (this guide will assume you copied both files to /sdcard)
You will now download the firmware you want to flash (for example FRD-L09C432B394, only FullOTA-MF supported). Goto TeamMT Firmware Finder and search for the firmware you wish to download. Open the filelist.xml of that firmware and download all the files mentioned inside it. For example, the links for FRD-L09C432B394 are
Code:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/update.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/public/update_data_full_public.zip
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1585/g104/v93530/f1/full/FRD-L09_hw_eu/update_full_FRD-L09_hw_eu.zip
Copy the firmware files to /sdcard/HWOTA (ensure the files are inside HWOTA, it doesn't matters whether you copied the files to internal or external).
B) PREPARATION / Device
Flash the downloaded recoveries via fastboot:
Code:
fastboot flash recovery FRD_RECOVERY_NoCheck.img
fastboot flash recovery2 FRD_RECOVERY2_NoCheck.img
Reboot your device.
B) INSTALLATION
After your device is rebooted back to system, open any file manager that supports root.
Navigate to /data/ and create a new folder update/HWOTA.
Copy all the three downloaded zips to the folder created above.
Now using either Terminal Emulator or ADB Shell, grant SU privileges by executing su within the app or shell and further execute the following commands:
Code:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_full_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_full_FRD-L09_hw_eu.zip" >> /cache/recovery/command
You need to replace the file names (of the zip files) with the ones you've downloaded.
With everything done reboot your device to recovery:
Code:
reboot recovery
OPTIONAL: In case of bootloops, factory reset the device and also unlock bootloader if the device automatically relocked.
Credits:
@mankindtw : he originally patched the Mate 9 recovery removing the authentication. I patched Honor 8 recovery by identifying his edits and adding them.
@OldDroid : for hinting about how to patch the image and because this guide is inspired by his similar guide in Honor 8 Pro forums.

It appears that some information is not shown when using the XDA Labs apps. View in a browser so that you can see all the instructions
Edit - this is a known bug if XDA has been loaded into ram for a while. Close app and restart XDA if you encounter this.

Great. Very well explained. Keep it up mate.

For now use RedLotus method. There might be some problems with TWRP method. I'll try to find the root of the issue but until then, enjoy.

May I use RedLotus method without unlocking bootloader?

slonislaw said:
May I use RedLotus method without unlocking bootloader?
Click to expand...
Click to collapse
Yes you can use but it depends on the update you're trying to flash. Updates have built in verification and authentication checks and hence will fail.
That's where the modified recovery comes in which bypasses those checks and allows you to flash any firmware. Unfortunately, flashing modified recovery requires an unlocked bootloader.

I copied the FRDLO9-C432B396 FULL OTA MF downloaded from another device. My device is FRDL09-C185. I have the three files of my PC.
update.zip
update_full_FRD-L09_hw_eu.zip
update_data_full_public.zip
Which step is ideal for me to use?

vanbayor said:
I copied the FRDLO9-C432B396 FULL OTA MF downloaded from another device. My device is FRDL09-C185. I have the three files of my PC.
update.zip
update_full_FRD-L09_hw_eu.zip
update_data_full_public.zip
Which step is ideal for me to use?
Click to expand...
Click to collapse
Hmm...
Go with TWRP method since you already have the files.

thanks bro

@hackslash thanks for the detailed method. Can we do something similar for Honor 6x users as well. It may help in debranding or installing the other firmwares as well.

shashank1320 said:
@hackslash thanks for the detailed method. Can we do something similar for Honor 6x users as well. It may help in debranding or installing the other firmwares as well.
Click to expand...
Click to collapse
It is possible but I won't be able to confirm if the recovery works. I'll try to patch the image and will release a recovery for 6X too soon.

hackslash said:
It is possible but I won't be able to confirm if the recovery works. I'll try to patch the image and will release a recovery for 6X too soon.
Click to expand...
Click to collapse
Great. Let me know if i can contribute in any way, for files for testing anything.
Good luck. Hope to see some really useful tool for 6X too.

When I hit update in HiSuite it gives me an error saying "No Internet Connection. Please Check Your Network Settings."

Gus194 said:
When I hit update in HiSuite it gives me an error saying "No Internet Connection. Please Check Your Network Settings."
Click to expand...
Click to collapse
Did you run 'npm run listen-hisuite' before checking for updates. Follow the steps exactly as ordered and explained.

hackslash said:
Did you run 'npm run listen-hisuite' before checking for updates. Follow the steps exactly as ordered and explained.
Click to expand...
Click to collapse
Yup, followed all the steps. It says "Okay, Listening for HiSuite" Then I go to HiSuite and click update and it gives me the error.
Edit: What version of HiSuite did you use to flash the update? I updated HiSuite before doing the instructions, do you think that that has something to do with it?
Edit 2: Nevermind I think I fixed it, I just changed the Host line to to be in middle instead of the very end. Thanks for the help though

Guys is it possible to create a modded rollback package with inside these modded recovery images? I saw on firmware extractor something related to re-packing an update, would it be possible to create this package? It could be used to flash firmwares without unlock our bootloader? I suppose yes because rollback package has something of "magic" inside....it flashes everytime on a nougat firmware

In twrp, terminal " mkdir /data/update" is false " mkdir: can't creat directory '/data/update': File exists "
help me !

I have use RedLotus done. but end is erecovery?
now how should i do?

Gus194 said:
Yup, followed all the steps. It says "Okay, Listening for HiSuite" Then I go to HiSuite and click update and it gives me the error.
Edit: What version of HiSuite did you use to flash the update? I updated HiSuite before doing the instructions, do you think that that has something to do with it?
Edit 2: Nevermind I think I fixed it, I just changed the Host line to to be in middle instead of the very end. Thanks for the help though
Click to expand...
Click to collapse
I get the same error after doing the exact steps in the tutorial, can you tell me how did you fix it?
Cheers

flip360 said:
I get the same error after doing the exact steps in the tutorial, can you tell me how did you fix it?
Cheers
Click to expand...
Click to collapse
Instead of the host line being at the very end I put it in the middle.

J320FN: stock ROM: saving home? Custom .tar.md5 or by adb?

Hi all,
Could somebody please provide me a working link to a downloadable stock ROM for SM-J320FN ?
SSN: J320FNGSMH (Hungary, T-mobile), though any english speaking J320FN ROM will do.
I got "Custom binary blocked by FRP lock" message, almost sure I disabled OEM by accident before flashing faltisal's LineageOS (which worked pretty well so I'm going to reinstall it again, as soon as I have the device restored).
------
Ok, I've finally found some working sites with stock firmwares available. However all of the .tar.md5 images are single files. No separate bootloader, AP, CP, CSC, HOME_CSC. If possible, I would try saving some pics on my home folder.
The tar contains the following:
boot.img
cache.img
hidden.img
nvitem.bin
PM_sharkl_arm7.bin
recovery.img
sboot2.bin
sboot.bin
spl.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
Can wiping home be avoided by removing some .img from this .tar? Or could you provide some description how to make a HOME_CSC version of these?
I also looked another way: if I could backup via adb, as Android recovery works, but it's in sideload mode. Commands like adb pull or adb shell result in "adb: error: connect failed: closed".
Any solutions are appreciated.
Thanks in advance.

debi.janos said:
Hi all,
Could somebody please provide me a working link to a downloadable stock ROM for SM-J320FN ?
SSN: J320FNGSMH (Hungary, T-mobile), though any english speaking J320FN ROM will do.
I got "Custom binary blocked by FRP lock" message, almost sure I disabled OEM by accident before flashing faltisal's LineageOS (which worked pretty well so I'm going to reinstall it again, as soon as I have the device restored).
------
Ok, I've finally found some working sites with stock firmwares available. However all of the .tar.md5 images are single files. No separate bootloader, AP, CP, CSC, HOME_CSC. If possible, I would try saving some pics on my home folder.
The tar contains the following:
boot.img
cache.img
hidden.img
nvitem.bin
PM_sharkl_arm7.bin
recovery.img
sboot2.bin
sboot.bin
spl.img
SPRDCP.img
SPRDGDSP.img
SPRDLTEDSP.img
SPRDWDSP.img
system.img
Can wiping home be avoided by removing some .img from this .tar? Or could you provide some description how to make a HOME_CSC version of these?
I also looked another way: if I could backup via adb, as Android recovery works, but it's in sideload mode. Commands like adb pull or adb shell result in "adb: error: connect failed: closed".
Any solutions are appreciated.
Thanks in advance.
Click to expand...
Click to collapse
The solution I recommend is to install TWRP Recovery by flashing it using a tool like ODIN (search a tutorial on google for your phone). After flashing it sucessfully reboot your phone into recovery with key combination : Hold Home + Power + Volume Down until J3 2016 logo appear then go to Wipe section and select Advanced Wipe : Select System Dalvik Data Cache and dont select Internal Storage if u dont want to wipe your personal data.
Wait until it finish wiping then go back to TWRP Menu Home then choose Install and select the sdcard (path = storage/sdcard1) then select your stock rom and wait until it finish then reboot

[HOW-TO][EXYNOS/SNAPDRAGON] Root S20 series and upgrade firmware

Applicable Models:
All Exynos models including but not limited to:
SM-G980F or SM-G980F/DS (S20)
SM-G981B or SM-G981B/DS (S20)
SM-G985F or SM-G985F/DS (S20+)
SM-G986B or SM-G986B/DS (S20+)
SM-G988B or SM-G988B/DS (S20 Ultra)
All BL-unlockable Snapdragon models including but not limited to:
SM-G9810 (S20, Hong Kong, Taiwan, China mainland)
SM-G9860 (S20+, Hong Kong, Taiwan, China mainland)
SM-G9880 (S20 Ultra, Hong Kong, Taiwan, China mainland)
SM-G981N (S20, Korea)
SM-G986N (S20+, Korea)
SM-G988N (S20 Ultra, Korea)
Japanese model (SC-*) also use Snapdragon but I can't not confirm that its bootloader is unlockable.
It is known that bootloader can NOT be unlocked on U.S. models (U/U1) .
Frequently used key combinations of S20 series:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S20 series uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S20 series uses A-only partition which means there is only one set of system partition.
3. S20 series uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G9810", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OZL_CHC". The second 3-letter code "CHC" is your CSC.
6. Remember your model and CSC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
View attachment 4990053
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
If a recovery is available and you don't want to go through the process of downloading official firmware, go to #2.
You can also download a KERNEL TAR archive of your version here:
Exynos: https://github.com/jesec/proprietary_vendor_samsung_xyzs/releases
Snapdragon: https://github.com/jesec/proprietary_vendor_samsung_xyzq/releases
and then skip to Step 6.
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
View attachment 4990061
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G9810ZCU1ATD1). The last 4 letters (ATD1) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
View attachment 4990063
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
View attachment 4990065View attachment 4990067View attachment 4990069View attachment 4990071
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
XDA:DevDB Information
Root S20 series and upgrade firmware, Tool/Utility for the Samsung Galaxy S20
Contributors
jesec
Version Information
Status: Stable
Created 2020-04-08
Last Updated 2020-04-08

Other Methods:
You still need to unlock bootloader and disable AVB. (check Stage 2-3)
Recovery Magisk installation:
1. Open Odin on your computer.
2. Reboot your device to DOWNLOAD mode.
3. Put the recovery TAR flashable into AP slot.
4. Click start.
5. Use Volume Up + Power to reboot into recovery mode.
6. Install Magisk via recovery.
My recovery usually includes Magisk in "Select from root" -> ".builtin" folder. Or you can sideload the ZIP flashable of your choice via adb or https://flash.jesec.io/.
Flash pre-patched boot (Kernel) image:
Basically others have done stage 4-6 for you. Be aware that it is always safer to DIY.
You are welcomed to share your patched image to the community by replying to this thread.
Naming convention: model + firmware version (last four letters of build number) + magisk version .tar
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
SM-G9810_ATD1_ef9d077c.tar:
https://drive.google.com/open?id=1SxKXWHqR0aM_g457Yp7pk524_6aqp1k5

Some Interesting Things:
Change your CSC (carrier code):
You have to root your device. There might be some secret codes to trigger the menu without root, though.
Note that you can only change it to carrier configurations already included in your firmware.
WARNING: Your device will be reset to factory settings.
In a local terminal, type:
su
am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity

Cheers jesse seems like years since we were on s9 forums nice friendly guide you made here

What is the purpose of disabling android verify boot?

ngoralph said:
What is the purpose of disabling android verify boot?
Click to expand...
Click to collapse
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
ngoralph said:
Am rooted without doing this step will it cause any problems?
Click to expand...
Click to collapse
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
Am rooted without doing this step will it cause any problems?

Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar

bigback said:
Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar
Click to expand...
Click to collapse
you can extrsct boot and re tar it all in mixplorer then just upload to pc and flash in odin

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.

chieco said:
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.
Click to expand...
Click to collapse
Backread he already answered it on my inquiry

ngoralph said:
Backread he already answered it on my inquiry
Click to expand...
Click to collapse
I qouted his answer to your question asking for more details.

Magisk Root on Snapdragon based SM-G9860 S20+?
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.

chieco said:
I qouted his answer to your question asking for more details.
Click to expand...
Click to collapse
jesec said:
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.
Click to expand...
Click to collapse
AloxeCorton said:
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.
Click to expand...
Click to collapse
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.

So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
As it finishes flashing firmware hold volume buttons as it reboots. Then flash patched boot.img and reboot. Worked for me going from ATCH to ATCT today.

jesec said:
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.
Click to expand...
Click to collapse
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
I had the same issue... I used a tool (lz4_win64_v1_9_2) to uncompress lz4 format... I kept it just as boot.img and packed in boot.tar file and it worked.
Just for info, 7-zip built wrong tar file (don't ask me why...)... I had to use cygwin for it (or a linux if you have)

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
That's expected.
From Android 10, encryption keys are tied to AVB key (stored in vbmeta). By disabling AVB, you changed the AVB key from Samsung's to none. Though, if I remember correctly, some old versions have security loophole that allows you to boot a patched kernel even if AVB key is intact (recovery is still protected however). That's actually a serious breach of this additional integrity assurance. (your sensitive data is still safe nonetheless as there is a customer key tied to your password/pattern/etc)
Read more: https://source.android.com/security/keystore/version-binding
AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
That should not happen. Here is a screenshot if things are done right:
Make sure you pack the TAR right (see OP for a screenshot of boot.img.lz4.tar) and the file you transfer to your device is the TAR file (boot.img.lz4.tar if you don't change the file name).
Plus, maybe check if Magisk version is right. Make sure you use the Canary builds.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
do it on fone thats what i did mixplorer will tar it for you then move to pc and flash