I have been enjoying trying out the new ROMs, but I have run into a problem where ADB stops working over USB after I install a DK17 ROM, If I go back to a DK05 ROM then it is working. I am able to use adbWireless. Is this a known issue? Is there a workaround?
Check to see if you have USB debugging enabled.
PokrTom said:
I have been enjoying trying out the new ROMs, but I have run into a problem where ADB stops working over USB after I install a DK17 ROM, If I go back to a DK05 ROM then it is working. I am able to use adbWireless. Is this a known issue? Is there a workaround?
Click to expand...
Click to collapse
go to menu, settings, applications, development, then check USB debugging.
Related
ok i have installed many roms for my g1, have had the hero for sprint for awhile and everytime I try to do the fresh rom i get errors, ive tried wiping it then installed the update.zip, tried to just overwrite it still errors which always forces me to nandroid restore,
I can do the eclair 2.1 no problem, but fresh always gives me errors. atm i have a rooted sprint htc hero, no custom rom on it atm. any help?
What kind of errors?
Have you tried re-downloading the ROM?
well when i first boot it up i does the "fresh" sound and goes though all the boot ups and says ok, then gets to the last one that says like boot up fresh o somethingthen [wait] i wait, it eventually starts up but mainly alot of force closes,
im thinking of unrooting my phone back to stock and I have been looking at pre kitchen, so once my phone is stock, i just plug my phone in and do auto-root? and thats all i have to do?
because im thinking of going stock then auto rooting for ease.
samrozzi said:
well when i first boot it up i does the "fresh" sound and goes though all the boot ups and says ok, then gets to the last one that says like boot up fresh o somethingthen [wait] i wait, it eventually starts up but mainly alot of force closes,
im thinking of unrooting my phone back to stock and I have been looking at pre kitchen, so once my phone is stock, i just plug my phone in and do auto-root? and thats all i have to do?
because im thinking of going stock then auto rooting for ease.
Click to expand...
Click to collapse
The long wait after the first flash is normal and you will see that every almost every rom after the first boot. If your phone is totally stock (you mentioned you tried wiping data) then you definitely shouldn't be getting FC's.
Did you wipe your data after using the 2.1 rom and before flashing fresh rom? That would be the easier way to go about things. But using the RUU to flash back to totally stock and starting over wouldn't hurt either.
yeah i have wiped everything and tried, i mean i rooted and hacked my g1 for over a year numerous times, so idk. just quick questions on how to revery back to stock because this have never done. im downloading the RUU 1.56 from here
http://geekfor.me/news/sprint-ruu-fails/
not really sure on steps to go back to stock once I get that file?
and also new to pre kitchen, once my phone is back to stock and unrooted etc... do i just plug in phone to pc, start pre kitchen and click auto rooter?
samrozzi said:
yeah i have wiped everything and tried, i mean i rooted and hacked my g1 for over a year numerous times, so idk. just quick questions on how to revery back to stock because this have never done. im downloading the RUU 1.56 from here
http://geekfor.me/news/sprint-ruu-fails/
not really sure on steps to go back to stock once I get that file?
and also new to pre kitchen, once my phone is back to stock and unrooted etc... do i just plug in phone to pc, start pre kitchen and click auto rooter?
Click to expand...
Click to collapse
Once you download that file just extract it and run it. It will walk you through it from there and once it's done you will have a stock from-the-factory Hero. Once you get it booted up and stuff then open the kitchen (get 0.2) and go under the help menu and run the diagnostic tests. As long as sendkeys, adb, and rooting tools pass then go ahead and go to the auto rooter and that's it. If any of those 3 fail then you may not be able to use the rooter.
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
not sure if i have to mount her or not because it is connected to my computer
samrozzi said:
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
Click to expand...
Click to collapse
Try closing the RUU, putting your phone in to fast boot and then checking device manager on your computer to make sure you aren't missing any drivers. If you aren't then start the RUU again.
To go in to fastboot power your phone completely down. Then hold volume down and power. This should get you a screen with 3 skateboarding androids. And then I believe it is volume up for fastboot. Make sure it's plugged in to your comp and confirm device manager is clean, and then run RUU.
samrozzi said:
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
not sure if i have to mount her or not because it is connected to my computer
Click to expand...
Click to collapse
I had that problem, and installing HTC Sync fixed it.
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
samrozzi said:
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
Click to expand...
Click to collapse
I have Windows 7, and both HTC Sync and the pre-kitchen work fine on my computer. What is it that you think Windows 7 is preventing you from doing?
samrozzi said:
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
Click to expand...
Click to collapse
A couple of things.
Install HTC Sync or go get the Android SDK to install the ADB driver.
Then run RUU
Boot the phone into fastboot Power off, hold down volume down button while phone is booting back up.
When you are in Fastboot, press Volume up once.
Then plug the USB in and run RUU.
I have Win7 32 and x64 and have been able to do all ADB functions fine with both machines, its a little more cumbersome, but not an issue.
TTG flashing issues
I had TTG and was trying to reflash to MODACO. The Rom wouldn't reflash. I wiped, factory reset.... Just boot looped or froze. A lot of errors and force closes. I'm running GUTTED 1.6 now with no problems. Why would there have been an issue trying to flash MODACO...?
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.
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.
Wifi no longer works on my 2.3.1 Nexus S after rooting. Can anyone please help? I see possible driver solutions to the same problem under Nexus S, but assume the driver for Nexus S is not the same. When I try to enable wifi it says ERROR. I just discovered the camera also is not working.
Edit: Momohamed20's stock NAND fixed all my problems YAY!!
I've seen Wifi not work on mine running 2.3.1, I haven't rooted, usually it's after I try to turn on Wifi Hotspot and get the "Error" message, then Wifi won't work again until I reboot.
well i've rebooted and gone to fastboot and restore boot many times ... no difference
heinrich said:
well i've rebooted and gone to fastboot and restore boot many times ... no difference
Click to expand...
Click to collapse
A friend of mine just returned his to Best Buy because he was having the same issues. His new one doesn't have the issue
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
heinrich said:
Dudes this is totally not cool. My phone is hosed. All I did was take a working 2.3.1 and unlock/root it
Click to expand...
Click to collapse
Have you flashed either the MCR or CM7 ROMs in the Development section and still had the same problem?
Or the stock 2.3.1 NAND backup floating around in there too.
I just got my NS today its rooted with working camera and wifi, I'm also on 2.3.1. What I did was unlock the bootloader and rooted using the superboot method. You don't have to mess with anything else. I've read in several posts if you use other methods it can cause the issues your having
Sent from my Nexus S using XDA App
I just flashed the boot image from http://forum.xda-developers.com/showthread.php?t=884194 and the camera now works again, but not wifi. I can't find the stoclk NAND or I'd flash that. I see a link to the stock system.img in the thread I link to in this post, but it's a broken link
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
heinrich said:
No I haven't tried the MCR o CM7 -- no idea what they are but will go find out.
Click to expand...
Click to collapse
Ah, okay, MCR is Modaco Custom Rom and CM7 is Cyanogenmod 7. They're both very good custom ROMS based on Android 2.3.1 with some added features and/or other changes. MCR is closer to stock, imo, if that's something you're interested in.
In order to flash them to your device you need to be rooted(which you said you are), and be able to flash Clockwork Recovery via fastboot or ROM Manager. If you're not familiar with Clockwork recovery/ROM Manager, check out this thread before proceeding: http://forum.xda-developers.com/showthread.php?t=875875
yep I have clockwork recovery and rom manager and all that
If someone can help me find the stock system rom I think it will fix tghe wifi problem .... camera now works.
Oh my goodness isn't there someone who knows how to get wifi working again?
RESOLVED
Momohammed20 resolved my issue with his full restore stock image and excellent write-up here: http://forum.xda-developers.com/showthread.php?t=884093
Kind of a "getting my bearings" question, but I have been flashing custom recoveries, ROMs, etc. for going on a year now, but, you know, I just follow guides and use common sense, so I am definitely still a novice by all means.
Interesting thing just happened. This week I turned off USB debugging and then Developer mode altogether after flashing back to the stock MDC rom so I would get the MDL OTA update. The update came, and tonight, three days later, I installed it and then proceeded to install the OUDHS recovery.
Odin flashed it but just sat there at the end with "RESET" in the status box. I assumed that was because I unchecked the "Auto-Reboot," so I then powered down (just held power button, not battery pull or anything), and launched into recovery (VOL.UP), and voila! I was in the custom recovery.
I then flashed Shabby's custom kernel and SuperSU, rebooted, and now I'm rooted. SuperSU works, Titanium Backup works (which I used to freeze "seandriod" to get rid of the security warning), etc.
TL;DR: I forgot to turn back on Developer Mode and USB debugging before doing all this, yet it all still worked. :cyclops: Why, then, do I read so often that one needs to turn that on to flash things with Odin?
~Zach~ said:
TL;DR: I forgot to turn back on Developer Mode and USB debugging before doing all this, yet it all still worked. :cyclops: Why, then, do I read so often that one needs to turn that on to flash things with Odin?
Click to expand...
Click to collapse
Developer mode is for adb access to the phone. Doesn't have anything to do with Odin or recovery.
Sent from my SPH-L720 using xda premium
crawrj said:
Developer mode is for adb access to the phone. Doesn't have anything to do with Odin or recovery.
Click to expand...
Click to collapse
Well, assumed adb, but I thought Odin just had the necessary framework compiled in.
Well, okay. Thanks! :good: