Related
Hi all,
I've recently flashed to MoDaCo 2.2 however I'm just assuming my device got rooted at the same time - but I don't know for sure.
What's the easiest way to verify it has been rooted?
Thanks!
1. use search forum or google..
2. adb shell su
thats it
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Breakthecycle2 said:
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Click to expand...
Click to collapse
Have you enabled USB debugging? Settings-Applications-Development
trice1921 said:
Have you enabled USB debugging? Settings-Applications-Development
Click to expand...
Click to collapse
Yup did that too...my other phones pick it up no issues.
I also get the exact same problem (i.e. Device not found) - I guess it is a hint that it isn't rooted maybe (although I assumed it was automatic with flashing MoDaCo 2.2)?
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
robboy said:
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Click to expand...
Click to collapse
OK I got a work around. You need to restore your PC to a point BEFORE you plug in your hero. I did this and now works great.
How I might undo root process?
I think that replace chmod 4755 permision to default in the "su" file, but I don't know how to
No need to do, but I'm intererested in the concept
There is a thread on how to unroot:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
ZenorGR said:
There is a thread on how to unroot:
Click to expand...
Click to collapse
I'm sorry but could don't find ...Thanks!!!
its a sticky.. its really hard NOT to find it
edit: okay it WAS a sticky, but its also on the first site in this subforum.. so no problem to at least SEE it
Okay, I am getting ready to root my phone tonight...
As far as all that - I think I got all that covered.
As far as flashing a recovery - I want to use amon-ra's - RA-evo-v1.8.0 found here - http://forum.xda-developers.com/showthread.php?t=705026
In that post it gives two differant ways to flash the recovery:
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
via terminal app or adb => Make sure your rom contains flash_image!!
Code:
Copy recovery-RA-evo-v1.8.0.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
My questions are:
first of all - what is "Fastboot"?? I mean is it an application that I can download and install it this way?
second of all - what is a "terminal app"
&
third - what is "adb"?
I keep hearing the term "shell", is a "shell" the same as windows command prompt? Or is that "adb"?
I know these are probably stupid questions for most, but I like to have every thing ready to go before I tackle projects...
Any guidance would be greatly appriciated!!
J
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
terrel_b said:
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
Click to expand...
Click to collapse
Great, thanks for the response! That helps alot - I searched around a little while waiting for a reply and still didnt clear any thing up. I have already DL'd ROM Manager and I will just use that... I just like to have as much info as I can...
Thank you!
J
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
ifly4vamerica said:
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
Click to expand...
Click to collapse
Im using unrevoked... I am still running hboot 0.97.0000... thanks for the input, I appriciate it!!
J
roscoenr said:
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
Click to expand...
Click to collapse
Very helpful info - thanks!! I have already DL'd ROM Manger Pro...
Okay - another question, can i place the amon-ra recovery on the SD card BEFORE i root the phone or should I do that AFTER I root the phone? Just curious, I dont even know if it matters one way or the other... Just want to be sure before I do it...
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
JayStation3 said:
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
Click to expand...
Click to collapse
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
alekosy said:
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
Click to expand...
Click to collapse
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
JayStation3 said:
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
Click to expand...
Click to collapse
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
Everything is there, pretty much solid on the information. I hope it works out for you, if not don't RUSH and take your sweet old time browsing the forums for help. GL
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
cool, I will read them and figure it all out... thanks for the info... i flashed amon ra last night, did a back up w/ TB... did a NAND back up through the recovery of the phone... Im just a little confused on the differant recoveries...
Jbcarrera said:
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I thought I did reboot at least once, when I was preforming the NAND back up - but Im rebooting now and I will test it out again...
I do not have great 4G signal here at my house, so that may be it as well... I will mess with it and see whats up through out the day and let you know tonight...
I have noticed that my touch screen doesnt seem as responsive as it was and the phone in general is kind of glichy...
Ok, my 4G is still working... I must not have had a strong enuf signal at my house for it to kick in... No I'm having problems getting tether to work... I started a new thread on that one though...
Sent from the MATRIX... while plugged into my EVO... using the XDA app... from a galaxy far-far away.......
Okay, many of you complain about USB MASS STORAGE not working with swap enabled. So heres a guide, using CWM (latest version) to set it up with working USB.
NEEDED:
MicroSD (i use class 4 sandisk 8gb)
Root+Busybox
CWM Recovery* (see post 2 for reasons of the *)
Terminal Emulator/ADB
Download this file http://dl.dropbox.com/u/1169731/swap_enabler.sh and place it IN THE ROOT OF YOUR SD!!!
Precautionary:BACKUP EVERYTHING ON MICRO SD CARD.
Steps:
Making the partition
Make sure you have everything backed up, as this WILL wipe your SD.
Boot into clockworkmod recovery.
Go to Advanced->Partition SD Card->EXT and Swap. I chose 128mb for EXT and 256 for SWAP.
Activating Through ADB
Make sure you downloaded that file earlier.
Type this into the CMD:
Code:
adb shell
chmod 755 /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
And reboot
When your phone has rebooted, go back into ADB, and type:
Code:
adb shell
free
and if you didnt not get 0's next to SWAP, it worked.
Activating through Terminal Emulator
Load up Terminal Emulator
Type in this:
Code:
su
chmod 755 /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
reboot. when your phones has booted back up, load terminal emulator once more, and type:
Code:
su
free
and if there isnt a bunch of 0's next to SWAP, it worked
And thats that!
Enjoy
TO DISABLE THROUGH ADB:
adb shell (skip if you're already in adb shell)
sh /mnt/sdcard/swap_enabler.sh disable
Click to expand...
Click to collapse
TO DISABLE THROUGH TERMINAL EMUALTOR
su
sh /mnt/sdcard/swap_enabler.sh disable
Click to expand...
Click to collapse
NEW QUICK EASY WAY (HIT AND MISS)
1) download script manager from the market
2) run swap_enabler.sh with script manager
3) reboot
SPECIAL THANKS TO: Nv for the script, and cimer for the original guide.
also, thanks to cjward for reminding me to put in the thanks ;D
* this guide is for CWM recovery, as the steps for 4EXT may be different. Also, when i tried to do it with 4EXT, it never activated the swap partition correctly.
Man, I've been trying to get this right. Think I messed up because I did not restart after running the script, so when I did the free command I got them zeros.
enserio said:
Man, I've been trying to get this right. Think I messed up because I did not restart after running the script, so when I did the free command I got them zeros.
Click to expand...
Click to collapse
what SD card you have? also, i have noticed it does not work on some roms, but most it does.
I used this method to set swap up to use with virtuous 3.5 and work great for me on my first try. It definately helps out.
Sent from my HTC Vision using xda premium
xT4Z1N4TRx said:
what SD card you have? also, i have noticed it does not work on some roms, but most it does.
Click to expand...
Click to collapse
The 8GB one that came standard with the G2 in the US, Dec 2010. If you need me to take it out and confirm what kind, I will, because this something I want to learn how to do. Also, I tried it with the ILWT Rom. I was trying to get to to work because I wanted to flash that Virtuous 3.5
PS - Anyone have a better method for backing up the SD card besides creating a folder on the desktop and dragging everything in there?
when i type su in terminal emulator I get
"[1] + Stopped (signal)"
I'm now getting a +2 error.
This is mildly frustrating because it seems so easy. I've learned several other processes to do to my phone, and THIS is the one that I get hung up on?
Latest debacle:
I wipe using G2+Superwipe. Make partitions of 128 and 256. Sdcard goes completely blank, so I have to mount it in recovery, and load up a nandroid. I figure, its still all good, go through with it. So I run the commands in Terminal Emulator and get the +2 error. damn damn damn
enserio said:
I'm now getting a +2 error.
This is mildly frustrating because it seems so easy. I've learned several other processes to do to my phone, and THIS is the one that I get hung up on?
Latest debacle:
I wipe using G2+Superwipe. Make partitions of 128 and 256. Sdcard goes completely blank, so I have to mount it in recovery, and load up a nandroid. I figure, its still all good, go through with it. So I run the commands in Terminal Emulator and get the +2 error. damn damn damn
Click to expand...
Click to collapse
Have you tried with ADB?
Sent from my Desire Z running @ 2GHZ
now on terminal emu i get: arith: syntax error: "65 on +2"
I'd try adb but i dont know much about adb
Hi everybody
I was asking myself, before doing it, do I really need it ?
I mean, I'm on Cyanogen Nightly and I've seen it's needed on virtuous (awesome) roms. But on CM, will it change something to activate swap ?
Thanks in advance
xT4Z1N4TRx said:
Have you tried with ADB?
Sent from my Desire Z running @ 2GHZ
Click to expand...
Click to collapse
well, new SDK is giving me problems setting up on my mac. Now you have to use SDK manager, which says to run 'android' file, and when I do it gives me an error just as its about to finish setting up.
Ugh, I want this to happen.
EDIT: got ADB fixed. gonna gee it a go this way.
KeitaroSenpai said:
Hi everybody
I was asking myself, before doing it, do I really need it ?
I mean, I'm on Cyanogen Nightly and I've seen it's needed on virtuous (awesome) roms. But on CM, will it change something to activate swap ?
Thanks in advance
Click to expand...
Click to collapse
This I would also like to know! Thx!
While I can't be 100%, I would say that it wouldn't help you much at all, on any CM based ROMs. Just the ones that are RAM intensive (i.e., sense roms). I know that I only want it to run the Virtuous 3.5 ROM.
Can anyone tell me is there a difference between doing it this way, or just using the app "swapper for root" from the app market..?
Thanks
Thought I would pop in. Doing it via terminal does not normally work you need to do it via ADB. If you're unfamiliar with ADB please go to here: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ and learn about it. It can be such a useful tool. You do not need swap for CM7,MIUI, or Sense 2.1. It can be needed for Sense 3.0 or Sense 3.5 because Sense is such a memory hog at those version levels.
fredcorp6 said:
Can anyone tell me is there a difference between doing it this way, or just using the app "swapper for root" from the app market..?
Thanks
Click to expand...
Click to collapse
Yes, using this way restricts it to one partition, whereas using swapper allows it to use the FAT partition. This means, with this only your swap part will get corrupted over time, whereas with swapper your FAT will, losing your data.
Sent from my Desire Z running @ 2GHZ
Ah ok I see.. cheers
Anyone able to overcome the +2 error? Using Umaro kernal on EliteMod CM7.
Code:
# sh /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
* Some tests.
/mnt/sdcard/swap_enabler.sh: arith: syntax error: "65 on +2"
EDIT:
Probably something not being compatible either busybox or CM7 but I got it to work by doing the following after looking at the code in the swap_enabler.sh file.
Since it was "65 on + 2" I figured that the cut commands weren't being executed properly somewhere and that it should have been 65 + 2 = 67..... =)
in shell i typed swapon /dev/block/vold/179:67
and it worked. Of course I had to manually make an entry in init.d and test it =)....
Maybe this can help OP edit the code.
Nshih422 said:
Anyone able to overcome the +2 error? Using Umaro kernal on EliteMod CM7.
Code:
# sh /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
* Some tests.
/mnt/sdcard/swap_enabler.sh: arith: syntax error: "65 on +2"
EDIT:
Probably something not being compatible either busybox or CM7 but I got it to work by doing the following after looking at the code in the swap_enabler.sh file.
Since it was "65 on + 2" I figured that the cut commands weren't being executed properly somewhere and that it should have been 65 + 2 = 67..... =)
in shell i typed swapon /dev/block/vold/179:67
and it worked. Of course I had to manually make an entry in init.d and test it =)....
Maybe this can help OP edit the code.
Click to expand...
Click to collapse
Why do you want to use swap on cm7. There are zero benefits. But there are disadvantages, it could affect battery life, performance and wear your sdcard out faster
Sent from my HTC Vision using Tapatalk
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
threepio said:
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
Click to expand...
Click to collapse
You can adb pull the dcim folder to your PC.
Edit: You would also be better served in the long run learning to return to stock yourself instead of using a toolkit.
http://forum.xda-developers.com/showthread.php?t=1626895
JM2C
3rdstring said:
You can adb pull the dcim folder to your PC.
Edit: You would also be better served in the long run learning to return to stock yourself instead of using a toolkit.
http://forum.xda-developers.com/showthread.php?t=1626895
JM2C
Click to expand...
Click to collapse
Thanks JM2C. I thought that I might be able to do the ADB pull. I have no idea how ADB works though...
Thanks for the link on the
It's not too complicated. It is a lot of steps but a developer novice can follow the instructions to install and use adb just to pull a few files. Also that's one reason why I let dropbox sync my photos as I take them, so if something happens I have an auto cloud backup.
Sent from my Galaxy Nexus using xda premium
---------- Post added at 05:56 PM ---------- Previous post was at 05:51 PM ----------
threepio said:
So I think I am SOL, but I wanted to ask you guys first.
My Nexus wont boot past the Google screen all of a sudden today. So I am going to attempt the toolkit version of returning to stock later. But before I do that, I want to try and salvage my pictures from the internal memory.
Is there a way to mount the internal storage to my PC so I can pull the files off?
I thought not having an SD card was no big deal, til now when im about to lose 500+ pictures.
Am I screwed?
Thanks
Click to expand...
Click to collapse
Here is a link to some basic adb instructions:
http://forum.xda-developers.com/showthread.php?t=517874
exportsmedia said:
It's not too complicated. It is a lot of steps but a developer novice can follow the instructions to install and use adb just to pull a few files. Also that's one reason why I let dropbox sync my photos as I take them, so if something happens I have an auto cloud backup.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So I found a tutorial for setting up ADB for the nexus, but all i can get into is the bootloader and the recovery. I cant get my computer to recognize my phone...even though its plugged in. So how would ADB work?
threepio said:
So I found a tutorial for setting up ADB for the nexus, but all i can get into is the bootloader and the recovery. I cant get my computer to recognize my phone...even though its plugged in. So how would ADB work?
Click to expand...
Click to collapse
If you have a custom recovery you should be able to get adb access. You just need to set up the drivers
I believe the previous link I gave even has a small platform-tools download so you wouldn't have to set up the sdk.
3rdstring said:
If you have a custom recovery you should be able to get adb access. You just need to set up the drivers
I believe the previous link I gave even has a small platform-tools download so you wouldn't have to set up the sdk.
Click to expand...
Click to collapse
So when i go into device manager I have Android 1.0 listed under other devices. But when i try to have windows search for drivers, it doesnt find anything. Is ther a specific driver from samsung that I can download somewhere and then point the driver update to it?
threepio said:
So when i go into device manager I have Android 1.0 listed under other devices. But when i try to have windows search for drivers, it doesnt find anything. Is ther a specific driver from samsung that I can download somewhere and then point the driver update to it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
3rdstring said:
http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
Ok that worked I now have the android bootloader interface in my device manager....now what? When I open cmd and type "adb devices" nothing comes up
threepio said:
Ok that worked I now have the android bootloader interface in my device manager....now what? When I open cmd and type "adb devices" nothing comes up
Click to expand...
Click to collapse
Boot into recovery (You do have a custom recovery installed?)
3rdstring said:
Boot into recovery (You do have a custom recovery installed?)
Click to expand...
Click to collapse
I have Clockwork mod installed. and still when i try adb devices nothing comes up.
So I got something to work. When I typed adb devices under "list of adb devices attached" i got 0146A5B1301C007 recovery
Is this my phone?
threepio said:
So I got something to work. When I typed adb devices under "list of adb devices attached" i got 0146A5B1301C007 recovery
Is this my phone?
Click to expand...
Click to collapse
yes
now im trying to get the command right.
what is the whole string for adb pull?
*edit*
I found that is---> adb pull <remote> <local>
So I type " adb pull /sdcard/dcim c:\nexus
(i made a file on the root of my c: drive to make it easy to type to pull the files.
but it says /sdcard/dcim does not exist.
threepio said:
now im trying to get the command right.
what is the whole string for adb pull?
Click to expand...
Click to collapse
I've pushed a ROM a few times, never pulled. I would try...
adb pull /sdcard/DCIM c:\
or
adb pull /data/media/DCIM c:\
threepio said:
now im trying to get the command right.
what is the whole string for adb pull?
*edit*
I found that is---> adb pull <remote> <local>
So I type " adb pull /sdcard/dcim c:\nexus
(i made a file on the root of my c: drive to make it easy to type to pull the files.
but it says /sdcard/dcim does not exist.
Click to expand...
Click to collapse
MOTHER EFFING CAPTALIZATIONS! GOT IT WOOOOO pulling all my files as we speak. I wasnt typing the directories with captial letters like they are. I was typing all lowercase. gosh dangit!
THANK YOU THANK YOU THANK YOU
threepio said:
MOTHER EFFING CAPTALIZATIONS! GOT IT WOOOOO pulling all my files as we speak. I wasnt typing the directories with captial letters like they are. I was typing all lowercase. gosh dangit!
THANK YOU THANK YOU THANK YOU
Click to expand...
Click to collapse
Glad you got it working. As was mentioned previously DropBox photo syncing can be a lifesaver. :good:
3rdstring said:
Glad you got it working. As was mentioned previously DropBox photo syncing can be a lifesaver. :good:
Click to expand...
Click to collapse
You know i just got into dropbox. I am going to start using it more.
Now i gotta figure out how to restore the phone. Now that I have the pictures off it, i can toy with resetting it to stock. and starting from the ground up.....fun...
Now I just flashed back to stock using the fastboot from the link posted on page one.
Thanks for your help guys
threepio said:
Thanks JM2C. I thought that I might be able to do the ADB pull. I have no idea how ADB works though...
Thanks for the link on the
Click to expand...
Click to collapse
qbking77 has a great YouTube video walking you thru it. Also has how to return to stock/unbrick
*This Jedi master be a Ninj-ESS*
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Veid71 said:
Did you try it? You can try something simple like swapping boot slots in the twrp terminal emulator
Click to expand...
Click to collapse
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
Nope, haven't tried it. Not sure if I need any files on the phone for it to work?
Click to expand...
Click to collapse
I'm not sure either but i can't imagine it'll hurt to try a reboot command or to swap slots
How can this even work? ADB only works when the phone is in fastboot mode, which automatically means that Android isn't even running surely? Hence you can't run apps.
Sent from my Pixel XL using XDA-Developers Legacy app
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
NO
With two phones and adb over network you can send a command to another phone using Tasker (maybe other apps too, only ever used it while looking for an answer to your same question). I know I at least sent reboot from one phone to another... But I think fastboot won't work like this, only (simple) adb shell commands - I'm pretty sure I gave up on it once I realized that I think it is not possible to change boot slots using this method....
Other than that, FlashFire can be used I a rooted phone to change boot slot - wipe dalvik and reboot to other boot slot. I don't know a way on a non rooted phone - anyone know a way without using pc and fastboot?
GroovinChip said:
For example, via a terminal emulator or simply an app that will execute ADB and Fastboot commands?
Click to expand...
Click to collapse
For fastboot and adb in recovery, you'll need the phone connected to to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely, but you won't be able to see the phone's screen.
For adb in normal boot, you can either use "adb over network" (LAN) (if WAN, you'll need to bypass firewall if any) or connect your phone to a computer (or device) via usb that you have access (local/remote) to in order to issue commands remotely. You can see the phone's screen using tools such as AirDroid or TeamViewer.