Skip to content

Odin NAND Erase Guide | Re-partition Samsung Devices

Odin is mostly used by users to flash firmware binaries and custom recovery. However, Odin can also be used to re-partition, flash lock, decompress data, flash user data, and erase all data on Samsung Galaxy devices. You can even remove FRP (Factory Reset Protection) on Samsung and perform some very complicated tasks. In this tutorial, explain what Odin NAND Erase or NAND Erase All is, and how you can use it to erase all data and re-partition a Samsung phone or Galaxy Tab.

Actually, Odin is not just a simple flash tool for flashing the stock firmware. It is meant to be used only in the Samsung service centers by Samsung engineers to fix non-functional Galaxy devices. Do you know that Odin can flash or install firmware on more than 60 Galaxy devices at the same time?

Anyway, let’s keep our focus on Odin’s ‘Nand Erase’ option. I know a lad who enabled Nand Erase in Odin while installing the firmware on his Galaxy S9 just out of curiosity. You know what, he ended up with a bricked phone. Nand Erase had wiped all partitions on his S9 including EFS, boot, recovery, kernel & system partitions. Fortunately, he was able to fix his phone by following one of my tutorials published on another website.

NAND Erase Meaning in Odin

NAND and NOR are actually 2 main types of flash memory, that are related to computers and it stores the BIOS settings to the ROM of a computer. Since Android devices don’t have a BIOS, flash memory, or NAND relates to the bootloader and OS kernel that work together to boot Android devices into the system.

NAND is neither an acronym of a term used to express a boolean nor logic gate “NOT AND“. Being a non-volatile memory, it keeps the essential OS data even when your Android smartphone is turned off.

Thus, when it comes to Android, NAND memory stores the following partitions of your Android device.

  • boot
  • kernel
  • recovery
  • system
  • data
  • cache
  • .android_secure
  • datadata
  • wimax
  • efs
  • preload

When you create a nandroid backup, an exact mirror of all the above partitions and directory structures are created. Similarly, when you perform a NAND erase in Odin, you wipe all the partitions on your Samsung Galaxy device. In simple words, you’ll end up with a device without an operating system. A sheer piece of hardware is all you get as the boot, kernel, system recovery, data, EFS, etc. have already been wiped. Obviously, your Samsung phone or tablet won’t boot up at all except to the Odin or Download Mode.

You cannot fix a Samsung device after an unintentional NAND erase action by simply flashing the stock firmware. Since NAND erase wipes all existing partitions from the device’s storage, you’ll have to re-partition your device in Odin with the help of an appropriate PIT (Partition Information Table) file.

What is Re-partition in Odin?

As I already mentioned above, the flash or NAND memory on Android devices is divided into partitions and block structures. These partitions are essential to the proper functioning of a device. It’s the PIT file that tells Odin how much space to allocate to boot, kernel, system recovery, data, and EFS. Not just that, it is also responsible for the location and path of these partition blocks on the internal storage.

The Re-partition option in Odin is not meant to be used during a normal firmware flash. If you have to install firmware, just add the BL, AP, CP, and CSC files to Odin and do not change the default settings.

The PIT file determines the structure, location, and size of specific partitions. Since a NAND erase wipes all partitions, the only way to re-partition your device using is to flash a PIT file that is strictly for your Samsung Galaxy device model and storage capacity. Flashing a wrong PIT may result in a semi-bricked device. Moreover, if you flash the PIT file of a 128GB device model on a 256GB model, your phone may be configured to show only 128GB as available storage. I personally experienced this issue on my Nexus 6P.

You must not enable the Re-Partition option in Odin unless you got the correct PIT file. When you click the Pit tab in Odin, it will show you a warning.

pit warning in odin

Odin warning on PIT selection

It means that you don’t need to flash a PIT file in normal circumstances. In certain situations, when your Samsung device’s partition table is corrupted, flashing the PIT manually can be the only way to fix the issue. If you find the IMEI number of your Samsung Galaxy phone missing, it might be due to a corrupt EFS partition. You can restore the lost IMEI by flashing the Partition Information Table. You can follow these steps to flash only the PIT file in Odin.

  1. Boot your device into the Download mode.
  2. Launch Odin and connect your device to the PC.
  3. Add the BL, AP, CP, and CSC binaries to the corresponding sections.
  4. Select the Re-Partition option.
  5. Click the PIT tab and add the correct PIT file for your device model.
  6. Hit the Start button on Odin and wait for the installation to be finished.

