I've (probably) severly bricked my Xperia S - Sony Xperia S, Acro S, Ion

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.

Related

acro s hard bricked

i got my acro s hard bricked
I used twrp for making a backup for the the stock firmware.
and then i installed the 5.0.1 the lollipop custom firmware
the link :http://forum.xda-developers.com/showthread.php?t=2799765
, but it was not rooted but somehow the recovery was working good .. i decided to restore the stock using the backup version which i made in the beginning coz the ROM was sucks. after finishing the loading it asked for restart and after that i got a blank screen and the following
-no response for charging
-no LED lights at all
-non of any combinations working (volume+ and power on , hard reset or volume+up+power on)
-access to fastboot or flashtool is denied
-no power on no vibrations
but after a day of charging an Orange LED appears but i waited for two more days till the LED disappeared
and tried the flashtool but all i got is "device connected but with debugging off"
i think the problem was using recovery with unrooted device but can't find a solution for that
any suggestions ??!!
Notes:
am too calm
am not panic ..
am not in hurry too
and it's not a big deal
i just want the device back in order to get my stuff from it that's why going to Sony service center is not an option coz they format the whole device
Similar here on st26i
On 4.4 Paranoidandroid I've got after a five days of use in one second a lot of force closes. From every app from the system. It was impossible to stop it, or make normal reboot, so I've hold Power + VolUp and waited till three vibrations. Then turn on the phone, normal vibration and SONY logo.
After that black screen. First with some backlight, after minutes phone backlight turn off.
Now:
- No response for Power button
- No response for Power+VolUp combination
- No charging LED
- System find only SEMC Flash Device
- Flashtool says Device Connected with USB Debugging off
- Combination Power+VolUp make connected device to disconnect and connect again as SEMC Flash Device
- Cant acces fastboot, dwonload mode.
smogf said:
Similar here on st26i
On 4.4 Paranoidandroid I've got after a five days of use in one second a lot of force closes. From every app from the system. It was impossible to stop it, or make normal reboot, so I've hold Power + VolUp and waited till three vibrations. Then turn on the phone, normal vibration and SONY logo.
After that black screen. First with some backlight, after minutes phone backlight turn off.
Now:
- No response for Power button
- No response for Power+VolUp combination
- No charging LED
- System find only SEMC Flash Device
- Flashtool says Device Connected with USB Debugging off
- Combination Power+VolUp make connected device to disconnect and connect again as SEMC Flash Device
- Cant acces fastboot, dwonload mode.
Click to expand...
Click to collapse
it seems like we stuck here
Yup.
Is there any windows/linux software for SONY devices like KDZ for LG phones? Which have an emergency flash option and, etc.???
/EDIT
So... I have read a little and I think (wchich I supposed before witout reading) boot is "dead".
I think it will be possibly to flash new boot with s1boot, but. I cannot find service manual for lt26i. Can anyone have it? Or can say where is the Test Point in this device?
makaom said:
i got my acro s hard bricked
I used twrp for making a backup for the the stock firmware.
and then i installed the 5.0.1 the lollipop custom firmware
the link :http://forum.xda-developers.com/showthread.php?t=2799765
, but it was not rooted but somehow the recovery was working good .. i decided to restore the stock using the backup version which i made in the beginning coz the ROM was sucks. after finishing the loading it asked for restart and after that i got a blank screen and the following
-no response for charging
-no LED lights at all
-non of any combinations working (volume+ and power on , hard reset or volume+up+power on)
-access to fastboot or flashtool is denied
-no power on no vibrations
but after a day of charging an Orange LED appears but i waited for two more days till the LED disappeared
and tried the flashtool but all i got is "device connected but with debugging off"
i think the problem was using recovery with unrooted device but can't find a solution for that
any suggestions ??!!
Notes:
am too calm
am not panic ..
am not in hurry too
and it's not a big deal
i just want the device back in order to get my stuff from it that's why going to Sony service center is not an option coz they format the whole device
Click to expand...
Click to collapse
Same situation, really need help from someone because its my only android phone right now.

[Q] Xperia Arc do not start (black screen) and I can not turn off it normaly

