Red LED, No Boot Because of My Idiot Moment - Sony Xperia ZL

Just happened today, I root the phone with kingroot, then installed XZDualRecovery to remove the kingroot and replaced them with SuperSU. One thing led to another, instead of flashing the SuperSU package, I end up formatting the internal storage. Nothing left there. Luckily I managed to realized my mistake in time, before rebooting the phone. So I download the flashable stock rom, planning to copied via MTP, then flash it to restore my phone. Two hours later, the download finished - yes, sadly, it took that much time here to download 1++ GB, and I still considered it fast - That 2 hours of being bored unfortunately led to another stupid mistake. I rebooted the phone before I copied and flashed the downloaded stock rom :crying:
TWRP only only offers me to flash the SuperSU package, then rebooted. Needless to say, the phone is dead. Just the red LED laughing constantly of my stupidity.
Quick Googling tells me the symptom pretty much the same with hardbricked ZL. Red LED, no Fastboot, No Flashmode. Pressing the button at the side of SDCard slot only make the phone vibrates, show Sony Logo, then blank. Okay, time to get panic, time to light a cigarette and take a distance for a bit to cleared out my head.
That done, I start googling to troubleshoot the problem. Quick search reveal the tools I need to recover the phone. I need Flashtool, ftf stock rom, good cable data, probably EMMA too. Unfortunately, the Flashtool only available through torrent, which has no peers, so I have to look somewhere else to get it. Wasn't ideal, but what a heck, I need to recover this phone.
Once all the tool in place, time to execute. Several guides I've found tells me I need to flashed the stock ftf with flashtool. But even with the cable plugged and constant pressing on the all available button (power, vol up, down and sdcard side button) can't make the phone recognized by the computer. I've tried every combination of cable plugged/unplugged, button pressed/depressed, all to no availed. Desperation seeps in.
Okay, time to take another break, another cigarette, and charge the phone for a bit. Afterward, I choose to tried to work on the phone recovery using linux. Maybe windows messed up somehow with the driver thingy that prevent me to fix the phone. No such luck unfortunately. Linux also failed to detect the phone. Hmmpppphhhh... Back to windows then.
I fired up the flashtool, pressed to lightning button, choose flashmode, pick the ftf files, then pressed the yellow button on the side of sdcard slot continually. The phone vibrates, 3x, I keep pressing, then it vibrates again 1x, but no respond from the computer, so I keep on pressing it. It vibrates again in 3x, paused, 1x, long paused rhythm. Then something happened, the LED turn green, and the windows notifying something happened. The log column of the flashtool start filling with lines, but end up in lost connection with the phone. Its a progress though, so I turned the phone off for a bit, to restart the process again. What I've done:
1. Start the flashtool.
2. Wait till it finished the initial detection.
3. Pressed the lightning button in flashtool.
4. Choose the Flashmode.
5. Choose the ftf files to be flashed, then pressed the flash button.
6. Pressed the button at the side of the sdcard slot continually - using a bamboo toothpick - until the LED turn green.
7. Let the flashing process done.
8. Restart the phone.
Voila, the phone boot normally, showing the sony logo, then the blue wave then it boot to the wizard screen with low batt warning. So I plugged it to a charger, then proceed with the wizard. The funny thing is, I swear I had more than 90% battery before I entered my special idiot mode. Apparently all of that red led period drained the battery fast. So after I finished the wizard, I put the phone on airplane mode to accumulate enough juice (till 9%) then I test to reboot the phone to make sure it really work. And it does. So I turned it off, to charge faster so I can start updating the firmware (I used C6502_10.5.A.0.230_10.5.A.0.230.ftf) and sets the phone straight again.
So that's how I spend my quality time today. Not much, but hopes it can help anyone out there with the similar problem. Cheers.

Very informativ.
Thank you for sharing your experience. I've found it very useful.

seriously a big thanks. thats a lot of effort. cheers to you. even though i dont need it now (hoping i dont end up like that) its still a great gesture from you.

Related

Boot problems - can't get to Tricolor, but boots to Android

