Related
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
usadevil7193 said:
hi mate...i m new to android..i own a nexus1..hav rooted without unlockin d bootloader..i am tryin to push d track ball to wake mod...evry time i type adb remount it says permission denied..any ideas to get things workin...???????
Click to expand...
Click to collapse
Welcome to XDA and Android! Are you trying to get help for your Nexus One? This forum here is specifically for the HTC Hero CDMA.
You will probably find better and more specific help in the Nexus One forums which are here: http://forum.xda-developers.com/forumdisplay.php?f=556
Great post, very easy to follow, thank you.
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
this also works for the samsung Galaxy S in recovery mode.
mikeybonez28 said:
yea I'm trying to do this, over and over, but with not luck. i have sdk on my pc and im running the cmd prompt to run adb remount & devices and its not picking up the phone, wth is going on, plz help
Click to expand...
Click to collapse
mine shows up but then says error, device offline
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
yogi2010 said:
hi, i have adb recognizing my phone, but i still can't seem to push the files over.... every time i try, i get 'cannot stat 'su' : No such file or directory'. i have made sure over and over to put the files in the same folder where adb is.... actually i have tried placing the files in the tools folder, as well as the platform-tools folder, and i keep getting that error when i try to push anything.
any suggestions? thx
Click to expand...
Click to collapse
i had the same issue with something i was trying to push. I think you need to make sure you have exactly the same file name like caps and all. i was trying to push rootexplorer.apk and i got the same message but i then changed it to RootExplorer.apk and it work.(notice the difference in caps)
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
{LCD}Stelios said:
Does it matter where sdk is installed my file path is
C:\Program Files\Android\android-sdk\tools
instead of
C:\android-sdk-windows\tools.
I just installed it in the default location.
I type adb remount and get the not recognised command.....
Thanks.
I don't think my phone is being picked up?
Click to expand...
Click to collapse
Make sure your have the drivers for your phone installed first of all.....Then, in your command prompt you have to change directories to the sdk (which you made harder by not installing to C:\
Try: cd Program Files\Android\android-sdk\tools
Then type: adb devices
That should return "xxxxxxdevice" connected....Then you know you have it set up.
Look in kyouko sig he has all the commands for adb
Sent from my HERO200 using XDA App
Bierce22 said:
just watch this and it'll explain everything.
http://www.youtube.com/xdadevelopers
Click to expand...
Click to collapse
great video arse....thanks for the help donkey
Flashing fresh ROM via ADB in Linux
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
pacut said:
Hello there.
M volumeUp and VolumeDown buttons are broken on my rooted Desire HD, so I cannot go through CWM any longer.
With regard to this post, I would ask the followings:
1) can this method be used to flash a new ROM (i.e. Coredroid, Leedroid..) without the need of those 2 buttons ?
2) My PC runs Linux. How does it work with this O.S. ?
Thanks
paolo
Click to expand...
Click to collapse
There is a thread somewhere on how to flash without a SD card and flashed using adb I believe, but don't take my word for it. Adb works fine with Linux, just have to set it up differently. Look in my sig and select the compile aosp on Ubuntu one and follow instructions on getting the USB set up.
Sent from Dorian's HTC Hero CDMA
Yes, I saw it. It's http://forum.xda-developers.com/showthread.php?t=911228
The fact is...still have to navigate through menu via VolumeUp/volumeDown buttons
Maybe through ROM manager, premium, I can install ROM direclty.
I am gonna trying
YES ! It works !
Hi I need help. I accidentally wipped my phone in CWM and now I'm trying to use adb push to push the update.zip into my phone sd everything seems to work but then in CMW it says there are no files..
any suggestions?
[Edit]
nevermind
I kept trying different locations
not sure which one did the trick but I'll list the one's I tried
so \update.zip /sdcard/
.... /sdcard/update.zip
(note I put "/update.zip" thinking maybe it needed to be reallocated to the same file/destination
Can i use adb push *.apk /system/app to push several files at once, and then repeat but using *.odex instead of *.apk? I keep ending up getting the same error, and i want to find out which app is messing with me...
rulermon said:
Prerequisites have...
A:android-sdk-windows installed
B: (on your phone) go to menu>settings>applications>developement and make sure usb debugging is checked.
C: the file you are pushing must be placed in the tools folder of adb so if you are pushing file "build.prop.txt" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices example adb push build.prop.txt /system/bin
6. repeat step 3 for multiple files
7. adb reboot this is how you finish
Click to expand...
Click to collapse
Hey guys ...
I have also rooted my phone , everything was OK until one day i tried to write something to /system/app and i recieve this error:
in Addition , i am writing "adb shell" and it shows me $
if i am doing adb shell --> $ --> su --> it shows #
Can some1 knows what is the problem?
This is copied from the Droid2 section and is said to work on the X for those of us that didnt move SU b4 updating to 2.2 or those that lost root for whatever reason.
Cool How to root the Droid 2
All credit goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.
Attached Files
File Type: rar Droid2Root.rar (954.1 KB, 733 views)
Last edited by karnovaran; Yesterday at 01:58 PM.. Reason: Clarity
Reply With Quote
Hello all...
This worked on my DX that I upgraded to 2.2 just fine. The root pw isn't given anywhere in the instructions as it is in the 2.1 manual root steps.
Any thoughts on the root pw so that I can SSH to the device after rooting?
This method worked for me after thru much trial and error I was able to update to Froyo only to discover I lost root. Did not want to roll back to 2.1 and start over. Thanks so much to everyone who came up with root process and to those who discovered it worked on the DX.
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Tried uninstalling and reinstalling everything, the one click roots say it can't find my droid X and going through your instructions adb can't find my device ether. I kinda been having a problem with doubletwist where it doesn't recognize my device properly, could that be related?
I don't know why, but after typing ./rageagainstthecage-arm5.bin it showed the text talking about donations, etc went right back to the $ prompt, and never booted me out of shell. I waited 15 minutes at the $ prompt before Ctrl-break'ing out of shell and trying to relogin. noticed adb is repsonding sluggish. Maybe it's still working? Anyone else having this problem?
Edit: I retried the ./rageagainstthecage-arm5.bin command after rebooting the phone and it worked this time. And I'm rooted! Wireless Tether for Root app works perfectly!
Also I notice when I say PC mode the little debugger icon then doesn't show up like it does in USB mode or charge mode. could this be why the device isn't showing up?
Ok so I manage to get everything good up until the point where I should be looking for a # instead of a $ for terminal. I've done the rage and waited till it kicked me out and went back in and got the same result.
The way that I got through my problems is I set the droid x to USB charge only mode (PC mode there was no debugging and every time I plugged it in, it wouldn't take the ADB driver it wanted a MB810 or something driver)
I know I set the permissions right, and it does run (shows up a little message about donating and in a min or so kicks me out, anything else I can try?
Thanks for the help.
mavermc said:
I tried intstalling the 64bit drivers (then rebooted) then hooked it up in PC mode and can't seem to get it to show up in the list of attached devices.
Click to expand...
Click to collapse
You need to turn off USB debugging first time you connect DX to PC and let the drivers install. After the drivers install, turn on USB debugging and let the driver installation complete again. Then go in terminal (also make sure you change directory to where the adb application is) and type in "adb devices". If your device does not show up, change USB connection method to Windows Media Sync mode on DX and try again.
I hope that helps because that is the limit of my knowledge on the subject.
No reboot, battery pull, then reboot = weird!
Okay, so after I rooted my DX, I went to reboot it (powered off then back on) and it got stuck on the M screen. So I pulled the battery, reinserted it, and then powered on again. It rebooted fine. So...why the battery pull?? Anyone??
So i rooted using this method, (finally got it to work, just used it in usb charge mode on a XP machine) Now my phone seems to drop battery like crazy, all I've changed besides the root is install set cpu (and set some profiles to lower the clock with screen off and low battery and hi temp) installed battery life widget and a little white widget that shows what the current clock speed is. oh and wifi teather, any idea why my battery just sucks now? and things like battery info (to show whats using the battery) force closes on me after root, anyone else with these problems?
read-only what? help!!
is it ppossible to do this from the device?
Will this root work on ota froyo upgrade that we will have in a few days?
Sent from my DROIDX using XDA App
Like many have said it works perfectly if you disable the USB Debugging...install all drivers again and then put it in "Charge Mode"
I finally have my phone rooted...Now I know why my Deodex didnt wanna work. Thanks to all for releasing this and ending my headache
Hi all.
Give a try to my version of the instructions. This is kind of like the holy grail of rooting the Droid 2 at the moment. Much clearer! More info! Enjoy!
http://forum.xda-developers.com/showpost.php?p=7865824&postcount=164
dscottjr81 said:
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two)
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
Click to expand...
Click to collapse
One thing I found was after it ran and returned to a cursor, I closed the cmd window and relaunched it and had no issues. Before I restarted I did switch to Charge only w/ USB debug active.
It wouldn't work at all for me until I put the contents of the Droid2Root.rar in my /tools folder. The adb commands would not work as soon as I "cd c:/Droid2Root", but the adb commands would work in the /tools folder. So I just put the contents of the Droid2Root.rar in my /tools folder and it worked just fine. O yea I'm on the OTA 2.2 (2.3.15) that came out today. I also did it under "Charge Only" with debugging.
So I take it that the One-Click root will not work withfroyo 2.2 update????
i continuously get the money sign even after it kicks me out from the ./rage step and i kill-server then adb shell.
its still there even after 3 attempts at the ./rage step what should i do? it just wont (#) prompt me
I am not a developer or even smart. I poked around until I found something that worked for me. Use at your own risk.
I rooted and installed CM 7.0.2 in the past and was pretty happy. When 7.1.0 came out I took the leap. Everything was great except for GPS. GPS did not connect at all. Nothing I did could bring it back other than going back to stock rom. After much frustration and fighting I have it working.
Many people said to make changes to the /system/etc/gps.conf. The problem I had was S-ON was preventing it and nothing I could find explained a work-around. Sorry if I missed it.
I am going to explain what I did to get it going.
Phone details:
- My phone is rooted and CM7.1 installed.
- S-ON
- GPS don't work (even after 30 minutes of waiting)
- Clockwork is on sdcard as update.zip (not permanent)
- Phone is connected to the computer (with adb installed and working)
Proceedure:
1. Unzip the gps.conf.zip file (attached) to the root of your sdcard
2. Turn off the phone
3. Press and hold the volume down and then press the power button
4. Choose "recovery" from the menu and press power (phone will reboot into recovery)
5. Press and hold volume up and press the power button (this may take a few seconds)
6. Choose "Apply sdcard:update.zip" and press power button (assumes clockworkmod is on the sdcard and named update.zip)
7. Choose "mounts and storage" and click the bottom middle button (trackball)
8. While mount /system is selected press the trackball. (sinkinglow suggested that you might need to mount /sdcard as well)
9. Switch to the computer now
10. At a command prompt (DOS) in the folder where adb.exe is located type "adb shell"
11. Type "cd /system/etc" (if you cant get in then you did not mount /system properly)
12. Type "cp /sdcard/gps.conf ."
13. Switch back to the phone.
14. Click the trackball again to unmount /system.
15. Click the back arrow (bottom right)
16. Choose "reboot system now"
Once the phone is back up, you should be all good.
GPS fix htc espresso
Is there anyway that you could maybe post a youtube video on how to do this, or send me a pm.I will give you my contact info.Maybe you could walk me through it.
ok im stuck at (12. Type "cp /sdcard/gps.conf .") i get this in cmd prompt :
C:\Users\Ryan>adb shell
~ # cd /system/etc
cd /system/etc
/system/etc # cp /sdcard/gps.conf
cp /sdcard/gps.conf
BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
Options:
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Force overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
/system/etc #
then step 13/14 (14. Click the trackball again to unmount /system.) says on phone Error unmounting SYSTEM:!
confused on where to go in cmd prompt i think theres a step missing
Try this
Instead of "cp /sdcard/gps.conf", use :
"cp /sdcard/gps.conf /system/etc"
Worked for me and GPS locks within 15 seconds now.
boss2688 said:
ok im stuck at (12. Type "cp /sdcard/gps.conf .") i get this in cmd prompt :
C:\Users\Ryan>adb shell
~ # cd /system/etc
cd /system/etc
/system/etc # cp /sdcard/gps.conf
cp /sdcard/gps.conf
BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
Options:
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Force overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
/system/etc #
then step 13/14 (14. Click the trackball again to unmount /system.) says on phone Error unmounting SYSTEM:!
confused on where to go in cmd prompt i think theres a step missing
Click to expand...
Click to collapse
Step 12 issue
I think what is being missed it the "." at the end of that comand. The "." is the second argument of the "cp" command and "." means the folder i'm currently in.
If you leave it out you are not telling the cp command where to put the file.
Sorry if I abandoned this post. It sat for weeks with no responses so I quit visiting. Hope it helped you guys out.
Is there anyway that you could post a youtube video on this process.I am missing something
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
Maybe you could send me a pm.Then I could give you my contact info.we could go from there.I just really want to use cm7, but this GPS nonsense is keeping me from doing this.
Assumptions
I made a list of assumptions at the top of the post.
- My phone is rooted and CM7.1 installed.
- S-ON (not required but if you have S-OFF you don't need these instructions)
- GPS don't work (even after 30 minutes of waiting)
- Clockwork is on sdcard as update.zip (not permanent because of S-ON)
- Phone is connected to the computer (with adb installed and working)
So you must have already rooted and installed clockwork as well as CM7. You must have the clockwork (update.zip) in the root of your sdcard. you must have ADB working on your computer and working with your phone (shows in devices list). If you have those then it should be following the steps. I am not currently using my slide and do not have equipment or and account to post videos so that would be difficult. if you can tell me where you get stuck I might be able to help.
Like mentioned before I really don't know what I'm doing. I just tried TONS of stuff till I got a feel for things and found a combination that worked for me.
If you are having issues with rooting or installing CM7 or clockwork then that is beyond this tutorial and there is lots of info out there for that.
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
captorofxxx said:
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
Click to expand...
Click to collapse
Try this out before you begin. http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Simply start from where it says Windows and you should be good to go.
Did this fix just a moment ago and it worked like a charm. Thanks reiter01
I wish someone would post a video or give (intricate-no detail left out) instructions on how to do this.I video would be the ticket.If I could follow someone or watch someone do it........
I wish someone would post a video or give (intricate-no detail left out) instructions on how to do this.I video would be the ticket.If I could follow someone or watch someone do it........
reiter01 said:
I think what is being missed it the "." at the end of that comand. The "." is the second argument of the "cp" command and "." means the folder i'm currently in.
If you leave it out you are not telling the cp command where to put the file.
Sorry if I abandoned this post. It sat for weeks with no responses so I quit visiting. Hope it helped you guys out.
Click to expand...
Click to collapse
yeah i think that was the problem i didnt see the ''." there and sorry if im being noob with adb i was never any good with cmd prompt, i prefer a GUI
ADB issues
There are countless posts and article about getting adb working. I use a Mac so it's never an issue for me. If you haven't already installed the USB drivers for your specific phone the first time you hook up then you will have issues. Windows will choose a generic driver that ADB can't use. You need to find instructions on removing the generic driver and install the right one.
I'm really glad some had had success with my little tutorial. I am sure there has to be easier ways but it's the best I could come up with.
Worked great
This worked great for me, my GPS now locks on within seconds. One note to add, I had to mount /system and /sdcard. Thank you for this fix.
GUIless
@boss2688: I agree with having a GUI when available. I have no phone programming skills and so I didn't try that. I am not sure if it would work anyway because the S_ON would be in place blocking by the time the GUI shows up. On the other hand, I am sure that someone could make a zip with scripts etc to do what I am doing manually. I tried and failed to make a zip. I wanted to have it work just like you install google apps from clockwork.
@sinkinglow: Not sure why you would have to mount /sdcard. It should be mounted already at that point (I think). I no longer use my slide so I can't go back and test. Thanks for the tip. I will see if I can figure out how to edit the original post and add that as a possible step.
reiter01 said:
@boss2688: I agree with having a GUI when available. I have no phone programming skills and so I didn't try that. I am not sure if it would work anyway because the S_ON would be in place blocking by the time the GUI shows up. On the other hand, I am sure that someone could make a zip with scripts etc to do what I am doing manually. I tried and failed to make a zip. I wanted to have it work just like you install google apps from clockwork.
@sinkinglow: Not sure why you would have to mount /sdcard. It should be mounted already at that point (I think). I no longer use my slide so I can't go back and test. Thanks for the tip. I will see if I can figure out how to edit the original post and add that as a possible step.
Click to expand...
Click to collapse
a much easier way if you don't have experience with ADB would be to use Android Commander. Please see http://androidcommander.com/ (of course you would still need to mount the system from clockwork if you don't have S-OFF) hopefully this helps for those still having issues.
CM7 1 MyTouch Slide GPS fix
Im going up on the 26th, and was hoping to try this slide then bop over to Gothics. Im going to get to the slide and then make the call as to how safe it seems....Backup plan is any other thing time permitting from that spot. Thats how I roll
* I have to run USBDeview.exe and delete everything sometimes. I think the devices get confused etc..
* I also have to use "Vista_x86" drivers as none of them work for me ..in XP SP3
Code:
C:\usb\ANDROID\Vista_x86\androidusb.cat
C:\usb\ANDROID\Vista_x86\androidusb.INF
C:\usb\ANDROID\Vista_x86\androidusb.sys
C:\usb\ANDROID\Vista_x86\htcrndis.cat
C:\usb\ANDROID\Vista_x86\htcrndis.inf
C:\usb\ANDROID\Vista_x86\WdfCoInstaller01007.dll
Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
smokewagon said:
Hi All,
I am in the process of trying to root and install a custom rom on my Nexus 4 4.4.2. I am a new linux user (Linux Mint 16) and my rooting experience is limited. When I try to do an "abd pull /sdcard/ /sdcard/" this is what it says
adb pull /sdcard/ /sdcard/
pull: building file list...
pull: /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1 -> /sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1
cannot create '/sdcard/Android/data/com.google.android.gallery3d/cache/imgcache.1': No such file or directory
I was able to successfully do an abd backup...
USB debugging is enabled.
I get the same error whether the phone is connected as a Media device (MTP) or Camera (PTP).
any reason why the pull command wont work?
Any help is appreciated!
Click to expand...
Click to collapse
Maybe this will help?
http://www.herongyang.com/Android/adb-push-and-pull-Command.html
Not a big fan of the CLI.
Sent from my Nexus 7 (2013)
Your problem (almost certainly) is that you don't have a /sdcard directory (folder) on your computer unless you created one (there certainly is no default /sdcard in a linux desktop system).
I also don't know how you installed ADB on your computer.
(This should work, otherwise I'll have to change what I wrote below).
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
A little extra basic info for you, and welcome to linux. Soon you have the power to take over the world (ha ha ha... no, actually I'm not kidding at all).
As a basic rule, you should pretty much always be working inside of your home directory, for dealing with your personal files. Your home directory is /home/yourname. On my computers, my home is /home/kirk. My wife's home directory is /home/amy.
"~" is a shortcut for the home directory, for whomever is logged in at that moment.
If you wanted something that is on your desktop, it would be in the directory: /home/yourname/Desktop (~/Desktop). If you wanted to use your documents directory, it is : /home/yourname/Documents(~/Documents).
/home/yourname is where you usually where want to do your stuff.
"/" is the very root directory of the whole system, so you would be better off not creating and doing things like making directories like "/sdcard". That's a bad move. Leave root for system files. Not that you are necessarily going to destroy something by creating a /sdcard directory. But it'll cause you a few hassles.
So, use /home/yourname/sdcard (~/sdcard). Or if you want it on your desktop, (like I did above) use /home/yourname/Desktop/sdcard (~/Desktop/sdcard). Doing things inside of /home/yourname(~) means that you are the owner of that folder and everything in it, not root.
Otherwise you will just be causing headaches for yourself and having to grant yourself root permissions to work with those files (hassle). There's no good reason to do that to yourself. And if you did give yourself root permissions, and screwed up other stuff in the root directory like in: /etc or /dev or /bin, then you will REALLY be irritated.
Stick to your home for your personal files. /home/yourname (~)
Leave "/" or the "root" directory for system files.
You could check my little bash program for adb for Linux too. It's a program to be used in the terminal and it'll pull data off the sdcard etc. You can find it here
Sent from my Nexus 4 running Android 4.4
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
smokewagon said:
Thank you all for the help, I'll let you know how it goes.
Do I need drivers for my nexus 4 to work with Linux?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Try it without any installation of drivers just install adb tools and try the command line or my little tool. If it's not working, check the guides how to set up the usb-rules for adb
Sent from my Nexus 4 running Android 4.4
Thanks, will do.
Sent from my Nexus 4 using Tapatalk
iowabeakster said:
Try this:
$ cd ~/Desktop
(This changes you to your desktop directory, if you are not already there)
$ mkdir sdcard
(this will make a new directory called "sdcard" on your desktop, you should see it pop up on your desktop)
$ adb pull /sdcard/ ~/Desktop/sdcard
(should pull the contents of /sdcard from your phone and put them in your newly created directory on your desktop: ~/Desktop/sdcard)
BAM
Click to expand...
Click to collapse
BAM INDEED! It worked! I am pulling the contents now. Thanks a ton, and thanks for the other basic linux info, I will put it to good use.
Any other tips on using Linux to root android?
Shooooot....
So after the pull command finished, i opened the sdcard directory I created on my desktop, and it was empty....the pull command said this when it was done...
1733 files pulled. 0 files skipped.
2129 KB/s (995292697 bytes in 456.480s)
Any ideas?
Ok, I played with some settings and got it to work, though I don't know why it worked.
USB Debugged is enabled.
The first time I tried to 'pull' i had my USB computer connection set to "Camera (PTP)" - it didn't work.
I tried again changing the USB computer connection to "Media device (MTP)" - it didn't work.
I changed it back to "Camera (PTP)" and my computer recognized it in a different way than the first time (a dialog box popped up asking me what I wanted to do with the pictures that were on the device I had connected, this didn't happen the first time).
I am glad the pull command finally worked, I just wish I knew why.
I guess it's a tough road being a linux NOOB and a (near) Android NOOB. It's good to learn something new and keep my brain young.
I got tired of having to jump between a bunch of threads when setting up my Glowlight 3. So I'm consolidating directions into one post in the hopes that it'll save others time and trouble. Credit for instructions should go to the people who actually wrote them: arnchav of mobileread; RyogoNA, Silent eInk, cazar and Renate NST here on xda; and everyone who figured out the root exploit, sideloading, the devs behind Relaunch, RelaunchX and F-Droid. Material lifted from their original posts (linked at the bottom).
Now, this is going to walk you through doing a few things:
A) Setting up a progam called ADB on your computer so that it can talk to your NG3
B) Adding a "Launcher" app to your nook so that you can access other apps you sideload later
C) Root theNook so that you can do more stuff with the settings, including the ability to...
D) Fix a bug that, after installing a launcher, causes the NG3 to get stuck on the loading screen after rebooting
Before you start, you need to set up ADB on your computer. Follow the instructions linked here. The rest of this post will assume you're using Windows, but won't be hugely different from other OSs.
Here we go:
To set up ADB on your nook:
1. On your Nook, go to Settings>About. You should see the serial number, app version, etc. At the top of that page, there is a nook icon. Tap that icon rapidly until the developer menu opens.
2. Tap "Android Development Settings" and check the box for "USB debugging".
3. At the Developer options screen you are on (where you checked the box), hit the back arrow at the top-left of the screen to go back. But do not exit the developer menu.
4. On your computer, open a command prompt and navigate to the folder where you put adb (in my case I typed in "cd adb/platform-tools")
5. Plug the USB in to the nook. When the nook prompts you to turn on USB mode, do so. At the adb command prompt, type adb devices. ADB should recognize the nook, but say that it is unauthorized.
6. From windows, eject the nook to disconnect nook's file sharing. Once the nook's USB file sharing screen goes away, you should be able to see the developer menu again. Tap "Allow Debugging" one time! There will be no confirmation, just do it one time.
6. Unplug the USB, plug it back in, turn on USB mode when prompted. Back in the command prompt, type adb devices again. This time it should see the device and simply say "device" where it used to say "unauthorized". Congratulations! You can now install a launcher.
To install a launcher, like RelaunchX
1. Download your launcher apk of choice. If you don't know what to pick, try RelaunchX, and download the latest version from plusz's thread here: https://www.mobileread.com/forums/showthread.php?t=284418 (n.b. To make things easy, ignore his suggestion to get it through F-Droid as you'll need a new launcher to use F-Droid in the first place. Just download the apk).
2. In Command prompt, type adb install <filelocation>, where filelocation is the complete address of the apk. If you have file explorer open, you can just type adb install then a space, then drag the file in to the terminal and it will copy the location for you. (Make sure again that there is a space between "install" and the path or it won't work).
3. ADB should do it's thing and you will get a "success" message in Terminal.
4. Eject the nook from the PC. Shortly after the connection is cut, a window should open on the nook allowing you to select either the nook launcher or your new launcher. If you use RelaunchX, you may get a warning that it wasn't built with this device in mind. You can ignore it, it works great on this device.
This is all great, except there's a bug in how B&N set up the device that only shows up if you install a new launcher. If you reboot the device, you'll be stuck on the boot animation until you do weird things like hold down the power button for a long time to pull up the reboot/power off options (only seems to sometimes work). To fix that, we actually have to disable, remove, or replace the boot animation file itself.
To root:
1. Download the modified Glowlight Plus script attached here ("rootGL3.zip" - almost identical to cazar's rooGLP-3 script package, but with one line changing the model number from 510 to 520)
1. Enable USB debugging in Developer options
2. Connect USB cable and make sure your nook is showing up in 'adb devices'
3. Extract rootGLP.zip and run rootnook.cmd (or rootnook.sh on linux)
To fix (read: disable) the buggy boot animation:
1. Connect your nook to the computer again
2. (windows) open a command prompt and and navigate to the folder that adb is in.
3. Enter the following commands, in order:
Code:
adb shell
su
mount -o remount, rw /system
mv /system/bin/bootanimation /system/bin/bootanimation.bak
reboot
OPTIONAL: To restore a working boot animation (steps above will replace broken boot animation with a black screen that goes away after a few seconds)
1. Download the attached zip
2. If it's not still connected, connect the Nook to the computer again and tap the button on the nook to turn on USB mode when prompted,
3. On your computer, open up the Nook in Explorer(/Finder/your file manager of choice). Open up the NOOK Folder if you see one.
4. Copy the file inside the zip (bootanimation) to that folder on the Nook.
5. Eject the nook (as in, in windows, click the option to safely remove it as a device) but keep it physically connected
6. Open a command prompt(/terminal/whatever you use for adb) and navigate to the folder that adb is in.
7. Enter the following commands:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
cp /storage/spsd/NOOK/bootanimation /system/bin/bootanimation
cd /system/bin
chmod 755 bootanimation
reboot
You now have a rooted Nook Glowlight 3 that'll boot into a launcher of your choice! You can now sideload apks of your choice using adb the same way you installed RelaunchX.
Have fun!
Sources for these instructions:
https://www.mobileread.com/forums/showpost.php?p=3632665&postcount=118 (how to sideload onto nook 3)
https://forum.xda-developers.com/showpost.php?p=75717722&postcount=113 (same as above, diff user)
https://www.mobileread.com/forums/showthread.php?p=3632665#post3632665 (to get RelaunchX)
https://forum.xda-developers.com/showpost.php?p=64191791 (for nook GLP rooting script)
https://forum.xda-developers.com/showpost.php?p=76042888&postcount=127 (to fix boot animation loop)
HELP! I DID THIS A LONG TIME AGO AND NOW MY NOOK GLOWLIGHT 3 IS STUCK ON THE LOADING SCREEN!
Don't worry, this is fixable. What's happened is that Barnes and Noble pushed out a system update that undid almost everything except that part that breaks the boot animation thing (specifically it overwrites the directory with everything that gives you root access and a working boot animation, but left your custom launcher in place).
All you have to do is re-do most of the steps above. Start from the "to root" step - even if the device is stuck on a boot animation, you should still be able to use adb. After redoing the steps, your GL3 should work normally again.
Unfortunately it looks like this is going to happen every time B&N pushes a system update, but that's not that often.
If someone knows a step-by-step way to replace the stock bootanimation with the 4.6 bootanimation file (zipped up and attached here, thanks to RyogoNA), let me know and I'll update the OP. I tried used adb shell to copy it to /system/bin/bootanimation, but I still just get a black screen on startup in its place.
jptiger said:
I still just get a black screen...
Click to expand...
Click to collapse
Mmm, did the copy of bootanimation work?
Did you:
Code:
/system/bin # chmod 755 bootanimation
Tried that, but I got an error about a Read-only file system, even after using su. What's the basic thing I'm missing?
jptiger said:
Tried that, but I got an error about a Read-only file system, even after using su. What's the basic thing I'm missing?
Click to expand...
Click to collapse
Got a private message pointing me to the command I was missing, apparently from a how-to page in Russian. For anyone else trying to do this, try:
Code:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p5 /system
cd /system/bin
chmod 755 bootanimation
Can't get adb devices to give autorhized access to ng3 w 4.9.2.24 os
First off thank you for doing this work, and I am excited to root my ng3!
In trying to follow your directions on rooting, I am hitting a snag. The os is not operating in the anticipated manner. When I do the usb unplug and replug and hit the usb debugging checkbox I can not get authorization.
Please help!
Thanks in advance!
Trouble with root
Hi,
Thanks for putting this all together. However, I'm having trouble with the root step.
You'll have to put the link together because as a new poster I can't post links.
Any help would be appreciated!
imgur . com
/a
/ckm0jRq
xelcho said:
First off thank you for doing this work, and I am excited to root my ng3!
In trying to follow your directions on rooting, I am hitting a snag. The os is not operating in the anticipated manner. When I do the usb unplug and replug and hit the usb debugging checkbox I can not get authorization.
Please help!
Thanks in advance!
Click to expand...
Click to collapse
Hmm. Did you get authorization after following the directions under "To Set up ADB on your Nook"?
L3R0k2b2 said:
Hi,
Thanks for putting this all together. However, I'm having trouble with the root step.
You'll have to put the link together because as a new poster I can't post links.
Any help would be appreciated!
imgur . com
/a
/ckm0jRq
Click to expand...
Click to collapse
Ooh, that's exotic. I've never seen that before. Just going off the error text, you might need to find a newer version of adb somewhere online. Try that or try a different computer?
Adb is super stable for many years now, although it can fail to connect to your device properly for many reasons.
Can you reach developer menu navigating with nooks keys? I sometimes enable /disable /enable usb Debug, followed or preceded by revoking all PC's permissions. These are all standard options in android phones s system. menus. Rebooting nook may help too, and numerous times I've seen bad cables get in my way. Tip, just because a cable works with one device is not a guarantee it's working everywhere.
RE: STEP 6. "From windows, eject the nook to disconnect nook's file sharing."
Note:
1. The location of the eject menu is where you typically see "Safely remove hardware and eject media" in the windows taskbar.
2. After attempting to eject your Nook GLP, you may get a window that pops up that says "Windows can't stop [your device]" because a process is using it -- and you may not be able to track down which process is using it (for me, closing all windows and apps didn't help). If this is the case, hit "WINDOWS+X >> Shut down or Sign Out >> Sign out" -- then log back in. This *should* stop all processes and allow you to proceed to the next step (it did for me).
*My Nook GLP recently updated and I lost root. This also caused the startup animation to continue non-stop (but holding the power button and then selecting cancel from the options allowed me to select which launcher I wanted to use).
** Additionally, I had one other issue. My (windows) laptop wouldn't recognize my nook at all. Turns out it was the USB cable. So if you have that issue, try using a different USB cable -- preferably the one that came with your nook.
Missing epubs
So I followed the instructions, everything comes up great. I can sideload apps, I have a new launcher etc. But if I copy a file (epub or otherwise) into the NOOK folder on my PC and then browse to the NOOK folder using the file manager on the Nook reader, its empty. At first I thought it was an issue with the file manager, so I installed another one. Same thing.
When I load epubs into the NOOK folder and open the B&N launcher, it sees the books and adds them to my library. But for whatever reason I can not find where the epubs are using a file manager. I even tried using grep to search for the file I copied in adb shell but it doesn't come up with anything. Anyone know whats going on and how to fix it?
Never mind its under /storage/spsd/
mount: Operation not permitted
I get this error after typing in the mount -o ... command.
Any help apprecidated!
root file missing
Hey, @jptiger In the setup instructions the rootgl3.zip file is missing a link now... Does anyone have an active link to this file, or another working root process? I couldnt find one by searching online..
Misssing files
I rebooted my nook recently and it comes back up but when I got /storage/spsd/ its empty. When I attach my nook to my pc, I can see all my books. So I did the following:
Code:
adb shell
su
busybox find / -name "*.epub"
The only files that it shows are the sample epubs that come with the Nook. I am kind of stumped as to how the files show up when I browse the nook as a usb drive. But will not show up when browsing for them via the nook itself or adb. Any thoughts?
Heretic09 said:
I rebooted my nook recently and it comes back up but when I got /storage/spsd/ its empty. When I attach my nook to my pc, I can see all my books. So I did the following:
Code:
adb shell
su
busybox find / -name "*.epub"
The only files that it shows are the sample epubs that come with the Nook. I am kind of stumped as to how the files show up when I browse the nook as a usb drive. But will not show up when browsing for them via the nook itself or adb. Any thoughts?
Click to expand...
Click to collapse
It looks like the flash memory on the Nook maybe going bad. There was a bunch of .chk files in the hidden LOST folder. Reformatting it and copying the books back to the nook seems to have fixed the problem for now. I may have to invest in the Kobo Clara HD in the future.
andjosgra said:
Hey, @jptiger In the setup instructions the rootgl3.zip file is missing a link now... Does anyone have an active link to this file, or another working root process? I couldnt find one by searching online..
Click to expand...
Click to collapse
That's weird. I don't know why they took down the original attachment. I can't find it, but I've gotten the on from the NGP+ and modified it the way they did with the originals. It's attached to this post, give it a shot.
EDIT: I uploaded the version attached here to the OP, but with the original name. The two zips have the same contents.
Heretic09 said:
So I followed the instructions, everything comes up great. I can sideload apps, I have a new launcher etc. But if I copy a file (epub or otherwise) into the NOOK folder on my PC and then browse to the NOOK folder using the file manager on the Nook reader, its empty. At first I thought it was an issue with the file manager, so I installed another one. Same thing.
When I load epubs into the NOOK folder and open the B&N launcher, it sees the books and adds them to my library. But for whatever reason I can not find where the epubs are using a file manager. I even tried using grep to search for the file I copied in adb shell but it doesn't come up with anything. Anyone know whats going on and how to fix it?
Click to expand...
Click to collapse
adb can't access NOOK storage when it's still connected to PC. Eject the device under BNRV520 (should say "NOOK: (F" or similar), but do not disconnect. Then you can find files in both adb and later NOOK's file manager when you disconnect. (should be under /storage/spsd/)
Guide is great though. Thank you all so much! Fast and easy! (unlike making a B&N account)
btw, I had to run "adb shell su" instead of 'adb shell' -> 'su' to get su priviledge, so maybe try that.
what is the adb command to manually launch relaunchx? the launcher option stopped working, and i can't get it to run at all.
Happy to report that the excellent instructions work great on the new 7.8" Glowlight Plus that got released yesterday. Change the model number to BNRV700 in the rootnook.cmd file and you're good to go!