Yesterday I bought a brand new Xperia Mini Pro. Being used to CM7 on my old phone I immediately unlocked the bootloader and flashed the fixed boot.img
The system boots up fine but I'm experiencing random hard freezes. The phone doesn't react to anything and can only be powered on again by removing the battery! It never happened to my while the screen was on, only when the phone was in my pocket or just lying on the table.
This is very annoying, given the fact the phone is brand new. I'm on the latest original firmware 4.0.A.2.368 posted by DooMLoRD including his boot.img and unlocked bootloader.
Does anyone suffer from the same problem? Any suggestions?
Thanks
got the same fone, same fw, same kernel and works like a charm.
Did you wipe cache, dalvik-cache and reset to factory defaults during flashing sometime?
If not this could be a solution, but wipes all your data, like the word tells
I always checked "Wipe User Data" when flashing via FlashTool. Does this include cache and dalvik-cache as well?
This also happens without SIM-card inserted, so I guess it's not radio related.
It never happened to me while playing music or while charging!
I contacted SE support, they told me to send it back.
I'll relock my bootloader and try to repair once again, but I probably have to send it back afterwards.
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)
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
hackkpo said:
Im Argentinean first of all and I'd bought my new GS2 3 days ago on mercadolibre.com.ar (a site like ebay.com) to a guy that imports it from factory. After of almost 50 days of waiting, i did got my new mobile phone, when i got it i'd upgraded to JellyBean with the official samsung rom, and that's when the problems showed up, the top left corner come overheat turning off the device, over and over again. So after some failed testing I'd chosed to change the kernel to Siyah expecting some performance improve but it become kind of worst because when the screen blackout the device just reboot itself, but if i keep doing something on it nothing happens, just when the screen comes black.
So i guessed that it may was related to the kernel, so downloaded another official rom jelly bean, this one was a Pre-Release rom, that some time ago i'd installed on a friend's galaxy s2 and it worked fine (despite the increased battery drain). This wasn't any solution though, because it keeps rebooting when the screen comes black.
I did tested to turning on without the simcard and microsd card, with the same results.
Another fact is that if i left the music playing and turn of the screen with the power button, nothing happens, it works perfectly.
It seems that is some kind of trigger when the mobile actually suspend itself doing really nothing.
Now i dont know what to do, should i test some custome rom/kernel?? should i get the chances to use the warranty? (implies to send again the device to china i guess ¬¬)
Please help, and thanks in advance.
Click to expand...
Click to collapse
You should try custom rom. Try to Flash Neatrom or any stock custom rom.
Hope it solves your problem.
Sent from my iPhone using Tapatalk
Firstly, you need to verify that it's a genuine S2. Turn the phone off, take the battery out and post on here EXACTLY what you see on the sticker in the battery compartment.... Just don't post the IMEI number...
Sent from my GT-I9100 using xda app-developers app
Model: GT-I9100
SSN: -I9100GSMH
RATED: 3.7V ------- : 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
IMEI: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
S/N: R5XA73828F1
That's all, its seems original, right?
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
hackkpo said:
i'd just installed the last samsung official Rom, form nordic countrys, and it seems to work just fine. I'll keep updated if it goes wrong again. Im so happy.
EDIT: Ok so i just leave it chargin the battery and it reboot itself 3 times again and 1 time just it turned off. I didnt tried leave it without the charger because it didnt have any charge. So im in trouble again >.<
Click to expand...
Click to collapse
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Jeetu said:
Go to recovery and do wipe data/ factory restet and wipe cache . Reboot . Phone will start working again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
hackkpo said:
Ok since that post i'd installed cyanogenmod 10.1.3 with JB 4.2.2 and it rebooted itself like 4 times and finally it keeped on like 10 minutes now.
Click to expand...
Click to collapse
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Jeetu said:
Yes do the same what i posted above and then flash your rom again.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Why would i reflash again? i dont get it
hackkpo said:
Why would i reflash again? i dont get it
Click to expand...
Click to collapse
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Jeetu said:
Because your phone is now in Bootloop.
Bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence.
Think of system apps that are compiled incorrectly, permissions that are not set correctly, files from other devices and even an init.d script, everything is possible.
To find the cause of a bootloop you have to think about what you did before getting the bootloop.
Choose one of the following reasons that caused the bootloop for you and try out its solution.
– After flashing a new rom
If you flash a new (base)rom on your device it may not automatically wipe your dalvik-cache, This means your old dalvik-cache will be used for the new system files which would result in a bootloop, to fix this problem:
1. Start your phone in CWM Recovery
2. Go to Advanced
3. Choose “Wipe dalvik-cache”
4. Now go to “Mounts & Storage”
5. Choose “Wipe /cache”
6. Reboot your phone
Note: by wiping “/cache” and “dalvik-cache” you make sure it’s completely deleted, some roms use /data and some use /cache for the dalvik-cache
If the problems still exists after doing that, you could try to wipe your /data partition. before you do that first make a backup of your phone (in it’s current bootlooping state)
1. Start your phone in CWM Recovery
2. Now go to “Backup & Restore”
3. Choose “backup” (it may also be called “backup to internal/external sdcard)
When that’s done you are free to wipe /data, you can achieve this by doing:
1. Now go to “Mounts & Storage”
2. Choose “Wipe /data”
3. Choose “Wipe /cache”
4. Reboot your phone
If the rom still doesn’t boot correctly it’s probably the rom which isn’t working, contact the rom creator then and try an other rom for the meanwhile.
Click to expand...
Click to collapse
No is not, the cellphone starts normal, and while im using it nothing wear happens, but when i left it the screen goes black and the device reboot itselfs. But now im seeing that doesnt happen anymore, i dont know why.
Still with cyanogenmod rom, i connected the phone to charge the battery, and i saw a tendency of reboots and turnings off while the percentaje comes to 100% and a increasing overheat on the left-top of the phone, i suspect that the problem may be related with the amount of charge from battery and the overheating... Hardware problem?
Well... After all this time my cellphone went through the argentinean official service of samsung and the tech guy told me that he couldn't do anything on my device because he tried installing a lot of samsung official roms and the device was still malfunctioning. So he gave up on it, so i'd tooked it to another service (non official this time) and that guy told me that it may be a non official device, so he wouldnt do nothing on it, because i couldnt get the hardware that possible was malfunctioning. So here im now, with the all money spent for nothing.
My question is, what can i do to know if is or isnt an ORIGINAL samsung device? Knowing that i'll choose how to proceed. Txs!
Phone info:
Sony Xperia Tipo ST21i
Rooted
LOCKED Bootloader
Custom Firmware and Custom Rom: Gimlo
Xposed Framework Installed
Problem:
After my last reboot, phone is stuck at 'SONY' bootlogo. I am able to boot to CWM Recovery. On removing battery, phone would switch on automatically sometimes. But the main problem,, the phone doesn't go past the 'SONY' logo.
Edit: The phone charges(shows red led and the charging icon) on connecting to pc via usb.
'Might Be' Causes:
Everything had been working fine upto yesterday. Yesterday i was cleaning up my phone so..something might have happened yesterday. So all the things i did in chronological order(besides daily routine):
Uninstalled apps- Meme Generator Free, Township
Installed- Wakelock Detector and ran it once
Uninstalled Script- TweakDrypt(using Terminal Emulator)
enabled Xposed module for Greenify(free version)
Reboot!
And the phone has been like this since yesterday.
I haven't flashed any rom or anything..and i don't think it is a hard brick either..So will i have to use the flashtool to flash the stock firmware and rom?( I would like an alternative to preserve my data please!)
Solutions Tried:
→Google searches...only found suggestions regarding flashtool to flash the device stock
→At first, i went to CWM and took a nand backup of 'current state' of the phone. Then, I cleared cache and wiped dalvik cache. Rebooted, still it is stuck.
→Did a soft reset, "Power+volume up" until i get 1 vibration..and then released it..no effect.
→I make weekly nand backups of my phone..so i tried restoring last week's backup. Even then it is stuck! I don't understand why would that happen...
Please help...If i have missed out to mention any detail, please do tell and i will send it.
Sherl Holmes said:
Phone info:
Sony Xperia Tipo ST21i
Rooted
LOCKED Bootloader
Custom Firmware and Custom Rom: Gimlo
Xposed Framework Installed
.......
.
Click to expand...
Click to collapse
-_-..Could find no solution...Finally flashed stock ****.
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)