Develop Bugs

[Q] need a solution possibly semi bricked epic touch no usb to pc recognition

I need help any ideas or similar experiences?
I flashed a bad renamed tar file that ended up being [email protected] gt i9100 firmware
Now when i go into Odin mode which I still have , I get no USB to PC recognition ?
No yellow com port in Odin?
Even when u plug USB in it just turns on automaticaly and shows gti910 on boot up then goes right intob 3e stock recovery and no button options are compatible with phone and the charging mode is at a standstill with a small circle not moving ,the battery was very very low before this all happened but enough to power up as well.
I've tried 4 USB cords uninstall kies,reinstall kies, tried other Odin versions ,
Tried 2 desktops and a laptop ,thanks to a botched tar file for a i9100 that was named eg30.tar!!
Could it be that USB mounting has been cut internally or not compatible with the device having wrong firmware? What about USB debugging obviously not enabled because the phone won't even boot
My binary count was at 8 when I got phone now its 11 does to many flash attempts affect anything
I think it would flash correct tar if only could get USB to work
If I atleast have Odin am I in luck? Any any similiar experiences or info would help!
I can't return it cause was bought used and sprint knows esn was tied to an alternate line over a month ago

Try this ..... By the way next time just bump your other post it didn't need another thread
http://www.forums.acsyndicate.net/s...din-Completely-Stock-EG30-Restore-your-system
Sent from my SPH-D710 using xda premium

I have the same problem. Any solution? The above link doesnt work.

seawind107 said:
I have the same problem. Any solution? The above link doesnt work.
Click to expand...
Click to collapse
If you did flash an non-Sprint ROM your USB is likely disabled. You can try moving something to an MicroSD card and flashing from recovery, JTAG or take to Sprint. (Flashing from recovery, at least from other posts, will not restore the USB use.) I'll try to find the last post on this, someone else had this recently.
*EDIT* Here's the support for my post:
http://forum.xda-developers.com/showthread.php?t=1577734&page=2

garwynn said:
If you did flash an non-Sprint ROM your USB is likely disabled. You can try moving something to an MicroSD card and flashing from recovery, JTAG or take to Sprint. (Flashing from recovery, at least from other posts, will not restore the USB use.) I'll try to find the last post on this, someone else had this recently.
*EDIT* Here's the support for my post:
http://forum.xda-developers.com/showthread.php?t=1577734&page=2
Click to expand...
Click to collapse
Oh,thanks for your quick reply.

Soft bricked - No recognition

EDIT: Sorry, this post wen't to completely wrong place. Hope some mod can move this to right section.
I know. There's number of similar threats. I have read them all. Or at least feels like it.
I managed to soft brick my sgs2. I was playing with this new lol boot (dual boot app) from market. I think I pushed something wrong in this app. After that my intention was to make a CWM backup before I start to play seriously with lol boot. At the second I pressed backup from the menu, my phone shut down. Now I'm in a sitsuation whre I can't enter recovery mode. There's just this Samsung Galaxy logo. At the time I had CheckRom v4 installed.
My intention was to flash stock rom via odin. I can enter to download mode just fine BUT odin or kies isn't able to connect to phone. Kies is recognizing the usb connection, but fails to connect it properly. Here's a list what I've tried so far:
- Restart PC (100x)
- Restart Odin (101x)
- Restart Kies
- Reinstall USB Drivers (with Kies and without)
- Trying different computer which has never seen Kies or any Samsung USB drivers
- Reinstalling Windows (W7 x64)
- 3 different USB cables (2 stock Samsung)
- Different USB ports
- Also Nexus S USB drivers as mentioned on another thead in XDA
- Starting odin after USB connection, and before
- Googling with any keywords I have come up
Is there anything else I can do for now?

you mean when you try to connect to odin there is no yellow square ?
maybe try to remove battery for + 90 sec and try to enter in odin ?
ps in this situation you must forget kies since its barely work when everything is fine with the phone ...

