Develop Bugs

Pleaseeee helpppppppp....real emergency :'(

i was running creed's rom v2.1 and was wishing to upgrade my firmware,PDA n CSC with files in doky's thread.
i was reading about preparing phone before odin flash on internet and found that its advisable to hard reset mobile before flashing through odin..
so i got this code *2767*3855# and i entered it and after a while my phone rebooted and was stuck at boot animation with continues boot loops..
i quickly removed the back cover and removed the battery for 30 sec and put it back....tried to go into recovery mode using normal [volup]+[home]+[power] and it didint enter recovery , instead rebooted again and same..boot loops
i then assumed that my phone was bricked
i then went on to this tread for soft/hard brick http://forum.xda-developers.com/showthread.php?t=1498327
followed that link to the forum....decided to flash my phone to stock as MY PHONE COULD BOOT INTO DOWNLOAD MODE AND NOT RECOVERY
i downloaded the S5360XXXXX_S5360XXXXX_S5360XXXXX_HOME.tar.md5 file...opened odin v1.85 as admin in win7....then loaded that file onto PDA and left all other boxes to default ,,,connected my mobile via USB in recovery mode and i got the following error...i keep getting this error....no matter what i do...even earlier i tried installing doky's packages using odin and my odin gave same error...i tried both odin version....v1.85 and v1.84
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6102DDLA3_S6102ODDLA3_S6102DDLA3_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> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP GUYS :'(
WHAT SSHOULD I DO NOW ? :'(
IS THERE ANYWAY OUT ?

machinehead121 said:
i was running creed's rom v2.1 and was wishing to upgrade my firmware,PDA n CSC with files in doky's thread.
i was reading about preparing phone before odin flash on internet and found that its advisable to hard reset mobile before flashing through odin..
so i got this code *2767*3855# and i entered it and after a while my phone rebooted and was stuck at boot animation with continues boot loops..
i quickly removed the back cover and removed the battery for 30 sec and put it back....tried to go into recovery mode using normal [volup]+[home]+[power] and it didint enter recovery , instead rebooted again and same..boot loops
i then assumed that my phone was bricked
i then went on to this tread for soft/hard brick http://forum.xda-developers.com/showthread.php?t=1498327
followed that link to the forum....decided to flash my phone to stock as MY PHONE COULD BOOT INTO DOWNLOAD MODE AND NOT RECOVERY
i downloaded the S5360XXXXX_S5360XXXXX_S5360XXXXX_HOME.tar.md5 file...opened odin v1.85 as admin in win7....then loaded that file onto PDA and left all other boxes to default ,,,connected my mobile via USB in recovery mode and i got the following error...i keep getting this error....no matter what i do...even earlier i tried installing doky's packages using odin and my odin gave same error...i tried both odin version....v1.85 and v1.84
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6102DDLA3_S6102ODDLA3_S6102DDLA3_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> sbl.bin
<ID:0/005> BcmCP.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP GUYS :'(
WHAT SSHOULD I DO NOW ? :'(
IS THERE ANYWAY OUT ?
Click to expand...
Click to collapse
try updating thru kies or flashing custom rom...

zeusseuz said:
try updating thru kies or flashing custom rom...
Click to expand...
Click to collapse
but sir how can i ?
odin keeps giving me that error with my phone
it cant even enter recovery mode....nor does it boot completely...just has boot loops
please suggest me a way out

budy the file you try to flash its not right.its one file and odin dont suport it for our phone.go to development section and find odin firmware packages by Docky.download yours and flash it!you are ready!report back if need more help

termagazis said:
budy the file you try to flash its not right.its one file and odin dont suport it for our phone.go to development section and find odin firmware packages by Docky.download yours and flash it!you are ready!report back if need more help
Click to expand...
Click to collapse
sir....i tried already.......and after you said so//..i just tried again.....here it is..same error
<ID:0/005> Added!!
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

machinehead121 said:
sir....i tried already.......and after you said so//..i just tried again.....here it is..same error
<ID:0/005> Added!!
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
so the firmware you downloaded was one file or 3 files?

