Nand flash was not detected what to do. ERROR: NAND Flash was not detected what does it mean

Nand flash was not detected what to do.  ERROR: NAND Flash was not detected what does it mean
Nand flash was not detected what to do. ERROR: NAND Flash was not detected what does it mean

Smartphones based on Android occupy a leading position in the market. However, this does not guarantee their uninterrupted operation. Very often, users are faced with various minor problems, which, fortunately, can be solved fairly quickly. A more complex problem can rightfully be considered the error "ERROR: NAND Flash was not detected". It does not allow the mobile device to log into the OS, and when trying to “reflash” (via the SP Flash Tool, for example), it displays this message.

ERROR: NAND Flash was not detected when flashing via SP Flash Tool

Causes of the NAND Flash was not detected error

NAND Flash is a modern way of storing information in phones, its memory. Therefore, when an error occurs in the memory cells, then the message “NAND Flash was not detected” is displayed. In more detail, it can be translated as "memory was not found."

Most often, this problem occurs on Android devices from Lenovo, and some models with MTK processors.

Memory gets corrupted for many reasons, but there are a few main ones:

  • The most frequent physical failures of the device are noted.
  • Incorrect installation of a new firmware is less common.
  • Outdated databases of programs for flashing.
  • Installed protection from software interventions.

Fix ERROR: NAND Flash was not detected

First of all, you should establish the performance of the smartphone itself. That is, you need to make sure that the memory is fully functional. Perhaps there were moments when the phone got caught in the rain or fell to the floor before. Then the cells could simply stop working correctly.

  • The solution in such a situation is to repair in a service center. You will have to completely change the NAND Flash to a new one. It is not recommended to try to do this at home, it is very Great chance break other installed modules in the phone.

Flashing

When you are convinced that the memory is working properly, you should double-check the installed OS. Perhaps the firmware has defects in its assembly, which lead the smartphone to problems. Sometimes, when reinstalling updates, users did not carefully read the instructions, so something is simply done in the wrong sequence.

  • Find a completely different firmware version. Make sure the source is reliable, that it can be trusted - it is advisable to look for the official websites and forums of the manufacturer. Read the enclosed instructions carefully. After all, sometimes there are options when you should remove the battery before starting to change updates.

Special utilities

The utility for reinstalling service packs can also be broken or outdated. It is because of the outdated collection that modern phones stop working as a result. Everything must be up to par.

  • Download a different version of the program or completely different software with a similar function. There are many such programs: SP Flash Tool, ROM Manager, FastBoot, also many phone manufacturers have proprietary utilities for OS firmware.

It is advisable to try each of the options. You can also try to change the computer and flash the firmware on a different operating system.

Conclusion

We have described the three most common options for the appearance of this problem on Android. Of course, they are general and may not always fix the NAND Flash was not detected error in Android devices, as there may be some nuances for each model. But, of course, you should start checking with them.

Error: NAND Flash was not detected!
1. Download SP flash tool (I think you already have) and Smartphone multiport download tool = http://www.mediafire.com/?1ycvu9ywv7vjnhv.
2. Open and run as admin - SPMultiPortFlashDownloadProject.
3. Click file, open download agent name" and add "MTK_AllInOne_DA.bin".
4. Open factory database and select the .mdb file.
5. Click scatter file - and select the .txt scatter file.
6. Then the "top three boxes (LCD and camera driver) . You click last - ???????? button and unlock it for changing driver parameters.
7. Remember the 1st box for back camera, 2nd box for front camera, 3rd box for display driver.
8.My recommended:
under sensor 1 selectv5647_raw
under sensor 2 select:hi704_yuv
under sensor 3 select:T050UWV014NS or if it doesnt work LM050AMYBO1E
(if doesnt work change again and again)
9. Select high speed and no battery (I think no need to do).
10. Simply close the Tool. then open, SP flash tool
11. Select scatter loading, and load the same "scatter file" , which you previously opened in the "multiport download tool"
12. SELECT "UBOOT" ONLY AND NOT SELECT OTHER ALL PARAMETERS. THEN CLICK DOWNOAD.

Then reboot your phone and check... display is ok ?
If not ok, Then again open smartphone multiport download tool and change the display driver and do the same all things previously.
You have to do repeatly, until, you are getting display normal.
The same thing for camera's working also.

