Last night I Unrooted and restored to bnn 1.3. Now when I plug in the nook to my windows 7 pc it doesn't recognize it. Last week I installed ADB and drivers (even though I never got it to recognize my device on cmd). I thought maybe this is the problem, but yesterday I took my friends stock 1.3 and did the update from my pc for her, which is what made me want to convert to stock and test out 1.4
any ideas? the threads I found with this type of thing happening were rooted still.
cancel that, after messing around i figured out to uninstall adb interface and that worked. hope maybe this will help someone else.
Related
Okay... this will be my second attempt to get this fixed.
I rooted a week or so ago according to justadude's great tutorial. I made a nandroid backup... I thought I took all the recommended precautions. Then I fiddled. Deleted some of the T-Mobile bloat, installed launcher pro... that's it! Now, I can't USB Mount to my computer (even with USB Debugging turned on... it says I can mount, but when I do "mount" it doesn't register on my computer). I also can't download anything from the Market! Everytime it just got stuck Starting Download... so I searched and followed some recommended instructions for clearing Cache and Uninstalling Update. Now I just get notifications that say Download Failed.
I HAVE searched the forums for answers, so please, I don't need sarcastic comments about how I should just figure it out. I wouldn't be posting if I could just punch in the magical search that fixes everything.
Thanks!
when deleting your bloat stuff did you delete tw launcher or any other touch wiz stuff?
That would probably cause problems if you are still running stock rom.
No, I only deleted stuff like Avatar, MobiTV, GoGo... the apps that I would never use.
I forgot to mention that I restored to my backup as well, so now all the crap is back, but I still have the same problems with the USB and Market... I've been sifting through forums all day and can't seem to find a good solution other than a factory reset (obviously... not ideal).
i just had this issue, not with the market, but with pc recognizing my phone.
1. make sure you got the proper samsung usb drivers installed on your pc.
2. turn off usb debugging on your phone if you have it enabled.
3. turn off your phone.
4. turn on your phone and give it some time to scan your sd cards.
5. turn on usb debugging on your phone.
6. plug in the usb cable and go ahead and mount the sd card.
the above steps was what I did just now 10 minutes ago to the T (except install usb drivers since my pc already had it and for some reason stopped recognizing it just now) and my computer recognized my phone again. worth a shot.
Thanks! That resolved my USB issues... now all I need is to be able to download apps again and I'll be a happy man!
Well, I changed my game plan a little... just flashed Bionix Fusion 1.1 (out of curiosity and just plain fed up with this Android Market issue). It's all good! The ROM rocks and all my issues are fixed. Thanks to those of you who posted trying to help out!
First off let me say hello to everyone! I have never posted here but do A LOT of lurking . Big ups to all the devs here. You have helped make my Fascinate 100 times better than it was out of the box. I post over at fascinate forums and posted this issue I have been having. If anyone can help out with this I would appreciate the hell out of it.
Running
Community Rom v 1.2 w/ stock kernel(WHICH IS AWESOME BY THE WAY! Best Rom I have ever used hands down!).
EnV Theme(which is equally awesome!)
Can not get my computer to recognize my phone via USB(phone issue)
So here is what happens.
My USB mount was working fine until last night. Now every time I connect my phone to my computer I get a message in the bottom right corner telling me windows does not recognize the USB device.
When I click the message I get this
USB Device Not Recognized
USB Root Hub
Unused
Unknown Device
When i click the unknown device I get this
Windows has stopped this device because it has reported problems. (Code 43)
This is not a computer issue...it is a phone issue. I have tried plugging my phone into 3 different computers, installed the drivers, and get the same issue every time. If it is an internal error there is nothing I can do because I can't Odin back to stock and take my phone in to Verizon.
Things I have tried
Uninstalling and reinstalling the drivers multiple times, different drivers(generic and the ones from the samsung page), fixing the drivers, different USB ports, different USB cables, different rom, different kernel, re downloading drivers(both).
I cannot figure this out. If anyone can help me it would be much appreciated.
:edit: My phone WILL charge when plugged into the USB.
p.s. Once my Pizza gets here I am going to attempt putting the phone into Download mode. I completely forgot to check if Odin would recognize it in DLM. If it does I am reverting back I am going to revert back to stock and have a rooting/flashing party by myself tonight(I have beers).
I'm sure your already aware to make sure your in usb debugging mode. mentioned it just incase.
Yes my phone is in debug and set to mass storage. I want to try a hard reset but don't want to be such with a stock fascinate if it doesn't work.
Alpha Tappa Lambda
I had similar problem, and my Odin wouldn't work either.
Turned out to be some dirt in the usb port, cleaned it out with a scrap of paper with isopropyl alcohol. After a couple of cleanings, the PC recognized the device for the first time in 2 weeks. I am not the only one who has had physical problems with the usb port, search on it. The Fascinate seems to be fragile in this respect.
Of course, if your Odin detected the phone then its something else...
Good luck.
I had this exact problem and it was the USB cable for me
I didnt think of it initially cuz it would charge my phone fine
I went through every step over and over and even reformatted my entire PC
Then i grabbed by coworker's ATT captivate charger and everything worked fine...
so my suggestion is to find someone with a samsung OEM charger and see if that's your problem
I also think it has something to do with the USB port. I had the exact same issue and it ended up being dirt in the port on the phone
masterjeff said:
I also think it has something to do with the USB port. I had the exact same issue and it ended up being dirt in the port on the phone
Click to expand...
Click to collapse
I had the same thing, would charge but computer wouldnt see it. Cleaned port with a little rubbing alcohol and it worked like a charm.
My new phone will be here tomorrow. I ended up flashing ED01 with CWR and now have a fully stock fascinate ready to be sent back.
I haven't read this thread for awhile but I wish I would have tried the cleaning method before having to get a replacement phone in. Oh well...should be a fun re rooting a brand spankin new stock phone tomorrow
Well now I know what it was. I just got my new phone in. All was well.
Rooted to EF, Odin'd the EC01 radio, and flashed OTB 1.3 and was just setting everything up. I rebooted after flashing everything.
Then came the fast media scan hack. Guess what...my phone will no longer connect via USB after flashing that.
Does anyone know how to remove this? I can no longer Odin anything and I am pissed off right now.
p.s. not pissed off at anyone in particular...it's my problem for flashing not the devs...but seriously this sucks.
Re flashed the Rom, went into terminal emulator and restored the default media scanner, rebooted phone, rebooted computer, USB works fine.
Right after I flashed the fast media scanner I had the same problems I was having before...now everything is working just fine. Not trying to bust on adrenalyn or anything. Just reporting my experience with the fast media scan hack.
Cannot Get Computer To Recognize Phone
I tried installing the Anonymous ROM and got bricked. A friend of my was able to get it back to factory settings. Now, no computer will recognize my phone.
I have tried several computers, 3 windows 7 computers and 1 iMac. None of them recognize the phone.
I have tried two different cables and every USB port on all of the computers. Nothing seems to be working.
All I wanted to do was get the Sprint crapware off my phone and now I can't even get back to where I was.
Also, when I try to do the ROM manager I am getting a file signature error.
You can try Software Data Cable app, This app allows you to connect to your computer via the same wifi connection. You might give it a shot.
Sent from my SCH-I500 using XDA Premium App
I had this problem once. I think i went into my usb settings and click ask on connect or something like that. Worked for me at the time.
Sent from my SCH-I500 using XDA App
My phone is doing that now how do you undo the speed hack?
Sent from my SCH-I500 using XDA Premium App
I was in the same boat. Was rocking UKB ComRom 2.0 when all of a sudden I could no longer connect my phone via USB to my PC. I was running Windows Vista and had never had a problem before. I tried multiple PC's and multiple cords. I was worried that I would have to get a replacement.
I cleaned the USB port on the phone with no luck. Installed and deleted and reinstalled the drivers 3 times with no luck. Made sure USB settings on the phone were correct. Toggled the USB settings a few times just in case- no luck. Did a Dalvik and Cache wipe with no luck. The only thing that worked for me was the do a factory reset/Wipe and then redo my phone from there. It left UKB ComRom 2.0 on the phone and I just had to add back in my data. Just an FYI.
ive had this issue since ukb 2.0 i moved to cm7 mtd did a full data wipe and still have this issue >,> wonder if i have to manually change it or somthing
Just had this happen again today on my phone. Fixed it back on the 29th after doing a factory reset and then reinstalled my apps/ etc......This time all I had to do was a Davlik, Cache wipe and it seemed to fix the problem. Never had this happen before ComRom 2.0, but not it is happening more frequently it seems. Any ideas?
I cannot for the life of me reroot my Kindle Fire 6.2.2. It was recently rooted and, upon attempting to install CyanogenMod 9, I discovered that KindleADB is no longer recognizing my Kindle. I uninstalled and reinstalled all the necessary drivers, software, etc. I reformatted my Kindle to factory state. I even went as far as to reformat my computer and, for the life of me, I cannot find a way to get KindleADB to recognize my device. I've read through all the threads, tried all the recommendations and the only reassuring thing I've discovered is that I am not the only person with this problem, although no answers were posted. Does anyone have anything to recommend or has anyone solved this problem that hasn't posted a solution? I am going ABSOLUTELY INSANE not being able to restore my Kindle's full potential. Help?
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
Thanks
Click to expand...
Click to collapse
You're in a rough spot here. You only have two possible options:
1) See if someone with your phone can make a debrick img file similar to this idea -
http://forum.xda-developers.com/showthread.php?t=2660566
I haven't seen anyone say they have tried something similar on your phone, but the only other option will be...
2) JTAG Service such as this -
http://mobiletechvideos.mybigcommerce.com/
If you're getting QHSUSB drivers, you're past the help of conventional unbricking methods using tools like Kies, Odin, or Heimdall.
Thanks, you've given me some hope! I have some data I would really like to restore..
I'll try and post back here if I get some results
johney9 said:
Hi,
As the tittle suggest, I've managed to brick my phone.
The phone isn't responding at all, and acts as though the battery is pulled out. When I connect it to my PC, it shows up as QHSUSB_DLOAD, and there are no drivers.
Note that this is the same PC I used to flash cyanogenmod 10.2, so I have all the required samsung drivers. Also, it's the odin doesn't detect my phone.
The last steps I took before my phone died:
1) installed App2SD
2) partitioned my SD
3) installed and configured linux swap
4) restarted
After that, the phone got angry and just wouldn't respond. I didn't even have time to transfer any of my apps to the SD.
The phone has a custom rom installed (cyanogenmod 10.2). Already took it to a service place, with no luck..
Any ideas?
hope anyone kan fix my problem i returned back to the stock rom 4.0.4 after i was on cm 12 then tried to ger back to cm11 the wifi and the bluetooth is not working on both cm11 and cm12 what can i do
Click to expand...
Click to collapse
Hey guys, I could really use some help figuring out how to fix this.
Neither my phone, or my PC realize they are connected to each other after I have updated my phone to OOS 11.0.5.5 an hour or two ago. I have tried two different USB cables in two different ports of my computer and still nothing.
I had connected my 8 Pro to my PC using one of these cables only a week ago! Before the update, my phone was on build 10.13, or something like that.
See, what happened was, My phone has been rooted since like last June or May, but I've always had that 'your phone has an update' notification in my notification bar forever. Well, I accidently hit it one day without realizing it (a couple months ago) and my phone tried doing an OTA update but it told be it failed because my phone was rooted, however, it still pushed the update through.
This put my phone in a weird unrooted limbo where gapps thinks my phone is rooted, but none of my apps that require root actually work and I am currently trying to fix that.
So, to start I was gonna just fully update my phone to get rid of the notification and just root the latest OOS. I downloaded and installed the OTA and I got some kind of root error, but like the last time, the phone applied the update. Now, I am trying to connect my phone to adb, but there's no acknowledgement from either the PC or the phone that they are connected.
How can I solve this?
first try using a different USB cable. And check if that works.
Dianafoe said:
first try using a different USB cable. And check if that works.
Click to expand...
Click to collapse
I've tried two different ones, and nothing. They both work for charging through a wall outlet and just last week they worked on the PC. It is not the cables.
So after the factory reset, did you reset up Developer options like USB debugging?