Xperia ray freeze on bootloader. - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

I had loaded 1 custom rom (cm-10-20131007-NIGHTLY-urushi ) after try to kitkat rom (AORP - 4.4.20 - BETA#1 - Ray). I use 10 days without any problem. My battery run out to %0. I connected pc by usb cable when phone turned off. The phone itself has made something. After that phone can't open, stuck at bootloader. I try to something but i can't fixed.
1) I flash same rom and kernel, but nothing changed.
2) I turn back stock rom ' 2.3.4 and 4.0.4' with tft, buth nothing changed.
3) I turned back (cm-10-20131007-NIGHTLY-urushi.zip) room. and phone opened but touch panel didn't work. I try all function with pc mouse. Every function run witout problem except for touch panel. I try diffrent kernel 4.1.2 but result same.
4) I sent mechanics. They try jtag but they didn't connect jatg
I hope I could tell properly. Thank you in advance

Related

[Q] com.android.phone force close, X10 Mini Pro

Hello,
I have a weird problem, I sold my X10 mini pro, but the customer has a weird force close of the phone app...
the rom version is 2.1.1.A.0.6 as it is the latest available with an italian KIT number.
Anyone knows how to solve this?
He already tried to reflash via Pc Companion, and hard reset via settings...
he is allready done hard reset and memory reset and what the phone doing now?
he says that sometimes the phone hangs, and it shows the phone FC, the only way to reboot is to take the battery out. But the rom is the original one
if the phone is stock... 3 things
1. the phone has problem in it electronic cirquits not firmware
2. he maybe try to unlock it or root it or other kernel /rom
3. dont put the battery out just press the menu button and on/off button together to reboot it
tell him to make a reset and let the phone as stock without programms to see... if the phone has stock apps with the latest stock firmware maybe is the (1.) if the phone is stable in stock mode tell him that is some programm make that hang... because i see that on my phone where i had it stock... install apps only from android market and see if it stable.... then continue easily and stable ... not 5 to 5 programms every time....
wankel29 said:
if the phone is stock... 3 things
1. the phone has problem in it electronic cirquits not firmware
2. he maybe try to unlock it or root it or other kernel /rom
3. dont put the battery out just press the menu button and on/off button together to reboot it
tell him to make a reset and let the phone as stock without programms to see... if the phone has stock apps with the latest stock firmware maybe is the (1.) if the phone is stable in stock mode tell him that is some programm make that hang... because i see that on my phone where i had it stock... install apps only from android market and see if it stable.... then continue easily and stable ... not 5 to 5 programms every time....
Click to expand...
Click to collapse
I don't think he rooted or installed anything, and the phone was working fine when I had it. It's so weird...
if the phone work fine when u had it and is stock and it did not fall down and brake any electronic parts tell him to reset it all everythings programms and start from begginng maybe is a programm... or else he is unlucky guy recycle or fix it to Sony Ericsson... after all i believe that is a programm problem and i say again ... if the truth is that the phone is stock...
IMHO full memory (on-board).
Remove some apps...
Cheers,
M.

[Q] Screen won't go off !!

Hi, I have a Galaxy S2 (I9100) that's on a stock rom GB 2.3.4
The kernel is KH3.
Phone works fine, but I cannot update to higher android version because KIES says my device cannot be updated with KIES.
After searching these forums I managed to root my phone (flash a rooted kernel with ODIN) and installed a custom rom.
I tried MIUI rom (JB) and also ParanoidAndroid (JB) and both have the same problem.
The screen shuts off after the 30 sec setting, but then after 1 sec it's ON again.
After 30 sec its shuts off, and after 1 sec it's ON again
If I flash a stock rom back (KH3) the everything is fine again.
Also flashed a MIUI ICS rom, which has the same problem!!
Anyone heard of this problem before, or knows what to do??
1. Did I do something wrong?
2. Is there a way to go to ICS stock rom (KIES or another way)?
Please help....
1. Flash a different kernel
2. Or go to Sammobile and download stock firmware, flash it with Odin.
Sent from my deep fried potato
Did you do full wipe before flashing a custom rom?
Yary12 said:
Did you do full wipe before flashing a custom rom?
Click to expand...
Click to collapse
I did
- factory reset
- wipe cache
- wipe dalvik
Then install rom
if custom rom - screen on after 1 sec.
if stock rom - screen normal
************************** UPDATE **************************
Flashed a stock kernel from SAMMOBILE (Latest ICS 4.04 for Netherlands) with ODIN
Same problem !!! Screen turns off after time out, 1 sec then turns on again..
I found that with this firmware an app called "Screen Off And Lock" was installed.
Does that mean that Samsung knows the problem occurs in ICS (and higher).
I checked the option with the delay especially for devices tjat turn screen on again after turn off,
but still the same problem stays.
******** ANOTHER UPDATE *********
Just found out....
Everything works OKAY if I connect the phone to my PC.
It's charging then offcourse, and the USB is connected then.
That must be a clue to the solution, but I haven't found it yet.
Maybe someone else has an idea now (I really hope so)
ferjen said:
******** ANOTHER UPDATE *********
Just found out....
Everything works OKAY if I connect the phone to my PC.
It's charging then offcourse, and the USB is connected then.
That must be a clue to the solution, but I haven't found it yet.
Maybe someone else has an idea now (I really hope so)
Click to expand...
Click to collapse
Maybe your usb port is f*cked like mine, Does it happen only when you fully charged the phone ? becuz my device recognize it as charging(when not having a charger connected), ---> so connecting/disconnecting every time . . My screen goes on/off cuz it connects/disconnects the charger (while no charger connected.) If this is your problem u can try cleaning usb port or check this post http://forum.xda-developers.com/showpost.php?p=30290884&postcount=3619
Unexist6969 said:
Maybe your usb port is f*cked like mine, Does it happen only when you fully charged the phone ? becuz my device recognize it as charging(when not having a charger connected), ---> so connecting/disconnecting every time . . My screen goes on/off cuz it connects/disconnects the charger (while no charger connected.) If this is your problem u can try cleaning usb port or check this post http://forum.xda-developers.com/showpost.php?p=30290884&postcount=3619
Click to expand...
Click to collapse
I don't think this is the same as my problem, because in GingerBread everything is OKAY...
Thanx anyway.

