Related
Ok, I have a T-Mobile locked and branded Desire and so trying to create a Goldcard but it just gives me Permission Denied when trying to get the CID, what am I doing wrong? I have followed the steps to the T
try the goldcard program?
YES!! Please seriously need help aswell with this. Have a sim free desire and I get to the line of code in the command prompt with
"ADB shell cat/sys/class/mmc_host/mmc1/mmc1:*/CID" and it just says device not found.
I am new to android so i'm pretty clueless with this. Any help would be greatly appreciated.
Kleptomaniac said:
... and it just says device not found.
I am new to android so i'm pretty clueless with this.
Click to expand...
Click to collapse
So about 'device not found'. I had this 'issue' when rooting mine a few weeks ago, so here's what I had to do.
When rooting, you're gonna be using the ADB tools to interface with your phone through USB. This would mean that the computer needs specific drivers for ADB to work properly, which for some reason, did not install well. I'm running Win7 x64 and had a hard time setting it up initially.
SO what you want to do is to first go to Device Manager on the PC and uninstall the drivers for anything related to the phone - it'd probably show up under 'Other devices' with a driver issue. Do that and unplug the phone.
Next, go to install PdaNet. Just run the exe and it will install the drivers you need for ADB to work! Once this is all done you can uninstall the PdaNet program if you don't use it - the drivers will still remain.
When you plug in your phone (it might prompt during the installation, I don't remember) and head to device manager now, you'll see a new entry at the top called Android Phone, with a device called Android ADB Interface. Once you see this, then you're good to go with the rest of the goldcard instructions you were following.
Just to be sure, reboot the PC and go to the Android SDK\Tools in a cmd prompt and type in adb devices. It should return with the serial number of your phone.
That's it, hope it helps!
Thanks alot man its nice to know people here are willing to help. I didn get the drivers but I used HTC sync instead to get them up and running, then after awhile of it still not working I found the goldcard program and it worked! Now all I have to do is wait for this root download to finish...
Hi guys,
I'm no stranger to rooting and installing ROMs, but doing so with ADB is completely new to me. I just got a G2 at the beginning of January, upgrading from a G1.
I spent about two hours trying to get the Android SDK and ADB working properly on my computer. Now ADB can see my phone, but when I try to do the first part of the temp root process from the wiki:
$ adb push su /sdcard/su
I get a permission denied error. I'm not supposed to be getting this, right? The gfree_temp-root.zip files are extracted to the folder where ADB is, and I can see in the prompt that ADB is trying to work, but I always get this error, and I don't want to continue until I know what's supposed to be happening. USB debugging is enabled and the terminal emulator app is installed. The sd card is mounted by the phone, not the computer. I still have 7+ GB left on the sd card.
$ adb push Superuser.apk /sdcard/Superuser.apk
gives me permission denied, too.
I've never installed Visionary or any other temp root app. The closest solution to this problem I saw was in response to a guy who had installed Visionary before, and so didn't need to worry about having superuser permissions. The only reason I could find that this might not work is because of stuff about rolling back OTA updates.
Thanks for any responses. Let me know if you need any more info.
I just used this method last night. Make sure you have USB debugging on first of all and make sure you don't have the "USB connected" option ticked when it prompts you. You want that off.
I had the permission denied too but when I turned off the USB Connection that mounts my sd card, I got it to work. Good luck!
The weird part is he specifically says he checked those things (USB debugging enabled and the SD card not mounted to the computer). Not sure why he'd be getting a permission denied (reading/writing from the SD card should not have any problems).
What OS are you running ADB on? And maybe this is a silly question but you are running the commands from your computer and not the terminal on your phone, right?
LGS1231 said:
I just used this method last night. Make sure you have USB debugging on first of all and make sure you don't have the "USB connected" option ticked when it prompts you. You want that off.
I had the permission denied too but when I turned off the USB Connection that mounts my sd card, I got it to work. Good luck!
Click to expand...
Click to collapse
That did it! Thanks, I am now perm-rooted and ready to overclock.
ianmcquinn said:
The weird part is he specifically says he checked those things (USB debugging enabled and the SD card not mounted to the computer). Not sure why he'd be getting a permission denied (reading/writing from the SD card should not have any problems).
What OS are you running ADB on? And maybe this is a silly question but you are running the commands from your computer and not the terminal on your phone, right?
Click to expand...
Click to collapse
I think I misspoke (typed?); when I said it was mounted by the phone, I meant I had selected to turn USB storage on with the phone. I thought I remembered seeing a way to do it through the computer, but I'm probably wrong. Either way, turning USB storage off fixed it, and now that I think about it, I understand why I would be getting permission denied. I guess I didn't fully understand what the wiki meant by "Make sure your phone's sdcard is mounted by your phone and not your computer when following these instructions."
For the record I'm using Windows 7 Professional, and installing ADB was a project in and of itself. Don't know if anyone else had problems with it.
Thanks for your help everyone. This is a great forum.
Great! Glad to be joined by another newly rooted user! CM7 Gingervillain is a great ROM, and I recommend you flash that. It already has an OC kernal built in so it's less work. All you would have to do is flash CM7 and then get SetCPU.
I love being rooted!
Edit: nevermind, I saw there was a superuser permission pop-up on my phone that I wasn't seeing before.
LGS1231 said:
Great! Glad to be joined by another newly rooted user! CM7 Gingervillain is a great ROM, and I recommend you flash that. It already has an OC kernal built in so it's less work. All you would have to do is flash CM7 and then get SetCPU.
I love being rooted!
Click to expand...
Click to collapse
Do the nightly builds have 4G working yet? It's not a huge deal because I use wifi at home, but it would be nice to keep 4G on there.
Hey all,
My Incredible won't be recognized by ADB on my Mac through the terminal. I type in "adb devices" and it returns "List of connected devices" but doesn't actually list anything. If I try something like "adb shell" it says "error: no devices connected". What could the issue be?? I have a PC as well and ADB works fine on the PC.
If it helps at all the phone is recognized through fastboot on my Mac but I can't perform any operations... I tried to flash a new recovery through fastboot and when I tried to do "fastboot erase recovery" it returned something like "erase recovery failed status malformed"...
Thanks!
debug turned on? Thought that it needed to be adb
Yeah debug is on.... also in case it didn't go without saying I'm rooted.
Hope someone can help with this!
Sent from my ADR6300 using XDA Premium App
Anyone have any ideas on this one?
Go here and follow steps for your system.....
http://androidsamurai.com/forum/viewtopic.php?f=12&t=4&sid=e1f4ce4f9ba69613dca7ba5db4a711a2
if I helped please don't hesitate to hit the thanks button
Sent from my Incredible using XDA App
Thanks for the advice, but I had already followed those directions when installing the SDK. As I said, the phone is recognized just fine on a Windows machine so I can only assume it's some setting that's perhaps incorrect on my Mac? Maybe in System Prefs?
I dunno. It isn't the biggest deal but it'd be nice to be able to use the ADB on my Mac without needing to boot up the PC. Thanks!
nufan947 said:
Thanks for the advice, but I had already followed those directions when installing the SDK. As I said, the phone is recognized just fine on a Windows machine so I can only assume it's some setting that's perhaps incorrect on my Mac? Maybe in System Prefs?
I dunno. It isn't the biggest deal but it'd be nice to be able to use the ADB on my Mac without needing to boot up the PC. Thanks!
Click to expand...
Click to collapse
Are you positive your path is correct..... and if it is check and make sure there are no spaces or weird characters....
Sent from my Incredible using XDA App
was it working before and it stopped working? I noticed that my Mac doesn't recognized the phone every once in a while with CM7 and the Incredikernel. I have to unplug it and plug it back in couple times to get it to register.
newtoroot said:
Are you positive your path is correct..... and if it is check and make sure there are no spaces or weird characters....
Click to expand...
Click to collapse
I'm pretty sure it's correct because the Terminal recognizes the "adb" commands as valid. For example, I can run "adb shell" and it returns "error:device not found". So I don't think that's the issue...
Grooby97 said:
was it working before and it stopped working? I noticed that my Mac doesn't recognized the phone every once in a while with CM7 and the Incredikernel. I have to unplug it and plug it back in couple times to get it to register.
Click to expand...
Click to collapse
The thing is, the computer recognizes the phone just fine. I can plug it in and select "disk drive" and both the phone and SD card mount without an problem. But when I try to run adb commands that's when it doesn't seem to see it for some reason.... I really don't get why this could be, when without changing a single setting on the phone it works fine on a PC. I'm probably missing something obvious, but I don't know what that might be.....
nufan947 said:
I'm pretty sure it's correct because the Terminal recognizes the "adb" commands as valid. For example, I can run "adb shell" and it returns "error:device not found". So I don't think that's the issue...
The thing is, the computer recognizes the phone just fine. I can plug it in and select "disk drive" and both the phone and SD card mount without an problem. But when I try to run adb commands that's when it doesn't seem to see it for some reason.... I really don't get why this could be, when without changing a single setting on the phone it works fine on a PC. I'm probably missing something obvious, but I don't know what that might be.....
Click to expand...
Click to collapse
forgive me if im asking a dumb question im just trying to help you narrow down your problem,,,,,, did you check and make sure usb debugging is checked? and if you type adb devices what does it say? ive noticed on the newer sdk that i installed they moved adb to platform tools and out of tools so you might check those things
Yeah, USB debugging is checked... when I type "adb devices" I get "List of devices attached" and it doesn't actually list anything. And yeah, the Terminal is definitely pointing to the right folder, I don't think I'd be getting any sort of response if it was pointing towards the wrong place, right?
ADB definitely works. It just doesn't like my phone for some reason
Well it definitely works on OS X 10.6 that's what my laptop uses. Have you tried parallels or bootcamping into a version of Windows? My work iMac is a piece of dirt and does not like adb thru mac os x but works fine with win xp on parallels.
Yeah, I'm running 10.6 on my laptop as well... right now for when I want to use ADB I've just been running XP on my bootcamp partition, which works fine. It's not the worst solution in the world, but I'd prefer being able to do it on the Mac side of things, which is where I spend far more time.
This is very mysterious....
Sorry, i know you must get this all the time guys, but i'm really struggling with rooting and such.
I'm on 1.72 and have no idea how to downgrade. I know you might say "read the guide" blah blah, but i don't understand it "Moron" i hear you saying. Anyway, Is there a complete noob guide for it anywhere? Like literally one that talks you through every step?
Also, my screen cracked, so i opened it up and replaced the screen myself, didn't have insurance or the £170 to have them fix it. Before the screen cracked it was doing this thing where it looked all psychedelic, Whites have blue coming off them, blacks have reds coming off them, that kind of thing. and its doing it again. This made me think it was a software issue, it happen to anybody else? I was thinking if i put a different rom on it, it'd stop, but i dunno. Anyway, thanks for any help anyone gives.
Does the screen replacement involve the flat ribbon cable between the screen part of the phone and the keyboard? I'm thinking it doesn't, but I'm certainly no expert. A damaged ribbon cable can cause colors to display improperly.
Nah, its attached to the screen so it was a new one.
The screen only comes with a small ribbon cable that connects to the pcb in the front half of the phone.
There is a larger ribbon cable that connects the two halves of the phone together, you can see it if you hold the phone halfway between open and closed. If this cable gets damaged, which happens easier than you may think then it can causes all sorts of things to mess up, including the colours on your display.
Unfortunately this cable is attached to the screen pcb so needs to be replaced as one unit.
So i'd need to replace my main pcb? Damn. Thanks for the help though! Could anyone help me with rooting?!
Sent from my HTC Vision using XDA App
at which point are you getting lost? sussed downgrading yet?
emdaftrave;14529179.Could anyone help me with rooting?! :D
.
Sent from my HTC Vision using XDA App[/QUOTE said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
Just have a search and there are numerous step by step guides, I was a total amateur and managed to do it, I think the hardest part to try learn would be using ABD (command prompt) and how to navigate to directories and push files but there are numerous guides on this forum so just pick your simplest and go for it!
elliott2705 said:
at which point are you getting lost? sussed downgrading yet?
Click to expand...
Click to collapse
Pretty much trying to install the sdk, i think im gonna reinstall it because its being a bit dodgy for me. But thanks for all the help guys!
Sent from my HTC Vision using XDA App
silverwind said:
Man, trust me.. It took only 30 minutes for me to root my dz
But, the preparation ( search and search) took 2 weeks
But it worths trying
The main keys are to instal ADB things (sdk android ) and create a gold card. Once you understand how to do that, you already half way.
The links are in the wiki
Cheers
Click to expand...
Click to collapse
can you use the SD card already in there as a gold card, or do you need a separate one?
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
emdaftrave said:
Ok so i have an actual problem now, not just not understanding the guides xD
On the Cyanogenmod wiki guide of how to install ADB, a couple of the steps are:
On success, open the command prompt on the computer, and type in the following command to sure everything is setup properly:
Code:
adb devices
If it lists any devices, everything is fine and you are finished. If not, the drivers may not be installed correctly, please continue.
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Well i did just that, and it doesnt say unknown device anywhere, and yet when i type adb devices in command prompt, it says 'adb' is not recognized as an internal or external command, operable program or batch file. Anybody know what gives?
Click to expand...
Click to collapse
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
pmcqueen said:
you either need to cd to the folder within your android sdk that adb is in (I think it's platform-tools), or add the android sdk path to your environment variables (google this, it's easy to do).
open up your command prompt and type:
cd C:\path-to-android-sdk\platform-tools
adb devices
if you don't add the path to your android sdk in the environment variables, you'll have to cd to the folder with adb every time you need to use it... not a big deal if you're not using adb a lot, but it gets annoying if you're opening up a command prompt to push/pull/shell regularly.
Click to expand...
Click to collapse
ok, i've done it, thank you very much! now to just downgrade and root!
Ok so i'm using the XDA wiki guide on rooting, and i've got to the part where you move all the files onto the phone. Specifically, the files that aren't moving are:
$ adb push flash_image /data/local/tmp/
$ adb push su /sdcard/,
I'm getting a "Permission denied" error in command prompt. I also don't have an /sdcard directory on my phone, maybe thats why i'm getting an error?
EDIT: Never mind, i had the phone in Disk Drive mode when it wasn't supposed to be. Sorry for the double post.
Hi, great site you have here. I dropped my GS3 and broke the digitizer. The phone turns on, but has a blank screen. Of course I didnt back anything up to google or save my contacts to my sim. I tried using kies with my laptop and connected my phone, but it says my phone is locked. I enabled a swipe pattern on the phone before i broke it, but I cannot unlock it since the digitizer is not working. Is there anything I can do to disable it? Also, Samsung is quoting me about $175 ($65 for the digitizer, $100 for labor/shipping) to fix the phone, however they wipe then entire thing and of course all my contacts, pictures, music, apps and everything will be gone. If I cant get kies to work because the phone is locked, can you recommend a good place to purchase the digitizer? Is it difficult to install yourself? Thanks for all the help
You can use the "adb pull" command to pull any files/folders off your sd-card even with the screen lock (I've tested this). Install the android SDK and adb can be found in the platform-tools folder. Simply use the windows command prompt to pull the needed folders out. Sorry for your misfortune hope that helps.
illmatic24 said:
You can use the "adb pull" command to pull any files/folders off your sd-card even with the screen lock (I've tested this). Install the android SDK and adb can be found in the platform-tools folder. Simply use the windows command prompt to pull the needed folders out. Sorry for your misfortune hope that helps.
Click to expand...
Click to collapse
Thank you for the help. I will try and you tube how to do what you told me, as I know next to nothing about using computers in this way lol
xxH3llsp4wNxx said:
Thank you for the help. I will try and you tube how to do what you told me, as I know next to nothing about using computers in this way lol
Click to expand...
Click to collapse
No problem! Good luck, there are tons of videos/tutorials on how to set up the SDK. Just make sure to install the right drivers or else your device won't show up in ADB.
Just to simplify it a bit, I figured it might save you some time.
1. SDK installer file:
http://developer.android.com/sdk/index.html
2. Once you've got the SDK installed and configured open up "Command Prompt" (if on windows) (have your device on and at the lock-screen).
3. In command prompt, navigate to "sdk/platform-tools/" (or wherever you chose to install the SDK, just make sure to navigate to the platform-tools directory as that's where adb is located) (use cd command)
4. Next, type "adb devices" into command prompt to make sure your device shows up (it might be named something weird, don't worry)
5. Now, type "adb pull /sdcard/*FOLDERTOCOPY* (if you don't remember the names of the folders you can dump the entire sdcard)
This will dump your sd-card files to the "sdk/platform-tools/" directory.
Cheers.
wow, thanks for the time to write that out for me, it is greatly appreciated. I will try this out when i get home from work.
Wont identify my phone
Hello! It seems that I have the same problem. I have followed your directions. However, when I type "adb devices" the next line is blank. I do not think that it see's my phone. I have a Galaxy S3 on Verizon. I am running Windows 8. I have attached the phone through it's USB and the computer sees the phone.
Am I missing something?
Thank you
Hi. Most probably it is due to adb drivers not being installed. Download the galaxy s3 toolkit, and install the android drivers from within.
Toolkit:
http://forum.xda-developers.com/showthread.php?t=1746665
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have just posted this thread to another topic of whom the user may encounter a similar contacts lost situation.
Hope that would help him
I recently had to pull files from a gnote2 with a broken screen. With the lock enabled you won't have access to the files via adb unless you have a custom recovery installed. What I did was enter download mode and then Odin an insecure boot loader. After that I was able to use adb to pull the files.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
illmatic24 said:
No problem! Good luck, there are tons of videos/tutorials on how to set up the SDK. Just make sure to install the right drivers or else your device won't show up in ADB.
Just to simplify it a bit, I figured it might save you some time.
1. SDK installer file:
http://developer.android.com/sdk/index.html
2. Once you've got the SDK installed and configured open up "Command Prompt" (if on windows) (have your device on and at the lock-screen).
3. In command prompt, navigate to "sdk/platform-tools/" (or wherever you chose to install the SDK, just make sure to navigate to the platform-tools directory as that's where adb is located) (use cd command)
4. Next, type "adb devices" into command prompt to make sure your device shows up (it might be named something weird, don't worry)
5. Now, type "adb pull /sdcard/*FOLDERTOCOPY* (if you don't remember the names of the folders you can dump the entire sdcard)
This will dump your sd-card files to the "sdk/platform-tools/" directory.
Cheers.
Click to expand...
Click to collapse
Thanks for this, I've just recovered data from a Galaxy S2 using this. I was able to activate USB debugging using blind touches, based on a video, and recovered the sdcard using
Code:
adb pull /sdcard/ MYFOLDER
Yea what people seam to forget is that adb only works if it was enabled on the device before hand....
Sent from my ATT Samsung Galaxy SIII using TapaTalk
broken screen with screen lock on, trying to use Kies as a tempory remote terminal
Hi all,
I have the Galaxy S3 SGH-I747, and this morning I managed to break the LCD. The digitizer isn't cracked, but seems to be unresponsive.. I'm not with any of the major carriers, I have GCI in Alaska. I'm on the road, away from home, working. I should be able to get a new case when I get home. Which will be in only 4 days, luckily.
I was also hoping I could use Kies essentially as a remote terminal to send SMS or make calls just until I can get home and replace the case. (Which in my mind is actually an easier quicker repair than the screen digitizer replacement, just not always quite as cheap.)
I have ADB, I'm just not an expert with it. Is there a way to use it to disable to lock screen, even temporarily, so I can use the GUI in Kies? Is there any was to turn on the Bluetooth perhaps? I already have the partnership established with my Laptop, and is set up to connect without confirmation. I might be able to figure out a way to get some sort of functionality out of it until I can get it repaired.
Yea what people seam to forget is that adb only works if it was enabled on the device before hand..
Click to expand...
Click to collapse
I don't think I have connected this phone with the ADB yet. I also didn't have the USB debugging mode enabled. Am I SOL getting it connected with the ADB, then?
Hi illmatic24. I need a help - I have a Samsung E7 - broken lcd, forgot the password and usb debugging mode is off. Is there anyway through which I can recover my phone's content? I want access to my internal storage memory. Any help will be much appreciated. Thanks, Ritz