Database Develop

soft bricked?

Hi all,
so i read the PSA and all the other info about bricking/ what not to load etc and took the plunge to update my kernel
Using odin, i flash the safe kernel DAFUQ_N7000_05272012.tar and everything went well and rebooted. Well this is where i'm stuck now
Reboots, i get the samsung screen with the yellow triangle now but that's it. nothing after that.
Read abit more and grab this kernel cm9_safe_kernel.tar and flash this. same thing.
I cannot get into recovery but i can get into download mode.
I read a few things about looking at repartitioning but as i didn't do a full wipe nor did a flash any roms, i don't think that is my issue.
Any suggestions?

flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle

denti said:
Hi all,
so i read the PSA and all the other info about bricking/ what not to load etc and took the plunge to update my kernel
Using odin, i flash the safe kernel DAFUQ_N7000_05272012.tar and everything went well and rebooted. Well this is where i'm stuck now
Reboots, i get the samsung screen with the yellow triangle now but that's it. nothing after that.
Read abit more and grab this kernel cm9_safe_kernel.tar and flash this. same thing.
I cannot get into recovery but i can get into download mode.
I read a few things about looking at repartitioning but as i didn't do a full wipe nor did a flash any roms, i don't think that is my issue.
Any suggestions?
Click to expand...
Click to collapse
Try flash gb rom. http://androidadvices.com/update-galaxy-note-n7000-gingerbread-xxlc1-236-firmware/

Moved To Q&A​
Please post all questions in the Q&A section​

azzledazzle said:
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
Click to expand...
Click to collapse
Do this....

thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care

denti said:
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
Click to expand...
Click to collapse
Flash Full GB STOCK ROM via PC ODIN and start again...
Also sounds a little bit like you were on ICS an have flashed a GB Kernel and rebooted....

denti said:
thanks for the replies but wee confused...
isnt' DAFUQ_N7000_05272012.tar a GB firmware?
also isn't the CM9_safe_kernel.tar a GM firmware to use?
might you be able to suggest a firmware?
without going into much detail, what's the differences between the DAFUQ, CM9_safe firmware vs the GB firmware?
take care
Click to expand...
Click to collapse
Its a kernel only.. Download full GB rom here.
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-N7000 using XDA Premium App

Ok, so i downloaded N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 and tried to flash via odin and it failed
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is the log.
any suggestions? I got firmware DAFUQ_N7000_05272012.tar
thank you

denti said:
Ok, so i downloaded N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 and tried to flash via odin and it failed
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLC1_N7000OXALC1_N7000XXLB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> hidden.img
<ID:0/006> modem.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
is the log.
any suggestions? I got firmware DAFUQ_N7000_05272012.tar
thank you
Click to expand...
Click to collapse
Read this carefully and understand. Is your device 16 gig? If yes. http://nguyenkieuhung1984.blogspot.com/2012/01/how-to-installflash-samsung-galaxy-note_09.html?m=1
Read 3C

azzledazzle said:
flash a full GB firmware with ODIN and you should be fine
Once done, Root and use Triangle Away app to reset counter and remove the triangle
Click to expand...
Click to collapse
Triangle away won't work on GB roms.
Try to reflash CF kernal using PC odin..

Fix it?

Odin help please!!!!

Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks

EFCLEE said:
Hi
Can somebody help me with this problem
Firstly during an official update from 2.3.6 to 4.0.4 using KIES bombed out at 4% so soft bricked is what we call it!!!
Can only boot into download mode so using odin to wack on
"N7000XXLRG_N7000DBTLRG_DBT\N7000XXLRG_N7000DBTLRG_N7000XXLRB_HOME.tar.md5"
Following message appears in Odin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006>
<ID:0/006> Receive Response form LOKE
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there anyway I can force write to it?
Could it be the firmware that is the issue or would I get this on everything I try?
Please help
Thanks
Click to expand...
Click to collapse
Did you select the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.

