[Q] Moving new hosts into /system/etc - Desire Q&A, Help & Troubleshooting

This is a copy post from here when I realised it was in the wrong spot.
I have a rooted Desire using unrevoked and am trying to use AdFree on 2.2 but I am told that the hosts file I need to block ads cannot be written to /system while Android is running. I did some searching but, alas, no luck on an answer.
I do not know how to get to a command prompt to follow the instructions in this thread and have looked in the ClockworkMod Recovery mode for something similar.
Anyone have an idea?
edit:
I also got Root Explorer off the market (which cannot simply copy the hosts file into /system/etc/ as it does not have access whilst Android is running) and I think the command prompt I need is the pc cmd prompt when the device is plugged into USB, but I am unsure which drivers I need. The ones mention in Toastcfh's guide is for the EVO, not the Desire.
edit 2:
I got the Android SDK with adb and made progress, but still stumped.
I connect the Desire to the PC and with the Desire in recovery mode with ClockworkMod I run adb with:
Code:
adb shell
# mount /system
# exit
adb push hosts /system/etc
adb reboot
Following the example from here but it's a different device and dunno what to put for the first argument in '# mount /dev/block/mtdblock4 /system'. Any help at all would be much appreciated.

The symlink option in adfree should work for S-on devices.
If it doesn't try this:
Code:
adb remount
adb push hosts /system/etc
adb reboot
If that doesn't work flash this.

Related

help changing boot screen

Hey all, ive been trying to change my boot screen to the haters gonna hate one for a few days now but cant seem to get it to work at all, i have full root and tried to the fastboot method and recovery/adb method. no matter what it stays the same as the one i had originally, i never get errors when trying to push the files if someone can give me instructions for dummies haha or another method id really appreciate it sorry for being a noob at all this.
I had the same problem
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
oh yeah sorry i should have included that i am on evios 1.2 beta 2 rom
I'm not familiar on where to place boot on this rom. Try all three locations I suggested. System customize resource. System media. Data local. Tell me if it works out.
I had this animation on EViO. I just pushed it from my desktop to system/media. Worked fine for me.
how do you push it from the desktop? i tried all 3 methods posted above and none worked. i had the file in the android sdk tools folder though...also whenever i try to do adb remount i get "remount failed:invalid argument" and adb root gives me "error:closed" i tried killing adb and restarting but no luck
This might be an obvious question, but do you have USB debugging enabled on your phone? Under Setting>Applications>Development
You arent going to be able to push anything if you can't get ADB running first.
yeah debugging has been enabled the whole time
ok have you been in recovery mode?
try typing
adb shell
su (make sure #comes up.)
exit (retype until you get back to the tools directory)
then do the push commands to system media, system customize resource, and data local.
Just use this program. Its as easy as it gets.
http://forum.xda-developers.com/showthread.php?t=701295
dkdude36 said:
First of all, what rom are you using? Different rooms pull from different places. I might be able to help you out. If you are running cyan6, try this:
Adb reboot recovery
Adb remount (make sure it remounts. Maybe also do adb root to make sure.)
Adb push blahblah.zip /system/customize/resource/bootanimation.zip
Adb push blahblah.zip /system/media/bootanimation.zip
Adb push blahblah.zip /data/local/bootanimation.zip
If you want sound, push that to the same locations. Make sure there is only one of each file in each folder. Then, to check,
Adb reboot
Hope this helps
Click to expand...
Click to collapse
Putting sound in boot animation doesn't work with cm6. Just to clarify. No one has been able to get it to work unless you found something out to make it work please share as I have hates going to hate also and want to use haters everywhere mp3 and is perfect for it.
Sent from my PC36100 using XDA App
yeah i have also been in recovery mode every time i tried to run a command prompt for adb...i tried that when i hit adb shell i get # but when i type su after the # it says "/sbin/sh: su: not found"
mount: mounting /dev/block/mtdblock4 on /system failed: Device or resource busy
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
A duplicate file name exists, or the file
cannot be found.
thats what i get when in command prompt when i try to use the program you just posted above
Want a easier way? Use root explorer and copy and paste. Works for my every time. It's in the market. And root explore you can manually turn writeable on and off to move it into system. It's on the top right of screen in root explorer when you go into system folder.
Edit: the command you are tying to put in enables you to push and pull in the system folder. Root explore you can just click a button.
Sent from my PC36100 using XDA App
Good idea
Root explorer works most of the time. If you have the cash, go ahead. You should make site out posted though.
/sbin/sh: reboot: not found
been trying to use adb and i keep on getting that....any of you know a fix?

[Q] HTC Desire Z Rom Upgrade

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

[Q] How do you change system font without rooting?

Okay, so i have been at this for like an hour and its pissing me off, cuz i just keep going in circles....i was using this tutorial
http://www.tech-recipes.com/rx/10573/android-how-to-change-the-default-system-font-requires-root-or-adb/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+Tech-RecipesMain+(Tech-Recipes+Main) and when ever i typed adb remount it told me remount failed: Operation not permitted
I checked the post and he says the following
Manual Way Using ADB and Command Line
1. This way assumes you have the Android SDK installed and setup. You also need the USB Debugging drivers for your device installed. Also be sure to copy the TrueType font file into the same folder as the adb.exe and fastboot.exe programs (default is c:\android-sdk-windows\tools ). This should work on a non-rooted device since we are using the SDK and ADB Remount commands; however, I have not tested personally on a non-rooted phone.
He said should but he has not tested it. Considering you are trying to replace something in /system I doubt it will work without root.

can not mount system in read-write mode using adb without recovery mode

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]

