Bricked N7100 - Galaxy Note II Q&A, Help & Troubleshooting

Hello, my friend briked her N7100. She says it went out of battery, and since then she could not turn it on anymore.
I tried to recover it with Kies, but it says the device wasn't recognized, and asks to reboot and try again, no matter what I do, it wont recognize it. I downloaded the firmware from SamMobile, and tried with Odin, but no success too. I get these errors:
Without PIT file:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try with PIT_N7100_16GB_20121102.pit, it logs:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried ODIN-KashaMalagaTOUCHCWMRecovery-V6.0.3.0 too:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
How it looks when turned up on any other option than download mode:
imgur.com / b63BPxL
Is there any way to unbrick it?

Ok, it suffered from SDS... Is there any way to recover from that?

replace chip

Related

[Q] Phone stuck at splashscreen odin fails

Hello my friend gave me his note II to look at ( GT-N7100) , he has never tried to do anything to it other than use it regularly a.k.a no modding etc..
His phone suddenly just started to hang at the screen where it says Galaxy note II. Recovery mode does not work but download mode works. I downloaded a stock firmware to flash on ODIN but I receive this error every time.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNG3_N7100AMNFNG2_N7100BVUFNE1_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> 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)
Is the hardware on the phone fried the eMMc chip ?
All the help would be greatly appreciated !!
I also tried flashing a recovery tar file and this is what I get
<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> recovery.img
<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)

Galaxy S4 i545 Bricked! Help a guy out?

Hey all. Recently i tried to flash stock android to my i545 and it soft bricked on me. I've tried odin numerous times, every version of it I could find, with many different mirrors on the .tar. I've also tried using .pit to no avail. My odin log is as follows for each attempt:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried kies with no luck due to it never freaking recognizing the device, and yes ive updated the drivers. Ive done all these steps with many different usb's, usb ports, computers, and versions of odin. Is there anything i can do or should i just start looking for a new phone? Help would be greatly appreciated
Make sure that you are flashing the correct Odin for the bootloader you are on download Samsung info and post baseband and bootloader and can point you in the right direction

[Q] [Help] NAND Write Start!!

I was on T889UVALL4, use Odin to flash root66_TMO_T889UVUCMK7_2.tar.md5, got PASS, phone stuck in boot loop, can not get into recovery mode, so I try flashing again and got the following error. ( i flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user _low_ship.tar.md5 with the same result)
Please help.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVUCMK7_2.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> SingleDownload.
<ID:0/003> boot.img
<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)
here is the Odin log for stock firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user _low_ship.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> SingleDownload.
<ID:0/003> boot.img
<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)
My question is: Can this be fix with Odin? or do I need to fix a shop that can repair the EMMC? if it is the latter, does anyone know where to find a trust worthy shop with in the San Francisco bay area?
Thanks
onqq said:
I was on T889UVALL4, use Odin to flash root66_TMO_T889UVUCMK7_2.tar.md5, got PASS, phone stuck in boot loop, can not get into recovery mode, so I try flashing again and got the following error. ( i flash KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user _low_ship.tar.md5 with the same result)
Please help.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T889UVUCMK7_2.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> SingleDownload.
<ID:0/003> boot.img
<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)
here is the Odin log for stock firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T889UVALL4_T889TMBALL4_598701_REV04_user _low_ship.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> SingleDownload.
<ID:0/003> boot.img
<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)
My question is: Can this be fix with Odin? or do I need to fix a shop that can repair the EMMC? if it is the latter, does anyone know where to find a trust worthy shop with in the San Francisco bay area?
Thanks
Click to expand...
Click to collapse
I found a pit file and try flashing with Odin, here is the output:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does that mean my EMMC is corrupted and needs repairing? :crying:
Boot into recovery and Factory/Data Reset
See if that helps
Double0EK said:
Boot into recovery and Factory/Data Reset
See if that helps
Click to expand...
Click to collapse
unfortunately, I can't get into recovery.
when I press volume up+home+power button, I just get a flashing Samsung Galaxy 2 logo (aka boot loop hell)
onqq said:
unfortunately, I can't get into recovery.
when I press volume up+home+power button, I just get a flashing Samsung Galaxy 2 logo (aka boot loop hell)
Click to expand...
Click to collapse
Get the tar file for the most recent TWRP and Odin that. Boot into recovery and factory reset. Try booting normally. If that fails try to Odin the UVALJ1 tar by MrRobinson. (2-3 times). Try booting normally. Once you can boot normally go ahead and try the MK7 tar.

flash grand i9082 failing

Hey guys!
Im trying to flash the stock rom, but I just wont work.
Logs:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXUBMGA_I9082OXEBMGA_I9082XXUBMGA_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> vc-firmware.img
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> BcmCP.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
I get failure are BcmCP.img
I am using a Odin 3.04
Still getting error, tried different USB ports, different cables, plenty different things
Can someone help? My phone is unusable

I cannot downgrade from Android Oreo to Nougat.

I have in the past downgraded to Nougat from Oreo but this time I cannot and I don't know why. I'm doing everything the exact same way I did the last time but it doesn't work this time. It fails in every version of Odin I have tried. I have even tried the PrinceComsy edition and still no dice. On the Download Mode screen it has a Fused number and a Binary number. Also it has something that says ABL and I don't know what that is. I look at the log but don't understand what the log is trying to say. If anyone can help me out that would be awesome. Also here is the log report:
<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.1203)..
<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> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<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> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> Removed!!
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/005> Added!!
Me too wtf this is crazy. A $1000 device that we cant downgrade if we want or even get an unlocked bootloader....

Categories

Resources