Database Develop

[Q] adb remount

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................

Inverted Google talk app?

I have read the discussions about amoled screens not using battery on pixels which are meant to be black because it simply doesn't light anything up in the case. I was wondering if its possible for someone to make a Google talk app that is black with white text. Since that's my most used app I'd be interested in seeing if it makes any battery savings.
Sent from my Nexus One using XDA App

I could have sworn that it had a black background in the Eclair days... or at least on CM5.x Eclair. I could be mistaken, though.

Its been done, along with gvoice.
http://forum.xda-developers.com/showthread.php?t=821214
Waiting for Gmail.
Consider that you will not be able to update without uninstalling the modded version.

Wow that's brilliant..never even thought about that before
Sent from my Nexus One using XDA App

The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk

Jack_R1 said:
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Click to expand...
Click to collapse
You mean you can't see if other people are on mobile or on android? Thanks for the update!

ksc6000 said:
You mean you can't see if other people are on mobile or on android? Thanks for the update!
Click to expand...
Click to collapse
I mean - before my update you couldn't see any of those. Not mobile and not Android. The watermarks just didn't show up near the contacts. Now you can see both.

Jack_R1 said:
I mean - before my update you couldn't see any of those. Not mobile and not Android. The watermarks just didn't show up near the contacts. Now you can see both.
Click to expand...
Click to collapse
Thanks, I really appreciate it. I'll push it when I get home.
Maybe you can help answer a problem I'm having, I have 2 nexus ones, one for Tmo and one for ATT. The ATT is just a backup in case I move to ATT someday, and it's like my wifi tablet lol.
Anyways, when I originally figured out how to push the talk apk to my TMo nexus one, it worked perfectly. However, when I pushed it to the ATT one, it looked like it worked fine, it showed that the 1032 kb were pushed (I'm just guessing the amount)...and I rebooted the phone...the google talk is still white :S....I did it again, and again it looked like it worked fine, but the google talk is still white! Any idea how to check to see what I'm doing wrong? The command I'm entering is fine..
The talk.apk is in my sdk tools folder..and the command I'm using is
adb push talk.apk /system/app/talk.apk

The command you're entering is wrong. Linux is case sensitive, so is Android. Copy the command I gave above EXACTLY. And you might be pushing the wrong file, since you don't have it named right.

Thanks,
I had just figured it out last night. I needed to capitalize the T in talk....however, now when I do
adb shell
cd /system/app
ls
I see in the files that there is a Talk.apk, and also a talk.apk. How do I remove the "talk.apk"?
adb pull talk.apk /c:/talk.apk ?

Pull doesn't remove, only copies to PC.
adb shell
cd /system/app
rm talk.apk
Once you execute "adb shell", you get to Linux shell. SH, specifically. Work with files and folders like you would in Linux.

Jack_R1 said:
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Click to expand...
Click to collapse
Works fine. Thanks.

Any way to install this via terminal emulator?
I am running Enom's 2.14.1, and I have apps2ext enabled...
I tried to use the command "mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system"
to remount via terminal emulator, but it says mounting remount on /dev/block/mtdblock3/system failed: Not a directory.
So I'm trying to figure out how to install these without the computer. I don't have root explorer but I'm not sure how it would work considering I have apps2ext enabled.
Any suggestions?

ksc6000 said:
Any way to install this via terminal emulator?
I am running Enom's 2.14.1, and I have apps2ext enabled...
I tried to use the command "mount -o rw, remount -t yaffs2 /dev/block/mtdblock3 /system"
to remount via terminal emulator, but it says mounting remount on /dev/block/mtdblock3/system failed: Not a directory.
So I'm trying to figure out how to install these without the computer. I don't have root explorer but I'm not sure how it would work considering I have apps2ext enabled.
Any suggestions?
Click to expand...
Click to collapse
Theres a space before "/system".
should work
1)mount as above
2)command: cp /sdcard/Talk_Mod.apk /system/app/Talk.apk

Thanks,
that gives me a new error though:
Code:
can't create '/system/app/Talk.apk': File exists

Got it!!
This command worked in terminal emulator to remount
Code:
mount -o rw,remount /system
Then I was able to do the cp /sdcard/Talk_Mod.apk /system/app/Talk.apk

