need help for remove setcpu adb - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi, I'm enter on my transformer by :
adb shell
and I want do that :
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock4 /system
cd /data/app
rm com.mhuang.overclock*
cd /data/data
rm com.mhuang.overclock*
cd /data/dalvik-cache
rm *mhuang.overclock*
exit
But when I execute su, it don't work :
/data/app # su
Segmentation fault
Can you help me ?
Thanks

Just reflash your rom without wiping data unless your trying to flash a rom that is overclocked by default

If it's in your data partition, then it's not a system file. Try this:
adb uninstall com.mhuang.overclocking (use the full package name)
EDIT: saw your other thread about borking your TF. follow badfrog's trick and flash a rom with a non-overclocking kernel, which will limit setcpu.

If adb uninstall don't work, which rom with overclock by default propose me ? Révolution HD ?
Sorry for my english, i'm french ?

Prime has a stock kernel as default
http://forum.xda-developers.com/showthread.php?t=1251044

Related

Install Modded RC30 from Bug Terminal?

Hey guys,
Sadly, I've got Vista64, which works fairly well, FYI.
Anyways, because of it I can't install the USB drivers.. But I figure I'm just using them to access the terminal, which I, on RC29, apparently already have access to...
If I copy recovery.img to the SDcard and then use the filemanager to put it in /system, would I be able to flash it from the homescreen? What commands would I use?
Just
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# cat /data/local/recovery.img > recovery.img
cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
flash_image recovery recovery.img
#
?? Is this going to do something bad...
Thanks
**I don't have write permission to /System using Android File Manager. I'm sorry I'm a linux newb here, what cmds do I need to use to overwrite that file?
grim1234 said:
Hey guys,
Sadly, I've got Vista64, which works fairly well, FYI.
Anyways, because of it I can't install the USB drivers.. But I figure I'm just using them to access the terminal, which I, on RC29, apparently already have access to...
If I copy recovery.img to the SDcard and then use the filemanager to put it in /system, would I be able to flash it from the homescreen? What commands would I use?
Just
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system
cd /system
# cat /data/local/recovery.img > recovery.img
cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
flash_image recovery recovery.img
#
?? Is this going to do something bad...
Thanks
**I don't have write permission to /System using Android File Manager. I'm sorry I'm a linux newb here, what cmds do I need to use to overwrite that file?
Click to expand...
Click to collapse
I have the same problem: I am using Windows Server 2008 x64 and there is no 64 bit driver for ADB. I ended up installing a Ubuntu VM:
http://www.koushikdutta.com/2008/10/developing-and-debugging-android.html
Well, I tired txting this to someone...
cp /sdcard/recovery.img /system
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system
cat /data/local/recovery.img > recovery.img
flash_image recovery recovery.img
Then booted into recovery mode and pressed alt-L...
And it doesn't work.
I guess it's VMWare time... zzz
Check out my post over at AndroidCommunity http://androidcommunity.com/forums/f28/i-have-rc30-and-root-6867/ this will allow you to install the modified upgrade without the adb, and sdk.

something up with my shell scripts.

