Database Info

Possible to unroot a CM9 ROM to work with Good?

I'm trying to get Good to work with my phone but the method I used to try an unroot my phone was unsuccessful. I don't mind having it restricted. I need to unroot because Good finds all traces of the rooted files and then flags your account as rooted user, locking you out of the application.

youll have to remove the su and the superuser app. i read in a different forum that it will work to trick Good into working.
Sent from my Nexus S 4G

Root it or not.

I am in big dilemma; either to root my tab or not.
There is no bloatware to remove and I dont want to play with it with custom roms like I do in my phone.
But I want to install different launcher which need su power to fix widgets.
So should I root it or not I am soooo much confused.

Sorry I can't answer that for you. I was about to ask the same question but in a slightly different form. This is my first tab ( a tab isn't worth getting if it doesn't have an active digitizer ), and I would like to know whether or not to root. The way I see it is that it breaks down into two lists: pros and cons, which I think is also the way you want to look at it. So aside from a custom rom, what are the pros and cons of rooting your Note?

All I want is different launcher with su power. . Touch wiz is silly. Dont let me resize all widgets and eat my all space.
With out root I cant place widgets on home screen in different launcher.

bikrame said:
I am in big dilemma; either to root my tab or not.
There is no bloatware to remove and I dont want to play with it with custom roms like I do in my phone.
But I want to install different launcher which need su power to fix widgets.
So should I root it or not I am soooo much confused.
Click to expand...
Click to collapse
I'm in the same dire dilemma...
Root Pros:
Many very useful apps require root to access the inner system settings
It allows to see what's behind the curtains of one's Android device (browse and see system files and settings) and (slowly) learn how does it work
Root Cons:
The device can loose its immaculate "official" status, loose the warranty and the OTA updates.
Some app (mainly apps dealing with media contents and concerned with possible copyright infringements) may stop working if they detect a rooted device, by means of the binary counter, that could anyhow be zeroed with "Triangle Away", or by the mere presence of the SuperUser (SuperSU) app.
The ideal way would be to root but, at the same time, being able to completely hide the rooted status of the device; both for Samsung warranty and Ota updates and for those apps that stop working if they "sniff" a rooted device... but I think that's not possible yet...

I find rooting a device also plugs a lot of security exploits too...
If you're able to, taking back to stock is fairly easy but that can be a BIG if sometimes....
Overall I find having root is a big "+". It allows me touse my device how I want and plugs those holes left by Google/Samsung in their OS.
Each person should evaluate if they need to or not but I find it a lot better to root simply for peace of mind... at least if I get a virus that destroys my tab , I'm the one who gave it root access... The blame is mine other than the tab dies mysteriously one day..

Rooting was super simple with the exynos exploit apk, if you didn't update. I rooted using that apk, then used the same developer's MobileOdin app to update while keeping root. For me, I'd say that rooting is very useful on this tablet because you can also enable multiwindow for every single app, something you won't have without rooting..

asdfuogh said:
For me, I'd say that rooting is very useful on this tablet because you can also enable multiwindow for every single app, something you won't have without rooting..
Click to expand...
Click to collapse
I thought you got that with JB?

JB only have a few apps added to have multiwindows then ICS...but if you root you can use multiwindow manager to add multiwindows ability to all apps.

Also adds the ability to freeze unwanted apps, backup OS in case of bad things happening (settings, OS and user data) and to truly set things up as you, the owner and user, want...
Allows 3rd party tracking apps like cerberus to track and remotely wipe sensitive data in case tablet goes missing not to mention turn on GPS to track and get pics of person using it.

In my view worth it for Titanium Backup Pro and Nandroid backup .
Warranty void easy enough to put that right .
OTA updates don't work not a problem this is after all XDA .
jje

I don't see the confusion on your part. It's a simple decision imo. You want an ability to do something that can only be done with root. Just because you root, doesn't mean you have to customize in any other way.
As far as OTA's go that should be a non–issue as well since they are mostly a joke as far as improvement in any significant way. Everything they have is readily available here on XDA and more often than not sooner.

bikrame said:
All I want is different launcher with su power. . Touch wiz is silly. Dont let me resize all widgets and eat my all space.
With out root I cant place widgets on home screen in different launcher.
Click to expand...
Click to collapse
Forgive me if I haven't totally understood what you want.....but you can install any launcher you want without rooting. I have Go Launcher, it allows me to resize Widgets etc.
Sent from my GT-N8010 using xda app-developers app