[UNIVERSAL GUIDE] Root Any Android Device Manually !

THIS GUIDE NO LONGER WORKS BECAUSE ANDROID ISN'T WHAT IT USED TO BE BACK IN 2013-14.
PLEASE STOP WASTING TIME TO FOLLOW THIS OBSOLETE METHOD 1. PLEASE REFER ONLY TO METHOD 3​
The Ultimate Guide to Rooting any Android Device Manually !!!!​
Wanting to ROOT Your Phone but can't do Because Of No rooting Guides or want to learn to root any device ? Then , This Guide Is For YOU
OK So lets start....
**What You Need**
1.Your Unrooted Android Device.
2.ADB Drivers Installed On Your PC. If you Don't Have Download From Here :
Code:
adbdriver.com/‎
3. The Most Inportant Root Kit Made By Me (N'ayam Amarsh'e) - Download From The Attachment.
4.Strength And Courage 'Coz Rooting Voids Your Warranty... If You have a samsung device then Don't Worry Your warranty is gone forever... But if you own any other, maybe you can void it or maybe......
I've Written Android Device as ADV to make it more easy....
**Steps**
So you have the adb drivers installed let's go....
1. Open The root kit by Extracting The Rootkit with WinRAR....
2.Turn 'USB DEBUGGING' 'ON' in your ADV...
3. Connect your ADV to Your PC...
4.In the root kit Open Cmd.exe File ... [ IF YOU CAN'T OPEN CMD, GOTO C:/WINDOWS/SYSTEM32/ COPY CMD .EXE TO YOUR ROOTKIT FOLDER]
5. In CMD window Type the following command...
Code:
->adb devices *Your device will get listed in the window if it doesn't check your adb drivers or if you have followed the steps properly...
->adb push busybox /data/local/tmp
->adb push su /data/local/tmp
->adb push Superuser.apk /data/local/tmp
If you Succeed Move On ...
6.Then You need Root Shell Type :
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not in 'su' shell.
7.Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
->chmod 6755 /data/local/tmp/su
->chmod 755 /data/local/tmp/busybox
->chmod 644 /data/local/tmp/Superuser.apk
{Note}The names of the files are case sensitive!
8.Done ? Now You need to open a copy of linux which has nautilus... So enter your linux (I recommend using ubuntu 11.4) and type in the terminal (ctrl+alt+T)
Code:
->sudo nautilus
this will open nautilus with root privileges...
You can just boot it from USB so no hassle of installing it... http://www.cyberciti.biz/tips/download-ubuntu-linux-11-04-iso-cd-dvd-images-natty-narwhal.html
Having your ADV connected with USB to PC switch it off and put it in download/recovery mode...
superlouro said:
DEVICE OFFLINE?
! SOLUTION ! (click me)
Click to expand...
Click to collapse
9.In The Exploring Window navigate to
Code:
/data/local/tmp
and move/cut 'su' and 'busybox' to
Code:
/system/bin
...
10.From the tmp Folder you went earlier Move/cut 'Superuser.apk' to
Code:
/system/app
11.Now Reboot You ADV ... Congrats ! You're now ROOTED !
Many Users Are Having Problem with This Method, If you can't do the method 1. Try Method 2.
METHOD 2
PLEASE DON'T ASK ME ABOUT THIS METHOD, THIS IS JUST FOR A TRY, MY BROTHER FOUND THIS METHOD TO BE WORKING, I HAVEN'T TRIED IT YET!
This is linux based method, It's quite easy if you follow every step correctly...
You need to download psneuter, https://github.com/tmzt/g2root-kmod/tree/master/scotty2/psneuter
When you have it execute the following...
Code:
adb devices
Code:
adb push psneuter /data/local/tmp
This will copy the file to your device and now we'll execute it..
Code:
adb shell
cd /data/local/tmp
chmod 777 psneuter
./psneuter
Now You'll see
Code:
adb kill-server
adb devices
adb shell
now # will appear in place of $, or after typing $su.
Code:
# mount -o remount,rw -t rfs /dev/block/st19/system
# exit
$ adb push busybox /system/bin
$ adb push su /system/bin
$ adb install Superuser.apk
$ adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19/system
# exit
$ adb reboot
Now your device will reboot and you can see SuperUser App in your app drawer...
----------------------------------------------------------------------
METHOD 3
There is no chance of the phone not getting rooted with my method but If you don't want to do the above methods, Try these, I'm pretty sure they will root your device with ease...
1. Framroot App [Not On Google Play]-http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2.KingoRoot App - www.kingoapp.com
3.One Click Root Free/Pro (My Favorite app, roots many devices with No-Brick Guarantee) - www.oneclickroot.com
4.Root Master App - forum.xda-developers.com/showthread.php?t=2672150
5.z4root App - http://forum.xda-developers.com/showthread.php?t=833953
6.Easy rooting toolkit App-http://forum.xda-developers.com/showthread.php?t=1321582
7.Vroot Software - http://vrootdownload.info/ or http://www.mgyun.com/en/getvroot
8.SRSRoot Software - http://www.srsroot.com
9.Unlock Root Software - http://www.unlockroot.com/download.html
10.Universal Androot App - forum.xda-developers.com/attachment.php?attachmentid=391774
ONLY FOR MTK DEVICES- MTK DROID TOOLS- http://forum.gsmhosting.com/vbb/f60...3-2014-imei-repair-rooting-tool-more-1780568/
HOPE THESE WILL DO....
Press Thanks To appreciate me to Work On Other Guides And Roms....
Your Appreciation Is Needed...
And This GUIDE IS Originally By N'ayam Amarsh'e
I have any error. Device is offline.
---------- Post added at 09:13 AM ---------- Previous post was at 09:02 AM ----------
uukasz92 said:
I have any error. Device is offline.
Click to expand...
Click to collapse
Problem solved i download another adb drivers and work fine
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
uukasz92 said:
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
Click to expand...
Click to collapse
that means you have not properly pushed the files into the directory.... Try installing adb drivers again and do the same steps...Good luck
When you open cmd just type ' adb devices' if your device gets listed then you can start if it doesn't check your drivers...
After uinstall all adb drivers and phone drivers comand prompt shows me a device code and status ofline. At the begining i install atached to therad package of adb drivers. But lately some where in Internet I find some update package of adb drivers. And there was the same sort of files like in your package. I put them there and replace and after that adb shows the device is working and status is online but your guide still does not work. Question is where is real problem ? I checked and Debug Mod is on, drivers are installed.
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
N'ayam Amarsh'e said:
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
Sent from my Mi-492 using xda app-developers app
Click to expand...
Click to collapse
I used the same files in android commander because program can't finde my device to.
Which phone you have.... Try to download its original drivers this might help...
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
uukasz92 said:
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
Click to expand...
Click to collapse
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
N'ayam Amarsh'e said:
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
Click to expand...
Click to collapse
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Droid Explorer cant change folders premission too. Command prompt says : Read-only drirectory. I don't know what to do now.
uukasz92 said:
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Click to expand...
Click to collapse
thanks.... Guide is updated now
Good 1 helped alot
harmeet singh said:
Good 1 helped alot
Click to expand...
Click to collapse
I am happy that I helped....
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
thankyou for information i think is hard for me
Very nice, ty
Humbel said:
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
Click to expand...
Click to collapse
For Your First Answer You Need not to worry /tmp and /tmp/ are the same...
2.Have you tried typing 'adb shell' then ' su ' if yes there's your solution.... If not then you have problem with su binary or busybox....
3.You have an Ubuntu 11.4 .iso file so burn it to a blank disk and boot your live disk .... It should be all right then...
4.Answer in 3....
5.Answer in 3....
6.Press Thanks if I helped...
bro im confused wt to do exactly in that sudo ... step pls give a brief explaination

Categories

Resources