jeetu1981 said:
Did you selected the firmware .tar file in odin PDA tab only?
This sometimes happens due to bad download file, try flashing some other firmware, preferably GB so that you can wipe if required.
search google with 'Receive Response form LOKE" and you will find lot of people having same issue and most of them able to resolve by flashing different firmware.
Click to expand...
Click to collapse
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?

EFCLEE said:
No I have been adding it to PHONE, is this wrong?
Anyways I just tried it again adding to PDA and this time it gets stuck on
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLRI_N7000OXXLP8_N7000XXLRB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
Any ideas?
Click to expand...
Click to collapse
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.

jeetu1981 said:
Yes, its completely wrong, you should select single firmware .tar in PDA tab only. Try again by rebooting your phone and check if you have kies running, if so close it completely.
SUGGESTION- Do not flash ICS stock rom now, I am not sure what has been messed up by flashing this using phone tab (ICS phone files on GB base, not sure), best is flash stock GB firmware first, then wipe in stock recovery and flash ICS.
Click to expand...
Click to collapse
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!

EFCLEE said:
WOW!!! Restarted phone wacked it into PDA and BAM!! started to copy over!!!
A million thank you's Jeetu1981 your a fkin diamond!!!!!
Click to expand...
Click to collapse
Cool... Consider urself lucky this time
And click on thanks is better than million thanks, lol
Sent from my GT-N7000

[SOLVED] Can't install for latest CWM recovery and CM

Hello all, I'm new.
Last night, I've already flashed to ClockworkMod recovery (5.8.1.8) after following the instruction from wiki, then I formatted all for data, cache, preload and sdcard (except emmc), and then also I tried to download latest version of ClockworkMod recovery and CyanogenMod stable or nightly builds for her Samsung Galaxy Note (GT-N7000) phone.
The biggest problem before I tried to install for stable or latest nightly builds of CyanogenMod, but it doesn't work due for asserting failure (the console log shows 'assert failed: getprop("ro.product.device") == "galaxynote"') as in status 7 of error.
And then, I can't install for latest ClockworkMod recovery while freezes and the message says "Replacing stock recovery with ClockworkMod recovery".
I need to teach for how to install, but could you please help me?
(Note: Sorry for bad English, but I could not understand anymore.)

You can't install recovery directly.. You need to use a custom kernel like Philz or Speedmod. Then you can go about cleaning and wiping.

nokiamodeln91 said:
You can install recovery directly.. You need to use a custom kernel like Philz or Speedmod. Then you can go about cleaning and wiping.
Click to expand...
Click to collapse
I've already cleaned and wiped for her's phone, and then I tried to install for latest Philz' CWM recovery, but what happens... it doesn't work.
So here is the recovery console log.
Code:
This package is for 'galaxynote,n7000,N7000,GT-N700' devices; this is a ''.
E: Error in /emmc/philz_touch_6.07.9-n7000.zip
(Status 7)
Installation aborted.

GrandChaos9000 said:
I've already cleaned and wiped for her's phone, and then I tried to install for latest Philz' CWM recovery, but what happens... it doesn't work.
So here is the recovery console log.
Code:
This package is for 'galaxynote,n7000,N7000,GT-N700' devices; this is a ''.
E: Error in /emmc/philz_touch_6.07.9-n7000.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I meant to say you CANT install recovery directly.
If that does not work then use Philz kernel that's is a tar.md5 file and use Odin to flash on PDA.

Flash philz ((kernel)) from this thread:
http://forum.xda-developers.com/showthread.php?t=1901191
Then you're good to go.

nokiamodeln91 said:
I meant to say you CANT install recovery directly.
If that does not work then use Philz kernel that's is a tar.md5 file and use Odin to flash on PDA.
Click to expand...
Click to collapse
I switched to Windows 7 after boot selection (I have a triple boot with my Debian-based distro, Ubuntu and Windows 7), running/downloading older to latest Odin3, power on to download mode, and then connect into my computer, but it won't appear in the yellow box of USB ID COM after installed/replaced the drivers from zadlg.