termagazis said:
so the firmware you downloaded was one file or 3 files?
Click to expand...
Click to collapse
3 compressed files sir
PDA_S5360_DDLA3
MODEM_S5360_DDLA2
CSC_S5360_ODDLA2

machinehead121 said:
3 compressed files sir
PDA_S5360_DDLA3
MODEM_S5360_DDLA2
CSC_S5360_ODDLA2
Click to expand...
Click to collapse
ok just checking your steps.
so you put pda_s5360 in pda field
modem in phone field
csc in csc field
right?and you didnt check the repartition ?

At first, I think Your phone wasn't bricked, it was just a slight boot-loop.
Maybe You pressed the buttons in wrong tact.
As long as you see boot animation, the recovery and download menu 100% surely accessible.
Try again to go download monde, flash one of my packages (avoid one-file packs)!
If got boot loop, then go to recovery (follow my hints in post #2 of Odin packs topic to access recovery and download mode)
...then wipe cache and data!
Hope you succeed!

termagazis said:
ok just checking your steps.
so you put pda_s5360 in pda field
modem in phone field
csc in csc field
right?and you didnt check the repartition ?
Click to expand...
Click to collapse
yup.....exactly...all steps neatly followed as mentioned in doky's post

machinehead121 said:
yup.....exactly...all steps neatly followed as mentioned in doky's post
Click to expand...
Click to collapse
weird.try another firmware

Doky73 said:
At first, I think Your phone wasn't bricked, it was just a slight boot-loop.
Maybe You pressed the buttons in wrong tact.
As long as you see boot animation, the recovery and download menu 100% surely accessible.
Try again to go download monde, flash one of my packages (avoid one-file packs)!
If got boot loop, then go to recovery (follow my hints in post #2 of Odin packs topic to access recovery and download mode)
...then wipe cache and data!
Hope you succeed!
Click to expand...
Click to collapse
not sure about slight boot loop sir...but it was stuck on boot anim for quite a long time....
i did sir..i tried flashing only 1 of your package....modem....and same error again
and i still cant enter recovery mode....download mode is still accessible....but now....my phone is not even able to go up till boot anim :| its just stuck on samsung logo

termagazis said:
weird.try another firmware
Click to expand...
Click to collapse
i tried single packs as well sir.....like just pda...or modem......still same error.....odin aint working no matter what i do "(

machinehead121 said:
i tried single packs as well sir.....like just pda...or modem......still same error.....odin aint working no matter what i do "(
Click to expand...
Click to collapse
i mean download another firmware from doky put all files and flash.another firmware different than that you try

On SAMMOBILE there is two DDLA1 packs, one of them (named S5360DDLA1_S5360ODDLA1_ODD.rar ) contains 4 or 5 files.
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-S5360&r=2#regiona
Download and flash it, with the bootloader part as well!
Put "DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5" to the bootloader, and the other parts as usual (PDA, MODEM, CSC)
PIT and repartition NOT NEEDED!

termagazis said:
i mean download another firmware from doky put all files and flash.another firmware different than that you try
Click to expand...
Click to collapse
ok sir...it is gonna take time for me to download the packages again...
or should i just just take my phone to samsung service centre ?

Doky73 said:
On SAMMOBILE there is two DDLA1 packs, one of them (named S5360DDLA1_S5360ODDLA1_ODD.rar ) contains 4 or 5 files.
http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=GT-S5360&r=2#regiona
Download and flash it, with the bootloader part as well!
Put "DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5" to the bootloader, and the other parts as usual (PDA, MODEM, CSC)
PIT and repartition NOT NEEDED!
Click to expand...
Click to collapse
oh i searched that file and iam downloading it now sir
gonna try this one too *fingers crossed*
is this a serious issue sir ?

btw, Kies has to be closed when flashing via Odin!

doky73 said:
btw, kies has to be closed when flashing via odin!
Click to expand...
Click to collapse
omg...sir i wanna thank you alotttttttttttttt !!
It worked :d
hell your awesome sir ! :d
hats off to you.
Wish i could do something more than pressing thanks button..but i can wish goodluck for you and your future projects =)
once again thanks alot sir !

...........

Soft Bricked, No recovery Galaxy Pro 8.4

Hello guys.
Im new to this forum and I have to say it is amazing but, unfortunately, nothing available could helped me.
My Galaxy Tab Pro 8.4, I believe, is soft bricked, I cant access recovery mode. I have tried flashing Stock ROM, TWRP (again), CWM, CF_Autoroot. I even opened the tablet and removed the battery but it still didnt work.
I had CM12 installed and it prompted me to install a nightly, so I did. After the process was done and the tablet booted I kept getting the error and pop up saying "Unfortunately, Google Play services has stopped working."
So, I tried to install Gapps again but it just made it worst this time. So, I tried backing up (I believe I didnt wipe or whatever is called before backing up) and after this my tablet wont work.
The tablet turns on only when plugged in. I can only see three different screens - battery with loading unanimated loading icon, splash screen, and I can enter download mode. I tried to use Kies but that didnt work.
I read on one forum that maybe it could that the NAND rw was corrupted but I do not know how to fix it. Also, something about the kernel, but I do not want to mess anymore without somebody's expertise.
I have looked everywhere but I couldnt find anything, so I decided to post and see if anyone would help me. Thanks in advanced.

Still...
Jessooca said:
Boot into download mode.
download Odin here: ...
download your latest stock rom. here ...
Use Odin to Flash the stock tar or md5 {whichever it is} in Odin flash it in the PDA slot, don't check anything just put the stock tar or md5 in that slot it should do it's thing. wait for it to check the file and flash away.
Let me know what happens
-- if it bootloops after you've flashed it, just boot into stock recovery and do a factory reset. Then reboot and it should boot back up good as new.
*On a side note, some people forget to extract the md5 file from the file they download so if Odin doesn't find your stock rom you downloaded, make sure the md5 doesn't need extracted.
Since you've got Download mode, we can get you back up and running.
Click to expand...
Click to collapse
Hello, I want to thank you for taking your time and helping me but unfortunately it still dont work. After it is done flashing successfully, the tablet auto reboots and stays stuck in the splash screen until I unplug it or enter download mode again. I cannot enter custom nor stock recovery mode. If I hold the necessary keys to enter recovery mode it only shows the splash screen, if I keep holding the keys down it turns off an immediately turns on into the splash screen.
Thanks for your help, though.
Below is the Odin message (though I do not think you need it):
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANK1_T320XAR1ANK1_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> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Thanks!
Jessooca said:
Give me just a few minutes and i'll tell you what to do next, you're almost there!
Click to expand...
Click to collapse
Ok, I will. Again, I really want to thank you for helping me, and even if we cant fix it I will be very grateful.

Thanks Jessooca, fixed my Galaxy tab 2 pro
Jessooca said:
Boot into download mode.
download Odin here: http://androidhost.org/get/PVAIv
download your latest stock rom. here: http://www.mediafire.com/download/ul9d01zlrq3dl72/T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5l
Use Odin to Flash the stock tar or md5 {whichever it is} in Odin flash it in the PDA slot, don't check anything just put the stock tar or md5 in that slot it should do it's thing. wait for it to check the file and flash away.
Let me know what happens
-- if it bootloops after you've flashed it, just boot into stock recovery and do a factory reset. Then reboot and it should boot back up good as new.
*On a side note, some people forget to extract the md5 file from the file they download so if Odin doesn't find your stock rom you downloaded, make sure the md5 doesn't need extracted.
Since you've got Download mode, we can get you back up and running.
Click to expand...
Click to collapse

Yes I do, but your suggestion fixed my issue and felt you deserved the credit.

Problems with S4 mini GT-I9195 (loop, can'tacess recovery mode)

Hi guys!
i recently got my s4 mini bricked, so following some instructions on this forum i could debrick my cel phone, but I'm still with some problems.
- My cel phone stay on loop with the logo of sansung
- I can acess the download mode BUT I CAN'T ACESS THE RECOVERY MODE!
- When I plug the usb cable it apears the batery image and the cel starts without I press anything, it doesn't just stay charging.
I had download the firmware from sammobile, the correct to my country (Brazil) and did all correct following the tutorials, using odin and everything, but it don't work!
Could someone pleeeeeease help me!!!

Post odin logs

Davidich said:
Post odin logs
Click to expand...
Click to collapse
Thanks for you fast reply!
here's my odin log:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/008> tz.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> NON-HLOS.bin
<ID:0/008> cache.img.ext4
<ID:0/008> hidden.img.ext4
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/008> Added!!
I don't know if it say something, but i saw an another s4 mini in download mode on the internet, and in the corner appears this:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Sansung Official
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
And when I put mine in download mode, also appears this:
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Sansung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
there's more in my than in the other, there's why this?
I didn't say but I can't acces recovery mode because the screen appear, with recovery booting write on teh corner, but the phone restart to the normal mode and stay in the loop

If you use kies try to close all kies processes in task manager...and if you have a antivirus disable it because it can close your firewall...also try to change the usb port

Davidich said:
If you use kies try to close all kies processes in task manager...and if you have a antivirus disable it because it can close your firewall...also try to change the usb port
Click to expand...
Click to collapse
I made all this and without success , here is the odin log:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> system.img.ext4
<ID:0/007> tz.mbn
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After the odin, the phone restart and stay in the loop.

Try another rom from sammobile

Davidich said:
Try another rom from sammobile
Click to expand...
Click to collapse
I've tried at least three of them, now I'm downloading another, but i don't know if will change something
that I said on my second post, about waht is write on the corner of the download mode, doesn't mean nothing?

The information in download mode is OK. What were you running before you bricked your phone?

RuffBuster said:
The information in download mode is OK. What were you running before you bricked your phone?
Click to expand...
Click to collapse
Practically nothing, I was talking on the whatsapp and I locked the phone and sleep, when I wake up it was bricked :/

Unfortunately there seems to be a few of these phones that just die all of a sudden. May well be a corrupt internal memory. If you weren't doing anything unusual to your phone and Stock ROM doesn't work then this may well be the case. But don't take my word for it it may be something else.

RuffBuster said:
Unfortunately there seems to be a few of these phones that just die all of a sudden. May well be a corrupt internal memory. If you weren't doing anything unusual to your phone and Stock ROM doesn't work then this may well be the case. But don't take my word for it it may be something else.
Click to expand...
Click to collapse
I hope a lot to don't be this, I will keep trying, but it's being a lot complicated!
If somebody still can help me would be awesome!

julioghigi said:
I hope a lot to don't be this, I will keep trying, but it's being a lot complicated!
If somebody still can help me would be awesome!
Click to expand...
Click to collapse
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
On your logs from Odin it was Bootloader Version 1 , so your running JB V.4.2.2 ? And your tried to update in KitKat?

bierma32 said:
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER AP SWREV: 1
WRITE PROTECTION: Enable
On your logs from Odin it was Bootloader Version 1 , so your running JB V.4.2.2 ? And your tried to update in KitKat?
Click to expand...
Click to collapse
Yes I flashed JB V.4.2.2 with odin, and I also tried to update in kitkat, but with the same effect
I want to ask, I had some problens with the ear speaker of the phone and I broke the flat of these, so I'm doing all thiss without the ear speaker, would be this the problem? like the phone doesn't detect this and don't start?

Now I tried to update to kitkat 4.4.2 again to look de bootloader version, and it keep on version 1, should be this?
I tried to update to kitkat 4.4.2 of Russia, and appear those messages
Set warranty bit : system
Set warranty bit : cache
Set warranty bit : hidden
Secure check fail : modem
Why???

RuffBuster said:
Unfortunately there seems to be a few of these phones that just die all of a sudden. May well be a corrupt internal memory. If you weren't doing anything unusual to your phone and Stock ROM doesn't work then this may well be the case. But don't take my word for it it may be something else.
Click to expand...
Click to collapse
Hi!
If my internal memory is corrupted, there is a way to correct by sd card mode? or by JTAG? or the only way to save the phone is changing the eMMc chip?

Hi julioghigi. Did you ever manage to solve this? I am facing the same issue and I am clueless...

Similar problem here
Similar problem for me and still no solution :s
Link to thread here.

same here, any solution??

Same problem
Sertico said:
same here, any solution??
Click to expand...
Click to collapse
Hi Julio i send you inbox...

rogersc79 said:
Hi Julio i send you inbox...
Click to expand...
Click to collapse
Lucky Sertico, Christmas father came early for ya
Cheers

Stuck at Samsung Logo Tmobile Note II (T889)

Hello ! All
Couple of days ago my phone shutdown while it was on 7 % . from then whenever I try to charge or connect. It shows me SamsungNote II logo or when I pull the battery out and put it back and connect the cable it shows me empty battery logo (inside it refresher circling).
What I have done so far......
Factory Reset (Vol up /Home/Power)
I tried to reset to factory as soon as I select delete all data and select yes it restarts and back to Samsung Logo......
Download Mode (Vol Dwn /Home/Power)
I can get into Download Mode but It doesn't show up in the odin...my other note II pops up but not this phone.
Changing Ports/Cables
I have changed ports/Cables but nothing worked it out , other Note 2 which I have picked every cable/port ...
Led Lights : I dont see any lights flashing .......
Need Help ..Thanks

Could it be a battery problem?

audit13 said:
Could it be a battery problem?
Click to expand...
Click to collapse
the batteries working fine with my other Note II (T889), How about charging port is bad ????

Yes, could be a bad USB port which causes the phone to not appear in Odin.

How did it go? My Note II just had the same thing and I couldn't even get to recovery.

testrider said:
How did it go? My Note II just had the same thing and I couldn't even get to recovery.
Click to expand...
Click to collapse
Does it go in Download Mode ????
remove battery ...Put it back in (Remove sim/Sd card)
Hold Power /Home /Vol Down
or
Hold Power /Home /Vol Down ..Let go Power button
This is what I am planning to do
ordered the Charging Port Dock ..going to replace it ....
After search came to know few things
1. Bad Charging port
2. Charger/cable is not compatible i.e same voltage with Note 2
3. Batteries in the market are bad ..they say its OEM but they are bad (Found OEM battery which is $13)

Thank you for your reply and I appreciate it!
I already searched here and found no solution of my problem. I hope you could help me out.
- I have my Note II for 3 years and it never had any problem until today, when it rebooted by itself and now stuck at "Galaxy Note II" screen. I have tried all of the following:
1) Removed battery, retry many many times, same thing
2) Try to put it in recovery mode by VOL_UP+HOME+POWER, the same "Galaxy Note II" showed up and nothing further
3) I was able to put it in download mode but that didn't help
4) I tried different battery, same thing
5) when I plugged in the USB charger, the battery icon showed up with no battery level and only a circle on top of it.
Please advise what I should do next? My Note II was running stock firmware 4.1.2 and rooted. No CWM. It's a T-Mobile (model SGH-T889) if that makes any difference.
THank you very much in advance!
Mike