Thanks for your reply. Odin doesn't 'do' anything when i connect my device. I'm using version 4.43. When I connect s2, windows install two drivers, Samsung Mobile USB CDC Composite Device and Samsung Mobile USB Modem. I also tried taking battery off. Actually the battery wasn't attached for 6 hours, still no success.

I didn't see this in your list, but have you tried entering download mode and connecting?
Sent from my GT-I9100

can you enter recovery? which recovery you have? Clockwork? 2e, 3e?
Just trying to feel out your situation...

Guys. I think there is some Android God that came to help me. After ~36 hours of googling, crying and throwing the phone to the wall, I've managed to solve my problem! As I was googling cheap shotgun for me, I had a vision. Why not, let's try older odin. The solution was v1.83. And right when I plugged in my phone with this odin, it got recognized! At the same second! Nuff said, I'm satisfied. And do you know what is the best part? I flashed with original stock rom and every app, every launcher and so on was STILL WORKING and running!
Thanks to everyone. I'll be more careful next time!
EDIT: How the heck the custom binary counter went to zero? I was thinking its only possible with usb jig?

not older odin! but the one u need for sgs2 (and 1) only use odin 3 v. 1.83 or v. 1.3.
The one you said IS NOT FOR YOUR PHONE. Sorry I missed that text.

So if I understood you correctly, u are saying that I flashed my phone with wrong version of odin (1.83) ? Sorry, I'cant understand english too good, so can you say your point more literally and s_l_o_w_l_y? Thanks

I only use odin3 v1.3 or odin 3 v.1.83.
As far as I know, you cannot use anything else, since it is not made for your device!
I might be wrong, if so, somebody correct me.
Sent from my GT-I9100

So if you're correct on this, the reason why I couldn't get my phone recognized was the wrong version of odin?

pazzio said:
Guys. I think there is some Android God that came to help me. After ~36 hours of googling, crying and throwing the phone to the wall, I've managed to solve my problem! As I was googling cheap shotgun for me, I had a vision. Why not, let's try older odin. The solution was v1.83. And right when I plugged in my phone with this odin, it got recognized! At the same second! Nuff said, I'm satisfied. And do you know what is the best part? I flashed with original stock rom and every app, every launcher and so on was STILL WORKING and running!
Thanks to everyone. I'll be more careful next time!
EDIT: How the heck the custom binary counter went to zero? I was thinking its only possible with usb jig?
Click to expand...
Click to collapse
gratz!
to reset your binary, there is only one way to do it. u are right, usb jig.
however, beware, i read somewhere saying that GB ver 2.3.4 onward has a new version of bootloader which prevent usb jig from resetting the counter, which mean samsung is trying to lock the bootloader now. however, flashing the old bootloader still helps (claim by others).

[Q] Unrooted GS3 with mobile odin. Broken now and can't fix

Long time listener first time caller (this is my first post here) I'm going to try not to leave out any details. Bear with me.
I rooted my Tmobile Galaxy s3 for the first time and installed CM10.1. It was great for a few months, then it started getting glitchy. So I would flash the nightly release and it would be fine for a while. I decided to unroot and start fresh. It was then that I discovered the PC wouldn't recognize the device. I followed a youtube tutorial to unroot with Mobile Odin. I extracted and flashed a stock image called Tmobile_GS3_SGH-T999_4.0.4 after clearing counter with Triangle Away.
Well it seemed to go well, unrooted my device, but now the OS is incomplete. No internet app, messaging won't work at all, and it keeps crashing and freezing. The usb port is still not working so I cannot root with my computer, and the flash counter still says 1 and status says modified.
Tmobile sent me a new one on warranty, but I'm really worried they're gonna charge me 500 bucks because it's "modified". I have a few days before I have to send it back, Is there anyway that I can fix this without connecting it to my computer? Any help is GREATLY appreciated.
Thanks

