Hey, so I was trying to enable non-market apps through ADB. Everything was going good until I typed in "adb reboot" and then stupidly unplugged the cable.
Now the phone doesn't do anything, can't boot Android, only the recovery menu. It just shows the intro movie and then shuts down. I've tried deleting user data and clearing cache from recovery which doesn't help.
I do have a NANDROID backup for it, both on the phone and on my PC (which was made with Clockworkmod Recovery). But the problem is that I don't have the update.zip for Clockwork on the /sdcard, it's in /titaniumbackup. How can I put the update.zip on the /sdcard of a bricked Captivate?
when you boot in recovery, does ur computer recognize the device if connected with usb? If so you can use adb to relocate files, droid explorer may even work.
Oh thanks, I had no idea ADB would work in recovery, gonna try that and get back to you.
As you can see I'm still new to Android. Dumped iPhone 3G for Captivate. But I'm learning!
So Droid Explorer won't install because it doesn't like 64bit Windows.
ADB can connect, but I can't put any file on the device (I've tried the "adb push" command) or gain root, says permission denied. Please help!
EDIT: Never mind, by some miracle of God it all worked out and let me adb push all I needed, I'm in Clockwork Recovery and my phone is gonna be OK.
i have droid explorer running on my intel, windows 7 ultim 64x rig. works.
you just have to make sure you dl the 64 bit version of the program. Here's a link:
http://de.codeplex.com/releases/49896/download/139717
you also need .net framework 3.5 sp1 at least. I installed the newest one and it works regardless.
im glad you managed to unbrick your device. Kudos.
Related
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
bump. i also need this. btw have you tried using a script to do it?
danboard said:
It seems as though a lot of people have had this problem for other phones but I haven't been able to find a solution to it (forgive me if its somewhere very obvious ).
After editing my framework-res.apk I am trying to push it back into my milestone through the SDK so I have tried to get my phone to show up while in recovery mode so I can push it back on.
The problem is that while in recovery my phone won't appear under "adb devices" I have tried using GOT's recovery and also the regular Openrecovery v1.37
Thanks
Click to expand...
Click to collapse
Did you read this thread?
http://forum.xda-developers.com/showthread.php?t=698059
and especially did you install this driver?
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=bda09ec8009a0210VgnVCM1000008806b00aRCRD
I do have read the thread and I have installed that driver. While in recovery mode using GOT's or OpenRecovery I notice that under device manager it says my phone is listed as "Android Phone" and if my phone is on and I connect it to my computer with USB debugging it lists it as "ADB interface". I can't get the phone to appear under adb devices while in recovery mode.
USB-Debugging active? (Settings-->Development)
It is when the phone is on, but what I am trying to do is push a file to the phone while its "off" in recovery mode so the usb debugging is irrelevant or so i believe.
Yes, sorry, you are right.
As I can remember, I have had a similar problem a year ago...
Try to copy adb into another directory and use it from there. Sounds stupid, but helped me in the past.
Sent from my Milestone using XDA App
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
danboard said:
I just tried changing my directory for the sdk but doesn't seem to help. Just to make sure is there anything i need to do once inside the OpenRecovery? After loading up the update.zip i connect it to my PC and in cmd I navigate to the SDK folder. So far thats all I m doing and checking its connected with "adb devices" which always comes up empty. Just want to make sure I m not missing any steps considering I have the usb drivers installed and the sdk SHOULD be installed correctly since i can access them when the phone is on.
Click to expand...
Click to collapse
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
micdim said:
I have the same problem as you described. Is it solved?
I am using windows 7 and the driver is also installed correctly. only problem is the empty device list..
Click to expand...
Click to collapse
Seems OK now. I just reinstalled official SDK.
dl.google.com/android/installer_r08-windows.exe
Okay here is the thing, I am a bit of an advanced user, and have been flashing ROM's for quite a while, so i am not a noob and I have already tried everything in the book to fix my problem.
Info:
1- Drivers installed on Windows 7 and have been working for the past 4 months.
2- USB Debugging ticked
3- Windows recognizes the Galaxy Tab 7" GSM (P1000 International)
Problem:
1-Running "adb shell" in adb results in: error: device not found
2-CWM Restore stops at android_secure.img not found and aborts.
How did it happen (Detailed):
1- Was on Overcome 2.0.1 "Hermes" and found out that there was an update on kies from someone.
2- Decided to restock
3- Flashed P1000JPJM5 (I already did that quite a few times and no problems ever occurred from that)
4- When i restocked i wanted to root, so i went into settings>Application>developement> and ticked USB Debugging
5- Plugged in USB and I opened up Super One Click Root v1.7 and hit Root, however, Nothing happened and it was "Waiting for device" forever.
6- tried Super One Click root v1.9 with the same result
7- Opened adb and typed "adb shell" and got error: device not found.
8- I downloaded Better Terminal app from the market and tried "adb shell" and i got "Adb not found" as a result
9- I wanted to root my device to use the Bootloader Batch and change my protected boot loaders
10- tried everything, Restore factory from 3e Recovery, Doing the same from Setting>Privecy, Flashing the same ROM Over and Over again with no luck
11- learned later that flashing ChainFire's Gingerbread P1000XXJMQ is safe on protected boot Loaders so i did that
12- the problem persisted and i just cant use adb
13- I had a CWM Backup done so i thought doing a restore might solve the problem, but that resulted in a failure in restore. it stops at android_secure.img not found and aborts restore.
If anyone kow's a solution or at least knows what might have gone wrong Please shed some light on how to go about this issue.
Thanks
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
pwolfamv said:
While the device is plugged in, go to device manager and delete/uninstall the device. Should ask you if you want to delete the driver files also, check the box and go.
After that it will probably ask you to restart, restart the computer and reinstall the device with the google drivers.
Click to expand...
Click to collapse
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
DistortedWisdom said:
well its like i said earlier it is NOT a driver issue.
I mean even Emulater apps from within the Tab are not recognizing ADB
Click to expand...
Click to collapse
Did you at least try what I suggested?
I can't get my galaxy tab to be seen by adb either. At least not since upgrading to Gingerbread.
I'm using the
"sprint_p100_Samung_GALAXY_Tab_USB_Drivers.msi" file from the Samsung web site.
hello and pardon by the English because I am translating.
I have a HTC S and I wanted one 2 days ago I put a ROM nandroip and everything but I realized and I wipe the entire phone erasing all the ROM and everything I had.
the problem is I can not install a ROM on my phone now because every time I try from windows CMD when you start the installation makes me daemon not running, and sends me error: device not found.
I've tried with another tutorial that you have with the application all in one kit but also not let me access this sd every time I try to enter telling me insert disk into drive E: \.
I can do?
I think it may be by the drivers of PC but not sure I instadao have 5 or 6 drivers and nothing.
an administrator's name is called android MYHTC ADB and other android or something.
I am desperate thank you very much took 2 days doing everything.
thank you very much.
my windows is XP.
Ok, Sorry but im having difficult understanding everything you say, But i think i got the basics.
I would suggest you re download the drivers, Remove HTC Sync if you have it. Move all of your ADB files in to 1 folder so its easier to navigate to when using ADB.
Can you boot the phone into recovery ? I assume you have CWM as you say you installed a nandroid ? If so, Use ADB whilst in recovery, USB Debugging is always enabled when in recovery so you should have no issues finding your device from there.
If all goes well and you find the device, You can then PUSH and INSTALL files / roms from there
Keep us posted
http://www.youtube.com/watch?v=JmvCpR45LKA
I have seriously searched EVERY DAMN INCH of the Internet for this. Okay, obviously, I've seen all the posts like this one:
http://forum.xda-developers.com/showthread.php?t=2351390 (I actually wanted to reply there but can't, sad)
And I've done all those steps, I've uninstalled everything, I've reinstalled everything, I've called my mom to tell her she wasn't lying to me about me being special, I've done it all ten times. This is what happens:
System stuff: Windows XP, cyanogenmod 10, ADB and Apps set to root, USB debugging on, Android 4.2.2, latest Android Commander, Galaxy S3 Sprint, Android Debug Bridge version 1.0.31
I open cmd and type adb devices, it shows me a device is available:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
ba0a8be4 device
I open Android Commander, it has a blank line that's highlighted blue, I click "OK", it says:
Connected device has status offline and cannot be used. Please reboot your device.
I reboot my device, same thing happens.
Does anyone have any ideas? I'm seriously about to just flash it to 421 but I hate just giving up. I hate it almost as much as I hate asking for help. I spent 7 hours last night (I was up until 2am!!) and then another 4 or 5 today just trying to figure this out. I'm completely lost here. Oh, another thing, since I'm at it, does anyone know how to delete the saved RSA key from my phone? I looked in that data/adb place that link said and renamed it but it didn't seem to reset the key... maybe I need to restart, I'll try restarting after I rename it. Yep, I bet that'll work. It probably had it in memory. Anyway, pointless rant about RSA done. I hope someone has some ideas before I resort to just sitting in the corner, cuddling up with my phone, and crying until my mommy tells me I'm special.
Another possibly important thing is that Droid Explorer works briefly (I can see phone's files come up) but then crashes when I try opening anything.
It also, as I was just playing with it, seems like Android Commander causes the adb server to become outdated. Does that mean anything? I just ran adb devices, then tried AC, then did adb dev again and it needed to restart the service. I don't know if that means anything. Just something I noticed.
Oops I had to update the link, I just realized I copied the wrong one from the page suggestions it does. This now has the one I meant.
Did you find a solution? I am having the same problem.
I gave up. Flashed stock, then cm 10 with system and cache wipes then cm 10.1 without wiping system. Haven't tried with my computer since I mostly use my phone. I'll check later and update this and let you know. I would have just kept stock but my god that stuff sprint puts on sickens me......
I found a solution and it works.
http://forum.xda-developers.com/showpost.php?p=40276190&postcount=1488
Yeah, I even said in my message that I made sure that was up to date. I was able to connect to adb and see it show up as a device now but Android Commander doesn't work. I did find out that adb push (and I assume pull) works but that probably worked before and I just didn't try. Anyway, I'm not too concerned. Glad you got yours figured out.
Hope this helps!
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
lukesheardown said:
I managed to get android commander to work by installing the latest adb with the sdk manager and then I copied adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll to the bin folder located where ever you install android commander!
Click to expand...
Click to collapse
Copying the adb files to the bin directory worked for me, thanks!
Hello everyone and thanks in advance for anyone replying to my dumb question.
Today I was preparing to use the Aroma Toolkit to restore my phone to a basic stock. I placed it in a folder called ".rom" on the internal sdcard so it would appear at the top. (can you believe it?) I have CWM Red and it doesn't see ".rom" as it is now hidden. (I guess) Unfortunately, I already wiped AND formatted "system" so I can't boot the phone up to change the folder to something more sensible. I cannot restore from Odin OR Heimdall because my phone won't show up on ANY PC and it only shows "Unknown USB Device." I've been up and down with that one too. Also, I tried to put the toolkit on the external sdcard both as is and as update.zip but it says there are no files. I think my only way(s) out of this would be to Odin or Heimdall, if I can get either working again, or if there is a way to get the CWM Red to see that hidden ".rom" folder.
ANY help at all would be greatly appreciated.
Thanks for reading this.
folders and files that begin with a dot are hidden in linux systems like android. you are seeing an unknown device because you dont have samsung drivers installed. you should be able to go into mounts and storage and select usb mass storage or something like that and it will mount as a mass storage device where you can rename the file in windows where that doesnt show as a hidden file.
if you wiped system, if you turn off your device, you might not be able to get back into recovery and youll have to use odin or heimdall. you can download the samsung drivers from http://d-h.st/xEG and when you are in recovery mode, go to device manager and select from the list of device and choose samsung composite device or something like that i dont remember.
next time you want a folder to show at the top of the list, i think you can start it with an underscore. i could be wrong about that though. you can try it out and see.
I don't recall if red CWM has the mount as usb storage option. If not...
Next step is getting the drivers on your PC. Easiest option from there is Odin or Heimdall - unless you want to download the android SDK and use adb shell to rename the directory.
Underscore should work for sorting...
fwiw I use exclamation points.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
well, if youre not going to download mode to run odin, and you cant do usb mass storage in red cwm, and you want to do it from recovery, you need to choose samsung adb device in device manager. then you need adb and can do adb shell and run "mv /sdcard/.rom /sdcard/_rom"
mrpectate said:
Thanks for the reply! Although I did have the Samsung drivers installed with Kies mini, I removed Kies and installed the drivers in the link you gave me but no luck. USB used to work fine in Win as well as Lin but it stopped suddenly. I am able to get into both recovery and download mode fine but I can't go anywhere from there. I tried to "mount sd_ext" under mounts and storage in recovery, hoping to access the aroma toolkit file from there, but I get a can't mount error that says /dev/block/mmcblklb1p2 (file exists). "mount USB" doesn't help either. I really did it this time....
Thanks again for the input
Click to expand...
Click to collapse
sd_ext in red recovery does not refer to the external sd card (even though you would think it does from the name)
For compatible drivers, remove all Samsung phone related drivers from your system and install the first driver package located here (not the mini-kies one):
http://www.samsung.com/us/support/owners/product/SGH-I997ZKAATT
Some things that may help:
http://forum.xda-developers.com/showthread.php?t=1982306&page=2
Also, turn off auto driver install in Windows 7 - could be your PC is deciding what is best for you before you can install working drivers:
Go to Control Panel > System > Advanced System Settings > Hardware > Device Installation Settings > "No / Never"
Then install the driver, then connect your phone. Once the driver and devices are fully installed you can change the above setting back to what it was or to "No / Install" (that's where I usually leave it)
Good luck
Well I sincerely appreciate all the help from you guys, and Zen Arcade, thanks for the toolkit that brought me back from disaster quite a few times. I tried all of your suggestions, but it seems like I might have a hardware failure which occured before all this. I was able to connect to USB fine and out of nowhere it just wouldn't anymore. That was OK. I still rom-hopped along with straight to phone rom aquisition, but then I made a mistake. One I have learned from. I'm not able to get the phone to show up AT ALL. I even tried a clean install of WinXP then the drivers from Zen's post, and Nicky's Win7 laptop. I also tried several versions of Linux. Only Mint's Gparted could see it as /sdb/ with a corrupted partition. I even gave Haiku's Drive Probe a shot. Jack of Clubs, I tried the SDK shell but it just scans and sees nothing. I just think that the USB thing is roadblocking any hope of saving this heap. Recovery is there, download mode is there, but the connection required to utilize either of those is gone.
Again, I truly appreciate the help.
Well I've been trying to get CWM to see the Infuse Toolkit (and various roms) on external_sd but it keeps saying:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount /sdcard
I've tried 4 different microSD's formatted as FAT, FAT32, and I used SDFormatter (I saw someone recommend that somewhere). I really see this as the very last ember of hope for this phone before I let it go.
Any ideas?
BTW, my CWM is v2.5.1.3 - Voodoo lagfix
Thanks again and in advance.
Infuse GB recovery menu will not see external SD card.
If you can get adb working - connection to your PC - you have some options. From adb there are commands that will allow copying files from PC to phone ... also from external to internal sd card depending on which kernel you are running. You could also rename your hidden folder too.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thanks again for your continued help Zen. I just can't get it recognized (in a constructive way) by anything. I tried Santoku linux today and nothing. I've just been beating my head with this thing. Well here it is: CWM is accessible, as is download mode, and it charges fine, but no PC connection. When it was given to me, the glass was cracked, but it always worked fine for me. It's in a Ballistic case. If your interested in it, I'll be happy to send it to you, even if it's just for parts. I loved this phone, and had a lot of fun with it. (thanks to this community and all of its' contributors) I think it's time to move on.
I'm gonna start looking at a phone with a good selection of custom roms cuz I just love flashin' 'em
Let me know if your interested in this phone Zen.