[Q] Flashed RocketRom, Now running slow. - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

This is probably a bad flash, but I want your guy's opinions on it as well. I installed the new ROM last week, but something went wrong and it got stuck in a boot loop for over half an hour. I finally decided to just pull the battery and try again. Still a boot loop. Went into recovery and cleared the cache, and it started up. Everything has been working, but about half the time the phone is slow and unresponsive while opening/closing apps, and can be a little laggy while switching screens. Even while using apps, things like the keyboard will be slow. For example, sometimes when sending a message, everything freezes for a second before becoming responsive again.
Suggestions?

Sounds like a bad flash, running very smoothly on V15 for me, yet to update to V16 - perhaps re-flash to a newer version?

Try a full wipe (you will lose your apps and settings)
Sent from my GT-N7000 using Tapatalk

Thanks for the replies. Ill see if I can get it updated to v17.

just make sure you full wipe before. it's worth it

mfractal said:
just make sure you full wipe before. it's worth it
Click to expand...
Click to collapse
What is the easiest way to do a full wipe? Will formatting the sd card work or is that not full enough?

You need to enter recovery and do a full wipe from there. To enter recovery press the power button and choose this option.
Sent from my GT-N7000 using Tapatalk

Related

Nexus one Boot-Loop

anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.

Stuck on Boot Screen

Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
I've read you can hook up to your pc and mount your sdcard from cwm. Never tried it but if it works you can save your data that way then maybe a master clear/cache or dalvik wipe will help.
Sent from my SAMSUNG-SGH-I897 using XDA App
BumRush said:
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
Click to expand...
Click to collapse
You can mount USB in recovery and get all your stuff off of your SD that way. You can also nandroid your current ROM in CWM and re-flash it, then restore from backup. As far as saving texts and all that, Idk if you can, but I'm sure someone else does.
Also, you could try clearing dalvik, cache, and then running the kernel cleaning script. It's gotten me out of a few binds before. It might help you to where you wouldn't have to flash again.

[Q] CM9 Reboot Issue

I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
I meant ACMEInstaller2 where I wrote Novacom2 ....
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
that may be the route I go. After about 15 reboots it is currently holding steady I have not made any interventions.
As a side issue, I get email notifications but the email app crashes upon opening. Gmail works fine though....
quarlow said:
The only time I got random reboot is if I try to overclock. I went to replace CWM with TWRP today, and checked in CPUspy something quick. I had 36 hours of up time (remember this only dropped 4 days ago). Initially I tried to OC, even only going one step up I got freezes, and reboots. But leaving it at stock frequencies I have zero stability issues.
I would say to start fresh. With a fresh downloaded copy. Go into CWM and wipe data / factory reset, wipe cache, advanced > wipe dalvik, mounts > format system, data, cache, then reinstall, and install the charge fix. Then don't restore anything, and see if that fixes it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
I did a fresh start as above and the CM9 from is running problem free and 10x better than before when I had done the acmeinstaller2 method. Thanks button hit.
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
Try fixing permissions and wiping up cache from CWM, that fixes the reboots after power-on for me.
It used to do it if I left the screen to go off, but is fine now
I too am having reboot issues, but it only happens when I'm doing something. So far trying to open the Photoshop PS Touch app will cause a reboot, clicking settings in boat browser, etc. It's strange as hell.
I as well get the stock android mail client crashing when opened but its notifacations and gmail all work. I just installed maildroid and disabled stock email and seems to work OK
gizmo2431 said:
I just installed CM9 via the Novacom2 method. The tablet seems to reboot itself after a few minutes of being booted up for no apparent reason. I can start up the device, and not even touch one thing, and after a bit it will self reboot.
Anyone experiencing this? Should I do a reinstall? Novacom2 method, or a complete factory reset with CWM?
CM9 runs extremely smooth otherwise, but I can't have it up for more than 5 minutes with a self reboot. It's bizarre.
Thanks in advance people...
Click to expand...
Click to collapse
I have the same issue, but normally when the screen is on, it always reboots when I try to connect to usb storage, I have a galaxy s2 running on stable(nightly had too many bugs). anyone has the same problem?
I usually get reboots when I let the screen turn off due to inactivity. I tried installing TWRP and doing a clean install from there but it rebooted at the setup screen for CM9. I've had reboot issues since I first installed CM9, but its improved a little bit. I did try uninstalling android completely then reinstalling, but still got reboots. Does anyone have any other suggestions?
I think the best thing to do is use ACMEUninstaller to complete remove Android from your TP, then reinstall from scratch. I had reboot issues after upgrading from CM7a2 until I did a complete wipe.