Hello all,
I've searched and found some things, but nothing that matches my problem.
HTC Kaiser, branded Swisscom. HardSPL, I don't remember the version. Trying to get to tricolor screen, no key combo works. Camera+reset w/stylus, camera+power, even the two soft keys to reinstall the rom in memory.
After pulling the battery (and waiting more than 5 minutes) and inserting again, pushing the power button turns on the green LED, but goes no further, even after waiting up to 10 minutes. Pulling the battery, then plugging in the USB charger (without presses the power button) will flash a white screen after 7 seconds, then a pause of another 10 seconds, then the phone boots in to Android (again, without pushing the power button, just plugging in the USB cable.
Once in Android, everything works (except the factory reset, it just hangs forever). I need to install WM 6.5 ROM.
Tried the KAISDIAG.NBH and the 329 HardSPL recovery, but no reaction and still can't get to the tricolor.
One last piece of information, when I plug in the USB data cable, the phone flashes the "USB connected" message, and then repeatedly flashes it again every 3 seconds. The computer makes the USB connected sound, but no communication and the KaiserCustomRUU.exe can't see the phone.
Any suggestions to get to the tricolor? It unusual to turn on the phone by just plugging in the USB cable.
Thank you and great work.
Try power+camera+stylus pressing the reset.
A while back the charging behaviour was changed, so that now plugging in a charger, or usb, boots the phone, ( previously we could not charge if it was switched off).
Your problem of `losing` the bootloader has been seen before, but is rare, and seems to have no definite cause, the last time I remember seeing it turned out to be a faulty camera button.
Sent from my HTC Dream using Tapatalk
Thanks and one more question
Thanks Zenity.
I'll continue working on it. One quick question, is there a command in Android to force a hard reset or to the boot loader?
Camera Button
Ok, after searching more (due to Zenity's suggestion) and reading other threads, I don't think it's a faulty (Fawlty?) camera button.
Somehow, the phone takes along time to boot, and must use some info from the bootloader, as it loads Android.
But all attempts to get into the bootloader fail. I can't establish communication by USB, but I think I will focus my efforts there. I've pushed and help all the buttons in different combinations for too long.
I'll let you know, and thanks again!
Ok, done some research into way to detect that the camera button is functioning, ( since this button is vital in getting the bootloader), no luck yet, but research continues, looking at remapping the camera button using atools, just so i can get a response of some sort, ( normally the camera button does nothing in android, it's unmapped).
Edit: nope, atools won't help, won't let me remap the camera button.
Atools-keymapper remap the key only in the android GUI not in kernel so any change doesn't effect directly the kernel.
Yeah, realised that, just thought there might have been an easy way of diagnosing the camera button, to see if it was at least functioning, but if it's not enabled at kernel level then it will be difficult to test without disassembly and getting a meter on it.
Sent from my HTC Dream using Tapatalk
Update - Android.process.acore
Hey all, still trying to connect by USB to use the CustomRUU tool. Now when I plug in the USB, I get a repeating 'Process android.process.acore has stopped etc".
when I click force close, it pops up again and again.
Pulled the battery, and rebooted. Now it boots repeatedly, it shows the splash screen, right when it should go to the Android home screen, it reboots.
Any ideas? Thank you!
probable that the FC and subsequent reboot corrupted the data partition, which is known to happen when the device shuts down unexpectedly.
You can try a 'fix permissions', and 'clear dalvik cache', but normally it takes a wipe and re-install of the system, you may get away with not clearing data, but it's often safer to go for the full wipe of system and data.

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work

[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....

[Q] phone unresponsive, will not power on

Let me start off by saying I was flashing a different rom, kernel, flashable zip with all my user apps, and gapp(all via philz recovery, clean wipes only ). I pushed reboot and the screen went black and did not reboot. Attempting to power the phone on, boot to recovery, or to download mode and the phone is completely unresponsive. I tried plugging it into a computer and going through my files saved on the phone, the computer will not recognize the phone, or charge. If anyone could send me a thread that could point me in the right direction would be great. Thanks.
Here's a good place to start once download mode and recovery are unavailable: http://forum.xda-developers.com/showthread.php?t=2549068
You need to find a debrick image that matches the bootloader you had on your phone. The files might not necessarily be linked in that thread, but it details the method.
Good luck
Much appreciated who knows when how long that might take if it all. I also did forget to mention im on the NJ1 boot loader. But oddly enough I just had my battery itself charging in wall charger seperatw from the phone. I Read earlier that there are instances where the battery has to be full for the phone to reboot. I plug it into the udb on my computer leave and come back the red led light is on but the battery falls out because I didnt put the back cover back on, still won't reboot or turn on now. Still not recognized by my computer.

Problem with booting G4

Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.

I've (probably) severly bricked my Xperia S

Hello everyone! I decided to disassemble the phone (I had had disassembled it a few times before, and previously everything was fine after that), but this time after assembling it back I found out that screen and light bar don't work, but system seemed to be working (because there were working LED indicator of charging and vibrations). Well, not-working screen may be may fault, but I don't see any damage signs of flexible flat cables or display.
The thing is that my computer was unable to see its files (except compability XML files time to time, after countless plugging and unplugging the device). It recognizes that the phone is Xperia S, there is a logo of it, a branded tab when clicking on the device icon in Control Panel... Another interesting thing is that Windows recognizes the phone's firmware version as 1.0 ; Files weren't that important for me, so I tried making hard-reset. After that, nothing changed. Tried installing stock ROM (My phone had been running stock ROM already btw) using Flashtool and the device in fastboot mode (flashmode didn't work because I had to use older Flashtool version, but I found out it too late, so installed an older Flashtools version after that step), installed stock kernel... And then I couldn't turn it on but could enter flash mode/fastboot mode (BUT ONLY after making hard reset again.) OK, installed stock ROM again (now in flash mode), now I can use flash mode and fastboot, but once I leave these modes and leave the phone charging, LED indicator works as long as the phone is turned off. After pressing the "Power" button, I can do nothing with my phone at all. Entering flash and fastboot modes works only after making another hard-reset.
TL;DR: Screen doesn't work (light bar as well), I'm able to use flash mode and fastboot mode, but I can't turn the phone on (after attempting to turn it on, LED indicator won't work, and as I can't turn the phone off using the screen, I have no other options to power it off for flashing except making a hard-reset, or maybe removing the battery). Would be glad to hear your advice about what to do.

Categories

Resources