Related
I think I put myself in a bad situation here...
I spent all day trying to figure out how to root my 5 week old Nexus as it's tethering ability is my only access to the web.
So - step one, I did the one-click method, as the instructions I was finding for "the long way" were written by people who know what they're doing FOR people who know what they're doing.
Once that was accomplished, I downloaded Rom Manager. Unfortunately Rom Manager didn't seem to want to work with One-Click's style of rooting, locking me on the boot screen every time I tried using it.
So, I finally worked out how to root my phone the "normal" way and Rom Manager was working.
Here's where my mistake came in... I was one part frustrated from how long it took me to figure it all out, one part elated that I finally DID figure it out, so I immediately put Cyanogenmod on my phone... without backing it up. I played with it a bit, but realized my mistake, so downloaded the 2.3.3 Stock Rom.
That totally futzed things up for me... First, my USB connection isn't working anymore. The USB cable still powers my phone, and the USB ports on my PC still work, but I can't get a phone to pc connection through USB anymore.
Second, my cell radio isn't working anymore, I can only get anything over wifi. The OTA 2.3.4 update was pushed and installed to me that way (The current version my phone is on now...)
Third, apparently my phone was no longer rooted, so Rom Manager wouldn't work anymore for me. When I go to the bootloader menu and try to Recover, it brings me to an android with a triangle and exclamation point symbol.
Once there, some trial and error brought up a menu that I'd hoped would have let me reroot or reinstall a working Rom, but every one I try gives me a Signature Verification error and aborts the install...
So, I'm stuck... Without my USB connection working, I can reroot my phone, and without rerooting, I can't get a working ROM back in place. If ANYBODY can help me with this, it will be greatly appreciated. If any additional information is needed, I'll do my best to give it. Thank you...
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Can you see the phone in fast boot by usb also have you course factory reset and then try to flash
Sent from my Nexus S 4G using Tapatalk
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
TBoarder said:
The big problem is that I'm unable to make a USB connection anymore. My phone is not reading any kind of connection to allow for file transfers or debugging, but it still powers the phone.
Click to expand...
Click to collapse
Can you answer my question about fastboot? I want to help you.
matt2053 said:
Who is your carrier? Need to know which phone you have.
Also I assume that since you said you rooted the hard way eventually, that means you successfully used Fastboot to unlock your bootloader, yes?
The Android with exclamation point is just the stock Android recovery partition.
The key to fixing your problem will be to get USB connection between phone and PC.
Please plug in your phone to USB connected to your computer, then put your phone into Bootloader mode (Power on while holding Volume Up). On your computer, open a command prompt window and type "fastboot devices" and post what it says.
Click to expand...
Click to collapse
I did that and nothing came up.
TBoarder said:
I did that and nothing came up.
Click to expand...
Click to collapse
ok can you please install PDAnet on your computer?
http://junefabrics.com/android/download.php
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
matt2053 said:
ok can you please install PDAnet on your computer?
This will ensure the proper must up to date drivers are installed for you. This is the best and most reliable way to get the correct drivers.
EDIT: Then try fastboot again and tell me the output for "fastboot devices"
Click to expand...
Click to collapse
It was already installed, but I reinstalled it. I got to the end of the process where it asked me to go into USB Debugging mode and won't finish the install because it's not reading the USB connection.
(Sorry for any delays here... Being a newbie, I have a 5 minute delay between when I can post)
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here: http://forum.xda-developers.com/showthread.php?t=947950
matt2053 said:
No worries, thanks for trying. If you have hardware failure you might be out of luck. USB connection is pretty crucial for this stuff.
Maybe you can try Odin. See here:
Click to expand...
Click to collapse
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
TBoarder said:
I've been looking into Odin, to see if there's a way I can do it just by pushing the files I need to my phone's sdcard and going into recovery mode. Not looking likely, but I'll read through the thread you linked me and maybe something will pop up. Thank you...
On the plus side, I just contacted Sprint and I *might* be able to get my phone replaced... Much as I'd like to troubleshoot this myself, it's looking like my only option. Too bad getting a phone replaced this early in a contract, just out of the warranty period is a total pain in the neck...
Click to expand...
Click to collapse
Can you post a link to the stock image you installed?
Was there ever a 2.3.3 for the nexus s 4g? Seems like it shipped with 2.3.4
Sent from my SPH-P100 using XDA App
matt2053 said:
Can you post a link to the stock image you installed?
Click to expand...
Click to collapse
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
My suggestion is to try and use Odin to flash it back to stock, I don't think Odin needs any drivers to see the phone...
Sent from my Nexus S 4G using XDA Premium App
TBoarder said:
It was downloaded through ROM Manager.
And yes, if I could get back into ROM Manager, I'd warn people NOT to flash their ROM to that. Bad mojo there.
Click to expand...
Click to collapse
Yeah see the thing is there is no 2.3.3 for NS4G. If you flashed 2.3.3 that means you flashed a GSM Rom on your CDMA phone. Oops! not the first time it has happened I'm sure.
Sent from my Nexus S using XDA App
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
How did you find astock 233 rom in rom manager, I only see cyanogen nighties oxygen, peter alphonso, extras etc everything is for the nexus a 4g
Sent from my Nexus S 4G using Tapatalk
TBoarder said:
Which totally explains what went wrong... Wow. ROM Manager, I though, was supposed to only bring up ROMs that are compatible with your phone model. Any way somebody can either let the developer know about this, or at the very least put a comment in the 2.3.3 ROM that specifically says it won't work with Sprint's network? That way nobody else will go through the hell I put myself through...
I'm wondering, could the USB connection issue be connected, like the "program" that controls that is integrated with the radio? Just curious, is all. Thanks again for your help!
Click to expand...
Click to collapse
Yeah. I have the T-Mobile version. When I download through Rom Manager I get a popup that says "select your phone model" or something similar and then two choices: "Nexus S" or "Nexus S 4G". It would be really easy to mess that up.
The good news is that I believe your phone can still be recovered, you're definitely not the first person with this exact issue, and at worst, it sounds like you have a Sprint rep who is willing to work with you. I think Odin is your only chance for a software solution. I can't walk you through Odin though, because I've never used it myself.
Let me know what happens.
Sent from my Nexus S using XDA App
matt2053 said:
Let me know what happens.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I just got my warranty replacement phone due to an abnormally long backorder. Thank you very much for your help (And well, I would've more appreciated it if you hadn't shown me that the problem was all my fault... ). Being my only phone and being poor, I won't be trying to root again, no matter what I learned from this problem. Anyway, thanks again, the help was, in all seriousness, greatly appreciated.
Well looks like I HARD Bricked my phone when I ran SuperOneClick v2.3.1 to Root my phone.. "its only 2 days old" the phone will not even power up now.. and when I plug it into my pc It just shows up as "qhsusb_dload" in my device manager.. rogers is going to send me a new phone overnight and I have to send back my bricked one.. do you think they will find out I was rooting the phone? they are just replace it as a power issue.
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
See if these drivers will work for ya. If not, probably nothing you can do about it.
Sent from my SGH-I727 using Tapatalk
Yep tryed the drivers.. Odin will now see the phone but just sits a setting up connection... also the phone can been see with the battery in or out... Rogers is sending me a new one tomorrow or Monday.. .from what I seen there is no way for them to tell if I have rooted the phone or not since they will have to do a jtag flash.
They will probably just say it was a hardware failure of some sort. You should be fine.
Sent from my SGH-I727 using Tapatalk
well I got QPST to see my phone now I just need a hex file to flash to it... looks like its been wiped clean my phone... odin will not see it but qpst will.
Haven't played with qpst since I tried to "unlock" a cdma phone. What a joke that was. CDMA sucks so bad. Sorry for spamming your thread..
Sent from my SGH-I727R using XDA App
I saw your post in the dev thread that you got scolded for. Not sure if it's locked yet so I'm posting here.
I'm hard bricked as well, with a replacement on the way. I'd rather fix my phone if possible with QPST. Please report back if you're able to get that hex image or find another way to make the phone work again. (although I'd be looking for the AT&T image--not the Rogers version)
Thanks and good luck!
Yes I have been looking for both images AT&T and rogers but none to be found.. the good thing is if we hard brick our phones and it will not even power up. We can still access it with Qualcomm Product Support Tools (QPST).. Now I can't find an image but if someone would be nice enough to upload a hex image of their low level boot.. but then they have to know how to use qpst. and its not a very nice tool to use.
TriC_101 said:
Yes I have been looking for both images AT&T and rogers but none to be found.. the good thing is if we hard brick our phones and it will not even power up. We can still access it with Qualcomm Product Support Tools (QPST).. Now I can't find an image but if someone would be nice enough to upload a hex image of their low level boot.. but then they have to know how to use qpst. and its not a very nice tool to use.
Click to expand...
Click to collapse
Can you link me to QPST? I've got a similar situation to yours.
By the way,
Does your phone do anything at all to indicate it's been plugged in?
Have you tried opening ADB to see if it is recognized there?
Ya the phone will not power on at all, nothing on the screen but when I plug it into the PC it sees Qhsusb_dload. in the Device mannager and QPST will see the phone.. but its stuck in a mode waiting to download a hex or bin file from Qpst.. but the phone will not power up at all. so ADB will not work.. the phone is stuck in a very low programming level.. here is a link to the software
http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html
so what do we do now, my phone is bricked too :[
Does it power on?
Wow thats alot of bricks. Most ive ever seen in one forum. What did you all do. Try and flash something from a different device?
what i did was i'm trying to flash the rom from galaxy s2 tmobile with the conversion zip but it bootloop on me, so i went to odin, it gave me error failed, i make mistake at this step is that i took out the battery the download mode to goes away, which i should have press volume up or down to get out of the screen after i did some research but everything was to late, i only have the phone working for less than 24 hours
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
JimmyStale said:
Does it power on?
Click to expand...
Click to collapse
no but i plug in my computer in does try to install the driver thou
silver03wrx said:
Wow thats alot of bricks. Most ive ever seen in one forum.
Click to expand...
Click to collapse
Perhaps we should build a house...
silver03wrx said:
. What did you all do. Try and flash something from a different device?
Click to expand...
Click to collapse
My phone got washed in the laundry and I'm trying to resurrect it.
even my skyrocket bricked any help please
silver03wrx said:
Wow thats alot of bricks. Most ive ever seen in one forum. What did you all do. Try and flash something from a different device?
Click to expand...
Click to collapse
Tried to flash a "rom" I made in dsixda's Android Kitchen http://forum.xda-developers.com/showthread.php?t=1390903
I'm pretty sure I followed the instructions completely, not sure where I went wrong. Maybe trying to flash a 2.3.5 over Alien 4 (which is 2.3.6)?
At any rate, not blaming the kitchen. I probably did something I shouldn't have.
Got a replacement yesterday, so I'm good now with a hard lesson learned. First hard brick ever!
One more....
i was chatting with whats app and then the phone reboots and black screen....
the important thing is that a friend purchased the phone in Canada and i have no invoice and also no HTC service in México...
bad way to start the year.
TriC_101 said:
well I got QPST to see my phone now I just need a hex file to flash to it... looks like its been wiped clean my phone... odin will not see it but qpst will.
Click to expand...
Click to collapse
you are right, i also can see my phone on QPST and it seems to be clean. I think we just need someone to backup their phone and boot image in hex to unbrick the phones....
Someone that want to help us to test this???
Greetings
xuvert said:
you are right, i also can see my phone on QPST and it seems to be clean. I think we just need someone to backup their phone and boot image in hex to unbrick the phones....
Someone that want to help us to test this???
Greetings
Click to expand...
Click to collapse
I wouldn't mind helping as it would possibly benefit me as well. I can't seem to get QPST to read my working 727. I can get it to recognize the device but it says "no phone".
If someone wants to point me in the right direction I'd be glad to help.
Hey guys,
So I have the Galaxy S2 Skyrocket with AT&T and I have it rooted etc. Today I tried flashing the MIUI rom, but was unsuccessful due to a message saying "Installation aborted". So I did as I read to do and wiped cache, Delvik or w/e, and then I reformatted the SDcard to redownload the ROM, however when I rebooted the next time it did not boot back up. Now I have the phone completely dead it would seem, I have tried the button combinations, etc to no avail.
What happened and is there anything I can do?
How can my phone be bricked if I never got to install a new ROM? I can't be without it for too long so any answers would be appreciated
Thanks,
Smernst
When you say button combinations are you saying you tried to get into download mode?
Sent from my SAMSUNG-SGH-I727
Sheolrock said:
When you say button combinations are you saying you tried to get into download mode?
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
Yes, exactly that
Smernst said:
Yes, exactly that
Click to expand...
Click to collapse
Sometimes download mode can work even if the screen isn't turning on. You should follow the instructions for download mode and see if Odin recognizes the phone.
Sent from my SAMSUNG-SGH-I727
Well there are symptoms of Brick See below and find ur category!!!!
appdroid said:
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware.
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed. If its hard brick Here is thread that will help you!!!
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Click to expand...
Click to collapse
Smernst said:
Yes, exactly that
Click to expand...
Click to collapse
appdroid said:
Well there are symptoms of Brick See below and find ur category!!!!
Click to expand...
Click to collapse
UPDATE:
I just went in to the AT&T store and they are sending me a new phone tonight and it should be here tomorrow!
Now, does anyone have a guide to recommend for getting, say, MIUI onto the Samsung Galaxy S2 Skyrocket? I don't know enough about the versions, mp5, etc to do it alone, and a safe guide would really help me
Thanks
MIUI rite now is not daily driver has lots of bugs and Here is link scroll down it will give you step by step instructions.
Smernst said:
UPDATE:
I just went in to the AT&T store and they are sending me a new phone tonight and it should be here tomorrow!
Now, does anyone have a guide to recommend for getting, say, MIUI onto the Samsung Galaxy S2 Skyrocket? I don't know enough about the versions, mp5, etc to do it alone, and a safe guide would really help me
Thanks
Click to expand...
Click to collapse
Got it, thanks
Also, if my phone is truly hard-bricked the AT&T guys that I return it to will not be able to tell that it is rooted will they?
Thanks
No att ppl are dumb and they can't even turn on the phone so they won't be able to say that it was rooted. When they ask you anything about rooting just pretend like you don't know what they are talking about.
Smernst said:
Got it, thanks
Also, if my phone is truly hard-bricked the AT&T guys that I return it to will not be able to tell that it is rooted will they?
Thanks
Click to expand...
Click to collapse
appdroid said:
No att ppl are dumb and they can't even turn on the phone so they won't be able to say that it was rooted. When they ask you anything about rooting just pretend like you don't know what they are talking about.
Click to expand...
Click to collapse
Okay sweet thank you for all the help!
See you around
Smernst
Hope next phone doesn't give you any grief.
Sent from my SAMSUNG-SGH-I727 using xda premium
Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.
If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...
droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.
droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app
T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app
Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1
droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.
Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1
Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!
I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app
I have a Samsung Galaxy S2 Skyrocket (SGH-I727 / AT&T) that I cannot get to connect to a PC after weeks of trying. I have tried to read through hundreds of threads regarding this issue and it seems others have had similar issues but nothing quite like this.
When I connect my phone to a PC, it does charge but Windows XP or Windows 7 will not recognize the phone. Anytime it is connected an error pops up stating "USB Device Not Recognized. One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it."
So to clarify, I have tried the following suggestions from others to troubleshoot and try to narrow down the issue:
1.) I have tried 4 separate USB cables, including the original OEM Samsung brand data cable that came with the phone.
2.) I have tried 3 separate PC's (2 with Windows 7, 1 with Windows XP).
3.) I have installed Samsung Kies on all 3 PCs, uninstalled and reinstalled the program as well as the Samsung Drivers on multiple occasions.
4.) I have done a factory/data reset on the phone twice to see if this was an issue caused by other apps I've downloaded in the past.
5.) I have tried to use USB Debugging/Developer option and then connect the phone to no avail.
6.) I have tried USB Mass Storage option before connecting the phone.
7.) I have tried to connect the phone to a PC in Samsung's default recovery mode and still showed it was not a recognizable device.
8.) I have tried a friend's galaxy S3 on all cables and PC's mentioned above and Kies immediately recognizes her phone.
9.) I have attempted to clean the physical microusb port with a small brush to make sure the contacts were clean and not being blocked by something.
10.)I have done a battery pull and about 20+ phone resets for all above mentioned attempts.
Based on all of these attempts without any success, it seems to me that this being a PHONE hardware issue is highly probable. I've ruled out just about every other scenario and I'm wondering at this point if my phone's Micro USB port is fried somehow.
Has anyone heard of this or is this a reasonable possibility?
I have tried just about everything I can so far, if anyone has any other suggestions or has any information that may confirm my suspicion, please let me know.
This all came about in the past week due to Jelly Bean being finally released by AT&T / Samsung for the Skyrocket and unfortunately, this update only seems to be available via Kies and a direct data cable to a PC. I have tried to go to Settings > About Phone > Software Update > Check for Updates (while connected to Wifi with a full battery) and the phone has told me 3 times over the past 3 days that my current Ice Cream Sandwich v4.0.4 Android is the most current software up to date. I'm guessing they're not planning on releasing Jelly Bean to the Skyrocket via OTA air updates....so now I'm stuck.
Bizarre issue you got there mate!
Sorry to disappoint you, but this isn't the right section for your device.
Please report ur post to the moderators and have it moved here:
http://forum.xda-developers.com/forumdisplay.php?f=1372
Thank you..
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Bizarre issue you got there mate!
Sorry to disappoint you, but this isn't the right section for your device.
Please report ur post to the moderators and have it moved here:
http://forum.xda-developers.com/forumdisplay.php?f=1372
Thank you..
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
you sent him to the i777 forum?
as to op, seems a bad/dead usb port
read this on installing stock firmware even w/a dead usb port http://forum.xda-developers.com/showthread.php?p=29977559#post29977559
vincom said:
you sent him to the i777 forum?
as to op, seems a bad/dead usb port
read this on installing stock firmware even w/a dead usb port http://forum.xda-developers.com/showthread.php?p=29977559#post29977559
Click to expand...
Click to collapse
Wow, thank you so much. This is the first thing I've seen from anyone regarding a possible fix outside of direct USB connection. I sincerely appreciate it!
xyberelite said:
Wow, thank you so much. This is the first thing I've seen from anyone regarding a possible fix outside of direct USB connection. I sincerely appreciate it!
Click to expand...
Click to collapse
You should also try a different computer if you can. It works on my laptop but not my pc. I have no idea why and have tried everything I can think of. Also, use the usb ports on the back of the computer, not the front
Edit: sorry I didn't read your whole post.
Sent from my SAMSUNG-SGH-I727
You should probably hit this.
vincom said:
you sent him to the i777 forum?
as to op, seems a bad/dead usb port
read this on installing stock firmware even w/a dead usb port http://forum.xda-developers.com/showthread.php?p=29977559#post29977559
Click to expand...
Click to collapse
Well after getting into the details on the post, it looks like this is created for a phone that already has a custom recovery such as CWM or TWRP installed. Since I do not have a USB port to use on this phone as of right now, is there any way to install a custom recovery on my phone without using USB?
I did download the stock 4.1.2 Jelly Bean firmware directly on the phone's default directory already and it's sitting there in a zip format. If I'm not able to root and/or install a custom recovery without using a USB cable, would it be possible to install the stock firmware using the default samsung recovery mode?
xyberelite said:
Well after getting into the details on the post, it looks like this is created for a phone that already has a custom recovery such as CWM or TWRP installed. Since I do not have a USB port to use on this phone as of right now, is there any way to install a custom recovery on my phone without using USB?
Click to expand...
Click to collapse
Yes you need to search the skyrocket threads the answer is out there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xyberelite said:
Well after getting into the details on the post, it looks like this is created for a phone that already has a custom recovery such as CWM or TWRP installed. Since I do not have a USB port to use on this phone as of right now, is there any way to install a custom recovery on my phone without using USB?
I did download the stock 4.1.2 Jelly Bean firmware directly on the phone's default directory already and it's sitting there in a zip format. If I'm not able to root and/or install a custom recovery without using a USB cable, would it be possible to install the stock firmware using the default samsung recovery mode?
Click to expand...
Click to collapse
no afaik, but read below
mtdew said:
Yes you need to search the skyrocket threads the answer is out there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
if there is ive never seen it, let us know how, that is how to install a rom/firmware w/out custom recovery and w/a dead usb port
Crap if he's bone stock then no if it were stock rooted he could use dd commands with terminal emulator.
Also nowhere in his description did he ever say he deleted the old drivers from device manager.
Also I'm wondering how you are installing these drivers.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
no afaik, but read below
if there is ive never seen it, let us know how, that is how to install a rom/firmware w/out custom recovery and w/a dead usb port
Click to expand...
Click to collapse
Well I did find this older thread that will supposedly allow me to install CWM and root without using a USB cable or PC. I'm going to try this since you all have confirmed that I'm not able to install a stock firmware/rom using stock recovery.
http://forum.xda-developers.com/showthread.php?t=1501719
Edit - Didn't work, apparently this was for 4.0.3, not 4.0.4.
I'm going to need to figure out how to root and get CWM on my phone just to install Stock Jelly Bean all without using a USB cable. Still no luck so far.
mtdew said:
Crap if he's bone stock then no if it were stock rooted he could use dd commands with terminal emulator.
Also nowhere in his description did he ever say he deleted the old drivers from device manager.
Also I'm wondering how you are installing these drivers.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I initially thought he had cwm/twrp installed
xyberelite said:
Well I did find this older thread that will supposedly allow me to install CWM and root without using a USB cable or PC. I'm going to try this since you all have confirmed that I'm not able to install a stock firmware/rom using stock recovery.
http://forum.xda-developers.com/showthread.php?t=1501719
Edit - Didn't work, apparently this was for 4.0.3, not 4.0.4.
I'm going to need to figure out how to root and get CWM on my phone just to install Stock Jelly Bean all without using a USB cable. Still no luck so far.
Click to expand...
Click to collapse
that's not for our phones, that would of bricked ur device if it had flashed successfully
get ur usb port fixed or try some tips in fixing it in the 1stop sticky
edit: try this http://forum.xda-developers.com/showpost.php?p=34906725&postcount=6
vincom said:
I initially thought he had cwm/twrp installed
that's not for our phones, that would of bricked ur device if it had flashed successfully
get ur usb port fixed or try some tips in fixing it in the 1stop sticky
edit: try this http://forum.xda-developers.com/showpost.php?p=34906725&postcount=6
Click to expand...
Click to collapse
It wouldn't work. Nothing will install in Android System Recovery <3e>. Everything I tried still came back with Signature Verification Failed.
I also tried lifting the "tongue" inside the usb port on the phone several times previously and that didn't work either. I must assume at this point the usb daughterboard or something inside is messed up.
Since stock recovery can't install any type of files and I can't connect the phone to a PC in any way and my phone is 100% stock without root or any custom recovery, I can only imagine I'm stuck in this situation. I have yet to see any solutions for getting root or installing CWM without having a USB connection that works. Unless I can do either of those things, it looks like I'm SOL for updating from ICS to JB.
If they had only made Jelly Bean an Over the Air update, none of this would be a problem really.
xyberelite said:
It wouldn't work. Nothing will install in Android System Recovery <3e>. Everything I tried still came back with Signature Verification Failed.
I also tried lifting the "tongue" inside the usb port on the phone several times previously and that didn't work either. I must assume at this point the usb daughterboard or something inside is messed up.
Since stock recovery can't install any type of files and I can't connect the phone to a PC in any way and my phone is 100% stock without root or any custom recovery, I can only imagine I'm stuck in this situation. I have yet to see any solutions for getting root or installing CWM without having a USB connection that works. Unless I can do either of those things, it looks like I'm SOL for updating from ICS to JB.
If they had only made Jelly Bean an Over the Air update, none of this would be a problem really.
Click to expand...
Click to collapse
Too dangerous the ota bricks tons of people when they do it I can only assume at&t is tired of it and opts for kies only. Also you could buy a daughter board and replace it. It's a relatively easy fix.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Too dangerous the ota bricks tons of people when they do it I can only assume at&t is tired of it and opts for kies only. Also you could buy a daughter board and replace it. It's a relatively easy fix.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So .... lesson learned here is that you CANNOT root a phone or install any custom recoveries such as CWM or TWRP without having a working USB connection. As a result, you CANNOT install any updates, stock firmwares and especially custom roms without the above.
Only option at this point is to order the replacement part for the USB port on the phone or to purchase a new phone (if it's outside of the warranty period).
xyberelite said:
So .... lesson learned here is that you CANNOT root a phone or install any custom recoveries such as CWM or TWRP without having a working USB connection. As a result, you CANNOT install any updates, stock firmwares and especially custom roms without the above.
Only option at this point is to order the replacement part for the USB port on the phone or to purchase a new phone (if it's outside of the warranty period).
Click to expand...
Click to collapse
No you need USB to root that's it technically. If you have root you can install a recovery IMG without a computer using a terminal emulator and dd commands.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks for the update. Hopefully it will help others:thumbup:
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
mtdew said:
No you need USB to root that's it technically. If you have root you can install a recovery IMG without a computer using a terminal emulator and dd commands.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
yes and no, its the chicken and the egg kind of question, for the sr to get root u need to flash the su files, but u need to have a custom recovery to flash the su files. is there a way to get the su files onto the sr w/out a custom recovery? I haven't seen one yet unless there was a oneclick method which I never used
vincom said:
yes and no, its the chicken and the egg kind of question, for the sr to get root u need to flash the su files, but u need to have a custom recovery to flash the su files. is there a way to get the su files onto the sr w/out a custom recovery? I haven't seen one yet unless there was a oneclick method which I never used
Click to expand...
Click to collapse
I used a one click waaaaaaaaay back when the phone was released probably wasn't supported lol but this was long ago on 2.3.5.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
I used a one click waaaaaaaaay back when the phone was released probably wasn't supported lol but this was long ago on 2.3.5.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There is no one click available for 4.x forward.
I am wondering, however, if something like this would work:
http://forum.xda-developers.com/showthread.php?t=1877270