Related
(Tittle changed from *Phone won't boot with sdcard inserted*)
I woke up this morning and my phone was just dead over night. I thought well the battery just drained but no. First it wouldn't charge, no red led lighting up on the power button. After 15 min. in the wall charger and no sign of charging i hooked it up on my netbook. About five min. went on and then the red led shined and i thought yes and tried booting but just a vibrate once and a black screen.
I was running latest 4.0.A.2.368, rooted, unlocked bl, doomlord's kernel and @thomassafca's samsung theme when this happened.
Tested fastboot mode and flash mode all good there, blue and green light.
Then i re-flashed doomlords kernel and it rebooted to the point of *sony ericsson* on the screeen and went black and then the charging icon and orange led.
Took out the battery and inserted it again and booted up. Again only vibrate once and then black screen.
Then flashed kernel.sin with flashtool, still the vibrate once and black screen.
So i was a bit lost and took out sim and sdcard and flashed 4.0A.2.368 ftf file posted by @thomassafca and it booted fine. Then i turned it off and inserted the sim and booted up. It booted just fine. Then inserted the sdcard and again vibrate once and black screen.
Then formated the sdcard extFat still no boot, tried Fat32 no boot, tried a card from my old nokia wich should be formatted correct since it also run on a linux base (maemo) no boot.
I'm a bit lost on what to do to make my phone boot with sdcard again.
Have been working with no issues at all since i flashed the new firmware/unlocked bl/flashed kernel/rooted.
Any help will or if someone could explain what happened will be great
Regards Dousan...
e: Ok a slight change in this. The phone when turned of won't boot again unless i take out battery and insert again. When booted into the phone i inserted the sdcard and mounted it and now it boots with the sdcard, but still the same issue of having to take out the battery to boot when turned off?
e2: Tried adb reboot and it seems to go in a bootloop. It connects to the pc and disconnects (windows sound plinging connected disconnected) and i can adb devices and a connected device number appears after the first pling and after the second pling there's no device to be found with adb and then it just goes on and on till i disconnect and pull the battery and boot? All this is with a black screen not even *sony ericsson* appears.
e3: Reflashed it with the latest fw and without pulling battery it booted right up and i thought, yes, problem solved. Went through setup and then turned it off and booted the phone and still vibrate once and a black screen. Pulled out battery and botted again and still vibrate and black screen? So pulled it out again and sdcard and it booted up fine. Inserted the sdcard when on and mounted it and it works, but still the boot problem?
After the reflash the vibrate felt different, stronger, and after i pulled the battery it's weaker.
e4:Flashed doomlords kernel again and rooted, still same issue?
e5: Solved problem by flashing doomlords kernel v2 for fw 4.0.A.2.368. After flashing it booted with the kernels new boot txt and then it turned off and the charging icon showed. Then booted into cwm and wiped dalvick cache and battery stats. Then rebooted from cwm and it booted up. To make sure problem was resolved I tried 2 times in a row to reboot with quick boot and it booted without me having to pull the battery Thanks all for your suggestions
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
AndroHero said:
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Cheers mate for the surgestion, but that was a no go, didn't help
Back on 4.0.A2.368/unlocked/doomlord kernel/rooted... With a reboot problem
Regards Dousan...
Could be related to the doomlord kernel?
Sent from my R800
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Deoxlar said:
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Click to expand...
Click to collapse
Not likely as i only OC'ed to 1400 the first feew days i had the kernel and then 1200 and when it happened stock clock.
My incident is isolated and your point is?
@captain67, yes it might be related to the kernel, could be?
Regards Dousan...
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Dousan said:
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Click to expand...
Click to collapse
And it turned out that there was a point to it, problem solved
First post edited (e5
Regards Dousan...
Had the same problem
It was solved by magic though
Sent from my Xperia PLAY R800i using XDA App
And then the problem reappeared and this time i couldn't fix it myself and has just gotten my play back from service today (one and a half week they had it). It turned out to be some hardware problem and i've got a new screen, top cover and some other stuf.
Flashed the latest FW and locked the bootloader before handing it in and just told them what happened. Woke up and turned the device on and it froze and then it turned off with the backlight on. Tried rebooting but just a single vibrate and then a black screen.
They fixed my issue but created another. The volume button is now broken and i have to go back tommorow for a second time. Just booted the phone this evening and wanted to hear some music, but couldn't turn up the volume without pressing a pionty thing on the rocker. Down works fine. Bit annoying that a broken volume button can leave the service place, that should've been seen by the service person in the shop before it was ok'ed.
The screen is nice and crisp and the old one had a backlight issue i just lived with... untill now
Regards Dousan...
So a little update on this:
As i said they broke my volume button while repairing it for the stuff i wrote about above (didn't want to turn on).
It took me a week to go back with my play and in the meentime i descovered that it would randomly turn off during the night and wouldn't turn on unless i pulled the battery and charge it untill the charging symbol showed on the screen. It would then boot and first i thought it was the battery that was drained, but when on the lockscreen it showed that there was plenty of juice on. One time it was 35% and another it was 62% and no way it could've charged that much in 1-2 min.
Another thing i descovered was that when turned off it wouldn't turn on again unless i pulled the battery.
Anyway i went to pick it up yesterday and here i saw that they've broken my R-trigger Those idiotic service people even ticked of a box on the service papers that they've checked that all buttons where working (i don't think so, slackers). They did this on both occations
My play had no juice on it so i wasn't able to see if they had fixed my problem about not being able to reboot without pulling the battey and the random switch off's. Further more the service papers that came back with the phone didn't mention it at all? They did fix my volume button or atlest it seems they did as i couldn't turn it on and check if it did actually work.
So once again i'm without my play, but this time they're processing it express
Regards Dousan...
As long as you can use your phone,its all good
Cat_On_Droid said:
As long as you can use your phone,its all good
Click to expand...
Click to collapse
Yeah i know, I'd rather have them fixing it though, than having a fualty device. In the end it might go to SE and let them see if they can fix the issue. Hope not, don't want to be without my play once again Got the iches for gaming and now EA got free games, bummer
Regards Dousan...
Well just need to vent a little.
Starting rant:
So I got my phone back today for the third time. They did fix the R-trigger they recked the last time it was in for service, but they didn't fix my issue with the random rebooting/turning on without pulling the battery.
They claim it worked fine before shipping it, but when i unpacked it and let it charge enough to power on guess what it didn't turn on i had to pull the battery to get it to turn on lol They shipped it without checking if they fixed it. Hell i don't even think they tried at all cuz then they would've cought it straight away. They're full of BS and when googling them and reading their trustpilot it's also full of dissatisfied customors with the same type of problem as me, no fixing or pour fixing or even more breaking of the device or simply lieng it was water damaged
Hey that sound's familiar to me, not fixed and more broken, those C*NTS.
I'm pissed and nothing i can do but a claim with the place i made the purchase.
Rant ended
Regards Dousan...
End of story...
Well the last update on this.
I made a claim with cdon.com where i bought it and sent it of to their service center for repair and once again it was returned non repaired. Still wouldn't turn on without pulling the battery. Then they sent it of to SE and they couldn't fix it either and sent a new device to cdon.com, but i chose to get my money back instead of a new device.
The cons of this device ended up being more than the pros. Relly liked this device though and what it was supposed to've been. I was just not the big gamer i used to be and mostly played RB6 online and found the lag of analog touchpads support in fpse annoying and psxperia converter tool didn't work with the games i liked to play.
Anyway it was a fun ride while it lasted and mostly a friendly helpfull crowd I encountered here in the play sub forum. Must say that it has been the best forum I've been submitted to so far
Thanks to all of you and I might see you around
Regards Dousan...
What are you going to buy in the end?
Logseman said:
What are you going to buy in the end?
Click to expand...
Click to collapse
I ended up with the Lumia 800. The N9 seemed nice and have good specs and a familiar OS, but tried it out a few times in a shop and didn't get that wow feeling. Further more read a few things on TMO (talk.maemo.org) in the N9 sub forum that convienced me not to pick up the N9. Even read some danish users experience with the device and it wasn't good all in all. Though the N9 has it's openess and a lot of modding potential i didn't want to go for a 'half finished OS' as i see it from reviews from users. On TMO hardcore N900 users that shifted to the N9 was dissapointed in the N9 as it's gone more mainstream and comercial in how Nokia build the OS.
As of now the Lmia suites my needs much better and I do like the WP7 feel and looks.
It was hard to choose between the two devices as they both have good things going for them.
Regards Dousan...
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
Dear all,
Require your help in recovering my Xperia Arc S from boot loop.
The phone had issue in switching on bluetooth. So i thought of restarting handset.
After restarting handset, the handset was stuck in reboot loop.
So connected the phone to pc companion and upgrade phone o.s to 4.1
It worked for 2 days. Now when i tried to switch on bluetooth from settings; phone got restart and stuck in reboot loop.
Kindly help.
Thanks in advance.
There's a thousand plus threads on boot looping, give one of them a read.
Sent from myushi
XperienceD said:
There's a thousand plus threads on boot looping, give one of them a read.
Sent from myushi
Click to expand...
Click to collapse
Dear XperienceD,
I have searched xda developer and read several threads, but none of them had proper resolution.
If you know any thread where proper solution is provided, Kindly let me know.
Thanks.
Since you repaired it with pc companion, and still get bootloop after enabling the bluetooth, i think this is caused by a hardware fault
Sent from my LT15i using xda premium
jikuma said:
Dear all,
Require your help in recovering my Xperia Arc S from boot loop.
The phone had issue in switching on bluetooth. So i thought of restarting handset.
After restarting handset, the handset was stuck in reboot loop.
So connected the phone to pc companion and upgrade phone o.s to 4.1
It worked for 2 days. Now when i tried to switch on bluetooth from settings; phone got restart and stuck in reboot loop.
Kindly help.
Thanks in advance.
Click to expand...
Click to collapse
Download PC Companion, repair your firmware.
If problem still exists, go back to the shop.
Guys sorry for kicking an old thread but a friend asked me to help out with ARC having the same problem on stock ICS 4.0.4 is there any solution for this? If I were to go to a custom ROM will it fix the problem?
Thanks in advance
abirjin said:
Guys sorry for kicking an old thread but a friend asked me to help out with ARC having the same problem on stock ICS 4.0.4 is there any solution for this? If I were to go to a custom ROM will it fix the problem?
Thanks in advance
Click to expand...
Click to collapse
Check the post above yours.
Someguyfromhell said:
Download PC Companion, repair your firmware.
Click to expand...
Click to collapse
abirjin said:
Guys sorry for kicking an old thread but a friend asked me to help out with ARC having the same problem on stock ICS 4.0.4 is there any solution for this? If I were to go to a custom ROM will it fix the problem?
Thanks in advance
Click to expand...
Click to collapse
I too have experienced the same problem..please provide.a.solution
Try this, helped so many times with Arc S:
- turn off your phone
- remove the battery cover
- remove the battery
- put a small piece of paper between the bottom edge of the battery hoousing and the battery (the side opposite of the battery connectors, so the piece of papper pushes the battery towards the battery connectors)
- put the battery back
-turn on your phone
Tipster said:
Try this, helped so many times with Arc S:
- turn off your phone
- remove the battery cover
- remove the battery
- put a small piece of paper between the bottom edge of the battery hoousing and the battery (the side opposite of the battery connectors, so the piece of papper pushes the battery towards the battery connectors)
- put the battery back
-turn on your phone
Click to expand...
Click to collapse
Its not the battery or power issue.
It has something to do with software.
rahulag1997 said:
Its not the battery or power issue.
It has something to do with software.
Click to expand...
Click to collapse
I had similar issue on my Arc S, and this helped. It seems that there is a loss of powerdue to bad contacts, and the voltage level drops so the phone goes into restart loop. Try it, can't do any harm
I had a problem earlier (some 10 months ago) when i turned on blue tooth it went on rebooting, I tried to get into settings and switch off the blue tooth which was not possible due to fast rebooting. Then I read read in a forum to leave the mobile to reboot for nearly 8 hrs or so, so I left it like that (to reboot continuously) for more than 6 hrs, then it became normal with blue tooth going off (I think so) and I went to settings and then to backup & reset (I think I lost some data during this). From then on I never tried to use blue tooth.
Again today (19 Nov. 2015) I wrongly pressed blue tooth instead of wifi, then again the problem of rebooting started, I was upset thinking of shunning this mobile once for all. Then suddenly I searched in web and got this link :xperia-arcs-auto-reboot.blogspot.in/2012/08/sony-ericsson-xperia-arc-s-auto-reboot.html , where it is asked to keep the battery tight in it's place to keep good contact with its terminals in mobile. Before doing this, I took a conductive metal (a small knife) and I shorted all the three pins in the mobile where the battery touches to give power. *WARNING: NEVER TRY TO DO THIS IN THE BATTERY*. Then placed a piece of paper in the back of the battery and inserted in the slot. Then I switched ON and it started and the boot was holding for some time (say 30 seconds), with in which I went to settings and switched of blue tooth and switched off the mobile. Then removed the battery and inserted again with the same piece of paper and restarted, now it's working.
In my experience, this mobile is having problem both in the battery placement for tightness and in the blue tooth software also. Otherwise this is a good mobile. Thanks for the forums which helped me salvage my mobile with many important contacts. I share this here out of gratitude for these forum. Otherwise I would have to spent a lot for software reloading if I went to authorised or some dubious service centres.
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Mr_Pistachios said:
Hey there,
Im a newb here, and this is my first thread, but whatever.
It all started a few months ago.
Several weeks after I rooted my play, and flashed cm7, with doom kernal, my play just suddenly didn't turn on. (Like, turned it off for the night, but refused to turn on in the day again) . However, after I took out the battery and charged it for 10 mins before plugging the battery back in and turning it on again, it worked. This happened intermittently, and through the 12 months I had with this phone, this has happened multiple times, albeit rarely. Every time it happened, it wouldn't turn on, no led when plugged in the charger, no nothing. Its like a dead brick. Plugged it into the computer and it says "QHSUSB_DLOAD". It would work after I charge it without the battery tho. LOL. - weird. (Something like this, link here
However, yesterday, 31/1/2013, my luck basically ran out. The same thing happened again, with "QHSUSB_DLOAD" showing up and all, but my above method didn't work. And so, I'm stuck with a dead brick.
Basically, my xperia play is unresponsive. Plugged it into the computer and it shows "QHSUSB_DLOAD" I think it stands for Qualcomm High Speed USB Download mode. Today, following this link I just randomly plugged in my phone while holding the back button, with flashtool open in the background. Its some miracle, like, my pc suddenly detected it as an unknown device, and flashtool did some kind of thing, not sure, forgot to screen shot but i think it goes along the lines of "installftfkit". After that, my phone booted.
However, because I wanted to plug in my sim card, i rebooted it, and this time it wouldn't turn on. I tried replicating the results, and all i got wasn't "unknown device" but "QHSUSB_DLOAD".
And there you have it, Xperia Play stuck at "QHSUSB_DLOAD" permanently after several times of intermittent incidents of that happening. It may be hardware failure, which explains the intermittent incidents.
But Im still kind of curious. What causes "QHSUSB_DLOAD"? What component fails that would cause the PC to read it as "QHSUSB_DLOAD"?
Its a dead brick, but I am still trying to revive it. I installed qpst and the QHSUSB_DLOAD drivers. QPST configuration reads a phone in download mode(image 1), QPST software download seems to be able to flash a phone and boot image(image 2). But it needs a hex file and stuff. (Not sure bout that)
Is it easy to get a boot image thing for xperia play? Can i flash it using QPST and make my phone work again?
Thanks for your help guys! Really appreciate it!
Click to expand...
Click to collapse
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
another Xperia Play Problem
Hi I am a noob also.
I am having a similar problem. Today I was trying to install the wifi module since it wasn't installed on the gin2Jellybean rom, i tried to flash the phone using the Flashtool (turned the cellphone off and pluged it in again while holding the back button) then the window disappeared and nothing happened. So I tried again, but first I took out the battery and put it in again and tried to flash again and now nothing is happening, Doesn't turn on, Flashtool doesn't do anything and when I try plugging it the laptop does the sound of an unrecognized device. The phone doesn't vibrate or anything when I press the power button.
Just realized that I tried flashing my cell phone using the x10 BLRelock.ftf crap.. is there anyway I can fix this?
Please Help.
Thank you.
216Monster said:
Correct me if Im wrong...but Im guessing you tried Flashtool and it doesn't work ?
Also , are you familiar with using fastboot?
Click to expand...
Click to collapse
Flashtool and fastboot doesn't detect my phone. So yea .
Mr_Pistachios said:
Flashtool and fastboot doesn't detect my phone. So yea .
Click to expand...
Click to collapse
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
216Monster said:
Are the fast boot drivers installed ? Is your boot loader unlocked ?
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Mr_Pistachios said:
LOL WTS.
As I said, its totally intermittent and random. I tried plugging it into the computer today, and this time a red led was flashing. I let it charge up a little, and there i had it, booted up perfectly normally.
Maybe the plug is becoming dusty or whatever, resulting in the detection being very intermittent? It happens on and off.
When the phone booted up, I noticed the battery level being very low (2%) maybe it needed some charging? Maybe the battery's screwed?
Its really weird.
And yea, fast boot drivers are installed, and boot loaders are unlocked (If not cm10 wouldn't have been installed lol)
Gonna keep you guys posted and see if it goes dead after restarting. Gonna restart after it charges up to 40%.
(I need to restart cos I have to plug in my sim and memory card)
Click to expand...
Click to collapse
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Mr_Pistachios said:
Well, I restarted and it worked.
My theory is this: Phone ran out of batt one day. Plug is loose and dusty. Computer couldn't detect it properly, charger couldn't charge my phone properly (contacts are rusty or whatever shyt) and therefore phone couldn't on.
Don't know why my computer detected it as QHSUSB_DLOAD multiple times throught the 1 month tho.
Could a dirty plug cause that?
During that 1 month there was no response on the computer, thought it was bricked lol.
Anyways, I will keep you guys posted if this happens again, thanks for your help guys!
Imma keep this thread open since this is intermittent.
I'll only close it after 2 months.
Click to expand...
Click to collapse
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Mr_Pistachios said:
zzz. It couldn't boot up again. This time no QHSUSB_DLOAD, no nothing on the computer. 0 detection 0_0
Click to expand...
Click to collapse
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Mr_Pistachios said:
My phone is just driving me batshyt insane -.-
I tried pressing the power button again and it worked, without plugging in the charger nor the computer.
It's intermittent, and now im afraid to turn it off 0_0
Click to expand...
Click to collapse
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Mr_Pistachios said:
FML. Hands were itchy and wanted to see what would happen if I turned my phone off.
Now it can't turn back on, with the computer only detecting QHSUSB_DLOAD.
Click to expand...
Click to collapse
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Made sure to on my phone with the sim card in this time
Never gonna off my phone ever again (Hope it doesn't run out of batt LOL)
One thing to note is this really weird fluctuation in my phone's battery levels. Maybe my battery is going nuts? Attached is the screenshot.
Made sure to on my phone with the sim card in this time
The epic fluctuation may provide clues as to why my phone's behaving like so.
As you can see from the third dip, I was charging my phone. And then after switching it off, it wouldn't turn on. After a day, and countless times of trying to wake it up, you can see that the battery level has dropped sharply. Weird.
The first dip happened a few days ago(not able to turn on) on 1st Feb. The second dip happened on the 4th, while the third happened on the 5th, today These drops in battery levels happened when my phone couldn't turn on.
Qhsusb_dload
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
extrem3hunt said:
I am sorry to say that my problem is still the same every time I plug my phone it is shown as QHSUSB_DLOAD.
I just need to find a driver for it.
PS my phone never turned on after the brick.
Can someone send me a link to the driver and instructions if hard to install.
Thank you.
Click to expand...
Click to collapse
Does plugging the phone into the computer while holding the back button work?
Mr_Pistachios said:
Does plugging the phone into the computer while holding the back button work?
Click to expand...
Click to collapse
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Even if it finds the driver, it wouldn't help you, cos QHSUSB_DLOAD means that the phone can't find the rom, and kernel or whatever. (I think) Its like a computer without an operating system. QHSUSB_DLOAD = Qualcomm Highspeed USB Download Mode, which means its waiting for the manufacturer to flash the rom and shyt, and therefore, your phone is bricked. (Dead brick, i think?)
For me, i think there's something wrong with the connections in my motherboard, resulting in the phone not being able to find the rom and stuff.
Maybe there's no hope for you.........
In short, I think your phone's bricked forever.... Most probably.
any fix bricked play
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
extrem3hunt said:
Nope every time I connect it is detected as QHSUSB_DLOAD and it tries to find a driver and fails.
Click to expand...
Click to collapse
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
QSHUSB_Dload Fix
tommyforest123 said:
Hi,
I am in the same boat. I get the QSHUSB Dload error and I cant get the phone into flash mode. Its basically dead, as the others have mentioned. Anyone get a fix for this thanks
Tommy
---------- Post added at 04:15 PM ---------- Previous post was at 04:06 PM ----------
Hi, could you fix it in the end, I have the same problem...looks like I may need a new play after only 1 week lol : (
Click to expand...
Click to collapse
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
extrem3hunt said:
Hi, I have fixed my HARD bricked phone with the help of Alejandrissimo, contact him and tell him about your problem and he fix your phone online.You will need to know some basic knowledge of electronics and you will require a piece of wire. This is where you contact him.
unlock-bootloader(dot)com/contact/
Click to expand...
Click to collapse
Well, okay, imma give it a try, tnks.
Before flashing your "bricked" device, try this!
Mr_Pistachios said:
Turned on my phone after 10+ tries.
What I did:
1) Plugged out battery, held power button
2)Without releasing the power button, insert the battery.
Repeat until phone turns on.
Moral of story: Persistence pays off. Nah jk.
Click to expand...
Click to collapse
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
proteusgr said:
YOU SAVED ME! We have an Xperia Play at work and it wouldn't boot. Plugged it in USB and the HS-USB QDLoader 9008 Device came up. I read your post, did the power+battery thing 8 times, and it magically came back to life!
I wouldn't believe it if someone told me, but for some reason this seams to work. removing the battery and plugging it back in did not work for me, but holding down the power button did the trick.
:good::victory:
Click to expand...
Click to collapse
HAHAHAHA LOL.
Glad it worked out for you
My guess is that there's something loose inside, and repeatedly trying to do that may help.
I think it's something to do with Sony's build quality, or maybe because the phone sustained hard knocks and stuff. (Probably just wear and tear)
Aledranssimo didn't reply me, so yea. T.T
This issue is probably an intermittent one I guess. I've since moved on and gotten a new phone (Lumia 520)
Hello guys, I had a problem with my phone. I took a photo and the phone restarted alone. Then it started to bootloop infinte times. I do the reset button trick, I repaired with Xperia Companion, I flashed with Flashtool and it keeps bootloping every time. I send you two photos, the first shows you that it's switching on and the second where it does the bootloop with 3 red lights flashing. Can you help me?, or it's something hardware related?. In Argentina can't fix it if it's hardware because this phone wasn't launched in my country.
Okay something is going here. Sony Kill Switch activated in all Z5P?? because Why is everyone having this issue at the same time after like 5 years of smooth sailing?
OP needs to clarify what has been tried. Did you try all the basic reset tricks and holding buttons etc? if you did your last resort will be be allow boot loop to continue until drained. Then fully recharge and use the volume keys to skip the sony logo and boot to the android swirly flash screen thing. Safe boot or fast boot whatever it is
I starting to see a trend with the dates these issues are happening... hopefully this is just a user that has not tried the basics.
p.s.#Only responding coz noone else has bothered
TKBS_UnrealEngine said:
Okay something is going here. Sony Kill Switch activated in all Z5P?? because Why is everyone having this issue at the same time after like 5 years of smooth sailing?
OP needs to clarify what has been tried. Did you try all the basic reset tricks and holding buttons etc? if you did your last resort will be be allow boot loop to continue until drained. Then fully recharge and use the volume up ket to skip the sony logo and boot to the android swirly flash screen thing. Safe boot or fast boot whatever it is
I starting to see a trend with the dates these issues are happening... hopefully this is just a user that has not tried the basics.
p.s.#Only responding coz noone else has bothered
Click to expand...
Click to collapse
Thank you very much for your time. Yes I did it all, buttons combination, batery drain, repair with Xperia companion and finally flashing again the first Android version. Anything worked. I don't know what more to do.
Ferdesor said:
Thank you very much for your time. Yes I did it all, buttons combination, batery drain, repair with Xperia companion and finally flashing again the first Android version. Anything worked. I don't know what more to do.
Click to expand...
Click to collapse
Yesterday i Flashed my first Sony device. It failed 3 times before i got it to work.
Fist it failed on the PC, Then 2nd time It bootlooped. 3rd Time it finally installed applications. Then Bootlooped 1 more time.
I now have A Sony Z5 with 6.01. I am amazed that it worked but there are issues with both Sony phones and Xperifirm that seem to make it hit or miss
I am going to return my XZ3 becuase it is horrible. The Z5 Premium is by far the best Sony avilable. It is worth sending to SONY for repairs
@op
- Try again with Xperifirm / FlashTool 0.9.25
I did it, nothing happen. Same at always.
I keep it switched off some months to see if it starts again alone with the time but no.
It's keep bootloading.