Develop Bugs

Another Soft Brick...

Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED

I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?

bbrou33 said:
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
Click to expand...
Click to collapse
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin

audit13 said:
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
Click to expand...
Click to collapse
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.

britt21 said:
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
Click to expand...
Click to collapse
The only ATT DKL3 firmware that I can find is in this thread. WinRar was failing to unpack the .7z file every time I tried. But I'll try again later when I get home

bbrou33 said:
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
Click to expand...
Click to collapse
You can try different stock firmware from sammobile if you are sure you do not have the 4.3 bootloader.

stuck on boot screen with no recovery mode [SM-t320]

Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.

bmesta said:
Hello Guys!! I'm hoping someone can give me a hand. I got a Samsung Galaxy Tab Pro 8.4 (SM-T320) that is soft brick. If i'm not mistaken the device was been updated via OTA and crashed. Every time i try to turn on the device I get the following message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". For some reason I'm not able to boot the device into recovery mode. It seems the partition got damaged. Please note that I'm using the following commands to boot into recovery mode (volume up+home+power). I have tried connecting my tablet to Samsung Kies v2.6.3.14074_11 and use the option "Firmware Upgrade & Initialisation" but at the end of the procedure I get the following message "This version of the device cannot be updated". I have attempted to flash the device using Odin v3.07. The stock ROM I used was T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5. The Odin PASSED and reset device but the phone did not boot back up. It just gets stuck on the boot screen. I have also tried to flash the device with custom recovery cwmr-20140605.tar. but I didn't have any luck. If anyone has any ideas or solutions, please let me know. I'll greatly appreciated.
Click to expand...
Click to collapse
Very strange.
Did you tried another firmware version using odin?

edlabh said:
Very strange.
Did you tried another firmware version using odin?
Click to expand...
Click to collapse
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?

bmesta said:
I just attempted to use odin v3.09 but I'm still having the same problem. It keeps getting stuck on the samsung galaxy tab pro sm-t320 screen without recovery mode. I have attempted to flash cmw again but the problem persists. I also noticed the battery won't charge anymore. I'm not sure if this was due to a failed flash. Anyone has any other ideas?
Click to expand...
Click to collapse
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".

crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device

bmesta said:
I managed to get my tablet to charge by tearing down the device and reconnecting the battery. After doing this, i plugged it directly to the wall. I got this idea from a youtube video. Im going to leave the battery charging all night. Hopefully tom its a good day and i have a working device
Click to expand...
Click to collapse
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?

edlabh said:
Wow!
just now I realize this problem with non-removable battery. This really sucks!
How did you charge the battery? Maybe a lipo charger?
Click to expand...
Click to collapse
Im really happy to say that now i got a working tablet. I guess removing the battery did the trick.
'edlabh' thanks for all your help. I was able to charge the battery by plugging it directly to the wall. Please note that i had to take the entire tablet apart and disconnect the batteryfor 15 min before reconnecting it. Thank god im good with teardowns and i dont give up that easy

crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
Hello, I was wondering if you would help with the kernel... Idk how to do it. I have done everything he did and even opened my tablet and took out the battery but it still did not work. :crying:
---------- Post added at 07:01 PM ---------- Previous post was at 06:32 PM ----------
crpalmer said:
Get the cwmr tar file (unzip the zip). Flash it in Odin. When it starts to flash it, hold the volume up key until it shows the galaxy tab pro splash screen and says something like "warranty bit set: recovery".
That should get you back to recovery. If that doesn't work, post a screen shot of Odin after the flash.
If your kernel is broken, which it sounds like it is, it's normal that it won't charge because it needs to boot the kernel to charge even when you "power off".
Click to expand...
Click to collapse
I already tried flashing TWRP, CWM, CF Autoroot (to be able to install a custom recovery). I opened it and removed the battery for 15 mins. unlike this guy, it didnt work for me. I also tried flashing CM12. The tablet wont turn on without being plugged in and I can only access "Downloading Mode"
Perhaps the kernel is broken, but how do I fix it?
This is Odin's message, after flashing stock firmware.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANG1_T320XAC1ANG1_HOME.tar.md5 is invalid.
<OSM> End...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320XXU1BOC1_T320UVS1BOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
But it still wont boot past the splash screen nor can I access recovery mode.

Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key

otyg said:
Install Kies 3 from Samsung and try the tools -> emergency firmware recover option before anything else gets messed up.
Odin is not safe to mess around with, if you accidentally check a wrong option or use any field other then AP, you might end up with perm brick
Sometimes the vol keys are reversed try Power + the other vol key
Click to expand...
Click to collapse
Also, another thing is the when I plug it in and press the power button it lights up and shows the battery icon with no charge stuck in a loading icon that is not animated.
I will try your suggestion but I had already try (on Kies) Update and Recovery but it didnt work (perhaps because of the tablet being in Downloading mode?)
UPDATE: Kies 3 wont recognize tablet, even in Downloading mode (which is the only mode I can access).
Thanks!

This thread is very old. But I've the same problem, stuck at samsung logo and only get into download mode. Accessing the twrp recovery mode is not possible. I've not flashed the device and the battery had over 90% percent. I started the device suddenly it turned of and it was not possible to start it again. Has anyone solved this problem?

