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.
Related
I just purchased back after selling 2 years ago this great gadget . It has been one of my extremely rare changes of mind as i underestimated its capabilities...
I have some basic questions in case someone can give me a tip :
I now own a motorola e and have no Samsung device to pair it with , what should i do?
the watch is updated to last tizen fw via kies and is on factory reset form so i have no access to its settings
I need to make it work independantly if this is possible or via the moto e...
I also managed to flash the last tizen rom based here via the instructions
http://forum.xda-developers.com/gal...evelopment/rom-tizenmod-3-0-skin1980-t2850353
my moto e is not rooted running 4.4.4..
thx for any help
On 4.4 you can still make just about everything work properly without a Samsung phone. Never tried without root tho. Your best option without rooting would be simply trying to install gear manager apps the normal way, download and install.
I have best luck with 502 version of gear manager personally, the later versions I never get to work properly. Go to this thread and grab the 502 version as well as gearmanager stub, install both and reboot. Enable bluetooth if you havent, dont connect tho, just enable then run gear manager and it should install whats needed. If it gets stuck saying connecting for longer then 30 seconds or so cancel it and it will finish installing, if not restart gear manager and it will.
On a rooted device you manually drop the files in place, set permissions and reboot then continue. It should work the same. Here is a tutorial on doing it but I don't want the un-needed crap from Samsung running on my phone so I do it the way I posted above and just download the apps I want from here. More maybe available from the galaxy store but honestly, that's enough for me and my needs.
Your other alternative is running null rom on your watch, thats based on Android, more info here. Any needed files can be found on my copy.
In the past, I have had updated a few times on root without facing a single problem, until yesterday, when I received the Lollipop update which weighs 776.73mb and stops updating in the very beginning before running into some error 0x11110000.
So, question is that is it possible to update ON ROOT ?
I know using SuperSU unroot one can't change the LG RCT check, but what's interesting is that after making a second attempt to update, IT STARTS ALL OVER AGAIN. I mean, downloading 776.73mb multiple times isn't going to reduce your data bills
Any ideas ?
Rooted. Stock ROM.
EDIT
Fixed it by performing a full 'unroot' inside of SuperSU and then using the LG PC Tool to update to Lollipop Well, I'm rather surprised that it worked when the same didn't work on the phone itself. So I'm guessing that the process used by the tool overrides all problems as long as the firmware remains stock.
Oh and I really didn't want to mess up that bad by taking the route suggested in that thread, @lfom, because I don't have an extra phone to fall back on, in case my current one fails to work
Modern SU tools also modify other system files, primarily to try to resist to updates... My bet that what is causing the problem is the same as this other thread (it offers a solution too):
http://forum.xda-developers.com/showpost.php?p=44913304&postcount=8
Actually , i updated my phone with root using LG tool, after update i lost my root but all apps where there, which means there is no need for unroot os something like that.
So, I acquired my GT P1000L quite recently (like, 4 days ago), and I started to look for methods on how to upgrade it from 2.3.6 to kitkat 4.4.4. And after hundreds of forums and threads, I finally found one that worked for me. Managed to install CwM recovery, CF root (A big problem that I'll explain later), and proceeded to install everything.
After a lot of cold sweat, since it was my first time doing this kind of upgrade, finally the Cyanogemod logo showed up, took 2 minutes to load everything, and it asked me to choose the language...And my sadness started when I discovered my touch screen stopped working.
So, after crying on the corner like a little kid, I found a tutorial on how to go "restock", I guess that's what is called, rolling all the way back to 2.3.6, Which didn't take that long, everything good and dandy, when I discovered 2 major reasons why it didn't work for me.
1: The CF Root that I used, only works with P1000, not P1000L (at least is what some people in the cf thread said), and CF was the reason why my touch screen stopped working.
So I decided to go back and see if I missed something, and saw a small warning saying that I should at least have CM 10.2 before upgrading to CW 11 (the one for kitkat 4.4.4). And that led me to my second problem, find a ROOT and instal CWM mod and go to 10.2.
So I searched, and found demonlord V4 (I think that's it), root, and tried it...And boom. The Root failed, and I was like WTF?
And when I decided to check the root's log, it said that some folders were protected, read only files (Something that never happened before). So I decided to try another root, Kingo root, and to my surprise, ROOT Failed again.
Tried ADB, Qatbd, none of them seem to work.
How can I root my device again? Or at least remove the read only protection?
The same happened to me! I still working to make my root work again! Anybody that can help us?????!!!!!!!
Take kingo root app on ur pc and root ur phones
Sent from my SM-J500F using XDA Forums
Ummmmm,,,
I think that i can help u...
i am now rooting gt-p1000l with kingo root and i think it's working...
better try with that though
p.s. it is computer version. i already tried with apk and it didn't work
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!
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!