Error: NAND Flash was not detected! 1. Download SP flash tool (I think you already have) and Smartphone multiport download tool = http://www.mediafire.com/?1ycvu9ywv7vjnhv. 2. Open and run as admin - SPMultiPortFlashDownloadProject. 3. Click file, open download agent name" and add "MTK_AllInOne_DA.bin". 4. Open factory database and select the .mdb file. 5. Click scatter file - and select the .txt scatter file. 6. Then the "top three boxes (LCD and camera driver) . You click last - ???????? button and unlock it for changing driver parameters. 7. Remember the 1st box for back camera, 2nd box for front camera, 3rd box for display driver. 8. My recommended: under sensor 1 selectv5647_raw under sensor 2 select:hi704_yuv under sensor 3 select:T050UWV014NS or if it doesnt work LM050AMYBO1E (if doesnt work change again and again) 9. Select high speed and no battery (I think no need to do). 10. Simply close the Tool. then open, SP flash tool 11. Select scatter loading, and load the same "scatter file" , which you previously opened in the "multiport download tool" 12. SELECT "UBOOT" ONLY AND NOT SELECT OTHER ALL PARAMETERS. THEN CLICK DOWNOAD. Then reboot your phone and check... display is ok ? If not ok, Then again open smartphone multiport download tool and change the display driver and do the same all things previously. You have to do repeatly, until, you are getting display normal. The same thing for camera's working also.

Detect language Klingon (pIqaD) Azerbaijani Albanian English Arabic Armenian Afrikaans Basque Belarusian Bengali Bulgarian Bosnian Welsh Hungarian Vietnamese Galician Greek Georgian Gujarati Danish Zulu Hebrew Igbo Yiddish Indonesian Irish Icelandic Spanish Italian Yoruba Kazakh Kannada Catalan Chinese Chinese Traditional Khysha Lati Creole литовский македонский малагасийский малайский малайялам мальтийский маори маратхи монгольский немецкий непали нидерландский норвежский панджаби персидский польский португальский румынский русский себуанский сербский сесото словацкий словенский суахили суданский тагальский тайский тамильский телугу турецкий узбекский украинский урду финский французский хауса хинди хмонг хорватский чева чешский шведский эсперанто эстонский яванский японский Клингонский (pIqaD ) азербайджанский албанский английский арабский армянский африкаанс баскский белорусский бенгальский болгарский боснийский валлийский венгерский вьетнамский галисийский греческий грузинский гуджарати датский зулу иврит игбо идиш индонезийский ирландский исландский испанский итальянский йоруба казахский каннада каталанский китайский китайский традиционный корейский креольский (Гаити) кхмерский лаосский латынь латышский литовский македонский малагасийский малайский малайялам Maltese Maori Marathi Mongolian German Nepali Dutch Norwegian Punjabi Persian Polish Portuguese Romanian Russian Cebuan Serbian Sesotho Slovak Slovenian Swahili Sudanese Tagalog Thai Tamil Telugu Turkish Uzbek Ukrainian Urdu Finnish French Hausa Hindi Hmong Croatian Cheva Czech Swedish Esperanto Estonian Javanese Japanese Target:

Results (Russian) 1:

Error: NAND Flash not detected!1. Download SP flash tool (I think you already have) and smartphone multiport tool download = http://www.mediafire.com/?1ycvu9ywv7vjnhv.2. open and run as administrator - SPMultiPortFlashDownloadProject.3. Select file, open download agent name" and "MTK_AllInOne_DA.bin." -display and camera driver). You click last -??? button and open it to change driver settings.7. Remember, 1 box for the camera on the back, 2 boxes for the front camera, 3 box for the display driver.8. my recommended: under selectv5647_raw sensor 1 under sensor 2 selection: hi704_yuvunder sensor 3 selection: T050UWV014NS or if it doesn't work LM050AMYBO1E(if it doesn't work change again and again)9. Choose high speed and no battery, (I think you don't need to do).10. just close the tool. then open, SP flash tool11. Select Spot Load and download the same "scatter file" that you previously opened in the multiport download12 tool. SELECT "LOADER" ONLY AND DON'T SELECT OTHER ALL OPTIONS. PRESS THE DOWNOAD BUTTON. Then restart your phone and check... is the display OK? you get the display normal. The same for the camera work also.

translating, please wait..

Results (Russian) 2:

