I have multiple questions pertaining to root and ROMs, any advice on any one of them would be appreciated. My questions surround a Samsung Galaxy S 4G, and a Nexus 7 (2012).
Samsung Galaxy S
ROM Manager
The SGS4G XDA forums have coined it as the "ROM Mangler", my model of Galaxy S is not a compatible device. However, every ROM I've flashed so far has included Clockworkmod5 or Clockworkmod6 (which are only accessible through Recovery). I naturally want to use this app to manage my ROMs on this device, but am wondering if I should or if I will be able to?
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
I read a comment from a guy on Youtube that said he rooted his Nexus 7, but eventually received a software update from Google. He said he had to re-root his device after this. I am assuming the notification never went away, and he decided to install the update. How would I prevent something like this from happening? Should I install a ROM immediately after rooting??
Internal Storage
My Nexus 7 doesn't have an SD card, but has 32GB of internal storage space. My file explorer shows that the device has an 'sdcard' folder, but wouldn't that folder be wiped if I decided to root and flash a ROM on this device?? How would I prevent this scenario from happening?
General
Busybox
What is Busybox, and should it be installed? I watched a Youtube video suggesting to install it anyway, but I highly doubt I will ever use or need it. After rooting my Galaxy, I noticed Busybox was automatically installed. However after flashing several ROMs, I notice that some of them don't come with Busybox pre-installed.
Cyanogenmod
I currently have an unofficial Cyanogenmod 10.1 (w/Android 4.2.2) ROM installed on my Galaxy. But what is Cyanogenmod exactly, and why is it a big name in the ROM community? I've heard a lot about AOKP too.
SuperUser
My current ROM is missing a Superuser app. Should I install a Superuser app, and does it matter which one I choose?
If a Superuser app has already been pre-installed with a ROM, is updating to the Play Store version a good idea? Are there any consequences to installing a different superuser like Super SU or SuperUser from Clockworkmod? Is uninstalling one Superuser for another a good idea?
bump
Double44 said:
I have multiple questions pertaining to root and ROMs, any advice on any one of them would be appreciated. My questions surround a Samsung Galaxy S 4G, and a Nexus 7 (2012).
Samsung Galaxy S
ROM Manager
The SGS4G XDA forums have coined it as the "ROM Mangler", my model of Galaxy S is not a compatible device. However, every ROM I've flashed so far has included Clockworkmod5 or Clockworkmod6 (which are only accessible through Recovery). I naturally want to use this app to manage my ROMs on this device, but am wondering if I should or if I will be able to?
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
I read a comment from a guy on Youtube that said he rooted his Nexus 7, but eventually received a software update from Google. He said he had to re-root his device after this. I am assuming the notification never went away, and he decided to install the update. How would I prevent something like this from happening? Should I install a ROM immediately after rooting??
Internal Storage
My Nexus 7 doesn't have an SD card, but has 32GB of internal storage space. My file explorer shows that the device has an 'sdcard' folder, but wouldn't that folder be wiped if I decided to root and flash a ROM on this device?? How would I prevent this scenario from happening?
General
Busybox
What is Busybox, and should it be installed? I watched a Youtube video suggesting to install it anyway, but I highly doubt I will ever use or need it. After rooting my Galaxy, I noticed Busybox was automatically installed. However after flashing several ROMs, I notice that some of them don't come with Busybox pre-installed.
Cyanogenmod
I currently have an unofficial Cyanogenmod 10.1 (w/Android 4.2.2) ROM installed on my Galaxy. But what is Cyanogenmod exactly, and why is it a big name in the ROM community? I've heard a lot about AOKP too.
SuperUser
My current ROM is missing a Superuser app. Should I install a Superuser app, and does it matter which one I choose?
If a Superuser app has already been pre-installed with a ROM, is updating to the Play Store version a good idea? Are there any consequences to installing a different superuser like Super SU or SuperUser from Clockworkmod? Is uninstalling one Superuser for another a good idea?
Click to expand...
Click to collapse
To answer your questions:
Samsung Galaxy S
ROM Manager
ROM Manger has been buggy for a while now and can cause a lot of problems on certain devices, I would personally avoid it for the time being. That being said the best way to manage your ROM's (And any other Kernel, or MOD's you may want to flash) is too boot your device into recovery mode by using the key combination described in this post, or by running the following command from ADB on your computer:
Code:
adb reboot recovery
Once in recovery, you can flash any ROM that you pushed to your phones sdcard. Make sure to always perform a NANDROID backup of your current setup in recovery mode, before installing a new ROM, Kernel, or other MOD (Such as editing your build.prop file). Also before flashing anything in recovery make sure it is intended for your device and that you read and re-read, and re-read again the instructions on how to properly flash the file.
Nexus 7, and other Google/Nexus devices
OTA (over-the-air) software updates
It is always assumed that any OTA update you apply will break root and that you will have to re-gain root access by re-rooting your device. You can disable OTA updates a couple of different ways. One method is to use an app such as FOTAkill to prevent OTA updates from happening. Another method is to use an app such as Titanium Backup to freeze and disable certain system apps that control OTA updates from being sent and received. Lastly, you can install a custom ROM to prevent OTA updates from being pushed to your device.
Internal Storage
This is a great question. The way the Nexus 7 and other devices that don't have an actual physical sdcard slot handle this is the sdcard folder you see in the file explorer acts as an emulated sdcard. So this way when you go to install a custom ROM in recovery mode when the ROM installation requires you to wipe everything the contents of the emulated sdcard will be untouched and remain as if it were a actual physical sdcard.
General
Busybox
Busybox is a series of stripped down GNU utilities and command line applets, you can find more about Busybox and what it is here. As far as needing it in the beginning you might not need it but as you get more familiar with modifying devices is comes in very handy for performing certain operations and tasks and is worth installing just to have for it's functionality. A lot of root programs push the su binary, a Superuser.apk, and often times the busybox binary. Not all ROM's choose to include busybox but it's handy to have like I mentioned for it's functionality.
Cyanogenmod
Cyanogenmod is an aftermarket firmware distribution you can find more about it here. As for why is it famous it was one of the first well know custom ROM's and soon grew to include support for a vast amount of devices you can find more about the history of Cyanogenmod here. AOKP is another well know ROM that stands for Android Open Kang Project, it first came about when Android 4.0 Ice Cream Sandwich was released you can learn more about AOKP here.
SuperUser
If your current ROM is missing a Superuser app you may install one from the Play Store, it does not matter which one you choose it is personnel preference but I would use either Chainfire's SuperSU app or Koush's Superuser app. Updating a pre-installed Superuser app to the latest Play Store version is fine. There are no consequences to installing one Superuser app and uninstalling another one it's a matter of personnel preference which one you want to use. Keep in mind if you uninstall one Superuser app and then install a different one it may ask you to update the su binary (Which it should ask you if you want to do that once you launch the app for the first time) before it will function properly.
If you have any other questions let me know I'll be happy to answer them or elaborate on anything that may still be unclear to you.
Related
Hi I have bought a HTC desire rooted with cyanogenmod 7 and clockwork mod 5.0.2.0, I don't really understand what all of this means or does to the phone but I don't know what ROMs are maybe cyanogen is the ROM but I went to ROM manager and a list of ROMs came up that I can download, like cyanogen night or whatever it was called, how will downloading these change my phone and which ROMs are better than others.
P.S sorry for all the stupid questions just want to try new things with my phone. Also I don't know if this thread is in the right section :/
Hello,
Firstly you are in the right section . To clear up some of the terms you are unfamiliar with here are some short definitions.
A ROM stands for Read-Only Memory in computing terms and in the case of android refers to a custom operating system, both cyanogenmod and clockwork mod are ROM's.
Root describes the process in which you gain access to the system files (a term called super user access) on the stock version of your android device. The point of rooting is to get extra features both software and hardware related that were previously inaccessable. Such as backing up your files or support drivers for certain hardware.
You say your phone came rooted with those 2 roms applied therefore you dont need to either root or install a ROM, unless you want to change them which i dont advise untill you gain some knowledge of how they work. You would have to google your aforementioned ROM's to get to know what they change, but as of now i can tell you that you can run special apps of the android market that say they are for rooted users only (of course make sure your phone is supported).
If all this sounds confusing think of a ROM being Windows 7 and root being the reformat process that allows you to install Windows 7.
I've just tried to download my first rented movie on Google's Play Videos. I got the error that many have gotten for a long time "won't install on rooted device." I know that the OTARootKeeper exists for truly rooted devices, but my Nook isn't really "rooted," right?!? because it's still the original NT, just booted with Team B's SD Card CM7 most recent release.
My question is, should i used OTARootKeeper to allow me to download rented videos or is there a better way to handle this "bump in the road" of not being able to download a rented moving?
I am a noobie, however I've done lots of looking on line as well as searching forums and reading about past people's challenges with Google Play (Market).
As a final note, I do want to download b/c I want to watch on a plane flight vs stream through YouTube or watch live streaming.
Thank you for your help in advance!
To address the first part of your premise, your device is rooted.
Root means "root access" i.e. you have access to the root directory of the device. What you and many others think it means is "stock rom rooted" but this is a misinterpretation of the meaning "rooted." Your device is running CM7 which happens to be a "rooted" rom. In fact, the official Cyanogenmod team has decided to make future rom releases "not rooted" on upon initial flashing, though root access can be gained by toggling it in developer settings. I have even come across "unrooted" custom roms, meaning that they are custom versions of android, but much like many manufacturer ones, root access is not enabled "out of the box."
Now as to using Google Videos, I believe voodoo rootkeeper does not work for this purpose anymore. I think there is an app called "Super SU" that allows it, but I don't remember the exact setting you need to toggle to enable it. I'll report back after I test on my tablet.
Edit: So this is the app you want to use. In it, go to settings and toggle "Enable Superuser." You should then be able to use Google Movies. When you're done, just go back to SuperSU and toggle that setting again.
error --
Thank you so much first for the Rooted clarification and second for the SuperSU install information. Once I download from SuperSU and open it, I get the following error from SuperSU and am not sure what to do about it..."There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Help please!
I am having the same issue on my Nook Color. I've tried SuperSU but it fails on the binary installation. When I try using Voodoo I get an SU Protected error.
Am I missing something? This process is usually brainless and I really would like to rent a movie through Google Play to watch on my trip.
Any help on temporarily circumventing the root issue would be greatly appreciated. Is this a CM7 issue?
Sent from my NookColor using XDA
still needing help - pretty please!
EDITED: I'm wondering if a solution from another post may work for this challenge. Some people have had trouble downloading certain apps so they edited the build.prop to remove any "Nook Tablet" and replaced it with "XOOM" and said from that point they didn't have any trouble downloading. Unfortunately I'm not quite enough of an expert to know how to edit the build.prop on my device, so I'm wondering if someone can help me figure it out. cheers!
Cubanluke88 said:
To address the first part of your premise, your device is rooted.
Root means "root access" i.e. you have access to the root directory of the device. What you and many others think it means is "stock rom rooted" but this is a misinterpretation of the meaning "rooted." Your device is running CM7 which happens to be a "rooted" rom. In fact, the official Cyanogenmod team has decided to make future rom releases "not rooted" on upon initial flashing, though root access can be gained by toggling it in developer settings. I have even come across "unrooted" custom roms, meaning that they are custom versions of android, but much like many manufacturer ones, root access is not enabled "out of the box."
Now as to using Google Videos, I believe voodoo rootkeeper does not work for this purpose anymore. I think there is an app called "Super SU" that allows it, but I don't remember the exact setting you need to toggle to enable it. I'll report back after I test on my tablet.
Edit: So this is the app you want to use. In it, go to settings and toggle "Enable Superuser." You should then be able to use Google Movies. When you're done, just go back to SuperSU and toggle that setting again.
Click to expand...
Click to collapse
Thank you so much first for the Rooted clarification and second for the SuperSU install information. Once I download from SuperSU and open it, I get the following error from SuperSU and am not sure what to do about it..."There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Help please!
Hi All,
i have an issue - i installed custom ROM, custom kernel, all is working except root.
I have two root apps - superuser (standard) and one from ROM supersu. One came with ROM, and i flashed another (standard) just after flash (not sure why really)
So - I have two supersusers - bot don't have root... irony
Any suggestion how to fix that? Also, how should i delete superuser (standard) from system/app folder (without root apparently)?
Thanks all!
"This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me. It is impossible for an app to be installed in /system/app by the Play store. In fact, the entire /system partition is read only at runtime. The only way for an app to be placed in /system/app is via a rooting process (which usually installs Superuser), or by remounting the system partition as read/write and manually putting it there."
this is from the play store page. I guess you could try using root explorer to delete it but don't know if it will work
The more important question is why don't you have root? You have two root apps installed on a custom ROM. You should be able to run SuperSU and let it update the su binary. Then you can use ROM Toolbox or TB to remove Superuser.
Posted using Tapatalk 2
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Jsparta26 said:
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Click to expand...
Click to collapse
That's already been suggested in the ROM thread on another site, but he seems to be trying to get around it without reinstalling the ROM. He said over there that he doesn't know why he installed SuperUser since the ROM came with another su app and neither do I. He should just go ahead and reflash the ROM.
For some reason this guy seems to want to do things differently from standard practices and then ask for help when it doesn't work. His latest post in the other thread was asking if he could flash the ROM after removing the kernel (boot.img)!
I'm not sure where he comes up with these ideas but he seems to be off doing his own thing even though he is new at this stuff. I'm not suggesting that you don't help him, but wanted you to be aware that he may be creating problems for himself.
ramjet73
Thanks for the heads up. Your right, it don't make sense to try something different if what we suggest to somebody has been a better and usually a full proof way of fixing a problem. But like you said if he wants to add to his own problems that's on him. Let's make this clear to him too since he is new. Nobody on this site or other sites are responsible if you blow up your device, your gf leaves you, or you burn down your house and get fired. :highfive:
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
geske001 said:
I have a Note 2 (obviously), and I have rooted my phone the first day I got it and have never updated the phone since I purchased it. So, I am still on 4.1.2. My phone has been super laggy and I want to take the oppurtunity the when I reset my phone that I can take advatages of the new features that mobile phones have by upgrading all the way to 5.1.x.
So, I downloaded CM 12.1 by wilson3q with 5.1 system. I first tried the 5.0 version since the 5.1 looked too new, and did not have time to deal with the bugs. When I flashed the 5.0 version, I got errors of not being able to flash gapps for 5.0 and that I lost my root. I tried downloading the new TWRP to see if I can get a newer version that would work better, but no luck. I got an error saying that I lost my root privileges and did I want TWRP to fix it. I slid yes to fix, but no luck.
The same problem occurred when I tried with 5.1.
So, I ended up restoring my nandroid backup and I am back on 4.1.2 again with root working again.
I am thinking that I am probably supposed to 'step up' the updates, but not sure. Does anyone have a solution or a link to the solution that they can help with?
PS: I did not like the camera that came with the new mod. I do like the stock one. Are there flashes of cameras that I can use as well when I do end up upgrading?
Thank you in advance!!!
Click to expand...
Click to collapse
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
jheide44 said:
Try Phiz recovery, I've never had trouble with "[I605][CWM Advanced Edition] PhilZ Touch". If I recall we had to start using that one when kit-kat was released (i reserve the right to recall poorly)
I have a link to download mirror here:
http://forum.xda-developers.com/showpost.php?p=60899023&postcount=146
from your new recovery, you should be able to install CM12.1 and 5.1 gaaps recommended in the Wilson3Q i605 thread. from here:
http://forum.xda-developers.com/note-2-verizon/development/rom-unofficial-build-i605-t3069506
FWIW, I am on the 20150803 build and still using the GApps Minimal Edition 2015-04-04 for Android 5.1 (91 MB) from here:
http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
with no issues to report.
You may also need to track down updated radios (to flash from CWM). I think you can find a link to the updated ND7 Modem/Baseband here:
http://forum.xda-developers.com/showthread.php?t=2765021
somewhere in middle of first post
Click to expand...
Click to collapse
I assume that you are giving steps in order, BUT I feel that I should flash the radio to 4.4.2 first, in which the link was broken. I have spent a couple hours trying to find another link, but I am afraid that I may be using an incorrect one. Do you have a good link for that, please?
Also, I have ready the newest Samsung 3.10 Odin downloaded and installed, as well as the USB driver installed and downloaded the ADB fastboot. If I remember correctly, I am supposed to move this onto C: and run it to access the device (Note 2). It has been since Android first came out since I have used the ADB though. So, I apologize for the ignorance. So, do I just make sure the adb is in the same directory and run Odin or did I not need ADB and just run Odin?
I also assume that I run the Philz touch after I have gotten to 4.4.2 rooted first. Am I correct by assuming that?
jheide44 said:
Good Luck!
PS you may want to flash superSU from recovery... get the zip from chainfire's xda thread here:
http://forum.xda-developers.com/showthread.php?t=1538053
(I've been dirty flashing for so long I dont' remember if the rom came with SuperSU or superuser... as such I can't recall if I had to flash this zip or not, but I probably did if I had issues with root)
Note you may also need to enable root from the settings menu after enabling developer mode.
there should be a "root access" option (or somehting like that there)
PPS are you also remembering to wipe data & clear cache/dalvik?
I have found zoot's mega wipe useful...
http://forum.xda-developers.com/showthread.php?t=1983489
it is for the N7100/N7105, butI have used it on the i605 quite a bit. Initial test result reported here:
http://forum.xda-developers.com/showpost.php?p=44093932&postcount=117
that said zoot's script is probably overkill
Click to expand...
Click to collapse
Yes, I have done a cache/dalvik wipe a few times (because I have tried reflashing to get it to work with no luck).
I have downloaded the .zip version of superSU as well, and gapps minimal 5.1 with wilson3q's 5.1 ROM. So, I am almost ready to go with the exception of the correct radio upgrade file.
Thank you so much for your help!!! Much appreciated!
PS Will my old WifiTether apk files still work with 5.1 or do I need to get a new one?
Thanks Again!
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
I will try this later. Thank YOU! I have to take kids to practice now.
jheide44 said:
No need for Odin....
http://forum.xda-developers.com/showpost.php?p=35396049&postcount=1
(Good read)
Just flash philz from twrp. Reboot recovery wipe/reset... then flash new ROM gaaps... Wipe/reset... Then reboot.
I can post the radio zip to my site later tonight. I believe you can flash that last, or later (from philz cwm, after getting on cm12.1)
Same as superSU. Check out ROM first. It comes with root that can be enabled in developer options. you can always reboot to recovery later and flash the zip.
PS. WiFi tether built into ROM "hotspot" (no VZW subscription required)
Pps try this for the nd7 radios
https://androidfilehost.com/?fid=23501681358546508
Sent from my SCH-I605 (VZW Note 2) on CM12.1 using Tapatalk
Click to expand...
Click to collapse
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
geske001 said:
Sorry to bother you, but I still am getting errors with Failed root access for Titanium Backup Pro. I also cannot find Developer Options in the settings menu.
I have tried flashing the radio before and after wiping and installing the ROM then gapps then superSU. I get into superSU and it asks me for root access and I grant it, but Titanium Backup Pro still says that it has no root access.
Any ideas? Thank YOU!!
Click to expand...
Click to collapse
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
1- In the Settings app, select About Phone (or About Tablet).
2- Scroll down, and tap the Build number entry seven times. On the seventh tap, you will be notified that "You are now a developer."
3- Return back to the main Settings menu. Developer options and Performance entries should now be visible.
Click to expand...
Click to collapse
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
jheide44 said:
with SuperSU installed, you may need to just need to update binaries. open SuperSU and it should prompt you if necessary. the "normal" option should work (no need to flash from recovery)
for TiBu...
--within SuperSU settings you may need to disable (uncheck) "mount name separation".
--You may also have to enable unknown sources (under settings, security).
-- there might be something to enable for USB debugging as well (TIBU should prompt for it)
FWIW, you can restore user apps/data... but I would not attempt to restore any system data. Personally, I have found it best to get to know a fresh ROM for a while before trying to restore crap from an older ROM . there might be value in re-configuring apps manually and/or restoring them one at a time (after making sure the ROM is working properly) i.e. you won't need any of those aforementioned WiFi tether apps since it is built into the ROM now.
Instructions on enabling developer options in CM ROM, from here: http://wiki.cyanogenmod.org/w/Doc:_developer_options
(that is likely how to enable superuser that is "baked" into the rom, given you already installed SuperSU it may only complicate matters)
You may be rooted and just having TiBu issues. If all else fails you can check with an app. A long time ago, I've used "Simple Root Checker" by SimoneDev to check root/busybox. It is still in the play store.
Good Luck!
Click to expand...
Click to collapse
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
geske001 said:
Thank you! It ended up being my version of Titanium Backup. I downloaded a new version and it is good. As far as restoring is concerned, I do not even want the apps themselves restored from there, because there may be a new version and would like a fresh install of those apps. I just want my data restored. For example, I have a surveillance software that I would just like to restore the entries (IP's usernames and passwords). I would like my email settings to be there, so that I do not have to re setup my 7 email addresses. My Text/SMS messages and my alarms. So, I am not trying to do a full restore.
On another note, I am trying to get my calendars back into my phone with no luck. I cannot install google calendar and get my google calendars to populate into my task widget, and the ROM is not letting me set up my POP email addresses. Also, I see no ringtones, so I have no ringers to ring my phone nor tones for my alarm clock. I flashed gapps for 5.1 and I see nothing extra from the ROM. I thought gapps was google apps. Am I trying to do stuff differently than you? There seems to be a few problems in that manner that I am trying to work with.
I am thinking of downgrading to 5.0. Maybe the 5.1 is too new?
Again, THANK YOU for your help!
Click to expand...
Click to collapse
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
jheide44 said:
I wouldn't downgrade, nobody is actively working on 5.0.2 anymore.... that thread is basically dead. Also, it is likely less "stable"/mature than what you have installed now (that is currently being maintained). i.e. you have the ROM that I would stick with.
like I said I wouldn't restore any thing into system (apps or data)... you can do whatever you please. (but it could be causing you more issues than just biting the bullet & configuring manually) i.e. restoring accounts might result in unanticipated issues, you came from a much older version of android.
all I had to do was install google calendar from play store and then the CM12 calendar stuff all worked (I might have had to restart and/or install the google calendar prior to setting up primary gmail). you might need to remove all your accounts and load them again (a factory reset might be faster though.)
also you might have to update google services and the play store before certain things "play nice".
I know you don't want to hear this but...
from here on out i'll likely point to all your issues being based on restoring system data. (based on my limited knowledge and personal experience). FWIW, I'd try to reconfigure/setup everything manually and you will likely have much better results.
Click to expand...
Click to collapse
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
geske001 said:
I figured that, and feared that and the same time. So, what am I flashing onto the phone with gapps then? Also, one of the reasons I was wanting to go back was because there are a few apps that are not 'compatible' with this system. Meanwhile, I am going to wipe and reset again, and do what you suggested and just reconfigure.
Thanks again!
Click to expand...
Click to collapse
GAaps are the google apps... good read:
http://wiki.rootzwiki.com/Google_Apps
(hopefully I am not out of line for posting a link to that wiki)
many ROMS like CM don't' include gaaps due to licencing/legal issues. which is why the AOSP roms devs often have you flash the GAAPS package separately (also you can pick your package for your fact pattern... full gaaps/minimal gaaps/etc.).
Also the gaaps zip files you flash from recovery install the files into system. a lot of folks like the minimal editions of GAaps because it doesn't force all the apps into system. instead it just gets you up and running with the play store and a few essentials... that lets the user install all the other google apps as user apps, from the play store.
basically taking the "debloat" mentality as far as you can... keep stuff out of system and let the user decide what to install.
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.