I've been running ICS for about two weeks without a problem. I just flashed the 5/4/12 ICS build today and it also seemed to work fine. I noticed that I still could not access the phone via USB. To determine whether it was a phone or PC problem I restored the DINC from my last Gingerbread backup. When I cleared the phone and restored my current ICS backup the phone boots to the splashscreen and freezes. I tried a fresh install of the ICS build, but it still freezes at the splashscreen. Any ideas or suggestions? I'm currently running my last Gingerbread backup for now, but really want to get back to ICS.
rhazzon said:
I've been running ICS for about two weeks without a problem. I just flashed the 5/4/12 ICS build today and it also seemed to work fine. I noticed that I still could not access the phone via USB. To determine whether it was a phone or PC problem I restored the DINC from my last Gingerbread backup. When I cleared the phone and restored my current ICS backup the phone boots to the splashscreen and freezes. I tried a fresh install of the ICS build, but it still freezes at the splashscreen. Any ideas or suggestions? I'm currently running my last Gingerbread backup for now, but really want to get back to ICS.
Click to expand...
Click to collapse
hi which ICS rom?
Shano56 said:
hi which ICS rom?
Click to expand...
Click to collapse
I think he's talking about miui 5.4.12, I've been having a ridiculous problem trying to get it to boot as well.
Sent from my ADR6300 using XDA
Related
I'm currently using Cm7. I just rooted it tonight and I'm currently not being able to receive txts. I rooted using Revoked and clockwork recovery.
Did I root wrong? I tried wiping and reflashing different wrongs. I also tried downloading different Messaging apps such as: ChompSms and Handcent, still no luck. Please help
Did you update all radio/WiMAX/PRI/NV?
I'm having the same issue. I was running the latest Calukin rom (which has sense) and all of the sudden it stopped, I uninstalled all my apps, nothing, I flashed to mikfroyo, nothing. Updated my prl and profile, nothing.
I experienced a similar issue switching from one CM7 nightly to another, I forget which I was upgrading from/to. To resolve the issue, I restored the nandroid backup of the last working ROM I had, verified things were working again, and reflashed the latest nightly from there. Good luck, hope this helps...
Brian
brianw7761 said:
I experienced a similar issue switching from one CM7 nightly to another, I forget which I was upgrading from/to. To resolve the issue, I restored the nandroid backup of the last working ROM I had, verified things were working again, and reflashed the latest nightly from there. Good luck, hope this helps...
Brian
Click to expand...
Click to collapse
not to thread hijack, but I was running a sense rom and it happened suddenly
I'm haven the same issue wit my CM7 nightly build 29...any way on fixing that problem
Sent from my PC36100 using XDA App
Today when i got home i turned on Wifi and suddenly my phone went into a boot loop.. It doesnt get past the "Google" logo at the beginning and just keeps rebooting every 5 seconds.. I have tried doing a hardreset restoring to factory settings but that didnt work.. It is rooted.
Can anyone help me fix this?:/
What Rom/Kernel are you on? Can you get it into download mode? Have you tried restoring a Nandroid? Have you tried a fresh install?
I had the CM9 3/29 nightly running. Had the phone in desktop mode all night. This morning it started rebooting after coming to the home screen, and then situation is getting worse, it reboots after every boot. I had a good CM9 nandroid back up, restored and still doing the same thing.
CM9 nightly, no separate kernel, just some tweaks and was @1350 under performance.
Can there be some hardware damage?
Help please!!
---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------
Phyxius said:
Today when i got home i turned on Wifi and suddenly my phone went into a boot loop.. It doesnt get past the "Google" logo at the beginning and just keeps rebooting every 5 seconds.. I have tried doing a hardreset restoring to factory settings but that didnt work.. It is rooted.
Can anyone help me fix this?:/
Click to expand...
Click to collapse
Was your phone continuously on, and got hot by any chance?
Don't run performance governor. Also just do a full wipe system and data and flash a known stable CM9 build. That should get you up and running.
Sdobron said:
Don't run performance governor. Also just do a full wipe system and data and flash a known stable CM9 build. That should get you up and running.
Click to expand...
Click to collapse
Done, no go there. One thing I am noticing is a "pop" sound just before it reboots
This happened to me 2 months ago. The way I fixed it was by putting it into download mode and flashing 4.0.1 YAKJU via the ODIN file found on the Samsung German website. Phone has been good ever since. *knock on wood*
EDIT: BTW, after that, I updated to 4.0.2 OTA normally, and since then, I've been manually updating because I rooted my phone.
Sent from my Galaxy Nexus using XDA App
wiki_warren said:
This happened to me 2 months ago. The way I fixed it was by putting it into download mode and flashing 4.0.1 YAKJU via the ODIN file found on the Samsung German website. Phone has been good ever since. *knock on wood*
EDIT: BTW, after that, I updated to 4.0.2 OTA normally, and since then, I've been manually updating because I rooted my phone.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes thats the only way to do it.
Installed the rootkit 5.6 and downloaded the 4.0.4 into the corresponding folder.
Sure wiped my phone completely, but I don't have a $600 paper weight.
Thanks all!
Hi everyone.
I'm having a little problem with my Xperia S, it's kind of new (2 weeks of use).
When I'm using normally the cellphone, everything works great, but if don't use it for a long time and I grab it faster and unlocked it, sometimes the cellphone freezes! Well, not exactly freezing, it still works but VERY slowly, almost like freezing. I can't turn it off with power button, I had to user Power + Volume button to turn it off/restart it.
That happened in first week, so I unlocked bootloader and flash it another kernel (advanced stock kernel), and the problem was there.
Later I made a backup of the firmware (I updated to its last version with PC Companion, ICS btw) and flashed a custom ROM (XTXperience 4), and the problem was still there.
Yesterday I flashed a Generic ICS ROM downloaded from XDA Server using Flashtool, everything went normal until today, when the problem happened again.
I've been searching here in XDA and Google and still nothing seems clear of what is causing the problem, if it's the sim card or maybe a hardware problem. I'm going to relock the bootloader today, and I will try to repair the phone using SUS.
What is causing the cellphone to freeze? Hope someone help me with this. Thanks in advance!
btw, sorry about my english, hope you understand most of what I wrote
Well in my experience,
The phone freezes because it is too hot,
Or the RAM memory suddenly drops.
I mean sudden ur phone's RAM memory is 0.
I'm not sure too.
But I think reflashing the kernel, or flash other kernel will fix the problem
Try it
Sent from my LT26i using xda premium
What ics firmware did you flash? And did you do a complete wipe when flashing?
Sent from my Jellybean Xperia S
I've flashed other kernel and yes, I do a complete wipe when I flash another ROM, via Flashtool or CWM.
I've been thinking of rolling back to GB to see what happens.
Yesterday my phone freezes like 2 or 3 times in less than 15 minutes. First time I reboot the phone and it was ok like 5 minutes, then it freezes. I reboot again the phone and happened again.
Its not even hot or using a lot of RAM, it always has like 250 or 200mb free
Did u play with CPU settings?
w3nZ said:
Did u play with CPU settings?
Click to expand...
Click to collapse
No, this is happening since the first boot of the phone. When I turned it on the first time it happened, and I had to search how to force a reboot because I didn't know how to do it LOL
It doesn't happen very often, but when it does is very frustrating!
Try flashing a new rom, but wipe the system partition too? I always do that to ensure a fully clean install.
l.Urker said:
Try flashing a new rom, but wipe the system partition too? I always do that to ensure a fully clean install.
Click to expand...
Click to collapse
I'm thinking in flashing a non based stock rom, like CM or MIUI, because I flashed XTXperience before and the freezing happened.
Oh, and the problem still exists. I believe Wi-Fi connection maybe it's the problem, I'm testing some things right now.
Had this too using Supercharger (by zep) but after few setting it's gone. Maybe you should try to run the script ?
It was with stock rom and advanced kernel v15/16.L
Well, I was on 6.1.A.2.45, I relocked the bootloader and an update changed the firmware to 6.1.A.2.55 using SUS without wiping data and the problem was still there, so I repaired the phone with SUS, it erased everything and the problem was gone for like 2 days. Today it happened again.
babylonbwoy said:
Had this too using Supercharger (by zep) but after few setting it's gone. Maybe you should try to run the script ?
It was with stock rom and advanced kernel v15/16.L
Click to expand...
Click to collapse
Advanced Stock Kernel supports 6.1.A.2.55 firmware?
babylonbwoy said:
Had this too using Supercharger (by zep) but after few setting it's gone. Maybe you should try to run the script ?
It was with stock rom and advanced kernel v15/16.L
Click to expand...
Click to collapse
Well, I Supercharged my ROM now, which setting do you use to fix the problem? I'm still having it.
I even flashed a CM10 based ROM and its still happening! I think it's a hardware problem
Nek0x90 said:
Well, I Supercharged my ROM now, which setting do you use to fix the problem? I'm still having it.
I even flashed a CM10 based ROM and its still happening! I think it's a hardware problem
Click to expand...
Click to collapse
Hi, did you manage to solve the problem? I'm having similar issues like you
I have a used (out of warranty) DINC 2 rooted with Cyanogenmod 7.2 installed (Page Plus). The phone has been working fine for about a month. All of the sudden, the phone will not turn on unless I remove the battery first. If I remove the battery and boot the phone, everything is fine until I turn it off and then it won't come back on. If I do a complete shut-down, then it will turn on. I tried wiping the cache - no help. I tried restoring an old backup that was working at the time - no help. Any ideas? What should I try next to debug this?
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
brymaster5000 said:
Do you have s-off? What version of CM7 are you using (official or custom)? What kernel are you using? Have you tried other ROM's?
Click to expand...
Click to collapse
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
rh09 said:
Yes, I have S-OFF, it's rooted. Running CM7.2, official, I assume (CyanogenMod-7.2.0-vivow). Kernel version 2.6.35.14-cyanogenmod-g9b2f4dd [email protected]#175. No, I have not tried other ROMs, it was working fine with this one for about 6 weeks and just suddenly this problem started happening.
Click to expand...
Click to collapse
UPDATE: I think I might have figured it out. I borrowed a battery from another phone and it seems to work fine with a different battery. Anyone have recommendations for a good aftermarket battery (not extended) for the DINC2?
UPDATE 2: The "fix" didn't last. The same problem resumed after an hour or so on the other battery. Still open to suggestions.
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
vforaci said:
When I installed CM10 and was experiencing a bootloop the same thing was happened to me. Could not turn on phone unless I pulled battery first. I have since corrected the bootloop issue and have not experienced it since (same ROM).
Click to expand...
Click to collapse
I don't have any bootlooping - the phone was working great with CM7.2 until this started happening. Can't figure out what caused it. How well is CM10 running on your DINC2 (like, performance-wise)? (Assuming that's the phone you have.)
Performance is better than Viper and yes I have the Dinc2.
What is the turbo engine? I've never used or heard of it. I did have reboot issues with the early builds of cm10. I just flashed psycho's new 4.2.2 build & it seems to be quicker than evervlov. I need to give a couple days though.
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).