I seem to be frequently flashing or messing up my G1 so I decided to write some shell scripts to help out but they seem to only half work if at all. Actually I'm not sure what they did because they displayed no output.
This script is supposed to backup the default init.rc and mountd.conf files then replace the existing ones with the modified ones.
Though it does not work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
busybox cp -a /system/etc/mountd.conf /sdcard/recovery/mountd.conf.bak
busybox cp -a /system/init.rc /sdcard/recovery/init.rc.bak
busybox cp -a /sdcard/recovery/mountd.conf /system/etc/mountd.conf
busybox cp -a /sdcard/recovery/init.rc /system/init.rc
then this is the next set to move the apks and the program caches which doesn't work.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
busybox cp -a /data/app /system/sd
rm -r /data/app
ln -s /system/sd/app /data/app
busybox cp -a /data/app-private /system/sd/app-private
rm -r /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -R /data/data/com.android.browser/cache/webviewCache
ln -s /sdcard/cache/webviewCache /data/data/com.android.browser/cache/webviewCache
rm -R /data/data/com.android.vending/cache
ln -s /sdcard/cache/marketCache /data/data/com.android.vending/cache
rm -R /data/data/com.google.android.street/cache
ln -s /sdcard/cache/streetCache /data/data/com.google.android.street/cache
reboot
Plus both run and output no errors either. Who knows what problems I'll run into because I have no idea what they actually did.
Anyone see anything wrong here?
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
I have a menu that does that and I have got some experience as why it works one day and not the other.
Rafase282 said:
Well I'll help you.
1-) After you back up the mount and stuff and put the other back, you MUST reboot before keep going.
Click to expand...
Click to collapse
I took the reboot out after the mountd.conf and init.rc did not appear to copy due to the lack of /dev/mmcblk0p2 hoping to see some sort of output why it did not run. Unfortunately it runs and backs up the files but does not replace them with the modded ones.
Rafase282 said:
2-)After boot then you can copy the files or make the symlink. I suggest you dont copy the app to the sdcard on teh scrip since they should be there already. so do that manually once then the script just delete the folders and then crate the symlinmks.
Click to expand...
Click to collapse
Not copying the apps is a good idea, modified the script to not do so.
Rafase282 said:
I have a menu that does that and I have got some experience as why it works one day and not the other.
Click to expand...
Click to collapse
Does Android require that you do a chmod on all shell scripts first?
On Debian I usually just use sudo sh ./ and it runs the script w/o changing anything on the file permissions so I figured Android would be similar if I just ran them as root. Still I see a lot of people requiring a chmod 777 on any guide referring to running shell scripts.
I will try that and report back with my findings. Thanks for replying.
Does Android require that you do a chmod on all shell scripts first? I just have to type m oon anywhere in the androud shell and my scripts run, for that i put it on /system/bin and do a chmod 4755 to the file. it is still needed to type su before you run the script.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/sd
cp /sdcard/media/Data/mountd.conf /system/etc/mountd.conf
cp /sdcard/media/Data/init.rc /system/init.rc
Thats my code for copying the modified files to the right place. So maybe you should try that.
Oh for androoid you dont unless you put it on /system/bin then you will have to use sude and sometiems it still wont run due to lack or permisions so is better to do a chmod 4755
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
joshtheitguy said:
Well I made the changes suggested and did a chmod on all the files prior to running but with no luck.
The odd thing is if I use the shell scripts as a guide list it works perfectly but if I try to launch them as a shell script all sorts of strange undesirable things happen to my phone.
The time consumed trying to use the scripts and recover from what happens from what they do out weight the effects of typing everything in.
Click to expand...
Click to collapse
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
LucidREM said:
you can only run the script once .. when the "ln -s" has already been done it has to be undone before trying to run the script again .. otherwise you would be copying the files onto themselves .. not sure if you've tried running it more than once
Click to expand...
Click to collapse
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
joshtheitguy said:
These scripts were intended for my usage after a system restore from a update.zip file which wipes /system in the process.
My intentions were to:
1. remount the fs rw
2. copy the original init and mountd files to the sd then copy the modified to their respective places in the system folders then reboot
3. reboot then create the sym links appropriately then move my caches too
Well unfortunately the only thing that works is the backing up of the original init and mountd files.
Click to expand...
Click to collapse
yes .. but you can't create the sym links when they already exist .. running the update.zip only wipes the /system .. not /data .. if the links were there before the update.zip they will be there after

Fix_permissions mistery