Error: NAND Flash was not detected!
1. Download pi flash tools (I think you already have) and smartphone multiport download tool = http://www.mediafire.com/?1ycvu9ywv7vjnhv.
2. Open and run as administrator -. SPMultiPortFlashDownloadProject
3. Click the file open download agent name" and add "MTK_AllInOne_DA.bin.
4. Open factory database and select .mdb file.
5. Click scatter file - and select scatter .txt file.
6. Then the "three boxes" (LCD and camera drivers). You click on the last - ???????? button and unlock it to change the driver settings.
7. Remember the 1st drawer for rear camera, 2nd drawer for front camera, 3rd box for display driver.
8. My Recommended:
with sensor 1 selectv5647_raw
under sensor 2 select: hi704_yuv
under sensor 3 select: T050UWV014NS or if not working LM050AMYBO1E
(unless changes work over and over again)
9. Select high speed and without battery (I think there is no need to do).
10. Just close the facility. then open, pi tools flash
11. Select the load spread, and download the same "scatter file" that previously opened in the "multi-port download tool"
12. SELECT "UBoot" AND NOT Select other all options. Then click DOWNOAD. Then don't restart your phone and check... is the display OK? If not ok, then again open the smartphone multi-port download tool, and change the display driver and do the same all before. You have to do repeatly until you get the display normal. The same for camera work also.

In today's article, we will analyze the NAND Flash was not detected error, which is a rather serious problem for any owner of a smartphone based on an operating system. Android systems. It is not so easy to meet this error: this message pops up during the process of flashing the device, during memory testing.

Usually, when users realize that their smartphone cannot load the operating system normally, they attempt to flash it, and also perform a memory test (or resort to a memory test after installing the firmware). Here they are faced with the error NAND Flash was not detected.

Translated into Russian, the error message translates as "NAND flash memory was not detected." The reasons for this error may be the following:

  • physical damage to the smartphone's NAND memory;
  • unsuccessful attempt to install the firmware;
  • outdated flashing software;
  • Your smartphone is protected against software changes.

Solution for NAND Flash Not Detected Error

There are not so many solutions to this problem: checking NAND memory, checking the firmware being installed, and changing the flashing utility. The first one is almost impossible to do at home, so we recommend that you take your smartphone to the nearest service center and rely on the local guys. Perhaps you have recently dropped your smartphone, as a result of which its memory was damaged.

However, if the memory turned out to be in perfect order, then the problem probably lies in installed version flashing or software with which you are trying to install it. Try to find some other firmware version and install it. Among other things, make sure you follow the instructions that come with the firmware. If this does not help, then use another program to flash your smartphone. Any other will do - use the search engine and advice from other users. With a normally functioning memory, one of these should help you get rid of the NAND Flash was not detected error.

Some of the Android mobile devices may not function properly. When the phone is turned on, the user often sees only a single flash of the screen, and attempts to clear the device cache (wipe cache) do not give the desired result. When you try to flash the system using the appropriate flash utility, the memory test of this program displays the message "ERROR: NAND Flash was not detected". In this article I will tell you what the message ERROR: NAND Flash was not detected means, what causes this error, and how to fix it.

So what is ERROR: NAND Flash was not detected ? First of all, it is worth deciding on the answer to the question “nand flash what is it”.

As you know (or maybe someone is reading about this for the first time), there are now two main methods for the type of flash memory - this is NOR flash and NAND flash, which differ in the method of connecting cells into an array and read-write algorithms.

If the NOR flash works with small memory, then the NAND flash is used where large amounts of memory are needed (tens and hundreds of gigabytes). In particular, NAND flash memory is widely used in modern mobile devices(smartphones and tablets), allowing you to quickly and efficiently solve various digital problems.

Accordingly, when a user encounters a dysfunction of his smartphone and tries to reflash his device (i.e. install another software shell on it) using specialized programs (usually this is one of the versions of the SP Flash Tool program), the test of this program may issue the message ERROR: NAND Flash was not detected, which means “Error. No NAND Flash detected"

Causes of ERROR: NAND Flash was not detected

Causes ERROR: NAND Flash was not detected can be of three main types:

  1. Physical failure of the NAND Flash memory of your smartphone (tablet);
  2. Incorrect versions of the firmware files that are installed on your phone;
  3. An outdated version of the SP Flash Tool itself.

After we have decided on what ERROR: NAND Flash was not detected means and what are the causes of this dysfunction, let's move on to methods for solving it.

How to fix the error ERROR: NAND Flash was not detected

So, how to fix ERROR: NAND Flash was not detected? First of all, it is worth deciding whether your device has been subjected to any physical impact (for example, whether water has entered it). If something like this, nevertheless, happened (and recently), then there is a high probability that the flash memory of your device is damaged, and irretrievably. In this case, the best solution would be to buy a new device.

If nothing like this happened to your device, then try using a different firmware version for your device. Pay attention to the version of the scatter file (scatter), problems are often observed with it, as well as with the preloader that does not correspond to this device. Firmware of some devices (for example, lenovo) must be carried out with the battery removed from the device.

