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
Related
Getting an orange light (not flashing and its been on since yesterday). Wont turn on in any ways, by presing volume up and power for several seconds(i tried for minutes) or pressing down and power. Not even connecting it by USB, i tried many USBs and a laptop+ computer. This phone is just about 2 weeks old and lightly used, because I'm using my old phone.
This phone as never been dropped, hit, left without charge, or watered. So I am really surprised of the quality. I bought this phone in the US and moved to Costa Rica so i cant just send it back. This really annoy me, to think that i wasted 539.00 dollars in this "Quality" product that lasted 2 weeks.
I read some solutions like leaving it charging for a long period of time. Or if that doesnt work, drain the battery. But i think the later is impossible since the battery is fully charge, it would take weeks for the battery to run out (how do i know it is fully charged?, my nokia charger gets hot while charging and it is totally cool charging the xperia), and flashing, but my computer does not recognize the phone even by pressing volume done for several minutes and power.
Please any help? thanks!.
Xelestial01 said:
Getting an orange light (not flashing and its been on since yesterday). Wont turn on in any ways, by presing volume up and power for several seconds(i tried for minutes) or pressing down and power. Not even connecting it by USB, i tried many USBs and a laptop+ computer. This phone is just about 2 weeks old and lightly used, because I'm using my old phone.
This phone as never been dropped, hit, left without charge, or watered. So I am really surprised of the quality. I bought this phone in the US and moved to Costa Rica so i cant just send it back. This really annoy me, to think that i wasted 539.00 dollars in this "Quality" product that lasted 2 weeks.
I read some solutions like leaving it charging for a long period of time. Or if that doesnt work, drain the battery. But i think the later is impossible since the battery is fully charge, it would take weeks for the battery to run out (how do i know it is fully charged?, my nokia charger gets hot while charging and it is totally cool charging the xperia), and flashing, but my computer does not recognize the phone even by pressing volume done for several minutes and power.
Please any help? thanks!.
Click to expand...
Click to collapse
Have you flashed anything to the phone? I cant beleive it just did this without you doing something to the phone. Have you rooted? Have you tried to unlock the bootloader?
Please install flashtool and post the log from flashtool when you try to connect the phone normally, in flashmode and in fastboot mode.
PS,
Now you have asked your QUESTION and I have tried to ANSWER it, can you guess which section you should have posted in?
General, Question & Answer, development or themes and apps?
gregbradley said:
Have you flashed anything to the phone? I cant beleive it just did this without you doing something to the phone. Have you rooted? Have you tried to unlock the bootloader?
Please install flashtool and post the log from flashtool when you try to connect the phone normally, in flashmode and in fastboot mode.
PS,
Now you have asked your QUESTION and I have tried to ANSWER it, can you guess which section you should have posted in?
General, Question & Answer, development or themes and apps?
Click to expand...
Click to collapse
I swear i didnt touch the phone i barely installed any apps like facebook, waze, and prolly one or 2 more. The reason is because i was waiting for my sim cutter and for the mean time i was using my old c6-01 nokia. I tried flashboot and it keeps telling me device not detected. i tried pressing volume down and power, etc. To be honest i barely used this phone. Just to check my FB or waze (like a google map). I moved to Costa Rica so i cant send it back.
Thread moved. Please post all your questions here in Q&A in future.
Thanks
AvRS
Xelestial01 said:
I swear i didnt touch the phone i barely installed any apps like facebook, waze, and prolly one or 2 more. The reason is because i was waiting for my sim cutter and for the mean time i was using my old c6-01 nokia. I tried flashboot and it keeps telling me device not detected. i tried pressing volume down and power, etc. To be honest i barely used this phone. Just to check my FB or waze (like a google map). I moved to Costa Rica so i cant send it back.
Click to expand...
Click to collapse
ok, if you have not unlocked your bootloader you can not enter fastboot mode.
Download PCcompanion and follow the instructions to update software, then click on repair. It should work.
gregbradley said:
ok, if you have not unlocked your bootloader you can not enter fastboot mode.
Download PCcompanion and follow the instructions to update software, then click on repair. It should work.
Click to expand...
Click to collapse
Bootloader? havent tried that. tried the PCcompanion but its not detecting my phone, even pressing volume down+power. Ty for the reply!
Xelestial01 said:
Bootloader? havent tried that. tried the PCcompanion but its not detecting my phone, even pressing volume down+power. Ty for the reply!
Click to expand...
Click to collapse
Please dont worry about it. Just go through the process to update your software without actually attaching your phone. Then you will get an option to repair.
Then attach the phone in flashmode (Press volume doen whilst attaching the usb cable to the phone) and it should work.
If not, please download flashtool Find a link in the first post of the Devlopment section and also download a stock ftf for your phone from the all in one thread (First thread in the Q&A section)
Then drag and drop the ftf file you downloaded into the open window of flashtool and attach the phone in flashmode. If that does not work then please post what the log of flashtool says.
EDIT
Also, no need to ever say thank you to anyonr here, if you feel the need to offer your thanks just hit the thanks button, thats what it is for
AvRS said:
Thread moved. Please post all your questions here in Q&A in future.
Thanks
AvRS
Click to expand...
Click to collapse
Sorry for posting in the wrong section!.
gregbradley said:
Please dont worry about it. Just go through the process to update your software without actually attaching your phone. Then you will get an option to repair.
Then attach the phone in flashmode (Press volume doen whilst attaching the usb cable to the phone) and it should work.
If not, please download flashtool Find a link in the first post of the Devlopment section and also download a stock ftf for your phone from the all in one thread (First thread in the Q&A section)
Then drag and drop the ftf file you downloaded into the open window of flashtool and attach the phone in flashmode. If that does not work then please post what the log of flashtool says.
EDIT
Also, no need to ever say thank you to anyonr here, if you feel the need to offer your thanks just hit the thanks button, thats what it is for
Click to expand...
Click to collapse
If this helps, the phone is an unlocked version i bought from Amazon, I was using micro Sim card from a local company and it was working fine. I will try the tips you recommended me later when I am out of work.
Disconnect the battery, u have to take the back off. 1 screw behind the sim cover.
Sent from my LT30p using xda app-developers app
erhan12 said:
Disconnect the battery, u have to take the back off. 1 screw behind the sim cover.
Sent from my LT30p using xda app-developers app
Click to expand...
Click to collapse
I took the screw out... But how do u remove the back cover again?.
Theres a thread somewhere which shows a disassembled xt, search.
Sent from my LT30p using xda app-developers app
Hard brick LT30p ?
Hello to all... What could hapen to my phone, that it wont turn on? Hard brick? Everything was fine, I just searching on the webs ho to sim-Unlok, found sites, gived IMEI and they tell the price, and just searched some other to get the price (where is cheeper). Some days ago I tryed to flash stock rom O2 with flash tools from here http://forum.xda-developers.com/showthread.php?t=1910216, everything goes right. Version was 4.0.4 and I do not update (when I connect to Wi-Fi it gives me update) because I thought wen I sim-ulock then I do this. After flashing stock rom I noticed, that my sony wont start without restart (press power + volume up + volum down) (maby goes in to deep sleep or something). I thought never mind, it maybe softwere problems and when I debrand it will goes everything ok, because I rewrite software and add my sim when sim-Unlock I do. And when I decided to debrand, it is to day, I see, that I can't turn on my phone. PC do not detect and no sign at all. Trayed to hold all butons and so on, nothing... What hapens? Yesturday I was using it without SIM (because it is still simlocked) to search on the internet, google and everything was OK, power left about 60% when shutdown. So any ideas how to start the phone? The phone was not rooted. Maby some how something block my phone with IMEI? Because I write it in some forums asking for sim-unlock, so just don't know what to do... Any ideas or suggestions?
unrealliving said:
Hello to all... What could hapen to my phone, that it wont turn on? Hard brick? Everything was fine, I just searching on the webs ho to sim-Unlok, found sites, gived IMEI and they tell the price, and just searched some other to get the price (where is cheeper). Some days ago I tryed to flash stock rom O2 with flash tools from here http://forum.xda-developers.com/showthread.php?t=1910216, everything goes right. Version was 4.0.4 and I do not update (when I connect to Wi-Fi it gives me update) because I thought wen I sim-ulock then I do this. After flashing stock rom I noticed, that my sony wont start without restart (press power + volume up + volum down) (maby goes in to deep sleep or something). I thought never mind, it maybe softwere problems and when I debrand it will goes everything ok, because I rewrite software and add my sim when sim-Unlock I do. And when I decided to debrand, it is to day, I see, that I can't turn on my phone. PC do not detect and no sign at all. Trayed to hold all butons and so on, nothing... What hapens? Yesturday I was using it without SIM (because it is still simlocked) to search on the internet, google and everything was OK, power left about 60% when shutdown. So any ideas how to start the phone? The phone was not rooted. Maby some how something block my phone with IMEI? Because I write it in some forums asking for sim-unlock, so just don't know what to do... Any ideas or suggestions?
Click to expand...
Click to collapse
I disassemble my phone, removed battery conetctors and added to the same place and my phone booted without a paroblme. Hmm? Is it sony's problems? Maby exists diferent way how to do that when phone just do not boot? Because if it hapens in the future, it's not so easy to remove back.
Who is trying to remove the back I can say, that the back is from soft (elastik) material, so do not afraid to give some preasure. And offcorse there are only one screw near sim card. I done it slowly from corner to corner to remove.
My simple guide where is back holders https://www.dropbox.com/s/8x2m0plk4c0cibn/LT30p reassemble-1.jpg
Xperia T dead
Hi, I have LT30p( Xperia T ) and it's dead right now.
I tried everything but it's not turning on.
No fastboot, no flashmode just the red light blinks twice when i hold the power button. When it died it was 71% Charged. It hanged and i went to CWM recovery(did nothing) when i chose reboot system, it didn't.
And it was 2 days plugged into wall charger.
and flashtool doesn't recognize it( I Installed The drivers twice )
Unlocked bootloader,CM 10.2( 4.3 )
Can You Help ME PLZ?
Thanks for Helping.
I hope someone can help me here, I'm posting with the belief that this may be a simple enough problem (With the hope).
I tried to install a Custom Recovery on my Galaxy S using this tutorial - wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd
I managed to get to step 6, and a blue bar appeared, but then i could not do step 7.
Now i cannot boot into recovery mode, nor will the phone boot past the Samsung Galaxy S logo.
I can still get into download mode, but Odin does not detect the phone.
. I have changed cable and tried different versions of Odin..
When i turn on the phone normally it shows the Samsung Galaxy S logo, blinks, and then reboots and does the same.
When i try to enter recovery, i get the same, unless i connect it to the PC. I then get an 8 pointed star, like the loading flash circle thing - the same as a flash video loading except it does not move.
I have also removed the battery and tried to enter recovery and download mode while inserting the battery.
I have removed the SIM and battery for a few minutes.
when i try to start Zadig, with the phone connected in Download mode, i get "Gadget Serial" as the device connected. I used to get "Samsung USB Composite Device"
I have tried many different things and read over the recommended threads on this forum. I think i need a bit more pointing in the right direction.
I really hope somebody can help me. I am very worried that i may have bricked it.
Thank you.
Try this:
This feature is great for people who
a) Have a bad KIES flash
b) Stuff up their phone somehow
c) Accidentally flash something dodgy via ODIN
d) Some other random occurence
To test this feature you just need to start with your phone turned off... Best way to be sure is to remove the battery.
Then
1. Put battery back in
2. Press and hold Volume Up + Home Key
3. Continue holding those buttons and then press and hold power button.
4. When you see the logo pop up release power button ONLY
5. Keep holding two buttons from step 2 until you enter recovery mode.
I hope this helps?
Also have you tried everything on this thread:
http://forum.xda-developers.com/showthread.php?t=1134975
akash6969 said:
Try this:
This feature is great for people who
a) Have a bad KIES flash
b) Stuff up their phone somehow
c) Accidentally flash something dodgy via ODIN
d) Some other random occurence
To test this feature you just need to start with your phone turned off... Best way to be sure is to remove the battery.
Then
1. Put battery back in
2. Press and hold Volume Up + Home Key
3. Continue holding those buttons and then press and hold power button.
4. When you see the logo pop up release power button ONLY
5. Keep holding two buttons from step 2 until you enter recovery mode.
I hope this helps?
Also have you tried everything on this thread:
http://forum.xda-developers.com/showthread.php?t=1134975
Click to expand...
Click to collapse
I hadn't seen that thread, but i have gone over tons of them Thanks for reply.
I eventually got Odin to detect it and I tried this - http://forum.xda-developers.com/showthread.php?t=1544487
It came up red and said failed.
I closed odin and disconnected the phone. Now i can't even turn it on.. Nothing. I am hoping the battery died, and it's a coincidence..
No response at all to any buttons... I haven't done anything else.
If i can get it to power up again, i'll try those tips.
Tomato_Jam said:
I hadn't seen that thread, but i have gone over tons of them Thanks for reply.
I eventually got Odin to detect it and I tried this - http://forum.xda-developers.com/showthread.php?t=1544487
It came up red and said failed.
I closed odin and disconnected the phone. Now i can't even turn it on.. Nothing. I am hoping the battery died, and it's a coincidence..
No response at all to any buttons... I haven't done anything else.
If i can get it to power up again, i'll try those tips.
Click to expand...
Click to collapse
Ok, Don't worry, Charge your phone battery to 100%, leave over night. ( keep charger connected to your phone overnight)
Best to have a fully charged battery in these situations!
Keep calm, and read and prepare what you want to do next.. Don't try everything in a frantic effort to get your phone started again.
I know it's difficult, but there are lots of threads on how to rectify most problems.
I wish you Good luck!!
sorry to ask some stupid question, but can u make sure what versiom ur fone is?
is it i9000?, or i9001 or i9003? or korean anycall? as far as i know, flashing i9000 ROM to i9003 will hardbrick da device.
Sent from my GT-I9000 using xda premium
akash6969 said:
Ok, Don't worry, Charge your phone battery to 100%, leave over night. ( keep charger connected to your phone overnight)
Best to have a fully charged battery in these situations!
Keep calm, and read and prepare what you want to do next.. Don't try everything in a frantic effort to get your phone started again.
I know it's difficult, but there are lots of threads on how to rectify most problems.
I wish you Good luck!!
Click to expand...
Click to collapse
Thanks.
This is a disaster. I tried to power it on to any mode there before i saw your post.
I needed to update the phone, because an app i needed for studying was only available on Android 4+.
Now no phone..
I saw a few threads, i hope after i leave it overnight i'll be able to power it.
If not, probably a JIG?
I don't fancy making one, but if i have to, i guess i'll give it a try. I don't think i could wait a week or more for a premade one to be delivered.
Anyway, for now, i'll keep my fingers crossed.
Thanks for help/tips and reply.
I'll post back tomorrow, hopefully with some better news.
Tomato_Jam said:
Thanks.
This is a disaster. I tried to power it on to any mode there before i saw your post.
I needed to update the phone, because an app i needed for studying was only available on Android 4+.
Now no phone..
I saw a few threads, i hope after i leave it overnight i'll be able to power it.
If not, probably a JIG?
I don't fancy making one, but if i have to, i guess i'll give it a try. I don't think i could wait a week or more for a premade one to be delivered.
Anyway, for now, i'll keep my fingers crossed.
Thanks for help/tips and reply.
I'll post back tomorrow, hopefully with some better news.
Click to expand...
Click to collapse
Sorry to say, most likely you will need a USB JIg to fix the problem you have. :/
If you linked the correct page when you said you tried to do this- and if I opened the correct page, that takes you to an SII section. Those are SII firmwares, not for the S.
So as compacity said, please clarify what device you have... Whether its an I9000 (galaxysmtd is for the I9000) or an I9100 (the firmware page you linked). If you do have an I9000, then your brick comes from flashing a different device's rom onto the S, which would give this error in Odin beause its incompatible.
In this case, you'd probably need a USB Jig to come out of it.
Try what the others said and hopefully you'll be at least able to enter Download mode before resorting to a jig, but considering your situation, I have to say realistically a jig is your best bet :/
Sent from my GT-P7510 using Tapatalk HD
You need a usb jig. It will get you into download mode. Now you need to flash cf root, which will come with cwm recovery. Recovery mode should work now. If you get computer!phone, then re-flash cf root. Now you should be able to flash CyanogenMod via cwm recovery. Thank if I helped!
Sent from my GT-I9000 using cm10.1
Soryuu said:
Sorry to say, most likely you will need a USB JIg to fix the problem you have. :/
If you linked the correct page when you said you tried to do this- and if I opened the correct page, that takes you to an SII section. Those are SII firmwares, not for the S.
So as compacity said, please clarify what device you have... Whether its an I9000 (galaxysmtd is for the I9000) or an I9100 (the firmware page you linked). If you do have an I9000, then your brick comes from flashing a different device's rom onto the S, which would give this error in Odin beause its incompatible.
In this case, you'd probably need a USB Jig to come out of it.
Try what the others said and hopefully you'll be at least able to enter Download mode before resorting to a jig, but considering your situation, I have to say realistically a jig is your best bet :/
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
huskyT said:
You need a usb jig. It will get you into download mode. Now you need to flash cf root, which will come with cwm recovery. Recovery mode should work now. If you get computer!phone, then re-flash cf root. Now you should be able to flash CyanogenMod via cwm recovery. Thank if I helped!
Sent from my GT-I9000 using cm10.1
Click to expand...
Click to collapse
Both helped a lot, thanks.
I had to end up bringing the phone to a repair shop
Something i am not inclined to do if i can avoid it. Especially if i caused it, i would hope i could undo it. But because i need a jig, and i wouldn't have time to get one or make one before Monday, i had to bring it to someone else.
I am buying the materials for a jig, and maybe going to buy one also, for future.
@Soryuu - Yep, i linked to the page, so i must have flashed the wrong firmware.
I'm angry with myself because i read everything else carefully. I had been reading all day. I guess i was just tired and thought I had got to the final hurdle. I was careless.
@huskyT - Thanks, will know that for future reference. I have two old Android phones somewhere. One is a Galaxy Europa, and one is an LG (not sure what model). Both are borked in some way, but i could probably use them for practice. I think the Galaxy Europa is flashed badly. Not by me. (Thankfully).
Tomato_Jam said:
Both helped a lot, thanks.
I had to end up bringing the phone to a repair shop
Something i am not inclined to do if i can avoid it. Especially if i caused it, i would hope i could undo it. But because i need a jig, and i wouldn't have time to get one or make one before Monday, i had to bring it to someone else.
I am buying the materials for a jig, and maybe going to buy one also, for future.
@Soryuu - Yep, i linked to the page, so i must have flashed the wrong firmware.
I'm angry with myself because i read everything else carefully. I had been reading all day. I guess i was just tired and thought I had got to the final hurdle. I was careless.
@huskyT - Thanks, will know that for future reference. I have two old Android phones somewhere. One is a Galaxy Europa, and one is an LG (not sure what model). Both are borked in some way, but i could probably use them for practice. I think the Galaxy Europa is flashed badly. Not by me. (Thankfully).
Click to expand...
Click to collapse
Don't stress mate, we all have bad days, we all make mistakes
Sent from my GT-P7510 using Tapatalk HD
Well....
I would have been quicker if i had ordered a jig and done it myself.. (Worth mentioning, i had told guy in phone shop what happened, and about the required "jig")
I collected my phone from the shop today, after a week, and i was told "Your phone is f*****d". To which i replied, "what? are you sure, i mean, i have only flashed it with SGS2 firmware, i'm under the impression it is very hard to break/brick, if i have a jig."
He told me, "Nope, it's beyond repair, it won't work. If you want, i can use the screen and other parts, i'll buy it off you for €40"
No thanks.
So now i am on the lookout for a premade jig. Does anybody know where i can buy one?
I meant to last week, but things happened, and without a phone i was running around a bit...
I'm going to check ebay, but if somebody could recommend somebody reliable, i'd prefer that. Thanks.
I bought it from ebay, no problem...but just saw a couple of minutes ago that also on amazon germany these jigs are offered now/in the meantime....
rodman01 said:
I bought it from ebay, no problem...but just saw a couple of minutes ago that also on amazon germany these jigs are offered now/in the meantime....
Click to expand...
Click to collapse
Thanks.
I bought a jig, and it arrived today. Have phone in charger.
Do i just plug the jig in?
Or do i also do the three button press?
The screen is completely black, and nothing appears on it.
only plug the jig in, thats all... phone will start in download mode of its own. :fingers-crossed: :fingers-crossed:
rodman01 said:
only plug the jig in, thats all... phone will start in download mode of its own. :fingers-crossed: :fingers-crossed:
Click to expand...
Click to collapse
Thanks, going to leave it charging for a little longer, and try it.
If it doesn't work, would a motherboard for the Samsung Galaxy S be easy to replace? I have found one unlocked for €25.
EDIT
Found a tear down video here - http://www.youtube.com/watch?v=vxPWsLd05F4
yes thats not so difficult...only thing a bit complicated is to open the back or middle cover...but there are a few movies on youtupe where you can see how it can be opened and dismounted....btw for the first try with the jig battery has not to be that full...only if it starts in download mode and you can flash it via odin I would recommend to charge it complete.
rodman01 said:
yes thats not so difficult...only thing a bit complicated is to open the back or middle cover...but there are a few movies on youtupe where you can see how it can be opened and dismounted....btw for the first try with the jig battery has not to be that full...only if it starts in download mode and you can flash it via odin I would recommend to charge it complete.
Click to expand...
Click to collapse
Thanks again.
I am after removing it from the charger, and inserted the jig. It's in about 30 seconds now, and nothing is happening..
that sounds not good...ususaly it takes only a few seconds or perhaps a minute till it starts to download mode....sorry for no better news....
rodman01 said:
that sounds not good...ususaly it takes only a few seconds or perhaps a minute till it starts to download mode....sorry for no better news....
Click to expand...
Click to collapse
What seems to have happened, is i tried to flash it with SGS2 rom. So is it unbrickable?
I am not sure but I think that minimum the bootloader is damaged...there is one more possibility: to repair it via jtag...but for this you have to find someone, who ones one and can repair it....some of the guys don't take much money for such a repair, but with transport costs ets...perhaps it would be cheaper and faster if you take the new mainboard you mentioned.
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.
Hi guys, been a bit out of the loop (hospital) but bought an Alpha around sep last year...within 2 months i used a official Maze update (OTA) and it then no longer charges...got onto them via facebook (as there were no official threads for this phone back then) and they sent me this to reflash it...
http://www.mazemobile.com/download-center
The ROM used to be there, but they have the ****ing cheek to say "people tried to flash and blamed MAZE" now it was MAZE's update in the first place that buggered my phone.:silly:..i still have the original ROM...
https://drive.google.com/drive/folders/0B8XLZxEJR8albndMcXJhWGtlVDQ
^not sure if that works for you, but basically it was..
:A really crap tutorial
:Maze Alpha flash tool.zip
:Maze_Alpha_V05_20170816
I've followed everything by the letter to no avail???
Now MAZE are bloody useless, can i count on one of you clever chaps to help me out?
P.s it's the 4 gig model.
Many thanks lads...
Any joy?
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
seedaripper said:
Is there anybody on here that had the same problem? You guys are usually really helpful, as i'm getting no rsponse from MAZE i thought i'd try where the true tech heads reside (i've received help before on my Xioami phones and smartwatches before) or is it that not many people have bothered with this phone? please help a guy out...much appreciated.
Click to expand...
Click to collapse
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Cheers...someone lives!
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
lukesan said:
Well the thing is that you need to provide a bit more info. 'I've followed everything by the letter to no avail???' But you are not telling what works or not or what step you are stuck in the manual.
A lot of things come to my mind.
- is it still booting
- did you try another cable - charger
- ...
If it still boots and works a bit can you connect it to a pc and access for example the internal memory etc?
Some more info would be of help to get response... although I find the Maze Alpha part of the forum a lot of read and very little help (a bit of ranting may wake up people)
Click to expand...
Click to collapse
seedaripper said:
Thanks for responding lukesan (much appreciated)
I'm using the original charger, it was working fine until i got the OTA so i doubt that's the problem.
No it doesn't boot (there is just enough charge to get to recovery mode,fastboot mode,normal boot)
I followed the manual/flash/tool etc (does the google drive doc show up for you as posted above?) everything seemed to go fine...but the problem still persists, it just wont charge?
Maybe i need a new ROM (or it could be the tool MAZE sent me) they are ****ing useless and i've started a bit of a social media campaign against them
(at first they were keeping in touch, but now they just ignore me completely on facebook) it pisses me off no end:crying:
P.s it does connect to my PC (sometimes), where should i dig around?
Click to expand...
Click to collapse
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
Charger you can easily check if you just connect it to another charger or a pc usb port. A PC usb port will only deliver (mostly) max 400mA to 500mA .. meaning it will charge, if it still does, extremely slow. So I would keep it connected to a pc all day long or night before trying to switch it on. Trying to switch it on during charging and batt at low level will probably not work. You could try to power on after 2 or 3 hours or so and if it powers on then I would power it off again to get at least some juice in it to play around.
Cable, I would go fetch another one, they will come in handy in the future too. If it doesn't fit properly because the port is to deep in the Alpha then just take a knife and carefully cut a very small piece of the plastic, just 1mm is enough. I've done this on the 2 extra cables I have here and it works perfectly and I don't even see it aesthetically so no harm done on mine.
Now if that still doesn't work we can try the next step. But be very careful to know that that will delete all data, pictures, etc off of the phone. Because of all my toying with this phone I stuck an sd-card in it and doing a backup before I play with it again.
The manual states that you have to press the volume up button.. Well you can already test that without hurting anything as long you don't press anything on the flashtool. So only volume up and then insert the usb cable to a pc. Now the mistake I made in the beginning was to also push the power button.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
Btw I know about their attitude. Well, as a Chinese company they must understand that by this attitude they will not going to sell any products anymore. I only bought mine because it was a special deal and I wanted to test an MTK chipset. They never replied to me why there is no real fast charge on it etc.
I also very very highly recommend you to invest, well for the price of a sandwich, to buy a usb charging doctor which will allow you to see the voltage and current. You don't need to be a doctor to us it and at least you see something instead of having to guess. Also while you are at it buy good quality chargers and a couple of cables. They will always come in handy and take some of the guesswork away if needed.
Top lad.
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
lukesan said:
Just checked, and yes it is the correct manual. But lets say that even me, a veteran (with no patience), had issues with it. It is 100% correct but ... well see later on where you get.
Ok, first couple of things come up in my mind. Could still be the cable, the charger or even the the charging port that is broken. Been in the electronics business since the late 80's and these things can go wrong or broken any minute even thinking that a firmware update caused it.
So on the pc open up your device manager. If you do volume up (not in any of the other modes like fastboot etc, so from a standpoint that the phone is completely off) hold it for 2 or 3 sec and plug it into the PC. Now you should hear the typical usb connection sound and see something happening like an extra device in the manager. Probably you do not have the correct drivers installed for starters. Look for mtk drivers for your OS. Be careful, a lot of crap and virus links out there.
Now another issue that I fell for the first time is that you have to connect it twice like that to the pc to actually flash. First time ... press the 'scan' and let it do it (think the top field will become green) and then disconnect the phone and do the same volume up and connect and then it will allow you to flash.
But first check what is happening before we have to flash it.
.
Click to expand...
Click to collapse
seedaripper said:
Again many thanks luksan (hefty bit of typing you did there mate )
I very much doubt it's the charger (i was extremely careful everytime with insertion) or port for that matter...this is the only USB-C i have (everything else is old school micro USB) and i resent forking out more money (the original trader Cafago said to send it back tracked at my own cost...£60!!!)
i'd like to try and fix the bastard and then sell it, never to return
Again, all these probs literally appeared after i did the OTA (i doubt it was coincidence)
i do like your advice on the re-doing the flash twice, so i may give that a go...bloody nora, what a pain in the arse!
Thanks for being a voice in the void pal...
See
Click to expand...
Click to collapse
Well don't flash it twice. You have to put it in that mode twice to start it to complete the procedure. I do not believe in the wipe it 3 times to be sure, turn around and jump to make it better or faster. Loads of voodoo that is not scientifically proven around. It's all about a 0 and a 1, there is nothing in between that.
But .£60 to send that charger, LOL.
A month ago I bought an Aukey charger that included a USB-C cable for like .£12 including shipping to Belgium. (well just followed the rain and snow and landed here)
Let us know what happens next.
Any update on what you did?
GAH!
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
seedaripper said:
Yes, i've just tried everything again...nothing seems to work? when i actually start the tool i get a number of errors (including scatter?) then the tool boots, i then go through the broken english bollocks of the 'guide' again, do everything and it still doesn't work?? listen man, could you do me a massive favour...just outline the steps (bullet point wise) on what to do? no chatting about the chinese or voodoo
just nice clear as day steps, because as it stands i'm going to have to pay £70 just to send this piece of **** back (and probably wont get a full refund)
If you could do that (and i mean laymans terms here) i'd be forever grateful...
Cheers bud.:good::good:
Click to expand...
Click to collapse
But what about the drivers etc.... What shows up?
ROM?
lukesan said:
Any update on what you did?
Click to expand...
Click to collapse
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
lukesan said:
But what about the drivers etc.... What shows up?
Click to expand...
Click to collapse
seedaripper said:
Nothing shows up...i think the first time i tried to plug it into the PC it ran a scan,(i don't think it found the drivers, as it doesnt show up on my computer :running win 7) from there on in, nothing? it also makes the mandatory PC sound bleep when plugged in, then about a second later i get the discharge bleep? (not sure if this is lack of charge) if i had a frigging phone i'd post screenshots! damned if i do, damned if i don't!
Click to expand...
Click to collapse
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
seedaripper said:
Perhaps it's the ROM? any chance you could give me the latest version? (or a link) i keep getting error in the light green field (FAIL) on the Tool?
I'm not sure if it's the tool or the bloody ROM?
As usual not a sodding dicky bird from MAZE (emails,twitter facebook etc) what a sh!tty company...
Click to expand...
Click to collapse
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
er?
lukesan said:
Well if it hasn't gotten the correct drivers it will never ever be able to flash. It's like trying to use your house keys to start your car.
I see all kinds of stuff happening if you keep the device manager open. Open up the 'ports' (com & lpt) section. Now press the 'volume up' key for a second or 2 and then connect it to a usb port while holding the key.. release it like a second later when it is connected to the port. Now you should see some stuff happening. Just did it on my win10 machine but should be pretty similar on a win7. One of them says first 'mtk usb' and then 'preloader usb vcom' . If these don't show up then look no further for now.
Click to expand...
Click to collapse
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
lukesan said:
His device doesn't charge and his battery is flat so I guess his by the time he can flash the device dies anyway.
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
Can't get my head round multi quote?
dreambo said:
Have you tried my backup here ?
Flash TWRP using fastboot method and then boot into TWRP and do a restore with the backup I provide for Maze Alpha 4/64
Click to expand...
Click to collapse
Yep, when i try to power on i have a split second of the MAZE logo, then back to death...i Can leave it charging and i get the wobble liquid battery graphic, but it never goes above 0%, as explained this only happened after a firmware update (#dreambo)
seedaripper said:
Ok, did that for a split second 'media TEK preloader USB VCOM (android) (COM4)' flashes up, i managed to click on it quickly and got to mediatek properties...then went to update driver (it searched the net and found it) all this time after the original insertion, literally a second after it just disconnects? (and it doesn't show up in my computer) i get this as device status.....
Currently, this hardware device is not connected to the computer. (Code 45)
To fix this problem, reconnect this hardware device to the computer.
I plug it back in, it says normal, then a second later the above message? any ideas?
Click to expand...
Click to collapse
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
lukesan said:
Mmm, if you see the preloader thing then I guess that is ok. ... it is no longer an 'unknown device' which sounds fine to me. Let me quickly test on my Maze for a sec. (will edit this post).
It is normal that it disconnects. My guess is that it tries to setup comms between device and something on the pc where it can talk to. If there is no communication then it just powers down again. The display etc will all stay off since it directly does the comms to the cpu and the ram. Sort of write only state. So it is a very low level form of programming. Can be scary for people because you see nothing happening on the phone during that process.
Ok just tested again.. Can you do step 1 to 5 in the manual without an error? (to be sure I would right-click on the exe and run it as administrator to start that program)
Till that step 5 no connection to the Alpha is needed. In step 5 if you have pressed 'scan' it should say something like resetting comm ports and only the 'stop all' should be clickable.
If we are that far then I guess we are a step further.
Give that a try and then we'll see for the next step.
Click to expand...
Click to collapse
Pics ...hopefully...
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