Random Reboots - Verizon Samsung Galaxy S III

I have a verizon S3 on MB1 it was rooted on beans for a while it worked fine. Got a new phone and my girlfriend wanted the S3 so i odin restored it back to stock verizon MB1. The phone rebooted earlier today and now its about every 5-10 mins i found a different stock verizon odin file and restored to it still reboots randomly so now im going to try and flash beans again to see if it works like it did before anyone have any other options the phone seems laggy and locks up at random times and if it randomly reboots more than 3-4 times it tries to reactivate again which makes it sit in the activation screen and it continues to reboot until i boot to manual stock recovery and wipe data. Also no apps are installed but the verizon factory ones
New Update: I rooted/unlocked/ and installed beans rom now it locks up black screens and reboots any help would be great thanks guys!

I would boot into recovery, factory rest, wipe dalvik, and wipe system. Then flash MF1, as MB1 is outdated now.
Sent from my Last Ever Samsung Device.

Related

[Q] Random reboot into Recovery

I have a Sprint Nexus S4g, and have been using Bugless Beast ROM for a few weeks. About a week ago I started having Random reboots to recovery, as well as locking up at the Google splash screen when rebooting. I have also had many problems with google apps crashing as well as the phone just being locked up when I go to use it (in this case the notification lights usually are lit).
I have tried clearing cache/dalvick cache and factory reset. The last time I even wiped my SD card and am now stopping Google from installing my apps other than Goomanager.
about an hour after my last attempt, I got my first random reboot to recovery. I am not sure what to try next.
Thanks for any help!
Go back to stock and see if the problems persist
snandlal said:
Go back to stock and see if the problems persist
Click to expand...
Click to collapse
I am going to try when I get home. If that doesn't work, I guess I will send it to Samsung under warranty.
Just returned to stock, and it is still locking up.

Infuse stuck in boot logo loop

My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Did you have any undervolt settings applied?
The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago
Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!
himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?
okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?
bump! really need help with this guys!
Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse
It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed
I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.
Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.

[Q] Phone doesn't boot all the way

I'll start with I'm running Bean's JB B6 with KTkernel selected in aroma.
I wanted to flash leankernel after running KTkernel for a while to see the difference for myself, and when I went to flash everything went smooth, but when I went to reboot, the samsung logo came and went, same with the splash logo but after that nothing. Screen went off and nothing happened for a good five minutes. I didn't wipe anything because I'd gotten away with it in the past.
I booted back into recovery, wiped cache/dalvik and reflashed and still nothing. Tried the same going back to KT and still nothing. Even tried to flash the stock kernel and the same thing kept happening; Samsung, Splash, Black.
I have a nandroid that I can restore back to but I really would hate to have to do that and want to avoid it at all costs... any help is greatly appreciated.
Reflash the ROM after wiping caches.
Sent from my SCH-I535 using xda app-developers app

Major breakage: phone hangs at unlocked bootloader after first reboot of custom rom

Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.

[Q] Phone won't boot

I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Why all the way back to ED1? Do you have everything backed up in case you need to flash with the pit file?
Sent from my SM-N900V using XDA Premium 4 mobile app
beavermjr said:
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Click to expand...
Click to collapse
No, the phone is not dead, it is a bit lag.

Categories

Resources