I followed one-click root method carefully on my epic 2.1u1 4-times now, and after approx. 1-2 days, my epic goes into a 30sec continuous reboot. Its almost not a full reboot, the screen goes blank for approx. 5sec and then the startup apps and radio connects....
The last incident occurred ONLY 2hrs after I rooted...
In order to resolve this, I have been going into recovery mode and performing a wipe/factory reset each time. Then re-root for a titaniumbackup restore.
I have been stock for 2 days now and without incident...
Anyone experiencing this or have any insight??
guruleenyc said:
I followed one-click root method carefully on my epic 2.1u1 4-times now, and after approx. 1-2 days, my epic goes into a 30sec continuous reboot. Its almost not a full reboot, the screen goes blank for approx. 5sec and then the startup apps and radio connects....
The last incident occurred ONLY 2hrs after I rooted...
In order to resolve this, I have been going into recovery mode and performing a wipe/factory reset each time. Then re-root for a titaniumbackup restore.
I have been stock for 2 days now and without incident...
Anyone experiencing this or have any insight??
Click to expand...
Click to collapse
Titanium backup is most likely the cause. But try using the latest root kernel method by noobl. 1.2.2
guruleenyc said:
I followed one-click root method carefully on my epic 2.1u1 4-times now, and after approx. 1-2 days, my epic goes into a 30sec continuous reboot. Its almost not a full reboot, the screen goes blank for approx. 5sec and then the startup apps and radio connects....
The last incident occurred ONLY 2hrs after I rooted...
In order to resolve this, I have been going into recovery mode and performing a wipe/factory reset each time. Then re-root for a titaniumbackup restore.
I have been stock for 2 days now and without incident...
Anyone experiencing this or have any insight??
Click to expand...
Click to collapse
Can't say I'm experiencing the same problems because my root went fine. My suggestion to you is to do what I did follow the instructions on the forum to flash your epic back to stock using odin. (It's on the first page.) But, this time after you flash the stock back immediately let it boot back up for the first time and without installing apps or anything else simply run the root script. Then use titanium backup to restore your apps (or App Brain).
This is what I did and I have yet to experience any problems with it.
Hope this helps.
THANKS FOR THE FAST REPLIES!!!
Even though I did a recovery wipe/factory restore, you still think I should re-flash a stock ROM?
guruleenyc said:
THANKS FOR THE FAST REPLIES!!!
Even though I did a recovery wipe/factory restore, you still think I should re-flash a stock ROM?
Click to expand...
Click to collapse
Well...that's what I did.
I was running for 2 days fine after a recovery wipe/factory reset on my epic.
So I proceeded to perform the sdx manual permanent root method after doing the one-click 4 times:
http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
It was fine since yesterday evening and approx. 24hrs later, after turning on wifi, its now rebooting continuously again...
Do I need to send my phone back to Sprint, OR should I flash a stock ROM this time before I root?
Please help!
where do I find odin to reflash stock ROM to my epic...?
New developments: After several self reboots 1 min apart, I turned off wifi and it seemed to become a little more stable. However, I started to play pandora and check email....then it happened again about 1 min intervals.
Now its been up for a few hours...
I am loosing my mind!!!
Sent from my SPH-D700 using XDA App
guruleenyc said:
where do I find odin to reflash stock ROM to my epic...?
Click to expand...
Click to collapse
what have you been using to reflash back to stock if you dont have it already???
I haven't been. Just doing recovery wipe/factory reset.
Do I need to flash?
Sent from my SPH-D700 using XDA App
Flash back to stock and see if it happens. Mine would reboot + hardlock on standby even on stock, so I had to take it back to Sprint store.
Flash to stock and DON'T restore any apps with ti backup. Don't even root it. Just run it for a day or two to see if you have a problem with stock sw.
It's stable for 2 days after performing wipe/restore from recovery mode.
However the reboot issue surfaces after rooting and restoring with titanium.........
What you peeps think?
Sent from my SPH-D700 using XDA App
Also, the reboot or reset issue is not happening as frequent and just so I am clear, its like a 10 sec event where screen hours off and comes back on and radios reconnect and media card rescans.
Sent from my SPH-D700 using XDA App
Don't use titanium backup. It seems to cause weird problems.
Firon said:
Don't use titanium backup. It seems to cause weird problems.
Click to expand...
Click to collapse
Titanium backup is fine so long as you don't restore a bunch of your old system settings en mass
If you simply restore your user apps and such or selectively restore some system items you are fine.
I have done batch restores for all apps plus data several times, I guess this included system apps too...?
Is this the problem and is titanium stable or not on the epic?
Sent from my SPH-D700 using XDA App
Oddly enough, the sudden reboots seem to have reduced to 1-3/day. BUT, upon opening titanium backup now....it warns me I don't have root anymore!
I performed the sdx perm root method on thur of last week....
I think flashing back to stock or a custom rom may be my best option at this point.
Please advise?
Sent from my SPH-D700 using XDA App
Seriously dood, I would flash back to stock following all instructions. If it runs right for a few days then just root it. DONT USE TIT BACKUP.
The common thing I saw in reading your posts is that have been restoring whatever is busted with titanium.
Update: although I had lost my root as per titanium, after re-rooting I have been stable for 2 days without going back to stock rom. But resumed KIK Messenger usage resurfaced my reboot issue.
Sent from my SPH-D700 using XDA App
I finally flashed back to stock using Odin. Everything stable so far...
Related
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
You should always perform a full wipe, to include factory/data, when flashing a new rom.
teh roxxorz said:
You should always perform a full wipe, to include factory/data, when flashing a new rom.
Click to expand...
Click to collapse
i did. every time
ryohei47 said:
i did. every time
Click to expand...
Click to collapse
Also, the dalvik, under advanced? And not flashing a kernel with it?
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Shigster said:
I found out that Clockwork never cleared Dalvik for me. I changed to AR and after clearing the dalvik I stopped getting reboots or bootloops. Maybe your phone doesn't like the new Clockwork...
Click to expand...
Click to collapse
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
oohhh. that sucks. try unrooting or using a stock rom for a while. if it keeps rebooting when you browse the web, play games, anything that works the phone, then there is nothing you can do. the phone is fried. wait until it is bad enough that you can do it whenever you want by firing up a game and playing for a few minutes. then bring to the sprint store and they will replace. hah why do i have to be the person who brings the bad news?
again, try unrooting first. you can even leave s-off to re root easily. if you have no reboots, then the problem can be fixed.
i feel so bad giving this news... hah
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
ryohei47 said:
that could be it. everytime i install RA though, it complains and doesnt boot into recovery correctly
Click to expand...
Click to collapse
If you're using ROM Manager, don't! Download the PC36IMG.zip file from amon's thread and place it on the root of your SD card. Shutdown your device. While pressing the down arrow key, press the power button. You will then enter the bootloader screen. After a few seconds, a few lines of text will appear and the bootloader will automatically detect the. PC36IMG.zip file and prompt you to install it. Follow the prompts to install. The installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. The recovery version will be listed at the bottom of the screen. Go to the wipe menu and wipe EVERYTHING except the SD card itself then go to the flash menu and flash whatever rom you wish to flash.
Posting & replying via the XDA Premium app
awesomeindeed said:
My phone recently started doing this. Doesn't matter what ROM I'm on, doesn't matter if I un-root with a factory RUU or re-root, doesn't matter what recovery I use, doesn't matter if I completely format my SD card or boot without one. It got to the point I had to take it to Sprint and have them order me a new one.
It would randomly reboot and then go into a bootloop that not even a factory reset would cure, just decides when to stop bootlooping on its own and occasionally works.
Click to expand...
Click to collapse
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
dougjamal said:
Were you one of the unlucky ones who were using CM7 when the bootlooping began?
Posting & replying via the XDA Premium app
Click to expand...
Click to collapse
No, I had already moved away from CM7 when it began. It started out of nowhere and just got worse on a daily basis.
I had also never used Unrevoked. I rooted with toast's original root method way back last August or so and was using the .76 ENG bootloader.
I had similar issues, in terms of both posts, and it got to the point that I just got it replaced from Sprint. It just progressively got worse no matter what was done. Has happened to others ... sounds like the phone might just be going.
=(
sent from my
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
k2buckley said:
Damn, that sucks. Is that stock, before u even rooted it? I would just take it right back to Sprint.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yep, stock. Only apps installed are GoSMS and XDA. I guess I'll give it a factory reset and see if that fixes it, or else it's going back.
awesomeindeed said:
My new phone arrived today. It's a refurb. HW 0003. Made it about 2 hours without a random reboot. Made it about another 4 before doing it again. This sucks.
Click to expand...
Click to collapse
umm... might have been one of the 2 i got with that problem... srry!
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
ryohei47 said:
i just hate unrooting, the whole process will end up taking a few hours. im probably gonna unroot, and if the basics work, i'll just stick with some simple z4 root and call it a day. any other options? cause htis is already my second phone, not exactly crazy about getting a third.
Click to expand...
Click to collapse
Unrooting take like 5 minutes...flash s-on tool, then the 5 minutes to run the ruu, then another 5 minutes to re-root.
ryohei47 said:
recently, my phone has just started a habit of randomly rebooting. i was using myn rls5 with net kernel 4.3.2, but i decided to try something different in an attempt to stop the problem, so i went to mikfroyo with its default kernel. right after i startthe phone and it gets to the homescreen, it starts restarting again. i cleared data and cache between roms, and im using clockworkmod 3.0.0.5
Click to expand...
Click to collapse
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
HipKat said:
My phone never has random reboots. Never. And I have a list of roms as long as my arm that I have flashed.
Click to expand...
Click to collapse
There are a bunch of bad EVOs floating around. If you have this problem, you're more likely to get one of these as a refurb as they are the ones they get back. They'll replace the display, etc. But its the mobo that is probably the issue, and they don't replace that. They probably just make sure that it boots up and can make a call..
Sent from my PC36100 using Tapatalk
yesterday a dialog popped up on my phone to update my phone. I clicked on postpone, thinking it would simply just ask me later. I am running RMK's ROM, and now every time I turn on my phone it turns off and tries to update, but fails. How do I stop my phone from doing this? I don't want the update.
Try either doing a data wipe or flashing another ROM then going back if you want to stay on RMK.
I have also heard wiping the cache from recovery works too.
I'm running RMK's Rom and just caught the update notice just now. PITA it limited deferment to 5 days. Earlier today I didn't catch it in time and had to batt pull after it hung. When I went to recover from a recent nandroid backup it hung trying to boot into CWM. I did get into recovery on the second attempt. Just be sure you have a current nandroid of your stuff.
Shouldv'e dug a little more before posting.
http://forum.xda-developers.com/showpost.php?p=16093933&postcount=383
Sent from my ADR6350 using XDA Premium App
Epic 4g running bonsai 4.0.1, rooted with CWM3.005 and flashed to cricket 3 months ago. I've been using titanium , superuser, pandora, all programs worked great. I even got most of the sprint crap off my screen.
Last week I was powering down to change batteries but I popped the battery out before the final buzz signaling full shutdown. upon reboot, phone had lost my home setting, icon placement, etc, and had sprint crap back on it. i reloaded the bonsai zip, but I cant restore using titanium because it won't let me access titanium, or pandora, and most of the games and apps I've installed. Also the launcher crashes a lot now...
Do I have to wipe the phone and start over? anyone have a suggestion? thx for reading...
Bravo u found a new way to factory reset
Id odin
Sent from my SPH-D700 using XDA Premium App
Yeah, I feel like a tard..
...whats odd is I still have bonsai, and i can still access CWM in recovery mode, so...i'm still rooted, and yet, it won't ACT like its rooted, denies me access to post-root programs. So odin from scratch? (hope this is a lesson for all us impatient noobs....WAIT FOR FINAL LIGHTS OUT! LOL)
Did you try wiping Cache and Dalvik 3x first? If so, sounds like an Odin fix. I would start fresh. One thing I have learned from testing things that aren't released yet is that Odin is actually pretty painless if your phone is recognized by PC. Its 3 min 35 seconds to get back to stock, 2 min for Root. The longest part is the RFS to EXT4 file conversion but its not bad at all and at least you will have a totally clean install.
Sent from my SPH-D700 using XDA Premium App
haven't tried the cache/dalvek wipe yet...doing now...
Hi all,
this is the 3rd time this is happening to me with different ROMs. The problem is:
The phone boots up normal, I can swipe to unlock, enter my PIN, but after pressing OK it won't unlock the SIM. If I lock the screen it won't come back on. It stays black whatever I do. After some time the phone reboots (soft reboot) and everything starts from the beginning.
The first time this happened I was using Modacos Ir9. I had the phone switched off over night and switched it on. Only thing that seemed to help was completely unrooting the phone and rerooting it again.
The second time I was using codeworkx CM9 Builds and tried to update. I restored my nandroid, but it kept happening. Flashing the XXKK1 Radio did the trick here.
Now it is happening again. This time I installed dropbox and the phone froze on the setup wizard...
I don't want to unroot the phone, it takes forever to restore the SD card.
Any advice on this one?
Update:
- Flashed the following radio images without any success: XXKL1, KRKL1, UGKL1 and XXKK1
- Used my older nandroids from CM9 and Modaco Ir10. NOT WORKING
- Wiped every nandroid. NOT WORKING AT ALL
- Reflashed CM9 and Ir10. Still NOT WORKING
I'm so lost I'm going to revert to stock and unroot... and try how far I can throw an 1 month old GNx from the fourth story.
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
I posted a thread here then to ask people if anyone experianced the same but got no reaction what so ever zo I guess "we" are a dark minority.
I don't know what it caused it or what the solution might be but a Factory reset did it for me.
Good Luck!
C-4Nati said:
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Last time it was working again after reverting to stock. But I bought it to use Custom Roms
I would say go back to stock w/ odin, Wipe everything and start again.
Diger36 said:
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
Click to expand...
Click to collapse
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
the_alien said:
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
Click to expand...
Click to collapse
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
zephiK said:
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
the_alien said:
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
Click to expand...
Click to collapse
I'm willing to bet an app is causing it.
Sent from my Galaxy Nexus using xda premium
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Potterified said:
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Click to expand...
Click to collapse
It can't be any app or ROM because IF it happens, it happens on all ROMs, regardless of wipe or not.
It just happened again and i wiped everything and tried using AOKP MS 3. Wasn't working... So I tried using the phone without the SIM card, because the hell only breaks loose after entering my PIN. And it worked. I could use the phone...
I put it back in and it worked...
I'm restoring my CM9 nandroid right now. I'm hoping it works...
edit: Nope, ripping out the SIM doesn't work. I'm reverting to stock and wait what happens. If it crashes again I'm trying to return it.
Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.
Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App
Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened
Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.
Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?