Related
Hi everyone! Im having a little problem, all your help will be really appreciated, I rooted my phone with the paul Obrien guide since day 1, but the thing is that I cant write on the /data or /system partitions, not even using command prompt and adb, or in an emulator over the phone, and in recovery mode using command promp its impossible to acces any shell command ... Im rooted right!? I have the icon with the ninja or that little black guy (haha), and Ive installed apps like market enabler etc... At some point I think i installed busybox, please keep your answers as newbi as possible, im just starting with android.. Thanks!!
greeting from shanghai!
It's normal that you can't access it whilst on the phone (blame HTC I think).
You will need to run this from recovery before you can see your /system folder:
Code:
adb shell mount /system
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu. (ubuntu.com ...download the iso, boot as a live cd, install gparted....google for more details)
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools installed and working (adb is included with the SDK, so install the sdk and you will have adb. GOOGLE "adb sdk install" for more details):
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
What I've Used Root For So Far
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop. EDIT: The software MAGICALLY reappears after reboot. I can't wait to crack this phone!
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
good stuff bro ima try this.
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
yes but
Dalamak said:
this is all well and good, but the point of rooting is the custom roms, we've had a Temp root since day one, but no reason to root it.
Click to expand...
Click to collapse
Yes we did BUT that temp root method didn't allow access to the real files of the device. It accessed copies (simply put I know). This temp root gives ROOT access to the entire device which puts us a GIANT step closer to a permanent solution.
Also, the other temp method couldn't handle installing Apps in one mode and using them in another. Some Apps disappeared at reboot. With this method, Apps that are installed in either mode are always accessible.
Basically I did this for my own device and just wanted to share with others
But of course I thank you for your efforts, you are a god, I meant no disrespect
texasaggie1 said:
Big props to SAINTH for his guide. Some of my guide is a word for word rip off of his guide. I just copied it and played around to get a simpler way to root. It is still temporary but now when you have "SU" you are messing with the ACTUAL files on the device, NOT a copy on your SD card. Also, programs installed in root mode are still on your device when not in root mode.
I wrote this entire post while tethered to my device using this method.
NOTE: IF SOMEONE COULD GIVE ME A RECOVERY TO FLASH, I THINK WE WOULD HAVE PERMANENT ROOT
OK, I am a dev noob... total noob... please no flaming...
Getting Started: (ONE TIME STUFF)
1) Partition your SD card with at least a 300mb EXT3 partition. I Used gparted in Ubuntu.
2) Download and install from Market: Bar Control. I will explain why in a moment.
3) Download and extract visionroot.zip into your tools directory.
4) Use adb to install programs and transfer files to your device:
On the phone, enable "USB debugging" in Menu -> Settings -> Applications -> Development
On a computer with the Android SDK tools (adb) installed and working:
adb push busybox /data/local
adb push rage /data/local
adb push root /data/local
adb push rsync /data/local
adb push su /data/local
adb install Term.apk
adb install Superuser.apk
adb shell chmod 755 /data/local/busybox /data/local/rage /data/local/rsync /data/local/root
5) Run Bar Control and select Terminal Emulator to run in the task bar. Early on, when I was playing around with this rooting method, temp root would just disappear. I found it stays if I use Bar Control. I think since Terminal Emulator is in the task bar, android is less likely to kill it. I did this whole post using tethering without root ever going away.
Ok. SETUP stage is now over. From this point on is how you will get root each time you boot up your phone.
Getting Root:
1) On the phone, open "Terminal Emulator" from the taskbar and type:
cd data
cd local
./rage
Wait for it to say "[+] Forked NNNN childs." then press the back button until you are back at the home screen. It will be slow for a bit.
2) Open "Terminal Emulator" again from the task bar and it should force close. It's ok if it doesn't. Just skip to #3.
3) Open "Terminal Emulator" one more time from the task bar and the prompt should display "#". This is the ROOT prompt! You are almost golden now! Then type:
cd data
cd local
./root
You may get some "Killall: Can't kill such and such" messages. Not a problem.
DO NOT hit the back button. You want terminal to keep running. Hit the Home Button.
YOU NOW HAVE ROOT! Superuser should be working too. We may find that we dont need bar control and terminal running. Let me know and I will change my post.
Click to expand...
Click to collapse
Dalamak said:
But of course I thank you for your efforts, you are a god, I meant no disrespect
Click to expand...
Click to collapse
LOL hahahah thats funny. I'm def not a god at this
Good job man! This will definitely make it seemer on the folks who aren't Linux friendly or lazy folks like me. Oh and btw... you're the futherest thing from a newb! Hahahha! You've been here longer than me. Its rare that I see the real old school guys here anymore. Weren't you in the wizard or tornado sub forum many years ago. You seem familiar...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Nevermind. I've decided to retract my comment and just try the process to see what happens.
Method worked amazingly well!
Thank you for this!!
Awesome job!
Sent from my T-Mobile G2 using XDA App
Will this work with the 4 click on-device root apk posted in this thread: http://forum.xda-developers.com/showpost.php?p=8535854&postcount=95 ?
Looks like a great guide as only 1 part is required - this allows me to part in my G1 AmonRa Recovery FTW!~111
(Also a great option if you are worried about booting up your G2 after formatting the SD as any progs looking for files there will be disappointed until you can copy them back ...)
Running a continuous Ping in Term now to see if that does the trick ...
EDIT:
Alright! this is awesome!
Q:
IF all we have to do to keep root is to keep the shell open - can't we run a prog or command to prioritize that prog ... like ... i remember that auto taskiller had settings against apps that were in the forgroud, background, background services etc ...
can we fool the OS into thinking this is allways a foreground process even though it's really running in BG ...or somehow give it highest priority?
EDIT 2:
Installed WirelesTeather.apk and ran and installed binaries - SU came up and granted all permission w/o issue - everything looked good.
Didn't open any other programs and decided to test it later, after noticing the AP didn't show I checked Terminal from the taskbar and it was back to $ (was closed by system)
I am running a fish aquarium for livewallpaper - so I'm sure this is why it closed as I'm running more processes at idle ... however, it looks like opening pretty much anything will cause the terminal to close and kill the "temp root'
Running a continuous Ping in Term now to see if that does the trick
FINAL EDIT:
OK! Ran continuous ping, opened Quake 3 - played for a bit - closed it.
Checked Term from the status bar - My Ping is still running !!1111 (IE the shell didn't close and we still have root)
So ... maybe this helps
You are the man. Downloaded. Tested. It works!
Sent from my T-Mobile G2 using XDA App
GREAT WORK!
Got it up and running, and just got 2.26 down, 1.23 up on my laptop off wireless tether.
so since this works directly with system files what happens if you try to metamorph something..will it revert on reboot or stay
Excellent job!
You are a genius! Your guide worked perfectly! I am typing this while tethered to the G2 - I agree with you, getting Root for tethering is worth the hassle of getting Root access! Keep up the great work!
I had been taking the SIM chip from my G2 to G1 (rooted, of course!) for Internet access - No more! Thanks again!
sino8r said:
...
Oh btw, someone posted a clockwork recovery that was allegedly compatible with the G2 but I don't think anyone had the balls to flash it. Its in the root think tank thread...
Click to expand...
Click to collapse
ive tried, several different ways, even ones that had a good chance of bricking, i.e. messing with ruu, and swapping files in the middle of flashing, just to try and get this perm root
texasaggie1 said:
Some people are questioning the value of root without custom ROM's. Here is what i have used ROOT for on this ROM so far:
1) Wireless Tether - this alone is worth it! The 9-5 version from this page works amazingly on the G2:
http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=NexusOne
2) Uninstall Crapware - I used Titanium to uninstall Web2Go. What a pile of steamy poop.
3) Back up with Titanium - Most awesome backup program out there. Needs root to work.
Click to expand...
Click to collapse
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Which Version?
aacrabtree said:
For Wireless Tether, I'm getting an error where it can't start access point. Anyone else have that problem? My computer won't recognize it without it.
EDIT:
Never mind, access point won't start if WiFi is on, and WiFi Tether isn't automatically shutting it off (like I think it's done on other phones), so if anyone else has the problem, turn off WiFi, then run WiFi Tether.
Click to expand...
Click to collapse
Which tethering apk are you using? If you are using the one from the link I provided it should work. I am not having to turn off wifi first for it to work for me.
Hi,
i have recently bought an HTC desire Z (G2) device, and downloaded a 163MB .zip rom. what do i have to do to install it??
i searched every where and could not find an answer!!
thanks
Look here:
http://forum.xda-developers.com/showthread.php?t=801206
You shall find all answers to your questions there
Razorless said:
Look here:
http://forum.xda-developers.com/showthread.php?t=801206
You shall find all answers to your questions there
Click to expand...
Click to collapse
Flash the ROM via recovery. I realize that's vague but you need clockworkmod recovery and to do that you need to have s-off. And to get s-off is a whole new thing all together because you need perm root
To root it, s-off it and rom flash it, you have to be willing to accept the consequences if you don't read enough and if you make a mistake!
And, that's the key, read everything and keep reading until it makes sense to you. Then follow the instructions to the "T" make sure you know your builds and then it's a leap off faith.......if you don't understand something, ask a question or two. There is all the info that you need right in the threads. Good luck and don't be in a hurry . Happy New Year.
thanks all, i really appreciate your fast response.
actually i just want to enable arabic support on my htc desire z, and i downloaded the arabic files from
http://ardoid.com/?p=189
and installed visionary and done the perm root with su permissions and get a # after typing su in terminal
i copied the zip files to the sd, rebooted and selected recovery, then applied update.zip, the phone rebooted but without any success of arabizing.
my kernel is 2.6.32.21-gd2764ed older according to wiki
http://forum.xda-developers.com/wik...Subsidy_Unlock.2C_SuperCID.2C_and_Radio_S-OFF
my question is, do i need to s off to get the files installed? do i have to remove visionary as a second step with removing rooting?
the status is that my phone has permaroot, and what i understood is that i am a step away from s off using gfree, i downloaded the file to my mac, and copied to the sd card.
i have super user
su
#
i have understood adb, and terminal, and copied the script but resulted with errors, script used
cd /data/local
chmod 777 gfree
./gfree
sync
error result on phone after chmod 777 gfree
unable to chmod gfree:no such file or directory
#
i have copied gfree.zip to sd card via mounting the phone via usb. and then changed the mode to charging mode automatically and enabled usb debugging.
again, i would appreciate your efforts, since this thread is closed;
http://forum.xda-developers.com/showthread.php?t=857390&page=15
Microzift said:
i have understood adb, and terminal, and copied the script but resulted with errors, script used
Click to expand...
Click to collapse
The error you are receiving means you don't actually have gfree on your phone (at least not in the right location). Did you receive any errors from ADB when you pushed the gfree file? Also, be sure you pushed the actual gfree file and not the zip (you need to extract it from the zip first).
Microzift said:
i have copied gfree.zip to sd card via mounting the phone via usb. and then changed the mode to charging mode automatically and enabled usb debugging.
Click to expand...
Click to collapse
Are you saying you tried this as well? Or did you not actually use ADB? If you are trying to accomplish this without ADB, you might want to take a look at this thread for instructions: http://forum.xda-developers.com/showthread.php?t=903152. And again, you will need to use the contents of the zip file, not the zip itself.
ianmcquinn said:
The error you are receiving means you don't actually have gfree on your phone (at least not in the right location). Did you receive any errors from ADB when you pushed the gfree file? Also, be sure you pushed the actual gfree file and not the zip (you need to extract it from the zip first).
Are you saying you tried this as well? Or did you not actually use ADB? If you are trying to accomplish this without ADB, you might want to take a look at this thread for instructions: http://forum.xda-developers.com/showthread.php?t=903152. And again, you will need to use the contents of the zip file, not the zip itself.
Click to expand...
Click to collapse
thanks for your reply, i checked the thread and more questions!
actually i am confused, i do the steps without getting the point of it, i installed astro, visionary 14, terminal emulator on phone, and adb on mac.
i dont know what adb is for, and i kind of understand that its for copying files from sd to phone internal memory? is that right? or does it have other functions,
its also not easy to understand astro, can it copy files from sd to internal memory?
do i have to drag adb to terminal every time for adb to run?
shall i use gfree or gfree_2 on my sd?
does terminal with su be enough or i have to use adb?or copying gfree to sd would be enough via usb mounting? where is data\local?
after my current understanding, i have decided to not use adb, and i have reached this step,after writing this script in the terminal,
got superuser for terminal emulator (ON PHONE)
su
cd /sdcard
chmod 777 the GFREE
./gfree
permission denied!
please let me know if i have misunderstood anything or if i am on the wrong track to s off.
i apologize for the long questions,
thanks again
Microzift said:
i dont know what adb is for, and i kind of understand that its for copying files from sd to phone internal memory? is that right? or does it have other functions,
Click to expand...
Click to collapse
ADB stands for Android Debug Bridge. It allows you to do a number of functions to your phone from your computer. The most common commands are push and pull (copies files on your computer to/from your phone) and shell (starts a shell terminal on your phone---basically the exact same as running the Terminal app on your phone, only you can type all of your commands on your computer instead). It also allows you to do things like install APKs stored on your computer directly to your phone and viewing log files.
Microzift said:
its also not easy to understand astro, can it copy files from sd to internal memory?
Click to expand...
Click to collapse
Astro is simply a file manager for your phone. It allows you to do basic file management (copy, move, delete, create new directories, etc.). Some directories are read-only by default however (rooting the phone will allow you to, among other things, mount these directories as read-write---once rooted, Root Explorer is a popular file manager like Astro that will allow you to manipulate these directories).
Microzift said:
do i have to drag adb to terminal every time for adb to run?
Click to expand...
Click to collapse
No, this is not ADB should be used (it is a command line tool). Check out the various guides on setting up/using ADB.
Microzift said:
shall i use gfree or gfree_2 on my sd?
does terminal with su be enough or i have to use adb?or copying gfree to sd would be enough via usb mounting? where is data\local?
after my current understanding, i have decided to not use adb, and i have reached this step,after writing this script in the terminal,
got superuser for terminal emulator (ON PHONE)
su
cd /sdcard
chmod 777 the GFREE
./gfree
permission denied!
Click to expand...
Click to collapse
See my next post for instructions on rooting without using ADB.
Permanent Root without using ADB
Extract the contents of gfree_temp-root.zip to your SD card (located on the Wiki). Also extract the gfree file from gfree_02.zip to your SD card. Note, you need to extract these files, not simply copy the entire zip to your SD card. Also, if you copied these files to your SD card by mounting your phone over USB, be sure to unmount it again prior to starting the remaining steps (i.e., turn off USB storage). Your SD card should now contain the following files: busybox, gfree, rage, root, su, and Superuser.apk.
Start Terminal on your phone (download from Market if you don't already have one) and type the following commands exactly as shown.
Code:
cp /sdcard/rage /data/local/tmp
cp /sdcard/busybox /data/local/tmp
cp /sdcard/root /data/local/tmp
chmod 755 /data/local/tmp/*
Then run the following command if you need temp root (so not needed if already temp rooted with Visionary). It is recommended that you uninstall or disable Visionary though and use this method however (some people have had problems when using Visionary). If you want to use Visionary for your temp root, skip this step and just right to the permanent root commands further below.
Code:
/data/local/tmp/rage
You should see a message similar to "Forked #### childs." Hit Menu and select Reset Term (the app will close). Launch Terminal again (it may force close). Launch it one more time (you now have temp root).
Now to achieve permanent root, run the following commands:
Code:
cp /sdcard/gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
Make sure there are no errors from the gfree output.
Lastly, run the following commands (the root script will install Busybox and set up the su apps for you):
Code:
/data/local/tmp/root
sync
If you have no errors, reboot your phone. You should now have permanent root.
ianmcquinn said:
Extract the contents of gfree_temp-root.zip to your SD card (located on the Wiki). Also extract the gfree file from gfree_02.zip to your SD card. Note, you need to extract these files, not simply copy the entire zip to your SD card. Also, if you copied these files to your SD card by mounting your phone over USB, be sure to unmount it again prior to starting the remaining steps (i.e., turn off USB storage). Your SD card should now contain the following files: busybox, gfree, rage, root, su, and Superuser.apk.
Start Terminal on your phone (download from Market if you don't already have one) and type the following commands exactly as shown.
Code:
cp /sdcard/rage /data/local/tmp
cp /sdcard/busybox /data/local/tmp
cp /sdcard/root /data/local/tmp
chmod 755 /data/local/tmp/*
Then run the following command if you need temp root (so not needed if already temp rooted with Visionary). It is recommended that you uninstall or disable Visionary though and use this method however (some people have had problems when using Visionary). If you want to use Visionary for your temp root, skip this step and just right to the permanent root commands further below.
Code:
/data/local/tmp/rage
You should see a message similar to "Forked #### childs." Hit Menu and select Reset Term (the app will close). Launch Terminal again (it may force close). Launch it one more time (you now have temp root).
Now to achieve permanent root, run the following commands:
Code:
cp /sdcard/gfree /data/local
chmod 777 /data/local/gfree
/data/local/gfree -f
sync
Make sure there are no errors from the gfree output.
Lastly, run the following commands (the root script will install Busybox and set up the su apps for you):
Code:
/data/local/tmp/root
sync
If you have no errors, reboot your phone. You should now have permanent root.
Click to expand...
Click to collapse
thanks, i could not find busybox, gfree, rage, root, su, and Superuser.apk on my sd after copying and extracting the zip files, the folders i unzipped did not also have the above files (gfree_temp-root.zip & gfree_02.zip from wiki, i do not have the above busybox etc files) i also kept them in separate folders on sd card; gfree and gfree_verify_v01
i think i have permanent root via visionary, i receive a # after typing su in terminal on phone. so i dont need rage i guess.
and after trying perm root as explained
cp /sdcard/gfree /data/local
i receive
cp: omitting directory '/sdcard/gfree'
where did i go wrong again!
Microzift said:
i think i have permanent root via visionary, i receive a # after typing su in terminal on phone. so i dont need rage i guess.
and after trying perm root as explained
cp /sdcard/gfree /data/local
i receive
cp: omitting directory '/sdcard/gfree'
where did i go wrong again!
Click to expand...
Click to collapse
If "su" is giving you a # prompt after a reboot then you have permanent root, yes.
Possibly a silly question, but you do have an SD card in the phone, right ? And it's mounted on the phone, not on the PC when you're trying these commands ?
steviewevie said:
If "su" is giving you a # prompt after a reboot then you have permanent root, yes.
Possibly a silly question, but you do have an SD card in the phone, right ? And it's mounted on the phone, not on the PC when you're trying these commands ?
Click to expand...
Click to collapse
thanks for asking, and thanks for clarifying the perm root.
regarding the sd, yes i am ok with mounting and charging mode, and i make sure that the phone is always in charge mode when using adb or terminal on the phone automatically when using usb. and only convert to pc mounting mode when i need to copy a file (like gfree or gfree veryfy) to phone sd card.
although i still keep the usb connected to mac in charge mode when i try terminal on phone (and adb is running). i disconnected to try and received the same error.
Microzift said:
thanks for asking, and thanks for clarifying the perm root.
regarding the sd, yes i am ok with mounting and charging mode, and i make sure that the phone is always in charge mode when using adb or terminal on the phone automatically when using usb. and only convert to pc mounting mode when i need to copy a file (like gfree or gfree veryfy) to phone sd card.
although i still keep the usb connected to mac in charge mode when i try terminal on phone (and adb is running). i disconnected to try and received the same error.
Click to expand...
Click to collapse
When you are getting that error with the "cp", try "ls /sdcard" and see if you get a big list of files, which should include whatever you tried to "adb push" there (e.g. gfree).
You don't have to use adb to copy adb to the phone, that's just one way of getting it there. You could mount the SD card from your phone onto your PC and copy it there that way. You just need to get the gfree binary onto your phone somehow, then copy it to /data/local
I just thought - you are running that "cp" command on the phone in Terminal Emulator, right ? Not on your Mac ?
steviewevie said:
When you are getting that error with the "cp", try "ls /sdcard" and see if you get a big list of files, which should include whatever you tried to "adb push" there (e.g. gfree).
You don't have to use adb to copy adb to the phone, that's just one way of getting it there. You could mount the SD card from your phone onto your PC and copy it there that way. You just need to get the gfree binary onto your phone somehow, then copy it to /data/local
I just thought - you are running that "cp" command on the phone in Terminal Emulator, right ? Not on your Mac ?
Click to expand...
Click to collapse
great now i get why i need to mount and copy gfree to phone sd, so that i can copy from sd to internal phone memory using terminal (on phone) or adb on mac.
yes i am running cp on terminal emulator on phone.
after ls /sdcard i receive
/sdcard
#
Microzift said:
thanks, i could not find busybox, gfree, rage, root, su, and Superuser.apk on my sd after copying and extracting the zip files, the folders i unzipped did not also have the above files (gfree_temp-root.zip & gfree_02.zip from wiki, i do not have the above busybox etc files) i also kept them in separate folders on sd card; gfree and gfree_verify_v01
Click to expand...
Click to collapse
Do not keep them in separate folders on the SD card. The files need to be on the root of the SD card in order for the commands I gave you to work.
Microzift said:
great now i get why i need to mount and copy gfree to phone sd, so that i can copy from sd to internal phone memory using terminal (on phone) or adb on mac.
yes i am running cp on terminal emulator on phone.
after ls /sdcard i receive
/sdcard
#
Click to expand...
Click to collapse
That is showing no files in your SD card folder. It sounds like it is actually mounted on your PC when you are running that, rather than being mounted on the phone itself.
steviewevie said:
That is showing no files in your SD card folder. It sounds like it is actually mounted on your PC when you are running that, rather than being mounted on the phone itself.
Click to expand...
Click to collapse
i have disconnected the usb from my pc, and still get the same message.
this is my understanding; mount sd on pc; means i can access the sd as a hard disk via the phones usb cable on my mac desktop.
unmounting; means i gain access of the sd on my phone only?
i found an option on phone, unmount sd card, should i do this every time i use terminal? i think this is for to unplug the sd card from the phone.
how can i get the sd mounted on my phone? i can see the same files via astro on my phone.
i still receive /sdcard
thanks guys, i just rebooted
my desire z is S OFF now.
and installed the recovery
thanks for all of your efforts
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
hookinhorns81 said:
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
Click to expand...
Click to collapse
I'm not sure if you had a typo in your original post or if that is how you actually entered the commands on your computer when you tried this, but based on the "paths" you entered, the commands should be:
CD\
CD\androidsdk\tools
adb devices
As for the themes, fonts, etc., there is an app in the market called MetaMorph that will do that for you. You just need to have .zips for it to apply.
There is also a tutorial for MetaMorph "somewhere" in the "Themes" section on XDA. I couldn't find a link to post for you, but I know it's there!
As far as getting in adb if you have windows XP you can go to the tools folder and hold shift and right click it. In the.menu it will say start command prompt here. Click it. Now you are on your tools folder where adb is. Then you can use adb and get into the shell.
Sent From My Evo Killer!
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]