Related
1. When i plug my usb cable and transfer files using them,then I turn off usb and unplug it from phone then xperia has black screen and freeze. 2. after batery calibration (I think) on every restart or shutdown my phone freeze on cyanogen mod 7 animation and not happened,but somethimes when touch my screen then appear pin and keyboard. Sorry for my english. has enyone know to fix it? i do full wipe
What ROM and wich version do you use?
And you tried do a full wipe?
cust0m said:
What ROM and wich version do you use?
And you tried do a full wipe?
Click to expand...
Click to collapse
dude..cant u see his title?he using a ROM called GingerDX..
@scorpion 21:
have u try full wipe?coz mine just working fine..
Using GingerDx i do full wipe that problem i had with froyobread too. I mybe some kind of bug
Full-wipe is not the answer to anything people!
Hey guys,
i got the same problem.
I tried to run the following rom on my phone: http://forum.xda-developers.com/showthread.php?t=1188486 (latest version v009) and after i "installed" the rom, it wont start in the right way.
The phone is always freezing on the cyanogen mod 7 screen...
I got the same problem on the froyobread release too ;/
Maybe there s someone who know how to fix it?
The problem was for me too. But when I connected phone, not only it turned black, it rebooted and i saw bootanimation, and that was a loop od 3 times. I fixed it with Manager permissions option, try it, maybe it will be usefull, I don't know.
May be because you use a theme which is installed on sd card.
Sent from my X8 using XDA App
Can someyone tell that to doxianh?
I found how to fix black screen on usb only: when connect your phone (turn on storage function) transver files and do what you want,then in windows find your device or sd card right click on it and click ,,eject'' then on phone press ,,turn off usb storage'' and then just remove cable and screen will be automatically loaded try
scorpion 21 said:
I found how to fix black screen on usb only: when connect your phone (turn on storage function) transver files and do what you want,then in windows find your device or sd card right click on it and click ,,eject'' then on phone press ,,turn off usb storage'' and then just remove cable and screen will be automatically loaded try
Click to expand...
Click to collapse
You must always click eject whenever disconnecting any kind of external storage (sd, usb...)
I know that,but if I press back button when cable is connected everything freeze
Full wipe and battery reset solved my problem ;=)
hi, i have a problem: I use gingerdx 009 and sometimes it ask me for PIN unlock operator; i click "exit" and the x8 starts normally.. why?
Thats hapens to me because we have moded xperia to work on 1 mobile operator but rom like gingerDX support it much more just ignore thst
Sent from my X8 using XDA App
When I just installed the GingerDX ROM I had the freeze on animation problem, and it gones with a full-wipe just after the reinstallation of the ROM, you might try install the custom zip and do a full wipe before restart from xrecovery
for the USB problem, as the last post, you have to use safe eject before turn off USB massibe storage from the phone
I rebooted my Samsung Galaxy S I9000 today and got a bootloop.
(I wasn't messing with firmare or smth, it was low on memory and clearing doesn't help so I decided to reboot it)
When I try to enter recovery mode I am getting the same bootloop.
The only thing that I can do is to enter download mode.
But no driver is working for me so Odin can't see the phone.
The firmware is Andy Thomson's ICS (version prior to 2.8.10, one ore two earlier, I can't remember precisely) with Mackay kernel.
I've tried countless number of drivers on Win7 х64 and XP 32 and it's still "Unknown device".
I've tried Samsung drivers extracted from KIES (including latest 1.5.9.0)
I found some hacked versions that said to be specially modified for win7-64 and ICS roms
I tried to extract drives from Heimdall - no luck with that too
I installed the Android SDK and USB drivers from it
All of above didn't help
Any suggestions?
Gloosy said:
Any suggestions?
Click to expand...
Click to collapse
try the procedures and solution on My Android Solutions link below
xsenman said:
try the procedures and solution on My Android Solutions link below
Click to expand...
Click to collapse
Holding power button without battery solved my problem with non-detecting device. When I connected it to computer, the drivers were automatically installed and now Odin can see my phone. (But without picture and the com port is on yellow background if it means something) That's at least something, thanks!
But flashing pit or kernel or pit with kernel (as in your instructions about bootloops) doesn't help. I still got a bootloop and the picture on boot is still from Mackay kernel despite i've flashed it with semaphore and didn't see any errors in Odin while flashing.
Still cant get to recovery mode (tried different combinations from your faq)
Gloosy said:
Holding power button without battery solved my problem with non-detecting device. When I connected it to computer, the drivers were automatically installed and now Odin can see my phone. (But without picture and the com port is on yellow background if it means something) That's at least something, thanks!
But flashing pit or kernel or pit with kernel (as in your instructions about bootloops) doesn't help. I still got a bootloop and the picture on boot is still from Mackay kernel despite i've flashed it with semaphore and didn't see any errors in Odin while flashing.
Still cant get to recovery mode (tried different combinations from your faq)
Click to expand...
Click to collapse
get into download mode and flash a JPU ROM plus Semaphore of CF root to recover
Gloosy said:
I rebooted my Samsung Galaxy S I9000 today and got a bootloop.
(I wasn't messing with firmare or smth, it was low on memory and clearing doesn't help so I decided to reboot it)
When I try to enter recovery mode I am getting the same bootloop.
The only thing that I can do is to enter download mode.
But no driver is working for me so Odin can't see the phone.
The firmware is Andy Thomson's ICS (version prior to 2.8.10, one ore two earlier, I can't remember precisely) with Mackay kernel.
I've tried countless number of drivers on Win7 х64 and XP 32 and it's still "Unknown device".
I've tried Samsung drivers extracted from KIES (including latest 1.5.9.0)
I found some hacked versions that said to be specially modified for win7-64 and ICS roms
I tried to extract drives from Heimdall - no luck with that too
I installed the Android SDK and USB drivers from it
All of above didn't help
Any suggestions?
Click to expand...
Click to collapse
have you tried installing the whole Kies? Because that solved my problem when I experianced your problem.
Jayfunk said:
have you tried installing the whole Kies? Because that solved my problem when I experianced your problem.
Click to expand...
Click to collapse
Thanks, but that part of the problem was already solved earlier in the thread.
But I did install Kies before that and it didn't help.
xsenman said:
get into download mode and flash a JPU ROM plus Semaphore of CF root to recover
Click to expand...
Click to collapse
Thanks, but I've already reflashed stock and Jelly Bean after that. Everything's ok now except that I hoped to solve it less radically.
Hi there, same thing happened to me (except my phone was low on battery so it was shutting down. Bootloop now)
As i have a charging-screen loop, i dunno if my phone is really charging or not. should i just wait one hour or so be4 i start flashing it with odin?
dont wanna flash my phone with 5% battery ..
Goerni said:
Hi there, same thing happened to me (except my phone was low on battery so it was shutting down. Bootloop now)
As i have a charging-screen loop, i dunno if my phone is really charging or not. should i just wait one hour or so be4 i start flashing it with odin?
dont wanna flash my phone with 5% battery ..
Click to expand...
Click to collapse
Never Flash Phone with low Battery Charge, use external charger to charge Battery First to full, if possible
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
thanks 4 your fast reply!
xsenman said:
First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card....
Click to expand...
Click to collapse
Did that already, and will do that before i flash again.
Since i don't have an external charger, and no device where my battery would fit in, do u know what likely it is, that my battery is charging up?
Goerni said:
thanks 4 your fast reply!
Did that already, and will do that before i flash again.
Since i don't have an external charger, and no device where my battery would fit in, do u know what likely it is, that my battery is charging up?
Click to expand...
Click to collapse
it depends on what is causing the bootloop, If the bootloader is the problem, than it may not charge your phone . so try to power down and try charging, see if you get charging screen on your phone, when phone is "OFF"
Try not to take the risk of flashing with a low battery charge as , nothing would work, if you lose power when flashing botloader or when booting ..see My Android Solutions, scroll down
Hello everyone
my phone was not getting charged, i went to the samsung service and they said me that something's wrong with the battery so i got it replaced today and still the battery is not getting charged !! :| I tired different chargers but still the same problem. My phone is still in warranty and i am going to the samsung service again ! Any idea whats wrong with my phone??
and yeah one more problem, when ever i install a JellyBean custom rom and if i restart the phone its getting stuck on the samsung logo !! I tired flashing roms (Ultimate Jellybean and Angry v3 ) its getting stuck after reboot :| so please if anyones knows whats wrong with my phone, please let me know !!!
Thank You ! :fingers-crossed:
If you really bought a new battery and it's not charging in every charger you tested:
the new battery isn't so new
or
all chargers are broken.
And to your problem with JB:
http://forum.xda-developers.com/showthread.php?t=2075188
In your own thread post 9 with your own answer might help again
ThaiDai said:
If you really bought a new battery and it's not charging in every charger you tested:
the new battery isn't so new
or
all chargers are broken.
And to your problem with JB:
http://forum.xda-developers.com/showthread.php?t=2075188
In your own thread post 9 with your own answer might help again
Click to expand...
Click to collapse
i bought the battery from the samsung store, I guess its a new :\ about the chargers i have a s2 as well and its charging perfectly with the same chargers
thanks, ill check out the thread
ThaiDai said:
And to your problem with JB:
http://forum.xda-developers.com/showthread.php?t=2075188
In your own thread post 9 with your own answer might help again
Click to expand...
Click to collapse
Oops, i created that thread and forgot about it Sorry my bad
i know how to go back to ics now , but i want Jellybean. Thats y i flashed JB again and im getting the same problem :\ can anyone say me how to fix that ?
xp3rto said:
Oops, i created that thread and forgot about it Sorry my bad
i know how to go back to ics now , but i want Jellybean. Thats y i flashed JB again and im getting the same problem :\ can anyone say me how to fix that ?
Click to expand...
Click to collapse
are you able to use you USB port/cable at all? can you connect the pc to the phone ?
if not; Id say your usbport is borked.
Anthropostar said:
are you able to use you USB port/cable at all? can you connect the pc to the phone ?
if not; Id say your usbport is borked.
Click to expand...
Click to collapse
Yeah i'm able to connect the phone to the pc
xp3rto said:
Yeah i'm able to connect the phone to the pc
Click to expand...
Click to collapse
k, so and JB roms are getting stuck at boot huh.
what i would do:
I'd say
->fire up Odin, flash a kernel that includes CWM. (dunno what kernel youve been using, but lets start all over)
->Reboot -> reboot into (cwm) recovery, and flash the superuser (SU) package again.
#-If all that succeeded (you are now properly rooted);
->in CWM make a backup.
->flash a CM 10.1 kernel
->flash any JB (4.2) rom.
#-Once all that succeeded, reboot.
->If your JB rom loads succesfully hopefully youll see your device charging.
->If not, reboot into recovery again, make sure your device has been plugged in long enough to have loaded the battery (maybe not shown in stats).
-> in CWM choose Clear battery stats.
Thats what i'd do.
Anthropostar said:
k, so and JB roms are getting stuck at boot huh.
what i would do:
I'd say
->fire up Odin, flash a kernel that includes CWM. (dunno what kernel youve been using, but lets start all over)
->Reboot -> reboot into (cwm) recovery, and flash the superuser (SU) package again.
#-If all that succeeded (you are now properly rooted);
->in CWM make a backup.
->flash a CM 10.1 kernel
->flash any JB (4.2) rom.
#-Once all that succeeded, reboot.
->If your JB rom loads succesfully hopefully youll see your device charging.
->If not, reboot into recovery again, make sure your device has been plugged in long enough to have loaded the battery (maybe not shown in stats).
-> in CWM choose Clear battery stats.
Thats what i'd do.
Click to expand...
Click to collapse
Ill give this a try and let you know
Anthropostar said:
k, so and JB roms are getting stuck at boot huh.
what i would do:
I'd say
->fire up Odin, flash a kernel that includes CWM. (dunno what kernel youve been using, but lets start all over)
->Reboot -> reboot into (cwm) recovery, and flash the superuser (SU) package again.
#-If all that succeeded (you are now properly rooted);
->in CWM make a backup.
->flash a CM 10.1 kernel
->flash any JB (4.2) rom.
#-Once all that succeeded, reboot.
->If your JB rom loads succesfully hopefully youll see your device charging.
->If not, reboot into recovery again, make sure your device has been plugged in long enough to have loaded the battery (maybe not shown in stats).
-> in CWM choose Clear battery stats
Thats what i'd do.
Click to expand...
Click to collapse
Im not able to install the JB rom :| My phone restarts when the installation is about to complete.
ThaiDai said:
If you really bought a new battery and it's not charging in every charger you tested:
the new battery isn't so new
or
all chargers are broken.
And to your problem with JB:
http://forum.xda-developers.com/showthread.php?t=2075188
In your own thread post 9 with your own answer might help again
Click to expand...
Click to collapse
I bought a new charger today and my phone is charging Thanks
Hello everybody, this is the situation:
Phone model:Samsung Galaxy S3 mini I8190
ROM version:maclaw cm10.2
what i did:
used cm10.2 for the last months, installed a new nightly now and then (thanks to novafusion team ), everything worked fine.
i switched to cm11 yesterday and installed it as i did the nightlys before, without wiping dalvik or reinstalling gapps or something like that.
a few apps went missing and i could not open the rom manager app which i used to reboot into recovery mode (explanation later).
also the play store was saying connection error so it did not work. when i installed an app from the f-droid store i ended up in cwm where i thought maybe with the old cm10.2 installed again the play store would work again and i could figure out how to handle everything. installed it again, also installed gapps, remembered to do dalvik wipe and now i am stuck with the cm loading logo on my screen. reboots dont change it.
three weeks ago the phone got wet, was dried in rice very fast battery out etc but it still did never recognize a plugged in headphone again, so there must be some damage.
all the buttons worked fine thought while it was turned on.
my big problem now is that while its turned off i cant get into download mode or recovery mode with (vol-down home power) and (vol-up home power). it only turns on as if i only pressed the power button.
is there anything possible? i really liked this phone but maybe its time to move on!?
thanks for any help i know it is 100% my fault and i am pretty stupid but well now its done ;P
You went from JB to KK which means new android version, so factory reset is a good start and you will also need new gapps for KITKAT.
Have you tried to install adb and samsung usb drivers? Maybe you can reach the phone from there even if it's stuck at boot.
Code:
adb reboot download
or
Code:
adb reboot recovery
For adb and drivers just search xda.
tys0n said:
Have you tried to install adb and samsung usb drivers?
Click to expand...
Click to collapse
Yes i just tried. first installed samsung drivers started adb and connected phone. win 7 (64bit) searches for drivers after the phone is connected, the first time it said I8190 driver and mtp driver installing but mtp failed. if i plug it back in now it only looks for mtp driver and fails.
adb says "list of devices attached" if i do adb devices but since it does not attach any devices i guess it does not recognize it?
if i use the "adb reboot download" command it obviously says device not found. so...
btw i just figured out that while starting the win 7 starts looking for a U8500 USB ROM driver if i only plug the phone in and the maclaw charging logo pops up. also fails though. the U8500 USB ROM is disconnected after 2 seconds says the device manager.
thanks for helping and have a nice day!
Did you enable usb debug on your phone, in /settings/developer options ?
tys0n said:
Did you enable usb debug on your phone, in /settings/developer options ?
Click to expand...
Click to collapse
not manually, as far as i can remember...
well its too late now
Ultralord1 said:
not manually, as far as i can remember...
well its too late now
Click to expand...
Click to collapse
Yeah I guess so. Without buttons or adb it will be pretty much impossible.
One last idea. Get a USB jig to see if you can force it to download mode, and then reflash thru Odin. They cost about 1usd on eBay :thumbup:
Otherwise open it and try to fix buttons.
Sent through time and space from my s3mini/CM11
tys0n said:
Yeah I guess so. Without buttons or adb it will be pretty much impossible.
One last idea. Get a USB jig to see if you can force it to download mode, and then reflash thru Odin. They cost about 1usd on eBay :thumbup:
Otherwise open it and try to fix buttons.
Sent through time and space from my s3mini/CM11
Click to expand...
Click to collapse
yeah i will probably order a usb jig.
its weird with the buttons because i am sure that they work. when the os was working the buttons were working while it was turned on (100% sure and no problems while on), but i could already not get into recovery and download mode.
that does not sound like a hardware problem to me :/
Hello everyone, I have an update and need your help again, just to make sure what to do next, I don't want to screw things up again
I ordered usb jig, but the phone was completely dead when it arrived. So I opened it up and cleaned all the corrosion from the water away, still dead.
I bought a phone with broken display on ebay now, which was 40€, put the working parts of both phones together and now I have a fully working s3 mini again!
Fully working? Still stock rom on here... We don't want that!
My only question is which cyanogenmod do you think is the best one to use on a daily basis? I want to use maclaws cm11 but I am not sure which one to take, hes got new ones every day...
Thanks for all the help
Bruno
It's not my first time to flashing roms. But this time i think phone dead. Here is the story: I installed cm12 and wipe system flash cm 14 adn finally today i flashed cm13 and i loved it. But when i opened file explorer i see internal storage is 2gb(before flashing it is 10gb). When i opened TWRP 3.0.2 i see another legacy sd partition. I think if i will format this partition i can get 10gb internal storage back. And i formatted legacy sd using twrp. But when i push reboot system now phone turned off and never go back. no any red or green light. I'm sure phone have min 50% charge and battery new(not battery problem). I tried remove battery but it is not work. When connect it to pc see this on bottom right corner ''QHSUSB_DLOAD'' and no driver found and no any light on phone. What can i do now? Flash tool and Emma dont recognize device.
Elshan_Nurmammadov said:
It's not my first time to flashing roms. But this time i think phone dead. Here is the story: I installed cm12 and wipe system flash cm 14 adn finally today i flashed cm13 and i loved it. But when i opened file explorer i see internal storage is 2gb(before flashing it is 10gb). When i opened TWRP 3.0.2 i see another legacy sd partition. I think if i will format this partition i can get 10gb internal storage back. And i formatted legacy sd using twrp. But when i push reboot system now phone turned off and never go back. no any red or green light. I'm sure phone have min 50% charge and battery new(not battery problem). I tried remove battery but it is not work. When connect it to pc see this on bottom right corner ''QHSUSB_DLOAD'' and no driver found and no any light on phone. What can i do now? Flash tool and Emma dont recognize device.
Click to expand...
Click to collapse
Hi! i have de same problem right know... i format de lagacy sd and now is bricked like your phone.
Did you solve IT?
Hi. Generally when the phone doesn't respond, you had to consider it hard bricked, and there's no solution that you can apply without putting the hands on the Hardware. My advice is to try let it charging for 24+ hours and see if something happens. For example if the led turns on, probably you are in soft brick and you can bring it back to life. There's a tread here in XDA explaining the importance of charging cycles for the late 2012 Sony devices.
In my case I couldn't flash nothing on xperia T until I haven't let it charging for 25 hours straight. Then I was able to bring it back to life.
Hope you can do the same. In any case, good luck.
I might be reckoning wrong, but I believe I've recovered my T several times using stock firmware in such case.. Then go again with CM or whatever.
landerxxx said:
Hi! i have de same problem right know... i format de lagacy sd and now is bricked like your phone.
Did you solve IT?
Click to expand...
Click to collapse
MaliSimo said:
Hi. Generally when the phone doesn't respond, you had to consider it hard bricked, and there's no solution that you can apply without putting the hands on the Hardware. My advice is to tryif something happens. For example if the led turns on, probably you are in soft brick and you can bring it back to life. There's a tread here in XDA explaining the importance of charging cycles for the late 2012 Sony devices.
In my case I couldn't flash nothing on xperia T until I haven't let it charging for 25 hours straight. Then I was able to bring it back to life.
Hope you can do the same. In any case, good luck.
Click to expand...
Click to collapse
after+ 12hr of charging i see blinked red every 2 mint .... what can ido for this ??plz help sorry for bad english
Sorry for the late reply. Its a good sign, so now you know your phone its not hard bricked. There's hope!!! Let it charge for other 12+ hours and you should see the blinking red led becoming continuous. Then you could try flashing a kernel and a custom recovery, if it works you can try flashing a ROM. Alternatively you can try to flash a stock ROM via flashtool.
Anyway now you know the phone it's alive, keep trying and you will able to bring it back to life.
Many thanks for you pro.... but usb not recognized or appear like "Qualcomm driver ..any advice ....any way I could leave it in charger and try again....Thanks for ur reply...
Maybe you can try, if you didn't already, to install the latest Sony flashtool, browse the installation folder, search for drivers and use the installation tool to reinstall the blue board 3 drivers (if you are using win 10 you may need to disable the driver signature to install the drivers properly).
I got the same problem with my Xpetia T, here I will report the steps I followed:
1. The phone didn't respond to any command, even to hard reset (pressing power button and volume + for 10s until you don't feel 3 vibrations, not recommended to do that, but I was a little frustrated).
2. I let it charging for a bit then I tried to flash a stock ftf file ( Installing the drivers just how I explained at the beginning) via flashtool. I managed to put the phone in flash mode but the procedure failed when the program started to flash the system file.
3. So I let it charge for 25h: in the first 5h no led showed up, then blinking red led, then continuous red led and finally continuous green led.
4. After that I retried to flash a stock ROM via flash tool but the procedure failed again when it was flashing the file system.
5. So I made a desperate try: I flashed all partitions but system via flash tool, then I extracted the system partition opening the ftf file with a zip manager and I used the fastboot functionality in flashtool to flash the system partition.
6. After I did that, I didn't see any improvement and I decided to put the phone in charge again and..... The kernel battery charging symbol appeared!!!
7. I let the phone charge over night then I booted it up! He booted in provisory mode and I managed to turn on USB debug and I gave permissions to my PC.
8. Then I installed TWRP via adb and so Linage 14.1 custom ROM.
The only problem I found it's my battery is practically dead, so I will try to replace it by my self in near future (this phone as known battery issues)
This is the method I followed, I don't know if is equally good for your case but I Hope this steps somehow help you.