I didn't thought that the battery was the problem, because one time the devices started and showed about 90%, but it was the battery. The batteries are very bad for this device, this is my third one.

[Q] Unable to flash to stock with odin / having two 0 directories

So newb questions and might have been answered but I have been unable to find the answer I'm looking for.
Background:
SGH T999
Original I was on 4.1 stock. I used towelroot and was able to root and all that jazz. I uploaded an old version of CWM to my phone and was unable to flash and ROMs, they would all hang on the Samsung Galaxy SIII screen.
I updated CWM to put on a Cyanogen Mode ROM and all was good. I tried out a couple other ROMs then decided I wanted to go back to stock and see how stock 3.3 or 3.4 was. I tried using Odin to bring back to stock and no luck. I then installed PhilZ recovery and booted to Wicked ROM for 4.1. After this I got current TWRP and tried to update other roms. I went into ROM manager switched over to CWM 6.0.4.5 then updated my kernel. At some point along the way I noticed that on the internal sd card I have a 0 directory inside my 0 directory.
Now when I reboot my phone into Recovery mode I see a Samsung Galaxy SIII screen with the Cyanogen guy on it, then it loads to CWM but nothing is on the screen but the hat, then after a couple of seconds it loads to a Samsung screen quickly, then to the Samsung Galaxy SIII and hangs indefinitely. I'm still able to get the phone to go into download mode fine. Now I'm trying to just bring back to stock but not having any luck. Here's my repro:
1. Put hardware into download mode (HOME + Vol Down + Lock).
2. Open Odin 3.09 as Admin (I'm using Win 7).
3. Connect hardware to computer (Odin recognizes 0:Com5).
4. Place "T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5" in AP field.
5. With only "Auto Reboot" and "F.Reset Time" selected press Start button.
RESULT:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Then on my hardware I get
ODIN MODE
PRODUCT NAME: SGH-T999
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Offical
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
SW REV CHECK FAIL : Fused 1 > Binary 0
Click to expand...
Click to collapse
Any idea's how I can bring this back?

tiger_johnson said:
*snip*
Any idea's how I can bring this back?
Click to expand...
Click to collapse
Hmm, if the device is recognized in your PC by ODIN there's still hope. I personally recommend TWRP (LINK for latest ODIN flashable version) for everything as CWM has caused havoc with my phone before. Stay away from it. IF you can still access recovery, do format everything, including the internal SDcard. Also please use the PIT file when trying to use ODIN for the MD5 firmware you're choosing. LINK for the PIT file (choose your model's PIT and put it on the PIT part of ODIN then proceed on flashing the MD5 firmware - credit goes to DocHoliday for the PIT files). That little file can sometimes fix stuff when trying to ODIN the device back to stock firmware. Just giving ideas, don't give up and best of lucks!

You can't flash MD5. It looks like you are currently running MJC base firmware which means you can ONLY flash MJC or NC2 with Odin. Do not try to downgrade via any method or it will hard brick your device.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
---------- Post added at 12:25 AM ---------- Previous post was at 12:23 AM ----------
"SW REV CHECK: Fused 1" means you currently have MJC. It will change to Fused 2 if you update to NC2. (If I'm remembering all those nemesis right).
Just FYI in case anyone was wondering.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Memory Damaged message, won't reset, recovery mode fails (red triangle,Android down )

Hi, I've searched hi and low for help, but can't find anything that seem to apply to my phone or case. I have a Canadian Mobilicity S3 model SGH-T999V that just bricked itself. Everything is official other than I unlocked it to switch to Wind: Binary Count = 0.
The Story: Last week (Tuesday Sep 22nd 2015) The phone restarted a few times for no apparent reason, then the next day errors about missing files started to pop up to the point that I had to reset the phone to be able to use it. Start fresh all good for a week, then one restart yesterday (Sep 30) and this morning I have a screen that says: "Device Memory Damaged - the data partition has been corrupted.you need to reset your device to factory defaults.this will erase all your date. (reset device button)" I press the button nothing happens, so I take out the battery, leave it while at work, then try again: same thing - I try to reboot into recovery but fail: I get a down android with an open belly cover and a red triangle picture for a bit and the phone reboots back to the damaged memory screen. I can get into the download mode, but Odin doesn't see the phone.
Any advice on how to proceed from here would be greatly appreciated.
I've used Odin before on my Nexus S, but that was many moons ago, it's dead now...
Thanks in advance.

Can you get into download mode? If you can, yet flashing the stock ROM from sammobile.com and flash it using Odin.

Thanks for the reply.
Odin doesn't see the phone and I don't remember exactly how to use it either, but I know it's very model specific, as to files and ROMs to download and install, hence the advise seeking. I guess I'm hoping someone in the know can tell me "follow the instructions for such [more popular] model #, that will work on the 999"...

The T999v is a very popular model in Canada as it was used by Wind and Videotron.
Are you able to boot the phone into download mode? The Samsung drivers are installed? Are you using a Win7 machine?

Yes it boots into Download mode but not into recovery. I have Kies installed along with the drivers, could reinstall that just in case. Running Windows 10 Pro Preview, in the process of upgrading to the final release.

I recommend grabbing the latest firmware from sammobile.com for the phone and flash it in Odin 3.07 with the phone in download mode. I would not bother with Kies.

I've updated my build of Windows 10, that may have been one of my problems, now Odin reacts to the phone but fails:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNH2_T999VYVLFNH2_T999VVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says in red: "Secure Check Fail: aboot
So much for that! guess it's fried at the hardware level.

I'm thinking you are suffering from a hardware failure as stated by the message you mentioned before. It has happened to others and I can't recall anyone having much success in restoring functionality.
If you want to try again though, uninstall kies from your computer as it interferes with Odin. There is also a newer version of Odin, but I doubt that would make much difference on the S3.
If you are unable to get it working again and want a relatively cheap fix, search ebay for a used motherboard or a device that has a broken screen but otherwise works. Then swap out the board.
Sent from my SGH-T999 using Tapatalk

The update is failing because the ROM you are flashing has a bootloader that is older than the version currently installed on the phone as verified by the following stop error in Odin:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!

I have a feeling DocHoliday77 is probably right, I've bought a new phone from my provider for 9$ (Alcatel onetouch Pop D3) and posted a wanted ad for broken S3 ... not ready to completely give up on the S3 just yet, but neither do I have high hopes.
Getting rid of Kies
The firmware is the most recent for the SGH-T999V on sammobile.com - I can try without the V maybe

Only T999V firmware will work on the T999V.
If you are selling it and it has a good working display you should be able to get a decent amount for it still. Not sure how much they are going for these days but it's always been the most expensive and in demand part for the device.

Need help with flashing GT-N7105

My Note 2 randomly started to reboot and got stuck in the GT-N7105 screen. I have never rooted or done anything similar (never tried either). I have no idea what is wrong. It had been restarting randomly at about once a day or once every 2 days.
But here is what I tried from various forums and guides:
1. Removed battery and held power button for up to a minute then tried turning on - Didn't help
2. Help Power+Vol up+Home and tried factory reset. Factory reset failed. (nothing could be mounted) (I removed sd card before doing this).
3. I can get the phone to download mode, but flash fails on Odin. (I downloaded latest firmware for GT-N7105 from sammobiles). Haven't tried using PIT file and re-partition option (too scared).
4. I also tried using the Unified Android Toolkit. It was a failure too.
Other info: 1. I do NOT have USB debugging enabled (I feel so bad for not doing it); 2. Odin shows NAND write failed error.
If anyone can help it would really be great. I mostly got help from this post: http://forum.xda-developers.com/showthread.php?t=2154890 But this is for GT-N7100.

What error did you get in Odin? Did you use the original Samsung cable to flash via Odin? Tried other USB cables and all available USB ports?

audit13 said:
What error did you get in Odin? Did you use the original Samsung cable to flash via Odin? Tried other USB cables and all available USB ports?
Click to expand...
Click to collapse
NAND write failed. Yes I used the original samsung cable, its the best one i have. Tried all available USB ports

What is the actual file that did not flash? Maybe post the Odin log?

audit13 said:
What is the actual file that did not flash? Maybe post the Odin log?
Click to expand...
Click to collapse
This is the .md5 file I used: http://www.sammobile.com/firmwares/download/48001/N7105XXUFOB2_N7105OLBFOD1_XSP/
Odin log:
<ID:0/006> 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/006> Odin engine v(ID:3.1101)..
<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> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

The error after sboot.bin file leads me to believe that the ROM may not be made for the phone or the bootloader in the ROM is too old.
The model # is confirmed as being the GT-n7105 in download mode?

audit13 said:
The error after sboot.bin file leads me to believe that the ROM may not be made for the phone or the bootloader in the ROM is too old.
The model # is confirmed as being the GT-n7105 in download mode?
Click to expand...
Click to collapse
Yes, I'm sure the model number is GT-N7105. Here is what the Download mode screen says:
ODIN MODE
Product Name: GT-N7105
Current Binary: Samsung Official
System Status: Official
Knox Warrant Void: 0
RP SWREV: A2
"Android Logo"
Downloading...
Do not turn off target!!
This screen also stays the same when I'm trying to flash. I'm not sure if that's ok or not.

Everything looks fine. Maybe try a different computer or version of Odin?

audit13 said:
Everything looks fine. Maybe try a different computer or version of Odin?
Click to expand...
Click to collapse
This is what has been bugging me, everything looks fine, but nothing seems to work. I've tried every version of Odin, but I used only one PC. If u have any suggestion on why NAND write would fail, do tell me.
Could it be because of USB debugging not being enabled?
Thanx a lot for your help!

I think you'll need to try another PC.
Odin usually fails to write for five main reasons:
1) nand chip is damaged;
2) USB cable is not compatible with Odin and/or phone;
3) USB port (usually USB 3.0/3.1 port) is not compatible with Odin, phone, and/or USB cable;
4) ROM was not made for the phone;
5) ROM's bootloader is older than bootloader on the phone.