Database Info

[Q] * [Discussion : Inputs from Android Experts] *Topic: BOOTLOOP / NAND WRITE FAIL*

Hello XDA community,
I am proposing this thread as a common knowledge base on
Rampant Nand Write Fail issue.
Having searched through numerous forums here & on Internet, i concluded no working solution on it.
Many have accepted fate of their devices - Dead .. and put them in storerooms.
For rest frantic people out there eating into *help me* lines , they will soon accept the same.
So, the purpose of this thread is to Analyze why did it happen, than to expect a Resurrection .
Having been a victim of NAND WRITE Fail, here are my Final thoughts :
Characteristics of problem :
1. BootLoop
2. Typical of Kitkat OS
3. Download mode available
4. Recovery mode unavailable
- flashes open-stomach android logo for split second , BootLoop again.
5. Happened in devices that initially did not come with KNOX,
but were upgraded to Kitkat with KNOX.
Observations :
1. Changing System / USB 2.0 port - did not solve.
2. Changing versions of ODIN - did not solve
3. Re-flashing of Stock 4.4.2 ROM - Failed [NAND Write Fail]
4. Flashing of older Stock ROMs - Failed [NAND Write Fail]
- also gathered info : You can not downgrade since Kitkat Bootloader wont allow.
5. With ONLY Download mode accessible,
- Not a single tar was successfully Flashed onto device.
- All recovery tar files fail to flash [NAND Write Fail]
Conclusion to Discuss with Experts :
1. Write to NAND memory is being blocked by something [Boot Loader ? ]
2. NAND memory itself is damaged.
- Unlikely seeing the wide scale of this problem.
3. Why is Download mode accessible,
and what causes a flash-second opening into Recovery mode... then Reboot.
4. What role has KNOX to play here [Trying to root tampered with WHAT PART OF KNOX Rule] ?
5. What do we know about bootloader in this context ?

thanks for opening this thread.
I have the same problem with my M480W.
However I am able to enter recovery mode, yet nothing works ...
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I havent yet tried to repartition, cause I cannot find the correct pit file for my model.

Megatronicalite said:
thanks for opening this thread.
I have the same problem with my M480W.
However I am able to enter recovery mode, yet nothing works ...
Code:
E: failed to mount / system (Invalid argument)
can't mount '/system' (invalid argument)
E: failed to mount / system (Invalid argument)
E: File Open error '/cache/recovery/log'
E: can't open /cache/recovery/log
E: File Open error '/cache/recovery/last_log'
E: can't open /cache/recovery/last_log
E: File Open error '/cache/recovery/last_install;'
E: can't open /cache/recovery/last_install
I havent yet tried to repartition, cause I cannot find the correct pit file for my model.
Click to expand...
Click to collapse
PIT Has not solved this problem on any device i know...
Per my knowledge from various posts, they all ended up finally making it a 'Paper Weight' .

Has anyone found a solution?

[Q] Xoom TWRP/Wingray 4.4.4 no longer boots, won't mount storage

My rooted Xoom seems to be unable to read the internal storage. Does anyone know if there is a way to recover?
Here are the details:
I have been running Wingray on my Xoom for about a year, and everything had been working fine until the last couple of weeks.
It would frequently not wake up after it went to sleep, and I would have to restart with the Power-Vol+ combination.
Yesterday, it finally would not load android at all. It displayed the animated graphic indefinitely.
I booted and started TWRP, which loads successfully. It prompts me to enter my password. Since I didn't use one, I cancel this.
When I look at the log, I see:
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
...
E:Unable to set emmc bootloader message.
I then tried to format.
After typing 'yes', the log shows:
Formatting data using make_ext4fs...
E:Unable to wipe '/data'
E:Unable to format to remove encryption.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount internal storage
When I try to mount storage, I see:
sdcard (12772MB)
Internal Storage (0MB)
My PC does not recognize when it is powered on while connected.
Does anyone have any ideas whether or not I can get this functional again? If so, any suggestions would be appreciated.

[Q] My Internal sdcard is corrupted! Please Help!

I Think my Internal sdcard is corrupted!
Please Help! Reflashing android won't work. I think the partition is corrupted!
Device: Google Nexus 5
Original OS: Android 5.1.0_r1 (LMY47D)
Recovery: TWRP 2.8.6.0
One day I turned my phone off, and later i decided to go into recovery. I believe I went inside Advanced Options and clicked "Fix Permissions." Then I proceeded to reboot. I was busy at the time, so when I remembered about my phone, I saw that it was still booting. It had been at least 30 minutes so I knew it was in a bootloop. I decided to go back into recovery and reflash the system.img onto it. No luck. I realized I had to try flashing the entire Nexus image (using the flash-all.bat). The phone would still not turn on. I tried flashing different versions of android, and here are my findings:
Android 5.1.0_r3, 5.1.0_r1, 5.0.1: all cause my phone to not be able to boot up (stuck on the 4 color flying animation)
Android 4.4.4, CyanogenMod (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip): Allow my phone to boot up.
However, after I found that I could boot onto Android 4.4.4 and CyanogenMod, I realized that I could not get access to the sdcard!
Here are my findings:
When I go to the phone's root folder, I see a FILE called "sdcard"
When I go to \storage, I see a FILE called sdcard0
When I open camera, the app crashes (possibly because it stores pictures on the sdcard).
I tried to delete these files when I had root access with CyanogenMod but the file manager said "can't delete file." When I am in recovery mode (TWRP) however, I can see the sdcard folder and the contents. Just through every system boot, the sdcard is inaccessible.
After I realized that the problem wasn't due to the data on my phone (after flashing many system images), I realized my data partition might be corrupted. Then I went to this site and followed the directions: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
The e2fsck command didn't do anything as cmd said "The superblock could not be read or does not describe a correct ext2 filesystem."
Afterwards, my friend told me to try mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
I typed that in adb shell and something happened. I started processing blocks or something. Unfortunately now, I am unable to mount the data partition at all. I am also unable to flash the userdata.img onto my phone through fastboot.
UPDATE: When I open up twrp recovery and look in the log I see the following:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount '/cache/
E: Unable to mount '/persist'
...done
E: Unalbe to mount storage.
E: Unable to mount /data/media during GUI Startup.
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to Mount '/cache'
E: Unable to mount /data/media/TWRP .twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
Anyone know how to fix this? Please help, I owe you so much if you can solve this! Reply to me if you're able to help, I'm also new to xda so I don't really know how messages work. Thanks!

