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...
Hi there, this is my first post, i didnt want it to be like this but i have come to you in desperation.
I was excited about 4 hours ago to realise my phone was getting an update saying it was going to imporve battery life etc..
Well i let it do its thing while it was downloading, i went to check after an hour or so and it said the software had been corrupted or something along those lines, either way it had to start the download again.
It was about bed time when this happened so i chucked it on the charger, fell asleep, woke up and it was doing something on a kind of screen i had never seen before, black screen, obviously showing that it is processing the update(i was a little tired from waking up) i think i remember taking its time maybe longer than it should have been.
I went back to sleep woke up about an hour ago from now and checked my phone and the screen would not turn on, i think the charger cable had fallen out from the phone because it is loose and does that some times.
So i placed the cord back in and it didnt seem to respond with the red led coming up for a while then all of a sudden it worked for some reason, but was flashing. i suspected this was because the battery had been sucked dry. So after a while the led stopped flashing and i pressed the power button, sure enough it powers up straight away to the HTC - quietly brilliant screen. And thats that, end of story. It's stuck on that screen WTF?
I have been through forums like these interested in changing ROMs and so on but it all seems so complicated i never even bothered, so obviously i am a noob, but i dont think there is any reason for this to happen other than sh*t luck.
Can anyone help us out?
Your better off sending for repair unless you want to start unlocking the bootloader etc.
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
masucu said:
Reboot your phone in bootloader ( press PowerButton + Volume down at the same time) you will get to a screen with various lines, look factory reset, navigate that menu with your volume keys. Hit factory reset you should get . See if it fixes it.
Click to expand...
Click to collapse
mercccccccccccccccccccccccccccccccci
zezo_ddd said:
mercccccccccccccccccccccccccccccccci
Click to expand...
Click to collapse
Well did it work? before you say that long thanks
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
helter_skelter87 said:
Thanks for your help, unfortunately, the factory reset didnt work.
What happened when i first did it, the update screen came up like the first time but still ended up freezing on the quietly brilliant screen.
I'd be willing to unlock the bootloader, i really dont want to send the phone away for a third time. Why didnt i get the Galaxy S3!?!?!
I hate to ask, can u point me to the right thread to do that, there seems to be a few but they seem to have different purposes.
Thanks again.
Click to expand...
Click to collapse
If you wait a day or so, the RUU will be released for your region now that the OTA has been released.
You'll be able to fully reload your phone - this is all HTC do when you send it for repairs and you can do it in a lot less time.
At the moment, HTC may even reload the 2.17 software so you may still have the problem again when trying to load the OTA.
Thanks all for your interest.
I spoke with customer support and they told me exactly what i already had done, factory reset through hboot.
After that was a no go, he told me i have to send it back to the point of sale, so they can flash the software?
Where can i find this ruu once it has been released?
I'm pretty sure the updates all say to not have the phone plugged in when updating.
Sent from my HTC One X using xda app-developers app
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
foofiebeast said:
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
Click to expand...
Click to collapse
Hi,
The best way to rule out any software problems would be to flash the latest 6.2.B.1.96 ftf using Flashtool. So, first make sure that the phone has enough charge, then press and hold the volume up+power combination until you get three vibrations. Then press and hold the volume down key and simultaneously connect the USB cable when Flashtool prompts you to. Once the flashing is complete, disconnect your phone and turn it on normally.
Regards,
abcdjdj
Sent from my LT26i using xda app-developers app
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
foofiebeast said:
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
Click to expand...
Click to collapse
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
sudhindrakv said:
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
Click to expand...
Click to collapse
Well there is a slight problem.
The phone does not have an unlocked bootloader yet, so I can't use flashtool. It has been flashed back to stock using the method I mentioned above. I have just finished installing ADB because (bear with me please) there is no way to turn the phone into fastboot mode without turning it off (I cannot currently turn it off because I can't see what is happening on the screen and don't remember how this phone works when you hold down the lock key to turn it off). I can perform a hard reset, but no way to just get it to turn off entirely.
So I thought I could use adb to shut it down, but adb won't work unless I have debugging enabled, which again I can't do unless I could basically just blindly navigate the menu to those buttons.
Although if I wait until the phone is fully dead then I can hopefully get it into fastboot mode, but that only gives me one chance. Plus it has a full charge right now, so that's going to be awhile.
Any suggestions?
I can get it in to fast boot if I'm quick, but I still can't enable debugging beforehand so its semi worthless.
I've been trying to watch videos to see where the button placement is to navigate through the menu to blindly enable debugging, but I can't seem to figure it out. It also doesn't help that I have no idea what version of android is now on the phone. I used the mac sony bridge app to restore the phone, but i'm not sure if that set it back to stock stock, or what version of android it set it to.
I am also now even more confused because I connected the phone to the computer and when I browsed it, all the pictures I took were still there...which should have been wiped when I restored it with sony bridge...
figured out it was 4.1 and watched review videos until i found one that showed the menu layout (although now I realize google images would have been more helpful).
Now going to see if I can get the bootloader unlocked.
I still feel like flashing 6.2.B.1.96 isn't going to do anything, because I assume that is what the sony bridge app flashed to it. Also I don't see where you are talking about that the issue I am having was a known issue, if you could point me in that direction that would be very helpful.
EDIT: Actually I'm not sure I enabled debugging after all, as when I do adb devices, no device is listed as running, just a blank space. Though I'm still not convinced doing the above would do anything, as it is basically what I have already done, just with flash tool as opposed to the official sony route.
Anyone have any ideas? I got a torx 6 and opened the phone, checked the connection between the motherboard and phone and it is fine. Screen is still having same issue.
I would be happy to just buy a replacement part for it, but i have no idea what part is messing up. Is it the display (the touch works fine) or is it the motherboard (it seems weird that it would be this because the phone functions completely normally, I even accidentally answered a call yesterday).
If i was to try and replace the LCD (or whatever it is) would I have to replace the digitizer as well? At which point it would make more sense to just sell the phone for parts I suppose.
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
dkconor said:
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I'll go ahead and try that out, but is there really much of a point do you think? Considering I've technically flashed the phone back to stock using the official software, why would it be any different doing it this way?
I am asking honestly btw, not trying to sound rude. I'm thinking it is more of a hardware failure, i just have no idea what part exactly is failing.
The phone itself works totally 100% fine, the touch works totally 100% fine, the only thing that is not happening is the data getting to the screen and displaying. The screen just flashes white for a second and then fades out (as you can see in the youtube link). Or it flashes a solid block of white at the top in the middle and faded white the rest of the way down and then it slowly all fades out (or disappears immedaitely if i press the lock button. The buttons all work fine (physical and touch) and i can navigate around the phone, albeit totally blindly.
This is really frustrating, and I'm pretty disappointed to see how sony had no interest at all in helping me resolve this situation.
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
UchihaDareNial said:
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
Click to expand...
Click to collapse
....right i know, but why does that matter. Why would reflashing my phone help at all at this point. Did you even read my post?
Listen to us
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
424aca said:
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
Click to expand...
Click to collapse
Hi,
because I could not follow the advice from the first user because the bootloader is locked. The second person gave me the advice, but honestly it seemed like pretty pointless advice. I don't understand how it is "obviously different" if it is literally flashing the same firmware (at least the first advice was that). I don't think it's that strange to ask why it would be any different.
To me it sounds like I had a broken window in my house and I asked someone how to fix it. I bought the replacement glass from store A and it didn't fit. I asked for help and someone pointed me to the exact same item at store B and said that surely it would work. Do you understand why this could be confusing? I feel like about half the time people give help on XDA it is very general and people are just looking for "thanks"...
I'll definitely try this though if you think there's a chance that it might work out differently. I'll try and get it set up tonight, thanks for the encouragement, I understand I probably sound stupid, just trying to figure out what to do.
Also, I assume this flash tool won't work if USB debugging isn't enabled. As I've said in previous posts, I can click things just fine, but because I can't see what I am doing, I don't have way of knowing where to click on the menu.
Does anyone have their phone set up with this version of android still. If you could take screen shots of each click to make to get to the dubugging box (and if there is a confirmation box) i would greatly appreciate it. I only had the phone for a week before this randomly happened, so I hadn't thought to enable debugging yet, as I hadn't even thought about custom firmware yet.
EDIT: Or even just a picture of what the screen that comes up when you long press to shut the phone down. I have no way of turning off this phone right now without just waiting for it to run out of battery.
Holding down the power button for a long time does nothing, holding vol up and power restarts it, but I need a way to turn it off. If i hold the power button for like a second so instead of locking it, the menu comes up, I just can't seem to find the freakin button for power off.
(please remember I can see nothing on the screen, it is just blank).
flashtool does not need debugging when you doing the actual flashing
to turn off the phone
SIMULTANEOUSLY hold down
Power+ Vol up + Vol Down (AT THE SAME TIME)
wait for about maybe less than 25 seconds and you will experience THREE short consecutive vibrations
at this time...the phone is off
then you can begin the flashtool method
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
olik79 said:
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
Click to expand...
Click to collapse
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
levone1 said:
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
Click to expand...
Click to collapse
Thank you SO much! I wasn't really able to boot using power and volume up, BUT after your encouraging words and the idea that I might just be using wrong keys, I researched some more and found out about this little red button within the sim card slot! It allowed me to reboot, get into fastboot, install recovery and cyanogenmod afterwards! I'm happy again
Hello.
The phone won't boot up anymore. No matter what I try ( the volume up and power button thing were it vibrates ) it just won't boot. It doesn't get past the wave thingy.
Before that apps randomly closed ( stopped working / application stopped ) and it was generally really slow and laggy.
So now i don't know what to do with the phone, it simply won't turn on.
Any ideas on what to do with it?
Hello, i have something like that, only way to fix was flashtool
help
The same thing happens to me, every time a notification comes out that the application stopped ... and there comes a time when it freezes and no longer turns on, I repair it again with Xperia Companion and after a few weeks it fails again , does anyone know why this happens or what problem does it have?
I have not yet flashed with flashtool because I do not know the process and I do not know what room to use, please help.