Database Develop

How to remove ROM Manager ?

I find that ROM manager could not be uninstalled. There is only a button to upgrade, but no button for uninstall. How can it be done?
Sent from my HTC Magic using XDA App

Try Titanium Backup

Help
Rom Manager will not show in Root Explorer or Astro whether its installed or not. This is on my Xoom 3g, rooted by Root My Xoom, without Timat. Clockworkmod will not update my Xoom to HRI66, it doesn't exist but it does at SDcard/update.zip. I've been researching this and working on this for 2 days now. Using Root My Xoom while rooting can't install in either. Suggestions needed.

Have you tried the instructions here: wiki.cyanogenmod.com/index.php?title=Barebones ?

I just use Root Explorer and delete it.
Make sure you look in system\app to find it.
Works for me without an issue.

With Titanium Backup is very simple.

Yeap with titanium backup is very very simple, just click on uninstall app and enjoy

Before you Install ROM Manager - read this!
I installed ROM Manager v.4.8.0.6 which includes ClockworkMod (CWM) to backup my new stock ROM.
Problem #1 with ROM Manager
CWM won't install because it does not use verified signatures which my stock device requires to install it.
I removed ROM Manager and re-booted.
I installed ROM Toolbox.
Problem #2 with ROM Manager
With ROM Toolbox, when trying to backup ROM I get the message:ROM Manager blocked other apps from creating backups in recovery unless ROM Manager Premium is installed.
Once you install ROM Manager Premium you can use ROM Toolbox to backup your ROM. ​I have sent emails and tweets to the author but have yet to receive a reply. (See attached screen capture)

bump..I experience the same

I flashed my galaxy tab with a stock ROM Android 3.2 via Odin than rooted again, but ROM Toolbox brings up the same dialog. I'm a newbie, but this looks weird to me. I think that after this type of flash the cache and all data should be wiped.
So is it a really a problem of ROM manager, when it has not been installed after the stock firmware upload?

same here
i have encountered the IDENTICAL problem to Catalyst2012. Has anyone figured out what to do? My device is Vodafone 858 (Huawei U8160), if that helps?
Catalyst2012 said:
I installed ROM Manager v.4.8.0.6 which includes ClockworkMod (CWM) to backup my new stock ROM.
Problem #1 with ROM Manager
CWM won't install because it does not use verified signatures which my stock device requires to install it.
I removed ROM Manager and re-booted.
I installed ROM Toolbox.
Problem #2 with ROM Manager
With ROM Toolbox, when trying to backup ROM I get the message:ROM Manager blocked other apps from creating backups in recovery unless ROM Manager Premium is installed.
Once you install ROM Manager Premium you can use ROM Toolbox to backup your ROM. ​I have sent emails and tweets to the author but have yet to receive a reply. (See attached screen capture)
Click to expand...
Click to collapse

With ROM Toolbox, when trying to backup ROM I get the message:
ROM Manager blocked other apps from creating backups in recovery unless ROM Manager Premium is installed.
Once you install ROM Manager Premium you can use ROM Toolbox to backup your ROM.
I have sent emails and tweets to the author but have yet to receive a reply. (See attached screen capture)
Click to expand...
Click to collapse
according to Koush, the developer of ROM Manager:
ClockworkMod recovery is open source. However, the hooks that ROM Manager uses to automate backups by hooking into ClockworkMod Recovery are proprietary.
I have told other developers, if they wish to use the ClockworkMod Recovery hooks, they can do it in the following ways:
1) Build, distribute, and support their own version of ClockworkMod Recovery, so that I am not responsible for the maintenance of it.
2) Use the ROM Manager API, which requires a ROM Manager Premium License.
The user can ALWAYS make backups manually in recovery, without a Premium license.
Basically, the issue here is that developers are relying on me and my open source work, which I maintain, to build a competing product to my paid applications. Essentially undercutting me by relying on me developing 90% of the product for them. It seems pretty silly for me to continue maintaining and distributing something that directly competes with my income, so I put a stop to it. If they want to build a competing product, they will have to go through all the hassles involved with building, distributing, and supporting recovery images.
So, no, those other applications are not "blocked" from creating backups. They are just being lazy, and not actually building/flashing their own recovery image. Nothing is preventing them from building a ROM Manager clone, if they really wanted to. They are just avoiding doing the hard part.
Click to expand...
Click to collapse

1. run ClockWorkMode with superpol′zovatelâ2. click boot in rekaveri3. reboot and there is a problem in the form of inscriptions: failed to verify whole-file signatureE: signature verification failedV the problem who experienced?

The is no responded from rom manager. He just takes your money and won't respond to email.

[Q] How to transfer apps and data through ROMs?

I am really enjoying to try different custom Roms.
But everytime when I flash to JF6 and get new Roms, I have installed all my applications and email accounts again and again.
Is there any way to carry over?

