Related
I looked around the net for a feasable solution but nobody seemed to give me a practical solution. So I decided to experiment and came up with an unbelivable solution that takes literally 20-30 seconds per app and is FULLY automated.
My problem was as follows. I like to install new ROMs by wiping, flashing and reinstalling my apps. The problem with that is when you have 130 apps and Astro file manager seems to install 3-5 then quits back to the packages screen, it becomes extremely friken agrivating and simply hell-as annoying!
So I needed a way to install all my previously backed up apps (which Astro does a BEAUTIFUL job with) from my SD card to my phone all in one go, without prompts and without any input.
To do this its simple, just write your own batch script and run adb install.
You will need:
1. Android SDK (your version, ie. 2.2, 2.1, 1.6 ect.)
Code:
youtube.com/watch?v=A1SOSXwkc_8
2. USB Cable to PC
3. Enable "USB Debugging" on phone
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Now, I assume you already have the APK bunch on your SD card, like I had.
I use Astro File Manager to backup all my apks to my /sd/backup/apps (which is automatically set).
Once you have all your APKs in one directory, I suggest putting them on you C:\. For example "c:\apps" for ease of scripting.
Step 1.
Open command prompt (CMD) and change directory to your "c:\apps"
Example:
Code:
cd..
cd..
cd apps
Now you should see your path set as "C:\apps" in CMD.
Step 2.
Create directory print.
In CMD "C:\apps" run:
Code:
dir /s /b > print.txt
This will print all directory files and extensions but nothing else, like size and attributes into your "C:\apps" folder. Now you will see a "print.txt" file in your "c:\apps" folder. If you open it, you will see a list of all your APKs.
Step 3.
Assuming you are using Notepad to view your "print.txt" file, press "CTRL+H". This will open the Find and Replace dialog box.
In Find type
Code:
C:\
In replace type
Code:
adb install -r c:\
Hit enter and it will modify all the APKs with the adb install command. Save and close notepad.
Step 4.
Now you need to rename that .txt extension in your "c:\apps\print.txt" to "print.bat". You need to have extension shown in windows. Google that if you dont know how to do that.
Once saved as a .bat file, simply execute and it will run through the sequence to install all your APK files without any prompts on your phone. Voila, and enjoy.
EXAMPLE:"c:\apps\print.bat"
Code:
adb install -r c:\apps\com.twitter.android-1.apk
adb install -r c:\apps\com.ups.mobile.android-2.apk
adb install -r c:\apps\com.vavni.android.battleship-1.apk
adb install -r c:\apps\com.viclabs.myRemote-2.apk
adb install -r c:\apps\com.waterflea.wifiscan-1.apk
adb install -r c:\apps\com.wyse.pocketcloud-1.apk
adb install -r c:\apps\com.xrath.jmsn-2.apk
adb install -r c:\apps\com.xtralogic.android.rdpclient-1.apk
adb install -r c:\apps\com.xtremelabs.android.speedtest-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.im-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.mail-2.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.search-1.apk
adb install -r c:\apps\hongbo.bluescreen-1.apk
adb install -r c:\apps\info.marlan.sim-1.apk
adb install -r c:\apps\koushikdutta.telnet-1.apk
adb install -r c:\apps\kr.mobilesoft.yxplayer-2.apk
adb install -r c:\apps\net.mafro.android.wakeonlan-1.apk
adb install -r c:\apps\nl.rogro.GScript-1.apk
adb install -r c:\apps\org.ajeje.fakelocation-1.apk
adb install -r c:\apps\org.ale.abtc-1.apk
adb install -r c:\apps\org.android7.aviplayer-1.apk
adb install -r c:\apps\org.connectbot-1.apk
adb install -r c:\apps\org.gmote.client.android-1.apk
adb install -r c:\apps\org.iii.ro.meridian-1.apk
adb install -r c:\apps\org.kman.WifiManager-1.apk
adb install -r c:\apps\org.openobjectives.serverassistant-1.apk
adb install -r c:\apps\org.prowl.networkmapper-1.apk
adb install -r c:\apps\org.transdroid-1.apk
This will go in sequence and show "success" when finished installing. It will then run the next command in sequence until its done.
** I tried to write this thread as a help to those trying to do the same thing I was trying to do. This is in no way meant to validate anything and is meant merely as a resource to anybody. If your going to be an ass, shove it, if you like it, im happy I could help.**
Wow, that certainly is an interesting solution. Personally I just push everything to data/app when in recovery, wipe dalvik-cache, then reboot, always works fine.
An even easier solution:
http://forum.xda-developers.com/showthread.php?t=716806
Thanks man! this helpes me out with multiple installs on the SDK's VM.
hello,
i know i am off topic but i dont find only this thread with the app i am searching.
i search for the "ups mobile" app and the market on my desire (froyo 2.2) found this app not. (Sorry for my english) The app is free, no warez!
Can anyone send my the app or an link with the app ?
many thanks and sorry for off topic.
peter
Check this out...
http://forum.xda-developers.com/showthread.php?t=740545
All the work are already done :0)
Thanks for the advice. However, I have about 50 apks to backup and Astro is unable to backup like 15 of them. IE Crystallight Defense. It just says it's unable to do it and I don't know why. Thanks for any help.
awesome, simple yet effective ... just restored 103 apps
thanks
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Install apk
Hello Fellow Androids!
If this is off topic, please accept my apologies. I am searching through all of XDA for a simple solution to adding apk. Now before you start bashing, please keep in mind that I am well aware of the "search" options + google + XDA etc.
Long story short, I have:
1) Rooted
2) Fashed many Roms (currently on Stock 2.1)
3) Lag Fixxed (see signature)
4) Removed Bloatware
5) I am familiar with ABD and commands
Problem:
All I'm trying to do is install certain "apk"s using ADB. I am well aware of the Program that installs/ pushes apps automatically that are found in G1 + Vibrant + HTC + Droid Forums without having to do any typin......BUT.....I would like to know my way around ABD <----Main reason why i dont want the easy way out.
I have been here:
http://forum.xda-developers.com/showthread.php?t=716806
as well as here:
http://forum.xda-developers.com/showthread.php?t=743457
even been here:
http://forum.xda-developers.com/showthread.php?t=740545
I know what you are thinking, why not use them? As i said before, i would like to be efficient with ADB. So...
I have tried methods found here:
http://forum.xda-developers.com/showthread.php?t=517874
As well as:
http://forum.xda-developers.com/showthread.php?t=532719
The problem I am having is:
Whether i navigate to my folder (desktop with all my apps) and use either
"adb push app /system/sd/app
adb push app-private /system/sd/app-private"
or simply
"adb install <path to file> - Example: adb install c:/apps/apps2sd.apk"
I always get the error: "cant find <whatever apk> to install"
No matter which directory i have it, i get that message.
Note:
1) I have debugging on
2) I mounted sd <----also tried Without mounting
3) I have used the same command when I removed bloatware but i understand Adding apks are slightly different.
4) I have all the drivers installed + Microsoft's .net framework + etc
What am i doing wrong?
All Critics, input, education bashing (just not hating) lol are welcome. Thanks!
dannycurtean said:
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Click to expand...
Click to collapse
Very nice, thanks.
Is there any way to make installed APKs being seen by Market ?
I mean, is it possible to relink all the batch-installed .apk files as they were installed from Android market ?
If not, this method is fine at first but becomes painful with all the lost market updates
Thanks a lot
darkcell said:
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Click to expand...
Click to collapse
Thanks a lott for this !!!!
having about 260 apps installed it saves me several hours to reinstall after updating to froyo !!
k.mooijman said:
Thanks a lott for this !!!!
having about 260 apps installed it saves me several hours to reinstall after updating to froyo !!
Click to expand...
Click to collapse
Would be them updated from market, afterwards ?
I fear they'll loose the market link, by installing them from local apk files...
Even easier.
Thanks for the great information. I realize you can save yourself a few steps after gathering all the apk's in one location by using this command line (XP or higher):
Step 2. In the Android SDK folder containing adb, type:
Code:
for %f in (c:\apps\*.apk) do @(echo adb install -r %f)
dannycurtean said:
I looked around the net for a feasable solution but nobody seemed to give me a practical solution. So I decided to experiment and came up with an unbelivable solution that takes literally 20-30 seconds per app and is FULLY automated.
My problem was as follows. I like to install new ROMs by wiping, flashing and reinstalling my apps. The problem with that is when you have 130 apps and Astro file manager seems to install 3-5 then quits back to the packages screen, it becomes extremely friken agrivating and simply hell-as annoying!
So I needed a way to install all my previously backed up apps (which Astro does a BEAUTIFUL job with) from my SD card to my phone all in one go, without prompts and without any input.
To do this its simple, just write your own batch script and run adb install.
You will need:
1. Android SDK (your version, ie. 2.2, 2.1, 1.6 ect.)
Code:
youtube.com/watch?v=A1SOSXwkc_8
2. USB Cable to PC
3. Enable "USB Debugging" on phone
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Now, I assume you already have the APK bunch on your SD card, like I had.
I use Astro File Manager to backup all my apks to my /sd/backup/apps (which is automatically set).
Once you have all your APKs in one directory, I suggest putting them on you C:\. For example "c:\apps" for ease of scripting.
Step 1.
Open command prompt (CMD) and change directory to your "c:\apps"
Click to expand...
Click to collapse
darkcell said:
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Click to expand...
Click to collapse
This looks like a great solution. Is there some way to run this from the phone itself? When I tried using Terminal Emulator in ICS, I get a Segmentation Fault error.
Found this in Google results, was extremely useful for restoring all my Xoom apps from my pre-root times
Hi to spartan062984
Couple of suggestions which I found to work.
Copy adb.exe to \windows\system32.--- this will give you a global adb which works from any directory.
Make a folder 'APK' ( or what you wish ) and put your apk's into it.
In DOS cd to APK and then run your install e.g. adb install xyz.apk \app
Hope it works for you
Keith
dannycurtean said:
I looked around the net for a feasable solution but nobody seemed to give me a practical solution. So I decided to experiment and came up with an unbelivable solution that takes literally 20-30 seconds per app and is FULLY automated.
My problem was as follows. I like to install new ROMs by wiping, flashing and reinstalling my apps. The problem with that is when you have 130 apps and Astro file manager seems to install 3-5 then quits back to the packages screen, it becomes extremely friken agrivating and simply hell-as annoying!
So I needed a way to install all my previously backed up apps (which Astro does a BEAUTIFUL job with) from my SD card to my phone all in one go, without prompts and without any input.
To do this its simple, just write your own batch script and run adb install.
You will need:
1. Android SDK (your version, ie. 2.2, 2.1, 1.6 ect.)
Code:
youtube.com/watch?v=A1SOSXwkc_8
2. USB Cable to PC
3. Enable "USB Debugging" on phone
**Prefer doing a fresh install of latest ROM, no third party apps and dont open Android Market if you have Froyo because it will try and download all your previously downloaded apps again. Cool but not cool here.**
Now, I assume you already have the APK bunch on your SD card, like I had.
I use Astro File Manager to backup all my apks to my /sd/backup/apps (which is automatically set).
Once you have all your APKs in one directory, I suggest putting them on you C:\. For example "c:\apps" for ease of scripting.
Step 1.
Open command prompt (CMD) and change directory to your "c:\apps"
Example:
Code:
cd..
cd..
cd apps
Now you should see your path set as "C:\apps" in CMD.
Step 2.
Create directory print.
In CMD "C:\apps" run:
Code:
dir /s /b > print.txt
This will print all directory files and extensions but nothing else, like size and attributes into your "C:\apps" folder. Now you will see a "print.txt" file in your "c:\apps" folder. If you open it, you will see a list of all your APKs.
Step 3.
Assuming you are using Notepad to view your "print.txt" file, press "CTRL+H". This will open the Find and Replace dialog box.
In Find type
Code:
C:\
In replace type
Code:
adb install -r c:\
Hit enter and it will modify all the APKs with the adb install command. Save and close notepad.
Step 4.
Now you need to rename that .txt extension in your "c:\apps\print.txt" to "print.bat". You need to have extension shown in windows. Google that if you dont know how to do that.
Once saved as a .bat file, simply execute and it will run through the sequence to install all your APK files without any prompts on your phone. Voila, and enjoy.
EXAMPLE:"c:\apps\print.bat"
Code:
adb install -r c:\apps\com.twitter.android-1.apk
adb install -r c:\apps\com.ups.mobile.android-2.apk
adb install -r c:\apps\com.vavni.android.battleship-1.apk
adb install -r c:\apps\com.viclabs.myRemote-2.apk
adb install -r c:\apps\com.waterflea.wifiscan-1.apk
adb install -r c:\apps\com.wyse.pocketcloud-1.apk
adb install -r c:\apps\com.xrath.jmsn-2.apk
adb install -r c:\apps\com.xtralogic.android.rdpclient-1.apk
adb install -r c:\apps\com.xtremelabs.android.speedtest-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.im-1.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.mail-2.apk
adb install -r c:\apps\com.yahoo.mobile.client.android.search-1.apk
adb install -r c:\apps\hongbo.bluescreen-1.apk
adb install -r c:\apps\info.marlan.sim-1.apk
adb install -r c:\apps\koushikdutta.telnet-1.apk
adb install -r c:\apps\kr.mobilesoft.yxplayer-2.apk
adb install -r c:\apps\net.mafro.android.wakeonlan-1.apk
adb install -r c:\apps\nl.rogro.GScript-1.apk
adb install -r c:\apps\org.ajeje.fakelocation-1.apk
adb install -r c:\apps\org.ale.abtc-1.apk
adb install -r c:\apps\org.android7.aviplayer-1.apk
adb install -r c:\apps\org.connectbot-1.apk
adb install -r c:\apps\org.gmote.client.android-1.apk
adb install -r c:\apps\org.iii.ro.meridian-1.apk
adb install -r c:\apps\org.kman.WifiManager-1.apk
adb install -r c:\apps\org.openobjectives.serverassistant-1.apk
adb install -r c:\apps\org.prowl.networkmapper-1.apk
adb install -r c:\apps\org.transdroid-1.apk
This will go in sequence and show "success" when finished installing. It will then run the next command in sequence until its done.
** I tried to write this thread as a help to those trying to do the same thing I was trying to do. This is in no way meant to validate anything and is meant merely as a resource to anybody. If your going to be an ass, shove it, if you like it, im happy I could help.**
Click to expand...
Click to collapse
This works good so far.. lets hope that system process likes it.
trying now.
darkcell said:
this is simplest method yet...
copy .apk to any folder in sdcard, mine "marketapp"
then type these following commands below:
=====================================
adb shell
su
cd /sdcard/marketapp
for app in *.apk; do pm install -r $app; done
=====================================
regards,
d4rkcell
Click to expand...
Click to collapse
I love simple solutions in linux
You have killed all 100km long tutorials and apps
Very Good, Thanx
i'm testing
very good method..
good lock..
Hi guys,
sorry if my english isnt so good...
i'm in trouble with ADB..
i want to upgrade my swype keyboard on my NEW M1 rom eu....i got the 1.58 and i want to try the 1.60..
i found a thread on this forum with commands for upgrading the swype like this way:
Code:
adb remount
adb shell
su
pm list packages -f | grep swype
rm /system/app/<restOfApkPathFoundInAboveCommand>
pm uninstall <value after apk= found in result of 2 commands above>
exit
Install normally. If you want the apk in the rom:
adb push <newSwype.apk> /system/app/<newSwype.apk>
adb remount
adb shell
pm install <newSwype.apk>
(found here-> LINK)
I'm stuck at the beginning:
Code:
C:\android\tools>adb devices
List of devices attached
9000ec2a228b device
C:\android\tools>adb remount
remount failed: No such file or directory
my phone is rooted and in debug usb mode..I dont understand how can I go ahead...
what can I do?
thanks
ivan
Same here.
gbates said:
Same here.
Click to expand...
Click to collapse
oh..i'm not the only one! : >
we need to find the solution...but it's not easy..
are u using the NEW M1 rom too?
Rooting doesn't automatically give you remount permissions AFAIK.
i just use this command
Code:
adb push test.txt /sdcard/test.txt
and the copy is ok....i found the file in the sgs sdcard...
The command adb remount is for the /system directory (for set write permission) .... i think it cant find the directory /system on the phone......why?!?!
danmullen said:
Rooting doesn't automatically give you remount permissions AFAIK.
Click to expand...
Click to collapse
mmmm what do u mean? i need to do something else? thanks
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Same results using a different ROM?
psychedelic'd said:
Are you using the internal ext2 lagfix? I think that causes problems with the adb remount command. It doesn't work for me either.
Click to expand...
Click to collapse
No lagfix installed at the moment..i installed lagfix when i was on M2 but i think that reflashing removed the lag fix...is it right?
harold4 said:
Same results using a different ROM?
Click to expand...
Click to collapse
Not yet but i think i'm gonna try it this afteroon if i dont find a solution.
Sent from my GT-I9000 using XDA App
adb remount as well
Trying to remap hard keys, adb remount along with push and pull do not work. Depending on whether im in shell or not I get no such file or directory or file not found errors. I can change into directory of each of the folders im trying to work with, and look at the file but I can't push it from my tools folder(locally) or pull it from the system folder. Every tutorial I see has adb remount command first, which fails every time.
Samsung Fascinate
Blackhole-build your own rom
(also tried on jt's latest rom, same issue
Crazy
I'm having the same issue here too. I'm trying to get a custom boot screen on my rooted Samsung Infuse and I've tried every way I can think of and it wont take. Clockworkmod says successfully installed, but its not. Soon as I reboot I see the At&T stock boot. I've fixed all of my permissions and still no luck.
So I saw a solution to do it via adb by typing "adb remount" and I get the same thing u guys are getting. I've got a headache now. Done all I could, even typing "shell", "su", that all goes well then when I tried to push it "adb push bootanimation.zip system/media" I get adb: not found. Smh, is it a device issue?
i think ive got the solution
flash a new kernel..................................worked for me................
I had previously unlocked my bootloader and was running CM6.1, but I had to go back to stock because my company's email app (Good for Enterprise) refuses access on rooted devices.
I would like to monkey around with different configurations to see if I can find a way to run Good on CM6.1. I don't want to do this if I have to reinstall everything if it doesn't work however.
So my question is this. I just want to get the Clockwork recovery on my N1 so I can back up the non-rooted OS and monkey around a little. Can this be done with ABD on a non-rooted device?
Gave it a shot, worked fine.
"fastboot flash recovery clockwork-image-name.img"
Good for Enterprise still runs, so it isn't looking at the recovery to determine rooted status.
Nevermind, clockwork didn't survive a reboot. Good news is I was able to get a backup first.
After installing recovery via fastboot, try removing the following files via adb:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
danger-rat said:
After installing recovery via fastboot, try removing the following files via adb:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
When I try to do this from the recovery, these files are not found, and adb can't see the device from the bootloader. If I boot into the OS, it will be too late - the recovery would be wiped by then and I am back to square one. I must be missing something.
Is there any way to pull the System partition and mount the .img file on my PC to do this? That sounds a little dangerous though
Just thought, you need root to delete the files.
You'd probably have to root, install recovery, then install a non-rooted ROM, but keep custom recovery...
Sent from my Nexus One using XDA App
This is what you need to do:
1) boot your device into the OS
2) download the rageagainstthecage binary and save it as rageagainstthecage in the /tools folder (in the android SDK)
3) plug your device to your computer
4) open a command prompt in the /tools directory
5) type adb devices to make sure your computer sees your device
6) push the rageagainstthecage binary to /data/local/tmp/ by typing adb push rageagainstthecage /data/local/tmp/rageagainstthecage
7) type adb shell to open a shell
8) change the permissions on the binary to allow it to run by typing chmod 700 /data/local/tmp/rageagainstthecage
9) navigate to the directory (cd /data/local/tmp) and execute the binary by typing ./rageagainstthecage
10) wait for it to run, and it will exit the shell
enter the following command at the prompt: adb kill-server
11) enter the following command at the prompt: adb start-server
12) open an adb shell again: adb shell
13) now you should have a temporary root shell. You should see a # instead of a $. if you still see the $, go back to step 9. You may have to do this a few times (I had to do it 3 times before I got root access)
14) now, mount the /system partition as r/w by typing mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
15) delete the two files: rm /system/etc/install-recovery.sh and rm /system/recovery-from-boot.p
16) mount the partition as r/o by typing mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
17) exit the shell
18) now flash your custom recovery
Awesome, thanks. I'll give it a shot later!
This worked flawlessly, thanks for the great writeup!
Santoro said:
This worked flawlessly, thanks for the great writeup!
Click to expand...
Click to collapse
Two things: First, don't forget that any update from Google always has those two files in it, so they will reappear after every update.
Second, I just reread your first post again. I think you should still be able to kepp root and have your company's email working. I think the problem was that you were using an AOSP-based ROM instead of a stock-based one. Follow the directions for rooting in my signature (the first part is essentially the same as what you just did to gain r/w access to the system partition via adb, the second part is copying su and Superuser.apk to the right directories). Root is essentially one additional file copied to your /system directory, so I believe your company's email will still work with root.
efrant said:
This is what you need to do:
1) boot your device into the OS
2) download the rageagainstthecage binary and save it as rageagainstthecage in the /tools folder (in the android SDK)
3) plug your device to your computer
4) open a command prompt in the /tools directory
5) type adb devices to make sure your computer sees your device
6) push the rageagainstthecage binary to /data/local/tmp/ by typing adb push rageagainstthecage /data/local/tmp/rageagainstthecage
7) type adb shell to open a shell
8) change the permissions on the binary to allow it to run by typing chmod 700 /data/local/tmp/rageagainstthecage
9) navigate to the directory (cd /data/local/tmp) and execute the binary by typing ./rageagainstthecage
10) wait for it to run, and it will exit the shell
enter the following command at the prompt: adb kill-server
11) enter the following command at the prompt: adb start-server
12) open an adb shell again: adb shell
13) now you should have a temporary root shell. You should see a # instead of a $. if you still see the $, go back to step 9. You may have to do this a few times (I had to do it 3 times before I got root access)
14) now, mount the /system partition as r/w by typing mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
15) delete the two files: rm /system/etc/install-recovery.sh and rm /system/recovery-from-boot.p
16) mount the partition as r/o by typing mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
17) exit the shell
18) now flash your custom recovery
Click to expand...
Click to collapse
Without unlock recovery i can install Amon RA?(‘fastboot oem unlock‘)In this way as u typed.
W3ber said:
Without unlock recovery i can install Amon RA?(‘fastboot oem unlock‘)In this way as u typed.
Click to expand...
Click to collapse
Not sure what you are asking.
If your bootloader is unlocked, you can use fastboot. Download the recovery image you want into the /tools directory of your SDK and rename it recovery.img. Open a command prompt in the same directory. Type fastboot devices to make sure fastboot sees you device. Then type fastboot flash recovery recovery.img and you are done.
If your bootloader is not unlocked, you can use flash_image, but you need root access. See attachments on how to get root if your bootloader is locked, and how to flash a custom recovery with a locked bootloader.
efrant said:
Two things: First, don't forget that any update from Google always has those two files in it, so they will reappear after every update.
Second, I just reread your first post again. I think you should still be able to kepp root and have your company's email working. I think the problem was that you were using an AOSP-based ROM instead of a stock-based one. Follow the directions for rooting in my signature (the first part is essentially the same as what you just did to gain r/w access to the system partition via adb, the second part is copying su and Superuser.apk to the right directories). Root is essentially one additional file copied to your /system directory, so I believe your company's email will still work with root.
Click to expand...
Click to collapse
I was using the Nexus One 2.2.1 stock image directly from Google. My problem is that the Good for Enterprise actively checks for root. Specifically if the Superuser.apk exists, it refuses to let me in and cites corporate policy.
Since getting my stock backup, I was free to experiment and I had some success getting Good running on CM 6.1. Taking clues from your earlier instructions, I used adb shell to rename su to su.bak and Superuser.apk to Superuserapk.bak on the phone, then rebooted. After the reboot, I don't have root anymore.
This is a compromise, but at least I don't have to give up that CM6 goodness just to use my corporate email. So far I have not seen any issues in CM6 resulting from not having root. In an emergency I can rename them the superuser files back using rageagainsthecage as you outlined but I probably won't do it often.
Thanks for the help!
Santoro said:
I was using the Nexus One 2.2.1 stock image directly from Google. My problem is that the Good for Enterprise actively checks for root. Specifically if the Superuser.apk exists, it refuses to let me in and cites corporate policy.
Since getting my stock backup, I was free to experiment and I had some success getting Good running on CM 6.1. Taking clues from your earlier instructions, I used adb shell to rename su to su.bak and Superuser.apk to Superuserapk.bak on the phone, then rebooted. After the reboot, I don't have root anymore.
This is a compromise, but at least I don't have to give up that CM6 goodness just to use my corporate email. So far I have not seen any issues in CM6 resulting from not having root. In an emergency I can rename them the superuser files back using rageagainsthecage as you outlined but I probably won't do it often.
Thanks for the help!
Click to expand...
Click to collapse
Just for your info, Superuser.apk does not give you root, it only manages the root permissions. If your corporate email application checks only for Superuser.apk, you could technically delete Superuser.apk and keep the su binary. Your would still have root, and your corporate email app would work. The su binary is what actually gives you root access. All that the Superuser.apk file does is manages the permissions for root access, i.e., it allows or denies applications from using the su binary. Everything would work fine (including all apps that require root) without Superuser.apk. HOWEVER, just as a warning, without Superuser.apk, you would have no control over which apps have root access...
I will have to put su back and see what happens. I may be recalling wrong, maybe it checks for su also...
I experimented a bit more and it looks for both files. Sorry for the confusion.
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
So I picked up a ADT-1 due to having Ethernet and more HD space on it. FOund out only certain apps can "cast" to it due to it being a dev device has there been anyone that figured out what needs to get it to have full casting features?
https://developer.android.com/tv/adt-1/index.html
Try changing ro.build.type to eng in build.prop, that should open up all apps.
/sub
let us know if this works
Confirmed this works!
HomerSp = worth his weight in gold.
Sorry
HomerSp said:
Try changing ro.build.type to eng in build.prop, that should open up all apps.
Click to expand...
Click to collapse
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Bboy_LeoGun said:
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Click to expand...
Click to collapse
1. Root
2. Open /system/build.prop
3. Change the line
4. Reboot
5. Enjoy.
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Budius said:
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Click to expand...
Click to collapse
build.prop has to be chmodded to 0644, or the device will not boot.
HomeSp I can't thank you enough!
That was exactly the issue. Third time is a charm.
So at the end of the procedure I:
- cd /system/
- mv build.prop build.prop.bak (just for the the sake of it)
- mv /sdcard/build.prop /system/
- chmod 0644 build.prop
- chown :root build.prop (prolly not needed but what-a-heck, why not)
- ls -l (and checked that both build.prop and build.prop.bak are exactly the same permission, owner and group)
- exit, exit adb reboot and all works great"
Thanks again!!!
Budius said:
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
Click to expand...
Click to collapse
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
jm9843 said:
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
Click to expand...
Click to collapse
my idea was a bare-minimum changes too. I just ended up ****ing up stuff and had to re-built a couple of times until I made it right.
but yeah, if you're comfortable with terminal commands and do the proper `chmod` (which I originally didn't), you can get everything done with "adb shell su" following like this:
- from PC: adb shell pull file to your PC
- from PC: edit file
- from PC: adb shell push file to /sdcard/
- from PC: adb shell
- from device shell: su
- from device shell/su: make /system/ writable, chmod file, rename "old" build.prop, copy new one over, double check chmod before rebooting.
ps.: the root from that post does install SuperUser.apk on the device, it's there on the UI, but after you do those changes there's some options in the .apk to remove root and uninstall it (if you want to)
I just thought that I'd directly use some build prop editor apk and do it easily but now my device is bricked :v
Stock ROM on download.
I'm just getting a black screen and bootloader.
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
jm9843 said:
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Have any of you tried Slingplayer casting after changing build.prop?
Apple TV just died recently, it was the most reliable thing for Airplaying Slingplayer. Chromecast slingplayer kind of is ****ty at times.
Followed Budius' instructions and it worked perfectly.
adb pull /system/build.prop
----(edit build.prop on Notepad++ and changed ro.build.type=user to ro.build.type=eng)
adb push build.prop /sdcard/
adb shell
su
mount -o remount,rw /system
cd /system/
mv build.prop build.prop.bak
mv /sdcard/build.prop /system/
chmod 0644 build.prop
chown :root build.prop
ls -l
---(checked that both build.prop and build.prop.bak are exactly the same permission, owner, and group)
mount -o remount,ro /system
exit
exit
adb reboot
during the update from 5.0 -> 5.0.2 my ADT-1 stopped working again
It showed the little droid with the belly open and an error message
so that means here I went again to restore it, and this time I manage to streamline a bit the process, so let's share with you guys. Remember, my idea with this process is to have STOCK, but with Cast working from any app. I have no intention to root, or flash custom this or that. I want something that I can cast without issues and hopefully it will update the next update without problems.
first of all, the CWM link I posted before is giving malware warnings on Chrome so I found an alternative, and of course XDA is the source (see downloads).
so to factory restore ADT-1 to good working condition, was the same I said before:
- install CWM:
Code:
fastboot flash recovery cwm_molly_recovery_lpx13d.img
- install stock image. CWM->install zip-> from ADB:
Code:
adb sideload update-molly-Stock-LPV79-1.zip
- reboot and let auto-update run until the end.
now to enable cast to all apps with absolutely minimal modifications to the system (hopefully enabling future updates to run without issues)
- reboot ADT-1, holding the button, enter fastboot mode
- reboot to the CWM, but without installing it:
Code:
fastboot boot cwm_molly_recovery_lpx13d.img
- in CWM go to `mount n storage` -> mount /system
and carry on to do the build.prop modification from there, the trick is that I did not have to install a custom recovery and did not have to install super user. I made the modification directly via a RAM-only CWM and that's it. So below is just a copy of my previous post
Code:
> adb pull /system/build.prop /home/budius/build.prop
then change the build.prop on my computer and rename to new_build.prop.
And back to terminal
Code:
> adb push /home/budius/new_build.prop /system/new_build.prop
> adb shell
# cd system
# mv build.prop build.prop.bak
# mv new_build.prop build.prop
# chmod 0644 build.prop
And that's all! Full cast enabled to ADT-1 with the most absolutely minimal system changes I could come up with :victory: :highfive:
Downloads:
- here you'll find a very nice workin CWM.
- good working stock Android TV image for ADT-1
bonus:
while searching stuff I found this: https://plus.google.com/+AdamLawrence/posts/5Yr5vG7QJUq
I didn't try it but it seems useful, so the link is there.