testrider said:
Thank you for your reply and I appreciate it!
I already searched here and found no solution of my problem. I hope you could help me out.
- I have my Note II for 3 years and it never had any problem until today, when it rebooted by itself and now stuck at "Galaxy Note II" screen. I have tried all of the following:
1) Removed battery, retry many many times, same thing
2) Try to put it in recovery mode by VOL_UP+HOME+POWER, the same "Galaxy Note II" showed up and nothing further
3) I was able to put it in download mode but that didn't help
4) I tried different battery, same thing
5) when I plugged in the USB charger, the battery icon showed up with no battery level and only a circle on top of it.
Please advise what I should do next? My Note II was running stock firmware 4.1.2 and rooted. No CWM. It's a T-Mobile (model SGH-T889) if that makes any difference.
THank you very much in advance!
Mike
Click to expand...
Click to collapse
Same here bought in jul 2013 (little over 3 yrs)
at this moment we are in the same boat
Still it is a soft brick ..with Note II T889 there is issue, usually it happen when battery drains out completely .....
once I replace the charging port and put OEM battery will let u know.
I am not sure that I can share ebay links here ....
********did u try to connect via odin in download mode ???

No, I have not tried to connect ODIN. I tried Samsung Kies and it does not see it. At this moment, I have no way to charge my battery or check battery level so I don't want to reflash the stock firmware (yet), otherwise, if it dies in the middle I guess I will be in bigger trouble
Mine was running stock Samsung 4.1.2 and rooted. Yesterday, it was working fine then it rebooted itself and hung on "Galaxy Note II" screen forever...

