The past few days my phone has been rebooting constantly. Not a full reboot but like a hot-boot. It happens every single time I uninstall an app and more often than not when I install one. I have tried the phone in safe mode, as well as restoring back to mdk and the issue persists.
I am currently on HD15. No matter what I have done it still does this. I have also removed my sd card to see if that was it, and same thing happens. The battery isn't swollen and I really hope it isnt just hardware because I'd have to lose my mdk phone and that would suck. Any help or ideas is very appreciated. It's driving me insane.
Edit: The phone has also done it just when idling.
Hasn't happened to to anyone else?
Bummer.
RojoNinja said:
Hasn't happened to to anyone else?
Bummer.
Click to expand...
Click to collapse
This has been mentioned a lot in the Hyperdrive thread. Apparently it's a pretty common problem with MDK phones. I think I read it has something to do with the kernel. You might want to check there.
Sent from my NCC-1701 using Tapatalk 4
RojoNinja said:
The past few days my phone has been rebooting constantly. Not a full reboot but like a hot-boot. It happens every single time I uninstall an app and more often than not when I install one. I have tried the phone in safe mode, as well as restoring back to mdk and the issue persists.
I am currently on HD15. No matter what I have done it still does this. I have also removed my sd card to see if that was it, and same thing happens. The battery isn't swollen and I really hope it isnt just hardware because I'd have to lose my mdk phone and that would suck. Any help or ideas is very appreciated. It's driving me insane.
Edit: The phone has also done it just when idling.
Click to expand...
Click to collapse
I had it happen on my MDK S4 when using HD15, but not so often as it seems to happen for you.
I'm using the GPE rom (4.4.2) and never had any similar issues with it.
riker147 said:
This has been mentioned a lot in the Hyperdrive thread. Apparently it's a pretty common problem with MDK phones. I think I read it has something to do with the kernel. You might want to check there.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
Which kernel? I've tried 3 different ones.
I also odin'd back to stock mdk and still freaking have the same issues. Though I did the no-wipe tar. I wonder if a completely clean slate would fix it. I may try tomorrow after backing everything up completely and making another nand-backup. I have no idea what else to do other than replace the battery and see if thats the issue, or replacement phone and lose my mdk one.
RojoNinja said:
Which kernel? I've tried 3 different ones.
I also odin'd back to stock mdk and still freaking have the same issues. Though I did the no-wipe tar. I wonder if a completely clean slate would fix it. I may try tomorrow after backing everything up completely and making another nand-backup. I have no idea what else to do other than replace the battery and see if thats the issue, or replacement phone and lose my mdk one.
Click to expand...
Click to collapse
Yea try the full wipe from here
http://forum.xda-developers.com/showthread.php?t=2289325
Hopefully that helps and you don't need to get rid of your MDK phone
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Yea try the full wipe from here
http://forum.xda-developers.com/showthread.php?t=2289325
Hopefully that helps and you don't need to get rid of your MDK phone
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
So I just did this and it appears to have worked. Right now I am rerooting and trying to decide whether or not I should try restoring HD from a twrp backup or just restoring my regular apps on mdk.
RojoNinja said:
So I just did this and it appears to have worked. Right now I am rerooting and trying to decide whether or not I should try restoring HD from a twrp backup or just restoring my regular apps on mdk.
Click to expand...
Click to collapse
Well that's good news! Hopefully that issue is no more. I've used this same Odin file a few times and it's rescued me every time. I usually always go with a full wipe.
Also I flash KToonsez Kernel with every ROM I flash, Touchwiz or Aosp and it's treated me good each time.
only mentioning that since it was said that maybe this was kernel related somehow although I'm not sure why after you flashed the no wipe Odin file it still happened. Sounds like your phone just needed a good cleaning. I'd start fresh with whatever ROM you choose to flash.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Mistertac said:
Well that's good news! Hopefully that issue is no more. I've used this same Odin file a few times and it's rescued me every time. I usually always go with a full wipe.
Also I flash KToonsez Kernel with every ROM I flash, Touchwiz or Aosp and it's treated me good each time.
only mentioning that since it was said that maybe this was kernel related somehow although I'm not sure why after you flashed the no wipe Odin file it still happened. Sounds like your phone just needed a good cleaning. I'd start fresh with whatever ROM you choose to flash.
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Hmm, yeah a clean flash would probably be best. But I will go ahead and restore user apps (and things like messages and accounts on my phone), I am fairly certain it had nothing to do with those.
Will report back with how that goes. But for now, a backup of the fresh MDK install, thanks for the help!
Right so I stayed on MDK for now, and restored pretty much everything. I think what may have broken things is trying to restore media storage (playlists) in titanium backup. after the clean mdk image I made a twrp backup and decided to only try the setting options that titanium backup does. Well one (or more I suppose) of those broke everything and the rebooting came back. I restored from the backup again and restored those settings one at a time, but left out some of the green colored backups in tibu, and all is well. I will however wait until HD16 before messing with another rom.
RojoNinja said:
Right so I stayed on MDK for now, and restored pretty much everything. I think what may have broken things is trying to restore media storage (playlists) in titanium backup. after the clean mdk image I made a twrp backup and decided to only try the setting options that titanium backup does. Well one (or more I suppose) of those broke everything and the rebooting came back. I restored from the backup again and restored those settings one at a time, but left out some of the green colored backups in tibu, and all is well. I will however wait until HD16 before messing with another rom.
Click to expand...
Click to collapse
At least you know where the problem came from. I actually don't even bother saving and restoring with TiBu anymore because of issues that can sometimes pop up afterwards... I know for some though they really need to have their apps and data restored so just one of those things I guess
Sent from my SCH-I545 using Xparent Blue Tapatalk 2
Related
I flashed Trigger 3.0 when it first came out, I was so happy with the rom that I took a abreak from flashing different roms. A week ago I started to get some force closes and they became a bit more frequent. Over the past couple of days I have been looking for a new rom to run. I started with Explodingboy's Simply Honey 3.6, then tried Simply Honey v1.0XE and Heathen's Private stock 2.0. Each time I flashed a rom I came started by odin-ing to JDF first.
With all of the roms I got the same problem, which leads me to thing it's hardware based rather than the roms. I would flash the rom, the rom would work fine for a few hrs then the phone would freeze while asleep. The only way to wake the phone was to do a battery pull. This sleep freeze would happen 30-40% of the time the phone would go to sleep.
I'm going to try to flash a 2.2 rom and see if my phone does any better, the others were 2.3.3 or 2.2.1
What kernel are you running?
Hardware takes quite a bit of abuse to deteriorate. In fact, most "hardware parts" will just simply die, not slowly deteriorate.
Sdobron said:
What kernel are you running?
Click to expand...
Click to collapse
With Trigger 3.0 I was running overstock OC/OV, with no problems for many weeks.
Once I started looking for a new rom, a few days ago, I always used the default kernel.
Do you mean ODIN to JDK?
Thats the stock base for Vibrant.
Side note: I have been unable to use my screen while device is plugged in, to dosent make the right touches and bounces around the screen...I was thinking I needed to ODIN to JDK, so I did... nothing changed, now I'm thinking I might need to get a new phone... #FYI
Thats actually pretty interesting. For awhile I had the same problem it just wasn't as frequent as yours. I'm using the Overstock kernel which I think it was what mine was related to. I had my sleep profile in setCPU set really low, I bumped it up and havn't had any problems since.
studiozeroseven said:
Do you mean ODIN to JDK?
Thats the stock base for Vibrant.
Side note: I have been unable to use my screen while device is plugged in, to dosent make the right touches and bounces around the screen...I was thinking I needed to ODIN to JDK, so I did... nothing changed, now I'm thinking I might need to get a new phone... #FYI
Click to expand...
Click to collapse
Actually the phone ships with JFD, so your wrong haha. xD
Longcat14 said:
Actually the phone ships with JFD, so your wrong haha. xD
Click to expand...
Click to collapse
Java Development Kit
To the OP, maybe you've restored some corrupt titanium data. Only restore apps and no system data after a fresh flash and see what happens.
How about u coding to stock and leave it alone see if u have same problem if not then its not hardware related
Sent from my SGH-T959 using XDA Premium App
hotadef said:
How about u coding to stock and leave it alone see if u have same problem if not then its not hardware related
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
I second this. Go back to stock, and see what happens. Also, do NOT restore any backups at all, leave everything clean.
Also you can try and use System Panel, and see wich apps are running in the background, and then Titanium Backup to freeze app by app (not system apps of course) and see if any of these are causing you the FCs.
Hey all thanks for all the responses. I was reading them all yesterday but did not want to reply and jinx my trigger 3.2 flash. I've now been running trigger 3.2 for close to a day and no FCs.
I can say I did anything different with this flash to make it more stable. I went back to JFD via odin and use Ti to restore user apps and system apps (ONLY: wifi, bluetooth, user dictionary, and MMS)
thanks again for everyones help.
Glad to hear it is worked out.
I installed LI5 when it first got leaked, and was stunned by the speed increase it had over ol' ICS...
I absolutely loved it, and used it for quite some time. When LI8 leaked out I flashed that, but somehow felt that it was a bit slower than LI5, and so I flashed back to LI5, which worked great. (These 2 flashes were done without any wipe/format)
Then after a long time of using LI5, it started showing some signs of sluggishness and jerkiness, especially on the Apex homescreen. Just sliding across the homescreens seemed to be taxing the processor! I tried to tweak some settings, removed some recently installed apps etc. but nothing worked. I just couldn't understand it! Something that was working perfectly suddenly became slow!
I tried to ignore it too but it got too frustrating after a while. Then I decided to install LIB, this time after doing a full wipe and format. So I did a Titanium backup of apps+system data, formatted system, cache, the whole thing and flashed LIB through Odin. Then restored apps+data.
Well here it is. It's much better than what was frustrating me before, but still not as good as the Butter experience on LI5 when I first installed it. :crying:
What went wrong?? I hope to goodness nothing has happened to the hardware!
Please help me solve the issue.
Try another rom could be rom is bad
Sent from my SPH-D710 using XDA
g4rvd4 said:
What went wrong?? I hope to goodness nothing has happened to the hardware!
Please help me solve the issue.
Click to expand...
Click to collapse
Why don't you try full wipe?
You should have done it between LI5 and LI8. And, never restore data with Titanium, unless it's on the original ROM.
grandis12 said:
Why don't you try full wipe?
You should have done it between LI5 and LI8. And, never restore data with Titanium, unless it's on the original ROM.
Click to expand...
Click to collapse
There is no need to full wipe between LI5 and 8.
And as for what you say about titanium, that is just ridiculous, what would be the point of titanium if that was all you could do with it.
I've taken backups I've made on LI8 and am now using them on an aosp based ROM. No problems.
Seriously, you can't go around saying stuff like that, someone might take you seriously.
Sent from my GT-I9300 using xda premium
You 'shouldn't' restore system data. User data is fine obviously.
And as for your issue, I have no idea. I'm on LIB and seems fine.
Sent from my GT-I9300 using Tapatalk 2
My amaze used to be pretty solid, but I'm running into an issue where it reboots on a pretty regular basis, frequently when being turned on or launching something.
This used to happen when the battery got lower (like < 20%), so I bought some "Andida" batteries online which at first seemed great but quickly exposed the same problems.
Then I bought a pair of Anker batteries online, and at first things seemed ok but the problem has quickly reappeared and things are getting worse rapidly.
At this point, the Anker batteries are only maybe two weeks old, and no matter which of 5 batteries I put in (all fully charged, either in phone or in the Anker charger), reboots start appearing by 60%-70% battery life remaining, and its' getting so frequent that I can't rely on the phone for anything at this point.
Note - when plugged in, I don't have the problem.
It would be nice to have at least enough life left in this phone to get to the DROID DNA's release date in Canada, (or even a One X+) either of which look to be at least 30-60 days out.
Right now I am planning on doing a full NANDROID backup and fresh install of the ROM I'm running (ARHD 3.01). Past this, I could attempt to flash the latest Telus RUU but I doubt that's the issue, and I'm not sure if I would lose root or S-OFF if I go down that road.
Any thoughts on what the issue could be or if it's a detectable / repairable issue?
Thanks for any help!!
Massiv.
My phone used to do that. Just reflash an RUU. Your partitions are probably corrupted. If you want to root again, make sure you install a fresh ROM, not restore a nandroid.
I had the same exact issue no matter what Rom or ruu was flashed it still did it so I called T-Mobile and they replaced the phone under warranty and sent a new battery free of charge
Sent from my HTC_Amaze_4G using xda app-developers app
hasoon2000 said:
My phone used to do that. Just reflash an RUU. Your partitions are probably corrupted. If you want to root again, make sure you install a fresh ROM, not restore a nandroid.
Click to expand...
Click to collapse
Thanks guys. No warranty coverage anymore, so will try a from-scratch "superwipe" and fresh ARHD install, and barring that, will try reflashing the Telus RUU.
I'll report back with results...
Massiv.
same issues here, and after flashing the telus ruu no more problems. Mine werent' as bad as yours though, I'd go a few days to a week before I got a restart
andy55 said:
same issues here, and after flashing the telus ruu no more problems. Mine werent' as bad as yours though, I'd go a few days to a week before I got a restart
Click to expand...
Click to collapse
When you flashed the RUU did you lose root?
Massiv99 said:
When you flashed the RUU did you lose root?
Click to expand...
Click to collapse
Whenever you flash an RUU, you will lose root. Just use my toolkit to root it.
hasoon2000 said:
Whenever you flash an RUU, you will lose root. Just use my toolkit to root it.
Click to expand...
Click to collapse
Cool - thank you.
Massiv.
I'm not sure if I got used to the gs3, but I found the amaze a couple of weeks later laggy or stutter-y. I tried everything, sense 4, cm10 and... its just awful
Sent from my SGH-T999 using xda premium
eggydrums said:
I'm not sure if I got used to the gs3, but I found the amaze a couple of weeks later laggy or stutter-y. I tried everything, sense 4, cm10 and... its just awful
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Compared to newer high end phones, yeah HTC kinda sucks now. Nearly every other dual or quad core phone i've seen is really quick on ICS but not the Amaze.
Wrong section there mate. This belongs in Q&A section.
Thread moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Never rooted my new amaze and shuts down alot
Does this only get rid of root or does it get rid of s-off and sim unlock also?
Kusso - Flashing back to stock only removes root. It doesn't affect sim unlock or s-off.
That said - I am HAPPY to report that reverting to the Telus stock ROM (and getting off of ARHD and probably my slew of zillions of apps) has stopped the phone from rebooting, and battery life is also greatly increased!
The phone works like it should now, and is back to being a keeper.
Thanks for your help guys.
For thread searchers later, my process was:
-Backed up everything with titanium
-Backed up internal and external SD cards
-Formatted both SD's
-Manually copied back only core files (media and such) to the SD's
-Flashed the original Telus RUU from this site
-Flashed the OTA update
-Re-rooted and flashed back 4-Ext [Thanks Hasoon!]
-Mostly restored only core apps via Titanium, and mostly without the data unless I was sure the app was harmless
Back to a great experience.
Massiv.
I've always used TWRP on my phones, for years...but recently I keep getting stuck at the custom samsung screen during a reboot. I've seen others with this problem and heard that it may have something to do with the way it wipes the phone during a full wipe. But what is the fix? I almost refuse to go to CWM. I'm just tired of having to unroot and reroot, just to get TWRP to work normally. Let me know if you've experienced the same and what can be done. Thanks.
Been a lot of issues that have been obvious and many others that have been suggested to be due to twrp.
I switched to cwm probably 2 months ago
Sent from my SCH-I545 using Tapatalk 4
twiz0r said:
Been a lot of issues that have been obvious and many others that have been suggested to be due to twrp.
I switched to cwm probably 2 months ago
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
I really didn't want to have to...such a bummer. I guess I'm holding out because surely TeamWin knows about it and is fixing it. At least I hope they do. I knew that I wasn't the only one, was just hoping someone would have a tip that would save me some headache and keep me from having to switch.
For me sometimes it takes quite a long time to start. It seeming hangs at the teamwin startup screen for many minutes. Eventually it loads though.
ericstephani said:
For me sometimes it takes quite a long time to start. It seeming hangs at the teamwin startup screen for many minutes. Eventually it loads though.
Click to expand...
Click to collapse
Maybe I haven't been patient enough, but it never seems to get past that screen. It's weird though because guys like DROIDMODDERX on youtube flashes a ton of ROMS on his phone with seemingly no issues. I ended up just switching to CWM, even though I can't stand it. I guess I'll switch back when and if TeamWin address the issue. I wanted to try OUDHS and the other one that I can't think of the name of, but I'm leery of recoveries that I've never tried.
allforwon said:
Maybe I haven't been patient enough, but it never seems to get past that screen. It's weird though because guys like DROIDMODDERX on youtube flashes a ton of ROMS on his phone with seemingly no issues. I ended up just switching to CWM, even though I can't stand it. I guess I'll switch back when and if TeamWin address the issue. I wanted to try OUDHS and the other one that I can't think of the name of, but I'm leery of recoveries that I've never tried.
Click to expand...
Click to collapse
There are downloads of TWRP version 2.5.0.2 floating around that do not have the freezing issue. I will look around to see if I can find it or if I have it.
edit: check out this post for download: http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Thanks for the reply. That's the version that was just before 2.6 right? If so, I was having the same issues with it as well. I read in another post somewhere that it had something to do with the format all function, the one where you have to type yes to erase everything. That being said, I emailed TeamWin and asked if a fix was in the works or if there was a recommendation that they could make about how to actually use the TWRP so that I wouldn't have problems. I never got a response. So maybe I'll try to go back to 2.5...this is just really weird for me because I never had issues with my Note 2, ever. The only time I ever Odin'd back to stock was to sell the phone. I could flash 10 ROMS a day and never get stuck. Could be that I'm just dumb or missing something and that I'm doing it all wrong, lol, we shall find out. Thanks again.
2.5.0.3 and 2.6 are buggy 2.5.0.2 is great. There is also a flashable 2.5.0.2 in the link on my Sig below.
sent from my Verizon Galaxy sIV
Dubbsy said:
2.5.0.3 and 2.6 are buggy 2.5.0.2 is great. There is also a flashable 2.5.0.2 in the link on my Sig below.
sent from my Verizon Galaxy sIV
Click to expand...
Click to collapse
Awesome! So Dubbsy have you had issues with the newer builds then too?
Also, just so I make sure that I remember how to do it correctly, I just flash the zip in recovery right? I have been spoiled with goomanager and rommanager.
Thanks.
I was pondering RUU'ing back to complete, absolute stock... I feel maybe I've lost a little bit of the push from this phone after 1,000's of rom flashes... I mean, sometimes 4 or 5 a day.. It's an addiction.. I guess? Either way, would there be any specific benefit to doing this or would it just be something for my piece of mind.. Something I've been running through the old brain here..
I don't think its good to be flashing your phone that much when I pick a ROM I stay on it for months. Though if your not having any issues with your phone I would not return it back to stock just limit your flashing a little bit.?
Sent from my Nexus 7 using XDA Premium 4 mobile app
jbarcus81 said:
I was pondering RUU'ing back to complete, absolute stock... I feel maybe I've lost a little bit of the push from this phone after 1,000's of rom flashes... I mean, sometimes 4 or 5 a day.. It's an addiction.. I guess? Either way, would there be any specific benefit to doing this or would it just be something for my piece of mind.. Something I've been running through the old brain here..
Click to expand...
Click to collapse
I did this about a month ago just to update everything. I guess knowing all the stuff is up to date gave me some solace.... Lol
Sent from my HTC6435LVW using xda premium
LuckyPuppy said:
I did this about a month ago just to update everything. I guess knowing all the stuff is up to date gave me some solace.... Lol
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That's what I mean.. I wonder if it actually clears up unknown issues that may just be small enough to be noticed... Or if it just makes us feel warm and fuzzy?
The only thing updated was radio and hboot. Radio fixes SIM card issues.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
I have wondered the same thing... As a fellow flashing addict... Although I have learned a lot about recovering after fatal mistakes. I now feel confident taking more risks knowing that if I screw up, I can fix it
Sent from my BEAST MODE DROID DNA running CM11 ReBorn themed kitkat protected by my new (used) tempered glass screen protector/otterbox combo
DO IT
RUUing should really only bring back the stock radio and hboot. Whenever you flash a ROM everything else is included (system, kernel, apps) and replaces the stock ones, so its not like you were missing something.
orangechoochoo said:
RUUing should really only bring back the stock radio and hboot. Whenever you flash a ROM everything else is included (system, kernel, apps) and replaces the stock ones, so its not like you were missing something.
Click to expand...
Click to collapse
This. And the latest radio only supposedly fixes sim card detection. So you better off fastboot radio and hboot. Then clear everything. cache data system sdcard. flash a clean install.
thayl0 said:
Then clear everything. cache data system sdcard. flash a clean install.
Click to expand...
Click to collapse
You don't want to wipe the SD card unless you're prepared to side load a rom, but otherwise correct. Wipe data, cache, dalvik, and system.
I have yet to "upgrade" past 1.15, but I have flashed the new radios and maybe a hundred ROMs. I've never had a problem since I wipe data, system, dalvik, and cache, and I NEVER restore any apps or data no matter how inconsequential I "think" it may be.
jbarcus81 said:
I was pondering RUU'ing back to complete, absolute stock... I feel maybe I've lost a little bit of the push from this phone after 1,000's of rom flashes... I mean, sometimes 4 or 5 a day.. It's an addiction.. I guess? Either way, would there be any specific benefit to doing this or would it just be something for my piece of mind.. Something I've been running through the old brain here..
Click to expand...
Click to collapse
Gonna have to agree with Thay10 and Orangechoochoo on this one.
I've also flashed, and reflashed, many many ROMs. I'm currently using the 3.06 radio, and the Engineered HBoot. Running Viper2.5.0 on one DNA, and CM11.0 nightly on the other.
I see no benefit whatsoever in returning to a "stock" or a "matched setup". The whole idea of unlocking the device is to get away from the norm, and allow customization. Mix and match if you will. Maybe an older radio works better in your area. You're unlocked so you can do what works best for you, not what works best for "most consumers".
Running an RUU, just to run an RUU, makes no real sense to me.
Again, just my opinion.
Enjoy...