Ok, so here is what puzzles me:
I have a MT3G, SuperOneClick rooted, with RA 1.7.0, busybox 1.18.4, all apps requiring superuser permissions are working flawlessly (Titanium, SetCPU, Root Explorer, Droid Wall, etc). Fix_permissions works with RA (other/fix uid mismatches) and ROM Manager, but when I open the emulator and type $su #fix_permissions, it gives me
bash: fix_permissions: command not found
In adb shell fix_permissions, permission is denied. All useful ideas how to solve this are much appreciated, thanks...
Anyone?
Sent through XDA App
Ok, I don't want to open a new topic, but really need some advice here! I just used Root Check in advanced mode, before it ran it asked for and received superuser permissions, then the detailed results were:
Congratulations! You have root access!
Alternate su bin location:
/sbin/su: Permission denied
Root user id:
uid=0(root)
Root group id:
gid=0(root)
Click to expand...
Click to collapse
Seriously, guys, please help, I dont have a clue whether I have a permanent root or not. I forgot to mention I'm using the T-Mobile OTA Froyo 2.2.1 FRG83D. I've rooted this same ROM once, 5-6 months ago, when it was pushed out, I had no problems, fix_permissions were working. Then I nandroid backed it up, so I can restore it if I don't like the other ROMs I used later (which were Ginger Yoshi RC7 -a great ROM, but the launcher was constantly restarting, and then back to Super D - most stable one, but lots of the good apps are not for 1.6 anymore). However, when I tried to restore Froyo, it didnt work, so I had to start over, using the following steps to get the OTA and root it. Please, let me know if I missed something or did it wrong:
1. I flashed sappimg.nbh with hboot to get to unrooted Cupcake
2. Flashed DRC92 and DMD64 Donut updates with stock recovery <3e>
3. Got the OTA Froyo from T-Mobile (*#*#checkin*#*#)
4. Used SuperOneClick to root, then restarted the phone
5. Using Droid Explorer, I installed a terminal emulator, then I uninstalled Superuser (have read in several threads people saying they had problems with it when it comes with SuperOneClick), using
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# rm /system/app/Superuser.apk
# pm uninstall com.noshufou.android.su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
$ exit
and reinstalled it from the market.
6. Installed the latest busybox with Busybox Installer.
7. Pasted flash_image and recovery.img (Amon RA 1.7.0) to the sdcard, then installed recovery:
$ su
# mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
# rm /system/etc/install-recovery.sh
# cd sdcard
# mount -o remount,exec /dev/block//vold/179:1 /sdcard
# ./flash_image recovery /sdcard/recovery.img
# exit
$ exit
8. And finally I started removing the unnecessary system apps (Amazon, MyFaves, etc) with the emulator, using the same method I did to remove Superuser in step 5
Click to expand...
Click to collapse
Now, as I mentioned before, I cannot run fix_permissions through the emulator, but it runs through ROM Manager and RA (fix package uid mismatches).
Why is that? Is it the ROM, which causes the problem?
I'm clueless, please help!

INT2EXT

i want to use INT2EXT in cm9 i followed this tutorial
xpmode said:
INT2EXT+ INSTALLATION TUTORIAL
IF YOU ALREADY HAVE S2E, LINK2SD OR SIMILAR, YOU MUST REPARTITION SD CARD AND FACTORY WIPE
int2ext+ is a relatively new script that instead of making symbolic links(Link2SD) or moving certain partitions(S2E) to sd, extends your internal storage into your ext partition in sd, which means S2E's potential space saving and Link2SD's stability combined together and gives you something to brag about.
PREPARATIONS
Download the latest build of CyanogenMod 9.
Download the latest version of CronMod INT2EXT+ here.
Open CyanogenMod 9 zip.
Navigate to /system/etc/init.d
Open INT2EXT+ zip.
Navigate to /system/etc/init.d
Add the file called 40int2ext in the /system/etc/init.d directory in CM9 zip.
INSTALLATION
Go to recovery, do factory reset and advanced > partition sd card.
Select 1024M for ext(for some reason, I selected 4096 and it only read the first 1GB-ish) and 0M for swap.
Wait until it says Done and goes to menu.
Go to Mounts and Storage.
Select USB storage and connect your phone to your computer.
Copy your modified CM9 zip file to the root of your sd.
Select unmount.
Reflash ROM.
Reboot.
After reboot, go to settings > developer settings > root access and select Apps and ADB.
Go to your adb directory and do adb shell.
Type su.
Then do:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Reboot.
After reboot, reboot into recovery and flash gapps.zip normally.
Then go to Applications and enjoy your new, extended internal storage.
Click to expand...
Click to collapse
can someone help me how to do adb shell and go to adb directory
Use the directory that you used to root your device.
Hpsgill said:
can someone help me how to do adb shell and go to adb directory
Click to expand...
Click to collapse
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Chaosgod27 said:
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Click to expand...
Click to collapse
Thanks
No worries =)
Chaosgod27 said:
No worries =)
Click to expand...
Click to collapse
can u tell me how to use other scripts eg apps2sd,link2sd and their works
Hmm, if you want. Right now I'm a bit busy with work...
Chaosgod27 said:
Hmm, if you want. Right now I'm a bit busy with work...
Click to expand...
Click to collapse
Anytime ,when u r free or pm me
Sent from my HTC Explorer A310 using xda premium
What did you want to know about them? You want to know how to install them or?
Chaosgod27 said:
What did you want to know about them? You want to know how to install them or?
Click to expand...
Click to collapse
Every thing about there scripts I never partation my memory card
Sent from my HTC Explorer A310 using xda premium
Chaosgod27 said:
Err, now that's funny. To do adb shell, all you have to do is put in the command adb shell
Isn't that funny? xD
What the guide meant for adb directory is the place where the adb.exe file is kept.
So all you have to do is put in cmd:
adb shell
and while you're in shell you just put in those commands:
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
After that to close the terminal, type in:
exit
then adb reboot
Hope that helps =)
Click to expand...
Click to collapse
Hmmm, you don't need adb for this. Just use terminal emulator on your phone. It comes installed by default on CM9 roms. Or you can search play store for android terminal emulator. The app is by Jack Palevich
Code:
su
mount -rwo remount /system
cd /system/etc/init.d
chmod 644 00banner
chmod 644 90userinit
mount -ro remount /system
Then again, I don't really see why it is necessary to deny execute permissions to these scripts in first place. They are just empty shells - unless they have been modified.
I'm using int2ext4 right now and never really had to...
EDIT: If you want to reverse these changes then
Code:
su
mount -rwo remount /system
chmod -R 755 /system/etc/init.d
mount -ro remount /system
Hpsgill said:
can u tell me how to use other scripts eg apps2sd,link2sd and their works
Click to expand...
Click to collapse
Script details:
a2sd,a2sd+,a2sd++,d2ext,d2ext+,int2ext,int2ext+,int2ext4,int2ext4+ --- forum.xda-developers.com/showthread.php?t=1716124
mount2sd --- forum.xda-developers.com/showthread.php?t=1342387
As of link2sd it uses installrecovery.sh file in /system/etc to mount sd-ext partition. It then moves apps/data/dalvik-cache to sd-ext and places symlinks at the original locations.
Take a look here where i've explained why symlink based apps/scripts should not be used on HTC explorer.
Hit thanks if i helped!:good::good:
sabaatworld said:
Script details:
a2sd,a2sd+,a2sd++,d2ext,d2ext+,int2ext,int2ext+,int2ext4,int2ext4+ --- forum.xda-developers.com/showthread.php?t=1716124
mount2sd --- forum.xda-developers.com/showthread.php?t=1342387
As of link2sd it uses installrecovery.sh file in /system/etc to mount sd-ext partition. It then moves apps/data/dalvik-cache to sd-ext and places symlinks at the original locations.
Take a look here where i've explained why symlink based apps/scripts should not be used on HTC explorer.
Hit thanks if i helped!:good::good:
Click to expand...
Click to collapse
thanks maaaaaan!!!
where is the adb directory?? do we have to install it in our pc or its there in our explorer?
Sent from my HTC Explorer A310e using xda premium
everything i did went well and i checked the internal memory its shows 850mb ... now the problem is when i type adb shell in terminal its say error:device not found ... so what should i do ???