Please keep in mind that the re-partitioning procedure will wipe your phone’s data so take a backup before you proceed.

Steps to Re-Partition and Nand Erase using Odin

Finally, let’s see how we can perform a NAND erase in Odin and re-partition a Samsung device by erasing user data and all partitions. You can also fix your phone in case you accidentally or unknowingly erased all data. The steps described below will also help you restore the lost IMEI on your Galaxy smartphone.

Below are the steps to flash stock firmware on Samsung devices with the Nand Erase and Re-partition option enabled.

Preparations and downloads

There are a few things that you must do before you jump into the action.

    1. Download the appropriate firmware for your smartphone or Galaxy Tab. Here are the 6 best Samsung firmware download tools and websites from which you can download the BL, AP, CP, and CSC files for your device. When the firmware is downloaded, extract the ZIP file.
    2. Install the Samsung USB driver on your PC.
    3. Download the latest Odin tool and extract the downloaded zip on your desktop.
    4. Enable USB debugging from the Developer options under device settings. Skip this step if your device is not able to boot up at all.
    5. You’ll also need the correct PIT file for your Samsung device. You can easily extract the PIT from the CSC binary. Just add ‘.ZIP’ extension after .tar.md5 and unzip it. You will find the PIT for your phone inside the extracted folder.

      extract pit from csc on samsung pit extract

      Samsung PIT file

Instructions to Flash Firmware in Odin

Note: Please be warned that performing a firmware flash using the method described below will wipe your phone’s data. It’s strongly recommended to take a backup of your phone’s data beforehand.

  1. Turn off your Samsung Galaxy device and boot it into the Android Recovery Mode. The method and key combination to get into the recovery mode on Samsung Galaxy devices differ from device to device. You have to press and hold a certain hardware key combination for 5-7 seconds. There is an easier way that involves using ADB commands and works on all Android devices. However, you need to set up Android SDK Platform-tools first. I’ll mention all possible methods below:
    • Devices with Home button: Home + Volume Up + Power buttons
    • Galaxy devices with Bixby key: Bixby + Volume Up + Power keys
    • Samsung devices with no Bixby key: Volume Up + Volume Down +Power buttons (additionally, you have to hold the Volume Down key when the Samsung logo appears on the screen).
    • Galaxy Tabs: Volume Down + Power buttons (on some models, you need to press the Volume Up key instead).
    • All Android devices: Make sure your device is turned on. Connect your device to your computer via a USB cable. Unzip and open the platform-tools-latest folder and launch the command prompt window inside this folder window. Then execute the ‘adb devices‘ and ‘adb reboot recovery‘ commands one after another. Your Samsung device will reboot into recovery mode.

      samsung recovery mode

      Android Recovery menu

  2. Once you see the recovery menu on the screen, highlight the Wipe data/factory reset option using the Volume Down button and select it by pressing the Power key. When you see the warning screen, select ‘yes’ to confirm and press the Power key to wipe your device.
  3. When your phone boots up, go to Settings and enable USB debugging from the Developer options menu. This is not a compulsory requirement though.
  4. Boot your Samsung device into the Download Mode. You can use one of the key-combos mentioned below. You have to press and hold the hardware keys for 2-3 seconds. Alternatively, you can use the ‘adb reboot bootloader‘ command to get into the Download Mode.
    • Devices with Home button: Home + Volume Down + Power buttons
    • Galaxy devices with Bixby key: Bixby + Volume Down + Power keys
    • Samsung devices with no Bixby key: Volume Down + Volume Up + Power buttons.
    • Galaxy Tabs: Volume Up + Power buttons (on some models, you may need to press the Volume Down key instead).
    • Using ADB Command: Connect your device to your computer. Open the platform-tools-latest folder and launch the command prompt window by pressing Shift key+ right-click and selecting the Open PowerShell window here option inside this folder window. Then execute the ‘adb devices’ and ‘adb reboot bootloader’ commands. Doing so will reboot your Samsung phone or tablet into the Download Mode.

      adb reboot bootloader

      adb reboot bootloader command

  5. Open the Odin folder and launch the Odin3_v3.xx.exe.
  6. Now, connect your Samsung device to your Windows PC using the USB cable that came with your device. When Odin detects your Samsung device, the ID:COM port will be highlighted. You’ll also see ‘Added!‘ message in the log box to indicate a successful connection.
  7. Click the BL button on Odin, navigate to the firmware folder, and add the firmware binary that starts with ‘BL‘ in its name. Then click the AP, CP, and CSC buttons and add appropriate binaries to them as well.
  8. Having added the firmware binaries, click the Options tab in Odin and select Nand Erase and Re-Partition.
  9. Then click the Pit tab in Odin and select OK when you see the warning pop-up. Click the PIT button now, navigate to the PIT file and add it.

    odin re-partition

    Re-partition and PIT option in Odin

  10. Make sure your final Odin setup looks like the following screenshot.

    nand erase and repartition in odin

    Odin setup for Nand erase and re-partition

  11. If everything looks fine to you, it’s time now to make Odin do its job. Click the Start button.
  12. Doing so will initiate the firmware installation. You can check the progress of Odin Nand erase, re-partitioning, and firmware installation in the log box. You’ll also see the “Erasing NAND” message in Odin’s log.
  13. All you need to do now is to take a short rest after your hard work and wait for the firmware installation to finish.
  14. The whole process should take around 5-7 minutes and after that, you’ll get ‘PASS!‘ message in Odin and your Samsung device will reboot.