Phone gone crazy. Nothing works CM9+HydraCore

Ok so since today morning apart from calls (through the stock dialer) nothing works on my phone. I didn't change any settings or flash anything. Only thing that happened at night was a Scheduled Titanium App Data Backup, and I used the phone for over an hour after that with no problems.
All third party apps crash open opening. Smart Keyboard crashes every 10 seconds because I guess the service is trying to start the process. Gmail doesn't open. Go SMS, rocket dial, even the widgets don't load.
I tried rebooting a few times. Didn't work!
Tried Wiping Cache and Dalvik. DIDN'T WORK!
Is there any other solution before I do a complete wipe and re-install the rom?
P.S. on CM 9.0 (Stable) with HydraCore v1
did you wipe/factory reset after flashing cm9 ?
Its a must otherwise u will get fc's everywhere
Sent from my GT-N7000 using Tapatalk 2
indiandroid said:
did you wipe/factory reset after flashing cm9 ?
Its a must otherwise u will get fc's everywhere
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Umm I was using this combination ever since HydraCore came out. this problem happened overnight. No kernel or ROM update.
Anyhow I just wiped and re-installed everything as I couldn't wait. I need to use this as a phone not a toy

Nook HD+ Stuck at CM Boot Animation after several app installs

I installed the latest CM 10.2 (cm-10.2-20130827-NIGHTLY-ovation.zip) as well as the newest GApps. Everything seems to work fine until I install a few apps. Unfortunately I can't say if any of the apps could be causing the behavior which is as follows:
I've had this issue a couple of times already and, after becoming frustrated mostly due to the Nook only deciding to boot from the SD every once in about 30 retries, usually resulting in a revert to stock by default, I gave up and reverted to stock. Of course the taste of CM that I got was too sweet to give up completely. So, today I tried again and had the same problem. Seemingly it will work fine until you reboot after installing quite a few apps. I made sure to restart the tablet several times after installing it and everything went as planned. Whenever the play store had finished installing my swathe of apps, I decided to restart and this is when I was met, yet again, with the rotating CM boot animation.
It's quite annoying really, considering how fast it seems when I'm using it. I haven't got CM installed on the tablet's own recovery partition (if it has one -- I've not read up on these things) but have been running it from the SD. I don't know if that makes a difference. I've formatted all the pertinent partitions before starting the ROM for the first time. I delete the data/cache twice all-in-all, once before and once after. Dalvik too.
Basically I'm flummoxed.
Does it boot up after you clear cache?
I no longer saw this issue after unchecking wallpaper quick render under homescreen settings.
Sent from my BN NookHD+ using Tapatalk 4
realeze said:
Does it boot up after you clear cache?
I no longer saw this issue after unchecking wallpaper quick render under homescreen settings.
Sent from my BN NookHD+ using Tapatalk 4
Click to expand...
Click to collapse
I can't clear cache because I keep the recovery on the SD and it decides it doesn't want to boot from it nine times out of ten, even after following the newer instructions for formatting the SD. After a few failed reboots it just reverts to stock. If I flash CMW recovery to the Nook's recovery partition, will I still be able to revert to stock that way? As annoying as it is, it's nice to have that ability.
I'll try a new install today and avoid checking the wallpaper hack because that appears to cause a problem. I had flashed it yesterday and used it for quite a while, installed all my apps and restarted it many times without issue. After checking that I think I restarted and met the endless logo. Will report back later today.
I can confirm that when I leave the quick wallpaper render option unchecked, it does not lead to a catastrophic failure. Strange that I need to reformat the SD each time or it doesn't reliably boot from it. Either way, I've been using this install for a few days now without any unexpected issues.
Thanks for the advice.

Categories

Resources