Related
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).
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
So I somehow during my flashing adventures got to the point where my sgs3 would no longer recieve 4g/3g signal but only 2g. I reverted to stock rom, still had the issue (4.0.4), and it wouldn't let me upgrade to jelly bean, it told me "unable to connect to network" when I tried system update. So i took to the fixing my imei number, which apparently did something as I was then able to connect to the server and upgrade to jelly bean, with one problem; I was still getting 2g. I continued to try to use the rest of the guide (http://forum.xda-developers.com/showthread.php?t=1801997) but on jelly bean my computer would no longer recognize my phone through odin or qpst, etc, but I could view the files. I could do nothing to get it to bring up a port I could connect to. I downloaded/installed/uninstalled/installed the driver many times and still couldn't get it to connect. Like an idiot I tried through odin to flash back down to 4.0.4 so I could reestablish connection and continue fixing my 2g signal, but it quit halfway through and said "Can't open the serial(com) port" and didn't flash, so whenever I tried to turn on my phone i got the firmware upgrade error and telling me to connect to kies and use recovery mode, which I did. However, Kies wouldn't recognize my phone through it. It's drivers never connected, and it just sits there saying connecting. Samsung's help/support over the phone was literally WORTHLESS ("indian accent" Take da battery out ov your phone, sir. Wait 10 seconds. Put it back in..... They literally told me at one point "Go into menu, settings..." me-" In my phone?" him "Yes that is correct" me "Thats my problem dude, I CANT TURN IT ON") and I currently have a ups label to ship it in to get repaired, but I want to know if there is anything I can do before sending it in and waiting 5-7 days without a cell phone. Thanks in advance to help
Odin the stock4.1.1 software pre rooted or not.. My phone froze at samsung screen but just reboot and it will be fine
Sent from my SGH-T999 using xda premium
Did you even read the post...? haha it's not that simple, or otherwise I would've fixed it.
make sure you are using the samsung cable that came with your phone.
I don't have the cable that came with my phone, but that has never stopped me before and I don't see why It would affect my computers ability to recognize my phone if it was perfectly capable of doing such before.
So, the system won't detect anything when you plug it in, not even after a reboot?
Well, there are a couple things you can try.
First, uninstall Kies and the Samsung USB drivers.
Reboot.
Install the drivers in my signature (they are older ones, but stable - unlike the newer ones).
If that doesn't work, try a new cable and USB port on your system.
If that doesn't work, it's bad hardware.
This will end with you flashing a stock image, probably.
Aerowinder said:
So, the system won't detect anything when you plug it in, not even after a reboot?
Well, there are a couple things you can try.
First, uninstall Kies and the Samsung USB drivers.
Reboot.
Install the drivers in my signature (they are older ones, but stable - unlike the newer ones).
If that doesn't work, try a new cable and USB port on your system.
If that doesn't work, it's bad hardware.
This will end with you flashing a stock image, probably.
Click to expand...
Click to collapse
The computer makes the sound when I plug in my phone, so it recognizes it. I just can't access the com port and use odin. I'm trying what you gave me right now
milesmarrero said:
The computer makes the sound when I plug in my phone, so it recognizes it. I just can't access the com port and use odin. I'm trying what you gave me right now
Click to expand...
Click to collapse
I don't suppose the device qhsusb_dload is detecting?
Aerowinder said:
So, the system won't detect anything when you plug it in, not even after a reboot?
Well, there are a couple things you can try.
First, uninstall Kies and the Samsung USB drivers.
Reboot.
Install the drivers in my signature (they are older ones, but stable - unlike the newer ones).
If that doesn't work, try a new cable and USB port on your system.
If that doesn't work, it's bad hardware.
This will end with you flashing a stock image, probably.
Click to expand...
Click to collapse
oh **** yes! Man you're the bomb! Those worked perfectly! Thanks, if I could thank you a thousand times I would! Thank you, odin worked fine that time!
milesmarrero said:
I don't have the cable that came with my phone, but that has never stopped me before and I don't see why It would affect my computers ability to recognize my phone if it was perfectly capable of doing such before.
Click to expand...
Click to collapse
Glad you got the problem solved. The reason I said to use the samsung cable is that I was able to root and flash my first rom with a non samsung cable then after that it wouldn't work unless I used the samsung cable.
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
Here is my problem where I can't get my Sprint S3 connected to PC, I am half rooted, and have no custom recovery, I can't flash anything on my phone except OTAs, please help, any help is much much appreciated.
Background :
I had this phone working completely fine, I bought aftermarket USB cable and attached it to the PC, everything went smooth it got connected fine in MTP mode, on second day when I tried to connect it, it gave me error that USB Device Not Recognized.
Problem :
The phone is not getting connected to PC in any way, whether it is MTP, DM+Modem, PTP, ADB, etc... not even in download mode to flash it via Odin. No matter on which mode I am it always give me error that USB Device Not Recognized.
It sense when I change modes while it is connected to PC, like when I am on MTP and I click DM+Modem or I click USB Debugging, it displays that USB Device Not Recognized message again, so I it is sensing mode changes.
What I did so far :
Changed cable and used brand new Samsung Original cable, changed USB ports, changed 4-5 computers, installed and re-installed drivers numerous times, my friend who does the phone repairs changed Micro USB Slot on the phone 4 times with Original ones, he even took one from working phone and put in on this phone, no luck so far.
My inputs :
I've searched really a lot about this problem, but didn't find any single solution.
Some guys on forums reported that they solved problem by flashing a stock or custom rom as there might be a problem with Kernel.
I can't flash anything on my device since I am on stock recovery and half rooted, I had LJ7 rooted stock on my device, and I took MD4 OTA, now, my phone is half rooted, when I install any application which requires root, I get message that 'Superuser permission denied'.
I can't even uninstall Superuser, because it is system app, I tried to re-root phone via Motochopper method but it doesn't work.
I flashed this phone to different carrier, so, I am afraid I will loose my flash if I take latest 4.3 OTA.
PLEASE HELP IF YOU HAVE ANY SOLUTION FOR THIS PROBLEM, I WANT MY PHONE TO GET CONNECTED TO PC ANYHOW.
I AM READY TO DO ANYTHING YOU SUGGEST TO RECOVER MY PHONE.
keval32 said:
Here is my problem where I can't get my Sprint S3 connected to PC, I am half rooted, and have no custom recovery, I can't flash anything on my phone except OTAs, please help, any help is much much appreciated.
Background :
I had this phone working completely fine, I bought aftermarket USB cable and attached it to the PC, everything went smooth it got connected fine in MTP mode, on second day when I tried to connect it, it gave me error that USB Device Not Recognized.
Problem :
The phone is not getting connected to PC in any way, whether it is MTP, DM+Modem, PTP, ADB, etc... not even in download mode to flash it via Odin. No matter on which mode I am it always give me error that USB Device Not Recognized.
It sense when I change modes while it is connected to PC, like when I am on MTP and I click DM+Modem or I click USB Debugging, it displays that USB Not Recognized message again, so I guess it is sensing mode changes.
What I did so far :
Changed cable and used brand new Samsung Original cable, changed USB ports, changed 4-5 computers, installed and re-installed drivers numerous times, my friend who does the phone repairs changed Micro USB Slot on the phone 4 times with Original ones, he even took one from working phone and put in on this phone, no luck so far.
My inputs :
I've searched really a lot about this problem, but didn't find any single solution.
Some guys on forums reported that they solved problem by flashing a stock or custom rom and as there might be a problem with Kernel.
I can't flash anything on my device since I am on stock recovery and half rooted, I had LJ7 rooted stock on my device, and I took MD4 OTA, now, my phone is half rooted, when I install any application which requires root, I get message that 'Superuser permission denied'.
I can't even uninstall Superuser, because it is system app, I tried to re-root phone via Motochopper method but it doesn't work.
I flashed this phone to different carrier, so, I am afraid I will loose it if I take latest 4.3 OTA.
PLEASE HELP IF YOU HAVE ANY SOLUTION FOR THIS PROBLEM, I WANT MY PHONE TO GET CONNECTED TO PC ANYHOW.
I AM READY TO DO ANYTHING YOU SUGGEST TO RECOVER MY PHONE.
Click to expand...
Click to collapse
Did you uninstall drivers from Windows device manager before reinstalling drivers? I found that this sometimes helps.
joeyhdownsouth said:
Did you uninstall drivers from Windows device manager before reinstalling drivers? I found that this sometimes helps.
Click to expand...
Click to collapse
Yes my friend, I did that.
keval32 said:
Yes my friend, I did that.
Click to expand...
Click to collapse
Is Kies installed on computer? Which version of Windows?
joeyhdownsouth said:
Is Kies installed on computer? Which version of Windows?
Click to expand...
Click to collapse
No, Kies was not installed on my computer when this problem occurred, but I checked installing Kies but no luck so far, and I am on Windows Ultimate x64.