So, for some reason I've seemingly broken ADB.
I've been having problems with 4G, so I followed this thread to completely start over from scratch. I use ADB fairly often, so I think this is when it started acting up.
http://forum.xda-developers.com/showthread.php?t=715915
Anyway, customary disclaimer:
*I have USB Debugging Enabled
*I have killed ADB and restarted server
*I have re-downloaded HTC Sync to get new drivers
*I have tried using ADB from multiple backups of my Android SDK
*I CAN use ADB from recovery, but CANNOT when the ROM is up and running.
I'm on Fresh 3.1.0.1, and was prior to the restart from scratch thing.
What could have killed ADB connectivity from inside the ROM? Thanks for any help, I've tried all I can think of to get it to work.
Related
I have rooted my fascinate, no problem, I have installed the Deodex, no problem, then I put the captivate keyboard zip on and rebooted, and the whole thing went to ****. I can't do anything except light up the keys, this is a real pain in the ass, especially since all the real hard stuff went smooth. I am now trying to boot into clockwork and I can't seem to do that.
What happens when you try to boot to Clockwork ?
If you've installed CWM, you should be able to get to a shell via adb and put the files back the way they were.. I know you can do this as long as you're at the recovery menu, but depending on what's happening during boot-up, it might allow access to the shell without getting to recovery.
Basically just run 'adb shell' from your command prompt and see what you get (obviously the phone needs to be connected via USB).
Thanks guys, i got it working but I was scared ****less. I managed to get to clockwork and luckily I had a backup so I restored from there, I believe the problem came from flashing deodex.
Sent from my SCH-I500 using XDA App
Hey guys,
I finally decided to root my eris today. I used the revoked method on my mac and everything worked flawlessly. I then downloaded a ROM FroShedYoV7 and followed the installation steps. About half way through I received the error symlink /system/xbin/busybox SYSTEM:xbin/arp. I then tried a few different ROMs and received the same errors. I did a backup beforehand; however, I can not even restore to that. I was going to use the RUU method on my school's PC (I have a mac) but when I tried it, it was unable to recognize that the phone was connected - probably because it stuck at the fastboot screen. I still have access to the recovery though.
I did a little research on the matter and found that chrome sometimes messes up zips so I tried it with firefox and had no success.
Any help would be appreciated, I just want my phone back rooted or not.
what recovery are you using?
first, i'd pull the battery, re-insert and then try booting into recovery (volume up + power)... then, full wipe and try to flash again. are you verifying the md5 of the download to ensure it's not bad?
if you happen to be using clockwork, i think there is a thread that discusses cleaning some things up... i'll see if i can find it.
I'm not sure what you mean by verifying the md5, but I have tried multiple ROMs downloaded by multiple browsers. And also I did full wipes before each attempt.
I also just attempted this fix the RUU ROM rename to PB00IMG.zip fix, but had no luck.
Thanks for your help!
Also, I am using clockwork.
Use RA... CW has issues
Sent from my ERIS using XDA App
Try this thread and good luck.
Hey guys, I just made the move from Blackberry to the Fascinate from Verizon, it is stock with the DI01. I am familiar with rooting using ADB etc and I have been doing it for a few friends. My issue is when I plug the Fascinate via usb I get a CD-Drive icon with a few software like Samsung_Mobile_USB_Driver and TooLauncher_Bootstrap and when I mount SD I get the same CD-Drive icon with error message windows can't access this disc. Also ADB shell also reports Device not found with USB Debugging and Allow mock locations enable.
The SD settings is set to Mass storage and I have the Samsung driver installed.
Can anybody point me how to get the SD mounted as a storage disk so I can have access to it?
Thanks allot guys
Can you post what OS you are using for clarification?
The issue I had with this was I didn't realize I had to authorize the mount from the pulldown up top when I plugged it in. You probably did that, but just in case.
Swyped w/ XDA App. When in doubt, mumble.
Im on Win 7 x64 with Samsung USB x64 driver install.
The funny thing I had another Fascinate in just last week and I was able to connect and mount the SD card as a disk drive just fine.
Any tought?
Try restarting your phone with the USB cable plugged into your computer and usb debugging turned on.
Here are some posts by people with the same issue:
rmtobler said:
Well I finally got the computer to recognize the sdcard, but I had to flash the d101 odin files a bunch of times and start over. But after awhile on DJ05 the same problem happens again. I tried to check to make sure the sd was recognized after each step I took, but it seemed it seemed to have stop working overnight and now is just not recognized at all or as my cd-rom (drivers show 'samsung cd-rom usb device', though the sdcard is still working on the phone
Click to expand...
Click to collapse
rmtobler said:
I got mine to work again. Although I'm not exactly sure why it worked. But I un-installed and re-installed the samsung usb drivers and then later when I restarted my phone with the usb plugged in (and usb debug on) the computer started loading up the drivers correctly while the phone booted and it has worked since then.
Click to expand...
Click to collapse
nike984 said:
This worked for me too.
Basically you have to restarted the phone with the usb plugged in.
After than that the problems was gone.
Thanks rmtobler!
Click to expand...
Click to collapse
cseeley said:
I am not totaly sure that the connection issue is related to DJ05, or full DIO1 package. After running into the problems with the debug connection, I was not able to root because of the connection issue.
Luckily, I saved off a rom manager backup od my DJ05 after rooting it the first go around, as it seems as though something of DJ05 stays around, and breaks all my DI01 roms.
What I ended up doing, to get back up and running is as follows;
I formatted the SD card just in case that had a problem. Put my rom manager backups back on their, and then I flashed back the DI01 package to get me back to the factory radio. Then I flashed clockwork, I then copied update.zip from the clockwork thread to the root of the sd card, and booted into recovery. Next I restored my DJ05 backup that already had root, and then back into recovery and flashed the DJ05 radio, and Kernel.
I am now back up and running. Not sure on the debug connection, I will have to some things.
Thanks,
Chris
Click to expand...
Click to collapse
rmtobler said:
Try restarting your phone with the USB cable plugged into your computer and usb debugging turned on.
Click to expand...
Click to collapse
Don't know if anybody ever told you this!
You're the man, it works, I have access the SD card via USB.
Thanks ALLOT bro.
none of the above methods work for me. All trouble began when i installed DJ05. I used the **87284 through dialer to confirm its on USB mode. Now i don't have debugging and sdcard mount failure.
Under windows 7 x64 device manager other devices got loads of question marks on Data Interface.
I was looking at other post for EVO4G
http://forum.xda-developers.com/showthread.php?t=695243
The fastboot option is only available on HTC models i guess.
I was wondering about a fix for fascinate through Odin.
I would just suggest trying the different odin files for dj01 modem, system, recovery until you get a combination that gets the usb working again. The first time I used odin it worked great, then the second time it didn't work and I just kept doing it until it did. Then once I went to dj05 and flashed anything using clockwork the USB would go back to not being recognized but a restart w/ the phone plugged in fixes it.
Downloaded latest files & instructions from irc samsung-fascinate channel. it used to mount as CDROM earlier. That is gone now. Still shows question marks under Data Interface win7 x64. Tried various combinations. Went back to stock now.
However the baseband modem is DI01 and build number is DH12. Similar issue reported by http://forum.xda-developers.com/showthread.php?t=854704.
In search of DH12 baseband modem now. Hoping this will fix the issue i'm having. I've got a nandroid backup but that does not restore the baseband modem to DH12.
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
What did you come up with by searching the forums or Google?
Hemidroids said:
What did you come up with by searching the forums or Google?
Click to expand...
Click to collapse
As with many things, the info that I found is conflicting. Since I had been burned by trying things before verifying what I was doing, for once, I decided to reach out for advice BEFORE I erased something that isn't recoverable.
Yes, I know that many on XDA hate users who ask for help before researching on their own. The problem for me is that I couldn't find a clear answer.
Since I made my post, I tried a few things...
Details and questions are here: http://forum.xda-developers.com/showthread.php?t=2089144
Thanks for your response, although I get the feeling that you had expected me to know the answer to my question...
OldDogEyes said:
My N7 is rooted and stock... I used the N7 Toolkit method... My N7 is 32gb non-3G version...
It's been working fine, no problems. I thought that it was a little laggy since I installed a 2nd account on it ... so a day ago I deleted the 2nd account hoping to get rid of the lagginess that started after installing the 2nd account.
Today I came home with the N7 and I heard some notifications when it logged into my Wifi... And about 30 mins later I went to use it and the wall paper that is usually showing went black, the screen did some funny things and the tablet reset.
Now it's stuck in a boot loop...
I can get into the bootloader and recovery, but whenever I exit, it goes back into the boot loop.
Since I hadn't installed anything custom when rooting, do I even have Nandroid? Can I back it up and connect to USB before wiping?
Does wiping erase the SD portion of the memory?
Any ideas for troubleshooting? Would love to know what happened here...
Thanks...
Click to expand...
Click to collapse
First if you have a custom recovery, boot into that, wipe cache, then dalvik, and try rebooting. See if that works.
Nandroid would be the backup of your entire ROM that you made either using ROM Manager or manually initiating a backup in recovery.
Wiping using ClockworkMod Recovery or TWRP Recovery will leave the /sdcard area (/data/media) alone, however it'll remove your ROM. At that point, you'll need to re-flash a custom ROM to your device. If you reload the stock N7 images from Google, it WILL erase your /sdcard section!
You can push files to your device while in recovery using the adb push command. You can also pull files from your device using the adb pull command.
adb push <name of file> <location on device you want to push to>
EXAMPLE: adb push ROM.zip /sdcard/
adb pull <location of file on device>
EXAMPLE: adb pull /sdcard/ROM.zip
Research adb, adb push, adb pull commands.
Hi, It may not be completely bricked but as far as I am concerned it is. I tried to free up some space on the phone by formatting everything in ClockworkMod. Factory resets did nothing and the phone showed I had used over 10 GB. I figured formating was just going to clear out all the backups and old files.
As of now I can get into recovery but that's about it. When I try to reboot all it does is bring up the words GOOGLE. My PC wont recognize it as I cant enable USB debugging. I thought if I could just drag a new rom, gapps, zip file into the internal storage I would be good. I also thought I might be able to restore it to stock with a toolkit but again they request USB debugging on.
I am real new to this so any help would be greatly appreciated. Is there a way to bring this phone back to life in some sort of straight forward way?
PS. As of this morning things seem to have gotten worse. I used a toolkit to try and get things working and now I cant boot into recovery. All I get is the robot on its back with red triangle icon. I can press power, then volume up and get another menu but I am really at a loss. Any further help would be great. Thanks.
Thanks
You're definitely not bricked.
You must restore the factory image, which you can find from Google... Google "nexus factory image" and restore in bootloader mode.
I'm not going to go into detail on how to restore, there are dozens of threads on how to do that. Start by Googling "how to flash nexus factory images"...
I'm assuming that since you've dabbled with modifying your Nexus that you are familiar with the super duper important ADB/Fastboot procedures? If not, you've got a lot to learn before you start messing with your phone...
Edit: You can also attempt to ADB push a stock rooted ROM (only so you don't have to mess with gapps at the moment) through your custom recovery. Again though, do your due diligence and read before messing with this sort of thing.
Sent from my Nexus 4 using xda premium
Just sideload a rom with adb.
adb push a ROM into your memory via cmd prompt. I think you can adb push data using the Nexus 4 toolkit in the stickies.
When you figure out how to push files into your phone, flash the new ROM.
Alternatively, use efrant's guide from my signature. The only correct & educative way of returning to stock. Avoid toolkits!