Markhypnosis said:
Forgive me if I haven't totally understood what you want.....but you can install any launcher you want without rooting. I have Go Launcher, it allows me to resize Widgets etc.
Sent from my GT-N8010 using xda app-developers app
Click to expand...
Click to collapse
Yeah. Do u really need root just to change launcher?
Unless u need it for other reason, I don't think root is needed just for changing the launcher.
But if u want root access, then yes, ur device need to be rooted.
Sent from my GT-N7105 at the corner of this rounded earth

Yup I got that guys. Thank you.
I tried long time ago and it didnt work. Now it does
Sent from my GT-N8013 using xda premium

sphere314 said:
...The ideal way would be to root but, at the same time, being able to completely hide the rooted status of the device; both for Samsung warranty and Ota updates and for those apps that stop working if they "sniff" a rooted device... but I think that's not possible yet...
Click to expand...
Click to collapse
A new possible solution for some Samsung devices is here.
I haven't tried it yet, but, according to the thread posts it seems that:
it can preserve the official status and the binary counter
there's an "unroot" option, so that, if some apps sniffs the rooted status and stops working, you can temporarily unroot and have it work again
If anyone has actually tried it on the GNote 10.1, his comments will be appreciated.

Backup apps and data without root
JJEgan said:
In my view worth it for Titanium Backup Pro and Nandroid backup .
Warranty void easy enough to put that right .
OTA updates don't work not a problem this is after all XDA .
jje
Click to expand...
Click to collapse
You all know that there is a new backup program that does not need root to backup apps and app data.
Its called "Carbon - App Sync and Backup" by ClockworkMod
Here is the link https://play.google.com/store/apps/details?id=com.koushikdutta.backup
It works great.

sphere314 said:
A new possible solution for some Samsung devices is here.
I haven't tried it yet, but, according to the thread posts it seems that:
it can preserve the official status and the binary counter
there's an "unroot" option, so that, if some apps sniffs the rooted status and stops working, you can temporarily unroot and have it work again
If anyone has actually tried it on the GNote 10.1, his comments will be appreciated.
Click to expand...
Click to collapse
kkretch said:
You all know that there is a new backup program that does not need root to backup apps and app data.
Its called "Carbon - App Sync and Backup" by ClockworkMod
Here is the link https://play.google.com/store/apps/details?id=com.koushikdutta.backup
It works great.
Click to expand...
Click to collapse
I've tried them both and I'm really satisfied with the results.
1) before trying the Framaroot app I used Carbon backup to make a full backup of all my apps data (without root).
2) after that, being confident enough I could restore back my tablet apps data (in case something went wrong), I used the Framaroot app to get root.
Result:
1) I could backup my app's data before rooting
2) With Framaroot I have now root access. Anyway, the most important thing is that my device status has remained "Official" (1) and the binary counter is "unchanged" as well!
I wouldn't ever think that it was possible to root a device without having to change the recovery and, by doing so, change the device status/binary counter.
Now I know it's possible
(1) EDIT feb-17-2013
Update: the device status is now "Custom". Yet, after the rooting, I checked and rebooted more than one time. There must be some Android service that checks the presence of root periodically and finds out, sooner or later, if the device is rooted

sphere314 said:
I've tried them both and I'm really satisfied with the results.
1) before trying the Framaroot app I used Carbon backup to make a full backup of all my apps data (without root).
2) after that, being confident enough I could restore back my tablet apps data (in case something went wrong), I used the Framaroot app to get root.
Result:
1) I could backup my app's data before rooting
2) With Framaroot I have now root access. Anyway, et hemost important thing is that my device status has remained "Official" and the binary counter is "unchanged" as well!
I wouldn't ever think that it was possible to root a device without having to change the recovery and, by doing so, change the device status/binary counter.
Now I know it's possible
Click to expand...
Click to collapse
Thank you for the info on framaroot. I read the thread you had linked earlier and decided to try it out on my old Archos 101 gen 8 (since the developer indicated he was able to root this device with framaroot) before attempting to install it on my note. Needless to say, it didn't work on the Archos (tried it twice) and I ended up having to reformat both times because the tablet got stuck in a boot loop. Was installation really that smooth on your note and can you confirm that you're running JB 4.1.2 not 4.1.1 (saw your post in the framaroot thread).

