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!
Hi there,
So I was on Skype to my friend on my i9300, running stock 4.3, rooted, with yank555 kernel and with PhilZ 5 recovery. All these modifications were done about four weeks ago and the phone has served me perfectly well until today.
The flashing Samsung logo that comes up just before the phone boots appeared and the keys stayed lit, when nothing happened for a minute, I held the power button until it reset. Next, the phone took a good two or three minutes to boot and seemed to have forgotten all the information I inputted into it. I still had most of my apps but all the sign in information was gone and all the Google Apps had to reinstall themselves.
There seems to be no cause for the break down, and I don't have a recent backup as I haven't planned to flash anything until 4.4 is officially released. Does anybody know what could have caused this or if there is a way to recover my data?
Cheers.
Unplanned system shut down can partition corruption, reasons for it can be various -battery voltage suddenly dipped, kernel panic etc.
Data on your internal sd should still be there, as on the external sd. Anything else will be gone as it sounds like your data got wiped.
This is a year-old Galaxy S3 i9300 (Intl) which came with a stock 4.something, which I replaced after a couple of months with CM10. After that, I've tried plenty of different ROMs, but I mostly stuck with CM. There were often problems with some apps FCing and plenty of random reboots, but it was still mostly usable. Until recently, that is.
After a few more updates with the more recent CM11 builds, the phone just went into this boot loop that seems to trigger around the 1 minute mark regardless of what mode the phone is in. In most cases it's the CM11 boot animation, but even if I manage to get it into recovery or download mode, it still reboots. As a result, I'm unable to perform any repair via recovery (no fix permissions or wipe) and I can't get it to stay in download mode to send a different image.
Is this a hardware issue or something that can be fixed via software?
aalaap said:
This is a year-old Galaxy S3 i9300 (Intl) which came with a stock 4.something, which I replaced after a couple of months with CM10. After that, I've tried plenty of different ROMs, but I mostly stuck with CM. There were often problems with some apps FCing and plenty of random reboots, but it was still mostly usable. Until recently, that is.
After a few more updates with the more recent CM11 builds, the phone just went into this boot loop that seems to trigger around the 1 minute mark regardless of what mode the phone is in. In most cases it's the CM11 boot animation, but even if I manage to get it into recovery or download mode, it still reboots. As a result, I'm unable to perform any repair via recovery (no fix permissions or wipe) and I can't get it to stay in download mode to send a different image.
Is this a hardware issue or something that can be fixed via software?
Click to expand...
Click to collapse
If it reboots in recovery and download mode then it sounds like a hardware issue to me most probably your power button is the cause.
tallman43 said:
If it reboots in recovery and download mode then it sounds like a hardware issue to me most probably your power button is the cause.
Click to expand...
Click to collapse
I guess :-/
I did read several other boot loop issue posts, but most of them only reboot when the OS is booting, not recovery or download. The ones that have a 'global' boot loop issue are usually much shorter (3 sec or so) and can sometimes get it to stay by removing the memory card or just keeping it off for 5-10 minutes. None of thes things worked for me.
I have three Samsung phones with hardware issues - the i9300, the i9250 and the i9020 - which I'll take to the service center now.
:highfive:
Hi guys!
It is a bit crazy story so I will give you some details about it ...
I have an Ace 3 Duos GT-S7272 crazy device. I used to have so many issues with it but managed to solve it such as when I encrypted the external SDcard and it was the stupidest thing to do in an Android (cause it didn't actually encrypt a shi*) it just caused my phone to stuck in a bootloop as long as any SDcard is in it, remove it and all will work fine
- ((I somehow managed to fix it and it worked with SDcard but it used to reboot once then on the second boot it was almost perfect!))
- one day out of a sudden, stuck in a strange bootloop!! it boots fine to the startup and I can use it normally for 2 to 4 seconds and it REBOOTS again and again!
- I wiped cache didn't work ,,, still bootlooping
- I tried Safe Mode the same bootlooping
- I am leaving the Factory Reset option as my last resort and I am seeking your help guys so I don't lose my really important information on it !
- it is rooted ((but as I googled around I get the stock menu of Vup+M+power))
- I don't have a back up ((I have bad experiences with Backups))
- I strongly think that it can be saved without losing my information, cause it starts up normally for few seconds ((2 to 4)) and I could change things like Airplane Mode on/off
I really appreciate any help guys,,, I have been googling for days about this
I rooted my S6 Edge a couple of days ago with no problems. I later added xposed and a couple of modules, no problem (apart from swipeback needing removed after it disabled my camera/gallery). Last night I shut my phone down and put it on the charge for the night. Today after turning it on it was stuck in a boot loop. I have been searching for fixes but there seem to be many different scenarios. I have tried to boot to recovery multiple times to do a wipe partition cache as that seems to the general fix. Problem is I am only able to get into TWRP. So I tried to do a default wipe with TWRP (Says wipes Data, Cache, and Delvik (not including internal storage) ). My phone now only boots to logo before shutting back off. I assume anyway because it isn't boot looping anymore and holding the power button gets the same result, logo then black screen again.
I am able to get into TWRP menu though I should add just about any option I choose, after it executes/completes the phone freezes and needs to be forced off/restarted. It has done this since TWRP was installed.
I am also able to get to ODIN mode.
If I remember correctly it is the G925F Global model. Running 6.0.1 stock, rooted using SpaceX kernal.
This is the process I used to root: edit: Seems I cannot link until I have at least 10 posts. How to Root Galaxy S6/S6 Edge on Android 6.0.1 Marshmallow!
BY MAX LEE google that and top result should be the site I used.
Any help would be greatly appreciated. If you would need anymore info I will gladly do my best to give it. I would like to fix this without losing all my data, apps pics music etc. But if all else fails I am prepared for that.