How do I remove ClockworkMod? - Milestone 2 General

Hi, I installed ClockworkMod recovery installing Droid 2 Bootstrapper to make changes that I did. From now on every startup I get ClockworkMod recovery, can I remove it or make it appear only on request?
thanks

If you unnistall the droid2bootstrapper app you'll always get to recoveryon boot. Just reinstall the app.
Or, if you wanna delete it, do it in the Terminal Emulator/ADB Shell:
su
busybox mount -o remount,rw /system
rm /system/bin/hijacker
rm /system/bin/logwrapper
mv /system/bin/logwrapper.bin /system/bin/logwrapper
Sent from my Milestone 2 XDA App

Thanks! I did it with Root Explorer and it worked!

Moved to general as not android development.

Related

Titanium Backup working

Thanks for all the help from the forum on rooting.
Titanium backup is working great on the DI.
Got Root, Manually installed Superuser, Manually install busybox. Used Titanium to install a new Busybox to the app, everything backs up great.
It's missing from the market for some reason
xvenom89 said:
It's missing from the market for some reason
Click to expand...
Click to collapse
I pulled it from the market just a few hours ago.
xvenom89 said:
It's missing from the market for some reason
Click to expand...
Click to collapse
Did you make your root persistent? You're not going to be able to see root apps if you're not rooted, I don't think.
heavensblade23 said:
Did you make your root persistent? You're not going to be able to see root apps if you're not rooted, I don't think.
Click to expand...
Click to collapse
I could see Titanium on the market before I rooted. I would check the spelling or better yet, use appbrain.com to locate it.
how did you get superuser.apk to install?
See this post for installing superuser.apk
But how did you get busybox installed so Titanium would work?
When you go into Titanium, go to the Menu -> Problems. It will prompt you to download a version of busybox that works with it.
Skapunker said:
See this post for installing superuser.apk
But how did you get busybox installed so Titanium would work?
Click to expand...
Click to collapse
After Superuser.apk and su are setup
while still in recovery root (this does not seem to work if rebooted and using persistance root and remounting /system rw),
cd /system/xbin
/system/bin/cat /sdcard/busybox > busybox
chmod 777 busybox
./busybox --install -s /system/xbin
Reboot, Run Titanium, use Problems? button to download and install a new busybox into the Titanium app
For me, Titanium would not run to a point to use the Problems button until I put a version of busybox on the phone first.
da_knowledge said:
When you go into Titanium, go to the Menu -> Problems. It will prompt you to download a version of busybox that works with it.
Click to expand...
Click to collapse
That was easy, can't believe I didn't bother to try that, thanks
Thanks for the replies
Got it working!! Great, thanks!!
I just got my Incredible rooted and installed Titanium Backup when I run it it says "BusyzBox works but the "su" command does not elevate to root:"whoami" reports "whoami:unknown uid 10108" instead of root?uid 0. I think your "Superuser Whitelist" system app does not work. Please check with your ROM provider." how do I fix this? or is it even a problem? Thanks.
same problem here
I am sure it is just a linux issue, but I am getting it too, but i am not a guru and do not know how to handle it ;-)
Can anyone explain titanium backup a little more??? Do I need to backup every app individually or just let the schedule take care of it? Which schedule option should I pick (in terms of all the options of what function you want titanium back to perform)?
I figured it out.
Just wondering, updating the version of busybox will do nothing to the root access, correct? It'll just allow titanium to work properly and root will remain?
My problem was from a not working superuser.apk. rerooted using the files from the 10min root video and now all is well. To answer the above question in regards to updating busybox, I assume you are refering to letting Titanium Backup update busybox. If so it is ok to update busybox.
Yep, that's what I was wondering. Thanks
Sent from my ADR6300 using Tapatalk
Looking at what this backs up, I am a bit curious if it can actually restore some of it. Many sections it appears to be backing up are not writable even with root access at the moment on the Dinc.
I'm guessing it will require NAND access for this to truely be useful unless I am missing something...
krelvinaz said:
Looking at what this backs up, I am a bit curious if it can actually restore some of it. Many sections it appears to be backing up are not writable even with root access at the moment on the Dinc.
I'm guessing it will require NAND access for this to truely be useful unless I am missing something...
Click to expand...
Click to collapse
That was the main purpose of me getting titanium, i'm not expecting to have the need to restore anything until i flash a custom rom. Having the backup now is awesome because i know i won't lose anything once they figure out how to unlock NAND and flash a recovery and roms
when i'm in recovery mode trying to gain persistant root i get an error.
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
when in Titanium and I hit the "problems ?" button it downloads busybox, but says it failed because it doesn't have root.
any help?