mke1973 said:
Thank you for the info on framaroot. I read the thread you had linked earlier and decided to try it out on my old Archos 101 gen 8 (since the developer indicated he was able to root this device with framaroot) before attempting to install it on my note. Needless to say, it didn't work on the Archos (tried it twice) and I ended up having to reformat both times because the tablet got stuck in a boot loop. Was installation really that smooth on your note and can you confirm that you're running JB 4.1.2 not 4.1.1 (saw your post in the framaroot thread).
Click to expand...
Click to collapse
As I said in the other thread I'm not 100% sure about JB 4.1.1 or 4.1.2.
All I'm sure of is that the firmware code is N8000XXCLL3-N8000ITVCLL1
According to Sammobile it is 4.1.1 but according to Samsung-updates it is 4.1.2. In the tablet, in the "Settings - About device" page the Android version reported is 4.1.2.
Since I'm now rooted maybe I could find out the real Android version (beneath Samsung's touchwiz) by having a quick look at some of the system file... if anyone could tell me where to look .
Anyway I can confirm that my rooting process was really smooth, that it took less than a minute and that my Note's Status has stayed "Official". (1)
Probably I was just lucky or the firmware I had on the GNote 10.1 is one of those with which Framaroot works ok.
(1) EDIT feb-17-2013
Update: the device status is now "Custom". Yet, after the rooting, I checked and rebooted more than one time. There must be some Android service that checks the presence of root periodically and finds out, sooner or later, if the device is rooted

sphere314 said:
As I said in the other thread I'm not 100% sure about JB 4.1.1 or 4.1.2.
All I'm sure of is that the firmware code is N8000XXCLL3-N8000ITVCLL1
According to Sammobile it is 4.1.1 but according to Samsung-updates it is 4.1.2. In the tablet, in the "Settings - About device" page the Android version reported is 4.1.2.
Since I'm now rooted maybe I could find out the real Android version (beneath Samsung's touchwiz) by having a quick look at some of the system file... if anyone could tell me where to look .
Anyway I can confirm that my rooting process was really smooth, that it took less than a minute and that my Note's Status has stayed "Official".
Probably I was just lucky or the firmware I had on the GNote 10.1 is one of those with which Framaroot works ok.
Click to expand...
Click to collapse
Thank you. I may wait to see if other note users with JB 4.1.2 report success with Framaroot before I try it on my note since I had issues with a device that the developer had been able to root with his program. Even though I've backed up with Carbon, I don't care to deal with my note stuck in a virtual boot loop. I appreciate you pointing out Framaroot I hadn't seen the thread on it.

Successful Update to MF3, and Retaining Root

First off, I am not responsible for anything that happens to your device.
Secondly, the only way I have tested this is with a FULLY STOCK, ROOTED ROM with NO SYSTEM APPS REMOVED (frozen is okay).
I was able to update my I337 to the 7/9 release of MF3 and retain root.
1. Install VooDoo OTA Root Keeper, make sure all 5 boxes are checked (may have to reinstall superuser if "Google Play" displays and grant root to the app)
2. Reboot, double check VooDoo OTA Root Keeper again has all checked boxes, then tell it to save root
3. Defrost/Enable all AT&T update apps, including AT&T Software Update, download the update through the check for software updates option in settings, and apply it.
4. Reboot, Use VooDoo OTA Root Keeper to restore root
5. Profit
props to @gokartracer5 for being the first to find this
SOME USERS WITH CUSTOM RECOVERIES, KERNELS, or DELETED SYSTEM APPS HAVE EXPERIENCED PROBLEMS.

Great news. I posted this in the other thread:
http://forum.xda-developers.com/showpost.php?p=43504854&postcount=407

The real question is, if you have working root on MF3, how to extract it so that everyone on MF3 can reroot.

I have a few questions.
1. did you have a custom recovery?
2. did you go stock before update
3. did you wipe data factory reset