That’s it! You can now disconnect the USB cable and close the Odin window. You have successfully flashed the stock firmware on your Samsung device with Odin NAND erase and re-partition enabled. If you need help with anything while following this tutorial, don’t forget to leave a comment.

Read Next: List of Useful ADB Shell Commands

58 thoughts on “Odin NAND Erase Guide | Re-partition Samsung Devices”

  1. Hi tech guru
    I need help with a samsung J5 Prime SM-G570F
    Background:
    Although not network locked, the phone came with carrier bloatware and start-up screen.
    Phone worked 100%. Upgraded to a new phone and the J5 was left for about 6 months in a drawer
    I now need the phone for my dad
    Charged it up and switching it on I got a red line saying custom binary blocked by FRP lock.
    Searched through a lot of forums and most suggestions have got to do with lost google credentials – I cant try any of the options because the phone cant boot (not even by holding down volume down + pwr).
    I have the google credentials that was used on the phone.
    So I tried flashing with ODIN. Problem was selecting the correct csc code as there is a couple for South Africa.
    Not sure if this is where my problem started as I first used XFA and later discovered the carrier version for the phone is XFV
    Your guide is complete and I followed all the steps
    ODIN passes the flash but upon reboot the screen is just black
    ODIN does show the device as added even with the black screen
    No combination of options work – only the download option
    My question is – FRP lock: ON still shows in ODIN Mode.
    Is that what is causing the flash to pass but it does not change anything?
    And how can I get the FRP lock off?
    If I can get the phone boot I can sign in with my google account that was on the phone.

    Can you please advise what to do?
    Thank you
    Arlo

  2. Hello

    I have followed every step for flashing the rom with PIT file but iam stuck at repartition failed . I have used the PIT inside the rom, check the nand erase , repartition ,autoreboot , freset time. Do you have any advise on this?

    below is the result of odin ver 13.4 for your reference

    Thanks hope you can help

    Added!!
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Odin engine v(ID:3.1401)..
    File analysis..
    Total Binary size: 2237 M
    SetupConnection..
    Initialzation..
    Set PIT file..
    DO NOT TURN OFF TARGET!!

    Re-Partition operation failed.
    All threads completed. (succeed 0 / failed 1)
    Odin engine v(ID:3.1401)..
    File analysis..
    Total Binary size: 2237 M
    SetupConnection..

    1. Hi Mark, Which device model do you have and which firmware version are you trying to flash? Also, what is the current version of your OS and firmware?

  3. My samsung m30s got bricked while i was using it normally. It would not restart at all and is stuck on the boot-up logo. I have flashed without NAND erase and with NAND erase multiple times successfully (ODIN shows PASS). The issue is still not resolved. It is still stuck on the same logo. What could be the problem? The battery was at 100% as well. My ODIN log is below
    Added!!
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Enter CS for MD5..
    Check MD5.. Do not unplug the cable..
    Please wait..
    Checking MD5 finished Sucessfully..
    Leave CS..
    Removed!!
    Added!!
    Odin engine v(ID:3.1401)..
    File analysis..
    Total Binary size: 5955 M
    SetupConnection..
    Initialzation..
    Set PIT file..
    DO NOT TURN OFF TARGET!!
    Erase…
    ERASE_SECTOR: 1638144
    Get PIT for mapping..
    ERASE_OK
    Firmware update start..
    NAND Write Start!!
    SingleDownload.
    sboot.bin
    param.bin
    up_param.bin
    cm.bin
    keystorage.bin
    uh.bin
    boot.img
    recovery.img
    dt.img
    dtbo.img
    system.img
    vendor.img
    userdata.img
    vbmeta.img
    modem.bin
    modem_debug.bin
    cache.img
    omr.img
    product.img
    RQT_CLOSE !!
    RES OK !!
    Remain Port …. 0
    All threads completed. (succeed 1 / failed 0)
    Removed!!

  4. Hi tech guru
    I need help with a Samsung T725 Tablet that I inherited.
    All attempts to remove FRP failed:
    Flashing a Combination File with ODIN and a Pit File was refused with an error obout missing permission (abl) file.
    Flasing the stock firmware on my Samsung device with Odin NAND erase and re-partition enabled worked, but after restert the FRP Lock is already present.
    I used the firmware XSG-T725XXU1ASD2-20190411102740.zip and the combination file [up_vnROM.net]_COMBINATION_FAC_FA90_T725XXU1ATD2.rar.

    Thanks in advance for your help
    Juergen

  5. Hi there RAKESH,
    I just wanted to thank you for your great work here. I read 11 tutorials, all helpful and so clear and easy to apply. I have solved my problem via Nand firmware installation, and the device is perfectly working.
    Have a great day…

    P.S. This site is far beyond expectations.

    1. Hi Behrang, it’s always pleasant to be of any help to the readers of Technastic.com. Which Samsung phone do you have?

      Please follow us on FB and Twitter to support us. Thanks!

  6. Hello,

    Thank you very much for this useful tutorial, I´ve thinking since some time ago to flash a differente variant firmware of my device which is a Samsung A7 2018 SM-750FN (European), with a Samsung A7 2018 SM-750GN (Indonesia,Thailand, Vietnam) , just because of the native call recoding feature, which it is not available in the SM-750FN, but yes in the SM-750GN, because of the distribution region of device.

    Both are the same hardware and specifications (same model in fact) but for the GN variant which have a couple more gsm bands, apart from the same that FN has.

    Do you think I can flash it, following the Re Partition and PIT tutorial you share here? I had extracted and compared both firmwares PIT files and thy are exactly the same.

    I tryed to flash it before, using Odin, just in normal mode, only Auto Reboot and F Reset Time, activated, but it comes out with an error some like “Unable to Re Partition”.
    Both firmwares are same binary number, 5.

    I will appreciate any advice and help.

    Thank you very much in advance.

    1. Hi Raul, I won’t suggest flashing firmware that’s not meant for you phone model. However, the band erase trick could work in this case. Try finding an open firmware for the European region that might have call recording support.

      1. Thank you for your answer, There is no single european software with call recording feature , at least that I know , it is eliminated recording some contries regulaciones, not my country but not featured anyway. If you know a country firmware which it is implemented, I will try to flash it , I ve already tryed UK, FRANCE, GERMANY, and a few more, but … nothing.

        Thank you very much , I try with the Thailand variant and update resulta.

  7. I’m missing one important bit of info for Newbies like me with older devices: this procedure requires Repair Firmware packages! The standard firmware Frija downloads for my Galaxy Tab S2 is a single file archive for flashing “AP” only, which is all I am familiar with so far from previous Samsung ROM installations.

    That said, the steps are straight forward, let’s hope for the best 😉

    A word about the differences between Samsung 4 files/ 5 files (Repair firmware), Combination firmware, and “regular” firmware old & new would be appreciated – Google isn’t what it once was, unfortunately.

  8. On second thought… DO I need to enable USB debugging? Especially after a factory reset?

    • Odin requires USB debugging
    Odin does not require USB debugging to be enabled on your Samsung Galaxy device. USB debugging only plays its role while the device is booted into the OS. So, USB debugging is not at all related to the Odin tool and isn’t involved at all in the firmware flashing process.

    Which makes sense, how would you enable USB debugging on a bricked device?
    In any case, it doesn’t sound like a good idea to use Odin and adb at the same time…

    DO I have to do a factory reset… if I’m going to wipe ALL partitions in the next step? (and noob question, how does this work without losing access to download mode/recovery? )

  9. I just flashed my Galaxy Tab S2 successfully, albeit the reason to do so persists – graphics glichtes & force-closing apps. Either NAND Erase doesn’t rewrite ALL partitions, or I’ve got a hardware problem.

    Odin recreated sboot.bin, param.bin, boot.img, recovery.img, system.img, userdata.img and modem.bin, in that order according to the log; seven files total, and seven files/images were also in the old-style firmware archive I downloaded with Frija, though with different names: like cache.img and hidden.img (instead of param.bin und userdata.img). I’m still confused about these different firmware packages – the Frija download was ~ 1,37 GB zipped, the Firmware 4 file whose contents I flashed is ~ 1,73 GB; both are OXA (European) versions and exactly the same PDA/CSC/Phone versions. What accounts for the difference?

    I was careful to uncheck “Auto Reboot” in case Odin failed. I’ve never had that happen before, but does Odin auto-reboot only after SUCCESS?
    Because if Download mode/Recovery reside in partitions that get overwritten, they’re basically running from RAM and I wouldn’t want to lose the chance for a second try – call me paranoid, because the smaller images get written very quickly. (Odin keeps the device connected until you disconnect/hit Exit or I guess, reboot – unless it’s some sort of soft reboot. I don’t remember, I’m not doing this stuff often enough ;))

  10. please bro help im in huge trouble suddenly i did nanderase to recover imei now the phone wont boot it bootloops i did all the steps below but no result if you want to help me please you are welcome

  11. Bro i do nand erase . But when i flash the firmware it always stuck at bootloop. Rarely enters to recovery and system. How to fix this ?. By doing this will revind my phone?. Pls bro Reply Me Fast.

    1. Hi, a successful Nand-erase can fix several issues on Samsung phones including oot loop. Follow the guide carefully. Good luck!

    2. I just did that to a Galaxy A71, selected both Nand Erase and Re-Partition (selecting the PIT file too), and everything went well. It didn’t lose IMEI or anything related to hardware ID. The first time it stuck in a bootloop, then the second time (same process) it worked.

  12. Hello Rakesh,

    I have a Galaxy Note FE that suddenly died. I tried wipe cache, factory reset, all from the recovery menu and the phone still freezes up. I then tried your tutorial and followed everything. It looked to be successful with Odin showing the PASS message. My phone reboots and shows the Samsung Note FE logo. It then shows the Samsung logo and it just stops there. It does not go to the home screen or anything. Just the Samsung logo and a blue pulsating indicator light. I did some more reading and it seems this may be a case of bad emmc chip. Is help still possible? Thank you!

    1. Hi Marc, if the Nand Erase didn’t help fix your Samsung Galaxy Note FE, it might be due to some issue with the EMMC chip. You should take it phone to the service center.

      Can you please elaborate on how the problem began?

      1. Hi Rakesh, the problem started when I was updating apps through Google Play and watched a video saved on the microsd card. I put the phone to sleep and when I turned on the screen the phone just froze. So I simulate a battery pull with volume down+power button. When it turns back on I open Google Play again to see if the apps finished updating.

        The phone then freezes again. I thought the microsd got corrupted but turns out it was just fine. I repeat the battery pull and it just freezes again after getting to the home screen. From that, I tried booting to safe mode, wiping cache, and even factory resetting, all from the recovery mode. But even getting to the recovery mode is not easy as the phone would freeze while the phone is booting up or while at the recovery mode. It did show hope after the first factory reset as it was able to boot up and get to google account setup but it just froze all over again. Since then I was not able to get to the home screen. Just the Note FE logo and it goes on a boot loop after that.

        And that brings me to your tutorial. I have tried the steps here and it looks to have succeeded but after the reboot and the “ERASING” part it seems to not get past the 32% and would just reboot to Note FE logo then the Samsung logo and then that’s when it would freeze with the blue pulsating notification led.

          1. Hi Rakesh, if normal flash means re-partition and nand erase is not checked then yes, I tried it once but it did not help. The firmware I flashed I got it from sammobile.com. It’s android pie and the latest patch for note FE released April 2021.

  13. I have tried both the combination firmware, which fails as it stays on “analysing file” on Odin and tried the NAND erase for a Galaxy Note 9. It STILL has FRP lock after flashing. Any suggestions?

  14. Hi RAKESH
    Recent Death of family member
    Upon thier death left with
    Galaxy S4 & Galaxy Note 9
    Password protected can these be bypassed without loosing data
    Hopefully so as would like to retrive pictures ect.
    Many thanks in advance for any help you can possibly give.

    1. Hi Alan,

      If you chose to perform a Nan erase, it’ll wipe all data on the device. Since the phones are password protected, youan unlock it only if you have the PIN, or via Find My Phone service using Samsung and Google account. If you have access to your family member’s email accounts, you can try it. Usually, people remain logged in or use auto-fill service on their PC. If you got access to that, you should give it a shot.

      Also, you can hire some paid data recovery service like (drivesaversdatarecovery dot com) to do the job for you.

  15. Hi,

    Thank you for your well explained tutorial of how everything works, really helped me grasp the concepts. I applied this to a T550 tablet and was able to remove FRP.

    I appreciate your efforts here on this site, please keep up the good work!

    Thanks.

    1. Hello….so I have a T500 tablet and am having a hard time removing FRP….could you point me in the right direction, or simply explain, how you used Odin to do the job?

      Thanks!

  16. Hi Rakesh,

    first of all, thank you for your great tutorials. I found them when I wanted to completely reinstall Android on my Galaxy Note 9. A few weeks ago, my phone started to have only 2G-Connection so I brought it to a Samsung Service Center and they “reinstalled the software completely” (about 60€, since no warranty anymore).

    After that I had 4G-Connection again but only for about 7 days. After that, the same problem suddenly occured again… only 2G. So I tried to do this “reinstall of software completely” on my own using Odin and your tutorials (also with Nand-Erase and re-partition) and succeeded (thanks to you!), but still get only 2G-Connection. Thus the Samsung Service Center did maybe something different than me.

    So my question to you is this: Do you know what the Samsung Service Center possibly could have done different with my phone (they wont tell me, unfortunately)? Are there other techniques or more complete ways to reinstall the software? Since this is obviously no hardware error but software, it is very frustrating and I hope I can fix it with some sort of reinstall. Do you have maybe some ideas?

    Thanks in advance!!!

  17. Hi Rakesh,

    a few weeks ago, I started to only get 2G-connection on my Galaxy Note 9. Samsung Service Center completely removed the software and installed a fresh one and I got 4G-connection again (no warranty, about 60€).
    After a few days, the same problem came up again (only 2G-connection). I tried your tutorials to flash the firmware (also with Nand erase and re-partition) after performing the flashing, I still got only 2G-connection.
    So I was wondering what the Samsung Service Center did different than me. Do you have any idea what I could try do to (they wont tell me what they did exactly).

    Thanks in advance!

  18. Hi Rakesh,

    a few weeks ago, I started to only get 2G-connection on my Galaxy Note 9. Samsung Service Center completely removed the software and installed a fresh one and I got 4G-connection again (no warranty, about 60€).
    After a few days, the same problem came up again (only 2G-connection). I tried your tutorials to flash the firmware (also with Nand erase and re-partition) after performing the flashing, I still got only 2G-connection.
    So I was wondering what the Samsung Service Center did different than me. Do you have any idea what I could try do to (they wont tell me what they did exactly).

    Thanks in advance!

  19. I have samsung s9 plus SM-G965F which was used for O2 network in United Kingdom. I inserted BSNL SIM in India and it said network locked. Used odin to install Indian firmware. Still same message. Tried to unlock using unlock code got from browsing the internet. Now the phone is bricked with a message at the top of the screen saying WARNING:CMDLINE parameter modified. Please help. Thanks in advance

    1. Hi Madhu,

      You are facing this issue because you 7sed a wrong unlock code. You should have avoided flashing firmware on a carrier-locked device.

      Anyway, are you able to get into the download mode on your Galaxy SO+?

      1. Yes. I have installed G965FXXSHFUJ2 SW VER XEU/XEU ANDROID SEcurity patch 1 November 2021. But Indian SIM still not working. asking for muk ?
        who will give unlock code? Samsung or network operator

        1. Unlock code can be provided by the network operator. Alternatively, there are several online 3rd-party network unlocking services that can provide you a code a little cheaper.

    2. Hi Rakhesh, thanks for the amazing tutorial. I have a S10+ mobile which has green tint since a while. On some instances like always on display it doesnt show green tint, but as soon as i unlock the phone green tint appears. This makes be believe its a software issue than hardware and hence i want to install older Android 9 or 10 instead of 11. With hope that the green tint issue will be non existent in old OS.
      I understand that bootloader binary number needs to match if i want to flash through odin. The latest binary number doesnt match Android 9 firmware. 2 questions:
      1. Is it possible to downgrade a firmware with different bootloader/binary number?
      2. If yes, to force install such a firmware normally Odin gives error that binary on device is new so cant proceed. Will using nand erase and re partition and flashing with older Android with older bootloader binary number work?

      Thank you.

    3. Hello Rakesh
      If I repartition my S9 using the PIT file will this allow me to roll back my firmware from Android 10 to Android 8?

      1. Hi Stephen,
        You can’t roll back to the firmware version of your choice anytime. Certain firmware versions are locked so that you can’t downgrade. If you still want to try, you can go ahead. If you are unable to roll back to Android 8 from 10, you can re-install Android 10 using the method described here.

        1. Thanks, Rakesh
          When your repartition does that not completely clear all firmware and software within the phone as if a brand new factory build without any programing installed or are there secure untouched areas that store for example the IMEI?

          1. IMEI data is stored on a different level. It might get corrupted but not removed via this method. The EFS partition contains the IMEI but it is usually untouched. All other data is wiped after performing a Nand Erase.

            1. So would I be correct in saying there is another secure level within the phone that prevents Firmware rollback that is untouched when you do a repartition?

              1. Well, technically, one should be able to do a rollback but I haven’t tried it recently (until 3 years ago with my S9). That’s why I said you should try it as it’s safe as long as you can download the latest firmware and know how to install it using Odin.

      2. Hello Rakesh
        Im doing everything right but I cant pass the Nand Erase section its fails everytime when I pressing start. Without choose the option nand erase there is no problem but I must the erase the partitions I cant even enter recovery in my phone…How to fix Nand Erase problem? is there any write protection or something? my phone is galaxy grand neo GT-I9060

        Picture of the Fail Status in Odin, also I tried new and old versions of the Odin but the problem is persist…

        https://imgur.com/a/3KhFL1T

          1. Hello I tried all modified versions and 3.06 version but still can’t do Nand Erase to this phone… it fails every time like there’s something blocking me but i have no idea…Do I need to unlock bootloader or something else like in other brands?

      3. Hello friend,
        after I have done all the manual I am still having an error
        Re-Partition operation failed.
        Is there anything else that can be done?
        Thank you and good day.

      Leave a Reply

      Your email address will not be published.

      This site uses Akismet to reduce spam. Learn how your comment data is processed.