Anyone?

GrandChaos9000 said:
Anyone?
Click to expand...
Click to collapse
try installing driver from here.. Once installed connect the phone in normal power on mode and then let windows install the drivers...

nokiamodeln91 said:
Once installed connect the phone in normal power on mode and then let windows install the drivers...
Click to expand...
Click to collapse
Okay... but now what?

GrandChaos9000 said:
Okay... but now what?
Click to expand...
Click to collapse
Then boot into download mode and flash Philz kernel from there... Philz tar.md5 file selected in PDA and phone in download mode.

nokiamodeln91 said:
Philz tar.md5 file selected in PDA and phone in download mode.
Click to expand...
Click to collapse
Is it both all in PDA and phone before installing?

GrandChaos9000 said:
Is it both all in PDA and phone before installing?
Click to expand...
Click to collapse
It is just in PDA, he is saying to put the phone in download mode by pressing volume down+power+home button to be able to do that.

PDA and phone won't install due in the red box of failure, so here is my log.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-n7000.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: I've removed anti-virus and Kies (except for mobile drivers), but it failed again.

Anyone how to resolve this?

It seems you keep flashing PhilZ recovery. Don't do that. You need to flash PhilZ kernel which inlude recovery in it. Download from here latest one.
http://forum.xda-developers.com/showthread.php?p=31911620
Sent from my GT-N7000 using Tapatalk 2

U come from where? Gingerbread/ics/jb n what baseband u use
Phone status
Gingerbread
Ics
Jb?
Baseband?
Make sure philz kernel is compatible u device
GrandChaos9000 said:
PDA and phone won't install due in the red box of failure, so here is my log.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-n7000.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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

AMUK0110 said:
Phone status
Gingerbread
ICS
JB?
Baseband?
Click to expand...
Click to collapse
Uhm... Jelly Bean 4.1 Stock with apps in Germany about her phone.

U baseband?
Etc
GrandChaos9000 said:
Uhm... Jelly Bean 4.1 Stock with apps in Germany about her phone.
Click to expand...
Click to collapse

AMUK0110 said:
Your baseband?
Click to expand...
Click to collapse
N7000XXLSA in baseband version I guess...

And finally, I installed Philz CWM recovery (Version 5.15.0 - CWM base version 6.0.3.7) and it works for XXLTA-ATL baseband instead.
So here is my another log.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.15.0.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> zImage
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)

[Q] HELP. Brick.

So I've been using 4.4 SlimKat for quite a long time now and it has been running quite well. But earlier today out of nowhere the phone started to overheat like crazy and shut down.
I let it cool off for a bit then turned it on, and it got stuck on a bootloop on the Samsung logo.
Recovery works but whenever I try to flash or wipe anything, I get "unable to make /cache" and "Can't find log file" and formatting cache using make_ext4fs and it gets stuck on that.
And I tried installing the stock ROM using ODIN and that didn't work as well, It got stuck on "nand write start!!"
So, Does anyone have an idea on how I'd be able to fix that ?

FI would flash Philz kernel odin version. Then get to recovery, then do 'clean to install rom" then, do wipe dalvik cache, then flash a custom 4.12 rom.zip.
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
FI would flash Philz kernel odin version. Then get to recovery, then do 'clean to install rom" then, do wipe dalvik cache, then flash a custom 4.12 rom.zip.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Still stuck on "NAND write start!!"

Usamovic said:
Still stuck on "NAND write start!!"
Click to expand...
Click to collapse
Which file did you flash?
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
Which file did you flash?
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
This one : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/philz_touch_6.25.0-n7000.tar.md5
I got SetupConnection.. stuck couple of time too.