jhc9604 said:
I am really enjoying to try different custom Roms.
But everytime when I flash to JF6 and get new Roms, I have installed all my applications and email accounts again and again.
Is there any way to carry over?
Click to expand...
Click to collapse
Free app on market titanium backup. This will back up your apps, I would not suggest emails or any system data. It will save your apps and their settings. Once again though, no system data as this changes from rom to rom and restoring it can cause issues.
If you need a quick walkthrough pm me
Sent from my SAMSUNG-SGH-I897 using XDA App

You can also use the free version of Astro File Manager to backup your apps. It worked really well for me, but it doesn't backup private apps.

[Q] Full root CF LPY?

I have LPY running with the CF kernel which was flashed via mobile Odin. I have root access for programs like Titanium, but I cannot delete items from my system/apps folder. I use ES File Explorer with the options checked for root access and for rw on root. I figured it was just an issue with the kernel but I have been told that full root works for others. Does anybody have any thoughts as to how I could go about getting full root working? I want to delete that pesky GMS_Maps.apk so I can replace it with one with working navigation where I live. Thanks for any help!
Sent from my GT-N7000 using XDA

pezx44 said:
I have LPY running with the CF kernel which was flashed via mobile Odin. I have root access for programs like Titanium, but I cannot delete items from my system/apps folder. I use ES File Explorer with the options checked for root access and for rw on root. I figured it was just an issue with the kernel but I have been told that full root works for others. Does anybody have any thoughts as to how I could go about getting full root working? I want to delete that pesky GMS_Maps.apk so I can replace it with one with working navigation where I live. Thanks for any help!
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Check the "Mounted as button" on top left of Root Explorer and make sure you can switch the system to R/W (read/Write)
It may default to Read/Only

I downloaded root explorer in case that was the issue. I click the rw button when I go into the system folder but no joy. When I press it, nothing happens. The state remains ro and the button remains rw.
Sent from my GT-N7000 using XDA

Tried reinstalling cwm and su/busybox via cwm and still no dice. Thinking I might just have to live with it until another kernel comes out and I feel safer with all this installing zips in cwm. Still, if anyone has any thoughts, please let me know because it's a bit annoying to me.
Sent from my GT-N7000 using XDA

It's not LPY, but I seem to have full root again after flashing the newest ics and installing su/busybox using the following:
http://forum.xda-developers.com/showpost.php?p=26220075&postcount=148

Custom ROM and kernel on unrooted N7?

I was wondering if it's possible to root, install a custom recovery, ROM and kernel, and then unroot with that setup? I would like the performance improvements that come with a custom ROM and kernel, but need to be unrooted to run some apps (one being an app for work). Any help is greatly appreciated.
Sent from my Nexus 7 using Tapatalk 2

psousa781 said:
I was wondering if it's possible to root, install a custom recovery, ROM and kernel, and then unroot with that setup? I would like the performance improvements that come with a custom ROM and kernel, but need to be unrooted to run some apps (one being an app for work). Any help is greatly appreciated.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I believe that you could use the SuperSU application to disable root.
If that doesn't work, OTArootkeeper will actually allow you to make a backup of your root and then delete the regular root. When you need root again you just restore the backup.

theaftermath said:
I believe that you could use the SuperSU application to disable root.
If that doesn't work, OTArootkeeper will actually allow you to make a backup of your root and then delete the regular root. When you need root again you just restore the backup.
Click to expand...
Click to collapse
So disable root with SuperuserSU, then I could uninstall SuperuserSU? I believe the app for work will detect if Superuser or SuperuserSU are installed.
Sent from my Nexus 7 using Tapatalk 2

inksxpe pas
psousa781 said:
So disable root with SuperuserSU, then I could uninstall SuperuserSU? I believe the app for work will detect if Superuser or SuperuserSU are installed.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I kinda doubt it would notice. If root is disabled than it shouldn't be able to access whether or not other apps are installed. But you probably want to wait for a second opinion on that. I'm knowledgeable but I'm not a guru.

Thanks man, I appreciate the help.
Sent from my Nexus 7 using Tapatalk 2

You mentioned "custom kernel".
As near as I can tell some kernel devs have been shipping just a bare kernel (zImage, etc), and others provide flashable boot images - that is, kernel + ramdisk.
If the "kernels" which include a ramdisk do something typical like set "ro.secure = 0" as a convenience for adb users (in /default.prop et cetera), and your app which "checks for root" inspects this property, then even though you removed SuperSU/Superuser and their corresponding "su" binaries this (as a single example) might cause the root check to still fail.
I guess the point is that you would need to know what exactly the app in question is checking for to know whether your efforts will succeed. It could be one or more of any of these things:
- bootloader lock state (only if it is detectable from the OS, not sure if this can be done)
- presence of a /system/xbin/su or /system/bin/su file
- presence of SuperSU.apk or Superuser.apk in /system/app
- ro.secure value (or others properties such as adb settings etc)
- relative timestamp checks on certain /system directories.
- TiBu installed as an app?
- other ?
I think that it is feasible to detect a non-stock recovery or boot kernel but not very easily with a non-root app - so you can probably get away with having a custom recovery and an unlocked bootloader too.
No way to know in advance though.