[Q] removing BT5 arm off xoom

Hey, I installed BT5 arm on the Motorola Xoom wifi and i would like to know how to completely remove it from my device. My device is rooted and i have tried to delete the whole BT5 file with astro file manager and absolute file manager but neither of them worked. I was wondering if anyone knows another way of doing it.
I tried deleting it with commands in terminal emulator but its a read only file. Wouldn't chmod help with that? If so how would i use it?
jimmothycharles said:
I tried deleting it with commands in terminal emulator but its a read only file. Wouldn't chmod help with that? If so how would i use it?
Click to expand...
Click to collapse
Go read the backtrack 5 thread. There is a link on how to remove it. That really should be the first thing you check before asking
ok thanks, ill do that the next time i have a problem
I couldn't find it. I think it might be a tiamat BT5 img and i have the remover tool but im not quite sure how to use it. I just flashed it like i would do with a rom but it says installation failed. what would i do to fix that?
jimmothycharles said:
I couldn't find it. I think it might be a tiamat BT5 img and i have the remover tool but im not quite sure how to use it. I just flashed it like i would do with a rom but it says installation failed. what would i do to fix that?
Click to expand...
Click to collapse
Common knowledge - system must be set to RW
Here is an alternate route- manually
How To:
ADB Shell Folder Removal - (we will use BT5 as an example)
++++++++++++++++++++++++++++
1. Connect Xoom to pc
2. Boot into recovery
3. Toggle to internal storage as /sdcard
4. mount /data
Enter adb shell via pc
(cd to file location) in this case BT5, is in the sdcard directory
Code:
Code:
cd /sdcard #
(once typed, you will be at.... /data/media prompt)
if after the above command and you are not at the /data/media prompt start over)
Code:
Code:
rm -r BT5
(BT5 is the stubborn Folder)
*Side note ... This works for any other stubborn folder that you want to delete as well...
USE AT YOU OWN RISK - MAKE SURE YOU DO A BACKUP FIRST
If this was helpful Hit The Thanks!
it didnt work it said that rm failed for BT5, permission denied
jimmothycharles said:
it didnt work it said that rm failed for BT5, permission denied
Click to expand...
Click to collapse
Come on now, lol Your device must be set to rw. Google can guide you.
Mjamocha said:
Come on now, lol Your device must be set to rw. Google can guide you.
Click to expand...
Click to collapse
ok well this is what i got when i tried to do that.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>cd C:\Users\josh\Desktop\xoom files\BT5
C:\Users\josh\Desktop\xoom files\BT5>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # cd storage/sdcard0/0/0/0
cd storage/sdcard0/0/0/0
[email protected]:/storage/sdcard0/0/0/0 # ls
ls
Android
BT5
Box
DCIM
Download
Evernote
Pictures
SELog.txt
Video
airdroid
goodies
goomanager
tmp
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 # rm BT5
rm BT5
rm failed for BT5, Is a directory
255|[email protected]:/storage/sdcard0/0/0/0 # cd
cd
[email protected]:/data # exit
exit
C:\Users\josh\Desktop\xoom files\BT5>adb shell
[email protected]:/ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
[email protected]:/ # cd storage/sdcard0/0/0/0
cd storage/sdcard0/0/0/0
[email protected]:/storage/sdcard0/0/0/0 # ls
ls
Android
BT5
Box
DCIM
Download
Evernote
Pictures
SELog.txt
Video
airdroid
goodies
goomanager
tmp
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 # rm -rBT5
rm -rBT5
rm failed for -rBT5, No such file or directory
255|[email protected]:/storage/sdcard0/0/0/0 # chmod 777 BT5
chmod 777 BT5
[email protected]:/storage/sdcard0/0/0/0 # rm -r BT5
rm -r BT5
rm failed for BT5, Permission denied
255|[email protected]:/storage/sdcard0/0/0/0 #
I looked up on google how to mount system rw and thats where [email protected]:/ # mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system came from. then i tried rm -r BT5 after that and it was still denied. so i tried to
do chmod 777 BT5 to give all permissions and then when i tried to remove it again it was still denied.
I looked up the permissions of the file and its set to rwxrwxr-x. so chmod apparently didn't work

Categories

Resources