Related
I recently traded my Sammy Moment for a HERO. I am rooted and flashed but found that some ROMS gave me trouble; Fresh being one of them. Looping boot screens and slow performance contrary to what I read about the roms I flash. Is there anything I may be missing? I rooted via ADB and did find an issue while the recovery was flashing it said: MD5 failure and no space; but recovery still flashed and works.
Last I was on XDA was with my G1 and Tilt. Anyone wanna hip me to what I have been missing? By the way I have succefully flashed the BUUF rom and and the Zen, darch booted with FC's and the others looped.
I wiped dalvik and system and reformated my SD.
Does your Hero have "With Google" branding?
Some of the older phones don't. And at that, some of the older chipset phones can't over clock as high, and OC'd roms will cause a boot loop.
That's the only thing I can think of that wil lbe causing the issue.
You should also try to Wipe everything under the wipe menu except maybe rotate and batt stats before you flash a rom. I always try to wipe clean before I flash.
What Kcarpenter said.
I got my Hero the first day out at BB. I can only clock to 710 otherwise phone starts blitzing.
Gorguts said:
...slow performance contrary to what I read about the roms I flash...
Click to expand...
Click to collapse
Yeah, this is just what most of us here have learned to deal with, as this phone model is nearly a year old and built with hardware that isn't quite powerful enough to smoothly handle the software stuff we try to put on it these days. We are still way ahead of regular HTC/Sprint stock though which is nice.
other than what the others have said...
other options to try...
have you tried the DamageControl ROMs? they are very stable.
if issues persist... maybe you have a bad memory card? there were a rash of them and can cause weird issues.
or you have a bad hero! was it new? warranty??
if so.. get warranty trade in. if you can show issues with phone that is not related to flashing and rooting!!!
Try froyo if you don't care about sense. I have yet to have a bootloop flashing nightlies. Flash a new bootloader, wipe dalvic, system and cache. I'd do each several times just to be sure. Use a new download and verify the checksum
Sent from my HERO200 using XDA App
Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
How did you upgrade?
bkgrc said:
Hi,
I have recently updated my galaxy note's firmware to 4.1.2. Eversince the upgrade, the phone hangs several times a day and has slowed down drastically.
There is a huge lag even in simple things like typing on whatsapp, clicking a photo, watching a video, playing music files.
I have seen that there are a few others who have experienced similar problem in Note II.
Can someone please suggest me a way to fix this? I am having to restart the phone atleast 6 times everyday.
Thanks
bkgrc
Click to expand...
Click to collapse
Hi
i have been having the same problem have you found the solution if yes please share it,
i upgraded my galaxy note in February and i have my galaxy note is really slow many time and i have to restart it many times a day...And it gets really hot too.....
Note 1 hangs after upgrade
Hi baz77,
I did the upgrade via samsung kies, connect phone to my PC. few weeks ago.
Thx
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Note 1 hangs after 4.1.2 upgrade
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
Rooting does void your warranty but the process is relatively simple. Follow 1a method in this guide.
the link rcheung28 has provided is the perfect way / safe way
bkgrc said:
@ nokiamodeln91 - thnanks for your response. I am not completely aware of the process of rooting the phone.
Is rooting very complex? Could there be any warranty issues?
Thx
Click to expand...
Click to collapse
If ever you have to return your phone to the service center, simply flash an official wipe ROM through PC Odin (that will remove the root and restore the phone to its "original" state). That's what I did when I had to replace mine (I flashed a Gingerbread ROM, made sure the phone booted fine and I was good to go).
nokiamodeln91 said:
system is too heavy on a stock JB rom.. root it and remove some unused apps like chaton , google plus etc etc..
Click to expand...
Click to collapse
What if I just disable the app instead of root delete? Any idea which app can be disabled without affecting phone normal operation? Thanks
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
jaycm1130 said:
i wonder if restoring factory settings will result to improvements..
and if it is safe now using the JB kernel?..
Click to expand...
Click to collapse
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
I haven't used a stock ROM for while, not because of battery drain (which is mostly app-related and can be checked with BBS), but because it was sluggish compared to CM.
As for the media scanner issue, you can try this app.
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
jaycm1130 said:
did you tried stock kernel?
what is your feedback to it?..
i was wondering if the stock kernel for DXLSE was safe to do factory reset..
Click to expand...
Click to collapse
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
devll said:
Was on stock when I did the factory reset before flashing Philz. Nothing happen to my phone but I cant confirm that nothing is wrong. Maybe its because I got away with it. But I can only let you know that I did the reset on stock JB DXLSE Rom and kernel.
Even after doing the reset. Can still notice the batt drain and sometimes some apps can hang. Theres some laggy interface. Isnt as smooth as when I was on ICS 4.04.
Click to expand...
Click to collapse
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
jaycm1130 said:
maybe the custom kernel that you installed eats a lot of battery and/or the apps that you installed consumes resource even on the background..
try all stock kernel and rom.. let it settle for a week..
try also to replace the battery..
now if you insist in custom kernels, due to the fact that they are proven safe and has working CWM..
try tweaking with the settings.. through its governors,,
try debloating your rom by removing unnecessary bloatwares..
see if either any of this make sense to your device..
Click to expand...
Click to collapse
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
devll said:
Philz kernel is stock kernel with brink bug removed. So basically its a stock one.
For settings. I managed to set it as the same when Iam on ICS 4.04. For bloatware, all are disabled. Practically I set it as the same when Iam on ICS 4.04. Thats why Iam sure the batt drain and slight lag is there.
Hopefully someone here have a solution to it. :fingers-crossed:
Click to expand...
Click to collapse
Philz kernel is stock based kernel not a stock one..
try this app: https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats&hl=en
devll said:
Iam on JB DXLSE. Using Philz kernel DXLSE. Done factory reset but problem is still there. Batt drain quite fast with apps that hang once in a while. Slightly more laggy than ICS. Not the fault of kernel since Philz use stock kernel. Seems to be the problem of Rom. Media service seems to be running too often. But cant disable that app.
Anyone have any problem solving solution?:crying:
Click to expand...
Click to collapse
One thing that I've noticed that I haven't heard people talk about (maybe because it's stupid and non-applicable) is to go into your DCIM folders, both on your SD and in the phone and delete the entire .thumbnails directory. Mine somehow managed to accumulate a good GB or so of thumbs and that appeared to be bogging down media searching.
Even after that, phone has been really laggy lately. Going into running apps, I noticed a "Software Update" process running, even though I know this phone will not OTA update. Killed that process and things were ok again. YMMV.
Hey fellas,
I recently flashed a new rom and wiped my entire phone. Ever sense then my "touch" has been off about a half inch, it always think I am lower than what my finger actually is. I returned to stock and it was fine, I flash everything over again and the problem comes back. The issue seems to be flashing CF Auto-root 78542, has anybody ran into this issue before?
I found a more up to date (78557) version, I will try that and report.
Nope thats not it either.
Make sure you are using the correct version. Normally this occurs because you flashed the wrong model number.
Sent from my SM-N910T using XDA Free mobile app
Thats what I thought but I don't think so. I am going to double check and maybe re download everything
As far as I can tell, everything is good.. N910T
Hell-Razor said:
Hey fellas,
I recently flashed a new rom and wiped my entire phone. Ever sense then my "touch" has been off about a half inch, it always think I am lower than what my finger actually is. I returned to stock and it was fine, I flash everything over again and the problem comes back. The issue seems to be flashing CF Auto-root 78542, has anybody ran into this issue before?
Click to expand...
Click to collapse
Don't worry, here is the fix for it.
I had the exact same problem a few weeks ago.
Go to the dialer screen and click in:
*#2663# screen fix works perfect, it will display a menu, select re-calibrate
or update or something to that effect, ( I forgot the exact wording)
But when you see that menu screen you will know which one to click.
You might have odin flashed the wrong twrp for the phone, but either
way this will fix it.
I would suggest that before you do this, odin flash the n910t
stock samsung firmware, that way twrp will get over-written.
Good luck,
Have a great day!
Will do. I really want to go back to the fire kat rom but I am tired and dont feel like messing around with things anymore. Just want a WORKING phone lol
Its defenetly CF AUTO ROOT. I tried an older and newer version with nothing, what the hell ive never had this issue.
And the *#2663# isnt working.
Hell-Razor said:
Its defenetly CF AUTO ROOT. I tried an older and newer version with nothing, what the hell ive never had this issue.
And the *#2663# isnt working.
Click to expand...
Click to collapse
We both have the identical phones N910T (I am assuming).
If that's the case perhaps you should try it again, be sure to do a
full wipe first and then odin flash the official stock COG2 firmware
before entering the code.
Be sure NOT to odin flash twrp recovery or cf-autoroot
after odin flashing the firmware, don't flash anything
except the odin flash official COG2 firmware until the
problem is solved.
It has to work because it worked for me and I had the
identical problem as you are having now.
Good luck!.
I am almost done downloading the 5.1.1 official t-mo zip. If this doesnt work I will try that.
Thank you by the way
Sweet it worked. Now I just need to figure out how to root the sob so I dont run into this issue anymore.
Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Note 4 sucks after this MM update it is worst than any other small budget phone.
anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
So you'd recommend going back to stock kitkat?
SamC95 said:
Hey guys, been a while since I've been here.
Currently, I'm running stock android 6.0.1 (N910FXXU1DPB1) on my Note 4 (Snapdragon).
I flashed this via Odin (because back then it wasn't released in my country yet). Did the usual, clean reset and when i flashed there were no problems (besides meh battery time). But since a week or two I'm having a lot of problems, a lot of random reboots, reboot time is way too long, battery drainage is awful and random freezes. A lot of these problems occur when using snapchat, not sure why.
So now I'm wondering what is the most stable ROM around. Battery life and smoothness are most important to me. At this point, I don't really care if it's a custom ROM or stock. With my old phone (S3) i had a lot of problems after i started running custom ROMs so I'm hoping you guys have some options where this won't happen.
Thanks in advance, Sam
BTW: Sorry for my bad English, it's not my main language.
Click to expand...
Click to collapse
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
robmeik said:
I use and have been using Alexndr's ROM's for ages! They are reliable have plenty of options (root/no root, odexed/deodexed, xposed or not) ... he regularly updates and sorts out peoples' problems (although I have never had one) and produces a very stable ROM.
His instructions are clear and easily understood and he knows what he is doing! My favourite ROM maker ... Thanks Alexndr!!
Click to expand...
Click to collapse
Thanks for you reply.
Seems like a nice ROM, would want to flash it, but seems like I'm not going to be able to flash new ROMs (due to the problem described above.
I had the same problem. you must have the newest version of odin.
DrQuestion said:
I had the same problem. you must have the newest version of odin.
Click to expand...
Click to collapse
Seriously? Is it that simple lol? I'll try that, thanks.
EDIT: Turned out it wasn't that simple, got the message 'There's no PIT partition.'
anasrizvi said:
Note 4 sucks after this MM update it is worst than any other small budget phone.
Click to expand...
Click to collapse
I've been running Marshmallow on my N910C since it was released for my device, and I haven't experienced any major problems with it. Other than not getting the official OEM spare battery to charge correctly on it. Everything is work just fine.
I've been running the MM PaulPizz Rom for a few days and it's been rock solid so far. Not a single crash or error.
SamC95 said:
Another weird thing happened. Just installed TWRP (once again via Odin), but when I reboot into recovery, I first get the message 'installing system update', then it says 'no command' and then it reboots in Android Recovery. Any ideas how to solve this?
Click to expand...
Click to collapse
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
SamC95 said:
Thanks for your reply.
Alright man, I will try that tomorrow.
I think the download should be okay, downloaded V3.12.3 a few hours ago, or do I need a different one?
And should I also do this if I get the message that there's no PIT partition?
Thanks for your help, I'll let you know if it works or not.
Click to expand...
Click to collapse
I always use 3.11.1 straight from Sam mobile site. Here http://dl.sammobile.com/Odin3-v3.11.1.zip
Never had a problem with it.
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
After trying myriad of roms(Almost all roms from Snapdragon section) + kernels, I prefer Stock rom for it's batterylife + stable performance. I haven't rooted after returning to stock. But i will return some sort of custom rom soon as my phone looks so boring without ported apps, multi dpi compatible apps, etc. If u prefer stable performance move to pure stock, If u need assortment of features use one of the ported note7/S7 roms, If u want slick and fast roms use AOSP/CM based roms but as far my experience goes they are not much stable while compared to touchwiz.
Currently running latest MM stock on 910G.
Stonewolf said:
Stock ROM's all the way.
I've used KK, LL and MM. After upgrading to MM (by mistake) and using it for 2 weeks, had to throw it away! MM is the worst case ever! I've went even back to KK, used about 2 days and went finally for 5.1.1 - best case ever! No lag, no "app stop working", no delay (which with MM was about 3 secs between opening closing apps). But, the 5.1.1 has a little distress about battery drain (about 5% more than KK or MM). Is the only thing is keeping LL for being best version. If you rollback from MM to LL or KK, you MUST untick Auto Reboot! Just let the flash go till the end and then take the battery out; put it back, start with recovery and wipe everything prior booting normally. And for the downgrade you have to use:
1. from MM to LL - Odin 3.11
2. from MM to KK - Odin 3.09
Click to expand...
Click to collapse
Using Odin 3.11 to downgrade from MM to KK works just fine. I just did 2 days ago.
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Stonewolf said:
I had errors with 3.11; once changed to 3.09 worked like a charm. I've posted from my experience. Anyway, good to know other opinions and good to know that works either way (maybe my system had some conflict with vs. 3.11). However, that downgrade was done only to my first device, not the second one. I still keep MM on my second N4.
Click to expand...
Click to collapse
Have you tried 3.12? It's the only one that worked for me.
back to lollipop .......... one of the best Note 4 ROM ever build ...........
Been using Nameless ROM V7 ............
aaron74 said:
Try this. When in Odin, uncheck auto reboot, flash twrp, wait for it to finish, unplug phone, pull battery, then boot into recovery by holding vol up+home+power.
Recovery should stick
Also, double check you have right twrp. Even re download, maybe you got bad download
Click to expand...
Click to collapse
This did the trick, thanks a lot! I finally got to flash TWRP and ended up installing Alexndr ROM (thanks for the tip @robmeik) but sadly I'm still having random reboots