You will have to search for the specific firmware for your particular device on the network yourself.

Also, when answering the question “how to get rid of ERROR: NAND Flash was not detected”, I advise you to use only the latest version of the SP Flash Tool program, since a number of errors that occur during firmware can be caused by outdated version mentioned utility (there have already been precedents).

Conclusion

When answering the question "ERROR: NAND Flash was not detected what does it mean" it should be noted that the most common causes of this error are physical damage flash memory of your device, as well as incorrect versions of the firmware files used for installation on the phone. Try to look for alternative firmware versions, and also use the latest version of the SP Flash Tool utility - this will allow you to effectively fix the error ERROR: NAND Flash was not detected on your device.

In contact with

Possible errors generated by the SP Flash Tool when flashing devices based on MediaTek processors.

(1003) S_COM_PORT_OPEN_FAIL

Port problem.

It can occur if, for example, com-ports are disabled in your BIOS (although in this case the com-port is virtual here, and physical USB, but when you disable it, you simply won’t see the equipment on which the preloader drivers are installed). This is either a problem in the USB cable (changing the cable for firmware helps), or a problem in the USB port of the computer (plugging the cable into another port helps).

(1011) S_NOT_ENOUCH_STORAGE_SPACE

Occurs when the size of any part of the firmware exceeds the size of the space allocated to it (Usually this is a kernel or Recovery block). Perhaps changing the version of the flasher will help.

(1013) S_COM_PORT_OPEN_FAIL

The error is similar in nature and direction to error 1003.

(1022) S_UNSUPPORTED_VER_OF_DA

Need to use more new version SP Flash Tool

(1040) S_UNSUPPORTED_OPERATION

The scatter file does not fit the phone. For example, the name contains 6577, but the phone is actually 6573.

(2005) S_BROM_CMD_STARTCMD_FAIL

On phones with MTD flash, error cases:

1) When Download is selected, the checkbox is not set on the preloader or dsp_bl blocks. You must use the appropriate SPFT version, such as v2.xxx for MT6573 phones, or turn off the DA Download All mode.
2) When Download is selected, a checkbox is set on the preloader or dsp_bl blocks. It is necessary to uncheck these blocks! If these blocks need to be flashed, you must connect the phone in BOOTROM mode.
3) When you select ReadBack, Format or MemoryTest. It is necessary to connect the phone in BOOTROM mode.

(3001) S_DA_EXT_RAM_ERROR

There may be connection problems. Check the cable and/or reconnect the cable to a different port.

(3013) S_DS_SOC_CHECK_FAIL

It is possible that there is no bird on uboot in the SP Flash Tool window. uboot - bootloader operating system+ drivers for initialization of the main equipment (display, processor, GPIO). Or when there are Russian folder names in the path line, for example: C:\Users\Andrey\Desktop\Hata\Firmware\Tablet Firmware\8.31\Surfer 8.31 3G_20130402_V1.03\Surfer 8.31 3G_20130402_V1.03

(3144) S_DA_EMMC_FLASH_NOT_FOUND

In addition to the problem with iron, it can be when the Scatter file does not fit the phone. For example, emmc is present in the name, and the phone is actually with MTD flash.

(3066) S_DA_HANDSET_FAT_INFO_NOT_FOUND

Occurs during automatic formatting, you should try to set the formatting addresses manually.

(3036) S_DA_INVALID_RANGE

The problem is that the SP Flash Tool compares the address of the PMT block on the device's flash with the scatter file before flashing it and finds the difference, which is why it gives an error. The PMT block is created dynamically by the SP Flash Tool from a scatter file.

Solution to the problem:

To delete/overwrite a PMT block with a new one from a scatter file, you must first erase it on the device you want to flash. To do this, in the SP Flash Tool program, click on the “Format” button (we don’t change anything in the window that opens, just click OK), then click “Download” and the SP Flash Tool will write new data about the PMT block and others to the flash again.

(4001) S_FT_DA_NO_RESPONSE

The solution is to change the USB port and move the SP Flash Tool to the root of drive C:

There is also an option that the download agent file does not contain information about CPU / Flash. The solution is to update the flasher version.

The problem may be hardware, for example, with a failed flash memory

(4008) S_FT_DOWNLOAD_FAIL

Solution to the problem:

  • changing the version of the flasher, perhaps even more old version;
  • changing the cable for firmware;
  • It is also possible that the battery has run out during the firmware. Solution: charge the phone and try the firmware again;
  • It may also be worth flashing with the battery inserted.