re: flashing stock rom.
empire-1 said:
Long time listener first time caller (this is my first post here) I'm going to try not to leave out any details. Bear with me.
I rooted my Tmobile Galaxy s3 for the first time and installed CM10.1. It was great for a few months, then it started getting glitchy. So I would flash the nightly release and it would be fine for a while. I decided to unroot and start fresh. It was then that I discovered the PC wouldn't recognize the device. I followed a youtube tutorial to unroot with Mobile Odin. I extracted and flashed a stock image called Tmobile_GS3_SGH-T999_4.0.4 after clearing counter with Triangle Away.
Well it seemed to go well, unrooted my device, but now the OS is incomplete. No internet app, messaging won't work at all, and it keeps crashing and freezing. The usb port is still not working so I cannot root with my computer, and the flash counter still says 1 and status says modified.
Tmobile sent me a new one on warranty, but I'm really worried they're gonna charge me 500 bucks because it's "modified". I have a few days before I have to send it back, Is there anyway that I can fix this without connecting it to my computer? Any help is GREATLY appreciated.
Thanks
Click to expand...
Click to collapse
First thing to do is to put the phone into DOWNLOAD mode to TEST it and see if ODIN will recognize it.
If Odin recognizes it then there is NO need to send it back to Samsung, all it needs is a proper Odin flash.
Just because when all those missing apps and the usb had issues it does not necessarily mean that Odin will not recognize the phone.
If your computer is not working or you don't have a windows computer find a relative or a friend who has one.
Even a laptop computer would do just fine.
Good Luck!

Tried that
Thanks for your response, I have tried connecting it to Odin in download mode and it still will not see it. I really don't know what the problem could be. the usb used to work fine and there has been no physical damage.

re: try this.
empire-1 said:
Thanks for your response, I have tried connecting it to Odin in download mode and it still will not see it. I really don't know what the problem could be. the usb used to work fine and there has been no physical damage.
Click to expand...
Click to collapse
Try a different usb cable and or plug usb into different port,
if that fails, re-install the Samsung usb drivers for the phone.
Remember, if the phone goes into download mode 99.999% of the time the phone
can be flashed successfully using Odin.
The main reasons for usb issues in "download mode" are either loose connection to computer's usb ports,
usb cable intermittant or the Samsung usb drivers in the computer are corrupted in one way or another.

Thanks again
I guess I should have put this in my first post. I have tried 2 different cables in every port on 2 different computers. I have re installed the drivers multiple times as well. Also the new phone they sent me is recognized just fine.

empire-1 said:
I guess I should have put this in my first post. I have tried 2 different cables in every port on 2 different computers. I have re installed the drivers multiple times as well. Also the new phone they sent me is recognized just fine.
Click to expand...
Click to collapse
You are in a tough spot. I don't know if you have the stock recovery or not but if not you can either download the stock rom on the phone again...you know the best way although unethical really...being that the usb port is down is to re root it and flash a rom like the gt 1300 or whatever the international version is and intentionally hard brick your phone. Hard brick meaning won't even turn on withOut jtag and that even just clears everything out and reloads software like from the factory.If the phone won't boot up then there's no way for the person to tell its been modified. Majority of the time samsung doesn't get the damaged phones its some idiot making 8 bucks an hour to refurbish phones. That's what I would suggest you do being that the counter is still saying one flash
tmobile s3 running wicked. best rom i've ever used

Pretty sure I'm on stock recovery. it does give me an option to "apply update from external storage"
Thanks for all your help, I'll try to flash the stock rooted rom through the stock recovery although i'm not optimistic.
I will check out the wicked rom you mentioned, although I am a little hesitant to root my new one after this ordeal.

but how do I re root it if I have no usb or custom recovery?

re: flashing
empire-1 said:
but how do I re root it if I have no usb or custom recovery?
Click to expand...
Click to collapse
If you can get your phone to boot normally with any stock rom rooting will not be a problem at all.
If you get the phone working and booting properly you would be very lucky but from reading
everything you have wrote so far I highly doubt that you can successfully flash any rom at all
unless you have forgotten to tell us something.
Don't worry about rooting, worry about getting the phone to boot and work properly with stock rom.

yep. running stock recovery. hopeless?

