Hi,
until yesterday i had a perfectly working fast and snappy device:
JM5, Hackeclair, Tayutama´s update.zip lagfix, oc 120v2.3 kernel
then i tried to update the kernel to oc120v3 which worked out well and the device seemd running well so far. after some hours the device started to behave somewhat strange, it kept telling me "usb connected" again and again and again... so i got scareded and reflashed the 120v2.3 kernel. badly with no effect on the behaviour of the phone. so i just got scared eaven more and tried to reapply a nandroid backup of my virgin phone when i got it just to realize that this nandroid backup was far away from my original version, it showd me the wrong firmware number, did not overwrite the kernel and the csc and such stuff.
then i realized that i can only turn on my phone when it is connected to the charger and the green battery is showing, if i try to turn it on with usb disconnected it shows me the (not really) spinning wheel and then goes black again just to show the wheel again. also it often just crashes during sleep.
so what now? i cant reflash stock firmware since it is not available anywhere (a1 telekom austria branded) and so can not send my phone to repair...
any ideas someone????
you can send to repair saying it is dead. if it doesnt boot up they wont know what kernel or f/w is on it.. (a little dishonost since you toasted it).. or you can chalk it up to experience and buy a new one.. i never oc the extra speed is not needed and it chews through battery anyway.
just download a full firmware like JF3 then using odin and clicking the repartition option flash it to get rid of the oc kernel. I never mess with oc'ing as it tends to screw up your processor. Hopefully yours has not been fried.
it cant be the cpu, since it does start up when its connected to the charger, to me it seems more like the usb port of the device is defect (that could be why it always shows that "usb connected" notification) or somehow maybe the bootloader got messed up. actually the device is running well with a fresh installation of jm5 (repartitioned) except of not starting and those notifications...
also it could be somewhat hard to find jf3 since samsungfirmwares is down
Same thing happened to me a week ago. The usb connected message and the spinning wheel of nothing appeared on my Singapore galaxy set last week.
Went down to Samsung service center and showed them the phone. They were highly suspicious that this was caused by some custom firmware but later they honoured the warranty after some inspection.
2 hours later, my phone was fixed with Samsung telling me that it was because of the motherboard and that they had replaced a new one.
Hope you won't have trouble getting Samsung to do the warranty for you. Good luck.
Sent from my GT-I9000 using XDA App
FadeFx said:
also it could be somewhat hard to find jf3 since samsungfirmwares is down
Click to expand...
Click to collapse
Get them why you still can: http://www.samsung-firmwares.com/i9000.htm
Also right click the site and view source and save it as a html file then you will always have the links
Sounds like you killed the motherboard. Time for warranty. Next time how abouts you dont overclock
Sent from my Apple Newton 2100
kurtisnet said:
Same thing happened to me a week ago. The usb connected message and the spinning wheel of nothing appeared on my Singapore galaxy set last week.
Went down to Samsung service center and showed them the phone. They were highly suspicious that this was caused by some custom firmware but later they honoured the warranty after some inspection.
2 hours later, my phone was fixed with Samsung telling me that it was because of the motherboard and that they had replaced a new one.
Hope you won't have trouble getting Samsung to do the warranty for you. Good luck.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Did you have yur device overclocked, or just a custom firmware?
FadeFx said:
Did you have yur device overclocked, or just a custom firmware?
Click to expand...
Click to collapse
Nope not overclocked.
I was using the Lagfix 1.0 with Root access only when the funny thing happened. I was running DXJG4 official firmware.
hmm, on investigating further, i realize that if the phone is turned on with charger connected, and i instantly disconnnect it when it starts up, it operates normally, so i just need a charger or usb cable to turn it on and everything is ok. with this i can live for until i find time to bring it to service.
n1kon said:
Get them why you still can: http://www.samsung-firmwares.com/i9000.htm
Also right click the site and view source and save it as a html file then you will always have the links
Click to expand...
Click to collapse
hmm, too late... seems its offline... did you maybe do the backup? if so, could you please pm me?
FadeFx said:
hmm, too late... seems its offline... did you maybe do the backup? if so, could you please pm me?
Click to expand...
Click to collapse
try here: samfirmware.webs.com
FadeFx said:
hmm, on investigating further, i realize that if the phone is turned on with charger connected, and i instantly disconnnect it when it starts up, it operates normally, so i just need a charger or usb cable to turn it on and everything is ok. with this i can live for until i find time to bring it to service.
Click to expand...
Click to collapse
Same with my phone but even when it managed to start up, the phone will stop responding after around 1 min of screen off.
Sent from my GT-I9000 using XDA App
Get the JF3 here:
http://rs556.rapidshare.com/files/415212358/I9000XXJF3.rar
Related
Im really really hoping that someone can help me here
It started this morning around 10:00 or so - I took my phone out to check my messages, everything is working fine. I lock the phone and put it standby (power button) and *surprise*, it locks up and wont come out of standby
So i just re-set it (like im forced to do 20 times a day) and instead of booting it went straight to this red/green/blue screen. At the bottom of the screen it just says "Serial" but doesn't actually give a serial.
I instantly thought it was bricked, so i removed the battery and left it out for a few mins. Then i put the batt back in, and it booted normally. I used it throughout the day with no problems.
Fast forward a few hours and it does it again but now it wont boot at all (ive reset the thing like 100000 times in the last hour ive been working on it).
WTF is going on?? Im really really hoping that it isnt too screwed to fix
The last program I installed was the SPB pack, but that was over a month ago, and i use the phone every day, multiple times a day.
Oh, and to make things worse i was planning on relying on my TomTom tomorrow
and the text on that screen says:
Kais1*0
SPL-1.56.0000
CPLID-8
And at the bottom it just says "Serial" but none is given.
This blows
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Do you see "USB" instead of "Serial" if you connect your sync cable to your phone when in the bootloader?
If so, I would download the latest carrier-branded rom and flash it to your device. As long as the rom is designed for your device, then you do not need to do anything special prior to running the file from your PC.
grandpareza said:
Have you recently tried to flash your phone? Have you ever? If you never have flashed it or attempted to use Olipof's app, then take it to the store and demand a new one.
Click to expand...
Click to collapse
I have never flashed it but i have spilled water near it (on the counter, the phone got wet but that was months ago and has no relation to this).
Can they check if it has been wet before?
When i plug it into my computer it says USB instead of serial. Should I try to re-flash with an updated rom and see if it fixes it or just take it in?
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
GSLEON3 said:
If you find me on MSN IM ([email protected]) we can run a diagnostic & see what the problem is.
Click to expand...
Click to collapse
Thanks, ill give you a buzz.
I need to finish and email a few things first (shouldnt take more than 30mins).
Actually, ill just message you tomorrow or something.
Ive been really busy this week.
well did you get it fixed? what did you do?
Yikes, that happened to a friend of mine, but he flashed his and then had to reflash it. I think there is a place on the back under the battery that they use to tell if it's been wet. I would take it back, even if flashing it fixes it, you don't want it to happen again.
oh and it doesn't mean serial like a serial number, it is a serial connection.
I havent been able to get it fixed.
I think ill try to flash it this weekend and see if that fixes it
You'll only make problems worse if you reflash. I've analyzed the MTTY output you've sent me & you have a bad NAND storage blocks.
You need to follow the directions I sent to your email account via MSN IM.
DO NOT REFLASH UNTIL YOU'VE TAKEN CARE OF THE BAD BLOCKS!!!
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
dockular said:
jackjohnson said:
dockular said:
Sup Jack, my Tilt is doing the
Kais1*0
spl-1.56.0000
cpld-8
Serial
problem that you had talked about. I read that huge thread, lots of great info in there. Although its unfortunate what happened to you, I'm really grateful of all the troubleshooting that you've done before me, so I know what works and what doesn't. Interesting to note that I have had the Tilt since the day it came out, and never cooked/ flashed my rom. I have been using the Tilt rom the whole time with no problems. Otherwise I'm a huge power user and have a ridiculous amt of software installed.
So after everything was all said and done, did you end up just replacing the device? Thanks again man
-Anthony
Click to expand...
Click to collapse
Anthony,
Yea I went ahead and replaced it. No matter what I did to reflash the original bootloader, and flash the original rom, I always ended up with that same problem. Did you notice that if you can't get it out of the bootloader, but you connect it to your computer, and while it's connect, you soft reset, that it boots? Just curious. that's what happened to me. Either that or I would have to yank the sim and battery, then try.
My tilt was working fine for about a month with a flashed rom, up until I started installing gobs of software on it. Just a thought. If I were you, I would get the device replaced. Especially if you've never flashed a new rom on it - it definitely should not be doing that.
Scott
Click to expand...
Click to collapse
My computer has been broken for a month or two. To answer your question - I haven't been connecting it to anything other than an AC outlet. Anything installed in the last couple months was installed OTA... I usually just obtain a CAB by downloading it directly onto my device.
Also, its weird but sometimes after I drain the batter with the RGB screen then recharge it (this process takes about a day) then hit the reset button, it will actually boot correctly. I am on the third time this has happened. It was bricked for a couple days, then after a combination of charging / depleting got it to boot into windows. Then it happened again, then again.
As long as I don't restart the phone it will stay in windows... If I restart then I lose it for a day or so. Interesting to note that since this has happened, phone calls connect, but I can't hear the other party and they can't hear me.
Also, I use the mini usb out to a 3.5mm stereo jack to stream shoutcast into my car stereo while driving. Last week (at the onset of my problem) the music was playing from the Tilt's speakerphone, and not going through the headphone jack as it normally would. A restart fixed this, but when it happened again a day or so later, the next restart is what got me to that boot screen for the first time.
One of us should post this in the forum...
Click to expand...
Click to collapse
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
dockular said:
this happened to me and someone else in XDA a while back. I saw his thread (link below) and then PMed him. I will copy / paste our PMs:
http://forum.xda-developers.com/showthread.php?t=344402
jackjohnson said:
And just an update, I never sent back my phone or did anything as far as bad blocks go. I just let the battery drain and booted it right up and now it works perfect. I have since installed a few cooked rooms and radios and have had no issues since. This RGB screen was isolated to just those few days that we were talking about in the PMs.
Click to expand...
Click to collapse
Umm... GOOD FOR YOU!!!
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
dude i wasn't telling him to not follow your advice. was just letting him know my story. as a matter of fact, after reading your original post I have decided to check for bad blocks on my phone.
GSLEON3;2021681
[B said:
Umm... GOOD FOR YOU!!![/B]
I had him perform a diagnostic & it reported HE HAS A BAD BLOCK! So unless you're psychic or can be sure that every problem with Boot Loader is the same as the one you had, I suggest sticking to what you know.
BTW, search the CURRENT threads, in the KAISER forum, & you'll see I've helped a few dozen people with this & similar issues.
Click to expand...
Click to collapse
Well, this has happened to one of our phones. Can you just post the fix here instead of requiring the email/IM rotuine?
The USB cord was removed from my phone in the middle of an Odin restore (it was stuck at factoryfs.rfs). Now the phone won't boot and it isn't recognized by my computer when plugged in. Did I find a way to brick this thing? Any help would be appreciated. This is my fourth Captivate and I'm sure AT&T is going to start to give me a hard time. Thanks.
build a jig or buy one on ebay. you need to get into download mode and reflash to sotck.
http://cgi.ebay.com/ws/eBayISAPI.dl...47234&ssPageName=STRK:MESELX:IT#ht_511wt_1139
http://forum.xda-developers.com/showthread.php?t=731989
Try all 3 methods to get into download mode first
yes, you can try the key combo first. but as i know, build 1010 or later wont work for the key combo.
Got it back to d/l mode. Now it's stuck at factoryfs.rfs-same as last time. I'm finished with this phone. AT&T can send me another. This is what happened to the past two phones. Stuck on a Odin restore and can't get it up again.
Edit: Just booted up. That's a relief. Thanks.
Thare187 said:
Got it back to d/l mode. Now it's stuck at factoryfs.rfs-same as last time. I'm finished with this phone. AT&T can send me another. This is what happened to the past two phones. Stuck on a Odin restore and can't get it up again.
Click to expand...
Click to collapse
If it had happened on more than one phone, you may consider looking at odin...maybe remove and reinstall our check your drivers or computer...just double check all of little stuff that might be so obvious that they are not obvious
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5 1200 mhz/100hz kernel
so if your potentially bricking the phones, what do you tell AT&T that happened? and do they not ever check or whats the deal?
As far as I know at the wareenty centers they check for physical and water if they do attempt to boot as long as nothing looks custom they wont bother with checking the recovery or key combos samsung takes care of the rest they just want functional hardware..oh dont mention anything about modding. If anything syncing crashed is the best explaination. Tested.
Sent from my replaced cappy XD
Just dont become a familair face or it might get flaged on your account. Study up before doing somthing new. Just crashed my test cappy writing this had to stop and reflash heh live and learn.
A tech here on the forums said they can tell if it has been modified in just "3 clicks".
Sent from my SAMSUNG-SGH-IDK?
noobfail said:
A tech here on the forums said they can tell if it has been modified in just "3 clicks".
Sent from my SAMSUNG-SGH-IDK?
Click to expand...
Click to collapse
Lol....uh huh....i also have a direct line to the white house
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5 1200 mhz/100hz kernel
Omg really?!
Sent from my SAMSUNG-SGH-IDK?
Just messin' around....what kind of tech? Att, samsung or other?
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5 1200 mhz/100hz kernel
He said he was a manager of an actual at&t walk in tech support store.
I rooted a phone and flashed to stock and returned it with no problems.
Sent from my SAMSUNG-SGH-IDK?
Sorry I'm late getting back. My phone is up and running again. Got in to D/L mode and flashed back to stock. Got stuck on the AT&T logo, but used Odin one more time and it booted right up. The first time I brought in the phone, the tech took it to the display for 2 minutes and called the warranty dept for me. I think that it helped that the Chiefs playoff game was on. They didn't seem to want to be bothered! The phone rep asked about water and physical damage. No questions about modding. The second time I did it at home over the phone. Again, no questions about modding. I told the rep both times that I was trying to transfer music to the phone via Kies and it crapped out on me. It always help to play dumb and act like you don't know too much.
Thare187 said:
Sorry I'm late getting back. My phone is up and running again. Got in to D/L mode and flashed back to stock. Got stuck on the AT&T logo, but used Odin one more time and it booted right up. The first time I brought in the phone, the tech took it to the display for 2 minutes and called the warranty dept for me. I think that it helped that the Chiefs playoff game was on. They didn't seem to want to be bothered! The phone rep asked about water and physical damage. No questions about modding. The second time I did it at home over the phone. Again, no questions about modding. I told the rep both times that I was trying to transfer music to the phone via Kies and it crapped out on me. It always help to play dumb and act like you don't know too much.
Click to expand...
Click to collapse
I had the same exact problem when i was just starting to mess around with roms and my biggest issue was the sequence that it took to flash properly. i kept opening odin then putting my phone in download mode and THEN plugging it into use as opposed to how it should have been which is holding vol up and vol down pressed then plugging in usb.
bugity said:
I had the same exact problem when i was just starting to mess around with roms and my biggest issue was the sequence that it took to flash properly. i kept opening odin then putting my phone in download mode and THEN plugging it into use as opposed to how it should have been which is holding vol up and vol down pressed then plugging in usb.
Click to expand...
Click to collapse
That's the weird thing. I'm somewhat new, but have been flashing my Captivate since Sept. When the original Cognition came out I was flashing daily. I think my problem was, it took longer than usual to flash to stock, I got impatient and didn't realize I could get to D/L mode by taking the battery out, holding power and inserting battery. I always used the button combo. Live and learn.
same problem
Ok i have the same problem as the original post stated, running odin and disconnected right at the beginning of the rom flash! this phone wont power up, and my jig (which i have used before) will not work! Is it done for!?
Ur last hope lays in adams Am I bricked thread, where u'll find an app that checks what state ur phone is in (linux or ubuntu needed)
nevermind, I tried harder and the jig worked, its one of the homemade jigs, where you cut up your charger, and use resistors to create the circut . . . . jankety but i got it to work thanks anyway though
Glad you got it, but I would buy a jig and keep it in a drawer. Just in case.
My Samsung Captivate was working fine a day ago when I was transferring video off of it to my PC. Now this comes up and I'm like WTH lol. I've never dropped my captivate or damaged it( to my knowledge).
I have read in other posts that the only way to fix this is to replace the mini usb port inside of the phone... If that is true could someone direct me to a site that sells it?
Or is It a battery issue? because It now has a problem with showing the charging battery symbol when its not charging now...
I also thought about going to At&T and letting them tell me what they think, only thing i'm afraid of is that without me being able to flash back to Official 2.1 Eclair they wont help me...
Any suggestions guys?
Bump T_T............
lol, make it totally bricked, att will not see if the phone cannot turn on.
Have you tried switching computers? My laptop stopped reading my phone, but my desktop picked it up just fine.
Try factory reseting and flashing to a new rom
Sent from my GT-I9000 using XDA App
Well I would Flash it to stock, but how would I do that without the use of USB, because no computer can detect my phone as it is now.... the USB Port is damaged I believe.
As for Bricking it how can I do that because they told me I could replace it because I'm under warrenty, but they also told me that if its found out of warrenty that they may charge me upwards to 480 bucks for the replacement. The guy on the phone told me it only applied to cosmetic and liquid damage though, he didnt mention stuff like flashing the OS or modding.
This is strictly a Hardware Issue as it was working 2 days ago.
lol, you can easily brick your phone by doing the following:
1. download a rom;
2. go to recovery mode;
3. start flashing the rom and remove the battery during the process;
never help people like this ... i feel guilty ...
lol ikr? Never thought I'd ever ask that xD.
Can you plug your phone in to the wall charger and it charge. When you plug.it into.the PC are you getting a message about USB device not recognized. Are you using a.deshktop or a laptop what OS. If you are using a desktop are you using a port on the back preferrably the one closest to the motherboard. These are all things to take into account.
If when you plug it into the wall.or computer your phone will charge then most likely there is nothing wrong with your micro-usb on the phone. Instead its the computer. I had the same issue and had to fight with it for days but now it works everytime I plug [email protected]
Sent from my SAMSUNG-SGH-I897 using XDA App
I am using windows on my laptop and Fedora linux on my netbook and I have tried to connect all of them to it and it failed and they all had the latest drivers and my usb development and all that stuff is as it should be.
like i said in the OP it was working 2 days ago perfectly and I did nothing to change it or damaged it in any way ( to my knowledge) maybe the usb port got messed up when i tried to charge it but I can still get a charge but the battery keeps showing its charging even when it is off of the charger.
Izurin said:
I am using windows on my laptop and Fedora linux on my netbook and I have tried to connect all of them to it and it failed and they all had the latest drivers and my usb development and all that stuff is as it should be.
like i said in the OP it was working 2 days ago perfectly and I did nothing to change it or damaged it in any way ( to my knowledge) maybe the usb port got messed up when i tried to charge it but I can still get a charge but the battery keeps showing its charging even when it is off of the charger.
Click to expand...
Click to collapse
only way to really know is by flashing another rom... use your mobile browser not xda app, and go to xda, find a rom thread, and use the mobile browser to download the rom over 3g... reboot into recovery to install it, it will be in the download directory on your internal SD...
Well I would do that but Now I have another problem... it turned off and now it wont turn back on!!!! UGGGGGGGGGGGGGGH!!
Izurin said:
Well I would do that but Now I have another problem... it turned off and now it wont turn back on!!!! UGGGGGGGGGGGGGGH!!
Click to expand...
Click to collapse
anything from the charger? might bee good that it finally died... the att service center should swap it out for you now that its dead...
Well I thought I should Follow up on my Question... Somehow I got my Samsung Captivate to magically connect to my PC and believe me it was very Wonky. And Soon as my PC detected it I hurried and Downloaded Odin for Stock 2.1 and Put my Captivate in download mode using Cognition's Download mode option in the hold button popup on screen.
Long story short I was finally able to get my captivate back to 2.1 and the reported problem still exists... I'm calling ATT right now for my replacement that should be here in 2 days ^_^
Thanks Again to all the people here at xda for your help, I deeply appreciate it!
place dg cf7 on sd card via another phone or use an alternate browser to download it also get clockwork mod rec.zip and boot into recovery install from there, thats how I got back to stock after same problem as you,warranty phone.
worked for me
Stuck at "Samsung Galaxy" boot screen, cant get into bootloader, computer wont detect
Hey everyone this has been a huge hassle for me for the last few days and was hoping someone could help me. I have had to resort to using my HTC Legend...which I love but it doesnt have what I need.
I was in recovery the other day trying to load a custom rom through the CWM and I went through and accidentally hit "format system". I couldn't cancel the process so I knew something bad was going to happen....I reboot the phone and for the last 3 days I have had it plugged into the Usb charger with no luck of booting, it has been stuck at the "Samsung Galaxy S 19000M" boot screen and no further. I took the battery out and tried rebooting it after a few minutes. No luck with this either, still stuck at the Samsung screen. I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button).
I have put it into download mode and and plugged it into the computer (I am running Windows 7 64-bit) and it will not detect it. I have all of the correct drivers, I know this as I have a friend who owns the exact same phone and my computer detects it just fine. Odin nor ADB will detect that there is anything AT ALL plugged into the computer. It does not even come up as, "android device", or "storage", there is nothing, nota, it is as if the phone isn't even plugged in. It will not detect in "download mode" nor while its stuck at the "Samsung Galaxy S" screen, and yes I have tried a different USB cable, and still nothing..
I am quite capable with electronics but I cannot find anything on the internet as of what to do. Is there anything that I could load on an external SD card that would force the phone to flash a ROM with new kernal and modem? I think the phone is empty that is why it is not booting, as if there is nothing to load on the phone. Is there anything at all that anyone can think of??? I am completely stuck. I wanted this phone to last until the Samsung Galaxy S 2 was released here lol.
I'm with Virgin Mobile Canada. Thanks!
Cant you get it into Recovery mode?
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Herman76 said:
Cant you get it into Recovery mode?
Click to expand...
Click to collapse
Hey herman, "I CAN get into "DOWNLOAD MODE" but I CAN NOT get into recovery/bootloader (hold volume up/home button/power button)."
profalbert said:
Have you tried heimdall?
You will have to follow the instructions coming with it to the letter (about installing some custom USB-driver).
Click to expand...
Click to collapse
Hey, I will search for that right away and let you know how it turns out. Thank you!!
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
azzledazzle said:
well if you have download mode then dont panic.
just flash a 3 file firmware along with pit file and re-partition and you will be fine
Click to expand...
Click to collapse
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Galaxy19000M said:
How can I flash any firmware if my PC will not detect the phone? When I plug the phone in there is nothing. Odin doesn't detect the phone, Keis doesn't detect the phone, ADB does not detect the phone, and I just tried Heindall, and it does not detect the phone..... Maybe the actual hardware for the USB plug in is faulty in its self, in which case I am screwed.
Click to expand...
Click to collapse
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
azzledazzle said:
i see..... i only read the last 2 posts and im always telling people off for not reading properly
have you tried the obvious steps such as
Un-install - Re install Kies
Run Odin as administrator
Tried Alternative USB port - direct into the PC motherboard
Finally a different PC all together
hope you can get it workin hate to see another broken SGS
Click to expand...
Click to collapse
I have tried, uninstall-re install of kies, run odin as admin, alternate usb port, anddd I tried plugging it into my laptop...no luck...this absolutely driving me nuts because I know the phone cant be bricked, if I can get into download mode I SHOULD be fine but for some strange reason the phone seems to be undetectable...ahhhhhhhhhhhh if only there was just some way to access the internal storage or a program that would force a flash through an external SD....
I am going to try loading Ubuntu on my computer on one of my HDD and see if it will detect the phone. I am assuming this is my last option and I have high hopes as Ubuntu detects almost anything...I will update...if it doesnt work I might be looking into taking apart the phone its self and intalling a new USB plug in on the phone motherboard...
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
Click to expand...
Click to collapse
yeah lol like I said in the first post I tried a different USB cable all together.
I have two HTC Legends, tried both cables from them, plus the OEM cable that came with the SGS
azzledazzle said:
im not sure of any other steps
last resort.... have you tried another USB cable ? like your friends cable that he uses for his phone ?
EDIT: if i was you i WOULD NOT take the phone apart.... if you do and it does not work, your warranty will be void,
at least if you cant get it working you can send it off for repair and blame kies, you will have a good chance of getting it fixed by samsung than you would yourself
Click to expand...
Click to collapse
I dont know if it has been opened already by someone else. I bought the phone for $180 CAD from a sort of "2nd turn" site. As in it was being sold as is. The phone problem reported by them was that the USB connectivity was not working. When I originally got the phone from them everything was working correctly, except the USB connectivity like it stated. It came ROOTED and loaded with the leaked version of Froyo before it was out so I automatically assumed that was causing the USB problems. I got around to changing the ROM with a reported working USB using CWM. But, still no luck with USB connectivity. I just dealt with the problem and flashed everything through CWM. Which led me to this...ugh
Is there supposed to be a warranty seal behind the battery cover? Over the screws like there usually is? Cause I see nothing..
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
azzledazzle said:
thats not good news.
there is no warranty sticker, but samsung could find out if the phone has been opened.
It depends on the actual repair guy, to be honest, samsung will have 100's of phones to repair daily, the majority just get passed on - flashed - wiped - boxed and sent back to the owner.
however if some (P)Rick is having a bad day and wants to find out why the phone is in for repair, and he finds out its been opened up, or its had custom firmware, then he can refuse to fix the phone or send it back to you with a bill included lol.
so you have to have a good excuse incase the worst happens.
if you dont fancy your chances and you feel capable of replacing the USB yourself then hey go for it !!
Click to expand...
Click to collapse
Well thank you for all the help. I am going to try installing Ubuntu first and see what happens, I have never had any driver issues with that OS EVER so if its detectable, Ubuntu will be the one to detect it. If that doesn't work I might take my chances and send it in. And if like you said that one person decides to screw me over, they at least have to send it back to me, in which case I will just open it myself and change the USB plug in like I said. (which might not even be the problem...)
Is there anyway to tell on the out side without opening it if it has indeed been opened before???
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
azzledazzle said:
erm..... i dont think so, but i dont know what measures samsung have took to find this out.
if it was me the obvious things i would look for is, damaged screw heads and scratches down the sides - where the casing has been prised open. other than that i would not know what to look for
either way, i hope u get it fixed
Click to expand...
Click to collapse
Well I sent my phone in to Samsung last week and I just got it back today! I opened it up and I guess the problem with the phone was pretty bad lol they just gave me a new phone, I was thinking it was refurbed but it said right on the repair receipt "condition=NEW" I am extremely happy.
That aside, do you know if you can use the SGS II if it is unlocked in Canada?
Hi everybody,
a friend of mine got his HTC One (black) yesterday and rooted it. He flashed a proper custom ROM on it which I and another one of my work buddy use as well without any issues (InsertCoin). No further flashes done, no other custom kernels, no S-Off, no SuperCID. Just unlocked Bootloader and custom ROM.
He let the device run dry yesterday evening so it shut off itself automatically. He put it on his charger, the phone turned on, he did some surfing and installing apps from the market and set up his alarm. The phone charged over night and he was also able to switch off the alarm this morning.
He got ready for work, got into his car and wanted to switch on the screen on the one for some good tunes. But the screen stayed black.
When I arrived at work, he was a little upset and panicked a little. I thought I was able to recover the device.
After plugging it in to my work computer, the device manager just shows a unknown device called "QHSUSB_DLOAD" so I went to google and looked it up..
Weird thing is: QHSUSB_DLOAD wasnt seen yet on the HTC One (M7) as far as I can see it and it was pretty bad on the HTC One S. It means "Qualcom High Speed USB Download Mode" and on the One S as well as on the Nexus 4 this devices showed up after the bootloader got damaged or the device got stuck in that mode for good.
When plugging the device in (USB / Wall charger) the charging LED doesnt turn on at all, the capacitive buttons dont start to blink while holding down the power button as well.
This thing seems to be gone for good.
But aint it the way that we dont even have any access to the bootloader if its not an official update from HTC? Signature check and stuff? Since the device was rooted, no OTA updates were able to arrive at all. He told me that he didnt try to flash anything after we flashed the custom ROM.
Any advice on that?
Did you even try booting the device first thru hboot/bootloader or holding the power button to force a restart? If you did try connecting the device while on QHSUSB_DLOAD and execute a compatible RUU on your PC. RUU uses android's download mode to flash the ROM so it should be repaired by an RUU.
Already tried, no luck. Tells me the device has not been found.
I am sorry to hear that, man, but from the looks of it your friend now has a paperweight. I'd take it to an HTC service center and hear what they have to say regarding this; of course it will no longer be covered under warranty, but maybe they can fix it for you for a price or something.
Are you sure RUU can't find the phone? If it can't then I guess only a JTAG box can fix it so either send it to HTC for repair or have someone who knows JTAG fix it.
Try4Ce said:
Already tried, no luck. Tells me the device has not been found.
Click to expand...
Click to collapse
I saw this issue on my friend's GS3 once. It was hard bricked and there was no way to recover from what I read (at least on the GS3). I know I saw a thread somewhere here in this forum about the same issue and someone linked to a Sensation thread where there was a way to fix it but I'm not sure if it would apply to the One
Same problem - but the phone magically fixed itself!
I had the exact same problem with my HTC One as described in OP...
My alarm went off in the morning and I set off for work, my battery was low but I thought that I would just charge it when I got to work. I was playing a game (Dungelot) whilst waiting for my bus and was receiving pop up messages about low battery. When it got to 4% left I decided that I would finish the level then close the game down, but as I was just about to finish, the phone went blank...I assumed that I had naturally used up all the battery life and although peeved that I had probably lost my progress in the game, wasn't too bothered.
I got to work and plugged my phone in to charge on my computer. The computer wanted to search for QHSUSB_DLOAD drivers but I thought this must be what it does when my phone isn't switched on and it finds the device. I cancelled the search prompt and tried to switch my phone on...nothing happened.
I tried for the rest of the day, trying to force shut down the bricked phone by holding power in for 30 secs, trying to power into boot mode etc...everything! But the phone would not switch on and the only response I got from it was a little orange LED every now and again and the QHSUSB_DLOAD prompt.
After googling the prompt - I found myself here and REALLY began to sh*t my pants! I've only had the phone less than a month and felt I was tech-savvy enough to flash my phone with a new ROM (Android Revolution HD) to try and get rid of some of the bloatware. I had flashed a new ROM successfully a coupld of weeks before and everything had been fine up that point.
I went home depressed but throught i'd try to plug my phone into a proper mains charger rather than my work's old USB cable (that came with my previous HTC Desire Z) I was going to try a long night of searching the net to try and find a way where I could at least recover the photo's, Zoe's and vids of my new born son but had such a headache that I gave up and went for an early night.
I was woken unexpectedly the next morning by my phone alarm going off! I stopped the alarm and the home just went to Home screen as normal! I don't know how or why these events happened...whether it was the flashed ROM, the game I was playing, the battery running out before the phone could shut down properly, the old USB cable in my work not charging but detecting the device or a combination of all of those, but so far, the phone jumped back into life with the alarm after being charged in the mains all night!
Thought i'd share as it may just help someone else out there who encounters this!
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 08:20 PM ---------- Previous post was at 08:20 PM ----------
Also, its not unheard of. I've seen it happen a few times in these forums.
Sent from my HTC One using XDA Premium 4 mobile app
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
lampel said:
I wonder if having your alarm set saved you. This phone will actually power itself on so as not to miss an alarm.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
same here
Any idea how to fix it?
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
Jtag or send it to HTC is the only way.
Sent from my HTC One using Tapatalk
My Solution
Had the same Problem.
My Solution was to Download "HTC One (M7) Toolkit" and force Fastboot.
Pushed Power and Volume Down until Screen was Flashing.
Took about 2 minutes and the Phone was rebooting.
I have no idea what was happening. I have no idea if this helps or works for others. But its worth trying.
Sorry for my bad english.
Try4Ce said:
Any advice on that?
Click to expand...
Click to collapse
CoryTallman said:
Some phones have miraculously come back from QHSUSB_DLOAD with no explanation of why. Other than that it usually means a hard brick. You can send it to HTC, they will charge you and replace the main board, from what I've heard.
Click to expand...
Click to collapse
bkmenon said:
Hi Try4Ce,
I am facing the same issue. If your friend's phone is fixed, can you share with me how the fix happened?
Many thanks in advance.
Krishna Menon.
Click to expand...
Click to collapse
Delingerb said:
Any idea how to fix it?
Click to expand...
Click to collapse
This is some kind of mode that is enabled when you hold power on button when the device battery is completely drained. i.e. when you try to turn device on it will not boot up (Special I was connected to usb cable via PC to charge my phone NEXUS 4 when I get into this mode). I saw a similar mode where nvflash commands are executed something like APX(can't recall correctly) with Tegra 4 device (that time also I was connected with a usb cable and charging the tablet when it was completely drained!). A simple solution to quit this issue is DO not Panic and let the device get a little charge. After that boot normally with the power button. In case if it didn't try other modes to enter such as recovery or fastboot reboot commands if your device is getting recognised..
QHSUSB DLOAD means its a hard bricked phone, No amount of messing about with it will fix it, Send it to a service centre, it will probable have to have the motherboard replaced..Sorry
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
danielr18 said:
My device entered in QHSUSB_DLOAD mode after the 4.4 ota was installed and 30 minutes later, I was able to turn up the phone. It restarted itself like 5 times and then it was normal. Miracle..
Click to expand...
Click to collapse
What do you mean by "force"? What did you do exactly?
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
danielr18 said:
My device wouldn't do anything, and it was in QHSUSB_DLOAD . But when I later pushed the power button for a minute, it worked.
Click to expand...
Click to collapse
mine spent the night carrying on waking took the charger and the green light for continued access, tried to turn it on but could not. After reading your response, I tried to hold the power button for longer. After 15 seconds the phone rang and the light came on, everything works perfect so far
Today while I was updating firmware phone gone to QHSUSB_DLOAD mode.
I am guessing it's end of road. :crying: