Hello,
I'm using CM 13.0 (Android 6.0.1) on my lt30p & I have installed TWRP recovery.Few days ago i installed a battry saving app (meant for rooted phones) and I think I changed a wrong setting it my phone.After that my phone is slowed down too much and it freezes most of the time.
1) Yes, I checked the governers / CPU Freq they are normal (not power saving or anything.
2) I reinstalled CM(x2 times) again after doing a full factory reset and a data wipe, BUT THE ISSUE IS STILL THE SAME.
3)RAM is normally working as it should be(at least thats whats shown in the settings menu)
I think i need to WIPE everything from my phone and Re-install everything including recoveries and all.But IDK that will work too.So any expert on this please help me.THanks
I need a solution for this ASAP.Thanks in advance!
Related
Hello, im running on latest Nova HD.
My problem is that my phone shutdown by itself.
This is not SOD - i can turn it back on just by pressing the power button.
Any advices about this? Thank yoU!
Hello, just to add a question. At the moment I have Nova_HD 1.0.3 and the phone freezes and reboots when connected through USB. Anyone else has this problem? Usb-debug deactivated.
Thanks
EDIT: Just reinstalled with full wipe. working OK now..
Shutdown isssue too
Hello!
My biggest problem with O2x is signal loss when on GSM / WCDMA (auto mode) with official GB roms (v20l, v20q).
I routed my phone and installed Nova HD Rebuild 1.0.3. With Nova Kernel I had no wi-fi, with HP 2x and Harsh kernel, my phone is shutting down by itself, after a phone call, the screen remains off (black) and I have to remove the battery to use it again. With all the kernels I had huge battery drain (about 6-8 hours uptime with normal use). Always clean install, full wipe, dalvik cache, battery stats.
Now, I installed official, unrooted v20s Euro Open. I will test it and post my opinion about this rom.
martinesko36 said:
Hello, im running on latest Nova HD.
My problem is that my phone shutdown by itself.
This is not SOD - i can turn it back on just by pressing the power button.
Any advices about this? Thank yoU!
Click to expand...
Click to collapse
BeerFreek said:
Hello, just to add a question. At the moment I have Nova_HD 1.0.3 and the phone freezes and reboots when connected through USB. Anyone else has this problem? Usb-debug deactivated.
Thanks
EDIT: Just reinstalled with full wipe. working OK now..
Click to expand...
Click to collapse
You can try to put higher minimum frequency from 216 to 324 or flash latest Harsh kernel 3.0.34, but not before wiping cache and dalvik
I have noticed that the phone shuts down only when there's no radio signal for more than 5-10min. The phone keeps switching itself off unless I turn on air plane mode.
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
Hey there,
just installed RomAur v1.4.1
1. wipe factory reset
2. Installed
3. reboot
All went fine except that cwm stucked at "Formatting /cache". Read about issues in other threads so I rebooted and installed ROM. Now i'm wondering that all my settings and apps from old ROM are still there. RomAur is installed successfully.
Is that normal or did I miss something? Was expecting a "virgin" phone after install....
Greet
Cube
had the same problem, apart from the formattting cache part didn't crash, it just took an awfull lot of time (20-40 mins, first time I don't know exactly when it stopped, so wide range I know)
I did expect a virgin phone as well, which still hasen't happened after 2 tries
hi, im having a problem, is it normal for a custom rom to heat up my phone after about 5 minutes of using it? i mean while texting?
when it's in sleepmode evything coolsdown, but then after waking it up for about 5-10minutes it heats up, im using the governor
abbysplug and i/o sio. im not connected to the wifi or mobile data(never used data though). i turn off sync for all my accounts and
location is turned off, im currently using Carbon 4.4.2(06022014). and my battery drain is like 3-5minutes for every 1% of its juice. is it
normal? because when im in stock rom my battery last a lot longer. im using set-cpu and greenify as for my battery saving. oh and here's one
more problem, everytime a set a setting for example changing dalvik to ART, after i set it, and rebooted, i check in the setting it's back to dalvik.
also the read-ahead option for extsd everytime i set it up for 4000KB and thick the start on boot, after reboot it goes back to the default, same for my prefered network 2g/3g i always use 2g only but then after several minutes back to 3g again. please if someone can help me.
i did a fullwipe (System, Data, Cache, Dalvik Cache)
im using Aroma GAPPS
and Recovery is TWRP by Android-Andi
and the Rom is by New-Maclaw
For the heating up & battery consumption : It's 1GHz bug. Hung the WiFi and reboot. :good:
For changing from dalvik to ART : update your recovery with NovaFusion's last update and try again. Btw ART is working. :good:
As for the other problems are bugs of the rom : Update the rom and wait for repairs.
jstath1972 said:
For the heating up & battery consumption : It's 1GHz bug. Hung the WiFi and reboot. :good:
For changing from dalvik to ART : update your recovery with NovaFusion's last update and try again. Btw ART is working. :good:
As for the other problems are bugs of the rom : Update the rom and wait for repairs.
Click to expand...
Click to collapse
thanks for the response sir, i don't have a 1ghz bug, mine is playing around 200-1000, just updated my TWRP to 2.7.1 will try again to change the runtime.
Samsung Galaxy S III Mini battery drain problem
This has only happened twice. It could be my phone overheating and that causes my phone to reboot and go from around 60%-70% to exactly 4%.
But maybe its something else, i'm not sure. My phone isnt rooted or anything. But i will root it once i get this fixed.
I have the SIII Mini, Model Number- GT-i8190, android version- 4.1.2. PLEASE HELP
Hi guys, first of all this is my first post here and won't be my last.
I am an Apple/iPhone long time user and want to tryout Android, just because I think it's time for a change , without knowing if I could get used to the new OS and wanting to spend as less as possible on this "endeavor" I bought a second hand Galaxy Note 2 GT-N7100 from a friend, the phone worked perfectly when I bought it, it had Android 4.1.2 on it and I wanted to update it to 4.4.2, did some research on the net about this (learned about the locked bootloader - this wasn't an issue for me coming from the iPhone) and updated the phone using Kies - and this is were the fun begins.
The update failed, and the phone was softbricked but could still go into download and recovery mode, after reading a few hours on the internet, I used Odin to flash a 4.3 stock rom for the n7100 which I downloaded from samsung-updates, the software got installed on the phone but it was very laggy (with the phone opened but locked, when I pressed the power button it took about 7-8 seconds for the display to light-up, the animations were very sluggish and phone was unusable).
I installed another ROM, using Odin, this time a 4.4.2, with the same results (every time I reset to factory setting and wipe cache from recovery - this didn't help).
I then installed clockwork recovery and rooted the phone then installed cyanogenmod 10.1 which worked almost ok but if i locked the phone after a few seconds the phone would restart, wipe cache/restore factory settings didn't help, i installed it again hoping it would be just an issue with the installation but had the same result, phone would restart.
I've followed all tutorials I could find related to this phone and this issue, installed several patches, reinstalled several stock roms, installed Criskelo rom, all with the same result, the phone is very very very slow and freezez after a while or it restarts after i lock the phone.
So, let me just give u some history on the phone, enumerate the symptoms and where I am right now:
History:
The phone was bought from Vodafone Romania, was never rooted and was never updated (before me ) and still has 3 months warranty.
Symptoms:
- Phone is very slow, unusable
- Freezes after the display is locked
- it is not recognized in windows, when I connect it i can hear the windows connect chime but the phone storage is not mounted, in device manager the phone is recognised as "cdc communication interface" which is not installed - i have the samsung drivers installed, and i have tried on other PC's with the same result, I also tried with several data cables - same thing - the phone works ok when in recovery/download mode
- sometimes when the phone is connected to the PC and the screen goes dark a gray battery appears with a "wait circle" and the phone freezes
- in recovery the phone displays 14 bynaries downloaded and also knox warranty void 1
- most of the roms freez in the language selection screen - i boot-up the phone (after i do a restore factory settings) the installing application dialog appears and then the language selection screen appears, then after 5-6 seconds the phone freezes - the freeze is not triggered by something I do it's triggered by time, after 5-6 seconds no matter what I do with the phone the phone freezes, if it makes any difference, exactly before the phone freezes the display brightness goes to the maximum setting.
Where I am right now
- I installed another stock rom, 4.4.2, it worked acceptable for a few minutes (it got passed the initial setup with no issues) then i left it on the desk, the display went dark and the battery thing happened again and the phone froze, i restarted the phone in recovery, did a factory reset, when the phone started it froze on the language selection screen.
I am at this for about a week now and I have no more ideas and no more patience, and run out of threads and tutorials to read, I am 1 step away of using the phone as a paperweight so please help, any idea would be appreciated, even if it's to enlighten me about what happened and telling me that the phone is bricked.
I am willing to try anything even if it is risky and can totally brick the phone, this is not my main phone and it's purpose is to help me understand android, and help me not make the same mistakes next time.
But, if it's possible I would like to fix the phone because even though it's pretty old it's still an ok phone.
Sorry wrong forum. You need N7100, not the n7000. Good luck.