Have tryd but it force close! :-(

bgx said:
Have tryd but it force close! :-(
Click to expand...
Click to collapse
Make sure you're running compatible version. This is for Froyo, you're running CM7 - not the same Gtalk.

Jack_R1 said:
The app was problematic - not showing Mobile and Android contact status. I've updated it and attached the APK in the linked thread.
Attaching it here too.
adb push TalkMod_Mod.apk /system/app/Talk.apk
Click to expand...
Click to collapse
this is for Froyo, correct? Do you happen to have a Gingerbread version?

No, I didn't make one. Try to look for various dark CM7 themes, you'll probably find it there.

BusyBoX

I have busybox 1.6 on my captivate i see on www.busybox.net 1.17.3 is out. I have downloaded it from the site and its a tar file with a folder with a whole bunch of folders and files. How do you install this?

Are you familiar with the phrase, "if it isn't broken, don't fix it?"
I advise you to heed its warning.
But if you must proceed, a quick google search for "how to install busybox manually" brings up this very good result: http://www.droidforums.net/forum/droid-2-hacks/82573-busybox-manual-install-how-guide.html
Edit: By the way, love the avatar. Great album.

Yes i understand if its not broke don't try to fix it but i'm a OCD updater! Would there be any advantages of updating it? P.S. I saw Megadeth and Slayer a month ago they rocked!

Only advantages I can see are having a couple more bug fixes and maybe 4-5 new commands built in.

Download Busybox-1.17.2 HERE
Extract busybox to your SD Card
Make sure you are in PC Mode and Debugging is enabled in Applications options
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/busybox /system/xbin/
cd system/xbin
busybox --install /system/xbin/
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
sync
reboot
You can also use Root Explorer or whatever file browser you may use to copy busybox to your system/xbin folder. Some people use system/bin but I prefer xbin...just a habbit.
Click to expand...
Click to collapse
Ya, I read that and got really scared.
What is PC mode and where do you type these commands? (Vista user)

Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.

Cruton502 said:
Ok, figured out how to type in the commands and stuff, but I get stuck on the "cp /sdcard/busybox /system/xbin/" part, I get "cp: not found" I tried lookin up other methods and I keep getting stuck at the same part - trying to move the folder to the xbin folder. adb push gives me the same error - adb: not found.
any help would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.

miztaken1312 said:
Are you rooted? If your answer is yes, just download Busybox from the market and let the app do the installing for you.
Click to expand...
Click to collapse
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!

Cruton502 said:
Brilliant! Sooo much easier, but I'm not NAND unlocked, I'm z4rooted so it wouldn't install. Tomorrow I'll see if I can root through NAND.
I'll break you yet AT&T!
Click to expand...
Click to collapse
I think you're seriously confused. The Captivate isn't a NAND locked phone. Generally when you root, busybox is installed. (I think. At least it always was for me.) You could also try installing Titanium Backup and have that install busybox for you.

[Q] how to get market

I just put cm7 on a sd and am running it on my NC. how do I get the market on it? I saw one link but don't understand how to do it.

If all you want is the market, you can download the newest market APK from my webserver. The link is:
http://www.r00tyou.com/android/tools/Vending(new).apk
To push it to the device simple connect the device to your computer using ADB and type the following in the console:
adb devices
adb install \path\to\the\downloaded\apk.apk
Click to expand...
Click to collapse
Wait for it to successfully transfer over and install.
The viola, you have the newest market APK.
However, I suggest that you download the newest GAPPS from the cyanogen website and push over the whole gapps.
To do this, simply download the latest GAPPS from here:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps
Again, using ADB type the following commands:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [the path to your SDK tools folder]\system system/
adb reboot
Click to expand...
Click to collapse
The console will show the progress of what apps are being transferred over and installed. Once it is done rebooting it will prompt you for logging in to your google account to setup your device. You can simply skip this (Tapping in each corner of the screen starting from the top left going clockwise) or you can proceed with the setup process.
Hope that helps

Thanks for the info. It took some doing because I haven't written code since DOS.

Thanx alot man i had the same problem and this worked perfecty

Not sure if it's important since /system/ is mounted ro anyway but all apps in /system/app/ have 644 permissions, pushing files with adb (whether in linux or windoz) will give them 755 permissions defaultly, so I usually do a:
chmod 644 [app-name].apk
after I transfer the file. Might be a good idea to do this if you are remounting it a lot.
Cheers,
Mike
PS. Themed Markets :-D

[ROOT][10-29-13]How to Manually Root the Nvidia Shield

Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.

Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root

Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.

wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.

This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.

dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium

shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.

I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris

i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.

shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris

i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.

Does anyone if the root stop you from updating the device like GS4?

Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.

I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2

wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.

Finally success root my shield

oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc

gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?

Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.

gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.