Develop Bugs

[SHV-E250s] Bricked my phone

Hi guys,
Got my Korean LTE (SHV-E250s) yesterday and thought I'd root it so I can install a new English OS on it (Cleanrom Ace 4.5).
I followed Chainfire's thread on how to root my phone (http://forum.xda-developers.com/showthread.php?t=1933542).
So, first I downloaded Odin3 v1.85 and CF-Auto-Root-t0lteskt-t0lteskt-shve250s.zip.
Extracted both and managed to install CF Auto Root with SuperSU v1.05.
Sweet, everything was going well.
Then I found Cleanrom Ace 4.5 and its thread (http://forum.xda-developers.com/showthread.php?t=2055170).
So I installed Goomio from the play store and downloaded the current version of "twrp".
Now, here is where I stuffed up bad because I didn't make a backup.
I copied the zip file of Cleanrom Ace 4.5 onto my micro SD as well as the internal storage.
I booted the phone into twrp and went to factory wipe and reset. I got a little bit worried here because this is where things go wrong.
I went ahead and did it, rebooted to twrp again and installed Cleanrom Ace 4.5.
I got to the options and it was looking hopeful. Chose stock or custom animations to boot up, apps to install, etc.
Then it went to installation screen showing the progress and it stayed on 0.0% when it was trying to install the boot up animations.
After about 2 minutes or so it would reboot. I would try and install the ROM again but each time I got the same thing.
I tried rebooting normally but then twrp told me that I didn't have an OS to boot to. Uh oh.
After doing another wipe and reset, I could access the download mode (vol down+home+power) and the other mode, which I'm not sure if it's recovery mode? (vol up+home+power).
I tried using Odin3 v1.08, v.3.04 and 3.07 to load up some stock ROMs (N7105ZHDMB1_N7105ZZHDMB1_N7105XXDLL5_HOME.tar.md5, N7105XXDMB2_N7105TMHDLK8_N7105XXDLL5_HOME.tar.md5, and N7105XXDMB2_N7105VNZDMA2_N7105XXDMA1_HOME.tar.md5).
I tried using different USB ports and different computers. Each time I would get a red 'FAIL' screen in Odin3.
Below is an example of the message I'd get from Odin3 v3.07:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7105ZHDMB1_N7105ZZHDMB1_N7105XXDLL5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me? My phone gets stuck on the "Samsung Galaxy Note II" window and doesn't progress. I hold down the power button and it just reboots to the same window. I can get to download mode and what I think is recovery mode.
Any guidance is very appreciated. I have read around the threads and I know this isn't a hard brick so there may be some way to resolve this.
Cheers

Maybe this will help you or wait for Dr.Ketan to help you is a real doctor.
http://forum.xda-developers.com/showthread.php?t=2143515

adinfsfocus said:
Maybe this will help you or wait for Dr.Ketan to help you is a real doctor.
http://forum.xda-developers.com/showthread.php?t=2143515
Click to expand...
Click to collapse
Hi there, thanks for the link. I'm glad your issue was resolved.
However, I don't think I created a backup, so I couldn't just do a backup through recovery.
I can't reinstall any of the stock firmware I've downloaded as it says 'failed' every time in Odin3.

Update: I can't get into recovery mode now.

1. Even I had the same situation wen I ran megawipe script but stock rom installation in download mode gave life to my phone...
So first try installin wit different versions of odins and roms..
2. May be the whole internal memory lost all the partitions into which the files could be flashed.. 'wipe data factory reset' in recovery would have put them back ..but since ur phone recovery too is lost search for a tool which can put them back as I remember readin about such a tool... will search too..
Sent from my GT-N7100 using Tapatalk 2

maloolaba said:
Hi there, thanks for the link. I'm glad your issue was resolved.
However, I don't think I created a backup, so I couldn't just do a backup through recovery.
I can't reinstall any of the stock firmware I've downloaded as it says 'failed' every time in Odin3.
Click to expand...
Click to collapse
Try instal a costom recovery after you instal costom recovery with Odin (make a full wipe,format system,partition,wipe cache and dalvik) then download a costom rom and put on external SD card if you have if not borrow one or buy one and instal the rom from external Sd card.
I hope you solved.

adinfsfocus said:
Try instal a costom recovery after you instal costom recovery with Odin (make a full wipe,format system,partition,wipe cache and dalvik) then download a costom rom and put on external SD card if you have if not borrow one or buy one and instal the rom from external Sd card.
I hope you solved.
Click to expand...
Click to collapse
Would I still need GooManager or Terminal Emulator to install a custom rom like twrp? Because I can't install apps like GooManager or Terminal Emulator as my phone is bricked.
edit: Tried installing TWRP recovery using this hxxp://androidlegend.com/install-twrp-recovery-2-3-1-1-on-galaxy-note-2-n7100/ but Odin3 kept crashing every time I hit "start". I don't know if it's because my phone is an SHV-E250S and not a n7100 or what?
double edit: Update. I can get recovery mode again! Weird.
Options are:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
So I went ahead and selected "wipe data/factory reset". Rebooted and still the same.

Oh man!
So I've tried the method in this thread (http://forum.xda-developers.com/showthread.php?t=2040264) for Verizon Note 2 and I had a minor progress.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I605_VRALJB_Restore.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
The progress bar underneath where it would say PASS or FAIL actually said something, ie. Boot, which is something that hasn't happened with the stock ROMs I've tried in the first post. Now I just need a stock from for the SHV-E250s that will work!
Upon rebooting, it adds to my flash number, so it is writing, but not completing the install.

Has anyone got any ideas I can try?

maloolaba said:
Has anyone got any ideas I can try?
Click to expand...
Click to collapse
Try contact dr.ketan is a master:good:
http://forum.xda-developers.com/showthread.php?t=1896696

After wipe data/factory reset in recovery did u try changing into download mode n flashin rom through pc odin ???.. plz try it if u have not..
Sent from my GT-N7100 using Tapatalk 2

hkkanha said:
After wipe data/factory reset in recovery did u try changing into download mode n flashin rom through pc odin ???.. plz try it if u have not..
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did just that. Still no luck. Is this possibly because there isn't much support for the SHV-E250s in terms of recovery ROMs and Odin3?
A recovery ROM for N71000 was able to begin writing on my phone, thus increasing flash count, but failed at the beginning in Odin3.
I don't know if it's a ROM problem or a phone problem or an Odin3 problem?
Noob here, btw.

these stock ROMs that you have tried are not for galaxy note 2 korean version/shv-e250s..
try this latest stock ROM/firmware for shv-e250s : E250SKSVME1_E250SSKTVMAA_SKT.zip
get it from sammobile

m41n54j4 said:
these stock ROMs that you have tried are not for galaxy note 2 korean version/shv-e250s..
try this latest stock ROM/firmware for shv-e250s : E250SKSVME1_E250SSKTVMAA_SKT.zip
get it from sammobile
Click to expand...
Click to collapse
Please help, i really need pit file for SHV-E250s. I softbrick my phone. Please

tuannghia1985 said:
Please help, i really need pit file for SHV-E250s. I softbrick my phone. Please
Click to expand...
Click to collapse
Plz donot Install N7100 or N7105 Stock Rom on your SHV-E250S, Download Samsung Official Stock Rom from the link given Below and flash it through PC ODIN http://www.sammobile.com/firmwares/1/?model=SHV-E250S&pcode=SKT#firmware

[Q] Softbrick, bootloop, TWRP Password

My girlfriends S3 (Bell, I747M, d2can) is currently boot looping. It had a custom ROM on it, but I'll be damned if I could tell you which one. It was working, then it wasn't. No updates, no flash/wipe/etc.
Now I turn on her phone, and it gets to the ROM's boot screen, and just as it's about to complete, it restarts again. I can enter TWRP (2.6.3.1) but it requires a password (which is a bug, afaik). I can press "cancel" and try to reset/wipe, but it won't mount or reset the cache partition, so it fails.
I used Odin (3.07, 3.09) to try and flash TWRP 2.6.3.0 and 2.7.0.0, and both failed. The result was Odin would reboot the phone, then it would enter the same bootloop, and the recovery would still be TWRP 2.6.3.1.
I tried downloading a stock S3 firmware and flashing it with Odin. Same problem.
I've tried new drivers. New cable. New USB port. I've tried using a different computer. Always the same result.
So a summary of what I can/can't do:
Can't use TWRP to reset/wipe
Can't use ADB Sideload
Can't modify device via ADB
CAN see the device via ADB
CAN enter download mode
Any help?
I pulled DMESG at some point during all this. Maybe it can help shed some light: http://pastebin.com/4c2uL3Qq

Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.

theramsey3 said:
Dont know how much help it is but I quit using TWRP because of that bug, now I use CWM the philz touch version and haven't seen that again. When you are flashing the rcovery with ODIN you must absolutely uncheck the box for auto reboot. when you get the message that says the flash was successful you should then unplug the USB cable and do a battery pull, reinsert the battery, press the volume up key and the home key, press the power button until it vibrates then release the power button only, once the phone boots into recovery you may release the volume up and home buttons.
If you are trying to flash Stock roms be darn sure you have the right stuff IE AT&T phone using 4.3 you find here on XDA the correct odin flashable tar or for any other use www.sammobile.com if you have a canadian I747M go to www.sammobile.com and find the right one for the bootloaders currently on the phone. If you flash a phone that has 4.3 bootloaders on it with older bootloaders you will have an instant Hard Brick. Use Extreme Caution with bootloaders and ODIN tars. you could also use custom recovery to flash some stock or custom roms too those are alot safer and less likely to hard brick.
I think you are on the right track to trying to fix your ahem her phone, a little patience and reading go a long way IIRC the recovery thread instructions outline the need to uncheck the auto reboot box, with that being said you aren't the first one to over look it I have done it myself a few months ago. I wish you the best of luck and hope that a cache wipe will fix what you have going on if not try a factory reset, Good Luck.
Click to expand...
Click to collapse
Appreciate all the help! I've tried pretty much every combination.
I've turned off auto-reboot, flashed, but Odin stops at:
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
Click to expand...
Click to collapse
I assume that's where it's supposed to be. Then I enter recovery and it's still the same TWRP 2.6.3.1. Very strange.
I don't think her phone is using 4.3 bootloaders, as I don't remember them being available when I flashed this phone. I'm a Nexus guy, so maybe I'm doing something wrong this time.
EDIT: I also seem to recall on my phones that when I flashed something in Download/Fastboot mode, there was a progress bar of sorts on the phone itself indicating it was receiving something. On this phone it doesn't display anything to imply something's happening.

Boot into download and let us know what it says on the download screen. If you have the 4.3 bootloader, try flashing a pre-rooted 4.3 Bell ROM using Odin 3.07. If you have a lower version bootloader, try flashing a pre-rooted 4.1.1 or 4.1.2 ROM.
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139036464
In Odin, don't check auto reboot. When you see reset in the status windows, disconnect the USB cable and pull the battery. Boot into recovery and wipe cache, data, and reboot.

Thanks for the reply! I'm 99% sure it's a pre-4.3 bootloader. Here's what it shows in DL mode:
ODIN MODE
PRODUCT NAME: SHG-I747M
CUSTOM BINARY DOWNLOAD: Yes (2 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
DUALCOMM SECUREBOOT: ENABLE
If I recall correctly, a 4.3 bootloader would show two more lines at the bottom.

Tried installing a 4.1.1 ROM (root66_BMC_I747MVLDLK4)
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDLK4.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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
4.1.2 (root66_BMC_I747MVLDMF1.7z)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_BMC_I747MVLDMF1.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

I feel it's worth mentioning again: At no point, while using Odin, does the phone display a transfer bar of any sort.

Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.

audit13 said:
Try installing Philz Touch recovery via Odin and see if you can boot into recovery. Copy a custom ROM on an external SD card and see if you can flash that ROM from recovery.
Click to expand...
Click to collapse
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.

X04D said:
Tried Philz and Odin still doesn't seem to have flashed it.
I'll try with an SD card.
Click to expand...
Click to collapse
Try this: when you flash with Odin, uncheck auto reboot, start the flash process. When you see the word reset in the status window, remove the USB cable, pull the battery, and boot into recovery.

Softbrick, cannot mount /cache, and "sw rev. check fail. device:3, binary:2"

Softbrick, cannot mount /cache, and "sw rev. check fail. device:3, binary:2"
Hey everybody,
While trying to flash a custom rom on my brothers 10.1 2014 (P600), I had accidentally wiped internal storage and system in TWRP. Once that happened and I flashed the Hydronium rom, I hit problems: bootlooping, flashing with odin3 stopped working, and Kies was no help.
Here is what I have tried so far:
-Re-flashing the rom
+Caused bootlooping
-Tried flashing two stock roms from odin
+Caused a "fail" in Odin and the message "SW REV. CHECK FAIL. DEVICE:3, Binary:2"
-"Repaired" the "system" partition
+Nothing changed when I had tried re-flashing the stock and custom roms through TWRP and Odin3
-Tried recovering the stock from both versions of Kies
+Kies gives an error that "device cannot be updated". I think it's because it is a refurbished model.
Download mode is also telling me that I have a custom custom binary, which I assume is due to the su binary.
Also, here is is what odin was telling me when it failed flashing a US version of stock rom:
"<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUBMK1_P600XARBMK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<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> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
What do you guys think? I appreciate the help!

If you still can get into download mode, flash stock rom again, use odin 1.85 or 3.07

lsherif said:
If you still can get into download mode, flash stock rom again, use odin 1.85 or 3.07
Click to expand...
Click to collapse
Still nothing.
Every time I tried flashing, the tablet says "SW REV. CHECK FAIL. DEVICE:3, BINARY:2."

first try to flash another recovery like PhilZ recovery , then push any custom rom into external storage (SdCard) and flash it ..
or if you have previous backup of your rom push it into SdCard and restore it with PhilZ recovery ...

DocFreeDom said:
first try to flash another recovery like PhilZ recovery , then push any custom rom into external storage (SdCard) and flash it ..
or if you have previous backup of your rom push it into SdCard and restore it with PhilZ recovery ...
Click to expand...
Click to collapse
I flashed PhilZ and re-flashed the custom recovery fine (although it still just bootlooped), but the stock rom did not flash at all. All of the roms and such are on the microSD card because I can't access the internal storage.
I failed as a hacker and forgot to make a stock rom back-up, so I'm trying to do the next best thing and try to find away to fix the problem without it.

mwallig3 said:
I flashed PhilZ and re-flashed the custom recovery fine (although it still just bootlooped), but the stock rom did not flash at all. All of the roms and such are on the microSD card because I can't access the internal storage.
I failed as a hacker and forgot to make a stock rom back-up, so I'm trying to do the next best thing and try to find away to fix the problem without it.
Click to expand...
Click to collapse
did you try to do Wipe Data/Cache/Dalvik after flashing the custom rom ?

DocFreeDom said:
did you try to do Wipe Data/Cache/Dalvik after flashing the custom rom ?
Click to expand...
Click to collapse
That worked!
I think the problem was that TWRP was force closing when I tried wiping dalvik cache and data, and I never thought anything about it.
Thanks for the help!

mwallig3 said:
That worked!
I think the problem was that TWRP was force closing when I tried wiping dalvik cache and data, and I never thought anything about it.
Thanks for the help!
Click to expand...
Click to collapse
You are welcome
Hit "Thanks" if i helped you

[Q] Stuck in bootloop, Odin keeps failing

Hey everyone, hoping someone can help me out here.
Recently I decided to set my S3 back to stock after running Cyanogenmod for quite some time. Somewhere along the way, I must have grabbed a wrong file, but one thing led to another and my phone got stuck on the Samsung logo while booting. I am able to get my phone into download mode and have tried to flash any rom I can through Odin, but it fails every time. I have even gone and got the official firmware from the Samsung site and it still fails. Here is the error:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Anybody have any ideas what I'm doing wrong? Thanks

Odin is failing because you are trying to downgrade the bootloader.
What bootloader is on your phone? You have an i747 or i747m?

I have the i747

With an i747 and the fact that Odin is giving an error when trying to flash a stock LK3 ROM, you must have at least a 4.3 bootloader. This means that you cannot use Odin to flash a stock ATT 4.3 or ATT 4.4 ROM unless the ROM has been specifically compiled for use in Odin.
Do not make anymore attempts to to flash the stock LK3 ROM as this may brick your phone.
If you still have a custom recovery on your phone, flash any custom ROM and let us know the baseband.
We're all here to help.

Is there any way to get into recovery mode other than holding the volume up, home, and power buttons? The volume up button on my phone has been broken for quite some time and it took me a while to even find a way to get into download mode so I could attempt to use Odin.

VctrEco12 said:
Is there any way to get into recovery mode other than holding the volume up, home, and power buttons? The volume up button on my phone has been broken for quite some time and it took me a while to even find a way to get into download mode so I could attempt to use Odin.
Click to expand...
Click to collapse
Do you have a ROM on your phone?

Do you mean a ROM in a zip folder that I could flash through recovery? Because I think the only one I have on my phone is the one that could this big mess up

Sorry, I should not have used such ambiguous wording.
Does your phone have a ROM installed that will let you boot to the phone's desktop?
Not sure if this helps but you may be able to use this to flash a ROM and recovery: http://wiki.cyanogenmod.org/w/Insta..._custom_recovery_on_Galaxy_S_III_.28AT.26T.29
Do you have a USB jig?

audit13 said:
Sorry, I should not have used such ambiguous wording.
Does your phone have a ROM installed that will let you boot to the phone's desktop?
Click to expand...
Click to collapse
That I don't really know about. Is there a way to figure that out? Right now if I just boot the phone, it gets to the Samsung logo and just stays there, never goes any farther. Never makes it to the home screen.
Also, thank you for all your help so far, apparently I don't know as much as I thought I did..

Your phone could have a ROM installed but you probably need to get into recovery to wipe the cache, Dalvik, and data.
I suggest putting a custom rom such as CM10.2 onto an external SD card and try to get into recovery to flash the new ROM. Make sure you wipe cache, dalvik, and data before installing CM10.2.

Ok I will try that and hopefully something will happen. Do you know of a way to get into recovery other than the button combo since I don't have a functioning volume up button and also can't get to the home screen to boot to recovery from there.

Not sure but fastboot commands could work in download mode.

Those commands are given through ADB, correct? I installed ADB and it doesn't show up in the list of devices. I think that since the phone is stuck in a bootloop, it never gets to a point where it can be recognized and receive commands. It also doesn't get recognized in download mode.

When you connect it in download mode, are the drivers installing? Or were they installed from when you first used Odin?
You may have to try and get into recovery using the recovery keys. You have a USB jig?

I uninstalled the original drivers and let it reinstall once I plugged it in, but it still is not recognized. And no, I don't have a jig, I found a program that acts like one that puts it in download mode once I plug it in.

Putting the phone into download via USB program? That would be very helpful for many users. Do you have a link to the program?
I assume you could not get into recovery mode on your phone. Do you have the Touch version of CWM on your phone?

audit13 said:
Putting the phone into download via USB program? That would be very helpful for many users. Do you have a link to the program?
I assume you could not get into recovery mode on your phone. Do you have the Touch version of CWM on your phone?
Click to expand...
Click to collapse
Correct, I cannot get to recovery by using the volume up, home, and power buttons. I was hoping there could be some other program or commands to help me get to it since ADB won't recognize my phone.
And here is the link to the forum with the program that forces it into download mode. It even picks up my phone in a boot loop
http://forum.gsmhosting.com/vbb/f777/samsung-300k-tool-force-enter-download-mode-via-usb-1718796/

Interesting. I don't have a s3 to try it with but I will definitely keep it around

Do you have any hidden tricks to get into recovery mode without using the volume buttons? It seems like all my problems could be solved if I can get to recovery and flash a ROM, but that broken volume button is preventing me...

Sorry, I just know the button combination or from a booted ROM.
Too bad Samsung doesn't readily support fastboot commands.

[Q] Soft brick. Odin fails.

Hello!
I had a S3 i747 which receive OTA to latest update. Everything was fine except lagging interface and not working wifi\tethering so I did factory reset from "Settings". After that it is stuck on Samsung logo. So I tried to flash CWM 6.0.4.7 (guide on CM wiki, via Heimdall ) and CM 11 which failed then i tried CM 10.2 and then different ROMs from development thread, nothing worked...(all of these via CWM)
CWM refused to flash any of them except CM-11. Result of flsahing CM-11 is a phone stuck on Cyanogenmod screen(rotating and blinking LED).
What is my problem? Is it recovery or ???
ODIN Log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Since you updated via OTA to the latest ROM, which would be Kit Kat, do not use Odin to flash any stock ROM unless that ROM has been specifically compiled for flashing in Odin. With the 4.4 bootloader, attempts to downgrade the bootloader or modem can brick the phone.
Do not flash the LK3 firmware as this is 4.1.1 and you have 4.4.2.
Were you able to flash CWM onto your phone?

audit13 said:
Since you updated via OTA to the latest ROM, which would be Kit Kat, do not use Odin to flash any stock ROM unless that ROM has been specifically compiled for flashing in Odin. With the 4.4 bootloader, attempts to downgrade the bootloader or modem can brick the phone.
Do not flash the LK3 firmware as this is 4.1.1 and you have 4.4.2.
Were you able to flash CWM onto your phone?
Click to expand...
Click to collapse
Yes. CWM-Touch is working nice but can not access internal sdcard and any partition on it..

Can you access the external SD card? You could try flashing a ROM from there.
Have you looked here for a possible solution: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654

audit13 said:
Can you access the external SD card? You could try flashing a ROM from there.
Have you looked here for a possible solution: http://forum.xda-developers.com/galaxy-s3-att/general/ucuemjb-to-ucufne4-firmware-update-t2808654
Click to expand...
Click to collapse
I can and I did try flash another ROM from there from CWM. But all of them are beeing aborted (except CM-11) which is sticking at boot animation...

If it hangs at boot you probably just need to factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

elnurmen said:
I can and I did try flash another ROM from there from CWM. But all of them are beeing aborted (except CM-11) which is sticking at boot animation...
Click to expand...
Click to collapse
What error is CWM reporting when flashing a ROM?

audit13 said:
What error is CWM reporting when flashing a ROM?
Click to expand...
Click to collapse
I don't exactly remember but basically output is like:
1) Selected zip file...
2) Opening zip file
3) Installation aborted...
Nothing special...no error reported...
But I should add that when i try to format \system it said that internal sdcard is unavailable...

It's weird that CWM doesn't give an error. Without an error code, it's difficult to determine exactly what is causing the error.
What ROMs did you try?

Could've sworn I replied to this earlier! Anyway, flash again, and after it fails, do not reboot, but go back to the Advanced menu and copy log to sdcard. (in TWRP, if the external card is selected to flash from, the recovery.log will be copied there. Internal sd if you are flashing from the internal one. Not sure if it's the same in CWM)
Then attach the log here. It will usually have more detailed information about the failure/error.
Sent from my SAMSUNG-SGH-I747 using Tapatalk