testrider said:
No, I have not tried to connect ODIN. I tried Samsung Kies and it does not see it. At this moment, I have no way to charge my battery or check battery level so I don't want to reflash the stock firmware (yet), otherwise, if it dies in the middle I guess I will be in bigger trouble
Mine was running stock Samsung 4.1.2 and rooted. Yesterday, it was working fine then it rebooted itself and hung on "Galaxy Note II" screen forever...
Click to expand...
Click to collapse
here is the update
I have replaced the charging port ....Now my phone is getting picked by Odin ..going to flash the stock ROm first tonight
hope it helps you ........Also I am pretty sure battery got some issues too .........

I just reflash the stock Samsung 4.1.2 firmware (downloaded from sammobile) and while ODIN completed successfully, the same thing happened. It still stuck on "Galaxy Note II". here was the progress (ODIN connected to it just fine) and I still could not get into RECOVERY by VOL_UP+HOME+POWER.
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> sboot.bin
<ID:0/005> tz.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

testrider said:
I just reflash the stock Samsung 4.1.2 firmware (downloaded from sammobile) and while ODIN completed successfully, the same thing happened. It still stuck on "Galaxy Note II". here was the progress (ODIN connected to it just fine) and I still could not get into RECOVERY by VOL_UP+HOME+POWER.
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> sboot.bin
<ID:0/005> tz.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
check this page : Do I need to reset the Binary flash counter when already tripped?
http://www.androidayos.com/2013/04/...note-2-sgh-t889-to-original-stockromfirmware/

