Hi, I have read all the related threads about this kind of issue however mine seems to be a unique.
I had tried installing a customized ROM using xRecovery, after the installation was complete I rebooted the phone using the REBOOT button in xRecovery's menu.
When the phone restarted itself I constantly get the SONY ERICSSON white text come back up and then disappear after couple of seconds. This process has been now continuing for more than 3 hours straight.
My phone is an xperia x10, running on the android 2.3 (gingerbread) OS.
I took the following steps to see if I can fix anything (however no results):
1. Tried flashing the OS again however got this msg:
Android version : / kernel version : link_image[1965]: 1154 could not load needed library 'libm.so' for '/system/bin/sh' (reserve_mem_region[834]: OOPS: 1154 prelinked library 'libm.so' mapped at 0x40010000, not at 0xafc00000)CANNOT LINK EXECUTABLE
2. I factory reset the phone
3. Kept the battery out for couple of minutes
Basically, the phone keeps restarting itself and nothing I can do. I want to know if there are any solutions or that the phone is gone?!
Your help would be much appreciated!
Reflash your phone, that means you have to flash 2.3 generic again OR if you are able to get into xrecovery you may able to put a costum ron again.
Sent from my X10i using xda premium
Related
i have just got an xperia s, and unlocked the bootloader through sony's site today. i then flashed the pre-rooted firmware, the correct one for my model, and am stuck in a bootloop. I have had android phones before, and always been able to get out of messes like this, but sony's system seems to be somewhat different from my previous Moto. can anyone tell me how to possibly fix this? many thanks
Flash another firmware with flashtools.
Sent from my LT26i using Tapatalk 2
thanks, currently downloading the 73 version to test. I have an issue with flashtools though, and fastboot in general on my PC, the drivers do not seem to have installed, as when i try fastboot i get blue led for aprox. 5 seconds, then reboot into the bootloop. fastboot works fine on my mac though
Must install them manually. You open the device manager, right clicking on the S1boot, update drivers. Then shows you which folder is the drivers. and voila.
thanks, ive got it to boot again, and tried various roms, but keep having the same wierd issues. first, everytime i boot i have to go through the xperia setup completely from scratch again, as if the phone is brand new.
secondly, im using doomkernel v4a, and have installed the wifi modules as specified, but turning on wifi causes an instant crash and then reboot, sometimes immediately, sometimes after a short freeze
thirdly, somehow 'phone memory' is completely full, whatever i do. Internal memory, when the phone is completely empty, only shows as 25gb, but phone memory is totaly full, regardless of weather i clear app data/cache etc
any help would be greatly appreciated XD
hello,
you must flash doomkernel v1 or v1a , then after modules wifi for v1, before flashing v4a ,
(sorry for my bad english)
Hello I searched through the threads, bud didn't find anything that matched so here it goes.
I am working with a x10 mini pro, on which I have installed( bout a year ago) a cyanogen froyobread mod. Today I decided to update that, I downloaded flashtool and started working around it. Connected my phone and clicked on "Clean" by mistake, afterwards I think I clicked "cancel" , but I am not entirely sure.... anyways now my phone reboots all the time, when it loads up all of the apps crash ( for example "com.android.phone has stopped unexpectedly", launcher pro aswell) and a message appears - informing me that the applications system has failed.
I tried to troubleshoot this, even tried to install a new kernel and rom, but whenever I enter flashmode and attempt to continue the installation of the firmware, the phone itself disconnects from the process and continues on booting the cyanogen. What should I do. Any ideas ?
Also it seems that I am unable to enter recovery and fastboot.
EDIT: Found a way to fix it, but it restores to the original sony firmware( still better than bugged, right ?)
Here is a link: ww w.sonymobile .com/global-en/tools/update-service/ Just download and follow the steps
Yes, Thats true that app called SEUS on this forum. When you device bricked you can always restore it with seus.
Verstuurd van mijn U20i met Tapatalk
Hi, my problem is: yesterday I tried to install ICS according to one forum works smoothly and without problems but when I finished installing (using Flashtool) so I decided to start my mobile phone Sony Ericsson NeoV and there the problem occurred when I gave him launch appeared white text Sony Ericsson while there shone the text but after a while the phone is turned off again spontaneously turned on again and the text appeared to Sony Ericsson. Basically, the phone spontaneously reboots when turned on. Later I discovered that I abort the point when done reboot process (I made it to the main phases where I expected, if not installed but I have not noticed from there wrote that I still waiting) so they probably did not install ICS perfectly.
I tried to connect phone to PC but the circuit is only in the moment when the screen lit text Sony Ericsson strange for some 5-6 seconds (PC companion phone to register about 1-2 seconds as this phone is still searchable) basically the phone is not possible to combine with my PC (before it was normal) Do you think this could be combined with any other PC eventually somehow through the TV? Or not go at all correct?
Sorry for my English might understand How can problem
Thank you for every single idea.
Not sure what you did and which forum you followed, but ICS isn't flashed.
Flash ics .ftf again, and post the log of flashing process.
Try flash again by flashtool and not forget to disable final verification!
First I want to thank all members that have invested precious time and effort to help everyone! You are doing an amazing job!
Second thing I want to say is that I've searched the hell out of the Xperia X10 forum to find solution for my problem. But everything I found and tried was so far unsuccessful. After 1 week of unsuccessful trials, today I decided to join and open this thread as a final effort to seek for answers and a possible solution.
Problem: Every time I open camera application I receive message: "Camera not available"
Tested solutions:
1. I tried SEUS and upgraded to latest firmware: - Phone wont start, gets stuck on camera icon.
2. I tried Sony PC companion, update mode: Same as number 1. Then I tried repair mode: Same as 1.
3. I tried Re-installing a dozen of stock firmwares, 1.6 , 2.1 , 2.3. From branded to Global: - Phone works perfectly, but "Camera not available".
4. I rooted, installed xrecovery, tried several solutions, changed files. no progress.
5. Installed custom rom: Donut HD2.2.6 - Phone works amazingly, but "Camera not available"
Phone info:
Sony Ericsson Xperia X10i
Baseband: 2.1.71
Kernel version: 2.6.29-00054-g5f01537 [email protected] #1
Build number: DonutHD2.2
ETS is ******-8
Currently rooted and installed CWM and Xrecovery.
Cant unlock bootloader since it doesn't recognize certificate
I had a SD card problem before. Solved it by formating sd card with HP disk format software.
I hope someone could help me with this. I don't want to believe that the camera is dead because the phone is in perfect condition. But this would eventually be the final answer.
Thank you!
Have you try this:
http://forum.xda-developers.com/showthread.php?p=12061644
I don't know if that is solution for your problem, but you may try.
Sent from my X10i using xda premium
Dzufa said:
Have you try this:
http://forum.xda-developers.com/showthread.php?p=12061644
I don't know if that is solution for your problem, but you may try.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Unfortunately I'm not able to try and test this solution because I requires a rooted stock android 2.1 (eclair).
My phone doesn't start up on any of the 2.1 stock versions. So far I flashed around 7-8 different 2.1 versions from global to branded etc. but no luck.
Camera with arrow on screen icon appears after which "Sony Ericsson" screen appears and phone gets stuck here and phone temperature rises.
This happens with all 2.1 versions and also when I update with SEUS latest X10 android version.
Only 2.3.3 functions properly on my phone and amazingly battery lasts for 2-3 days even with constant usage of wifi, calls, music and gaming.
But when I tried your suggested solution with the rooted 2.3.3 it gave me some errors in the CMD. Which I tried resolving by running "runme" file as administrator. But another error appears. This is I suppose because of the different android version. The guy says that it works only on a rooted stock 2.1 firmware.
Is there any other way I could test his solution on 2.3.3 rooted stock firmware ?
Thanks again for the reply!
I appreciate it!
Hi, I have a strange problem with my Xerpia Z2..
After flashing a cyanogen mod to test it out.. it`s not possible for me to get a working generic Android system anymore.
The smartphone stuck in a caint of "bootloop" or, if it start android at last, it reboots after a short while automaticly.
The bootloop is like this:
Screen: Shows 10 sec. sony-logo -> than 2 sec. black screen -> than 5 sec. sony-logo -> than it starts from beginning..
The bootloop-lenght varied until it starts finally into android.. sometime it doesn`t come to that point, and it reboots for a very long period (until I get annoyed and shut it down)
I have trying the following things to solve that issue:
- Flashing several stockroms wirh flashtool (D6503_17.1.2.A.0.314_Generic DE.ftf / D6503_23.0.1.A.0.167_Customized DE.ftf)
- trying to reset the hole phone with the xperia "emma" tool
- trying to reset the hole phone with the pc companion software
.. in my opinion, the problem could be find in the bootloader/recovery.. I don`t think it`s a hardware issue, because cyanogen mod is still runs without problems. Maybe some cyanogen remains are still leftover in the bootloader, that don`t work with generic android versions.. that`s what I can imagine. (but i`m not an expert
I don`t get why flashing the phone doesn`t solve the issue., it almost seems that the flash process don`t touch the bootloader, to overwrite it with stock parameters (?) or does not fix that area which is responsible for that issue..
Phone status at this time:
Not root - not unlocked - no backup of TA - DRM Keys (The guy that I bought that phone from, saddly doesn`t do a backup /
Before you flash the stock rom, are you clearing the Dalvik cache?
Whenever I've been through instructions on flashing roms, that always seems to be a step, but I didn't see you mention doing that before flashing.
Lagamorph said:
Before you flash the stock rom, are you clearing the Dalvik cache?
Whenever I've been through instructions on flashing roms, that always seems to be a step, but I didn't see you mention doing that before flashing.
Click to expand...
Click to collapse
Hi, I did that.. the 3 checkboxes in Flashtool are always enabled (Wipe: Cache, APPLOG. Data)