[Q] [Fixed] MTK6589 - Flashtool readback killed BT/Wifi/GPS

Hello,
I've bought a new device - Evolveo StronPhone Q4, MTK6589 based phone. The stock ROM is basically vanilla Android 4.2.1. I've successfully rooted it using Framaroot.
Then I've created scatter file using MTK Droid Tools (all partitions that were formated were ext4).
Then I've decided to create a backup before I start playing with it, so I've tried backing up flash using SP Flash Tool (using Readback), it was running fine and downloaded approx. 20%, then crashed. I've tried that once or twice more times, always failed. Now after I plug it in, windows display "This device can perform faster" and FlashTool won't detect the device. If I connect it without battery with VolDn key pressed, FlashTool detects it and I get S_DL_GET_DRAM_SETTING_FAIL.
However, the phone boots fine, just GPS/Wifi/BT is not working. (No GPS icon appers, and I get errors like BT_open: WMT turn on BT fail in dmesg). Looks like an issue with kernel/HW issue.
Any ideas what could have gone wrong and how to fix it?
In the meantime, I've asked manufacturer for a stock FW image, but I'm not sure it helps...
Update: Okay, I have no clue what just happened. However I've unrooted, reverted everything I've modified on the phone so far so I'll be able to return it to manufacturer as "deffective"... And just for the curiosity connected it to the computer and tried downloading ROM one more time. And it succeeded - I'll upload the ROM once I get access to faster internet connection. I've removed the battery (phone was stuck in Preloader mode because I cancelled ongoing RAM test.), put it back and now everything works.
So, it looks like everything is fine now, however I'd love to know what happened, if you have any clue, please let me know!
fw problem
Mrkvak said:
Hello,
I've bought a new device - Evolveo StronPhone Q4, MTK6589 based phone. The stock ROM is basically vanilla Android 4.2.1. I've successfully rooted it using Framaroot.
Then I've created scatter file using MTK Droid Tools (all partitions that were formated were ext4).
Then I've decided to create a backup before I start playing with it, so I've tried backing up flash using SP Flash Tool (using Readback), it was running fine and downloaded approx. 20%, then crashed. I've tried that once or twice more times, always failed. Now after I plug it in, windows display "This device can perform faster" and FlashTool won't detect the device. If I connect it without battery with VolDn key pressed, FlashTool detects it and I get S_DL_GET_DRAM_SETTING_FAIL.
However, the phone boots fine, just GPS/Wifi/BT is not working. (No GPS icon appers, and I get errors like BT_open: WMT turn on BT fail in dmesg). Looks like an issue with kernel/HW issue.
Any ideas what could have gone wrong and how to fix it?
In the meantime, I've asked manufacturer for a stock FW image, but I'm not sure it helps...
Update: Okay, I have no clue what just happened. However I've unrooted, reverted everything I've modified on the phone so far so I'll be able to return it to manufacturer as "deffective"... And just for the curiosity connected it to the computer and tried downloading ROM one more time. And it succeeded - I'll upload the ROM once I get access to faster internet connection. I've removed the battery (phone was stuck in Preloader mode because I cancelled ongoing RAM test.), put it back and now everything works.
So, it looks like everything is fine now, however I'd love to know what happened, if you have any clue, please let me know!
Click to expand...
Click to collapse
hello,
could you please upload somewhere original fw for Evolveo Strongphone Q4. im in bootloop now
Hi all,
can you hel me with strongphone Q4, do you know any better rom for this phone?
Maybe by PM in czech? ...