theaftermath said:
I kinda doubt it would notice. If root is disabled than it shouldn't be able to access whether or not other apps are installed. But you probably want to wait for a second opinion on that. I'm knowledgeable but I'm not a guru.
Click to expand...
Click to collapse
This maybe stupid but I had the same issue with my xoom and a few apps not working while rooted. The solution was to go into system then apps and rename the superuser to something else and that fooled the program and it didn't sect root. Maybe try that?
Sent from my Nexus 7 using xda premium

Gsam root compainion installation

I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance

elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)

elfking7 said:
I have been trying to get "gsam root companion" to work on my htc one. I've rooted my device just so i could check out the features such as wake lock, etc.
The thing is, it keep saying "The Root Companion application is not installed correctly in /system/priv-app."
I tried manually installing it by copying the "com.gsamlabs.bbm.rootcomanion-1.apk" (whether or not if its the correct file) into the system/priv-app location. That restarted my device, and the file just disappeared from the priv-app location as well, and so the problem persist.
Am i doing everything wrong manually. Wish I could find a tutorial vid =/.
Thank you in advance
Click to expand...
Click to collapse
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?

alray said:
in order to write/modify/delete file in /system, you need an unsecured kernel (/system writeable), otherwise all changes made to /system will be reverted at reboot. I'm not using and never used gsam, maybe there is another option but the only one I know is to flash a custom kernel.
Kernel for the htc one (M7) are listed here
make sure to chose one that is compatible with your rom (sense/gpe based or AOSP based)
Click to expand...
Click to collapse
Thank you so much. I had this problem for days. Why isn't my unlocked phone writeable in the first place...

sharksfan7 said:
I just fiddled with this the other day, but didn't use the Root Companion app. It's not the Root Companion apk that's moved to /system/priv-app. It's the actual GSam Battery Monitor apk, com.gsamlabs.bbm.apk. The Root Companion app just does the move for you. If you have a file manager with root r/w permission, you should be able to do it yourself. Just move com.gsamlabs.bbm.apk from /data/app to /system/priv-app. Then restart your phone. I actually used an app called Link2SD to convert GSam Battery Monitor from a user app to system app and it accomplished the same thing.
I'm running the stock AT&T 4.4.2 ROM rooted with the stock kernel and haven't had any issues with changes reverting back after a reboot. I use ES File Explorer & set it to have R/W permissions in that app's settings, but I assume that only applies to that app. Yet I've converted a few apps from user apps to system apps (3rd party launcher GSam Battery Monitor & SuperSU are the ones I remember off the top of my head) and never noticed them switching back to user apps. That is until I update them; then they become user apps. I don't know if this is because the apps I'm using to switch them have SU permissions or what, but none have changed back by simply rebooting. And as far as I know, I haven't done anything to modify the stock kernel from the OTA. Is it even possible to unsecure a stock kernel using apps?
Click to expand...
Click to collapse
You just used your stock kernal 0.0
Why isn't mine like that. D=

elfking7 said:
You just used your stock kernal 0.0
Why isn't mine like that. D=
Click to expand...
Click to collapse
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.

sharksfan7 said:
I have no idea. I didn't even know about needing an unsecure kernel to be able to write to /system. Nor do I know how the stock kernel became unsecure in the first place. All I've done is root the ROM as I normally would by flashing SuperSU. Then grant root permission to the apps that request it. If something in that process makes the stock kernel unsecured, then I don't know what it was.
You said in your OP that you tried manually moving the com.gsamlabs.bbm.rootcomanion-1.apk to /system/priv-app. First of all, that's the wrong apk. See my original reply for the apk you need to move. Do you even have GSam Battery Monitor installed? Battery Monitor & Root Companion are two separate apps. Battery Monitor needs to be installed before Root Companion will do its thing. At least I assume that's the case, b/c like I said before, I didn't use Root Companion to move Battery Monitor. But the description in Root Companion says all it does is move the Battery Monitor apk to /system/priv-app. Secondly, how did you move the apk? What app did you use?
Like I explained previously I originally used an app called Link2SD. That gives an option to convert user apps to system apps & vice versa. Just now I used it to convert GSam back to a user app. I wanted to test if moving the apk manually made a difference. After I converted it to a user app, I used ES File Explorer to cut & paste the GSam apk from /data/app to /system/priv-app. I then restarted my phone. The apk did not disappear and the app continues to work.
Click to expand...
Click to collapse
I followed alray's advice. I installed the elementalx kernel which made my system writeable, since my stock kernel wasn't originally. I then retry using the root companion (I installed gsam battery monitor since last week) which finally worked by using the automatic option that the root companion provided. I didn't notice much difference with the app, after giving the battery monitor privileged access to the system=/.