re: flashing
empire-1 said:
yep. running stock recovery. hopeless?
Click to expand...
Click to collapse
I never said a word about stock recovery, I said STOCK ROM.
Invest in a JIG, it puts your phone into download mode instantly even if you cannot
do it manually with the three buttons as long as the phone is not completely dead.
You can buy a jig for less than $4.00 shipped on eBay, it's great little tool.
All you do is remove the battery from the phone and put it back in then simply plug
the jig into the usb port then in a couple seconds it will be in download mode then you
can unplug the jig and the phone is ready to be odin flashed..
Remember what I said before, just because the usb did not work with some
rom you flashed it does not mean that it will not work for download mode.
The jig was one of the best investments I have made when I started using these samsung android phones.
Once in download mode it will allow you flash the stock or stock rooted Jellybean 4.1.1 rom.
This is my best advice.

I am not having a problem getting into download mode, I will take your advice and buy a jig though in case I ever need it. Again, thanks for all your help, I think I may have to send it back and hope for the best.

re: flashing
empire-1 said:
I am not having a problem getting into download mode, I will take your advice and buy a jig though in case I ever need it. Again, thanks for all your help, I think I may have to send it back and hope for the best.
Click to expand...
Click to collapse
Before sending it back, if I were you I would find a friend or family member who has
a windows computer and just for the hell of it install the usb drivers in the computer
just to see for sure that while in download mode and connected usb cable if Odin still
is not lighting up the [COM:xx] top left rectangle on Odin screen.
I have odin flashed many phones dozens of times in the past 3 years and I have yet
to come accross one which goes into download mode but odin is not reconized
unless there is something wrong with the windows computer or usb ports and drivers.
That only happens as I said before, if there is something wrong with the drivers,
usb ports and or usb cables or some other malfunction in the windows computer.
Just think, if it works no need send the phone to samsung plus you would have learned
something too.

I did try my other computer with the same results, tomorrow I will try it with my girlfriends laptop, I am starting to think something happened to the usb jack. It didn't work before I unrooted it either, that's why I used Mobile Odin. I am all about learning this stuff though. I plan to root every new phone I get, this has just been a little frustrating.

re: well that's it!
empire-1 said:
I did try my other computer with the same results, tomorrow I will try it with my girlfriends laptop, I am starting to think something happened to the usb jack. It didn't work before I unrooted it either, that's why I used Mobile Odin. I am all about learning this stuff though. I plan to root every new phone I get, this has just been a little frustrating.
Click to expand...
Click to collapse
This is the first I heard that the usb did not work before and the usb socket might be broke.!!!
In that case since you cannot use the Wifi in your phone to transfer and install apps since it cannot boot normally
(unless I am missing something again) and you cannot use usb and it would not even help to remove the external
sd and copy any apps at all since you would have no way to install the apps.
Then you are right, you have to send it back, exchange it and hopefully you can come up
with a good enough excuse why it's not working so samsung will not charge anything )which I doubt)

I must not have been clear, I can use the phone. it makes calls, the wifi works, i can use third party messaging and browser apps. again, there has been no physical damage. the socket worked a few weeks ago when I rooted it. I only noticed it not working when I went to unroot it.
So basically it sounds like there is no way to root or install custom recovery without usb, correct?

empire-1 said:
I must not have been clear, I can use the phone. it makes calls, the wifi works, i can use third party messaging and browser apps. again, there has been no physical damage. the socket worked a few weeks ago when I rooted it. I only noticed it not working when I went to unroot it.
So basically it sounds like there is no way to root or install custom recovery without usb, correct?
Click to expand...
Click to collapse
I don't know of any way unfortunately
tmobile s3 running wicked. best rom i've ever used

Josh McGrath said:
I don't know of any way unfortunately
tmobile s3 running wicked. best rom i've ever used
Click to expand...
Click to collapse
Can you flash it through mobile odin? I don't know anything about the mobile version.
tmobile s3 running wicked. best rom i've ever used

