Related
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?
Okay, how about this one?
My phone WAS stuck in one of these infamous boot loop/battery thingys, but I just removed the battery and charged it with an external RC Battery charger ($60, charges EVERY type of battery, everyone should have one). When I put it back in, everything was great. I then used Flashtool to unlock the bootloader without problem. Then I went to flash a stock ROM to the thing via flashtool and left it go. When I came back, flashtool had completed the operation without errors, and had last told me to reset the phone. The phone, however, wouldn't turn on or respond AT ALL to anything I did. So I took the battery out and charged it, thinking it must just have run out of power but upon putting the battery back in, the phone remained unresponsive.
No modes, no lights, nothing. The ONLY thing that happens is if I have the thing plugged into the PC and I hold the UP (maybe the DOWN, i don't remember) button, the PC detects and tries to find drivers for something called QHSUSB_DLOAD... qualcomm High Speed USB download drivers, maybe? I've looked around and somewhere someone said that for another Xperia (don't remember which one) THEY had read that you could get the phone into flashboot mode somehow once installing the drivers. They supposedly come with the "gordon's" USB tools or whatever the heck it's called, but I couldn't get xp to accept anything included with gordon's as a proper driver. Yes, I know I had to INSTALL gordons, since an exe sure isn't a driver.
I've also found that, at least for the Galaxy 2, once you're at a point where it's asking for QHSUSB_DLOAD drivers, there's nothing you can do short of JTAG repair. However, as my friend so succinctly put it, "That's not a galaxy, it's an xperia" so I'm still holding onto hope. Anybody have any ideas? Or where I could find a QHSUSB_DLOAD driver and what to do with it then? I AM planning on getting a jtagger soon, so maybe this'll be the reason I finally do.
1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium
xperia
gregbradley said:
1) you did not unlock your boot loader successfully using flash tool, that's impossible.
2) uninstall all Sony and any phone software/drivers from your PC
3) charge your phone for at least 24 hours without touching it.
4) install pccompanion to your PC
5) with the phone still turned off, press and hold the volume down button and attach usb cable, then whilst still holding the volume button press the power button until the phone vibrates.
6) the phone should go in to flash mode and you should be able to repair using flash tool, if it doesn't try the next steps.
7) install flash tool and run drivers.exe, choose flash mode, fastboot and tx drivers.
8) press and hold volume. Up and power button until phone vibrates and go back to step 5
9) after you have tried all this please let me know what happens
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) Are you sure of that? I mean, it even has a BUTTON for it... it just automates the flashboot thingy if I remember correctly... the thing is, when I was writing my post, I wasn't sure if I was confusing this phone with another I was working on right then... but, no I'm pretty certain I did it through flashboot. Maybe not. Anyway, it wouldn't have even let me flash if my bootloader was locked still, right?
2) Haha- I'm afraid that's not really possible, BUT I already have PC companion installed and it was working fine. (Can you unlock your bootloader through PC companion? Maybe THAT's what I did- I KNOW I didn't do it through the command prompt, though...)
3) Okay, I am actually trying this as we speak, though I did take the battery out and charged it fully already
4) PC Companion installed
5) asks for QHSUSB_DLOAD driver, never vibrates
6) I wish
7)done
8) does nothing
9) Okay, so I will allow that perhaps there are things going on that all the uninstalling and reinstalling would fix and so I will try it out on a clean computer here in a little bit, but I don't think I'm gonna have any luck. I'll let you know what happens...
1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium
greg,since 23rd February 2013 you can unlock BL via flashtool.You should know that...
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
Click to expand...
Click to collapse
http://www.flashtool.net/changelog.html
AFAIK that is just for the devices it could unlock before (2012 and before), not the newer devices that it could never unlock such as ours.
Sent from my LT30p using xda premium
gregbradley said:
1) I am certain you have not unlocked your bootloader via flash tool or by pccompanion.
2) step 3 said charge battery for 24 hours, so you have not done that yet.
3) the remaining steps need to be done after the charging, so please follow the instructions as I have said them
4) the way you keep confusing terms and mixing up words makes me think you have not really done your research before trying to flash your phone. Reading is a great thing, try post 2 of the all in one thread. (there is no such thing as flashboot, that's a weird mixture of two different things, flash mode and fast boot, you need to know the difference between them. Also you can flash roms with a locked bootloader, you need to understand the difference between rooting and unlocking)
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
1) http://news.softpedia.com/news/Sony...ts-Flash-Tool-for-Xperia-Devices-315706.shtml - no wait, that just says it's supported by flashtool. I'll keep looking. I could tell you real easy if my bootloader was unlocked or not, but the thing wont turn on Would flashtool have offered me the bootloader unlock button if it didn't support it for my device? It tells me how to get to flashmode erroneously (for MY model, not most) but I figured it just wanted me in flashmode so I put the phone in flashmode. Hell, maybe I never unlocked the bootloader and just tried flashing a stock rom... would flashtool have allowed me to try and flash a non-stock rom with an unlocked bootloader? Would THAT have bricked the phone? I'm gonna go see what the rom I flashed was called now....
2) yeah, as I said, I'm doing that right now. though I took the battery out and charged it, so I thought it might work... even still, it's not been on for 24 hours yet as I writing this, so waiting... is there something that being on the charger for 24hours does besides ensure the battery is charged? Calibration or something? I can assure you the battery is fully charged to peak capacity.
3) will do, though when it doesn't work, do you promise that we can try to talk about QHSUSB_DLOAD? I promise that when it DOES work, I'll happily thank you and admit that even though you haven't quite given me a reason WHY, leaving it plugged in for 24 hours did something more than charge the battery. I know that sounds sarcastic, but I really think there's a chance it could but as I said, I can assure you the battery is charged to peak capacity
4) so I call "flashmode" "flash boot" mode- I am quite well aware of the differences between flashmode and fastboot mode. Figured since the one said flash and the one said fast it was obvious. Man, I did my "research", I read the all-in-one thread, as well as others... I've done this to dozens of phones over the last 3 years and just recently an Xperia Play which acquainted me with many of the idiosyncrasies of the Xperia line, flashboot, pc companion, etc... so when, after 3 years I finally actually ASK a question, I start to get this particular brand of close- mindedness... the way you keep not even trying to actually answer my question makes me think you didn't necessarily read my post before offering up a standard "cookie cutter" recipe which you don't necessarily understand enough to see how it might not necessarily apply. My REAL question was about QHSUSB_DLOAD device requiring a driver since that's the ONLY RESPONSE I CAN GET AT ALL from a phone WITH A FULLY CHARGED BATTERY. (you see, there I wanted to say QHSUSB_DLOAD driver, but that's not quite correct- QHSUSB_DLOAD.dll would be a possible name for the driver, but it's really a device called QHSUSB_DLOAD which does not have a driver. See how I'm taking pains to watch my words so as to not promote confusion.)
Cause you're RIGHT, really; using the proper terms IS important, but can you tell me that you SERIOUSLY didn't know what I meant when I said flashboot mode instead of flashmode? Or that you knew what I meant, but you thought that I didn't ? Did I ever confuse the two terms flashboot and fastboot? "there's no such thing as a flashboot"... what a silly-sounding thing to say... anyway, I never said there was- just that there was a flashboot mode. )Anyway, I do appreciate the help, just not the attitude, y'know?
The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
What charging for 24 hours does is to make sure there is some charge in the phone. I am no technical expert here, I am just very good at fault finding and knowing a trick or two that helps. The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc) However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
All I am trying to do is guide you through some fault finding techniques and then give you some advice on things that have worked for people in the past.
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
EDIT
There is still no such thing as flashboot....its called flashmode
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.
i also have this problem.
my xperia TL won't response anything. Plug in to PC it searching for QHUSB_DLOAD driver.
now, phone still in my drawer for 4 month
gregbradley;45518226]The attitude was not meant (Nor I hope delivered, maybe its just a style of writing and trying to get to the point quick)
Click to expand...
Click to collapse
S'okay. Attitude was a big strong for what I meant, but I couldn't think of the right word at the time...
What charging for 24 hours does is to make sure there is some charge in the phone.
Click to expand...
Click to collapse
Yeah, that's what I had gathered... I just got out of a bootloop by charging the battery with a programmable peak charger, so I KNOW its got a full charge.
The majority of people on here do not do their own fault finding before asking for help so before I dive in and help people I want to know that something simple has not been overlooked.
Charging for 24 hours has helped about 80% of the people on here who claim a hard/soft brick and they have tried ABSOLUTELY EVERYTHING to fix it.
Click to expand...
Click to collapse
See, right- that's what I always hear everybody say on forurms like this... cause it's TRUE. Most people asking a question generally barely know the proper question to ask and when the DO, they don't think to SEARCH for it. (Although I've always found the Xda forum search EXTREMELY lacking; I'd do a search for a term in the xda search and get nothing so I had to go to google and find the proper xda page through IT. It's much better of late, though)
However, it has been my experience that everything everybody always complains about; people asking before even searching themselves, people asking questions but not providing enough relevant information for the questions to be answered, etc... all these "rules of conduct" are based around the avoidance of WASTED TIME/EFFORT. Which I whole-heartedly agree with. I almost never ask about anything on the forums because it's almost ALWAYS faster to find the answer myself. It's usually out there.. so when I DO post a question, I will give a detailed account of my situation, how I got there and where I'm at... so, with all that everybody says about reading BEFORE you post questions why does it always seem like NO ONE EVER READS MY QUESTIONS before answering? For example, this time I was just like- "wow, dude didn't even read the background, gave me a cookie-cutter set of instructions and didn't even TRY to answer my actual question!"
Anyway, as for the QHSUSB download, I have had that before and just a perseverance of starting again from scratch and charging worked. (That's why I asked you to wipe all sony/phone/adb etc software from your pc)
Click to expand...
Click to collapse
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service... galaxys don't have flashmode, know what I'm sayin? I'm thinking maybe if I get the QHSUSB_DLOAD driver qpst or (more likely) qxdm will communicate with the port and I can do something like getting it into flashmode or rebuilding it or just figuring out what happened.
Haven't had much luck finding the drivers, but I haven't really looked that hard yet...
However, I am sure you are aware that the majority of times this happens you are left with a hard brick. Google gives a lot of results on this about Samsung and HTC phones (All of which offer no solutions) but very little for xperia phones.
Click to expand...
Click to collapse
Sure am. Yeah, what led me to post was when every time QHSUSB_DLOAD was even mentioned by galaxy owners, the immediate consensus was that this always means you're bricked and require JTAG repair service. As you say, not much regarding xperia, although the ONE thing I saw was someone who said that THEY heard something about getting the driver and being able to parlay that up into getting it back into flashmode or fastboot mode but that's about it. I'm gonna keep on it...
NB
It is sometimes hard for me to hold the hand of all the users I help. I get between 20-30 PM's a day (Some of which are quite bad mannered because I have not replied within a few hours with a message on how to help them, that does not put me in a good mood) and check the Q&A thread (And general thread for those that cannot post in the correct forum) on a very regular basis in order to help people, but the increase in people not reading and just flashing means I cannot dedicate the time to being a personal assistant to all, you may have see 4 new threads in the Q&A section in the last 24 hours, all made by different users with the same problem, all of which occurred because they were flash happy and tried CM roms without unlocking the bootloader....
Click to expand...
Click to collapse
No doubt... it is sometimes hard for me to ask questions because most times I only end up having to bring the person supposed to be helping me up to speed simply to be able to ask the question and have the answer be (usually, but not ALWAYS) "you're guess is as good as mine". I don't mean you, just so you know; I'm speaking of "how it usually goes".
EDIT
There is still no such thing as flashboot....its called flashmode
Click to expand...
Click to collapse
oh, for sure. flashboot MODE, however- well, there's still no such thing, but at least it's not as blatantly misleading
In the past some users have called these two modes different things, got them mixed up or even thought they were the same thing, that's why I wanted to know which one you meant.
Click to expand...
Click to collapse
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Also, the flashtool you linked to in point 1 is the official flashtool for Sony that only works on unlocked bootloaders. The flashtool from the first post in the dev section is the original flashtool by Androxyde and Bin4ry (First developed for the x10) and is the one to use for flashing FTF's and the one you used from your original post.
Click to expand...
Click to collapse
[/QUOTE]
Yeah, I know; I posted that link thinking it said something other than what it did- like there's gonna be a news article about Sony adding support I edited the post and mentioned that and left the link instead of just deleting it. Dunno why.
All that the Sony flashtool can really do is return you back to stock, right? I think I read something like that...
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?
adol.ivxx said:
For real? You've actually had that before and come out of it? Was it on an xperia device? That means there IS hope beyond JTAG service...
Click to expand...
Click to collapse
Yes, but it only happened the once, a fair few years ago before I really had heard of the problem. That's why I can not be quite sure how I fixed it, but it certainly was nothing more than perseverance of trying different things.
I was actually talking about fastmode and fastflash mode, but I would expect you'd never heard of THEM before, either?
Click to expand...
Click to collapse
Not for Sony Xperia devices.
So anyways, I tried it after charging 24hrs but there was no difference. Gonna look into this Qualcomm HSUSB Download driver- ANYONE know ANYTHING about it?
Click to expand...
Click to collapse
Sorry I could not have been more help. I will continue to dig around and ask others I know that might shed more light on this. I will post here again as when I have something you might appreciate. Good luck.
Ur phone is hardbricked
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Phenitei said:
Hi everyone.
A few days ago a non tech-literate friend of mine told me that he had dropped his phone in the sink (clean, cold water, about three weeks ago). He had since bought another rolleyes: shame to not even try to repair it!) but had precious data on it. I agreed to try and recover it from him as he's quite a good friend. Since I only got the phone long after the incident, it is as far as I can know perfectly dry. I have never had any dealings with Sony before (phone-wise)... I think the data should be attainable, I just don't have the knowledge yet.
Symptoms :
When plugged off, the phone just sits there with really nothing happening.
When plugged on to a power cord (France), there's a softly blinking red light on the left of the top front speaker.
When plugged to a computer, the same soft red light is flashing. (I therefore imagine it indicates charging)
What I have tried :
Holding the power button
Unplugged, for 2, 3, 5, 10, 20, 30 seconds, to no avail
Plugged, and it vibrates shortly after about 6-8 seconds or 2-3 seconds (am I turning it on and off/long press to get the power menu?)
Connecting it to a computer (Windows 7 and Arch linux):
On Arch, there's nothing. No disk/drive of any kind is detected (/dev stays unchanged...)
On windows, the first time I connected I got the pop up indicating a driver install for an "unknown device", and the install failed. Browsing this forum I learned about PC companion, which I installed. Windows then successfully installed a driver for "usb device". Windows explorer does not detect the phone as a media device of any kind and PC companion refuses to connect to the phone : when manually prompted to connect, it recognizes something is plugged, but tells me it "fails(ed) to connect to the pone/tablet. Please refer to the guide", guide of course which is worthless. (No logs or smthng? geez, windows!)
What I have not tried :
I have *no* idea on how to remove cover to access battery and so on. As the back is perfectly smooth I am afraid to break smthng if I try with a knife blade or so...
Sacrificing chicken and/or blond virgins to the blood overlords while chanting black magic
My guess is the screen is dead ( as it shows no sign whatsoever) but the phone seems to be partly working. 1337 guyz out there, ideas, help? (actually anyone is welcome of course :laugh
The main objective is only to recover data, not get it back working (would've sent it for repair otherwise!) If you need more info, I'll be happy to provide it.
G'day to yall!
(As I am currently undergoing heavy fire from my engineering study teachers, I will check this post about once a week. sorry for the answering delays...)
Click to expand...
Click to collapse
Not realla an idea, but maybe a little help. In the attachement you find a pdf. (Working Instructions for Assembly and Disassembly the phone). Hope, it helps a little. Good luck :fingers-crossed:
Thanks mate! Will look at it this weekend
One of the first thing you should try is to access fastboot. For this you have to hold volume down button while plugging it in to the computer. If the phone is a Xperia SP your led should be blue then (I'm not sure you have this model regarding the description you gave). If this works then we make a small step !
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Phenitei said:
Right I'll try that. Looking at the pdf given by reinipic, it seems it is one, as the phone corresponds to the photo of the Sp C5303/5302/5306/M35h.
Oops my bad!! You are, good sir, perfectly right, the phone is not an SP, as all Sps seem to have the front Camera as well as three sensors on the left of the top speaker. The model I'm working on only has a camera on the right side. ...
Erm as such I'm quite into the wild as to how to guess what model it is (google image is not really being helpfull...), any tips on that?
attached are front, back, and side photographs of the phone.
I have as well tried to long press the down button while connected to a computer (windows 7). The led changed it's pattern : it blinked shortly red twice,then green! :good: The screen still stays off though (which may confirm my hypothesis that it's dead), and the computer does not react.
As always, thx for the help!
Click to expand...
Click to collapse
:highfive: Bravo man! As pecOra said, you hae done a grat step - the phone is alive! LED blinking red then green, means, that´s ready for flashing a rom with Flashtool! The problem now is to clarify, what Xperia-model it is, after this you can seach in the right thread for a Rom to flash it on the phone with Flashtool
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
[UPDATE] : if, while connected to a computer, the up-volume button is long pressed, then the del becomes a stable and unchanging blue!
Phenitei said:
Cool! This has me ask two questions though :
- wouldn't flashing a ROM erase the data I'm trying to retrieve? As it's not on the sd card (whose slot is on the outside, and empty).
- I'm afraid I'm slow here, but how would flashing a ROM help retrieve the data, as the main obstacle is that the data on the internal sd card is not readable
Click to expand...
Click to collapse
STOP! Flashing a Rom ALWAYS deletes all data on the internal SD. In the current situation you can make again a functional phone. To readout the data from the SD is an other thing. For this experiment I am to less competent. Maybe another member is smarter than I am, sorry.
No probs! That's also my experience with my phone (wiping I mean), and is why I asked why I would want to flash a ROM. No worries, we all have different skills[emoji41] . I'll help you the day you mess up a samsung [emoji6]
Thx for trying!
Phenitei said:
No probs! That's also my experience with my phone, and is why I asked why I would want to do that. No worries, we all have different skills. I'll help you the day you mess up a samsung
Thx for trying!
Click to expand...
Click to collapse
:good: hope, pecOra can help you!!! He is a great man.
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
pec0ra said:
Ok that's good news, it means your phone isn't totally dead. The next step is to look if there is any way to access the data partition or sd from fastboot mode (when the blue led was on, it's generally used to access kernel/recovery partitions from the computer.) I'll make some search today and look in fastboot manual to see if I find something. You should try to find something too.
If there is no way with fastboot we'll try with adb but unless your friend was some kind of developer he probably kept it deactivated.
The phone looks more like a Xperia Z or a Xperia Z1 I think. Our xsp has a big led at the bottom.
Edit :
I found another thread with a similar problem. The solution is to flash a recovery and access adb from the recovery.
forum.xda-developers.com/galaxy-nexus/help/to-recover-data-fastboot-t1871698
The problem is that I'm pretty sure the phone must have an unlocked bootloader.
Is the phone rooted?
Click to expand...
Click to collapse
:good: +1
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Phenitei said:
Right. I'll look into fastboot and confirm the phone model this we, and will look at the thread you dug out tomorrow (gitta get some maths and physics done first ). (Great job finding the thread by the way! I hadn't seen that one)
I'm certain the phone os neither rooted nor was usb debugging enabled, as my friend is absolutely not into tech.
As always, your help is much appreciated, thank you.
Click to expand...
Click to collapse
Mmmh this is not good. The solutions use adb so you must have it enabled but that's not really a problem because if your phone boots until adb mode, it will probably boot until usb storage mode too. So if you don't have usb storage when booting, you probably won't have adb mode either.
The second solution was to use adb (or usb storage) in another environment which is much less complex and easier to flash without losing any data : the recovery. The problem is that you can only flash a recovery with fastboot when your bootloader is unlocked. The other ways to flash it use adb and as we've seen we don't have it.
I'm pretty sure you can't access any partition from fastboot if your bootloader is unlocked because otherwise it would open easy exploits to gain root without losing your warranty unlocking your BL.
Now what you still have available is flashtool. This is the (copy of the, with more possibilities) official way to flash firmwares. You use it from your computer when your phone is in the mode with the green light. The problem is that with this you can only flash official firmwares. They might still repair your phone depending on the problem but you must be careful not to erase the data. If you want to try this I can help you in the procedure (you can even pm me en français if you want)
By the way, are you trying to access data like app data/ contacts / messages or data of the external storage?
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
---------- Post added at 01:07 PM ---------- Previous post was at 12:40 PM ----------
reinipic said:
I personally agree the solution of pec0ra to flash a stockrom with the flashtool, without erasing date. It should be the only successful procedure. Good luck man!
Click to expand...
Click to collapse
Edit:
btw. when you are opening the flashtool and connect the phone with the pc, than you can see in the flashtool, which Xperia Model it really is, then you can search for the right stockrom and ... buuuuuum :laugh:
Right thanks a lot! I'll take the time to document my self a bit on all that and then I'll be happy to accept your proposal. Merci!
put it in a box of rice 4 days without touching.... you will see the results.
Kmiloxdxd, thanks for your proposal, I'll try! But as I said in the question, I got the phone at least a week after it fell into water, maybe more (up to 3 max) As such, I'm quite sure it's too late for that kind if trick... (which did save a few phones and watches of my own ^^)
You have 2 options..the first one is to reflash stock rom via flashtool without wiping data and the other one which requires a recovery, you can move this zip (http://forum.xda-developers.com/showthread.php?t=1646108) to your sd and move files from internal to external memory.
Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...
Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.
used this thread to try and return to stock:
https://forum.xda-developers.com/moto-e4-plus/how-to/moto-e4-qualcomm-owens-completely-to-t3743441
My **** turned off, now it wont turn on period. Cant go into any kind of download mode NOTHING. I have no warranty, I got the phone off the street. Tried to flash a custom rom did it wrong then tried to return it to stock because I didnt make a backup. I'm ready to throw it at a wall.
It WAS a boost moto e4 plus owens xt1776
If it won't turn on, there's not much you can do. The battery is technically removable, so you COULD try removing it and putting it back in, but I doubt it will help. You might want to see if Motorola will repair it. It's a longshot, but they might help you. I wouldn't tell them you bought it off the street. Just say you don't have a receipt.
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
ATTACK said:
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
Click to expand...
Click to collapse
You're right, I forgot about that one..
ATTACK said:
I know on older Motorola's, if you plugged them in and let it charge for a few hours, they would turn back on.
But I don't know what you did. It would help if you provided more info on what you did, so we could gain a better perspective.
Click to expand...
Click to collapse
If he temper any of the device partition than probably it will be a soft brick and should be resolved by the service center guy like i did this before three times with my Moto E4 and it won't turn on. No fastboot mode, no recovery, Just the notification light when connecting to a power source and nothing else. I also got the new IMEI number.
TheHitMan said:
If he temper any of the device partition than probably it will be a soft brick and should be resolved by the service center guy like i did this before three times with my Moto E4 and it won't turn on. No fastboot mode, no recovery, Just the notification light when connecting to a power source and nothing else.
Click to expand...
Click to collapse
We don't know if he messed with his partitons, though. Without further details as to what he did, all we're doing is guessing.
Sorry about my delay had some stuff go down. Uhm, I followed that thread, ran the commands listed, used a sprint factory instead of a boost, from what i read in that thread, it should have worked. But now I dont even get a notification light when i charge.
I'm having the same problem as him and I feel like I'm making some progress, but I still can't fix it. Here's my posts on what I found from that thread. They are probably better suited here anyway. https://forum.xda-developers.com/showpost.php?p=76459007&postcount=21
doodalydoo said:
I'm having the same problem as him and I feel like I'm making some progress, but I still can't fix it. Here's my posts on what I found from that thread. They are probably better suited here anyway. https://forum.xda-developers.com/showpost.php?p=76459007&postcount=21
Click to expand...
Click to collapse
Don't forget that the OEM files are labeled differently for Boost Mobile users, messing that labeling up during fastboot will cause it not to boot as well..
bcrichster said:
Don't forget that the OEM files are labeled differently for Boost Mobile users, messing that labeling up during fastboot will cause it not to boot as well..
Click to expand...
Click to collapse
I have the carrier unlocked version. I think the way I bricked my phone is that I OTA updated my phone and then tried to revert back to stock. I've seen a video on youtube of somebody who did the exact same thing and was able to unbrick his phone. I think the main problem right now is I can't find the right firmware files to use in QFIL. The stock firmware zips don't have the right files that QFIL needs