WoodburyMan said:
The real question is, if you have working root on MF3, how to extract it so that everyone on MF3 can reroot.
Click to expand...
Click to collapse
scott14719 said:
Great news. I posted this in the other thread:
http://forum.xda-developers.com/showpost.php?p=43504854&postcount=407
Click to expand...
Click to collapse
..
I am guessing that Voodoo creates a file with all needed files and install locations when it is prompted to save root. If that created file can be found (temporary stored location), extracted, and then put on someone else's phone, Voodoo could theoretically reinstall root on the other phone. The file structure would need to be the same (same build / ROM) and it would only work if Voodoo doesn't give each created file a unique ID that only matches the original phone the file(s) were created on.
A better way would be to simply figure out where and how Voodoo re-injects root and then make a script that follows the same method.

Roadk1ng said:
I have a few questions.
1. did you have a custom recovery?
2. did you go stock before update
3. did you wipe data factory reset
Click to expand...
Click to collapse
At the time I was stock rooted with Xposed framwork and with Nottach's mod, no custom recovery.
I did not have to factory reset.

Maybe the key is that with VooDoo, root remains physically on the device, so there was no need to try to put it back on through an external device.
Which makes me think it may not work for a new unrooted MF3 device...
However, I am no Dev... hopefully this gives the real geniuses something to work with.

Voodoo Description from Play store page...there is also an XDA link:
"Free tool trying to protect root across manufacturer's OTA updates.
Also serves as temporary un-root (see statement)
Distributed as free of charge - no warranty. Open Source license: WTFPL.
Alternative download link: http://dl.project-voodoo.org/apps/VoodooOTARootKeeper.apk
This application makes a backup or a protected backup of your device's root.
This device must already be rooted: OTA RootKeeper doesn't have the ability to root devices.
If several conditions are matched, OTA RootKeeper will make root survive OTAs and... pretty much well anything − except /system partition formatting.
Requirement:
- /system partition as Ext2, Ext3 or Ext4
- Upgrades not formatting or overwriting completely the /system partition.
Typical systems where its perfectly effective:
- Nexus S
- Galaxy Nexus
- Every Honeycomb tablet
Typical system where the protection won't work:
- HTC Desire
- Samsung Galaxy Spica
- Samsung Galaxy S / SII
The application doesn't support original Superuser and not SuperSU for a very simple reason. The same feature OTA protection feature is already present in SuperSU.
In most case, only manufacturer's original recovery is able to install OTAs. It should not interfere with OTA update process itself.
A bonus feature is present, allowing you to un-root your device while keeping a su backup.
This way you can naively hide root until you choose to restore it via without further complications.
This nifty feature work on every rooted device.
** Temporary un-root statement **
This feature is designed for dev purposes in order to test their app with or without root.
The goal here is not to encourage stupid and unacceptable behaviors by movie or content sellers trying to prevent you to purchase or watch digital media you purchased if your device is rooted.
Vote with your dollars: Don't accept being a customer of companies restricting your freedom with defective and and inefficient technical measures.
Source code is available here:
https://github.com/project-voodoo/ota-rootkeeper-app
OTA root keeper is Open Source. Contributions, reviews and comments are welcome!
If you like this app, feel free to donate via PayPal to [email protected] & make my day in the process "
XDA Developers thread: http://forum.xda-developers.com/showthread.php?t=1241517
I posted this for several reasons.
1. The Dev said SuperSU has the same OTA protection feature built in. Has anyone simply tried it?
2. Although the Dev states that Voodoo does not inject root, he did state that it created a "protected" backup...so it still might be possible to locate that protected backup and inject it into someone else's similar device?
3. More information may be available via the XDA link.
I'm not a Developer either, but it seems something could come of this for those that are already on the MF3 firmware without root.

Active devices came with MF3 and we have a working root. Has anyone with a regular S4 on MF3 tried it?
Sent from my S4 Active

TwoStroker37 said:
Active devices came with MF3 and we have a working root. Has anyone with a regular S4 on MF3 tried it?
Sent from my S4 Active
Click to expand...
Click to collapse
Tried, discussed, and tried some more. There is a lot of info available about it in the various threads. I think the general consensus is that the exploit used in the Active Root might work on the New MF3 (non-Active) OTA, however the APK geohot put together verifies that the phone is an AT&T Active or it aborts. People have tried to contact him, but I don't think anyone has heard anything yet.

I'm on Verizon, so its not exactly the same, but I'm having a hell of a time recreating your success. My device keeps error-ing out in the middle of the update

Yeah this is the method I used yesterday. It works. One thing you have to do after is open the supersu app and install the binaries. It will give two options. Choose normal.
Sent from my SAMSUNG-SGH-I497 using xda premium

I have used Voodoo's OTA Keeper on all by devices for years and I had placed the app on my phone and "saved" my Root immediately after I got my phone. I am on Stock and had Froze all update apps so I never got the update and then when I read about update and people losing Root I posted in some thread about possible OTA Keeper use prior to update. The comments I got back was that it would not work for some technical reason. Since I am not a developer I said OK and just went on. I still not done the update and the only thing I really wanted to try in update was the new modem which I just downloaded and Flashed. Still it good to see that OTA Keeper does appear to work. I will keep watching this thread and if everyone that is the trying app and it working I may Unfreeze and get update.

gokartracer5 said:
Yeah this is the method I used yesterday. It works. One thing you have to do after is open the supersu app and install the binaries. It will give two options. Choose normal.
Sent from my SAMSUNG-SGH-I497 using xda premium
Click to expand...
Click to collapse
Yep. I mentioned you in the OP.
SGS4 non stock

If you have root on this update now, would someone be willing to try installing Goo Manager and installing a custom recovery and then flashing a Loki ROM? Now we can finally move forward a little bit at least.

I'm on step 3. Keep getting "Software update interrupted"

AmesCell said:
I'm on step 3. Keep getting "Software update interrupted"
Click to expand...
Click to collapse
Try defrosting all frozen apps first.
SGS4 non stock

I did that. Set TiB to show only frozen and it's got nothing. I tried a few reboots to be safe. This thing has no mods other than root. I use TiB to wipe the ATT updater data and still same thing.

Is anything different about this if you're using custom recovery? I'm on rooted-MDL with CWM.

someone correct me if I'm wrong, but I believe that custom recoveries won't flash OTA updates.
on my s3 I used mobile Odin for flashing firmware .tar files and ota .zip files as it would always root and inject supersu. while mobile Odin is available for the us market s4, it is NOT available for the att s4.

[Q] Generic steps for un-rooting a custom ROM

Can someone shed some light onto what needs to be done to un-root a custom ROM? Basically I have a crappy old phone which I decided to repurpose for working with an MDM solution my company is using(Citrix Worx Home/Zenprise). I can't use the stock ROM because it's Gingerbread which is not supported by the Citrix app, so I had to flash CM9 on the phone.
The problem is that the app checks for root access. I tried using some tools like "Hide my Root" without success. Even if the SU app is removed, the root detection still triggers.
So I am looking for generic steps of what can be done to remove root access from a ROM which came rooted. Doing a search the only posts I find are more relevant to people who want to return to stock ROM and not unroot a custom ROM. Are there other things that need to be modified besides removing the SuperUser apk?

Try this app..
https://play.google.com/store/apps/details?id=com.universal.unroot
Costs a little but hope it's worth for it
Hit thanks rather than typing it

Getting to 4.3...got past 402 error!

Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!

doncaruana said:
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
Click to expand...
Click to collapse
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.

buhohitr said:
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
Click to expand...
Click to collapse
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?

doncaruana said:
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
Click to expand...
Click to collapse
Sorry but flashing the full firmware will wipe everything bring it back to factory stock phone, so you need to backup all your stuff.

Well, just to share with everyone, I did not flash back to stock. For a number of reasons, that wasn't really an option.
My first step was removing viper4android. That actually got rid of the "custom" screen with the open lock on boot.
Then I uninstalled busybox from within itself. Unfortunately, as noted elsewhere, that leaves several hundred symlinks in xbin, so I removed all of those (I was only left with dexdump and su there). After that, I actually uninstalled busybox via the app manager.
Then I used the unroot option in supersu to clean up the rest and remove it.
At this point, I should be completely unrooted, but still got the 402 error when failing to upgrade with the OTA.
So...I plugged the phone in and ran the software upgrade assistant that shows up on the "CD" that presents itself from the phone when you plug it in to USB to the computer. And, actually, that successfully completed the upgrade to 4.3!
Haven't embarked on re-rooting yet (using saferoot) but that's the plan at least.