I'm sorry to post this in the Fascinate forum, but as you all know Cellular South's version the "Showcase" is identical in hardware as is the Mesmerize, but there isn't a forum for either of them..
I see there's plenty of kernels and etc.. But is there just a simple lag fix that I can do to my Showcase that will make every day use better and less laggy?
A simple yes or no is fine with me.
if there is a way a link post or explanation would be VERY appreciated.
Thanks,
Elijahblake
(PS)Sort of on the same subject, but I read that gingerbread is going to support ext4 file system. I know the Galaxy S uses the RFS file system which I believe is where we get the lag in the first place.. Will it be possible to switch file system formats?
I'm not real familiar with all these Linux formats. Would it be similar to reformatting like from FAT32 to NTFS?
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
elijahblake said:
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
Click to expand...
Click to collapse
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
jt1134 said:
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
Click to expand...
Click to collapse
will do.. May take me some while to get all this info gathered..
quick question? I've read of some people not being able to see certain apps in the market after rooting.. Is this still the case?
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
elijahblake said:
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
Click to expand...
Click to collapse
To get the upgrade, you shouldn't have to un-root, but you should probably disable voodoo first as the update will almost certainly have a new kernel, and applying the update without disabling voodoo could cause quite a headache.
If you do apply the update right away, you could quite possibly loose root, so you may want to wait until the devs re-root the update. This could make things easier for you as the rooted update will also likely be cleaned up some.
To disable voodoo, you'd just need to create a file called "disable_lagfix" in /sdcard/voodoo and then reboot your phone. See the thread in the dev forum about removing voodoo for more details if you want.
ok well it looks like I'm rooted.. Now I tried to open the ADB that came in the fascinate root zip but it's not opening for more than a split second... you have a download link?
Also can uninstall all this bloatware now??
edit.. thought I had Android SDK on this laptop.. Downloading it now
jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
elijahblake said:
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
Click to expand...
Click to collapse
I have c:\androidsdk
I put ADB inside tools and it sees my device when I run ADB devices
But on the commands you listed nothing happens, I'm not sure if that's the entire commands or if I'm supposed to add something to them..
Try to run the following
Code:
adb shell cat /dev/block/bml7 > /sdcard/zImage
adb shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
adb shell mount
or just typing "adb shell" and entering the commands at the new prompt, and typing "exit" to get back to the normal command prompt.
here's what happened..
the first two commands didn't work. DO i need to create a folder name zImages?
The second command said access denied..
You tell me if the mount worked haha..
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
well, it granted me SU rights.. but still a no go...
i figured since i was in shell i shouldn't type that.. still got no directory found...
imnuts said:
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
Click to expand...
Click to collapse
would root explorer make this any easier?
I just tested out all of the commands on my Fascinate and they all worked, so I'm guessing that the Showcase is putting stuff in a different place. jt will have to help you out further as I'm not sure of where else to look for the info he needs.
elijahblake said:
i figured since i was in shell i shouldn't type that.. still got no directory found...
Click to expand...
Click to collapse
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
GeekMouse said:
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
Click to expand...
Click to collapse
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
It doesn't need shell at the beginning.
elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
This is how it should be typed
Code:
adb shell
su
cat /dev/block/bml7 > /sdcard/zImage
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
Related
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
killabee44 said:
If anyone can post a link to a detailed Ubuntu guide for newbies to root the Hero and remove stock apps, I would appreciate it. The guide posted doesn't go into too much detail in Ubuntu since the OP said that he could not get it to work in Ubuntu. Thanks.
Click to expand...
Click to collapse
Wouldnt the Mac version work since they are both *nix?
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
romeosidvicious,
Thanks for all your hard work. I and others really appreciate it.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Yep, that is something I had to do in windows XP as well. It will help many others as well. Thanks.
Stevious said:
I was able to root my Sprint HTC hero just fine running Jaunty. I followed the instructions in the guide you mentioned, for Ubuntu. One thing I noticed is before adb recognized my phone, I had to start "HTC Sync" from the phone's notifications. Just ignore the error about it not finding HTC Sync on your PC. Obviously it never will since HTC Sync is a Windows app
Click to expand...
Click to collapse
Great, now my Ubuntu Jaunty machine won't detect the phone. I did the above but it still won't work. Im gonna reboot and retry...
Edit:
Nope, no love for my Ubuntu. It's not seeing the Hero. I will have to research this one.. If anyone has suggestions, please chime in.
Ok, found a solution:
http://forum.xda-developers.com/showthread.php?t=537508
----------------------------------------------------------------
Here is the part that solved it for me:
Setting up UDEV to recognize HTC Device -
1. Type the following into a terminal (Applications > Accessories > Terminal):
Code:
gksudo gedit /etc/udev/rules.d/51-android.rules
2. Now add the following line to the blank file:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. Click save and close.
4. To restart udev, open up a terminal and enter:
Code:
sudo /etc/init.d/udev restart
---------------------------------------------------------------------
Thanks to Wddglr for all the useful info. It looks like I will be using other things he posted about. Hopefully that info will help someone else.
Just curious, which version of Ubuntu are you running? I didn't have to make any UDEV changes in Jaunty.
romeosidvicious said:
Here's the step by step that worked for me: http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I typed it so I could find it easily if necessary and figured why not share it....
Click to expand...
Click to collapse
I want to follow through with this...
I was following this
http://www.youtube.com/watch?v=ArMO5IHS2eI
until the step came to plug it in and then he suggested typing "adb devices" which told me this.
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Onompoly2 said:
"~/android-sdk-linux/tools$ adb devices
bash: adb: command not found"
So I came here and I want to follow the links tutorial.. two questions
Is it safe to proceed even though i've been told adb: Command not found
will i be able to proceed although ive been told this command is not found?
Click to expand...
Click to collapse
Try:
sudo ./adb devices
From the same directory. Or, you can specify the full path:
sudo ~/android-sdk-linux/tools/adb devices
To answer your other questions, it won't work if it says the command is not found.
Okay
It worked but I must have turned into an idiot when i decided my operating system was good enough.
This isn't working, and I am not even upgraded to the operating system the tutorial is written for...
194 updates due... running 8.04 with a bunch of double half installed broken applications.. maybe I should reformat.
I'll let you guys know how things go which ever way it goes.
back again. fresh 9.10 install fully updated.
Following this
http://romeosidvicious.com/2009/11/09/rooting-the-htc-hero-with-ubuntu-karmic/
I get this far
[email protected]:~# sudo su
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools#
[email protected]:~/android-sdk-linux/tools# ./adb push ../asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:~/android-sdk-linux/tools# ./adb shell chmod 0755 /data/local/asroot2
[email protected]:~/android-sdk-linux/tools# /data/local/asroot2 /system/bin/sh
bash: /data/local/asroot2: No such file or directory
[email protected]:~/android-sdk-linux/tools# ./adb shell /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/559/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It seems as though after it says "SUCCESS" that my terminal just stops responding to code...
Tried reading the link to where he made the tutorial from, but its a mixture of ubuntu and windows with 30 pages of posts.
Any thoughts/help?
Thanks
[Continuing]
So just pretending that everything is going as planned I reboot the phone and it actually turns my computer off as well..
So I continue with the steps.
[email protected]:~# cd ~/android-sdk-linux/tools
[email protected]:~/android-sdk-linux/tools# ./adb push ../recovery-RA-heroc-v1.2.3.img /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
1199 KB/s (3352576 bytes in 2.730s)
[email protected]:~/android-sdk-linux/tools# ./adb shell
$ su
su: permission denied
Click to expand...
Click to collapse
But Get permission denied.
I'm going to go ahead and start over but skip the first line that i input that said SUCCESS and stopped the terminal.
(really don't know what i'm doing but I think I need to get these two lines in
cat sh > su
chmod 4755 su)
EDIT: on second thought perhaps this has something to do with me being logged in as root on my computer from the get go, i'll try that.
A dummy and his cell phone perhaps soon part.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
reboot
Click to expand...
Click to collapse
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
I didn't, although i did try that as well
after I would do the mount commands i would no longer get a $ or a # sign, it was just a bunch of nothingness...
I ended up booting up my girlfriends vista and then spent quite a while figuring out how to get the driver for adb, I had to follow two different windows guides for rooting for some reason as well... so if that says anything.. just imagine how long it took me to realize how to get the driver hahah
buck2202 said:
It looks like you copy/pasted this whole section as a block. I think you need to execute the commands one at a time, and wait for a new "#" prompt between each one. The reason the terminal stops responding is that as one long string, it's not a meaningful command.
Click to expand...
Click to collapse
no, I'm having the same problem. After the "mount" command it gives me nothing.
Edit: doing this in karmic
Odd. I've had no problems following the generic procedure from theunlockr on ubuntu. My only suggestion would be to turn
Code:
./adb shell /data/local/asroot2 /system/bin/sh
into
Code:
./adb shell
/data/local/asroot2 /system/bin/sh
I'm not sure why it should make a difference, but on my computer "./adb shell <command>" exits the shell when it finishes. From what you've pasted, it doesn't look like that's happening to you, but that's my only guess right now.
If you run "./adb devices" do you see your serial number?
And out of curiosity, why are you running as root on your computer? (sudo su) Have you tried just starting the adb server as root, and running the rest of the commands normally? Does this work?
Code:
./adb kill-server
sudo ./adb start-server
./adb devices
So, everything I flash a new ROM, I have some commands I run via ADB on my laptop that moves some APKs around on the phone as well as pushing some to the phone. I would like to compile these commands into an update.zip file so that I don't have to be near a laptop every time I want to flash a new ROM. I read up on update-script syntax, but I didn't see anything regarding ADB commands. Is it possible to administer ADB commands within update-script syntax? The one I need to use the most is mv, so if there is an alternative to that in the update-script syntax, that would work too.
cambunch said:
So, everything I flash a new ROM, I have some commands I run via ADB on my laptop that moves some APKs around on the phone as well as pushing some to the phone. I would like to compile these commands into an update.zip file so that I don't have to be near a laptop every time I want to flash a new ROM. I read up on update-script syntax, but I didn't see anything regarding ADB commands. Is it possible to administer ADB commands within update-script syntax? The one I need to use the most is mv, so if there is an alternative to that in the update-script syntax, that would work too.
Click to expand...
Click to collapse
Well, mv for example is not an ADB command (adb shell mv) it's a shell command. So I think you want to be able to run shell commands from an update/r script?
If that's the case, download my rom and have a look at the build script, it executes a comprehensive shell script which might give you some pointers.
djmcnz said:
Well, mv for example is not an ADB command (adb shell mv) it's a shell command. So I think you want to be able to run shell commands from an update/r script?
If that's the case, download my rom and have a look at the build script, it executes a comprehensive shell script which might give you some pointers.
Click to expand...
Click to collapse
Thanks, I will check it out now.
cambunch said:
Thanks, I will check it out now.
Click to expand...
Click to collapse
djmcnz said:
Well, mv for example is not an ADB command (adb shell mv) it's a shell command. So I think you want to be able to run shell commands from an update/r script?
If that's the case, download my rom and have a look at the build script, it executes a comprehensive shell script which might give you some pointers.
Click to expand...
Click to collapse
Bump...
Care to post the build script instead of us having to download a ROM for it?
[GUIDE] How to do a full backup to /sdcard-ext
How to backup your atrix with adb
Prerequisites:
update: adb,fastboot,moto-fastboot all in one zip
1. Get adb (from one of the following) (awesome thread about adb where to get it and how to use it)
a) Android adk
b) Gladroot or many of the other older rooting methods that are script based in the stickys
c) obtain moto-fastboot for your os version
32 or 64 bit ms windows xp, vista, or 7
64 bit linux
32 bit linux
Mac osX
fastbootandfriends? d) Drivers for your device - windows 32 and 64 bit (motorola.com site) other os's do not need driver files.
2. Obtain root on your device
a) look in the sticky threads (I prefer the CWM zip here)
Warnings:
Do not restore /data "/dev/block/mmcblk0p16" if your going from one rom to another. use titanium backup or another utility.
Do not restore /pds "/dev/block/mmcblk0p3" unless you have a issue with your touchscreen or unless instructed to do so by someone that understands /pds.
Do not ever share your pds.img with anyone
Backup:
adb shell
su
Then type the dd commands below to create a image file on your external sdcard for the following...
Boot
dd if=/dev/block/mmcblk0p11 of=/mnt/sdcard-ext/boot.img
Click to expand...
Click to collapse
System
dd if=/dev/block/mmcblk0p12 of=/mnt/sdcard-ext/system.img
Click to expand...
Click to collapse
Data
removed use tibu
Click to expand...
Click to collapse
Osh/Webtop
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard-ext/osh.img
Click to expand...
Click to collapse
Recovery
dd if=/dev/block/mmcblk0p10 of=/mnt/sdcard-ext/recovery.img
Click to expand...
Click to collapse
PDS
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard-ext/pds.img
Click to expand...
Click to collapse
MOVE YOUR IMAGE BACKUPS OFF YOUR SDCARD!!!
Restore:
to restore use moto-fastboot (from the pudding thread)
boot
moto-fastboot flash boot boot.img
Click to expand...
Click to collapse
System
moto-fastboot flash system system.img
Click to expand...
Click to collapse
Data
removed use tibu
Click to expand...
Click to collapse
Osh/Webtop
moto-fastboot flash webtop osh.img
Click to expand...
Click to collapse
Recovery
moto-fastboot flash recovery recovery.img
Click to expand...
Click to collapse
WARNING - PDS is tricky - Do not touch pds unless you have to.
Also do not ever share your pds.img with anyone
PDS
adb push pds.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/pds.img
dd if=/data/local/tmp/pds.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
Why not just use cwm?
Sent from my Motorola Atrix using the XDA App
thebeardedchild said:
Why not just use cwm?
Sent from my Motorola Atrix using the XDA App
Click to expand...
Click to collapse
Because CWM nandroid restore has messed up a bunch of users touchscreens
Great info in one place, thanks!
Thanks
Sent from my MB860 using XDA App
I had to change the restore process for data to use adb as moto-fastboot will not flash a image that big.
my /data was 2 gig.
do not forget to delete data.img from /sdcard after you restore.
also keep in mind that your /data will be pretty big and will take quite a long time to restore.
also do not use DD if you have fat fingers and are prone to mistyping "of" and "if" since o and i are next to each other on most keyboards.
joe ferreira said:
Because CWM nandroid restore has messed up a bunch of users touchscreens
Click to expand...
Click to collapse
Wow that's stupid...Is there a fix on the way for that? This method here seems a little more intensive than just using CWM..
Oh well, thanks for giving us something to use while CWM sucks!
can we run these backup commands phone-side via terminal emulator?
the dd commands are best ran via adb
you can run them in terminal emulator but if terminal emulater fc's while your restoring then it could cause issues.
adb is the best way to do this.
really you should all be using titanium backup for /data anyways.
to avoid fat fingers you can also copy and paste.
Great thread Joe!
Permission denied
So I'm a bit of a n00b but I feel like I do pretty well at following directions. Obviously I'm missing something here because after typing "adb shell" and getting the '$' prompt I type the "su" command and am bumped to a new line without a '$' prompt. So far so good, but as soon as I type "dd" I immediately get "Permission denied". It won't even let me enter the entire line! Any help would be greatly appreciated.
AjaxTheCleaner said:
So I'm a bit of a n00b but I feel like I do pretty well at following directions. Obviously I'm missing something here because after typing "adb shell" and getting the '$' prompt I type the "su" command and am bumped to a new line without a '$' prompt. So far so good, but as soon as I type "dd" I immediately get "Permission denied". It won't even let me enter the entire line! Any help would be greatly appreciated.
Click to expand...
Click to collapse
you need root.
you type
adb shell
Click to expand...
Click to collapse
then type
su
Click to expand...
Click to collapse
then it will prompt you on the phone if you have root access to accept the root access request.
I had to remove the /data backup part until I can work the kinks out.
I will update and repost when it is finished
Thank you for the helpful response! I was able to install and run SuperUser on the device so I thought I had successfully rooted. Having been in helpdesk and IT for years there really is no excuse. I failed to follow my own first rule which is to reboot. After restarting my phone I was able to successfully logon to su and execute those commands, but it took finding out that I did in fact NOT have root access to prompt me to try such a thing. Thanks for providing helpful info and not flaming me (sincerely!)
what happens if you are on windows and not linux? can't restore the larger files through fastboot.
y2whisper said:
what happens if you are on windows and not linux? can't restore the larger files through fastboot.
Click to expand...
Click to collapse
your host system does not have anything to do with what I was discussing about image size.
the backup of /data was something that I had to takeout until i figure it out.
as always you should take multiple backups. I use titanium backup as well as the methods discussed in this thread.
i see. so how do I use moto-fastboot? to restore? (where to put the files etc)
y2whisper said:
i see. so how do I use moto-fastboot? to restore? (where to put the files etc)
Click to expand...
Click to collapse
correct me if I'm wrong, but I think you put the files in the fastboot folder.
if you don't put it in the fastboot folder -- you would have to type the full path of the file?
so im guessing --
fastboot flash recovery C:\MyDocuments\recovery.img
or something like that? im a noob too hehe
yeah that part i got down, but when I try to restore the system.img it doesn't let me due to the size.
EDIT
it says image is to big, use 0x10000000 bytes chunks
Failed <remote: 00000006>>
my sys files is 327680kb
Nevermind managed to find my way thanks to Magnetox!
I have bricked my device when I tried to copy framework-res.apk to the system folder. I renamed the old framework-res.apk to framework-res.apk.bak but before I could paste the new one the phone freaked out and rebooted and now I'm stuck at the ATT white screen. I have adb access though so I'm hoping I can just push the framework-res file using adb. Every time I try this though I get an error saying file system is read only. I know all I probably need to do is get the computer to mount system as read/write. I just don't know how to do this. Is there anyone out there who can help me out?
Modified from:
http://forum.xda-developers.com/showthread.php?p=41339365
You may need to do:
mount -o remount,rw /system
chmod 777 /system/framework
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
jack_slapped said:
Thank you for your quick reply. I'm kind of a novice when it comes to adb so bear with me, but when I use those commands I get 'mount' is not recognized as an internal or external command. I'm not sure if it matters or not but I'm running windows XP and my working directory is in c:\android-sdk\platform-tools when I tried executing "mount -o remount,rw /system".
Click to expand...
Click to collapse
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
jack_slapped said:
Okay I tried changing the command to "adb shell mount -o remount,rw /system" now I get the error mount operation not permitted. I hope this doesn't mean I borked it. . . Also want to note that I did root the phone.
Click to expand...
Click to collapse
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
alacrify said:
You need to do some reading before you go any further - please. ADB is a command shell, and the commands he gave you are for running IN ADB after it's successfully connected to the phone.
There are lots of good writeups on using ADB all over the place.
Click to expand...
Click to collapse
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
jack_slapped said:
I know believe me when I say I'm trying to read as much as I possibly can. Nobody wants this phone fixed more than me. It's just alot of new stuff and I'm not entirely familiar with it. I think I'm connected with adb and started a shell using "adb -s myserial shell". I input the first command and got "mount: operation not permitted". Not really sure why it would say that considering I rooted the device.
Click to expand...
Click to collapse
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
gwbard said:
You need to get INTO the shell first -- then execute the commands.
Also, always stop the system before modifying stuff, especially framework!
like so:
Code:
> [B]adb shell[/B]
$ [B]su[/B]
# [B]mount -o rw,remount /system[/B]
# [B]stop[/B]
# **[I]cp or mv whatever here[/I]**
# [B]reboot[/B]
your cmd prompt will return after reboot
Click to expand...
Click to collapse
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Aou said:
Be sure to follow gwbard's directions a little closer. The first command inside the ADB shell is "su" which will elevate you to root - this will be necessary in order to execute the "mount" command.
From your command line (assuming in Windows), you'll run the "adb shell" command that gwbard showed. It should give you a prompt that ends with a dollar sign. Once you execute the "su" command, you'll see that change to a pound/hash sign (#).
Click to expand...
Click to collapse
Yea I posted that last one before I saw his instructions. They were right on point. Thanks guys!
jack_slapped said:
Dude you are the man! That did the trick. I really appreciate it. I'm still trying to figure out exactly what a shell is and how that ties into adb but I learned a good bit about it from today. I've used linux before and I have heard of a shell but never really understood what exactly it was. Anyways thanks again for everyone who helped me get this working.
Click to expand...
Click to collapse
When you click "start" and type "cmd", you're starting a shell. They're command interpreters that extend functionality in specific ways. like "dir" for the Windows/DOS command shell, and "su" or "mount" for adb. Lots of good writeups on that around too
i'm new here so first of all hello to everyone.
heres my problem. hopefully somebody can help me.
how can i get an inode of a file. that meens to read a
particular part in the data partition. of course that
could only be possible with su, thats clear.
You've got to use the command line for every root thing.
You can get the inode as described here: http://www.cyberciti.biz/faq/howto-print-inode-data-structure/
How to use root commands: http://forum.xda-developers.com/showthread.php?t=2226664
nikwen said:
You've got to use the command line for every root thing.
You can get the inode as described here: http://www.cyberciti.biz/faq/howto-print-inode-data-structure/
How to use root commands: http://forum.xda-developers.com/showthread.php?t=2226664
Click to expand...
Click to collapse
thanks for the quick response.
i find out that ls has no option -i on android to show inodes.
does anybody know another way to get them
xiyuo said:
i find out that ls has no option -i on android to show inodes.
does anybody know another way to get them
Click to expand...
Click to collapse
Compile or use a version of busybox which has it and use that one. Add it to your apps assets and copy it to the data directory of your app. Then use that binary for the ls command.
That part is very difficult on Android. On one device you have got the ls command but the output might look completely different on another phone. (Some time ago someone reported that he noticed "ls" being linked to "ls -l" on one phone. On another phone the option "-l" might be missing.
So it is recommended to use busybox for every root command.
..
nikwen said:
Compile or use a version of busybox which has it and use that one. Add it to your apps assets and copy it to the data directory of your app. Then use that binary for the ls command.
So it is recommended to use busybox for every root command.
Click to expand...
Click to collapse
i did that.
but with
./busybox ls -i
i get
cant execute permission denied.
even if i use su. how could that be?
does anybody know how i get the permission?
xiyuo said:
i did that.
but with
./busybox ls -i
i get
cant execute permission denied.
even if i use su. how could that be?
does anybody know how i get the permission?
Click to expand...
Click to collapse
In Linux you have to add the right to execute it first:
Code:
su
chmod 775 <filename>