Related
Device: Galaxy Nexus I9250XXKL1
Carrier: Retail
Country / Language: Brazil / English
Build number: full_maguro-eng 4.0.1 ICL23D 320 test-keys
OS: Android 4.0.1
Kernel:3.0.1
I've just bought a Galaxy Nexus, I've turned him on, all OK, but I cannot add a Google Account, on Accounts & Sync > Add an Account, I just have the option for Corporate and Email.
No Google Apps at all (not even Google Market (Play Store).
SIM card is inserted (TIM Brazil)
GMS network is working
WiFi is working also
Mobile is brand new as retail (no carrier)
Do a factory reset.. I seen that happening to 2 people and the factory reset fixed it.. Hope it helps.
Skickat från Qs Mobilen (Galaxy Nexus)
Q.Entity said:
Do a factory reset.. I seen that happening to 2 people and the factory reset fixed it.. Hope it helps.
Skickat från Qs Mobilen (Galaxy Nexus)
Click to expand...
Click to collapse
I've did it 3x, no change
Spetsnaz. said:
Device: Galaxy Nexus I9250XXKL1
Carrier: Retail
Country / Language: Brazil / English
Build number: full_maguro-eng 4.0.1 ICL23D 320 test-keys
OS: Android 4.0.1
Kernel:3.0.1
I've just bought a Galaxy Nexus, I've turned him on, all OK, but I cannot add a Google Account, on Accounts & Sync > Add an Account, I just have the option for Corporate and Email.
No Google Apps at all (not even Google Market (Play Store).
SIM card is inserted (TIM Brazil)
GMS network is working
WiFi is working also
Mobile is brand new as retail (no carrier)
Click to expand...
Click to collapse
unlock the bootloader, root the phone and install 4.0.2 or higher or just install a custom rom with gapps
nccu_eagles said:
unlock the bootloader, root the phone and install 4.0.2 or higher or just install a custom rom with gapps
Click to expand...
Click to collapse
But I'll loose Warranty.
It's possible to update to 4.0.2 without rooting?
Spetsnaz. said:
But I'll loose Warranty.
It's possible to update to 4.0.2 without rooting?
Click to expand...
Click to collapse
If you ever have an issue requiring a warranty repair you can always restore back to a stock rom and re-lock the bootloader...
nccu_eagles said:
If you ever have an issue requiring a warranty repair you can always restore back to a stock rom and re-lock the bootloader...
Click to expand...
Click to collapse
Where can I find a "original" 4.0.2?
Spetsnaz. said:
Where can I find a "original" 4.0.2?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1392310
mskip said:
**FAQ**
----------------------------------------------------------------------------
Q. How do I Update to the latest Google Stock Rom?
THE FOLLOWING PROCESS WILL ERASE YOUR INTERNAL STORAGE BACKUP ANYTHING YOU NEED.
You can use the GN ToolKit which will do everything automatically or execute the following steps.
Or you can follow the following instructions and do it manually:
These steps assume that you have set up your adb/fastboot drivers correctly.
1. Download it from *HERE*.
2. Unzip it to a folder on your pc.
3. Copy the file fastboot-windows.exe to this folder (you can find the fastboot file in many places including my ToolKit download on post#1).
4. Browse to this folder on your pc, hold the 'shift' key down while right clicking on a blank area of the window and select 'Open command window here' to open a command prompt in that folder.
5. Boot the phone into Fastboot Mode (KEEP holding the 'Volume up' and 'Volume down' buttons while pressing the 'Power' button).
6. Connect your device via the usb cable
7. In the command prompt type:
which should return your phones serial number and prove you are connected.
8. To flash the google images type the following:
9. Press the power button to boot into pure Android and complete the setup.
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download and run the GN Toolkit.
2. Follow instructions on the first screen to install fastboot drivers (if you havent already done so)
3. Option5 to flash a stock rom.
4. Let the phone reboot, then shut the phone down and reenter fastboot mode again (hold vol up and vol down buttons together while pressing power button).
5. Option7 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped.
----------------------------------------------------------------------------
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1392310
If you just bought it, take it back.
Hexxenhammer said:
If you just bought it, take it back.
Click to expand...
Click to collapse
The problem is that I bought it online, to return it and receive a new one will take aprox. 15 days...
It seems you have a pre-release engineering build installed. You can unlock the boot loader, flash 4.0.2, relock and be done with it. Or you can send it back.
Just follow the instructions posted above. It's easy and can be done in less than 15 minutes.
Sent from my Galaxy Nexus using XDA Premium HD app
Don't worry about your warranty... you don't have one.
You have an early pre-releae eng version for software.
This is not a retail device.
That's really weird... anyway, since this is the only phone I have, i'll have to do this...
One big problem, I've tried with the GNex TOOLKIT and manually PdaNET exe to install ADB/FASTBOOT drivers...
With GNex i'm getting a error message regarding cache
With PdaNET i'm getting Install to phone failed, Installer fail to open device popup
Any ideas?
When I turn on the phone on FastBoot mode it shows
FASTBOOT MODE on red
and down bellow shows
LOCK STATE - UNLOCKED on red also
What does those messagers means?
Spetsnaz. said:
When I turn on the phone on FastBoot mode it shows
FASTBOOT MODE on red
and down bellow shows
LOCK STATE - UNLOCKED on red also
What does those messagers means?
Click to expand...
Click to collapse
looks like your bootloader is already unlocked. when you power on the device does it show a unlock symbol under google name? if so just flash clockworkmod
nccu_eagles said:
looks like your bootloader is already unlocked. when you power on the device does it show a unlock symbol under google name? if so just flash clockworkmod
Click to expand...
Click to collapse
Yes!
It shows a Unlock figure.
I would like to uplode the Google Factory Image, how to do that manually?
http://code.google.com/intl/pt-BR/android/nexus/images.html
I have this screen on normal boot:
{
"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"
}
and if I do the Fastbooloder (all buttons pressed) this screen:
1. Download the Android 4.0.2 factory images to your PC.
2. Unzip the file and its contents into your SDK/Tools folder (wherever your adb.exe and fastboot.exe files
are).
*Make sure they are not in their own folder, but have all been extracted to Tools.
3. From within your Tools folder, open a command prompt (SHIFT + right click – “open command prompt here”):
4. Type the following commands, allowing each to finish before moving onto the next:
adb reboot bootloader
sh flash-all.sh
or
adb reboot bootloader
chmod +x flash-all.sh
./flash-all.sh
Link
Ive installed SDK but there isn't those 2 .exe at Tools folder.
But on Desktop there is a folder called adb-tool_for_windows, with a Tools folder, and inside there is adb.exe and fastboot.exe
Can I use this folder?
To tools folder, do I have to extract what is inside the .tgz file or what is inside the .tar files?
I have here xxxx.tgz\xxxx.tar\yakju-icl53f folder\1 .sh files 2 .img files 1 .zip file
Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
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. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite 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 (Canary builds)
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-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
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.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
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.
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 (G770FXXU2BTD2). The last 4 letters (BTD2) 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.
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")
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.
(OPTIONAL) Use prepatched magisk boot
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"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
*reserved*
Thank you for this amazing guide and the file without which it would not have been possible.
Be sure to join my TG group, if you are interested in AOSP, there's a lineage build testing currently running.
Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.
Awesome
sosimple said:
Thanks for this.
But it really is the most difficult way to root i have seen.. I'm not sure how many will try all this just to root a phone.
Click to expand...
Click to collapse
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!
hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.
4TheBesT said:
hey guys i ve just bought s10 lite and rootted it with method upside. but i was apple user for a 3 years before that i used to note 3-4-5 series and it was easy to rootable also i was getting useable stuff like grenify or nice equaliser type apps. ı would like to know how can i enjoy my phone with rooted ? for example i have iphone x with me still and its jailbreaked and there are repo sites that help to get to download app or modules to make you happy with your phone. do we have such stuff in android going on right now ? thanks again for rooting and helps.
Click to expand...
Click to collapse
If you are not sure what's the purpose of rooting a phone you shouldn't be doing it. "To make you happy with your phone" is a really subject question with no right answer, that depends on your specific needs.
If you ask about modules check out Magisk Modules.
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
Hello, just to confirm that the steps detailed in this guide works, thanks OP, at least this gives us more freedom.
{
"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"
}
no able to root with this method ! .. step ( v-meta disabler ) with system CP,AP,HOME CSC fail with official binary .. i follow you're steps !
i guess the file v-meta disabler u have attached is not compatible with my device ?! and yes i have same you'res BTD2 ONEUI 2.1 FIRMWARE
teenoo said:
This will be done by absolutely everyone who wants to root his Galaxy S10 Lite. ABSOLUTLEY EVERYONE!
Click to expand...
Click to collapse
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.
Is there any way to unlock the bootloader and root SM-G770U1?
kamill85 said:
In my case, I flashed latest FW (July 2020), Magisk Manager (the "install" buttons were not visible at first, but after some reboots they were). Created patched boot with Magisk Manager, unlocked bootloader (in settings & in bootloader), flashed modified boot image and it worked. At first boot, it restarted, and wen back to recovery, stating that system is corrupted, gave option to factory reset, so I did, it restarted again, and again, and then it booted fine. No VMBETA flashing needed. The trick, was (I suppose) doing the factory reset after flashing the modded kernel. Finally, when the phone booted, I did the usual first-run setup and enabled developer settings / adb installed Magisk Manager - it completed the setup, everything was fine after that.
Click to expand...
Click to collapse
I was about to give up on the July update until I read this and tried a few more things. Bad internet caused missing "Install" buttons and I tried patched the WHOLE AP...instead of just patching a boot.tar like in Stage 5. So gooder internet, Odin-ing only the AP with the Magisk patched boot.tar, another wipe,
Code:
adb install .\MagiskManager-v7.5.1.apk
and I was rooty tooty.
I didn't care about burning everything on the phone. I think that some of the extra steps here were for trying to minimize the wipes. Thanks for the extra hope @kamill85 !
Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,
SamFirm
sosimple said:
Are there download links for official images somewhere without paying? Everywhere i searched you needed to sign in and pay..
Thanks,
Click to expand...
Click to collapse
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!
dim42 said:
Did you look up SamFirm like in the instructions? It pointed me to this page: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 That says it's deprecated but it was able to get me the July 2020 FW for the S10e. I didn't try the other thing, Updato that it points you to. I ran the exe in the zip and pushed a few buttons and it worked for me. No waiting 20 hours. Hope that helps!
Click to expand...
Click to collapse
Thanks. What Deprecated meant? What iis the difference from original?
the show stopper said:
Is there any way to unlock the bootloader and root SM-G770U1?
Click to expand...
Click to collapse
+1
Also curious if anyone's gotten this working with the US version
So if i do this ill never ever be able to use Samsung pay ever again?
Vaughnn said:
Models:
SM-G770F or SM-G770F/DS
Frequently used key combinations keys:
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. S10 Lite uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S10 Lite uses A-only partition which means there is only one set of system partition.
3. S10 Lite 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 (Canary builds)
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-G770F", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OXM_PHE". The second 3-letter code "PHE" is your CSC.
6. Remember your model and CSC.
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.
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
(Stage 4 and below are method to root your phone using your own odin files, if you wish to use a prepatched for a faster way to get root, go to OPTIONAL)
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.
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 (G770FXXU2BTD2). The last 4 letters (BTD2) 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.
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")
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.
(OPTIONAL) Use prepatched magisk boot
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"
BEWARE: PREPATCHED BOOT ONLY TESTED ON BTD2 ONEUI 2.1 FIRMWARE
(https://drive.google.com/file/d/1chFXa2w_t2EgbfQIiVDOVR2KUeiwFpUs/view?usp=sharing)
Telegram Support Chat: https://t.me/joinchat/FrDuSBgUxDGSZ1vVmej7fw
Click to expand...
Click to collapse
Anyway to get to pass the safety nets?
Yes i pass safety net, but i use systemizer and with it i cant pass.
When I switch off systemizer in magisk I pass safety net
Code:
Your warranty is now void.
If you root your device, Your KNOX status will be tripped.
You can still pass the safety net after you root if you follow the instructions.
I am not responsible for bricked devices, dead SD cards although it is not really possible
Please do some research if you have any concerns about doing this to your device
How to flash official firmware? (not the root and unlock bootloader part!)
You will need:
A Galaxy Z Fold 3 and common sense
Samsung Odin (the flashing tool of the official firmware)
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
You need to extract the zip file and you are going to use the file Odin3_v3.14.1.exe inside the folder.
Samsung Android USB Driver for Windows
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Double-click and install the exe file.
Samsung Official Firmware
Release 1.0.3 · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
Download the platform you want to download to. (Windows)
You need to extract the zip and double click open the file Bifrost.exe inside the folder.
You need to fill in the Model, Region, press the Check for Updates button and the Download button.
How to find the Model: on your phone → Settings → About Phone → The third row says the Model number and you need to remove the part with the part of /xx, for example, SM-F926B/DS and you only need to type SM-F926B
How to find the Region: You can check the Region at this link https://samfrew.com/model/SM-F926B/
You need to find find a three-letter word depending on your carrier and country and type it in Bifrost, for example, EVR
Press the Check for Update button and download it with the Download button.
Put it to a place you can easily find, ie. Desktop.
After downloading it, find the file SM-xxxxx_x_xxxxxxxx_xxx.zip.enc4 on the place you put it and change the document format from .enc4 to .zip. Then, double click and extract the file.
Open Odin3_v3.14.1.exe and turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Go back to Odin3_v3.14.1.exe:
-Click on BL and select BL_xxxxxxxxxx.tar.md5
-Click on AP and select AP_xxxxxxxxxxx.tar.md5
-Click on CP and select CP_xxxxxxxxxx.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_xxxxxxxxxx.tar.md5
Press Start to flash the firmware, after done, your device will automatically reboot to the system.
How to unlock the bootloader?
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
How to root your phone?
After you unlock your bootloader, you set up your phone and make sure you do not sign in google account first. Install Magisk https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk on your phone. Oh yes, in case you do not know, you need to allow the app to install apps so that you can install the apk.
Transfer AP_xxxxxxxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.
Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go' and find the AP_xxxxxxxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.
After finishing the patching, you need to transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.
Turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:
Click on BL and select BL_xxxxxxxxxx.tar.md5
-Click on AP and select magisk_patched-24xxx_xxxxx.tar
-Click on CP and select CP_xxxxxxxxxx.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_xxxxxxxxxx.tar.md5
When it finishes flashing it, it will automatically reboot and you can gain root access.
Optional: If you want to have the safety net passed (most of the banking apps use it), then you need to install the zip
as a Magisk module in Magisk https://github.com/kdrag0n/safetynet-fix/releases
How? Go to Magisk → Modules → install from storage and select the zip you downloaded.
How to update without losing root and data
Open Odin and put the new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do its stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power
As soon as the screen appears, let go of all buttons.
Within moments, the phone with updates, data and magisk rooted will present in front of you. Hurray!
Thanks for the post I want to try it but I'm on SM-F926U also I don't want to lose any data will this erase all my data such as apps, pics etc with backup?
AnnaNguyen said:
Thanks for the post I want to try it but I'm on SM-F926U also I don't want to lose any data will this erase all my data such as apps, pics etc with backup?
Click to expand...
Click to collapse
You must lost data when you root your phone.
What you can do is using Samsung or Google backup and move your photos and files to your PC
Thank you William again I just did it and I confirm works on SM-F926U
AnnaNguyen said:
Thank you William again I just did it and I confirm works on SM-F926U
Click to expand...
Click to collapse
You are welcome
Hi i tried to root my samsung galaxy z fold 3 model F926B version android 11 i did all steps using magisk version 23.0 but after i flash the patched rom i keep getting stuck on samsung logo and error says this device version is not official is there anyway i can bypass it?
nathanalbat said:
Hi i tried to root my samsung galaxy z fold 3 model F926B version android 11 i did all steps using magisk version 23.0 but after i flash the patched rom i keep getting stuck on samsung logo and error says this device version is not official is there anyway i can bypass it?
Click to expand...
Click to collapse
Just rooted my new GZF3 SM926B/DS with this method and got to the exact same thing (but using magisk 24.1).
Re-flashed and the same thing again but it was easily fixed.
One more part should be added to the guide.
After you flash the last time with the patched AP-file and get a boot loop to recovery, do a factory reset from (stock) recovery, phone restarts and you have to set it up but magisk is there and you're rooted!
Just go to apps, try to open magisk which will tell you that you need to upgrade to full version, accept, open magisk and accept the "additional part" -> phone reboot one last time and DONE!
You now have a fully functioning and rooted GZF3
iLind said:
Just rooted my new GZF3 SM926B/DS with this method and got to the exact same thing (but using magisk 24.1).
Re-flashed and the same thing again but it was easily fixed.
One more part should be added to the guide.
After you flash the last time with the patched AP-file and get a boot loop to recovery, do a factory reset from (stock) recovery, phone restarts and you have to set it up but magisk is there and you're rooted!
Just go to apps, try to open magisk which will tell you that you need to upgrade to full version, accept, open magisk and accept the "additional part" -> phone reboot one last time and DONE!
You now have a fully functioning and rooted GZF3
Click to expand...
Click to collapse
i did same steps as you but i did it with magisk 23 and worked thanks tho
iLind said:
Just rooted my new GZF3 SM926B/DS with this method and got to the exact same thing (but using magisk 24.1).
Re-flashed and the same thing again but it was easily fixed.
One more part should be added to the guide.
After you flash the last time with the patched AP-file and get a boot loop to recovery, do a factory reset from (stock) recovery, phone restarts and you have to set it up but magisk is there and you're rooted!
Just go to apps, try to open magisk which will tell you that you need to upgrade to full version, accept, open magisk and accept the "additional part" -> phone reboot one last time and DONE!
You now have a fully functioning and rooted GZF3
Click to expand...
Click to collapse
Ah, thanks for your recommendation. I have make it in the video but I have forgotten to mention it in the guide. Sorry.
Does this solve the camera issue on fold 3?
Oracle79 said:
Does this solve the camera issue on fold 3?
Click to expand...
Click to collapse
I think the camera’s all right
Oracle79 said:
Does this solve the camera issue on fold 3?
Click to expand...
Click to collapse
Yes, no problem with the camera. Quite sure it's the OS-update that resolve the issue. So just make sure you download the latest update (BVA9) and flash that one.
AnnaNguyen said:
Thank you William again I just did it and I confirm works on SM-F926U
Click to expand...
Click to collapse
Hey There, Did the F926U have the bootloader unlock option without having to pay for it and do it remotely ?
It was unlocked I got it on galaxyfirmwares for free
Thanks for the Guide , Williamtung
I want to share me experience ( SM-F926B ), updating from a rooted VBA9 to the latest BVB3 firmware , without losing root and data !
Steps:
1. Download the latest stock F926BXXS1BVB3 ( at the time writing this post )
Samsung Galaxy Z Fold3 5G Firmware Download SM-F926B Free Download
Samsung Galaxy Z Fold3 5G Firmware Download SM-F926B Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
2. Patch the stock AP (BVB3) file with magisk and just follow the guide from there... , You will be updated with the latest and rooted , extremely easy !
Transfer AP_xxxxxxxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.
Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go' and find the AP_xxxxxxxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.
After finishing the patching, you need to transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.
Turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:
Click on BL and select BL_xxxxxxxxxx.tar.md5
-Click on AP and select magisk_patched-24xxx_xxxxx.tar
-Click on CP and select CP_xxxxxxxxxx.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_xxxxxxxxxx.tar.md5
When it finishes flashing it, it will automatically reboot and you can gain root access.
pvillasuso said:
Thanks for the Guide, Williamtung
I want to share my experience ( SM-F926B ), updating from a rooted VBA9 to the latest BVB3 firmware, without losing root and data!
Steps:
1. Download the latest stock F926BXXS1BVB3 ( at the time writing this post )
Samsung Galaxy Z Fold3 5G Firmware Download SM-F926B Free Download
Samsung Galaxy Z Fold3 5G Firmware Download SM-F926B Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
2. Patch the stock AP (BVB3) file with magisk and just follow the guide from there..., You will be updated with the latest and rooted, extremely easy!
Transfer AP_xxxxxxxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.
Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go' and find the AP_xxxxxxxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.
After finishing the patching, you need to transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.
Turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:
Click on BL and select BL_xxxxxxxxxx.tar.md5
-Click on AP and select magisk_patched-24xxx_xxxxx.tar
-Click on CP and select CP_xxxxxxxxxx.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_xxxxxxxxxx.tar.md5
When it finishes flashing it, it will automatically reboot and you can gain root access.
Click to expand...
Click to collapse
Thanks for your sharing! I may add this useful information to the guide if you please.
Williamtung said:
Thanks for your sharing! I may add this useful information to the guide if you please.
Click to expand...
Click to collapse
Sure !! , thanks again , this is hands down , the best and easiest way to root/update keeping all your data and setup
Is there a way to Root the F926U?
About to find one.. Was wondering whether anything is possible?
JazonX said:
Is there a way to Root the F926U?
About to find one.. Was wondering whether anything is possible?
Click to expand...
Click to collapse
Not possible unless you able to unlock your bootloader
AnnaNguyen said:
Thank you William again I just did it and I confirm works on SM-F926U
Click to expand...
Click to collapse
So, you successfully unlocked your bootloader and rooted your SM-F926U?
Thanks.
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
{
"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"
}
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Did you know that....
The CSC_OXM file is used to restore the internal memory as factory, this will delete all personal data in the phone memory, all applications and data associated with it.
The HOME_CSC_OXM file, on the other hand, will not act in any way on the internal memory. Useful if you want to update while remaining in the same type of ROM. Not recommended if your phone has a Custom ROM installed, as it may not start or give errors in previously installed applications.
If you want to do a clean install of the original ROM, always use the CSC_OMX file!
Click to expand...
Click to collapse
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
Well now you have your Samsung with Original firmware again. Enjoy
ExileTM said:
Welcome to this easy guide.
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
View attachment 5628035
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
View attachment 5629259
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
View attachment 5629261
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
View attachment 5628037
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
View attachment 5629463
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
View attachment 5629465
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
View attachment 5629265
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
View attachment 5628039
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
View attachment 5628043
View attachment 5628045
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
View attachment 5628041
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
View attachment 5629449
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
View attachment 5629493
Well now you have your Samsung with Original firmware again. Enjoy
Click to expand...
Click to collapse
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
RedSpikeJr said:
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Click to expand...
Click to collapse
ExileTM said:
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
Click to expand...
Click to collapse
I followed the full guide, but I got stuck after flashing the firmware in Odin. It shows the screen of "Erasing data", and after that, nothing more
Even after locking again the bootloader
And yes, I ticked what's needed in Odin and used the .pit file
My model it's SM-N975F
The original CSC it's ZTO. Flashed the latest firmware
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
ExileTM said:
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
Click to expand...
Click to collapse
The USB it's the original from Samsung.
The device is 256GB
ExileTM said:
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
Click to expand...
Click to collapse
Tried this already. Didn't work
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
I tried this but not in the process of "Do the format and then do the Odin process" so I can try
I'm trying now with USB OTG to know if I can flash the system.img (and know if from there I can solve this)
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
Tried from reset data on official recovery to doing the change of format in TWRP and the doing all of the process again. No success.
Also tried with USB OTG with system, vendor, product and boot image. Neither
One thing that happened is that when trying to change the system partition to exFAT, it gave an error (system is not mounted) but changed the format to vFAT. Changing it to another option doesn't give that error, so I tried to do with another option and back to ext4.
I don't think it's a physical issue, if turns on, there is some hope at least
There is almost certainly a solution to your problem. (have you tried to do "format data" and typed "yes" in TWRP recovery?). Anyway, it's night at my place now, I'll see tomorrow to think of some other solution.
Tried already. Also tried to format the data with fastboot (Lineage Recovery gives the option to fastboot in Samsung)
I have the exackt same problem with my note10+ with 256GB and dual sim. and the problem you describe is also 100% what i experienced and still have as an issue... If you get to the point where you can solve the issue then please write me my friend. I will do the same ofcourse... btw can you use your pen in TWRP? i can only mark the files but not click them to run...? i have the idea that the TWRP for our model isnt built right somehow..
I assume you haven't solved the problem yet. In these days I have looked around but I have not found much ...
I saw a video, which through the ADB shell a guy was able to find the list of all partitions with the numbers of all the blocks and information and practically managed to rebuild the system partition from scratch, but I don't know if it works on samsung.
This is video:
Then another thing, what procedure did you follow for rooting? You may have had problems during the rooting process.
I followed this guide:
To update the situation
The battery of the phone inflated like a balloon, so I needed to go to a technician. I don't know for sure if that was caused by something physical, but will update when have some news
Ok, let me know if the technician can get you to restart the phone, and out of curiosity, he can bring the knox back to 0.
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
aaaajwedk said:
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
View attachment 5647587
Click to expand...
Click to collapse
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
ExileTM said:
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
Click to expand...
Click to collapse
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
aaaajwedk said:
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
Click to expand...
Click to collapse
OK well. Glad it was helpful. Yes, however, until you root all the apps will work. The only one are some applications by Samsung that will no longer work because they are based on the knox.
Otherwise like Google Pay, all banking and account apps, software updates should work smoothly.
Hi, is this guide usable for the S22 snapdragon version? My device is rooted, and I want to back to original firmware.
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
{
"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"
}
"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1.
"Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted.
"App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)
"App > Installed" shows the currently installed version of the Magisk app
V0latyle said:
Recommended changes:
Build Number need only be tapped 8 times to activate developer mode, not ten.
After downloading the firmware zip, the user will need to extract it. The AP file is what needs to be patched in Odin.
Flashing the AP file won't wipe data. This is determined by which file the user selects in the CSC slot: CSC.tar will wipe the device, HOME_CSC will not.
The "Ramdisk" information in Magisk does not indicate whether or not the device has been rooted with Magisk. If you install the Magisk app on a stock unrooted ROM, it will still indicate whether the device has ramdisk or not. The only difference this makes is how Magisk should be installed. See Magisk Installation
The "Installed" indicator in Magisk is what actually indicates whether the device is rooted. If this says N/A, the device has not been properly rooted. With root, "Installed" should show the version of the Magisk patch:
View attachment 5893171"Magisk > Installed: 26.1" indicates that the device is currently rooted with the patch that corresponds to Magisk release 26.1."Magisk > Ramdisk" only indicates whether or not the device uses ramdisk. Again, this has nothing to do with whether the device is rooted."App > Latest" indicates the latest Magisk release for the selected update channel (stable, beta, custom)"App > Installed" shows the currently installed version of the Magisk app
Click to expand...
Click to collapse
thank you, ive adjusted the how-to to your recommendations
Hello,
What about Knox with this method ??
Thanks
leosoftstudios said:
Hello,
What about Knox with this method ??
Thanks
Click to expand...
Click to collapse
I think this easily trips it. Cant confirm, because the usual system information in the bootloader doesnt show up for me. I tried using Samsung Pass with zygisk + shamiko (tried to activate anything samsung related in the denylist) but i just get the message that "you cannot use samsung pass on a rooted device", so iam not even getting past that.
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
terry_mccann said:
Why would someone root it? One UI is the most perfect Android imaginable....
Opinion,of course.
Click to expand...
Click to collapse
Funny how this pops up in every thread here like people get paid to go to a forum for custom roms and then leave their opinion, why a custom rom is useless...just why? how do you people even get here, arent you in the totally wrong place?
and to settle the argument: install a custom rom to get rom updates beyond the manufacturers lifetime support, simple as that. faster security updates, debloating, etc, dont get me started.
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
draykhar said:
Thank you for posting this guide, i had a question and was getting hung up on step 2.
The CSC code my phone is giving me is OYN, and I'm struggling to find that firmware version on the website provided. Do i just need to wait for the firmware for that CSC to be uploaded to that site?
Thanks!
Click to expand...
Click to collapse
I guess the CSC is country/provider dependend. Maybe your mobile shop got the device from another country or so? Try to check the model number (check 'SM-A546B' for the last letter), I found some roms with OYN as CSC with this model of the A54 here: https://samfrew.com/model/SM-A546V/region/VZW/ but was just a lucky find - definetly check your model number and make sure, you got the right one.
So I'm currently missing the "OEM Unlock" option w/in the "Developer Options" menu on my device. Does anyone know of any other alternative method to unlocking the bootloader for my situation?
Hi there
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
knighToFdemonS said:
WARNING! THIS WILL WIPE ALL DATA FROM YOUR DEVICE!
1. Get your android and device version from settings -> about phone -> service provider software version (for me its SM-A546B EUX)
2. Download the latest stock ROM for your specific device from https://samfrew.com/
3. Download and install Odin from https://samsungodin.com/download/
4. Activate developer settings (click 8x on buildnumber)
5. Activate usb debugging from the developer settings
6. Activate OEM Unlocking (THIS WILL WIPE ALL YOUR DATA)
7. After this factory reset, hold down volume up + power to get to the recovery
8. Choose to reboot to bootloader
9. You will be asked if you want to unlock the bootloader, choose yes
10. Put the downloaded stock ROM onto your device (sdcard, internal storage, etc)
11. Download the Magisk app from the Playstore
12. Open Magisk and hit install
13. Select the downloaded stock ROM from your storage and wait for the process
14. Copy the magisk-modified ROM to your PC
15. Pack the magisk-modified ROM in a TAR and flash as "AP" with Odin
16. Let the phone boot and complete the initial setup
17. Open Magisk and reboot if suggested
(18. Go into Magisk again, go to Settings and enable Zygisk
19. and reboot again)
Magisk should now show the current version in "installed" and apps can request superuser access now. If "installed" shows n/a then magisk root did not work.
If anything fails, you should always be able to press the powerbutton + volume up to get to the bootloader (big blue screen) and flash the AP of the stock rom.
Need help with:
- Patch dm-verity/vbmeta (to install a custom recovery)
- Porting TWRP to Exynos1380 kernel
Click to expand...
Click to collapse
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
sameog said:
Hi there
Hi there!
I just unlocked my a54 from Metro PCS. Can this phone be rooted? I haven't rooted since Samsung put an iron fist on US-based phones.
Anyone chime in.
Click to expand...
Click to collapse
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
LidelnFR said:
Thanks for the tutorial!
However, I'm pretty sure I used the proper firmware, but now the phone keeps complaining that I have to "update carrier settings" and to "reboot" and then it complains that it "couldn't update carrier settings".
Anyone having this, or having a solution? Couldn't find anything by myself
Click to expand...
Click to collapse
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
knighToFdemonS said:
I currently have the same problem but I had not much time to try things out in the last 2 weeks (and somewhat still waiting on that thread from the guy who wanted to build TWRP for this kernel).
I remember that at one time, I fixed that problem, but I cannot recall the exact steps what I was doing.
I think I cleared all the data stuff from the bootloader-menu (ex. wipe cache, wipe data, etc) just right after a fresh AP/image flash with the magisk-rooted-ROM. I remember doing it multiple times, on several reboots (tried to follow some very old youtube-videos which apparently fixed that problem in android 4).
But it could also have happened while i debloated the rom one time with adb commands (just uninstalled all the extra stuff like facebook and alot of samsung stuff aswell - that also might have fixed it.
Just got another idea: try to find the provider-app of the system message via "adb logcat".
Maybe I can find some time on the weekend to take another look but maybe this already helps you.
I just didnt want to reflash the ROM all the time, just in case something breaks and I have no TWRP yet to recover from a bricked device.
Click to expand...
Click to collapse
Thank you kindly for this! I am quite a noob so I don't want to reflash the ROM all the time either ^^
Not sure about these adb commands, but I might have a look if I have time (this is my gf's phone, I don't want to bother her all the time)
Btw, for the installation, I had to do these steps (most are identical, but some are slightly different or more specific):
### Preparation steps:
"Called" *#1234# to get CSC and other information
I used SamMobile (premium sub to get the file quickly because I was in a hurry -- this is not a promo, I have zero link with them whatsoever)
Went to this thread to get Odin 3.14.1 3B PatcheD (not sure it changed anything)
Did the steps to activate developer mode, USB debugging, OEM unlocking (it did not wipe anything for me)
Turned the phone off
Turned it on again using VOL+ and VOL- at the same time (had to try again because it didn't work the first time)
Another option is to use ADB: adb reboot recovery (first you have to list devices, and if need be authorize (from the phone) ADB to access it)
In the blue screen, written at the center, are the options you can "press" for (not easy to see at first)
So, LONG (!!) press VOL+ to ask to unlock bootloader
SHORT press VOL+ to confirm unlocking the booloader (which will wipe data)
Reboot phone
### Firmware/flashing steps:
On the PC, unzip the Samsung firmware
Put (only) the "AP" file into the phone (e.g. "Downloads" directory) (I had first to remove the trailing ".md5" from the filename to only keep ".tar", not sure it is mandatory but I didn't want to lose 12 minutes of copy for nothing)
Install Magisk on the phone (ONLY from their GitHub : topjohnwu) (you have to do it AFTER the bootloader is unlocked, if I understood things properly)
Using Magisk, click the first "install" button at the top (which will actually patch an AP file), choose the AP.tar file from your "downloads" folder (for example)
When done, copy the newly generated file (magisk_patched-26100_{UID}.tar) to the computer (I first had to unplug USB and replug, because it would not refresh the folder properly, at least on Windows 10)
The file was already in .tar extension (at least for me) so I didn't have to compress it again
Reboot the phone in recovery or "download mode" (using the same steps as earlier)
Launch Odin, plug the phone, and flash the Magisk-patched AP file (only this file) (leave the options to their default)
It should reboot the phone when it's done
### Magisk-related steps:
Install Magisk again (it should (??) be wiped iirc), it will ask you to reboot after some changes it automatically made
Reboot
Relaunch Magisk, go to options, activate Zygisk: it will install a new module
Reboot
Go to Magisk, enable systemless host file (or something like that) so that ad blockers (e.g. AdAway) can work properly
Reboot
Go to Magisk again and enable "hide magisk" from the options, choose a custom name
Reboot one last time (not sure you have to reboot for each Magisk step, it's just to be sure)
Again, most steps are identical, but other change slightly or are more precise, because honestly I was kinda lost at first
Thank you again for the tutorial!
For the carrier services, I tried to "reset network" but it didn't do anything.
urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
urbanman2004 said:
I got an A54 phone from MetroPCS as well, but was unable to unlock "OEM" b/c the option was missing from "Developer Options"... Could you screenshot where you were able to locate the "OEM unlock" option and what version firmware is your phone currently on?
Click to expand...
Click to collapse
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
bizkit_120 said:
Just throw some ideas, if flash another firmware change MetroPCS to T-Mobile for example or US global version, not sure if this OEM unlock toggle appears..if yes, it would be straightforward after that
Click to expand...
Click to collapse
I would have to unlock the bootloader in order to flash a different rom which requires the OEM unlock toggle to be accessible, but it's not.
bizkit_120 said:
I believe what he said is just carrier unlocked not bootloader unlocked, 2 different things..
Click to expand...
Click to collapse
Possibly so... I was waiting for them to respond to my comment to get a definitive answer, but time will tell.
Flash stock firmware doesn't require bootloader to be unlocked.. you can try flash another firmware see if OEM toggle comes up, then unlock it..