(4009) S_FT_READBACK_FAIL

In addition to reading errors in the phone itself, the same error occurs with errors in file system computer. For example, there is not enough space for the file, or the file cannot be overwritten because it is blocked (look at the log).

(4032) S_FT_ENABLE_DRAM_FAIL

The error occurs when trying to change the firmware on a device with a processor through the SP Flash Tool program.

Solution to the problem:

After flashing the phone, format the phone through the Format button (do not do this if you have a device on the MT6575 or 6577 processor) in the SP Flash Tool program, then flash the official or from your device firmware and flash all the blocks (check all the boxes). Sometimes you need to remove and reinstall the drivers and do the formatting again, and then reflash if the previous attempt was unsuccessful.

(4050) S_FT_NEED_DOWNLOAD_ALL_FAIL

The block sizes in PMT and in the scatter file do not match. You need to find the line in the BROM_DLL log:

size changed from 0x

Often happens:

Partition 13 (USRDATA) size changed from 0x0000000000000000 to 0x000000000B620000

There is no size in the scatter file, so SPFT itself calculates the size of USRDATA based on the size of the flash and the space under BMTPOOL. And in the PMT tables inside the body, the size of the blocks is registered, and in this case, someone or something wrote zero there.

To solve this case, you can rename the scatter USRDATA to __NODL_USRDATA ... But here error 8038 may occur due to the difference in wink.gif names. In the general case, this error is cured by loading all the blocks (sometimes one usrdata is enough), after which the size in PMT should change to the correct one.

(5002) S_INVALID_DA_FILE

When setting up the SP Flash Tool download agent, you need to select the flash driver that comes with this version. Selecting other agents gives such an error.

(5054) S_DL_GET_DRAM_SETTINGS_FAIL

If, with a full collection through the SP Flash Tool, and there is no way to install new firmware, and also fails to reset again.

Solution to the problem:

Reinstall drivers again.

(5066) S_DL_PC_BL_INVALID_GFH_FILE_INFOR

Wrong files. For example, we chose a scatter file from a folder with files not yet prepared for FT. You need to select a scatter file from the folder prepared for FT files.

(5069) S_DL_PMT_ERR_NO_SPACE

Hardware problem with flash memory

The error occurs:

If you do Format, then the error S_PART_NO_VALID_TABLE (1037) will come out and it says that you need to do Download to create a partition table.
Firmware Upgrade does not allow to do -> again due to error 1037
You can download only PRELOADER. Loading any other partition gives an error (5069) S_DL_PMT_ERR_NO_SPACE.
It does not depend on the version of the scatter file.
FAT also does not depend on the size of the FAT partition.
You can make Manual Format - gives, but within UA Size. After that, an attempt to fill in any section again ends with error 5069.

Most likely this is a feature of flash memory - there are cases when neither formatting nor low-level formatting gives no effect.

(6124) S_SECURITY_INVALID_PROJECT

Solution to the problem:

Choose: Options -> DA Download All -> Speed ​​-> Full Speed ​​(when High Speed ​​mode is selected, an error (6124) appears on some PCs).

(8038) SP FLASH TOOL ERROR

Occurs if the names or addresses of the blocks in the scatter file differ from the table inside the phone (PMT). You need to look at SP_FLASH_TOOL.log and look for the NOT MATCH line in it.

NandLayoutParameter::CompareIsNandLayoutMatched(): NOT MATCH: load item key(CUSTPACK2), value(0x3444000), target item key(CUSTPACK), value(0x3444000)

It is necessary to replace the name CUSTPACK2 with CUSTPACK in the scatter. If there are several differences, then this error will occur until the scatter after the corrections made becomes identical to PMT. You can immediately fix everything if you compare the tables that are in the log just above the NOT MATCH line.

The first one is from the scatter file, the second one is from the phone's PMT. It is necessary that all block names in the scatter be the same as in the second table.

(8045) SP FLASH TOOL ERROR

The error is similar to 8038, but editing the scatter file did not solve the problem.

Solution to the problem:

1) Firmware firmware through the programmer.
2) In rare cases, the firmware helped through the DOWNLOAD button with all the checkboxes set.

(8200) SP FLASH TOOL ERROR

Occurs if you are trying to flash a device on one platform with firmware from another.

Solution to the problem:

In other cases - changing the version of the flasher.

Invalid ROM or PMT address

If the hardware of the device is known to be in order, it is necessary to format the memory, and then flash the firmware in the standard order.