[Q] [Help] S3 GT-I9300 charging problem.

Hello Devs,
I have problem charging my s3 international version.
My phone is rooted and running custom rom s5 sensation v4.0 kitkat 4.4.2 with boeffla kernel v6.0 and latest CWM touch recovery.
I have flashed many custom roms before and all was working good before. The phone was also charging properly before.
But after some time when 4.3 was released I have flashed s4 revolution.
After flashing that rom my problem started.
1st problem was the phone was not gettin connected to my cell tower. Later after searching soo many hours on google I found out that it changed the efs version from v1 to v2. So I found out a rescue zip file which include only modem of xxemg4. I flashed it and then all was working good.
After some time I faced a problem of reverse charging means the phone is kept on charge but instead of charging the battery decrease. So again I searched on google about my problem and found out an app called galaxy charging current which show the power that is getting the phone while its connected to the charger. when I installed it and saw the current it was only showing max 100 min 999 and avg 100. I saw some where that the default current the phone should get is 1000 in max.
I searched alot on google on how to solve this problem, tried many diffrent rom , tried changing my charger, tried to flash back the previous rom which I was using in which I was not having any problem but after doing all this the result was same.
when I connect to the charger it shows 700 In max n after some time it keeps going down like 500 then 300 then last 100.
So after searching on google I have found out a solution of flashing custom kernel. I flashed googymax kernel in which using sTweak we can configure the battery power and ignore safety measures and unstable power.
After doing that my phone gets max 1000 min 1000 and avg 999.
My problem is that when ever I flash new rom I hav to flash custom kernel to ignore the unstable power and safety measures to properly charge my phone.
is there any way I can get back as before I was charging my phone without flashing custom kernel...???
Any answer will be appreciated.
Note :- I was using the original charger which I got in the box while purchasing.
First replace your battery, charger and lead, then flash full stock firmware with Odin.
What happens when you attempt to charge the phone completely off. Do you see the charging graphic?
If something is wrong with the micro-USB port then a wireless charging solution might be your only option.
You could try reloading the firmware using the Kies software on your PC - here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Thnaks for your rply
boomboomer said:
First replace your battery, charger and lead, then flash full stock firmware with Odin.
Click to expand...
Click to collapse
1st of all thanks for replying on my query.
As u stated to change the battery, Charger, Lead and to full flash stock firmware.
I already did that.
I have tried my friends battery with his charger ( not the 1 which come in box ).
but then also its the same.
Whats the problem in it.
Is it a software fault or hardware fault....???
Hermosa said:
What happens when you attempt to charge the phone completely off. Do you see the charging graphic?
If something is wrong with the micro-USB port then a wireless charging solution might be your only option.
You could try reloading the firmware using the Kies software on your PC - here's an overview of what to do:
- if you don't already have the Kies software installed on your PC, download it (just search Google) and install it. The first time it runs it'll update itself to the latest version so make sure you run it once before proceeding.
- put your phone in Download mode: with the phone completely off, press and hold the Volume Down and Home and Power buttons simultaneously, and release them all when you see the Samsung splash screen
- connect the phone to your PC with the USB cable that came with the phone
-- if you've never had the phone connected to your Windows-based computer before, you'll see messages about installing drivers, etc - just wait until this is done (may take 5 or 10 minutes) [I don't know what happens if you have a Mac - it probably just works]
- in the Kies software, select the second item in the Tools menu and just follow the prompts to enter the model number (in CAPS) and IMEI/Serial Number (both found under the battery - it's ok to remove the battery at this point)
- the Kies software should start downloading the correct firmware for your phone from the Internet; once that's done (depending on your Internet connection speed) it'll begin downloading that to the phone (this probably takes 10 minutes or so)
Click to expand...
Click to collapse
Thanks for the reply.
When I try to charge my phone when completely off, 1st it was showing me the graphics of battery charging when I was using 4.3 Custom Rom. But since I flashed my phone with 4.4 Custom Rom, I can't see the graphics of charging battery now.
As per your overview above I have tried all the possible ways to get back charging work properly ( your overview was also included in it ) but I dont get any success in it.
Now I have to compulsory flash custom kernel which supports the options of ignoring unstable power and safety measures.
But then also I will try to do what you told me.
Once again thanks.

Xperia Z2 stuck in bootloop with generic android / cyanogen runs without problems..

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)

Categories

Resources