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.
Related
Hey Guys..
I have a Desire here in my Hands with a strange type of Brick.. (at least one I've never seen before) ..
It just does not react to anything at all. The battery is charged and I tested with another cell to be sure that is not the trivial cause.
No Bootloader, No HTC Logo, No reactions at all..
Did happen while flashing a Froyo 2.2 Rom + Radio + App2SD (from the xda forums) via ClockworkMod Recovery but I wasn't there to witness the actual Flash.
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Then battery removed -> Brick.
Anyone got any Idea?
messywrk said:
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Click to expand...
Click to collapse
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Regards,
Dave
If you can access fastboot as opposed to bootloader you might be talking failing that back to HTC it goes
if your phone can not turn off whilst holding either volume down or the back button then yeah it's a brick, send it off to htc, just say it overheated and wont turn on again
foxmeister said:
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Click to expand...
Click to collapse
The battery was removed after flashing and rebooting.
Installed in the following order:
32.41.00.32U_5.08.00.04.zip
LeeDrOiD_V1.2b.zip
942_desire_froyo_a2sd-signed.zip
every process seemed to work normal, no error happened.
Then rebooted the Desire and the "Box with Android-Bot" Screen appeared.. this hung for 30 min or more when I could not think of any other solution than removing the battery to reset..
After this -> nothing.
I suppose as you say it has to do something with the Radio ROM..
Been coming from OpenDesire 1.6b - every flash ran perfectly up to this point.
Damn, I think this one has to go back to HTC.
Is there any possibility to unbrick a phone thats not responding at all?
Could HTC be aware of the modifications or will they really just go with the "overheated and won't turn on again" explanation?
Thanks for your help so far guys!
Yea, the little Droid with the box thing is during a radio flash and you should never pull the battery during that as it does result in a brick.
Can you reach fastboot as mentioned up above?
..tried pressing the "back" button with the power button and the vol-down button together with the power button..
even did the "insert the battery while holding the button" method..
I don't think I can get the thing to Fastboot..
But I will look further into this and try..
..
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
messywrk said:
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
Click to expand...
Click to collapse
I know someone who sent their phone back with a pretty much identical issue and the phone was fixed under warranty no problem.
Regards,
Dave
yay!
you know, even one post of you telling me it went allright for another guy is a big relief..
EDIT: just wanted to let you know I tried invoking fastboot via usb and the android PC tools..
just keeps waiting for the device.. and waiting ..
..will analyse USB traffic in general to conclude if there is a little itsy bit of life left in the phone, but I think this is a dead end too.
thank u all for ur help i have managed to unlock the phone as described
thanks alot every1
saifiraq: You seem to have stumbled in the wrong thread or could we help by coincidence?
..UPDATE:
Did usb-sniffer analysis while pulling battery, trying to turn on, plugging usb in etc.
NOTHING at all..
My baby is on it's way to HTC now.. wish me luck guys!
(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...
Hi everybody!
I have an almost 2 years old DHD which I think is completely bricked. It was working for approximately one years perfectly and then suddenly it stopped working. Whenever I tried to turn it on, it only vibrated once and did nothing more. Sometimes it turned on and these working periods were enough to restore to stock condition (It was rooted and had Eng S-OFF before.). I had brought it to service and they said they was not going to repair it as the device got water damaged. I'm pretty sure it was not! After a few weeks, it started working again. I was using it for 3 months then it bricked again and it's the situation today as well.
Previous week I looked into the development thread and saw all of these new amazing roms. So I took my DHD to see if it's working or not. The situation is the same. Everytime I power it on, the phone only vibrates once and nothing happens. I'm not able to get into hboot mode. At some very rare occassions the phone turns on and works flawlessly till reboot. When I connect it with USB, the computer doesn't recognize it. Battery is charged, I even tried another battery.
Does anybody know what happens with the phone? I'm open to any possible solutions to try. Please don't suggest to bring it to service or repair it, because I have another phone, just want to try to recover it and ask your ideas about the problem.
Thanks in advance!
Greetings,
Adam
So you say you cant enter in fastboot or recovery?
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
paescheh said:
So you say you cant enter in fastboot or recovery?
Click to expand...
Click to collapse
I cannot enter into hboot mode. Didn't try recovery, but assume it's the same.
waterbox said:
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
Click to expand...
Click to collapse
I also think it's a hardware problem. Will take a more careful look at the battery.
Sent from my CM10-powered GT-I9103
need help
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
goofed again said:
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
Click to expand...
Click to collapse
Wrong sub forum buddy, post in the One V Forum.
Its possible that there isn't "water damage", but there could be moisture getting into the phone causing it to act erratic. To cancel out that possibility, submerge it in a closed container full of rice for a few days
Sent from a satellite
Hi,
I recently got my phone unlocked via testpoint (I think) and it was fine for a week or so but then the touch screen started locking up after i turn the screen on and bring up the lock screen and wouldn't respond to my touches (so I can't answer my calls/texts until I restart my phone), the screen itself was fine as I can see everything still and the phone still responds as the gamepad is still functioned so I could turn it off and on again which then fixed it for a few hours.
This has been happening a lot recently and a new problem has developed which is that it will not boot properly, if I have it plugged in and boot from the "charging mode" its fine but the screen doesn't work until about 10 reboots and on battery it hangs at the Sony Ericsson text screen (On boot) and I have to battery pull it and reboot it many times before it will boot successfully again.
It is running a stock gingerbread ROM (Build .42 - rooted). This worked perfectly and never locked up once before the unlock, so I'm placing my suspicions on that. -.-
any ideas for fixes are greatly appreciated as having this phone doing this ALL THE TIME is very frustrating and seems to be happening more regularly and sometimes even when the screen is turned on and I'm using the device.
Thanks in advance and for reading all of that (If you did )
The fact that you unlocked it shouldn't matter that it's having issues booting up. I had mine unlocked via testpoint and it was all good. Try reflashing your stock FTF.
I think build .42 is Verizon, right? But what phone version do you have?
I have the R800i - originally locked to orange. I flashed a .42 build i fund on the internet, i think it was a Chinese ROM as it came with Chinese keyboard etc. and various Chinese apps
hmm, as I'm typing this I'm waiting for it to reboot - Not working -.- I got told by the guy who unlocked it that i cant update my phone or it may blank screen on me or something? i didn't want to risk anything by re-flashing it as i don't want to have to buy a new phone if this one completely messes up to the point that it's bricked I'm thinking a reflash is the way to go... Can titanium backup backup whatsapp properly so i dont have to sort out my activation stuff again? it's assigned to my old number atm so yeahh...
Same problem over here.
I used to use the Doom kernel for over a year without problem but then the touchscren would frequently lose it's ability to react to touch usually a reboot would fix it, at some point i had to hold a button while bootup for it to react again soon i discovered that sliding the gamepad out was what killed the touch capability sliding the gamepad back in did not restore it only a reboot or as i discovered holding the home button for about 10 seconds how ever it was less and less functional until at somepoint nothing would restore it and the touchscreen permanently lost it's touch. Assuming it might be a software problem i reflashed stock rom and stock kernel the problem still persists and i am not sure if ihad this problem before reflashing or not but i also now have the problem that when pressing the power button the phone does not react for 15 seconds before getting to the sony erricons (or doom kernel) writing to not move one step further no matter the wait while starting with usb plugged in again takes 15 seconds wait time before anyting shows up but then after 30 seconds continues to the next splashscreen to start properly.
Initially i assumed it would be a software problem (like slyhedgehog56) how ever as not even reflashing the entire system fixed it i think that option is out of question. with the touchscreen capability i would blame it on the digitizer but would a digitizer problem also cause the boot issues? With unlocked boot loader i am obviously out of warranty and id rather not have to buy a new phone i would what so ever not mind doing some basic human capable repairs on it (for example exchanging digitizer) how ever i don't want to invest into repairs that possibly wont help anyway.
I hope somebody can provide us with some insight.
Well you've also got to consider is electricals can go wrong weather its a phone laptop toaster ect sometimes stuff just stops working for no reason and something will break just the way it works unfortunately
Sent from my R800i using xda app-developers app
ILikeTheWayYouMove2 said:
Well you've also got to consider is electricals can go wrong weather its a phone laptop toaster ect sometimes stuff just stops working for no reason and something will break just the way it works unfortunately
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Well while it certainly is true that everything stops it's not quite for no reason i mean there is most certainly some reason, it's not like the device just randomly decides "im perfectly fine but i wont work anymore" if it's a broken contact a lose cable or a fried chip something IS to blame for malfunctions and if there is a specific pattern of malfunctions it may be possible to track back just what component gave up.
So thank you for notifying me that things break at times i will still continue to wait if somebody possibly has more detail on this particular malfunction though.
Grey-fox-13 said:
Same problem over here.
I used to use the Doom kernel for over a year without problem but then the touchscren would frequently lose it's ability to react to touch usually a reboot would fix it, at some point i had to hold a button while bootup for it to react again soon i discovered that sliding the gamepad out was what killed the touch capability sliding the gamepad back in did not restore it only a reboot or as i discovered holding the home button for about 10 seconds how ever it was less and less functional until at somepoint nothing would restore it and the touchscreen permanently lost it's touch. Assuming it might be a software problem i reflashed stock rom and stock kernel the problem still persists and i am not sure if ihad this problem before reflashing or not but i also now have the problem that when pressing the power button the phone does not react for 15 seconds before getting to the sony erricons (or doom kernel) writing to not move one step further no matter the wait while starting with usb plugged in again takes 15 seconds wait time before anyting shows up but then after 30 seconds continues to the next splashscreen to start properly.
Initially i assumed it would be a software problem (like slyhedgehog56) how ever as not even reflashing the entire system fixed it i think that option is out of question. with the touchscreen capability i would blame it on the digitizer but would a digitizer problem also cause the boot issues? With unlocked boot loader i am obviously out of warranty and id rather not have to buy a new phone i would what so ever not mind doing some basic human capable repairs on it (for example exchanging digitizer) how ever i don't want to invest into repairs that possibly wont help anyway.
I hope somebody can provide us with some insight.
Click to expand...
Click to collapse
I'm not gonna lie myself as the same thing exactly happened to my phone and it died week ago.
Here's how it started
1 Touchscreen died for 5 Seconds when I didn't use phone for long.
- Over two weeks this dead time longly extended.
3 Touchscreen became completely dead and unusable.
- Tried stock rom, Markpython's Ics Rom and Slimbean (no result so hardware problem).
5 Relocked the bootloader, flashed stock fw.
- Device won't boot unless in USB Mode
7 Phone turns unusable (Yes I can navigate using gamepad) and goes to Sony Centre
sewer56lol said:
I'm not gonna lie myself as the same thing exactly happened to my phone and it died week ago.
Here's how it started
1 Touchscreen died for 5 Seconds when I didn't use phone for long.
- Over two weeks this dead time longly extended.
3 Touchscreen became completely dead and unusable.
- Tried stock rom, Markpython's Ics Rom and Slimbean (no result so hardware problem).
5 Relocked the bootloader, flashed stock fw.
- Device won't boot unless in USB Mode
7 Phone turns unusable (Yes I can navigate using gamepad) and goes to Sony Centre
Click to expand...
Click to collapse
Sounds like the exact same problem yes (including the gamepad navigation) would you mind keeping me/us updated over how it goes? what they blame to be the culprint etc?
friends too..
Turns out a friends Xperia play has the EXACT same problem so the test point unlock isn't the issue here tried reflashing this one and no help at all, it will boot if I gold the power button then plug a USB cable in but the screen doesn't respond to touches. The same for both phones, they won't boot without a USB connected and will occasionally work once every 50 or so tries without the cable -.-.
I'm at a loss, I've searched the internet to find no help and everyone just saying "use the Sony repair tool" no. It doesn't work!
sewer56lol said:
I'm not gonna lie myself as the same thing exactly happened to my phone and it died week ago.
Here's how it started
1 Touchscreen died for 5 Seconds when I didn't use phone for long.
- Over two weeks this dead time longly extended.
3 Touchscreen became completely dead and unusable.
- Tried stock rom, Markpython's Ics Rom and Slimbean (no result so hardware problem).
5 Relocked the bootloader, flashed stock fw.
- Device won't boot unless in USB Mode
7 Phone turns unusable (Yes I can navigate using gamepad) and goes to Sony Centre
Click to expand...
Click to collapse
slyhedgehog56 said:
Turns out a friends Xperia play has the EXACT same problem so the test point unlock isn't the issue here tried reflashing this one and no help at all, it will boot if I gold the power button then plug a USB cable in but the screen doesn't respond to touches. The same for both phones, they won't boot without a USB connected and will occasionally work once every 50 or so tries without the cable -.-.
I'm at a loss, I've searched the internet to find no help and everyone just saying "use the Sony repair tool" no. It doesn't work!
Click to expand...
Click to collapse
I have the same exact problem ,I made a very interesting detailed thread about it a few minutes ago , please have
a look at it and put a comment or something ...
Totally Depressed : My Xperia Play is Stuck at Sony Ericsson Text at Boot Screen !
Still nothing for me
Still in repair centre.
Sent from my GT-I9300 using xda app-developers app
(Yay finally got an S3 like I said in my Rom thread)
sewer56lol said:
Still nothing for me
Still in repair centre.
Sent from my GT-I9300 using xda app-developers app
(Yay finally got an S3 like I said in my Rom thread)
Click to expand...
Click to collapse
Thank you for keeping us updated and yeah i can imagine it takes a little longer over the holidays.
(btw congratulations on the S3)
Grey-fox-13 said:
Thank you for keeping us updated and yeah i can imagine it takes a little longer over the holidays.
(btw congratulations on the S3)
Click to expand...
Click to collapse
I got it back , I haven't done any testing but it seems to be working fine.
Boot = OK
Touchscreen = OK
Gamepad = OK
Touchpads = Not Tested but should be ok.
Version = .42 (2.3.4) (UK GENERIC) - Same version as I gave into store.
The software was upgraded to the very last version?
Fought last version was .62
Sent from my GT-I9300 using xda app-developers app
---------- Post added at 06:27 PM ---------- Previous post was at 05:59 PM ----------
Forgot to say they changed the digitizer.
Sent from my GT-I9300 using xda app-developers app
sewer56lol said:
I got it back , I haven't done any testing but it seems to be working fine.
Boot = OK
Touchscreen = OK
Gamepad = OK
Touchpads = Not Tested but should be ok.
Version = .42 (2.3.4) (UK GENERIC) - Same version as I gave into store.
The software was upgraded to the very last version?
Fought last version was .62
Sent from my GT-I9300 using xda app-developers app
---------- Post added at 06:27 PM ---------- Previous post was at 05:59 PM ----------
Forgot to say they changed the digitizer.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Awesome! Keypad fault interesting
hmm you said you had flashed another rom that means you had your bootloader unlocked and your warranty voided right?
Did they charge you for the repairs?
Grey-fox-13 said:
Awesome! Keypad fault interesting
hmm you said you had flashed another rom that means you had your bootloader unlocked and your warranty voided right?
Did they charge you for the repairs?
Click to expand...
Click to collapse
I relocked my bootloader beforehand giving it to repair centre.
I fought I said this a couple of posts ago.
And no they did not charge me at all.
Sent from my GT-I9300 using xda app-developers app
Edit (here's the post) :
sewer56lol said:
I'm not gonna lie myself as the same thing exactly happened to my phone and it died week ago.
Here's how it started
1 Touchscreen died for 5 Seconds when I didn't use phone for long.
- Over two weeks this dead time longly extended.
3 Touchscreen became completely dead and unusable.
- Tried stock rom, Markpython's Ics Rom and Slimbean (no result so hardware problem).
5 Relocked the bootloader, flashed stock fw.
- Device won't boot unless in USB Mode
7 Phone turns unusable (Yes I can navigate using gamepad) and goes to Sony Centre
Click to expand...
Click to collapse
Yes i know that you mentioned it however i thought they would/could check the status using the IMEI and could tell if it was locked nlocked though admittingly getting the code to unlock it using th IMEI does not actually mean that you unlocked it... ut alrigh thanks again
sewer56lol said:
I relocked my bootloader beforehand giving it to repair centre.
I fought I said this a couple of posts ago.
And no they did not charge me at all.
Sent from my GT-I9300 using xda app-developers app
Edit (here's the post) :
Click to expand...
Click to collapse
Hi all,
I have a galaxy note 2, bought in November 2012, I rooted it a few months ago.
Yesterday it was fine, battery was fully charged and it was in my pocket.
It was not doing anything out of the ordinary but when I went to check the time I noticed it was off and I couldn't get it to switch back on at all I tried removing the battery, putting it on charge and still nothing. I tried recovery mode too - nothing.
The only thing that happens when i try switch it on is the little red light from the proximity sensor flashes for a split second.
Has anyone heard of this before?? I've searched and cant seem to find anything like this.
Any help would be greatly appreciated.
try to flash Stock firmware via Odin....
Unfortunately this is the main symptom of Sudden Death Syndrome (SDS). There is no known way to fix it by yourself.
Contact samsung service center ASAP.
Can you answer these questions.
Which firmware was installed on your device?
Have you updated your device to the latest update?
Till you updated it, have you done a factory reset with the old firmware?
j0nnymofo said:
Hi all,
I have a galaxy note 2, bought in November 2012, I rooted it a few months ago.
Yesterday it was fine, battery was fully charged and it was in my pocket.
It was not doing anything out of the ordinary but when I went to check the time I noticed it was off and I couldn't get it to switch back on at all I tried removing the battery, putting it on charge and still nothing. I tried recovery mode too - nothing.
The only thing that happens when i try switch it on is the little red light from the proximity sensor flashes for a split second.
Has anyone heard of this before?? I've searched and cant seem to find anything like this.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I`am sorry but you have to bury your motherboard. Take it to a repair center to get it fixed. Bad luck bro
gee2012 said:
I`am sorry but you have to bury your motherboard. Take it to a repair center to get it fixed. Bad luck bro
Click to expand...
Click to collapse
The smiley! Edit the smiley!
zeeshanonlyme said:
The smiley! Edit the smiley!
Click to expand...
Click to collapse
Exactly what was happening to me. Had the Notification LED blinking, wanted to check, couldn't manage to turn on the screen. Tried rebooting, but can't even see the boot-logo. Battery pulled - nothing. USB port not working when connecting to a PC.
I had MIUI on it with an increased counter, since here in Switzerland it isn't a big deal when you mod your device.
I hope they will ignore the fact of the increased binary flash counter...