Edit: I solved it by going back to Stock rom, Android 2.2.1 Froyo. It didn't happen anymore, so it must be some software related issue which remained on the phone even after fully wipe including the OS. Now I will just need to root the phone again and flash custom roms on it.
Hi there,
When I bought my Samsung Galaxy S back then it came with Android 2.2 Froyo (or it was Eclair, don't remember), which I updated to 2.3 Gingerbread. Since then I flashed newer Android roms found on this forum. I never had any problems. So I had ICS (various versions), JB (various versions) and KitKat (I think I was on 4.4.0 and later on 4.4.4)
So up to Android KitKat 4.4.0 I used it on daily basis but after I got a new phone I didn't use it much anymore (I would only turn it on to make sure the battery won't die). But recently I turned it on, I can do things on the phone but when I leave the phone on standby it would eventually reboot on its own.
I tried installing an older version of KitKat. I picked one from an older date, which happened to be 4.4.2. The same issue happens there too. I just installed Android 6.0.1. made by Full Advance. and the issue happens there too.
My phone has an SD card inserted but no SimCard, anything else you need to know just ask.
I would like to keep Android 6.0.1 from Full Advance. It seems a fast and stable rom. It feels faster than the KitKat 4.4.4 I had.
I would be glad if the issue on the self reboot would be solved. I want to use this phone as a MP3 player. I really like AudioFX.
Any help appreciated, thanks!
Related
Have a stock unrooted at&t N1, with 2.1-update1 firmware, EPE54B build. Daily have to go into process manager and kill apps to get the phone to respond. Seems a ton of apps are running and even though some may not consume memory (empty), the phone locks up and won't respond to touchscreen inputs.
Wondered if rooting and using a custom ROM like Cyanogen or some new build like FRF83 will finally get the phone to work without frequent memory clearing.
Will waiting for OTA fix the problem? Is this a common problem with stock firmware?
Trying to get a last minute response that will help me decide to root and update manually. Any help is appreciated.
I used to have a rooted Lollipop stock rom and then got the gearvr and it didnt work until I re-flashed the un-rooted firmware again , this caused me to reinstall everything from scratch , now a friend suggested i should try un-rooting option found in KingUser or SuperUser whenever I needed to use Gearvr (untested , just a thought).
so anybody tried this ?
I just dont want to have to reinstall everything once more , its pretty much annoying
Thanks in advance
Gear VR is only usable with MM and up. My S7 is rooted and it works wonderfully
I use it on Lollipop without any trouble , it gives me 3 hours of un-interrupted game play. when i upgraded to MarshMallow i could hardly make it to 40 minutes and it heated up like crazy . so my problem was last time i rooted it got stuck at splash screen .
I couldnt get the oculus software to install on my Note 5 with the first firmware (OI6 maybe?) I was able to use Cardboard etc.
I'm using a MOAR custom MM 6.0.1 ROM (which your phone has to be rooted since it's custom, for people that don't know) and it hasn't stopped me from installing the oculus software and using it. BUT I am having issues with it freezing after calibration, videos not starting etc.
Not sure if it's related to custom ROM or MM, other people seem to be having the same problems. I think I'm having more problems with the USB connectivity, I turned off "USB debugging" and that solved a lot.
When i got the phone the other day, it was running Tmo official 7.0. But the bloatware drove me to mod within minutes. I rooted it in short order successfully but since rooting, ive been having issues getting most ROMS to run, except for a few Adzcache had up on Androidfilehost. Those roms seem to be for the g920w8. but at least they boot and run, though only up to 6.0.1. My question is, whether i have an option to get a 7.0 ROM running on this. Any help or input is appreciated. Ive tried many roms, both odin loaded and flashed with twrp. so far only Adzcaches seem to stick. Ideally, I'm looking for a LOS15 ROM if at all possible or this bad boy. Again, thanks for any input in advance.
Hey,
I'm trying to install LOS on my ME176C, but it looks like that I need to be on 5.0 first. The problem is that back in the days I upgraded to 5.0 on release, but for whatever reason it bugged and the tab very often restarted itself. I later fried my mobo, so I don't know if this was fixed, but I have a new mobo now with 4.4.
Anyway, before doing anything I want a backup of stock 4.4, because it's questionable whether stock 5.0 will work properly, but apparently I need 5.0 to even download the unlocked bootloader (according to this), let alone to install TWRP to make backups.
Is there any way I can make backups of 4.4?
Hi,
I did some work on upgrading a LG P505R and I messed up with some stuff and hardbricked it quite few times but managed to recover it by digging a lot here and there and using the right tools, and I got clockworkmod 6.0.4 working and from there problems with colors began, I managed to use it to install a new ROM (Kitkat 4.4.4) after ( installing an upgrade earlier via kdz method on top of the stock firmware from Rogers so it became AT&T phone and worked fine but of course was very outdated and useless)...
So I installed CM-11-P500-Ver12 by sideloading via cwm and things went fine but all was in low color mode and kept going thinking that once the new OS is setup it will install the drivers for the "gpu" and everything will be fine but now I am stuck again ( I like learning this way and I don't mind if I brick it again )...
I just would like to know if there is a fix for this colors issue or just some more information about why did this happen and how it did spread from the recovery to the OS... I am pretty sure it's not coming from faulty hardware!