Related
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.
Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?
Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.
unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--
You could use adb to modify your build.prop
Sent from my SGNote
Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
nice to hear that you had this one fixed
Glad to hear its working now.
n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do
lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk
Hello,
I attempted to flash Trickdroid on my Sprint HTC one. I went through all the steps in the Aroma installer and it froze on 10%. I did rebooted back into recovery, did a full wipe attempted restore one of the two nandroid backups I made. After the restore, I would get a blank screen. All that was there was the Status bar. The phone would then reboot. I rebooted into recovery, did restore and cache wipe, and was able to install trickdroid. Now I am experiencing the same issue, a blank screen with just the status bar at the top, then it reboots itself. Is there a way I can fix this?? I'm stumped
Does anyone think this could be a kernel issue? I think it's strange that it would be booting to a blank screen after a nandroid restore. I noticed when I tried reinstalling trickdroid, it gave me an error when installing the kernel. I'm currently downloading a different ROM to try side loading in ADB, I'm also fine with going back to stock, but everyone is saying the stock RUU's arent available. Any help is appreciated. I hope I didn't just brick my new phone.
Here is what my screen looks like when I boot. It only shows reception bars, time and battery %. Everything else is black and it reboots as soon as the screen times out. This is after re-installing trickdroid. If I factory reset, it will show the lock screen but as soon as I unlock or let it sit it will bootloop. If I try to do a nandroid recovery, it does the same thing, but I am able to get to the drop down and go to settings. It will then reboot itself after about a minute.
You may find this guide useful
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
http://forum.xda-developers.com/showthread.php?p=41076144
Sent from my HTC One using xda app-developers app
still softbricked
Ahhh! this is getting really annoying and I am starting to freak out!!.
Still getting softbrick black screen followed by automatic reboot
1. tried nandroid backup one
2. tried nandroid backup two
2. erase cache, factory rest-blank screen
3. tried reinstalling trickdroid-blank screen,
4. erase cache, factory reset-side load android revolutrion- AROMA freezes
5 had to reflash recovery because couldn't access even after fastboot erase cache
6. adb sideloaded Android revolution, after install phone got stuck in fastboot,
7. tried erase cache, still stuck in fastboot. Won't boot into anything else...
CAN SOMEONE PLEASE HELP ME OR CONFIRM I AM ON THE RIGHT TRACK!!!!!!!
Even though both trickdroid and android revolution both say all phone variants are supported, apparently this doesn't mean sprint There is an entire section for Sprint HTC one. For anyone else who has this issue, the RUU was found here http://forum.xda-developers.com/showthread.php?t=2250904&highlight=ruu . I am up an running again! For all of you who replied, thanks for the help through this mini crisis I just had I guess that's what I get for being a XDA member for 3 years and never submitting a single post.
I have seen a few threads on this, but none that seem to fit my situation. I am new to the Nexus 6, but not to Android and rooting.
My setup: 64GB Nexus 6 with Android 5.1.1 LYZ28E on T-Mobile, rooted with Chainfire, Xposed SDK22 with Installer 3.0 Alpha 2, GravityBox, MultiWindowSidebar, and XHaloFloatingWindow. I also have MultiROM v32b and the modified TWRP recovery with Android M on the second partition, but I haven't used M yet.
The phone works fine when it's up and running, but when I reboot it gets stuck on the spinning balls forever. While it's stuck, if I hold power and volume down to put it into bootloader and power off from there, it will then boot completely but always optimizes all apps first.
Clearing cache and Dalvik cache in TWRP makes no difference. If I put it in bootloader and do "fastboot format cache" it boots fine and doesn't optimize apps (which seems weird to me). In that case I rebooted with "fastboot reboot", so maybe that caused it. However the next time I reboot normally, it sticks on the spinning balls again and I am back to where I started.
I am willing to try "fastboot format userdata" if it might help, but can someone tell me how to backup and restore my data first? Advanced restore from TWRP maybe?
Any ideas on how to troubleshoot or fix this, other than completely wiping and starting over again? I'm not convinced that would fix it anyway.
Try disabling xposed and test reboot.
danarama said:
Try disabling xposed and test reboot.
Click to expand...
Click to collapse
Thanks Dan, that fixed it! Now to enable it and one module at a time to find the culprit.
BTW, for anyone else interested in this, I used the zip files in post #18 of this thread: http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
I rooted my Z1 with pre rooted 5.1.1 Stock Rom. Everything was fine, until this night. I installed some xPosed modules then rebooted. But it got into bootloop, so i disabled xPosed Framework from recovery. Then it turned on. But few mins later when I tried a reboot (nothing special just reboot) it got me into bootloop. Disabling framework did not work. So I wiped out delvik, cache and system and installed backup file. It installed and after several minutes phone got turned on. But I couldnt see any files like storage, downloads or pics. I searched a bit and find out that I need to reboot. And it got stuck in bootloop again. So I need to follow these steps every time I want to use my phone. Cant even see files inside the storage. I can get into recovery.
Thanks.
install the rom again and try again or try installing xposed this onehttp://forum.xda-developers.com/xperia-z1/general/how-to-install-xposed-frameworks-xperia-t3372030 its stable worked on my xperia z1 c6092 do this after factory reset to reset the customizations
if it helped just give a thanks
Problem solved.