Today I was using my T-mobile galaxy note 2 (sgh-t889) perfectly. I've recently installed the OCT-OS Lollipop rom by hedwig34 and its been working fine until today
My phone rebooted and it displayed the Samsung Galaxy Note II Splash Screen for a while so I tried to do a battery pull but It kept displaying.
It just displays and shows nothing else, no reboots, just "Samsung Galaxy Note II"
Anyway, I've been trying to flash the stock roms that are on the Android Development forums, but when I do, Odin shows me this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Whenever I try to install custom recoveries or root by itself, it shows something similar.
I don't think NAND Write start FAIL looks anything good.
Can someone please help me!
Edit: I'm now able to enter recovery (TWRP 2.7.2.0) but it says I have no OS installed:good:
Recovery Problems
So, I've gotten myself into TWRP v2.7.2.0 and I was checking Install to see If I can install a new ROM and first thing I see is (Internal Storage 0 MB) and I'm scrolling through the stuff and it shows folders like cache, data, dev, efc, lib, preload, sbin, system, tmp and others. I can't mount anything (It doesn't give me option for USB Storage Mounting. the log shows something like this:
E: Unable to mount ' /data'
E: Unable to mount ' /efs'
E: Unable to mount internal storage.
E: Unable to mount ' /storage'
And so on..
And when I insert my SD card and reboot into recovery, It still shows the internal storage(0 MB) and doesn't show the contents in my SD Card.
OK I did some research and it seems that somehow i formatted all the data on the device. I've managed to transfer the Note 4 DN4 rom that I found on the Android Development forums. when I try to install it, It'll give me this:
Error flashing zip '/sdcard/DN4_v2 for lte(2).zip'
Updating partition details...
E: Unable to mount '/efs'
E: Unable to mount '/data'
E: Unable to mount '/data'
E: Unable to mount '/cache'
E: Unable to mount '/system'
E: Unable to mount '/data'
E: Unable to mount internal storage.
Sammpls said:
OK I did some research and it seems that somehow i formatted all the data on the device. I've managed to transfer the Note 4 DN4 rom that I found on the Android Development forums. when I try to install it, It'll give me this:
Error flashing zip '/sdcard/DN4_v2 for lte(2).zip'
Updating partition details...
E: Unable to mount '/efs'
E: Unable to mount '/data'
E: Unable to mount '/data'
E: Unable to mount '/cache'
E: Unable to mount '/system'
E: Unable to mount '/data'
E: Unable to mount internal storage.
Click to expand...
Click to collapse
So, Heres what I know now:
I've got no OS installed on the phone now. I have several partitions corrupted. .Pit files probably could fix it. t889 doesn't have any working .pit files. Even if they did work Odin wouldn't flash them anyway.
I've received no help so far from anybody and nothing seems to be working... I can't believe this topic has 60+ or so views but theres 0 people to help.
ANYONE??? I've been waiting all day for any response!
I literally just got the phone 4 days ago...
Even if you can't give me an solution, atleast tell me what's going on?!?!?
I had a 0 MB problem on my HTC One X. Boot into TWRP, mount USB, connect to PC, format data partition using fat32. Good luck. Hope fully, this will allow you to access internal memory.
Did you try flashing Odin without a pit file or re-partitioning? Did you try the stock firmware from sammobile.com?
http://www.sammobile.com/firmwares/database/SGH-T889/
I have exact same issues.
audit13 said:
I had a 0 MB problem on my HTC One X. Boot into TWRP, mount USB, connect to PC, format data partition using fat32. Good luck. Hope fully, this will allow you to access internal memory.
Did you try flashing Odin without a pit file or re-partitioning? Did you try the stock firmware from sammobile.com?
http://www.sammobile.com/firmwares/database/SGH-T889/
Click to expand...
Click to collapse
Is there any solution?
I don't know as it has not happened to my note 2, only my htc one x.
addison892 said:
Is there any solution?
Click to expand...
Click to collapse
so is your issue resolved now?
news about the problem?
There is nothing that explains a resolve to this situation. twrp absolutely useless as it doesn't even recognize usb or the ext sd card. odin fails, and no info to get thru it. Wish someone could post some fix. Have tried everything in the book. wanted to fix my note 2 for a family member.
Same issue
I had my phone working perfectly with an unofficial CM 13.1. One day my battery ran a little low, and after I charged it the darned thing got stuck at the "Samsung Galaxy Note II" boot screen. After going into TWRP I noticed that it could not access any of the partitions, nor the external SD card. I have googled about every combination of search terms I can think of, but this thread was the only one that came close to describing my situation.
Following a suggestion I saw somewhere, I have tried flashing the stock rom but Odin chokes at the system.img file. I then try to boot into recovery (now stock) and it says the flashing went wrong and to go back to Kies in recovery mode. I am able to use Odin to re-flash TWRP and boot up in that, but it cannot mount anything. The /etc/fstab file has entries for the partitions but they are invalid and do not point to any device. I looked in /dev/block but there is only one partition showing for the mmcblk0 device, mmcblk0p1. There used to be at least 16 (/data used to point to /dev/block/mmcblk0p16). I tried using Odin to flash a .pit file but it does nothing.
At this point my Note II is a doorstop. This is my only phone so I am stuck. Any help will be appreciated.
Help me, Obi Wan Kenobi. You're my only hope.
My note 2 started same way, some apps starts to stop, getting a lot of errors, then I tried to factory reset, now only shows t samsung logo, tried odin.
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
on cmw same thing
E: Unable to mount ' /data'
E: Unable to mount ' /efs'
E: Unable to mount internal storage.
E: Unable to mount ' /storage'
i have the exact same issue. Kindly tell me if you found any solution?
aghamoosaraza said:
i have the exact same issue. Kindly tell me if you found any solution?
Click to expand...
Click to collapse
Tried flashing with different USB cables and USB ports?
audit13 said:
Tried flashing with different USB cables and USB ports?
Click to expand...
Click to collapse
Of course I did. I have twrp recovery, I cant format my device. Unable to mount any folder.
If you tried using different USB cables, USB ports, and different versions of Odin, the phone may need to be force flashed using hardware like an Octopus Box or the memory chip is defective.
Same. Let my battery run dead on t0lte that was running lineageOS and now it boots to Samsung Note II . TWRP cannot mount internal or external storage. This is bad!
Related
Hi all,
I have a Note 2 GT-N7105 which has always ran stock firmware and never rooted.
The phone gets stuck on the Samsung logo and won't boot any further. When I get it into the Andriod diagnostic mode (Not sure what it is called) I get the following EFS error;
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
I have flashed the phone using Kies which hasn't worked. I have also downloaded Odin and used that to flash the phone with a stock 4.3 image using a PIT file and repartitioned the phone with still no luck. I don't have a backup of the EFS folder. How can I remount/ repair the EFS folder?
I have connected the phone using ABD but I'm not sure how to enter commands or even if it will help.
neocleous said:
Hi all,
I have a Note 2 GT-N7105 which has always ran stock firmware and never rooted.
The phone gets stuck on the Samsung logo and won't boot any further. When I get it into the Andriod diagnostic mode (Not sure what it is called) I get the following EFS error;
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
I have flashed the phone using Kies which hasn't worked. I have also downloaded Odin and used that to flash the phone with a stock 4.3 image using a PIT file and repartitioned the phone with still no luck. I don't have a backup of the EFS folder. How can I remount/ repair the EFS folder?
I have connected the phone using ABD but I'm not sure how to enter commands or even if it will help.
Click to expand...
Click to collapse
We both are having the issue here. Though, I'm on GT-N7100.
Things I have tried and the result is failure:
1. Changing USB
2. Updating drivers
3. Tried KIES firmware recovery
4. Tried to root
5. Tried to flash original ROM/firmware
6. Tried to flash PIT
7. Tried to nand erase all
These are the logs:
<ID:0/005> Erase...
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
Other than that, I can't do any **** on this. I'm tired.
Basically woke up with my phone as a brick... phone crashed when my alarm was supposed to go off (luckily I was already awake) and now hangs on the boot splash screen.
Device is an i747m, previously running S3Rx 3.0 (Android 4.3) with MK5 bootloader and modem. CWM 6.0.4.7 installed.
I am able to boot into both recovery and download mode.
However, in recovery mode, I get the errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Furthermore, if I try to factory reset, I get the error:
Code:
Formatting /data...
Error mounting /data!
While in recovery, I am not able to flash a new recovery or ROM. There are no errors when flashing, however, after rebooting nothing has changed. I'm assuming that's because the system cannot access the storage.
Through Odin, I can flash TWRP with no errors. However, once I try to boot into recovery, I am still on CWM 6.0.4.7.
Through Odin, I am unable to flash ROMs (trying to flash 4.3 MK5 stock rom). I am using Odin 3.07 on a W7 x64 computer with Samsung drivers installed and an official Samsung USB cable.
I receive the error:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747MVLUEMK5_I747MOYCEMK5_I747MVLUEMK5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
It appears that there is a problem with the internal memory since I can't read/write, but I am unsure if it is fixable.
I have come across this thread, but I am skeptical if it will work since it is for the Verizon S3.
I also came across this thread in my research, but I can't get cygwin to download >.> It seems promising, but I am unable to try it at the moment.
Any help or suggestions would be greatly appreciated. Please let me know if any additional information is required.
Have you tried flashing a 4.4.2 ROM?
audit13 said:
Have you tried flashing a 4.4.2 ROM?
Click to expand...
Click to collapse
Yes, I have tried flashing the 4.4.2 NE6 ROM using Odin with the same result (NAND write fails).
I have also tried flashing via Heimdall. No success there either. Heimdall is able to upload the file to my device (according to the progress bar), but then terminates with, ERROR: Failed to confirm end of file transfer sequence!
Also, the PIT file I extracted from my device via Heimdall does not match a "normal" i747m 16gb PIT found on the internet... I also cannot flash the 'normal' PIT onto my device (same error as above).
It's possible the internal memory chip is damaged which is not easy to repair. Simplest fix may be to buy a used s3 with a smashed screen and do a motherboard swap.
Yeah, that's what I'm thinking too at this point since I can't get anything to write onto the memory. I just loaded up Aroma File Manager through recovery and it looks like most of the files on my internal memory are gone, even though I have not been able to successfully factory reset through recovery. At least I have TiBkps of everything.
Do you think I could franken-phone using an i9100 (international model S3)?
Boot into download to find out.
Hello everybody
At dawn last Saturday, my phone rebooted only, did not go beyond the screen of SAMSUNG GALAXY NOTE II; I did wipes and did not work, try to re install the ROM stock and ODIN pulls me error. I have tried several rom stock and nothing, try using the ADB SIDELOAD method and it gives me about 55% error of loading the rom (Set_metadata_recursive: some changes failed
Updater process ended with error: 7 ")
The phone enters DOWNLOADING mode and Recovery mode. (USE TWRP V.3.0.2)
The recovery log shows a series of errors that I do not understand very well and lead me to think that there may be an error in the computer's HARDWARE (eMMC Chip?)
I would appreciate if someone could confirm the error of HARDWARE so I do not waste my time downloading files that will not serve if that is the problem.....
Thank you
Spanish version
En la madrugada del pasado Sabado, mi telefono se reinicio solo, no paso mas alla de la pantallazo de SAMSUNG GALAXY NOTE II; hice wipes y no funciono, trate de re instalar la stock rom y ODIN me saca error. He probado varias stock rom y nada, trate de usar el metodo ADB SIDELOAD y me da error al 55% aproximadamente de cargar la rom(Set_metadata_recursive: some changes failed
updater process ended with error:7")
el telefono entra en modo DOWNLOADING y modo Recovery. (USO TWRP V.3.0.2)
el registro del recovery muestra una serie de errores que no entiendo muy bien y me llevan a pensar que puede haber un error en el HARDWARE del equipo (eMMC Chip?)
agradeceria si alguien me pudiera confirmar el error de HARDWARE para no perder mas mi tiempo bajando archivos que no van ha servir si ese es el problema.
gracias
What error are you getting in Odin? Try using TWRP 2.87 to flash a rom.
sorry i forgot to post the ODIN Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and if i try to flash another recovery (TWRP 2.8 or philz_touch_6.48) the error its the same NAND Write Start!!
<ID:0/003> FAIL!
mcastrojz said:
sorry i forgot to post the ODIN Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and if i try to flash another recovery (TWRP 2.8 or philz_touch_6.48) the error its the same NAND Write Start!!
<ID:0/003> FAIL!
Click to expand...
Click to collapse
Same Problem Here Not able Flash using Odin.in Twrp Memory Show 0 mb .also cant find any file on twrp .
I think it is problem of samsung Emmc Bug.
shubhjit said:
Same Problem Here Not able Flash using Odin.in Twrp Memory Show 0 mb .also cant find any file on twrp .
I think it is problem of samsung Emmc Bug.
Click to expand...
Click to collapse
i think the same about eMMC problem, but my question is: if the problem is a eMMC bug, it can fix with any software? or the unique solution its change?
Odin stops when trying to flash the sboot.bin file because you need to use the original Samsung USB cable, use a different USB port, the rom is not for the phone, or the bootloader in the phone is newer than the bootloader in the rom.
audit13 said:
Odin stops when trying to flash the sboot.bin file because you need to use the original Samsung USB cable, use a different USB port, the rom is not for the phone, or the bootloader in the phone is newer than the bootloader in the rom.
Click to expand...
Click to collapse
Hmmm well ... i used the stock rom 4.4.2 installed in my phone before rooted; downloading from sammobile, i try with 2 different cables in the 3 USB ports of my laptop.... The bootloader theme is not clear to me ... As can be the bootloader newer than the bootloader of the rom if i try to flash the same stock rom that i haved before the problem?
its possible to flash only a old bootloader? after that flash the stock rom?
Try to confirm the bootloader version in the phone because the sboot.bin file is a bootloader. You can't flash an old bootloader over the newer bootloader and this could be why Odin stops.
Any update on this?
Did you find anything? I am experiencing the exact same issue.
Jo The Veteran said:
Did you find anything? I am experiencing the exact same issue.
Click to expand...
Click to collapse
Me neither, nothing so far, but I'm still looking....
Did you confirm the model # of the phone in download mode?
Mi phone model is a GT-N7100 .... i test with diferents cable and don't work, make the same in other computer with unsuccessfully results.... i don't know to do now.... i think that i need to go to see a cellphone thecnician.... or chage the eMMC Chip....
THIS IS the log of TWRP when start in recovery mode....
E:unable to find partition size for '/boot'
E:unable to find partition size for '/recovery'
E:unable to find partition size for '/modem'
E: primary block device '/dev/block/mmcblk0p16' for mount point '/data' is not present!
failed to mount '/data' (invalid argument)
unable to recreate /data/media folder.
UPDATING PARTITION DETAILS...
Failed to mount '/efs' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/System' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux support is present
Failed to mount '/cache' (Invalid argument)
Running boot script...
done.
Failed to mount '/cache' (Invalid argument)
unable to mount /data/media/TWRP/.twrps
MTP Enabled
i try to repair the system using twrp and don´t work .... log say Format failed...
My hope of being able to fix this without touching the hardware fades quickly
if any person with experience see this log, can tell me if my problem have solution? or go to the technician to change a eMMC chip?
mcastrojz said:
THIS IS the log of TWRP when start in recovery mode....
E:unable to find partition size for '/boot'
E:unable to find partition size for '/recovery'
E:unable to find partition size for '/modem'
E: primary block device '/dev/block/mmcblk0p16' for mount point '/data' is not present!
failed to mount '/data' (invalid argument)
unable to recreate /data/media folder.
UPDATING PARTITION DETAILS...
Failed to mount '/efs' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/System' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux support is present
Failed to mount '/cache' (Invalid argument)
Running boot script...
done.
Failed to mount '/cache' (Invalid argument)
unable to mount /data/media/TWRP/.twrps
MTP Enabled
i try to repair the system using twrp and don´t work .... log say Format failed...
My hope of being able to fix this without touching the hardware fades quickly
if any person with experience see this log, can tell me if my problem have solution? or go to the technician to change a eMMC chip?
Click to expand...
Click to collapse
Hi @mcastrojz,
I have exactly the same problem as your. Did you fix your phone yet. I brought my phone to a few phone store and they tell me storage has been broken, but I dont believe it, so I come here and saw your post.
manhtidus said:
Hi @mcastrojz,
I have exactly the same problem as your. Did you fix your phone yet. I brought my phone to a few phone store and they tell me storage has been broken, but I dont believe it, so I come here and saw your post.
Click to expand...
Click to collapse
Hi manhtidus; I have not yet been able to repair the phone; I have taken it to technical service and the only thing they are right to say is that you have to change the motherboard ... unfortunately I do not have money at the moment to do that and also to buy a new phone.....
can you try to install this file via odin
https://forum.xda-developers.com/attachment.php?attachmentid=1394028&d=1349983558
it is recovery-cache-fix by chainfire
it is only a test (in your case ) and it is not a fix ,nor a solution
and things maybe became worst (brick your phone)
so you could try it at your own risk
if the installation pass OK , so I think you have ray of hope
@xcorona: Thanks for reply, I tried install that file with hope, but it cant help, at least in my case.
P.s: In a crazy moments, I tried to download and flash anything I find on this forum, but no chance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm finding way to repartition, or remount internal storage. I think it can do something
Cause, everytime I boot into recovery, this noti will show on the log:
Code:
E:Unable to find partition size for '/boot'
E:Unable to find partition size for '/recovery'
E:Unable to find partition size for '/modem'
E:Primary block device '/dev/block/mmcblk0p16' for mount point '/data/ is not present!
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder.
Updating partition details...
Failed to mount '/efs' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Failed to mount '/data' (Invalid argument)
Failed to mount '/cache' (Invalid argument)
Full SELinux support is present.
Failed to mount '/cache' (Invalid argument)
Running boot script...
Done.
Failed to mount '/cache' (Invalid argument)
Unable to mount /data/media/TWRP/.twrps
MTP Enable
Thanks again, sr for my bad Eng.
@manhtidus
note 2 & S 3 (16 giga ) as you know suffering from Bad manufacturing ( internal storage like hard drive in PC ) , not all the phones
This problem appears after a period , it does not have a specific reason 100% for the emergence of this problem , so they call it (insane chip)
when the phone reach that point , PC in almost cases will not solve it
it only can be done via box (as easy jtag ) or replacing the hard or the whole motherboard
and i am sorry to say that all the next steps via PC it will be just wasting time
so it will be only Your decision time vs money
xcorona said:
@manhtidus
note 2 & S 3 (16 giga ) as you know suffering from Bad manufacturing ( internal storage = hard drive in PC ) , not all the phones
This problem appears after a period ,It it does not have a specific reason 100% for the emergence of this problem , so they call it (insane chip)
when the phone reach that point , PC in almost cases will not solve it
it only can be done via box (as easy jtag ) or replacing the hard or the whole motherboard
and i am sorry to say that all the next steps via PC it will be just wasting time
so it will be only Your decision time vs money
Click to expand...
Click to collapse
Thanks @xcorona, I think you gave me the answer I finding on the internet for a long time.
Cause my phone has been working very great from 4 years ago with stock rom, util it has this problem after I rooted and used some custom rom, so I thought its a software problem (because of my stupid), and tried to find solution on this forum.
Last chance, I brought to cell store where they tall me have to replace mainboard or internal storage of the phone, but I dont think that's the truth.
Now, I'll not try to fix my phone and let it rest in peace.
Thanks again for your great answer.
First, sorry for my bad Eng
I flashed my phone with some rom cook for N7100 and It running smoothies, but this morning, my phone auto restart and stuck at logo screen. I get into TWRP and find there is no OS and no internal memory, after try everything(I known), last chance I used Format Data, but It still not working. Tried to flash other Rom, even stockrom by Odin, but it gets:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I recorded the video too but I dont have enough post to post link, so sorry:
/watch?v=U8V_3aRfucw (youtube)
Updated video:
https://youtu.be/U8V_3aRfucw
Logo screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Internal Storage 0MB:
Wipe failed:
Data Format failed:
SD Card folder empty:
I really need help to solve this problem. Please help me.
Thanks.
manhtidus said:
First, sorry for my bad Eng
I flashed my phone with some rom cook for N7100 and It running smoothies, but this morning, my phone auto restart and stuck at logo screen. I get into TWRP and find there is no OS and no internal memory, after try everything(I known), last chance I used Format Data, but It still not working. Tried to flash other Rom, even stockrom by Odin, but it gets:
I recorded the video too but I dont have enough post to post link, so sorry:
/watch?v=U8V_3aRfucw (youtube)
Logo screen:
Internal Storage 0MB:
Wipe failed:
Data Format failed:
SD Card folder empty:
I really need help to solve this problem. Please help me.
Thanks.
Click to expand...
Click to collapse
Go to wipe click data click advance click change file system to fat32 and go to wipe again click advance click file system and click ext4 done
Or
Try Odin best guide
xress7 said:
Go to wipe click data click advance click change file system to fat32 and go to wipe again click advance click file system and click ext4 done
Or
Try Odin best guide
Click to expand...
Click to collapse
Thanks for reply, I tried that too but always notice:
Code:
Updating partition details...
"Failed to mount '/efs' (Invalid argument)
"Failed to mount '/cache' (Invalid argument)
"Failed to mount '/system' (Invalid argument)
"Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
And Odin failed too.
Someone please help....
Sorry for spam but help me please, I don't know find where to help
Odin fails when trying to install sboot.bin for one or all of these reasons:
the ROM is not made for the phone;
need to use the original Samsung USB cable;
need to use a different USB 2.0 port;
the ROM's bootloader is older than the bootloader in the phone; and/or
the phone's memory chip has failed and you need to replace the motherboard.
Did the ROM come from sammobile.com?
audit13 said:
Odin fails when trying to install sboot.bin for one or all of these reasons:
the ROM is not made for the phone;
need to use the original Samsung USB cable;
need to use a different USB 2.0 port;
the ROM's bootloader is older than the bootloader in the phone; and/or
the phone's memory chip has failed and you need to replace the motherboard.
Did the ROM come from sammobile.com?
Click to expand...
Click to collapse
The "phone's memory chip" part is the scariest part and I hope its not
I used "RESURRECTION REMIX [5.8.0]" Rom, and I tried flash Stock Rom N7100XXUFNI4_N7100OLBFNI1_XXV but it failed.
And I don't understand part "the ROM's bootloader is older than the bootloader in the phone". Where can I check it?
You confirmed that the phone model # is gt-n7100 in download mode? Did you get the stock firmware for the n7100 from here: https://www.sammobile.com/firmwares/database/GT-N7100/ ?
audit13 said:
You confirmed that the phone model # is gt-n7100 in download mode? Did you get the stock firmware for the n7100 from here: https://www.sammobile.com/firmwares/database/GT-N7100/ ?
Click to expand...
Click to collapse
Yes, I downloaded the stock firmwave form Sammobile,
Download mode screen showed:
Code:
ODIN MODE
PRODUCT NAME: GT-7100
CURRENT BINARY: Custom
SYSTEM STATUS: Offical
KNOW WARRANTY VOID: 1
RP SWREV: A2
Sounds like the memory chip could be defective.
Try flashing twrp 2.87 and see if that works. If it doesn't work, you can try a cell repair shop to see if they can force flash it.
audit13 said:
Sounds like the memory chip could be defective.
Try flashing twrp 2.87 and see if that works. If it doesn't work, you can try a cell repair shop to see if they can force flash it.
Click to expand...
Click to collapse
Still cant flash it:
Code:
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Just like the phone refuse to change anything in it :crying:
If cant find any solution, so last chance is bring it to store and pray
I admit it doesn't look good.
A cheaper solution may be to buy a used phone with a smashed screen and working motherboard.
Thanks for your helping.
I'll look for some chance from terminal or adb sideload, bad thing is last night it still working perfectly. so sad
manhtidus said:
Thanks for reply, I tried that too but always notice:
Code:
Updating partition details...
"Failed to mount '/efs' (Invalid argument)
"Failed to mount '/cache' (Invalid argument)
"Failed to mount '/system' (Invalid argument)
"Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
And Odin failed too.
Click to expand...
Click to collapse
Try pit for odin
xress7 said:
Try pit for odin
Click to expand...
Click to collapse
I'm finding PIT file for flash, but still get this:
Code:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe not right PIT file, I flashed 2 file "PIT_N7100_16GB_20121102.pit", "t03g_0907.pit" found on internet, but not working
Looks like you'll have to either take it to a cell shop or replace the motherboard.
Tried to use adb sideload to install other recovery, install perfect but after restart seem nothing change.
Tried change timezone on TWRP, but after restart, it did not save changes.
Same happened with my note 2 tried every thing but Nand is corrupted .there are only 50% chance .
Wow, I guest I'm the first one get this error:
After find out can push file to mobile by adb push XXX, I tried reinstall rom, and alot of stuffs to test, now I get this error when use "Data Format" on TWRP: "Unable to get block size for wipping crypto footer." and still
"Unable to wipe data
Unable to format to remove encryption --> I guess I need to do something in here
Failed to mount /efs, /cache /system /data
Unable to mount storage
Hope someone will help my resolve this
Update:
Sadly, After reboot phone, everything gone, nothing saved.
In my /dev/block/ there is no file mmcblk0p0 - 16 , just have loop0-7, ram0-15
hi
got a problem - phone hanged during startup on att logo, then i tried following
1. reboot via recovery - hanged after reboot
2. clear cache - hanged after reboot
3. factory reset - after reboot on samsung galaxy logo
4. OAT firmare is not picked up
5. odin nugat - getting write failed
6. odin marshmallow - same:
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
for marshmallow i used following firmware
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT.rar.
in recovery following error message shown at the bottom:
dm-verity verification failed
E:failed to mount /system (invalid argument)
any idea what to do next?
danila2 said:
hi
got a problem - phone hanged during startup on att logo, then i tried following
1. reboot via recovery - hanged after reboot
2. clear cache - hanged after reboot
3. factory reset - after reboot on samsung galaxy logo
4. OAT firmare is not picked up
5. odin nugat - getting write failed
6. odin marshmallow - same:
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
for marshmallow i used following firmware
G891AUCS2API2_CL8737252_QB10881022_REV02_user_low_ship_MULTI_CERT.rar.
in recovery following error message shown at the bottom:
dm-verity verification failed
E:failed to mount /system (invalid argument)
any idea what to do next?
Click to expand...
Click to collapse
Download qb2 for nougat again.
Be sure u got correct Odin.
As I had no problem redoing my phone
Friday night back to qb2.
Sent from my SAMSUNG-SM-G891A using Tapatalk