I found a thread over in the I9000 section that may explain our problems with the Market on JH2.
http://forum.xda-developers.com/showthread.php?t=757461
This would seem to suggest that if you are running an unreleased firmware you need to replace the build.prop file from the released version in order to fix the market.
I have not tried this yet, I need to find the build.prop file from the original firmware first.
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Explorer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
I found this JF6 build.prop file in the stock system dump here. Let's see how this works:
http://forum.xda-developers.com/showthread.php?t=730226
Uploaded the stock build.prop to /system. It seems to make no difference in terms of availibility of the missing apps (only tried Fandango, but still missing). Grrrrr...need solution.
This did work for me. Thanks for the JF6 build.prop file.
This requires a rooted phone. You can brick your phone messing around with root. Not my fault...
I shut down the Market app, cleared its cache in Settings/Applications/Market (Filter select All Files to show Market app).
I added the JF6 build.prop to /system, replacing the JH2 version. I use root explorer to move the file on and off the SD internal.
Changed the permissions back to rw-r-r, using root explorer permissions. When the file is transferred back to the phone from the SD, the permissions will be rw-rwx-rx. Changed ownership back to root.root on the phone using terminal emulator:
$ su
# chown root.root /system/build.prop
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
rajendra82 said:
Trying to what you posted, but I don't see market listed under Settings/Applications or Settings/Applications/Manage Applications. How do I get to it, to clear cache?
Click to expand...
Click to collapse
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
dontshakepandas said:
Once you get to manage applications you need to change the filter to show all apps. Press the menu button > filter > all.
Click to expand...
Click to collapse
Working now. This is great. Now with the last issue resloved, I can keep the new firmware around. This needs a sticky, with all these weekly firmware releases from samsung-firmwares showing up.
daverup said:
This did work for me. Thanks for the JF6 build.prop file.
I shut down the Market app, cleared its cache in Settings/Applications/Market.
I added the JF6 build.prop to /system, replacing the JH2 version.
Changed the permissions back to rw-r-r, and changed ownership back to root.root
Rebooted the phone, uninstalled and re-installed an app.
Searched for previously missing app and found it.
Click to expand...
Click to collapse
Can you post the commands used to do this for users who aren't as knowledgeable.
yes. walkthrough please?
would love to get this working, I don't want to have to flash back to original.
kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
Edited post with details
kyphur said:
Can you post the commands used to do this for users who aren't as knowledgeable.
Click to expand...
Click to collapse
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell. If you get an error about unknown user/group, try chown 0.0 instead of root.root.
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app (if running).
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
daverup said:
One more thing,
The trick is working to fool the Market into believing that a JH2 phone is actually still on JF6.
This will probably also fool any program designed to upgrade the phone after checking the firmware version.
It would probably be a good idea to reflash via odin back to JF6 before doing any "released' upgrades via OTA or Kies.
Click to expand...
Click to collapse
Either that, or get a full flash of the newly released Froyo firmware with GPS Fix in September (hoping and praying), and flash it forward to the new stock version. Of course, not all parts of the system are fooled. Checking Settings -> About Phone, still shows the correct JH2 information.
Nice. Seems to have worked. Funny, it didn't work until after i installed/ uninstalled a couple items.
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
staySICK said:
thanks!
For some reason I can't get any of this to stick. I'll rename the /system/build.prop to build.prop.bak with root explorer, but as soon as I leave the folder and come back to it the rename is undone.
debugging mode is on and root explorer says its mounted as r/w. tried changing permissions to rw-rwx-rx like you stated in your first intructional post, permissions do not change.
using adb shell only gives me the error that build.prop is read only.
Click to expand...
Click to collapse
I am guessing that your root privilages are not working. Does you phone give you a popup when you do su in ADB shell. If so, tell the phone to allow su privlages to ADB in that popup. If you do, ADB should not complain. If that doesn't work, you have to redo your rooting procedure, as something might be messed up there.
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
staySICK said:
adb shell su does prompt the superuser request on my phone, which I've acknowledged.
Rooted using SuperRooter by designgears method.
hm... just tried a simple adb shell command (reboot), gave me an error too.
Sounds like a problem with my root access then? maybe I should unroot and switch to the previous version of superuser.
Click to expand...
Click to collapse
Probably best to ask about this issue in that thread, as more knowledgeable folks might know how to overcome this.
rajendra82 said:
You need to be rooted and have busybox for this:
1. Extract the build.prop from the 7z file.
2. Connect the phone via USB, select mass storage mode if prompted, and copy the build.prop file to the sdcard (I am going to have to assume root of the internal sdcard for the sake of the commands below). Then disconnect USB storage so that your phone can see the file you just copied over.
3. Open a Terminal Emulator session or have the phone in debug mode, and start ADB shell, and do the following:
$ su
# mv /system/build.prop /system/build.prop.bak<- Or use rename in Root Explorer
# cp /sdcard/build.prop /system<- Or use copy in Root Explorer
# chmod 644 /system/build.prop<- Or fix permissions to rw-r--r-- in Root Explorer
# chown root.root /system/build.prop<- You have to do this in the Terminal or an ADB Shell
# exit
$
Now close the Terminal Emulator session. Double check ownership to root.root, and permissions to rw-r--r-- in Root Exploer or using ls -l /system/build.prop first if you are paranoid. If you are really anal, open the build.prop file you just copied over in a text editor, and make sure it says I897UCJF6 instead of I897UCJH2.
4. Start a task manager and kill the market app.
5. Press the menu key while on home screen and go to Settings -> Applications -> Manage Applications. Hit the menu key again, and change filter to All Applications. Then select Market, and clear the cache. I also cleared the cache of AppBrain while here, not sure if it made any difference, but won't hurt to do it.
6. Reboot the phone and use the Market for a little while. Install and uninstall a couple of apps. Once the cache rebuilds, the formerly missing apps Market pages will be visible, and available for downloads and show updates. When I first went in the Market, the apps were not there, but it took a couple times hitting the google server to get it all sorted out.
Click to expand...
Click to collapse
This worked for me, one thing to note, when I ran the last command from Root Explorer "# chown root.root /system/build.prop" Root Explorer responded with
chown: unknown user/group root:root
But after restarting and installing/uninstalling a few apps Fandango shows up where it did not before.
Thanks.
Related
This was created when we didn't have S-OFF yet.
If you have S-OFF or /system overlay script you won't need to go through all the steps simply download adfree android.
I know most of you will be able to do this. But I believe that it might not be as easy for the beginners. So here is a little walk through.
!NEEDs ROOT!
1. Download Adfree Android
2. Wait for it to determine local hosts then click on download and install hosts.
Now it will try to replace /system/etc/hosts but fail (it should reboot the phone but it didn't reboot mine)
4. go to adb and reboot your phone into recovery (with power on+volume down OR the command: "adb reboot recovery")
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
6. mount your system and sdcard you might be able to just use mount and mount everything but I've mounted them serperatly.
Here's how: "adb shell mount /system" next "adb shell mount /sdcard"
7. Now we're going to put it in the etc directory where it should be: "adb shell cp /sdcard/hosts /system/etc"
8. reboot the phone ("adb reboot")
That should remove most of the adds.
I know it's explained on a really low level of knowledge but I wanted to make it accessible for all of you.
Only the needed codes:
Code:
1. adb reboot recovery
2. start recovery-windows
3. adb shell mount /system
4. adb shell mount /sdcard
5. adb shell cp /sdcard/hosts /system/etc
6. adb reboot
has it the option to only block browser ads? when I tried it time ago it couldn't. I don't like to block the app ads
No it removes the adds everywhere. It simply blocks the links to adds. it doesn't actually remove them. they are still being called but they just don't show up.
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
PirateNL said:
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
Click to expand...
Click to collapse
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
A good guide, if a little misplaced, but another option is the /system overlay.
JonasDroid said:
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
Click to expand...
Click to collapse
Yes and yes
where is the most recent hosts file? I'm using a vibrant and it says it worked, but of course, it doesn't. And it doesn't copy the hosts file to my sdcard either ? odd
Hello ,
Finally I got Adfree working
Ok it's not perfect because app continue to reboot the phone after updating the hosts file ,
and we need to copy it manually in recovery mode but it better than nothing
Thank you very much JonasDroid for this little How to .
PS:
For me step 5
JonasDroid said:
Code:
5. adb cp /sdcard/hosts /system/etc
Click to expand...
Click to collapse
was
Code:
adb shell cp /sdcard/hosts /system/etc
Bye.
Yeah indeed its adb shell cp thx for letting me know
Sent from my Legend using XDA App
Can you link me the apk of adfree? I can't download the app from my phone
BTW it's 'ADs" single d
short for advertisment (notice the single d?)
Fixed that English is not my main language
Sent from my Legend using XDA App
JonasDroid said:
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
Click to expand...
Click to collapse
Can't get "start recovery-windows" to work. What is the "right directory"?
Things seems to have worked for me without that portion. Many thanks, I will now change my review in the market for that app from one star to three stars. If they include a note describing this problem upfront I may bump it up further.
It could simply be called start recovery (depending on where you got your rooting tools)(if you've got the from The Unlockr you'll need the -windows)
If you have S-OFF or if you use an /system overlay script these steps aren't needed. (It was created when we didn't have S-OFF for our legends yet.)
Anyone having problems with adfree scripts on Legend since Froyo update? Neve had a problem witha rooted 2.1, but have lots of problems since rooted Froyo 2.2
It seems HTC may have some service which is checking for modifications to symlinks etc.
When I run adfree in my S-off CM7, i get an java.io.EOFException.
Someone else having this?
I had some problems at first, but reinstalling adfree android from market seemed to help. No problem now with CM7 (01/03 from ali ba) and s-off.
adfree no block ads!
Hi,
i install the adfree on my legend with 2.2 with sense.
i did download the host from the app all work ok got a message say it was success install and need to restart the phone.
i did it but still get all the ad like before on all apps.
pls help!
Have you followed the steps? (explained in first post)
Note that you should have a rooted legend (if you don't know what that is then you don't have one)
I have been experimenting with my new droid/milestone the past couple of days, odd problems which I am past now but still curious about.
Firstly after flashing the 2.1 sbf with rsd it will autoboot and screen slider will be there, then when I reboot, screen slider will be missing. This only happend when I flashed an sbf from the sbf site(2.1 uk version, not service), doing a factory reset didn't have any problem -could reboot as many times and slider would be there.... then suddenly after factory boot it would dissapear after first boot. Anyway solved this problem by installing screen mode widget after first boot after flash, solved problem, but still weird. Fixed this now but still curious about it.
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Also any thoughts on why nandroid backup is missing from my recovery menu even though my droid is rooted. I thought it was meant to appear.
I am still learning and researching, and appreciate any links or tips.
droidtech1 said:
Next, nandroid backup is missing from recovery menu, I have rooted and can execute root commands after typing "su" via Android Terminal emulator, so pretty sure is rooted. So why no nandroid? I thought I could do nandroid backup after rooting.
Click to expand...
Click to collapse
This is odd. Which OpenRecovery did you install? Androidiani? GOT? Or the "original" OpenRecovery? Are you aware, that you come into OpenRecovery by starting Recovery Mode and apply update.zip?
droidtech1 said:
Next busybox won't install, tried the app, did the "searching system" for over an hour(not exagerrating), eventually gave up and uninstalled.
Trying to do a "manual busybox install" now, using this guide:
Busybox How-to? - Android Forums
Click to expand...
Click to collapse
Using the app from the market worked like a charm for me. No idea, what might have gone wrong for you...
droidtech1 said:
Can't execute commands via usb/adb in recovery mode as the other guy suggested so been trying these commands both with terminal emulator on phone, and usb-debugging mode with windows shell. Using these I can go "su" and type "ls" to see files on my droid phone....but when I try to "mount /system" or /sdcard from windows I just get a print about mount options, when I try to "cat /sdcard/busybox > /system/xbin/busybox" I get a "file is read only" error.
Click to expand...
Click to collapse
For remounting, try "mount -o rw,remount /dev/block/mtdblock6 /system" and for undoing this, use "ro" instead of "rw".
droidtech1 said:
I would like advice on how to install busybox, I would like to do it manually(because the app seems to not work for me, remember I waited over an hour while it "searched") and I want to learn to manually do stuff anyway. I tried to chmod /system/xbin too, but that didn't seem to change it from read only.
Click to expand...
Click to collapse
You should download busybox and put the "busybox"-file in the directory /sdcard. After that do:
Code:
# su
# mount -o rw,remount /dev/block/mtdblock6 /system
# cp /sdcard/busybox /system/xbin
# cd /system/xbin
# chmod 755 busybox
# ./busybox --install
# mount -o ro,remount /dev/block/mtdblock6 /system
One thought at the end: How did you root?
I rooted by flashing "vunerable recovery" using RSD lite, copied milestone-root.zip to sd card, renamed it update.zip, rebooted into recovery mode, flashed update.zip from there.
I didn't realise I had to install something like open recovery, think because I remember not having to do that on my pulse? Anyway will try and install one of those now.
Thanks those commands at the end helped, actually managed to copy busybox to /system/xbin, however the 2nd last one "./busybox --install" gave me a load of errors -all being no such file or directory, for example "/usr/bin/wc: no such file"
about 30 of those path errors. Maybe the command path "./busybox" needs to be something else?
ah, okay. sorry, I thought you already installed an openrecovery. for many cool features you will need it (e.g. nandroid, for overclocking it's not a must but a nice-to-have). please don't use GOT, it's rather old already. androidiani is okay, I think.
I think your previous attempts to install busybox via the app etc. mixed up some internal links in the device. please reboot and try again (the above steps except the "cp ..."). seems like the app tried to install busybox to /usr/bin but failed... I hope this failed attempt will be fixed by a simple reboot. otherwise it would be great to have the output of:
Code:
# su
# ls /usr/bin
No I re-flashed my main sbf and also did a factory reset to do a clean start, only thing since that full wipe I have done is rooting in the method I described, installed the screenmode widget, textedit, and android terminal emulator.
I have no such file /usr, are you sure I should have this in droid/milestone?
Here is my full output of my root system using ls:
tmp
pds
cdrom
sqlite_stmt_journals
config
cache
sdcard
d
etc
system
sys
sbin
proc
init_prep_keypad.sh
init.rc
init.mapphone_umts.rc
init.mapphone_cdma.rc
init.goldfish.rc
init
default.prop
data
root
dev
perhaps "/usr" is a sub inside one of the above folders? I tried using "find" to find it but that command dosn't seem to work since it won't even find the ones I can see with ls
I found it, /usr is inside /system... so if busybox was moved to /system/xbin, I'm guessing the ./ means install it to the parent directory which was /system which /usr is also in.
The errors I got said no such file "/usr" so It seems like it is trying to install to the wrong directory.... perhaps the command should be "busybox --install" or "/busybox --install" I don't want to experiment and mess things up before your opinion on this.
*edit almost forgot, output of /system/usr is
keychars
bin
srec
keylayout
share
output of /system/usr/bin is
panic_daemon
gki_pd_notifier
nvm_daemon
clean_dex.sh
brcm_guci_drv
bplogd_daemon
This is really strange. Maybe your busybox-file is corrupt.
Where did you download the busybox-file?
Which sbf did you flash?
So for explanation-purposes: When you put an executable or script file in any directory, you can execute it by first making it executable ("chmod 755 /system/xbin/busybox"), changing to that directory ("cd /system/xbin") and then executing it by adding "./" in front of it. The dot slash always stands for the _current_ directory. The _parent_directory has two dots "../".
If you want, you may try:
# /system/xbin/busybox --install
instead of
# ./busybox --install
Or maybe try this one:
# /system/xbin/busybox --install -s /system/xbin
Last time, I installed busybox into the directory /data/busybox, which worked brilliantly, but this path turned out to be unpractical. So I wanted to reinstall it in a different directory. I removed everything from /data/busybox including the directory itself and tried to start the whole procedure with /system/xbin. But that time it protested, that there were no files in "/data/busybox/...". Conclusion: The last busybox-install affected the second one. When I remember correctly I rebooted after that and used the app from the market *g*
My main sbf I flashed was android 2.1(uk version).
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
I also managed to install open recovery and do a nandroid backup succesfully
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Thanks for all your help so far.
droidtech1 said:
My main sbf I flashed was android 2.1(uk version).
Click to expand...
Click to collapse
Don't want to try one of the 2.2?
droidtech1 said:
I downloaded busybox 1.17.2(won't let me post url here), was from droidforums dot net.
I don't remember if I tried all of his commands, but the last one on that forum seems to have worked.. I think......... it was:
"busybox --install /system/xbin/"
After remounting with your commands and typing the above command, I didn't get any errors, I synced and rebooted and now when I "ls /system/xbin" it shows a bunch of files/names which look like busybox commands. When I type "busybox" it outputs a bunch of commands too... so I am guessing this means it has succesfully installed? I can't say I tried these before attempting install so I have no comparison but I assume I would have a different output if busybox wasn't installed.
Click to expand...
Click to collapse
Yes, this sounds very much like installation was successful.
droidtech1 said:
So assuming it worked, why would
"busybox --install /system/xbin/" work, and
"/system/xbin/busybox --install" not?
Click to expand...
Click to collapse
typing "busybox" without the path in front of it worked, because busybox is in the directory /system/xbin, which is already in your $PATH-variable (try "echo $PATH"). So the command interpreter (shell) will automatically look up "busybox" in /system/xbin.
I had a look at the busybox syntax and it's actually
Code:
busybox --install [-s] [INSTALLDIR]
So you have to put the directory you want to install in at the end. That's what your last command makes use of
droidtech1 said:
I have another short question, not specific to android but happens in all terminals I use, windows and linux alike. Sometimes I cannot execute commands anymore and it just becomes text in the terminal(just re-echo'ing my text output, without executing any functions)... can't remember specifically when it happened on my windows or linux pc shells, but on my android it happens whenever I have to give "SU" permission to the terminal, I have to quickly close the terminal and reload it again to get su access. I'm sure there is a name for this "state" where you are locked out of using commands in the shell and just typing text but I can't find a way to get out of it(without closing and re-opening terminal), there must be some key combination to be able to execute commands again in the current terminal session. If you have any idea what I am talking about?
Click to expand...
Click to collapse
Sounds like this is just the state, when shell is busy, i.e. when the last process you started is still running and no prompt ($ or #) is displayed. You may kill the last process in linux using CTRL+C, which will hopefully bring back the shell prompt. No idea which shortcut replaces this on the milestone/droid. I never use any android terminals, but only the ADB-Shell: http://developer.android.com/guide/developing/tools/adb.html
I'm learning to build apps for android so I thought having 2.1 on my droid would be better for testing (instead of 2.2). I also have a Nexus-S with 2.3 and a tmobile-pulse with 1.5. So I want to keep the most native version on each phone since most consumers won't install custom roms, although some will get updates anyway.
I use my droid a lot when I am out and use the terminal a lot so having busybox too has given me more to play around with. I actually find my droid much better working on than the nexus s, love the keyboard and dpad.
I rooted my DS7 and changed the "phone.apk" name, and I couldn't get past "Force Close" message, so I reset (Vol+ + Power?).
I got the option of "0. Boot", "1. Wipe"..., and selected 1.
Rebooted and was stuck at "Touch Android To Begin" - Android turns white, but does not move forward.
I reset and selected a different option of complete wipe of internal and personal data.
Rebooted and am still stuck at "Touch Android To Begin".
Any suggestions?
I have 2 SD7's, so do I need to back up a ROM off the good one and reflash the stuck one? If so, how would I do that?
Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).
Z4nd4r said:
Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).
Click to expand...
Click to collapse
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore/clear cache have changed all of that...by replacing all files/kernal/rom to factory?
S4F4M said:
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore have changed all of that...by replacing all files/kernal/rom to factory?
Click to expand...
Click to collapse
Wipe/restore, if I understand it correctly, only wipes out cache and data; basically, all of your personal information and files for apps and such (not your SD card). This leaves the kernel as it was.
Do you have CWR on there? If so, simply install a new ROM. If not, you can flash it on there via ADB, I think (check the CWR thread).
Your other option is to change the file name via ADB, or push a new one to it. I've uploaded the stock Phone.apk here:
http://www.megaupload.com/?d=EEBPHB4H
You can push it by doing
Code:
adb push Phone.apk /system/app
I think there's an adb command to simply rename, but I don't recall what it is. Once you do this, you ought to be good to go. Get signed in, then change/move both the apps and restart. It might be annoying with the force closes; not sure if you'll have to use the pinhole reset.
Good luck!
Thanks, Z4nd4r! I'll give it a whirl.
I just moved/deleted the files to test it out (and run some battery tests). I had the force close issue to the point that I couldn't do anything, so I used the pinhole reset. Booted up fine and no cell signal, just as it ought to.
What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.
S4F4M said:
What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.
Click to expand...
Click to collapse
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!
Z4nd4r said:
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!
Click to expand...
Click to collapse
Oh, I did. What was left out of the procedure I found was the mention of continuous FORCE CLOSE and the use of the pin reset.
I will write up detailed instructions for a new thread in case anyone else wanted to know.
I know this is a really old thread, but I am stuck on this as well in the same situation that the OP had. However, SuperOneClick 2.2 and 1.55 both seem unable to root the streak so I can use the adb server to push the proper apk back! Anyone have any advice? I need to rename or push both TelephonyProvider.apk *and* Phone.apk. I have tried using adb and of course it errors since the device is unrooted.
turn device vertical.
start upper right touch
lower right touch
lower left touch
upper left touch
One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...
there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date
I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.
http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App
OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
dry3333 said:
Hi!
I have problem with my HTC One m7 (ViperOne 7.0.1).
While I changed something in /system/app folder (eg. deleted a "DriveActivator.apk" - successfully accomplished) and restart phone, I see again that deleted app!!!
Do you know why? I'm using RootExplorer, I have root and granted permissions to r/w.
It seems like system restores some kind of backup - I don't know why, and I don't know how to fix it (I mean do some permanent changes in /system/app).
Click to expand...
Click to collapse
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
ajbiz11 said:
It appears that the System isn't booted with RW capabilities
There's a nice long command that I'll give you later that will fix it
If you wanna get it sooner and aren't afraid of adb shell (make sure you have root access enabled for adb AND apps, not just apps) you can Google remount Linux system read/write and you should find it
You'll need to modify that command to reflect the One, but the name of the partition should be something like by-name-system or something
I'll get it later if you need it when I wake up
Click to expand...
Click to collapse
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
dry3333 said:
Thanks mate!
Stupid question - how I can check whether I have root access enabled for adb and apps? I have superuser app, and in settings I can see: "Superuser Access: Apps and ADB" - is this what you are wrote about?
Click to expand...
Click to collapse
That's exactly what I'm referring to (The settings thing)
Lemme go find that command for you
---------- Post added at 06:00 AM ---------- Previous post was at 05:56 AM ----------
Wish I knew this existed when I was working on the L port
There's an app to do exactly what you need without looking up partitions
https://play.google.com/store/apps/details?id=com.beansoft.mount_system
Although if you want to go through terminal, here's a tutorial
http://ckirbach.wordpress.com/2012/11/27/how-to-remount-system-as-read-write-in-android/
Basically, you use grep to find the name of the system partition, then run the mount command to remount the partition you found in that precious step
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
dry3333 said:
I have this app: Mount /system (rw / ro), also I have this option in superuser and it works fine - I mean that I can change /system/app or for eg. edit /etc/hosts (I get message that ES explorer granted superuser access), but after restart I see previous files (before changes)... I have no idea how make this work - maybe I need custom kernel or something? I want to make permanent changes in system files...
I have reinstalled system (clean option with wipe all data), but still no results...
Click to expand...
Click to collapse
The remount app should do exactly that
Try the command option and make your changes then reboot
ajbiz11 said:
The remount app should do exactly that
Try the command option and make your changes then reboot
Click to expand...
Click to collapse
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
dry3333 said:
I have tried - still no results. My system already has RW permissions. Problem is that after restart my files are "restored".
Analogously like in Cisco IOS - commit but without write memory.
Maybe I should go to recovery and do something (but I don't know what)?
Click to expand...
Click to collapse
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
ajbiz11 said:
Check the Viper forum and maybe post there
I only run CM-base so I'm not too experienced with Sense issues
Click to expand...
Click to collapse
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
You can remove it from the ViperROM zip and format ONLY system and reflash
That SHOULD work
That's like...the be all end all
dry3333 said:
Thanks - they said they don't know, but it affects S-ON users....
Can You tell me one thing - I execute this script:
echo off
adb reboot
cd /d %~dp0
echo .
echo Waiting for device...
adb wait-for-device
echo.
adb -d shell stop
adb -d shell su -c "mount -o remount rw /system"
adb -d shell rm /system/app/DriveActivator.apk
adb reboot
This should remove DriveActivator (while script is ongoing I see no errors), but after reboot DriveActivator.apk is still in /system/app...
Is there any other way to permanently remove/change files in /system/app?
Click to expand...
Click to collapse
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
nkk71 said:
Make life simple: erase the apk while in custom recovery, TWRP has a file manager, or you can use Aroma File Manager
even adb commands while booted in custom recovery are better than booted up ROM.
Click to expand...
Click to collapse
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
dry3333 said:
Thanks for advice. Is it possible via TWRP not only remove file, but also replace it? Where shoul I place new file for replace original one?
Click to expand...
Click to collapse
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
nkk71 said:
I would recommend using the Aroma File Manager instead of TWRP's, just place all the files you'll need on your internal storage (including Aroma File Manager), then reboot to select "Install" to run the Aroma File Manager and remove/replace whatever you need to.
You may need to also check if the permissions are right, I can't remember if Aroma File Manager has that built in.
remember that once you are in recovery to mount /system (in the Mount menu)
and you can even use adb shell, and adb push commands to replace the .apk.... i'm just guessing it's easier with a GUI interface.
Click to expand...
Click to collapse
The windows drivers don't work with recovery mode (usually)
ajbiz11 said:
The windows drivers don't work with recovery mode (usually)
Click to expand...
Click to collapse
they do for me, but sometimes (after flashing a new/different version) i have to manually select the drivers, check FAQ#2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
dry3333 said:
I would like to thank you for advice. I did this via TWRP (after I had mounted /system). It works fine for me
Click to expand...
Click to collapse
sure, no problem :good: :good:
if all is good now, can you also edit main thread title to include [SOLVED], thanks
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title