[Q] I think I bricked my S3 :(

My S3 will not turn on and gets stuck in the booting process. I cannot go into recovery mode but I can go into download mode. Everytime I go into Odin and try to flash it with stock it gets stuck on the initialization step. I have tried different ports on my laptop and have all the proper drivers are installed (I hope). Does anyone know what to do? And how much would Sprint charge to get it fixed, I have insurance. And im using an HTC evo cable if that matters at all.

I can't answer all your questions, but if you plug it into the computer and it reads it as QLOAD USB or something like that, its a hard brick and its time to hit ebay for $30 brick repair
Since you can get it download mode its a soft brick. I would try reflashing the recovery to see if that will get you into it. If one doesn't work try another version then try another recovery (i.e. flashing twrp doesnt work try cwm).
if the tar file you downloaded doesn't work try another version (like LJ7).

Try different cables. 99% of the time ODIN related issues are because of the cable.
Thus is what you call a soft brick...a hard brick.will happen when the phone cannot turn on at all because you have flashed garbage to the bootloader. Just make sure to not flash ANYTHING you find in the international forums (S3 I9300 and I9305) and you will not brick.

I had problems with Odin and cables. Have you got the latest Samsung USB drivers? If so try an older one, it worked for me. Newer ones give me problems with my Note II as well so I stuck with the older ones.
Sent from my GT-N7100 using xda premium

[Q] Potential Brick =(

Hey guys,
I had a look around the forum found some similar issues but nothing that fit exactly.
I am stuck with my note 8, in an awkward position, I was flashing a new ROM onto the device, it was having some issues doing it (It wouldn't work, Would always fail) was using Odin, and the Note 8 toolkit. I was changing the recovery from CWM to TWRP and then it all went bad, now i have some firmware error come out whenever i turn the device on, I can still get into download mode, but nothing else. I tried using Odin to flash the stock ROM or even a recovery back onto the device and it fails every time. I also tried using Kies to do a firmware restore, it downloads the firmware then it can't see the device.
Any help would be great =\
Thanks =D

Ascel said:
Hey guys,
I had a look around the forum found some similar issues but nothing that fit exactly.
I am stuck with my note 8, in an awkward position, I was flashing a new ROM onto the device, it was having some issues doing it (It wouldn't work, Would always fail) was using Odin, and the Note 8 toolkit. I was changing the recovery from CWM to TWRP and then it all went bad, now i have some firmware error come out whenever i turn the device on, I can still get into download mode, but nothing else. I tried using Odin to flash the stock ROM or even a recovery back onto the device and it fails every time. I also tried using Kies to do a firmware restore, it downloads the firmware then it can't see the device.
Any help would be great =\
Thanks =D
Click to expand...
Click to collapse
Make sure you have a good USB cable... I have gone through 2 Samsung OEM cables, as one did a melt down and the other had intermittent charging disconnects. Have gone to Blackberry OEM cable as it is one of the best OEM stock cables I have had for some time, 5 years now and has never failed.
Second, did you enable USB debugging before doing the custom rom?
Are you using Odin 3.7?
I am surprised that Kies downloaded a ROM, it should have detected that the device was custom. Maybe what you are seeing with Kies is normal for custom ROMs. Don't know... What is the ROM info for the Kies download. I have an odd feeling that you flashed with an incompatible ROMs as the Note 8.0 has three different hardware configurations.

gooberdude said:
Make sure you have a good USB cable... I have gone through 2 Samsung OEM cables, as one did a melt down and the other had intermittent charging disconnects. Have gone to Blackberry OEM cable as it is one of the best OEM stock cables I have had for some time, 5 years now and has never failed.
Second, did you enable USB debugging before doing the custom rom?
Are you using Odin 3.7?
I am surprised that Kies downloaded a ROM, it should have detected that the device was custom. Maybe what you are seeing with Kies is normal for custom ROMs. Don't know... What is the ROM info for the Kies download. I have an odd feeling that you flashed with an incompatible ROMs as the Note 8.0 has three different hardware configurations.
Click to expand...
Click to collapse
Tried a different Cable before and it still didn't work, But I thought I would try a different one again (From a nexus 7 I have) worked like a charm, As if I have 2 Damaged cables Haha.
Thanks for the Help Mate =D.