Try taking it out and putting it back in. It happened to me too.

mygoldeneye said:
Try taking it out and putting it back in. It happened to me too.
Click to expand...
Click to collapse
By sdcard I mean the internal sdcard (/storage/emulated/0). Nexus 5 does not have an external sdcard slot anyways.

So you are saying you have no apps, no widgets, nothing... /storage/emulated/0 is your main storage which INCLUDES your system files (unless you have a phone or tablet that has a separate internal SD card - would be /storage/emulated/1 ... I am guessing)

TWRP 3.0.2.0 on 920W8 w/6.0.1 leaves me broken :(

So I decided I would switch back to a custom rom on my phone. I reverted to stock several months ago to get the official Telus 6.0.1 update. Now that I have that, I'm trying to get TWRP installed so I can throw a ROM on, but when I get TWRP loaded, none of the other file systems are mountable and I don't see anything in the /sdcard directory or anywhere else. There are errors when trying to mount them as well.
I did flash the 6.0.1 bootloader and modem the rom dev suggested before doing the TWRP recovery, but I'm still stuck with not being able to access anything while in the recovery, and I get thrown in to a bootloop if I try to boot the OS. I can flash the Telus 6.0.1 rom back to my phone and resolve this, but I'm wondering why TWRP is "corrupting" my phone like it is. Here are the errors i'm seeing in recovery:
Could not mount /data and unable to find cryptofooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount '/data' (Invalid argument)
.......done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present
Unable to mount /data/media/TWRP/.twrps
Anyone know what's going on here? I tried this same process a few weeks ago, but just resigned myself to staying on the stock Telus rom because this same issue came up.

How to uninstall Magisk?

Hello. I've recently tried to uninstall Magisk through its app but that doesn't seem to work. Some apps still detect that I have root access and not allow me to use it. Thus, I tried removing the install files in my phone and it still couldn't work. I have also tried factory resetting but for some reason TWRP won't allow it.
It writes:
"Could not mount /data and unable to find crypto footer
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Updating partition details
Failed to mount '/data' (Invalid argument)
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount '/data/media/TWRP/.twrps
MTP enabled
Failed to mount '/data' (Invalid argument)
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Formatting cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Invalid argument)
Unable to mount storage"
Phone is still working perfectly apart from these errors. How can I fix this? Any help would be greatly appreciated. Thanks!

larrysgx said:
Hello. I've recently tried to uninstall Magisk through its app but that doesn't seem to work. Some apps still detect that I have root access and not allow me to use it. Thus, I tried removing the install files in my phone and it still couldn't work. I have also tried factory resetting but for some reason TWRP won't allow it.
It writes:
"Could not mount /data and unable to find crypto footer
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Updating partition details
Failed to mount '/data' (Invalid argument)
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Full SELinux support is present.
Unable to mount '/data/media/TWRP/.twrps
MTP enabled
Failed to mount '/data' (Invalid argument)
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Formatting cache using make_ext4fs...
Updating partition details...
Failed to mount '/data' (Invalid argument)
Unable to mount storage"
Phone is still working perfectly apart from these errors. How can I fix this? Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
To answer this we need the following info:
1. What phone do you have?
2. Do you use a stock or custom rom?
3. If you use a custom rom, what rom is it?

Zapthos said:
To answer this we need the following info:
1. What phone do you have?
2. Do you use a stock or custom rom?
3. If you use a custom rom, what rom is it?
Click to expand...
Click to collapse
Well, I have a S7 Edge. I am not that experienced with tech so I'm not so sure what I did for the Rom.
I flashed it through Odin though. I could dm you the link of the tutorial if you don't mind

Re-Flash rom
You can try re-flashing the rom (not sure if it's a word but you probaly know what I mean). So enter twrp (power, volume up & home button), go to wipe and wipe the following: System, Data, Cache, Dalvik/Art cache. Once you've done that flash the rom. Depending on what rom you use, you can see if magisk is gone. If not, try another rom (make sure it is for your device!!!). This should help, if not let me know.

Or just run Magisk Manager, tap Uninstall, then tap complete uninstall.