Hello all,
I was on ICS 4.04 custom ROM with unlocked bootloader, and my ON/OFF button was failing since several days. In one of that times that I switched off the phone, I could not switch it ON anymore. I had not installed any thing (app, ROM, etc) before the problem. I bought a new ON/OFF module (3 € :cyclops: ) and the problem still goes on.
SIMPTOMS:
If I try to turn it ON, it really works (brivates and the retro ilumination works fine) but I only get a black screen (no logo and sound). If I connect the phone to PC it is recognized. I can go into flash/fastboot mode (green/blue led), I can charge it (red/green led).
If I tyry to switch it off normally trough the on/off button, it does not response (I can not turn it off in this way, only taking off the battery). The white lights in the 2 lower buttons reamins always on if I press the home button, so I can now that the pnone had not turned off.
If I try to go into recovery I can not do it (not purple light), the screen remains black with the retro ilumination working fine
WHAT I HAVE DONE
- to buy a new ON/OFF module that work fine (I think...)
- As I can go into flash/fastboot mode, I have installed several new stock roms with flashtool (GB, ICS) and several kernels without result
- I have checked all the internal conections in the PCB and screen, all seem to be right
- I have tried to go into the phone trough adb, but as I have installed stock roms, I have not enabled the debug mode in the phone, so I can not connect with it. I have searched the web, but I have not been able to find a method to enable the debug mode in the phone
- I have locked/unlocked the bootloader several times
- take off the batery a whole night and to try it again
I am thinking in a problem with the screen, but it was working fine just before to turn it off before the problem. The problem is that I do not want to spend the money for a new screen without to know if the problem is in the PCB :silly:
The more strange thing is that I can not to turn it off normally through the on/off boton , it seems that the phone has gone into a loop internally when you turn it on.
Some ideas?... Thanks in advance
You have the problem that your phone doesn't boot, the problems lies within your kernel,
first of all to fix it, use flashtool and search for a stock firmware for your arc, don't know if you got a lt15i?(Xperia Arc) or lt18i (Xperia Arc S).
This will fix your booting problem...
Make sure your bootloader is unlocked, make sure you follow the ROM-instructions step-by-step when you install one, because this is the reason you failed installing your custom kernel.
Some instructions on how to install a custom rom =>
Step 1. Gather information about YOUR phone. (write down your phone type, your kernel version, your baseband version etc....)
Step 2. On your phone go the your Settings>About Phone> Build Number and press this about 7 times, you'll notice the notification of becoming 'developer', then go back to settings>developer settings (above About Phone) and scroll to whenever you find USB-Debugging, make it active
Step 3. Install ADB and fastboot drivers for your phone
Step 4. Unlock your bootloader
Step 5. Find and download a compatible ROM ( Make sure your phone type is listed as working ... ) and install recovery on your phone.
Step 6. Open up the ROM zip-file and look for the kernel (Boot.img) inside of the ROM and extract it OR Download a kernel which is supported by the downloaded ROM
Step 7. Copy your Kernel image (boot.img) to the ADB Driver map (not necessary but alot easier to work this way) and copy your ROM-zipfile to your SD or Internal Memory.
Step 8. Open up a (Command) Terminal and use the 'cd'-command to explore to your map with adb drivers
Step 9. Connect your phone with your computer and type in the terminal-window: adb reboot fastboot
Step 10. You'll notice your LED changing to blue when it worked. Then type in fastboot flash boot boot.img
Whenever this step has worked you'll have flashed a custom kernel on your phone....
Step 11. Then you got to boot into recovery using Power + Volume Down
Step 12. In recovery do a Full Wipe, and install your ROM (+ Gapps whenever you need google play store.)
You now have a custom ROM and kernel installed!
many thanks MrMaddTraxx. That is not my problem, but your answer will be very usefull for me in the future :good:
Definetively I think that the problem is that the screen is broken. My main problem was that I have not enabled the USB debugging in my mobile and I could not make any important change on it.
Finally I got to enable USB debugging as I show in this post:
http://forum.xda-developers.com/showpost.php?p=61792353&postcount=204
Once I have USB debugging, I could enable the screen with this wanderfull app:
http://forum.xda-developers.com/showthread.php?t=2786395
I could control my phone as the touch screen works OK. I have been able too to connect it to my TV through HDMI, seeing my mobile in it too.
So the only thing to do is to buy a neww screen. I would like to ask you if you believe really that the problem is in the screen (as the backlight and touch screen work fine) or in the connections for the screen in the PCB
thanks

Red LED, No Boot Because of My Idiot Moment

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.

Galaxy Tab 3 NO Power, boot loops when plugged in. Otherwise nothing Video attached.

Hi all, I've been using XDA for years since the original O2 XDA's and I have never had to post anything as I've always found my solution. I'm hoping somebody can assist me with a problem I have on this stock galaxy tab 3.
The device was brought to me after being thrown down the stairs. I replaced the screen and built it back up,
Removed battery connector and reconnected = nothing happens
Press power = nothing happens
press download mode = nothing happens
press recovery mode = nothing happens
Plug USB into PC = nothing happens on PC or tablet
Plug in USB mains charger and it displays battery charging logo but it doesn't fill or animate the fill then it starts the samsung boot screen. It reboots and continues to do this constantly and never ends.
I've tried two batteries and both batteries work in another tab 3 but neither batteries changed how the device works.
Thank you for any advice in advanced!!
I just received a Tab 3 lite (SM-T110) for repair, it's having a similar problem.
It does automatically turn on when plugged into charger or computer.. It is stuck on a bootloop, requiesting a Kies recovery. It does reboot when given the three finger salute (center button, volume down, and power) - it will not enter recovery mode though - same firmware error message). The device is also full off or full on, no indication of it's it's recharging or no - let the battery run out, it's off - else it's on (does not turn on or off with power button). I don't have any info how it got into this state - most likely power loss during a firmware update, but haven't ruled out other possibilities (ie bad rooting job, a custom ROM upgrade went wrong, etc). I'm not 100% concerned about cause, but hopefully I can unbrick the thing.
Anyways, I loaded Kies onto my computer and put it into recovery mode and plugged it in - nothing. Exit the recovery mode of Kies, and all of a sudden the program goes nuts trying to connect and disconnect from the device. Hmm... Okay, disconnect it, uninstall Kies, install Kies3 and try again - same thing except it complains the device is too old when the program leaves recovery mode - but same thing otherwise - does not show up in recovery mode, connects and disconnects at huge rate when not in recovery mode....
Hmmm...
Now looking at the screen, it does indicate (in the upper left hand corner) that it's in ODIN mode... So my next step I figure I'll try ODIN (although I'm researching ODIN at the moment as I haven't used it before (never had to unbrick anything from Samsung prior to now).
Okay, that was painless - downloaded and installed ODIN 3.10.7, and then downloaded the latest firmware from Samsung, extracted the firmware, added it to ODIN's AP line, then hit start to push the latest firmware onto the tablet. Good as new again.

Phone Not Entering DA mode.

So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.

Categories

Resources