Manually Deodex Any S5830 Rom !!!

After i succesfull deodex my stock rom i've decided to share my experience with ya'll people ...
Here we go :
1. You must be rooted !!!
2. Download -> xUltimate
3. Unzip xUltimate v2.2, and launch "Main.exe"
4. Now xUltimate should recognize the phone and make a connection. You now should see a list of options.
5. Run option 1. After option 1 is done, run option 2.
6. Now these well take a while. Run option 3
7. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
8. Now run option 4, and wait.
9. Exit xUltimate, and put the phone in USB mass storage then copy "done_frame", and "done_app" to the root of the sdcard then put the phone in PC mode.
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
After phone is boot, reboot again in CWM and Wipe Dalvin Cache, reboot and ENJOY !!!
Notice : The boot will take a little bit longer than normal (2-4 seconds +)
P.S. For step 7 ... there is no guava.odex, don't worry about, continue to next step !
Credits :
Rainabba, Mike919, toxman, teenfaces, Xeudoxus !
Fisrt post ! Good work dude!!
You must have adb (by installing android sdk, platform-tools, install usb driver too) and jdk to do this if anyone is wondering.
kevinlekiller said:
You must have adb (by installing android sdk, platform-tools, install usb driver too) and jdk to do this if anyone is wondering.
Click to expand...
Click to collapse
I assumed that those who want to deodex their rom already knew that, anyway, thanx for reply
Nice tutorial!
Sent from my GT-S5830 using xda premium
Thanks y'all, I will also post other tutorials if i discover something interesting !
I know this question is stupid, but what's the difference between odexed and deodexed rom?
Yesterday I was trying to figure out how to deodex and today you make a tutorial, lol
Thanks.
excellent!! could create one of how to add cf-root and menu extended to create custom roms, is the last thing I need to learn to develop roms
tazlooney89 said:
excellent!! could create one of how to add cf-root and menu extended to create custom roms, is the last thing I need to learn to develop roms
Click to expand...
Click to collapse
Cf root xd to easy
Its in th .zip self
Just extract look in folder and place them where they belong
Sent from my GT-S5830 using xda premium
thanks dude!
now i can get pdroid running on stock rom *_*
Great tutorial thanks!
It would be great if you show how to enable CRT animation in any stock rom ang make grouping widgets in menu.
P4qui7o said:
After i succesfull deodex my stock rom i've decided to share my experience with ya'll people ...
Here we go :
1. You must be rooted !!!
2. Download -> xUltimate
3. Unzip xUltimate v2.2, and launch "Main.exe"
4. Now xUltimate should recognize the phone and make a connection. You now should see a list of options.
5. Run option 1. After option 1 is done, run option 2.
6. Now these well take a while. Run option 3
7. IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex". It's a bad file, and interferes with deodexing process.
8. Now run option 4, and wait.
9. Exit xUltimate, and put the phone in USB mass storage then copy "done_frame", and "done_app" to the root of the sdcard then put the phone in PC mode.
10. Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
After phone is boot, reboot again in CWM and Wipe Dalvin Cache, reboot and ENJOY !!!
Notice : The boot will take a little bit longer than normal (2-4 seconds +)
P.S. For step 7 ... there is no guava.odex, don't worry about, continue to next step !
Credits :
Rainabba, Mike919, toxman, teenfaces, Xeudoxus !
Click to expand...
Click to collapse
Superb Tutorial Dude...
I am currently testing @Jusadas latest "Carbon Sunday Beta1" rom... It is fully odexed & so far is bug free (Totally)...... I would like to try & DeOdex the rom so that PDroid & Patch can be implemented...
I Know that PDroid framework has now been ported for Odexed roms, but when I flash the Odexed version I get stuck at Android txt during boot...
Will report back if your technique works...
Stay Breezy n Be Lucky...
Pe"ACE"...
Thanx man what a great work , i actually look for deodexing method coz i want to translate an odexed rom but i has to be deodexed first
I'll give it a shot !
Excellent guide!!!
Will try it tmw
Thanks =)
Sent from my GT-P6800 using xda premium
Well the title says manually deodex. But this uses the tool. To manually do it you need to decompile each app individually and then edit it.
Btw, nice giude..
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
ERROR!
Tried this on my stock ddkq8 gingerbread 2.3.6 rom. But whenever I run this line: busybox cp /sdcard/done_app/* /system/app/
it says cp: No space left on device.
and my phone bricks.
It seems that the command does not overwrite the files in /system/app and thus the error.
BTW what do you mean by pc mode?
PLS reply!
galaxyace152 said:
Tried this on my stock ddkq8 gingerbread 2.3.6 rom. But whenever I run this line: busybox cp /sdcard/done_app/* /system/app/
it says cp: No space left on device.
and my phone bricks.
It seems that the command does not overwrite the files in /system/app and thus the error.
BTW what do you mean by pc mode?
PLS reply!
Click to expand...
Click to collapse
Before "10. Open a command prompt, and do the following:"
Just delete some apps to make 40 mb free in system !
That's how i did and work's
Use Root Explorer or something
shaaan said:
Well the title says manually deodex. But this uses the tool. To manually do it you need to decompile each app individually and then edit it.
Btw, nice giude..
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
Click to expand...
Click to collapse
Developer Talking
---------- Post added at 08:57 PM ---------- Previous post was at 08:56 PM ----------
Stuck on boot loop! :| And yes, I wiped everything. Nice tutorial BTW, appreciate it.
EDIT: Never mind. Sorted it.
C:\android-sdk-windows\platform-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# stop
stop
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# busybox cp /sdcard/done_app/* /system/app/
busybox cp /sdcard/done_app/* /system/app/
cp: can't stat '/sdcard/done_app/*': No such file or directory
# busybox cp /sdcard/done_frame/* /system/framework/
busybox cp /sdcard/done_frame/* /system/framework/
cp: can't stat '/sdcard/done_frame/*': No such file or directory
# rm /system/app/*.odex
rm /system/app/*.odex
# rm /system/framework/*.odex
rm /system/framework/*.odex
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# reboot
reboot
C:\android-sdk-windows\platform-tools>
how come mine is like this...? anyone can help me...? plz
after that my phone cant start...it stuck on the galaxy ace screen...???

Better way ???

What is better way to unroot you S4 on MF3 Odin back to stock MF3 or by SU full unroot?
It'll somewhat depend on why you want to remove root. But I've always used odin. You will lose all your apps this easy though. I've never tried using unroot inside super su and don't know if it leaves somethings behind.
Personally, I like to make sure everything is completely gone by doing the following:
First remove Safestrap via ADB:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Then, remove SU & Busybox via Root Explorer:
1. Navigate to /system/xbin
2. Delete busybox and SU
3. Naviate to /system/bin
4. Delete SU
5. Uninstall Superuser from the Applications Menu
Finally, nuke the entire thing by ODINing back to MF3 stock with this:
http://forum.xda-developers.com/showthread.php?t=2502003
You really only need to do the last step, but I always like to be extra safe.
jd1639 said:
It'll somewhat depend on why you want to remove root. But I've always used odin. You will lose all your apps this easy though. I've never tried using unroot inside super su and don't know if it leaves somethings behind.
Click to expand...
Click to collapse
One of my friends want to get back to stock with out root so he can push last update tru ADB. He is not using anything what required root but he rooted his phone..Also he want to keep his settings on phone.
jdisco1 said:
Personally, I like to make sure everything is completely gone by doing the following:
First remove Safestrap via ADB:
Code:
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system
Then, remove SU & Busybox via Root Explorer:
1. Navigate to /system/xbin
2. Delete busybox and SU
3. Naviate to /system/bin
4. Delete SU
5. Uninstall Superuser from the Applications Menu
Finally, nuke the entire thing by ODINing back to MF3 stock with this:
http://forum.xda-developers.com/showthread.php?t=2502003
You really only need to do the last step, but I always like to be extra safe.
Click to expand...
Click to collapse
Friend of mine don't have SafeStrip on his phone. BTW you can remove last version of SS with appication manager.
2nd step will remove will remove root and leave the rest of the OS intact. I think SU full unroot leaves busybox behind, and you cant delete it without root.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
jdisco1 said:
2nd step will remove will remove root and leave the rest of the OS intact. I think SU full unroot leaves busybox behind, and you cant delete it without root.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
cool thanks..

[Q] removing stock apps correctly (busybox and terminal emulator)

Alright, so checking up the system folder with root explorer I noticed that there are several applications related to the stock music player.
I can't just simply remove these "apks", right? Pretty certain there'd be leftovers of this app somewhere.
So, I realize, there's no "uninstall" script for the music app, but I was wondering, what is the most correct way to delete music application?
Simple doing this won't cut it, right?
Code:
su
cd system/app
mount -o rw,remount /system
rm -r MusicCommonUtility
rm -rMusicLiveShare2.apk
rm -rMusicPlayerWT.apk
mount -o remount,ro /system
For that kind of things I use Titanium backup app. With that app you can backup ANY app before uninstalling it or just simply uninstalling it. After that reboot the phone and that app is gone.

Lost root on Titanium Backup

I have the Verizon VS995 LG20 and rooted via DirtySanta a couple weeks ago. I recently have lost root privilege with Titanium Backup. Root on other apps is fine. The issue may be related to changes I made a week ago in trying to get root access for Secure Settings plugin for Tasker. Secure Settings doesn't work with systemless root. I have tried uninstalling and reinstalling both the su app and Titanium Backup, but I keep getting the same error:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted, and try again. This attempt was made using the "/system/bin/su" command." I would appreciate any suggestions in how I can fix this. I would like to make a backup before trying some new roms.
I just ran into this same exact problem. I removed the su files I created in order to get Secure Settings working and Titanium Backup now works. But why did Titanium Backup start having a problem with this all of a sudden and what is the true solution?
Here's what I did to fix Secure Settings from adb shell:
su
mount -o rw,remount /system
touch /system/bin/su /system/xbin/su
mount -o ro,remount /system
So I fixed the problem by just removing the su files. However I want both Secure Settings and Titanium Backup working!!!
TheShanMan said:
I just ran into this same exact problem. I removed the su files I created in order to get Secure Settings working and Titanium Backup now works. But why did Titanium Backup start having a problem with this all of a sudden and what is the true solution?
Here's what I did to fix Secure Settings from adb shell:
su
mount -o rw,remount /system
touch /system/bin/su /system/xbin/su
mount -o ro,remount /system
So I fixed the problem by just removing the su files. However I want both Secure Settings and Titanium Backup working!!!
Click to expand...
Click to collapse
I had a similar issue - TB stopped obtaining root after a kernel change - don't know why. I solved it by changing the su 'dummy' file in /system/bin/su (TB was trying to use this) to a symbolic link pointing at the real su:
Code:
[email protected]:/su # rm /system/bin/su
[email protected]:/su # ln -s /su/bin/su /system/bin/su
Rebooted and TB and SecureSettings can now use root.
Not having this problem but TB does force close alot on me. It started when rom toolbox pro deactivated app manager. Maybe TB has something to do with the dev?

Categories

Resources