I have been rooted for a while now, and i have never had this problem. At times, my phone will randomly reboot and then be in safety mode. I am getting really frustrated because i have to reset my widgets. It would be helpful if any one has a solutuin.
Thank You.
Did you recently switch to an EC10 kernel?
Just went through this with the lady's fascinate. So, yesterday, I used Odin to get the new CWM, then flashed adren's frankenclean, no more random reboots into safe mode! Idk if this is your fix, but it worked for me.
*EDIT* Random reboot into safe mode today, still no reasoning?
FrankenCleaned & Coma Volted
I am on EB01. I am going to wipe data and all that stuff and reflash everything again. Hopefully it works.Thanks for the advice guys.
Related
Hey guys,
I need some help getting back to stock ROM. I had Bionix before, and I tried to upgrade Bionix I think without disabling lagfix. I tried to flash back to stock, after reformatting internal and external cards and Odin reports everything went fine, but I can see one error "Data wipe failed".
The phone boots to the standard Tmo jingle and the softkeys are always lit, but the display seems to be off.
ADB can't find the device.
Is it bricked for good or is there still some hope? Any insight, tip, link, advice would be greatly appreciated.
Thanks
your not bricked, I am having the EXACT SAME ISSUE! you can just re-flash Bionix and even though it tells you it fails it will reboot into Bionix! However I can't get the stock rom to work WTH!! I have even tried my nandroid backups! I am lost but I can get back to Bionix so not all is lost.
*edit sorry* I had disabled my lagfix, I was just trying to flash back to stock. he tells you how to fix it in the thread.
So I've got a problem for you gurus out there. A little history...
It all started last week when I tried flashing to KaosFroyo v38 and it was eating my battery alive. People suggested flashing CFS kernel v6 (at the time) but every time I flashed I would never get past the skating androids. I factory wiped, davlik wiped, still no go. After messing with it for a couple days I just re-flashed back to KF v37 and figured I would wait for a new rev.
So this week CFS v8 is out and the new governor feature which I am really wanting to try so I figured I would give it a go again. Factory and dav wipe, flashed KFv38, flashed CFSv8 on top, same issue with the skating androids. Someone suggested to try a different rom. So, I tried CELBv3.6 since it had the same kernel and still no go. This morning I tried FloyoTazz v17 and the same issue.
It appears that it might be kernel related but I am really not sure. I PM'd conap and he suggested I get a logcat at boot to diagnose, but my device doesn't seem to boot enough to detect the device on my PC. When I enter adb logcat it just says "- waiting for device -" and if I enter adb devices nothing is listed. It's like all my phone does is turn on and thats it.
KaosFroyo is the only rom I've tried that I can get to flash and boot and v37 is the only one that doesn't drain my battery so thats where I am at.
Any help would be much appreciated.
Bump. Still looking for answers.
P.S. - Helped my friend root his eris this morning. Installed TazzFroyo v17 first time no problems. I'm really curious what in the world is causing my phone to not boot up...so weird.
Man I guess I really stumped you guys.
Just an update on some things I tried yesterday.
1. Reformated my SDCard to a single partition. No change.
2. Tried booting without SDCard. No change.
3. Unrooted back to factory 2.1. Re-rooted and flashed. No change.
I'm running out of google searches and ideas. Since I can't boot long enough for my PC to recognize my phone, is there a way I can run a boot log locally on my phone without adb? Unfortunately until I get a boot log of some sort, I'm stuck with the trial and error approach.
It is possible that your phone can't handle the CPU speed of 710 that the ROM and Kernal are clocked at. That would put you into a boot loop. I have seen that before. Not common, but it has happened. You might be able to PM Conap for suggestions on how to lower the clock speed before you boot up. I believe it can be done through the computer link in recovery.
koamalu said:
It is possible that your phone can't handle the CPU speed of 710 that the ROM and Kernal are clocked at. That would put you into a boot loop. I have seen that before. Not common, but it has happened. You might be able to PM Conap for suggestions on how to lower the clock speed before you boot up. I believe it can be done through the computer link in recovery.
Click to expand...
Click to collapse
I've run setcpu at 710 without issues, but definitely something to try. Thanks for the tip.
Just to follow up on this issue which is now resolved.
I have been working with Conap who writes the kernel for many of the new roms out there for the past week and we finally resolved the issue. Apparently with CFSv6+ he added CIFS support to the kernel which was causing the boot problem for me. After removing that from the kernel, everything flashes fine.
Im very dissapointed, my Streak has gone to silicone heaven and there is no reason for this either.
I got up this morning, got dresst and went to work as normal, I noticed my Streak vibrated in my pocket so when I got to work I had received a text so I proceed to unlock the device only to find it lagging to death and generally un-responsive.
This cleared and I started writing my responce to the text and the haptic feedback stopped and then the phone became fully un-responsive, so it was time for a bettery pull, I did this a further 3 times as it kept locking up (I though it was due to a media player I installed from the market last night so was going to uninstall it but it wasnt in the list of installed apps)
Then after the 3rd reboot I was then stuck at the boot screen and it would not go any further, I have gone into the recovery menu, cleared partitions etc etc and still its the same, I have also flashed back from DJ_steve 1.6.1 to 1.5.1 in the vein hope that it was something to do with 1.6.1, but no still the same.
Im going to try and put a stock rom on there and see what happens (as im able to flash etc etc it just seems to be when something is initializing during boot)
Im just wondering if anyone else has had this issue?
Try going to 1.5.1, allow it to boot fully. Go back into Recovery and do a factory reset. Option 4 in the Dell Menu, not StreakMod/ClockWorkMod. Allow 1.5.1 to fully boot up again. Go back to recovery and then flash 1.6.1 Hopefully this should get you up and running again. Do remember that 1.6.1 will take a while to boot up the first time.
Edrill said:
Try going to 1.5.1, allow it to boot fully. Go back into Recovery and do a factory reset. Option 4 in the Dell Menu, not StreakMod/ClockWorkMod. Allow 1.5.1 to fully boot up again. Go back to recovery and then flash 1.6.1 Hopefully this should get you up and running again. Do remember that 1.6.1 will take a while to boot up the first time.
Click to expand...
Click to collapse
Hi Edrill, thanks for the response, I have flashed 1.5.1 back on and factory reset, at 1st it didnt work but I tried again and was in the front room and I heard my alert tone back up and running on 1.5.1 think ill stick with that for now as its 2.2 anyways.
Thanks again bud.
No problem! Glad I could help.
Now that you've got a factory-resetted phone, going up to 1.6.1 shouldn't create any issues really. Just that the first boot after flashing 1.6.1 may take unusually longer than the first boot on any previous build, is all.
Edrill said:
No problem! Glad I could help.
Now that you've got a factory-resetted phone, going up to 1.6.1 shouldn't create any issues really. Just that the first boot after flashing 1.6.1 may take unusually longer than the first boot on any previous build, is all.
Click to expand...
Click to collapse
Ive opted for 1.5.3 for the time being, I had that for a few weeks without any issues so going to stick to that and see how the phone goes.
For now she's up and running without any issues *touches wood*
I installed avast mobile security and set everything up as a root user. I'm on the stock ROM and as soon as I was done setting everything up I rebooted and now Im' stuck in a boot loop. It does not boot loop every time... sometimes it boots up and after about a minute it reboots itself, then bootloops.
I removed avast as an administrator / rebooted / then did a clear data and uninstall. Same thing happens so I booted into amon and did a clear cache and dalvik cache.
I've also booted into Amon and wiped all caches. Still no go and I notice that I'm not getting any signal bars (yes, I remembered to put the cover back on). Any help would be greatly appreciated...
Try this.. http://forum.xda-developers.com/showthread.php?t=1394659
sent from ics land
edit: try what the person above me posted first.
Are you on the stock kernel too? I would recommend doing a full nandroid backup and an internal SD card backup and RUU from scratch if you can't get the loops to stop.
I ran avast! for a while with no issues. Could be the link above is what you need.
Thank you all, trying option #1 now. I do have a Nandroid backup I did after I first rooted, and I am on the the stock Kernel.
Holy Cow, it was set to WCDMA Preferred! I'm really surprised that avast changed that setting. I put it back to the correct setting and now my signal is back. I'm rebooting now to see if it sticks.
Thank you all a ton! I'll post back in a few and let you know if that did the trick *fingers crossed*....
Update: Been about 15 minutes and no bootloop or auto reboot so the fix seemed to have worked. Once again, thanks a ton you guys for the help, I appreciate it.
I doubt it was avast that did it. It seems to happen randomly to certain people.
So, SGH-177 had been rooted and installed CM7, then Unnamed, then AOKP. All were pretty buggy. We wanted to bring it back to factory (with root if possible). Not for a warranty claim, just so it would be somewhat stable.
Anyway, I found a one click ODIN solution for UCKH7 stock. I used that, it passed. then the phone just looped through the AT&T "Rethink Possible" splash screen. I tried to get into recovery mode, but it wouldn't load, so I flashed the Siyah kernel to get CWM on there. Still I can only get into download mode and the phone loops the splash screen.
I hoped that it was just taking some time to load up the first time, so I left it overnight. Still stuck on the splash screen this morning.
I spent hours on here last night and found lots of people saying that if you have access to download mode, or recovery mode, you should be able to fix it. I wasn't able to find any answers as to how.
Help?!
I've had this same problem before. what always fixes it for me is to get into the factory 3e recovery to do a reset. I know you said you couldnt get there but make sure (while the phone is off; remove battery if you have to before this) you are holding down both Volume buttons and the power button at the same time until you see the "Samsung Galaxy SII" screen, then release the buttons.
factory reset, then it should be fine.
If you can't get to recovery, read some more on here. I'm sure something is out there, but I don't know what it is.
Here are two posts that might help you out. I've been doing the same research since my "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII is due to arrive today or tomorrow.
http://forum.xda-developers.com/showthread.php?t=1451590
http://forum.xda-developers.com/showthread.php?t=1580885
Best of luck to you!
UnNamed buggy?
Out of curiosity how did you root and flash, cause that is probably one of the most stable builds we have with minor changes to stock.
Anyways good luck getting back to stock.
So, for some reason, the next time I tried booting into recovery, it worked. I got a couple errors, but then it booted up just fine. Don't know why it wouldn't get into recovery before.
Everything seems to be working as it should so far.
I'm guessing this may be why some of the threads I had seen didn't really offer a solution. Sometimes it finally works if you just hold your head right.
Thanks all!
Regarding UnNamed... I don't recall the method I used to root, it's been a long time and I've done various work on this (my wife's phone) and my Nexus One. Easy to get it confused. I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Major Wood said:
I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Click to expand...
Click to collapse
Did you also wipe cache and dalvik? May have been the problem...
I don't recall, but would be surprised if I hadn't done that
A year ago. When I first started flashing roms. I spent an entire week just reading the atrix forums and learning. I planned. I schemed. I asked questions. Through pm. And googled a LOT. Then when I had learned enough I did it. Point is....if yer not willing to have patience and learn as much as u can before u jump into this. Then its maybe not for you.
Sent from my SGH-I777 using Tapatalk 2