No you don't. You reset it only when you want to send it back to Samsung for warranty and you don't want them to know.
It doesn't affect the flashing of stock firmware.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
I was running stock 4.1.2, T889UVBMD1, so that was the firmware I downloaded. Unfortunately, after successfully flashing it, it still stuck at the logo!

testrider said:
No you don't. You reset it only when you want to send it back to Samsung for warranty and you don't want them to know.
It doesn't affect the flashing of stock firmware.
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
I was running stock 4.1.2, T889UVBMD1, so that was the firmware I downloaded. Unfortunately, after successfully flashing it, it still stuck at the logo!
Click to expand...
Click to collapse
I am back online
Used odin 3 v 3.10 ...
Stock T889UVUCOH4_T889TMBCOH4_TMB >> 4.3 Jelly Bean
USB Driver 1.5.49.0 (5.0)
Links :
http://androidromupdate.com/tmobile-galaxy-note-2-sgh-t889-stock-firmware/

It's working for you now? What was the Android version you were running before this happened?

I just used ODIN 3.10 and flashed the same stock Stock T889UVUCOH4_T889TMBCOH4_TMB and it still stuck at the logo...
Everything was completed successfully but it still stuck...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> tz.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

testrider said:
I just used ODIN 3.10 and flashed the same stock Stock T889UVUCOH4_T889TMBCOH4_TMB and it still stuck at the logo...
Everything was completed successfully but it still stuck...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T889UVUCOH4_T889TMBCOH4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> tz.img
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
dont know what to say I am no pro here
with my old Charging port when I was plugging it shows me battery and inside circling and with cable when I open I saw samsung logo , I came across a link which said remove the Charging port which could be faulty ...
try that option too ...it cost me only $5.50 and 15 minutes to do the replacement ....
https://www.youtube.com/watch?v=l9e9vIqZOUo
http://www.ebay.com/itm/311475649835?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT

qazafee said:
I am back online
Used odin 3 v 3.10 ...
Stock T889UVUCOH4_T889TMBCOH4_TMB >> 4.3 Jelly Bean
USB Driver 1.5.49.0 (5.0)
Links :
http://androidromupdate.com/tmobile-galaxy-note-2-sgh-t889-stock-firmware/
Click to expand...
Click to collapse
What exactly did you do? Just use ODIN and flash the firmware? That was what I did but mine still stuck...

testrider said:
What exactly did you do? Just use ODIN and flash the firmware? That was what I did but mine still stuck...
Click to expand...
Click to collapse
buy the charging port ...it may be the reason ....
with old charging port ..it was not charging but was still able to bring up logo/Battery sign ....
so it was not completely damaged ...there is no harm in buying only 5.50 ...

I already bought a brand new Samsung battery. I also borrowed a friend's Note 2 to charge the battery before putting it in my dead phone. No luck.
---------- Post added at 08:25 PM ---------- Previous post was at 08:20 PM ----------
I guess I can give it a try...
You replaced the port and did it boot all the way? You said you flashed the stock firmware too? If the port was working after you replaced it, why did you have to flash the stock rom?

Need help un-bricking my kids tab 3 7.0 SM-T210R...

Hi guys, bit of a noob here...I messed up my kids tablet.
It was running NoleKat 2.X, previous to that was running stock 4.4.2.
In an effort to get tablet back to stock to clear up some bootloop issues - used odin to flash stock 4.1.2 it worked no problem except Samsung update to 4.4.2 would no longer work...
so I break out odin again and grab what I think is the right stock 4.4.2 Rom from sammobile....try to flash it, it fails and now tablet only boots straight into recovery <3e>.
I tried wipes from recovery they all fail due to some make_extf4fs failed on dev block.
adb sideload will crash when ROM transfer gets to about 70%.
tablet will not take any other ADB commands
Smart switch and Kies will not reconize tablet say its unsupported - works fine on another tablet.
I can get it into odin mode but odin will fail no matter what I try and flash...works fine to flash second tablet I have.
Any suggestions or do I need a new tablet.
Plaz

