Hello guys. I'm new here. So, my note 2 restarted after i woke up and then it stuck at bootscreen. When i put it in recovery mode, it seems all things cannot be mounted e.g data,efs, system etc because no such file or directory. And then I flashed with odin then it said "NAND write start FAIL". What is going on with my phone? I searched this problem on google and most users said that it's EMMC corrupted. Can someone here clarify? Do i have to send my phone to repair or is there any other way to fix it?
Which file failed to flash in Odin? You used the latest stock ROM from sammobile.com?
What you have described happened to me not long ago ( woke up, bootloop, recovery mode errors ( can't mount bla bla ), getting Nand write fail with Odin when trying to flash anything). Came to the conclusion that I have a corrupt Emmc chip. Ended up buying a motherboard. You can try what is stated in this thread (didn't work for me, but good luck):
https://forum.xda-developers.com/showthread.php?t=2154890
You should try to format everything like data, system... then try to reflash rom
yeah that happened to me too last week i just bought a newer phone i didn't think repairing a 4 year old phone would be worth it
audit13 said:
Which file failed to flash in Odin? You used the latest stock ROM from sammobile.com?
Click to expand...
Click to collapse
Yes i was on 4.4.2 XXUFND4 firmware
Which file failed to flash in Odin? Was is aboot.mbn, system.img, etc?
Related
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.
dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works
I have searched all over the last few hours for a solution to this issue and yet it mystifies me.. I was running Mr robinson's rooted stock and my phone ran out of battery while at the store, when I got home it refused to boot up.. I have tried several ODIN formats, tried kies... When I get in stock or custom recovery it will fail to mount EFS partition Invalid argument.. Even after a full ODIN flash! Now the good thing is, I have fresh backups and even direct and recent full system and direct file backups of both my efs.tar.gz file and a 20mb file which I believe is the EFS partition... Yes nothing I mean nothing works, At this point if someone is willing and able to help me, you will be my eternal hero!
Thanks in advance for any assistance
Try the very earliest Odin tar available for your device. Do a factory reset then Odin (vice versa would work as well). If you are on the 4.3 bootloader flash the 4.3 Odin after if odin states that the flash failed. Does your battery charge?
Coug76 said:
Try the very earliest Odin tar available for your device. Do a factory reset then Odin (vice versa would work as well). If you are on the 4.3 bootloader flash the 4.3 Odin after if odin states that the flash failed. Does your battery charge?
Click to expand...
Click to collapse
I am on the 4.3 boot loader as my battery turns straight on when plugged in as well as Knox flagged in download mode.. I have flashed stock 4.3 with Odin several times and it completes the procedure no problem.. I have yet to try and flash an older stock rom but that was because I was under the believe there were compatability issues once I made the leap to the 4.3 bootloader. I really think this has to do with the ever present /efs cannot mount illegal argument in recovery issue.. Just cause that seems to be the one difference.. Thanks for your help!
UVALJ1 is my suggestion. I've had success with it recovering jacked up file systems 2x.
Coug76 said:
UVALJ1 is my suggestion. I've had success with it recovering jacked up file systems 2x.
Click to expand...
Click to collapse
Ok I will try and report back.
DarkMattr said:
Ok I will try and report back.
Click to expand...
Click to collapse
No such luck, it still freezes at the last screen before it would normally boot into android, which is now a samsung screen(which shows the process completed successfully). I did note that I AM able to plug my phone in while it's off without it autostarting up and let it charge without booting, which I thought had something to do with which bootloader I am on. Again the only constant is this EFS issue.. I'm praying for some expertise in the area
TL ; DR :
1. S3 got an update.
2. Bricked by the OTA update. was formerly 4.0.4
3. Debrick image is cuemjb, so I assumed that the update is cuemjb ( leaping past 4.1.1 and 4.1.2 )
4. cant mount cache after that.
5. Flashed Stock rom together with BL, CP, CSC, and pit file. Also, Nand erase all is toggled. ( Im sorry )
6. Now CWM cant mount anything under the mounts and storage except the ext-sdcard. I assume that is the problem why my S3 doesn't boot up. Please, anyone tell me how to recover my partition
Long :
So I just received an S3 from my Aunt that has been bricked after updating. I was there when she was updating her currently ICS phone, (4.0.4). After finishing downloading, the phone rebooted as it should be, and to our surprise, it doesn't power on anymore. I followed several threads that includes putting a debrick image into your SD card. And so it powered on, but not past the Samsung SIII logo. I boot into recovery to find that the cache cant be mounted. So I searched for other threads that could help me mount my cache, and one including using NAND ERASE ALL at the Odin ( my mistake, Im so sorry. cant detect trolls). I flashed the stock rom altogether with the BL, Phone, CSC, pit file, and the PDA. Afterwards I flashed CWM and SuperSU, just to find out that I cant mount anything under the mounts and storage tab. I dont know what to do, I just want to restore this phone. Some say that soft bricked phones can be recovered. Can someone out there help me ?
Alomia said:
TL ; DR :
1. S3 got an update.
2. Bricked by the OTA update. was formerly 4.0.4
3. Debrick image is cuemjb, so I assumed that the update is cuemjb ( leaping past 4.1.1 and 4.1.2 )
4. cant mount cache after that.
5. Flashed Stock rom together with BL, CP, CSC, and pit file. Also, Nand erase all is toggled. ( Im sorry )
6. Now CWM cant mount anything under the mounts and storage except the ext-sdcard. I assume that is the problem why my S3 doesn't boot up. Please, anyone tell me how to recover my partition
Long :
So I just received an S3 from my Aunt that has been bricked after updating. I was there when she was updating her currently ICS phone, (4.0.4). After finishing downloading, the phone rebooted as it should be, and to our surprise, it doesn't power on anymore. I followed several threads that includes putting a debrick image into your SD card. And so it powered on, but not past the Samsung SIII logo. I boot into recovery to find that the cache cant be mounted. So I searched for other threads that could help me mount my cache, and one including using NAND ERASE ALL at the Odin ( my mistake, Im so sorry. cant detect trolls). I flashed the stock rom altogether with the BL, Phone, CSC, pit file, and the PDA. Afterwards I flashed CWM and SuperSU, just to find out that I cant mount anything under the mounts and storage tab. I dont know what to do, I just want to restore this phone. Some say that soft bricked phones can be recovered. Can someone out there help me ?
Click to expand...
Click to collapse
Since 4.0.4 was your last working version of android I would suggest using Odin to flash stock 4.1.1. A tar.md5 can be found a sammobile.com. After that you can again try the OTAs.
hello guys, im having a problem with a s4 mini, i dont have a recovery, a friend gave it to me with this problem.
I can get download mode but when i try to flash TWRP or CWM i get the OK signs in odin but it doesnt get into recovery, well it gets to recovery but it says "no command" (sin comando, in spanish).
It used to have jellybean and updated itself to kitkat, it never had a custom rom.
This is what the screen in download mode shows:
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY: samsung official
SYSTEM STATUS: Official
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION ENABLE
I tried lot of things, but my last resort is to ask, if you have anything to help i appreciate!
maybe should try stock rom next with odin.
S3miniFin said:
maybe should try stock rom next with odin.
Click to expand...
Click to collapse
Already tried many stock firmwares for i9195 , when odins flashes it, it reboots to recovery and it says "NO COMMAND" ( Sin comandos ) then reboots and starts again with that.
Did you get this fixed mate. I'm pulling my hair out with the same problem. My son messed up a perfectly good phone that I had used for 3 years, and the toerag won't tell me what he did. (apparently he was texting when it when down) Tried various version of stock ROM and I get get diddly squat. ODIN fails to write the firmware and I get aboot on the phone screen. Current problem is stuck on Bootloop. Might just throw the thing away and buy a new one. Would like to fix it though....I'd be eternally grateful for any advice....Thnx
Capokhatpin,
Your son didn't do anything to your phone ! It's just faulty hardware and common problem to Samsung S4 Mini ...
And until now there are dozens of phones that are broken and there is still no solution for that problem.
So, leave the kid alone ...
Cheers !
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
lupus92 said:
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
Click to expand...
Click to collapse
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
lupus92 said:
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
Click to expand...
Click to collapse
I couldn't do it, i threw it away, just give the kid a slap, don't keep trying, you deserve better.
God**** phone.
IronRoo said:
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
Click to expand...
Click to collapse
So, I tried also to flash the stock ROM by booting it with „debrick“ image from SD card and flashing from „download mode“ went good, but after reboot it was same and I couldn't boot into „recovery“ with message „No command....“ or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
So, I tried also to flash the stock ROM by booting it with â??debrickâ?? image from SD card and flashing from â??download modeâ?? went good, but after reboot it was same and I couldn't boot into â??recoveryâ?? with message â??No command....â?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
No, sorry I misunderstood @lupus92 original situation.
Boombastical said:
So, I tried also to flash the stock ROM by booting it with �¢??debrick�¢?? image from SD card and flashing from �¢??download mode�¢?? went good, but after reboot it was same and I couldn't boot into �¢??recovery�¢?? with message �¢??No command....�¢?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
IronRoo said:
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
Click to expand...
Click to collapse
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Sent from my GT-N7000 using XDA-Developers mobile app
Boombastical said:
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Click to expand...
Click to collapse
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
IronRoo said:
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Click to expand...
Click to collapse
Thanks for sharing your thoutghs, but unfortunately I can't boot anymore to 'Download mode'. [emoji45] It can be still booted by 'Debrick' image from SD card but nothing more then that. From there I can't go anywhere further. Without SD Card it doesn't give signs of life except if it is attached via USB it shows as QHSUSB_DLOAD...
I have no time now to play with the phone, but I will try in the weekend again to come to 'Download mode' and to flash again recovery or to erase flash nand cause I have already EFS back up somewhere on my external HD and then we will see what will happened. Thanks again and cheers !
Edit: I can't flash anything thru 'Debrick image' via Odin 3.09. It always give error: Faild to write mmc nand... It can't erase nand nor boot to 'Download mode' ... So I'm clueless at the moment... It looks as the nand is damaged and it can't be accessed anymore... Sadly, I think this S4 Mini will be ended as spare phone for parts only for my girlfriend phone... That's it... If someone have more ideas about it I can still try it... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app
Hi,
I have a samsung gt-n7100 it hangs on the samsung galaxy note II logo and afterwards the android bot appears to be loading...then a red exclamation marks pops up and many error messaged appear such as failed to mount efs etc.
Android System Recovery is - KOT49H.N7100XXUFNE1
I have tried odin3, but it fails every single time....failed to write to nand in short.
I tried using the recovery pit and 4.1.2 recovery files, but same it fails every time and I have noticed that on the phone sometimes there is invalid magic string.
I am thinking that it could be the bootloader since it cannot be downgraded, but the link nd3 bootloader to flash is down and can't try that, but it can be anything.
Can anyone suggest anything? maybe even a way to flash phylz recovery and then flash a custom rom?
Am clueless and any help is appreciated.
Thanks!
use different ver. of odin or kies recovery.
what info do you have in odin?
hey I had same problem stuck on logo and could not use odin becouse of same problem. so it was long time ago and I dont remember in details but what I did was, I used microSD. moved rom files in it and installed them with recovery.Sorry my english is weak but if you dont have cwm recovery or twrp recovery try to find them for odin.I think I did not have them working too but I found recovery to installed with odin and It worked.no NAND error or things like that.so try to install recovery with odin and then put rom files on sd card(if you have it).since then I haven't tryed to install any stock rom using odin becouse I still have that NAND error and I dont want my phone to die in my hands . GOOD LUCK!
Are you using the original Samsung USB cable? Tried different USB ports?