Related
With certain files, SteelH describes using Root Explorer as "like trying to swap the engine of a car while it's running"
I experienced this as I tried to copy back a modified services.jar file with Root Explorer. I ended up using ADB and it worked fine.
Question 1: I did this while the phone was running/OS loaded, but ADB copy method worked while Root Explorer didn't. Why? Does ADB have higher authority in some way?
Question 2: How about using a terminal window on the phone to copy/replace files (if a computer is not handy)? Does it yield the same function/result as Root Explorer or ADB?
Question 3: If I simply want to back up the file, say services.jar or framework.apk, to be copied to SD, can I use Root Explorer for that?
Thanks.
snovvman said:
With certain files, SteelH describes using Root Explorer as "like trying to swap the engine of a car while it's running"
I experienced this as I tried to copy back a modified services.jar file with Root Explorer. I ended up using ADB and it worked fine.
Question 1: I did this while the phone was running/OS loaded, but ADB copy method worked while Root Explorer didn't. Why? Does ADB have higher authority in some way?
Question 2: How about using a terminal window on the phone to copy/replace files (if a computer is not handy)? Does it yield the same function/result as Root Explorer or ADB?
Question 3: If I simply want to back up the file, say services.jar or framework.apk, to be copied to SD, can I use Root Explorer for that?
Thanks.
Click to expand...
Click to collapse
i can't answer all of these authoritatively, but i will say
-i find adb to be the easiest way to do ANY modifications, as long as you know just a handful of commands and remember to remount. also remember to pull anything you are getting ready to mess with, just in case you bork it up. takes a lot less time to push an unmodified file than it does to do a complete restore. especially if you forgot to backup, lol
-if you have a terminal app mounted with rw privileges, you can move whatever you want wherever you want. however, referring back to my last point, adb is easier. i find that trying to type type type things out on a dinky little keyboard is a bigger pain in my butt than using my full size one, especially when i can use cut/paste from the intertubes.
-i think rooted explorere shouldn't have a problem copying a file from /system/ or /data/ to some folder on your sdcard
Thank you for the information. I just copied a file with terminal (on phone) and Root Explorer. Interesting thing: using the CP command, the file that was copied onto the SD showed the current date. The file that was copied using RE has the original date.
I can't speak for all GT 10.1s, but the one I received at Google I/O certainly does not have Google Books installed and it's not available in the Market. It comes with Kindle pre-installed, so I'm guessing Samsung has inked a deal with Amazon, but uhh... what about choice? I have several books from both Amazon and Google and use both applications on my Xoom, but now I'm curious why I can't use Google Books on my new tablet. Do I need to try to get the Google Books APK off my Xoom or what? Anyone else found a solution, besides reading their purchases online?
EDIT: The attached file is what finally worked for me. Thanks to smaskell for the link.
Books works fine on the 10.1. Just grab it off another device. My guess is that the market may not know the 10.1 yet as it is not really released now aside from IO.
Sent from my HTC Vision using XDA Premium App
I wasn't able to install the tablet version but I did manage to push it to /system/app/ and it works.
1. get root access
2. download busybox
3. adb push busybox /sdcard
4. adb push BooksTablet.apk /sdcard
5. adb shell
6. cd /sdcard
7. su
8. mount -o remount,rw /system
9. ./busybox cp busybox /system/bin - yes, I'm using busybox to copy itself
10. busybox cp /sdcard/BooksTablet/apk /system/app
and you're good to go!
I'm still struggling with this and I've tried installing (via adb, adb shell, and via Astro / app manager) both a BooksTablet.apk (with and without BooksTablet.odex) from a stock Xoom dump and with a copy from my Honeycomb 3.1 Xoom. Am I missing something? Installing always fails and simply putting the files in place does nothing as well (with a reboot). Anyone have any more ideas? I'm out at this point and it seems as if it should be so simple from what you guys are saying! Thanks for the help!
have you tried a deodexed version of the apk?
I have not and cannot seem to find these files anywhere and am not sure how to deodex the files I have. I tried the 1.2.7-dev version of baksmali with no luck. Any other thoughts or perhaps a link to the files you used that seemed to work? Thanks!
I used the one from this thread
http://forum.xda-developers.com/showthread.php?t=1071047
works like a charm
Case closed
Perfect! Thanks for the link, one of the two files in that thread worked like a charm! In case anyone else is looking for it, I've attached the file that worked for me.
Each time I try installing the BooksTablet.apk file provided above, it fails on the device. When I try installing it via "adb install BooksTablet.apk" it constantly fails with the error "INSTALL_PARSE_FAILED_NO_CERTIFICATES"
I took a look at the logcat output and it seems to be having an issue finding the "fallback_covers.png" file in the assets folder.
I tried renaming the apk to .zip and poking around and I was not able to find this file.
Anyone else having this issue when installing the Google Books app?
I searched around regarding the error message on installation and the solution is to uninstall the app and reinstall it. But because I don't have the app installed to begin with then this isn't an option.
Any help would be greatly appreciated. Thanks.
yeah, I had the same problem. The only way I got it to work was by pushing it to /system/app. see my earlier post for details.
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
nadewad said:
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
Click to expand...
Click to collapse
Did you try navigating to the apk and launching it?
nadewad said:
Ok so I tried following the same steps however, I was having some odd problems. I installed Titanium backup since it automatically installs busybox or so I've been told. When I actually try copying however, the adb shell throws an error saying busybox isn't installed which is odd.
Because of this the cp command also isn't available. Instead I copied over the BooksTablet.apk file from the sdcard to the system/app folder by using the following command:
dd if=/sdcard/Download/BooksTablet.apk of=/system/app/BooksTablet.apk
This command executes successfully however, the google books app still isn't available to launch from the app drawer. I verified that the BooksTablet.apk is actually in the system/app folder however, I still cannot launch it. Any other suggestions? Or did I just completely miss something. Thanks again for the help.
All the best,
Nader
Click to expand...
Click to collapse
While I did have BusyBox installed, I can only vouch for the last thing I did that wound up working since I'd tried so many different things before getting the right APK. So once I had the file in the first post (and of course a rooted GT 10.1), I opened a shell, mounted the /system directory for read/write, chmod'd the app directory to 777, pushed the APK into the /system/app folder and then chmod'd the directory back to 644 (IIRC?). So the steps would have been:
1. adb shell
2. su
(if you get a permission denied error, make sure you leave your screen on and accept the prompt by Superuser Permissions, I forgot this on the freshly rooted tablet the first time)
3. mount -o rw,remount /system
4. chmod 777 /system/app
(now either exit the shell or open a new command prompt)
5. adb push BooksTablet.apk /system/app/BooksTablet.apk
(now back in your su'd adb shell)
6. chmod 644 /system/app
(you'll probably want to note what permissions were there previously as I'm going from memory)
There was no need to launch the APK or issue an install command (it fails anyway), the Books app appeared right away in my app drawer but got a FC after only a moment of it being opened the first time. After a reboot, everything has been working just like on the Xoom!
Hi everyone. As a new Kindle Fire user, I bought mine AFTER the recent Kindle 6.2 update. After following step-by-step the instructions posted on this forum to root KF, I seemed to have succeeded at my first attempt. However, when trying to copy and paste either vending.apk or amarket.apk to system/app folder using File Expert which I got from Amazon store, I couldn't get it to work. This means I don't see either apps in the system app folder after I paste them there. I followed the instructions to the T and rebooted KF, still no show. I then tried to install it via adb, I was able to "adb install" googleservice frameworks on KF. But when trying to "adb push" the market app to system/app, I keep getting "adb access denied". I tried re-rooting with superoneclick, still can't "adb push".
I really don't know what went wrong. BTW, I could hard install the market app on to KF and gained access to the market. (I thought KF blocked it.) But all my download from android market seem unsuccessful. I need help. Thanks.
Problem solved. And here's what I found out and how I made it work. Thanks for everyone who posted to help.
After trying what everyone suggested here, I still couldn't get r/w perssion to the system folder. I reset my KF to factory setting and started all over again. This time I realized it was the File Expert app that's causing this problem. Although it seems like File Expert could gain full access to the system, it doesn't allow you to make any modification to the system folder. I know someone claimed it worked on theirs. But if your File Expert comes from Amazon app store, it DOES NOT work when you try to paste anything into the system. When I realized that ROOT EXPLORER is no longer available on Amazon, I figured that could be the reason. After downloading Root Explorer to my PC and installed it onto KF, everything worked like a charm! So for those of you who encounter similar problems, it's not you. It could be the File Expert app that you got from Amazon.
You need to mount system as writable
Thanks Felnarion. But I did that. It didn't help. I followed the instructions step by step. Don't where the problem is. I find it hard to believe that KF allows me to do regular install of android market(the market icon even shows on the carousel) but I can't do it the "sneaky" way? Anyone else tried installing market app directly from the sd card?
In that case I think it's your app. I just downloaded file expert and had problems copying to /system as well.
Try root explorer, haven't had any problems with it.
File Expert is broken in regards to mounting folders RW/RO. Even though it claims it has successfully changed permissions, it never does or they don't stick. I suffered the exact same issue, regarding mounting folders RW/RO, and had to install Root Explorer to get the job done.
Code:
mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
is the adb command
nycrare said:
However, when trying to copy and paste either vending.apk or amarket.apk to system/app folder using File Expert which I got from Amazon store, I couldn't get it to work. This means I don't see either apps in the system app folder after I paste them there. I followed the instructions to the T and rebooted KF, still no show. I then tried to install it via adb, I was able to "adb install" googleservice frameworks on KF. But when trying to "adb push" the market app to system/app, I keep getting "adb access denied". I tried re-rooting with superoneclick, still can't "adb push".
Click to expand...
Click to collapse
This might be a dumb question, but did you
Code:
su
and click OK on the Superuser prompt on the KF screen prior to the adb push attempts? Were you able to mount /system rw through adb? If adb can't get root access there's no way File Expert will be able to.
devilot said:
File Expert is broken in regards to mounting folders RW/RO. Even though it claims it has successfully changed permissions, it never does or they don't stick. I suffered the exact same issue, regarding mounting folders RW/RO, and had to install Root Explorer to get the job done.
Click to expand...
Click to collapse
File Expert works fine. I've used it to do all my root related installs. You just have to make sure you check the 'Root Explorer' box under Settings>File Explorer Settings before trying to do any /system mounts, it's off by default.
Thank you everyone for your help. If I remember correctly, I did try "su" in adb. but not sure if entered the code correctly. I also heard about File Expert could be the cause when it comes to gaining permissions. I checked root explorer on File expert settings as well. I'm beginning to wonder if my hard install of market app ,which worked to my surprise, messed things up. I will try to reset my KF to factory setting and start over again. I will report back with the result. Once again, I really appreciate everyone's help.
death2all110 said:
Code:
mount -o rw,remount -t ext4 /dev/block/platform/mmci-omap-hs.1/by-name/system /system
is the adb command
Click to expand...
Click to collapse
i have to admit this is the first time I see this code. I tried something similar based on an instruction from another site. But not this exact code. I will try it later.
that command line was a life saver
Saved me a future headache
nycrare said:
After trying what everyone suggested here, I still couldn't get r/w perssion to the system folder. I reset my KF to factory setting and started all over again. This time I realized it was the File Expert app that's causing this problem. Although it seems like File Expert could gain full access to the system, it doesn't allow you to make any modification to the system folder. I know someone claimed it worked on theirs. But if your File Expert comes from Amazon app store, it DOES NOT work when you try to paste anything into the system. When I realized that ROOT EXPLORER is no longer available on Amazon, I figured that could be the reason. After downloading Root Explorer to my PC and installed it onto KF, everything worked like a charm! So for those of you who encounter similar problems, it's not you. It could be the File Expert app that you got from Amazon.
Click to expand...
Click to collapse
Interesting. I was the one it worked for and I'm pretty sure I got mine from the Market, not Amazon. Good thing I haven't clicked that update button from within Amazon App Store.
Thank you for following up. Perfect example of how it can help others.
Glad you got everything sorted.
Hi all,
Ive spent to weekend reading about rooting and ROMS/Kernels and decided to try it. I used a root kit found here from Mskip (great kit). Ive sucessfully rooted, and then sucessfully installed Smooth Rom 4.3 with the Motley kernel.
Ive downloaded Titanium Backup and Rom Manager. TB worked and I did a backup (which I now cant find) (i have ES File Explorer). I upgraded to Titanium Pro, and now when I open the app is states root was denied. I remember when I first opened TB SuperSu asked me to grant it access. After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Sorry if this is noobish, not sure what to do and I dont want to keep going without a backup.
Edit: When I try to backup in ROM Manager I hit backup, it brings up the notification to name the backup, I hit ok and nothing happens.
cam75 said:
After a reboot I opened SuperSu and stated a Binary update was necessary and performed it.
Now TB pro states root was denied, when I open SuperSu there is nothing there in the apps list, and I dont know how to manually grant TB root access.
Click to expand...
Click to collapse
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
bftb0 said:
That sort of sounds like the SuperSU "su" update might have failed. Can you get root with other apps? (e.g. go in to a terminal emulator and type "su")
Note there is a chicken-and-egg problem if (either) SuperSU/su or Superuser/su fail: they need root themselves to remount /system so that the "su" binary can be updated.
If no apps can get root, then you sort of have "lost root", and the fix is to manually insert the .apk and su binary into /system/app and /system/bin/su (or /system/xbin/su depending on flavor!) either with a flash package in recovery, or manually via the adb shell command line (with custom recovery running).
HTH
PS you should be able to just manually start the recovery and do a backup in the meantime, no? The fact that ROM manager isn't doing anything could either be a lack-of-root problem or something else (a busybox dependency?)
Click to expand...
Click to collapse
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]:/ $
When TB is opened it states error "sorry I could not acquire root privilegdes. this applidation will not work. please verify that your rom is rooted and try again. this attempt was made using the "/system/xbin/su" command.
I dont see busybox in my app drawer
cam75 said:
thx for the quick response, however much of that is WAY over my head. I opened terminal emulator and typed su and this is what popped up. 1 [email protected]droid:/ $
Click to expand...
Click to collapse
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
bftb0 said:
If the SuperSU app (and companion binary) were working correctly, you should have seen one of those "Accept / Deny" pop-up messages coming from the SuperSU app... assuming that you didn't previously grant root access to that terminal emulator app. You didn't mention that happening.... ?
Also, usually the command prompt usually changes from $ to # when you have root, but not always; the explicit way to check would be to (after you have tried the "su" command) to type in "id" and hit return at the prompt - that will tell you explicitly if you are root or not. (That's the letter "i" followed by the letter "d" followed by the return key).
From the way you describe this, it is sounding like you lost root.
I gotta go watch part of the game. In the meantime, perhaps you should at least create a backup manually.
As I said, the simplest fix-up would be to get Superuser.apk/su or SuperSU/su re-installed into /system/app and /system/{x}bin/su (it seems that chainsDD and chainfire use different locations).
There might be floating around someplace a flashable zip file with this stuff in it - to be used for "lightly rooting" a stock ROM after a custom recovery is in place. But things have been in flux recently with both the SuperSU (chainfire) and Superuser (chainsDD) kits because of the JellyBean multi-user support, so the version you might need is important. So you would have to do the research to figure out where.
gotta go - good luck.
Click to expand...
Click to collapse
Thanks again.
Im watching Superbowl as well. I didnt grant Terminal access. I rebooted into recovery and restored to right after I rooted. SuperSu auto updated through the play store, and stated the binary need updated. I canceled that. TB and ROM manager are showing up in SuperSu. So now Im rebooting into recovery again to after I installed the Smooth Rom/Motley Kernal. I did make a backup of where SuperSu lost root. I now have three backups.
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
thanks again
I went to my restore point after root and reinstalled 4.3 Smooth ROM Mkernel. I did not take the SuperSu update, (ill wait for the next update) and everything is fine TB an ROM manager working fine, did a backup in both.
Thanks for your help on this.
cam75 said:
Question on installing the SuperSu apk file. I want to be sure I do it right, if needed. Download the file on my 7. it will go to my download folder. Move it to the system folder and open/run it? what do i do with the current SuperSu folder?
Click to expand...
Click to collapse
Dealing with .apk's is not that difficult - drop them into the correct place and reboot.
In Android, apps (.apk files) are stored in one of two places: /system/app or /data/app. It is even possible for two versions of an app to be on the phone - one in /system/app and one in /data/app; that is how upgrades of factory-installed apps happen: the pre-installed app is in /system/app... and never gets deleted (read-only filesystem), whereas update versions get dropped into /data/app. Generally you can just drop an .apk file into either of these locations, wipe the dalvik cache and reboot. During the android boot, these files are compiled into .dex objects in the dalvik-cache, and various version, consistency, rights and permissions are cross-checked.
Think of it this way: when you boot a new ROM for the first time, /data starts out completely empty. Everything needed to support each pre-installed app in /system/app gets created automatically during the android layer start-up.
The "su" native binary is a bit more complicated - it needs to be:
- owned by the user.group root.root
- be executable
- be setuid/setgid
Imagine that you had a copy of these two files on your "/sdcard". If you booted into the custom recovery, you could affect these changes like this:
C:\foo> adb shell
# mount # show what is already mounted
# mount /sdcard # if needed
# mount /system # if needed
# mv /system/app/SuperSU.apk /system/app/SuperSU.apk.old
# cp /sdcard/SuperSU.apk /system/app/SuperSU.apk
# mv /system/xbin/su /system/xbin/su.old
# cp /sdcard/su /system/xbin/su
# chown root.root /system/xbin/su
# chmod 6755 /system/xbin/su
# cd /
# umount /system
# exit
C:\foo>
*
As a practical matter, it is probably easier to just make sure to make a fresh backup if you are about to update the su binary - in case anything goes wrong. It might also be useful to use a root-aware file manager to remount the /system partition in rw mode prior to doing the "update su binary" procedure in the SuperSU app.
Good luck
* note that SuperSU and Superuser apps choose different locations for the su executable file - one uses /system/bin/su and the other /system/xbin/su. There might also be a symlink between these locations. Best policy is probably to examine a known-working installation to determine how to proceed.
Hi!
I've just rooted NST with NookManager.
I'm a total noob in android world (as I don't have any smartphone) and I'm searching for basics about rooted android devices since two days but I didn't come to a solution to my problems.
Simply I want to uninstall some apk as described in this thread http://forum.xda-developers.com/showthread.php?t=1933615
I don't have titanium pro or root explorer.
How to install/uninstall apps and how to take full control about entire nook file system?
Thanks
yell! said:
Hi!
I've just rooted NST with NookManager.
I'm a total noob in android world (as I don't have any smartphone) and I'm searching for basics about rooted android devices since two days but I didn't come to a solution to my problems.
Simply I want to uninstall some apk as described in this thread http://forum.xda-developers.com/showthread.php?t=1933615
I don't have titanium pro or root explorer.
How to install/uninstall apps and how to take full control about entire nook file system?
Thanks
Click to expand...
Click to collapse
It depends on the Launcher you are using.
By default you should have "ReLaunch" installed.
To uninstall an apk, just select it in the app list and hold for a little bit longer. A dialog containing "uninstall" option the should pop up.
The other way is to use "NookColorTools".
http://forum.xda-developers.com/showthread.php?t=868366
Install it , run it, select "manage applications", select certain apk, uninstall it.
edit : you should probably place 'NookColorTools' in /system/app/ using ADB
######################################
Installing apk's
1 way - put 'some_app.apk' on mSD card and select it using any file manager.[/COLOR]
2 way - configure ADB, connect your nook and type 'adb install /your_apk_location_on_harddrive
3 way - install Google Play using 'NTGAppsAttack', install "searchmarket.apk" (i uploaded it somewhere, check my posts), search for apk in google play and install it.
#############################
To uninstall a system apk
Read the forum before deleting any system apk's.
Most of them are necessary for the system to work.
1 way - get any file manager that can mount root partition (Rhytm file manager ; ES file explorer) , select "root explorer" in options, navigate to '/system/app/', Move/delete any apk that you desire.
2 way - configure ADB, connect nook, type 'adb shell', 'mount -o rw,remount /dev/block/mmcblk0p5 /system', 'cd system', 'cd app', 'ls' (to see apk list), 'rm apk_name.apk'.
#############################
To install a system apk.
configure ADB, connect nook, type 'adb shell', 'mount -o rw,remount /dev/block/mmcblk0p5 /system'
exit ADB, from your system type 'adb push /your_apk_location /system/app'
#############################
If you encounter problems with installing from mSDcard search for "howto allow install non market applications on android'.
Remember that only Apk's for Android 2.1 will install. 2.2+ versions will give you an error.
That works great except for MetroUI and Apple 4S. Neither of which seem to want to uninstall from the play store and there's no app entry to hold down on to force deletion.
Plus ESfilemanager isn't letting me go to the system menue else I'd delete the apk there and while ReLaunch /will/ for some reason let me go to /system/apps since it won't let me move the library.apk back to the app folder from backup I'm not sure I trust it to not somehow fubar a delete.
Plus my sister deleted my nook backup image.
Any ideas how to safely clear these thins for someone that's clueless on how to use ADB from ubuntu 12.04? A link to an idiot's guide would be nice if nothing else.
Goggles2114 said:
That works great except for MetroUI and Apple 4S. Neither of which seem to want to uninstall from the play store and there's no app entry to hold down on to force deletion.
Plus ESfilemanager isn't letting me go to the system menue else I'd delete the apk there and while ReLaunch /will/ for some reason let me go to /system/apps since it won't let me move the library.apk back to the app folder from backup I'm not sure I trust it to not somehow fubar a delete.
Plus my sister deleted my nook backup image.
Any ideas how to safely clear these thins for someone that's clueless on how to use ADB from ubuntu 12.04? A link to an idiot's guide would be nice if nothing else.
Click to expand...
Click to collapse
>TUTORIAL - EVERYTHING ABOUT ADB - Fully Illustrated
http://forum.xda-developers.com/showthread.php?t=1241935
-use ADB to install NookColorTools
-go to 'manage applications' (in NCT)
-delete what needs to be deleted
Deleting files is needed only when you want to get rid of a system app.
Don't forget to mount system partition with write permissions. Otherwise you will not be able to copy NCT to /system/app/
You are a lifesaver (and is this thing pinned? I don't recall seeing it pinned. Hell best way of hiding a thread is put it at the very top with a sticky and making it red blinky bold letters.)
OK derp. That guide's windows. Need something linux-centric. I've a feeling after the initial setup it's similar
On command line 'adb devices' gets me nothing even with nook in usb mode.
Edit again: http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Using that guide. Will edit/respond with results.
Edit the Third: Odd. Didn't have ot use ADB. ReLaunch let me install. Now to figure out wtf about mountingaccessing internal storage as root.
Thank you for your replies!
I prefer the ADB method via USB, I do not like to modify things by touch screen.
I installed ADB, server is running and nook is connected by usb cable, but no devices are found
Google does not help me (or I am failing with keywords) and I do not want to use a wireless connection.
yell! said:
Thank you for your replies!
I prefer the ADB method via USB, I do not like to modify things by touch screen.
I installed ADB, server is running and nook is connected by usb cable, but no devices are found
Google does not help me (or I am failing with keywords) and I do not want to use a wireless connection.
Click to expand...
Click to collapse
Make sure you have the driver installed properly. See the wiki article on installing the ADB driver for the Nook Simple Touch.
yell! said:
Thank you for your replies!
I prefer the ADB method via USB, I do not like to modify things by touch screen.
I installed ADB, server is running and nook is connected by usb cable, but no devices are found
Google does not help me (or I am failing with keywords) and I do not want to use a wireless connection.
Click to expand...
Click to collapse
Use "ADB konnekt" to connect with your pc via wifi.
If you want to connect via USB you have to turn on "USB DEBUGGING" (manually of using NookColorTools)
and add correct udev rules (http://ubuntuforums.org/showthread.php?t=1918512) on linux.
There are some differences in adding udev rules in different versions of Ubuntu/Debian/Mint. I have no idea on how to do that on Fedora,Gentoo etc.
Don't know how to do that on windows. This info can be found using a search engine x]. Look for ("android device adb setup windows")