I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat

plazomat said:
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
Click to expand...
Click to collapse
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
So when I flash twrp 2.8.0 it , the progress bar goes all the way green then fails after a few seconds here is the oding log...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> 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> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help RealWelder...
Plaz

And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz

plazomat said:
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
Click to expand...
Click to collapse
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ

plazomat said:
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
Click to expand...
Click to collapse
Hi i have the same problem can u help me pls?

Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to samsung ( I think) recovery....
Plaz

plazomat said:
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to recovery....
Plaz
Click to expand...
Click to collapse
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz

plazomat said:
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
Click to expand...
Click to collapse
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thanks RealWelder you are awesome to still be supporting these old beaters - gonna try this in the morning when I get some time....
Plaz

Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz

plazomat said:
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
Click to expand...
Click to collapse
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.

gr8nole said:
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
Click to expand...
Click to collapse
Thanks gr8nole - tried flashing the 3.0.0 TWRP still no joy - keeps booting into stock (ithink) recovery. I pulled it from your file repo on Android file host.
I say I think cause the font is so big and the display is in landscape mode.
Plaz

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Gave it a go with your ROM...still recovery boot loop as suggested by gr8nole.
Here is log..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Thanks again
Plaz

Hi Gents, still messing with this when I have time and no joy...
Can't get a custom recovery to stick, odin flashes file but when device reboots just goes back to stock recovery...
Any clues.
Plaz