Usamovic said:
This one : http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/philz_touch_6.25.0-n7000.tar.md5
I got SetupConnection.. stuck couple of time too.
Click to expand...
Click to collapse
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
How many times have you written the same post..? Ha ha... I counted 10...

nokiamodeln91 said:
How many times have you written the same post..? Ha ha... I counted 10...
Click to expand...
Click to collapse
And will continue !
Sent from my GT-N7000 using Tapatalk 2

I blame Phil.
Sent from my Nexus 5 using Tapatalk

AndroidSlave said:
I blame Phil.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It seems Phil is not having time to monitor all his threads.

forest1971 said:
That is the wrong file, find some older file which says kernel and ending with LTA, LT9...
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I flashed an LTA one and it ended up with NAND write start too.
I also have the yellow triangle thing under the Samsung logo now.

Usamovic said:
I flashed an LTA one and it ended up with NAND write start too.
I also have the yellow triangle thing under the Samsung logo now.
Click to expand...
Click to collapse
Should post log of odin as well.
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
Should post log of odin as well.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.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> zImage
<ID:0/003> NAND Write Start!!

Usamovic said:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.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> zImage
<ID:0/003> NAND Write Start!!
Click to expand...
Click to collapse
That is the correct file.
I would do:
- make sure you have uninstalled kies. Disable all antivirus.
- download an other file and flash again.
- if not work, then flash together with the stock pit file and tick repartition. (Stock pit can be download from dr.ketan thread in the sticky.
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
That is the correct file.
I would do:
- make sure you have uninstalled kies. Disable all antivirus.
- download an other file and flash again.
- if not work, then flash together with the stock pit file and tick repartition. (Stock pit can be download from dr.ketan thread in the sticky.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Still the same problem.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLT9-ORA-5.11.2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-XXLTA-ATL-5.11.2.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!

You mentioned earlier can still get into recovery? If so should try to use hg42 partition scanner.
Also I would try to use heimdall to flash. For me it works better than odin.
Sent from my GT-N7000 using Tapatalk 2

forest1971 said:
You mentioned earlier can still get into recovery? If so should try to use hg42 partition scanner.
Also I would try to use heimdall to flash. For me it works better than odin.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Recovery stopped working somewhere throughout this whole thing.
Thank you so much for helping BTW, I'm fully aware it's a hassle.

Usamovic said:
Recovery stopped working somewhere throughout this whole thing.
Thank you so much for helping BTW, I'm fully aware it's a hassle.
Click to expand...
Click to collapse
While all these flashing,, are you rebooting the phone into download mode? Back to back flashing will not work,, before every flash, power off and reboot into download mode.

nokiamodeln91 said:
While all these flashing,, are you rebooting the phone into download mode? Back to back flashing will not work,, before every flash, power off and reboot into download mode.
Click to expand...
Click to collapse
Yeah, I reboot every single time.

Usamovic said:
Yeah, I reboot every single time.
Click to expand...
Click to collapse
Alright... Try another PC and cables if possible.

[SOLVED FREE] URGENT Help before SERVICE [SOLVED FREE]

Hi, I tried to flash something in odin and my pc stopped usb connection, and now my phone can enter only in download mode.
When I try to flash something odin says write error. I searched on the internet and I saw that it might be an flash lock.
But I dont selected it in odin. I called samsung, and they recommended me a service. And it will be repaired for 28 USD . Can someone help me? As I helped others, now I need your help!
I will sent it to service in 3 days! Also, the repair is not free, because I dont reset binary counter....now is custom (5)

use 3 file rom file

Try wit Secure PIT file

Antox97 said:
Try wit Secure PIT file
Click to expand...
Click to collapse
amir_n71 said:
use 3 file rom file
Click to expand...
Click to collapse
Sorry but no one solution is working. I whink that I can't recover my photos from internal sdcard.
On phone appears: ,,odin transaction fail,, when I am connecting it....and on pc ,,write fail,,
What TO DO???!!!

All depends on what file the USB connection stopped.
If it was fat.bin, then it's pretty much dead.

MrMateczko said:
All depends on what file the USB connection stopped.
If it was fat.bin, then it's pretty much dead.
Click to expand...
Click to collapse
It says write error on any file. I don't know why, I never checked flash lock.
Also 1 click unbrick for samsung devices in not running on my pc.
(flash progress won't start)
-----2 days until service

Odin messages
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

MaDaLiNoSt said:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've NEVER seen that before It stop almost imediately Before flashing anything .. My Mini 2 stops in "Fat.Bin" .. Thats all .. did it showed any message at your phone ?? like "Secure Check Fail Id:0x95" ??

I never seen it too! I think that you must send your device into assistance, I'm really sorry

PHOTOS
Ezzam_Itachi said:
I've NEVER seen that before ... Did it showed any message at your phone ?? like "Secure Check Fail Id:0x95" ??
Click to expand...
Click to collapse
Now you can see how my phone is looking:
I see firmware error on power and recovery mode.
When I connect the usb cable in phone, I get error!
What to do??!! Next morning, tomorrow I will send it into service :crying:

Happy again
Hi, and thank you for all your feedbacks (posts). Now I recovered my phone with some pc softwares and everything is ok :victory:
Odin Log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_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> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> fat.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> appsbl
<ID:0/003> oemsbl
<ID:0/003> partition.bin
<ID:0/003> qcsbl.mbn
<ID:0/003> qcsblhd_cfgdata.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
PC Screenshot:
Note: Next time when someone will have connecting issues with phone, is easy to post here and I will give help !
Do not create a new thread, because there are too many threads based same error. (eg. recovery ramdump or not working)

Owh, now I remember that writings.. For that I have sent my device into service :/
When your device are coming back, don't flash any firmware! If you have a NFC model, you must flash a NFC model like XXLD2!

Waw !! You made it !! :victory: okay now I need your help ... How did you do that ?? I oftenly flash my phone with odin .. Unfortunately, It never .. NEVER pass the flash ..It always failed .. Maybe with your solution I can get this done .. Thanks for your help !!

Little Flashing TUT
Ezzam_Itachi said:
How did you do that?
Click to expand...
Click to collapse
Download mini 2 firmware from SamMobile
Click to expand...
Click to collapse
Simply enter the model number of your device in the search box and a list of latest firmwares will come up. To download a firmware, you will need to be logged in to your SamMobile account using your username and password.
Click to expand...
Click to collapse
Demo Firmware list:
Disclaimer
SamMobile & me are not responsible if you brick or damage your device by using the files available on SamMobile Firmware Portal. You are doing all at your own risk! Proceed only if you are 100% sure that you know what you are doing.
Click to expand...
Click to collapse
Download and install compatible Kies from Samsung
Select Kies 2.6 for devices launched before September 2013
Click to expand...
Click to collapse
Now lastest drivers should be installed via kies application.
Download and install Odin3 from internet.
Click to expand...
Click to collapse
Now boot phone in download mode via an key combination: Volume down + home + power
If your device is not recognized, or windows failed istalling drivers (CDC or other driver)
use Zadig to force reinstall drive. Zadig can be found in heimdall unbrick pack for windows.
Click to expand...
Click to collapse
An alternative of Zadig is Microsoft Device manager. Select uninstall device from app menu, and then move usb cable to another port.
This solution might not solve your problem.
Click to expand...
Click to collapse
Good luck with flashing!
About you fat.bin error:
-Download another compatible rom
-That's it! : )

Amazing! Congratulations

Antox97 said:
Amazing! Congratulations
Click to expand...
Click to collapse
Thanks :laugh:

Thanks !!

Ezzam_Itachi said:
Thanks !!
Click to expand...
Click to collapse
No problem
Sent from my GT-S6500D using Tapatalk 2