Related
Hey guys, I probably have a pretty unusual question or rather observation. Sometime yesterday night when I connected the Galaxy Nexus to the power outlet it started to make a crackling noise. I immediately disconnected it but it already smelled like burnt plastic. As you can believe I was pretty shocked! Trying to turn on the phone worked flawlessly though, so I though, OK might have been my outlet and tried two different ones. Still to no avail, the phone works but won't charge.
I turned it off for the night and waited until the morning to try to connect it to my computer (thinking maybe it's the plug that's broken) and reset it to factory default. Big mistake! Windows pops up with a warning telling em that it detected a power surge on one of my USB ports, resulting in my phone still not charging, the USB port being broken (won't recognize my USB key anymore), and and the Micro-USB connector emitting some smoke after I unplug it from the Nexus.
Now, enough storytelling. Maybe you guys can help me with the mountain of questions I have after this episode:
A) Really, what happened here? I don't think it has something to do with the software side of it, can it? (eg Battery overloaded?) Then I would guess more people would have had the same problem... I'm running AOKP M3 and Franco Kernel 3.0.08-M1.
B) Did anyone have the same problem?
C) I guess it's unfixable from a software standpoint, so my only option would be to send it back to Amazon and hope they replace it. Any other ideas? I bought it at Amazon.de (Germany) but due to it having AOKP Rom and Franco Kernel installed getting a replacement might be difficult.
C) How do I get my USB port functioning again? It's a new notebook but I don't want to send it back for repairs as I bought it in Hong Kong (I have an international warranty though.) and need it to write my Thesis.
Update: Uninstalled and re-installed the USB drivers, that fixed the USB port.
Thanks for your time and hopefully help!
A confused GN user.
majar said:
Hey guys, I probably have a pretty unusual question or rather observation. Sometime yesterday night when I connected the Galaxy Nexus to the power outlet it started to make a crackling noise. I immediately disconnected it but it already smelled like burnt plastic. As you can believe I was pretty shocked! Trying to turn on the phone worked flawlessly though, so I though, OK might have been my outlet and tried two different ones. Still to no avail, the phone works but won't charge.
I turned it off for the night and waited until the morning to try to connect it to my computer (thinking maybe it's the plug that's broken) and reset it to factory default. Big mistake! Windows pops up with a warning telling em that it detected a power surge on one of my USB ports, resulting in my phone still not charging, the USB port being broken (won't recognize my USB key anymore), and and the Micro-USB connector emitting some smoke after I unplug it from the Nexus.
Now, enough storytelling. Maybe you guys can help me with the mountain of questions I have after this episode:
A) Really, what happened here? I don't think it has something to do with the software side of it, can it? (eg Battery overloaded?) Then I would guess more people would have had the same problem... I'm running AOKP M3 and Franco Kernel 3.0.08-M1.
B) Did anyone have the same problem?
C) I guess it's unfixable from a software standpoint, so my only option would be to send it back to Amazon and hope they replace it. Any other ideas? I bought it at Amazon.de (Germany) but due to it having AOKP Rom and Franco Kernel installed getting a replacement might be difficult.
C) How do I get my USB port functioning again? It's a new notebook but I don't want to send it back for repairs as I bought it in Hong Kong (I have an international warranty though.) and need it to write my Thesis.
Update: Uninstalled and re-installed the USB drivers, that fixed the USB port.
Thanks for your time and hopefully help!
A confused GN user.
Click to expand...
Click to collapse
A) Sounds like a short circuit somewhere. My guess would be the connector or close to it.
B) I certainly didn't but I'm sure it's happened to someone.
C) Unroot and Relock and send it back to Samsung if Amazon doesn't take it back. I'm not sure about their return policy since it's a cellphone that is under warranty. May also depend how long ago you bought it.
The more I think about it I wonder if it's just the USB cable... Since you said the smoke came from the Micro-USB connector... Plug it back into the computer without the phone and see if you get the USB power surge thing again. There may just be a short in the cable.
Of course checking it with a multimeter would be safer, do you have one of those?
Or do you have another Micro-USB you can try charging the phone with?
chjade84 said:
C) Unroot and Relock and send it back to Samsung if Amazon doesn't take it back. I'm not sure about their return policy since it's a cellphone that is under warranty. May also depend how long ago you bought it.
Click to expand...
Click to collapse
The problem is that I can't even unroot it since it is not being recognized by the computer (and I get the power surge warning). I will try with the new cable, and then send it back even if it works. might give me problems further down the line if I don't.
chjade84 said:
The more I think about it I wonder if it's just the USB cable... Since you said the smoke came from the Micro-USB connector... Plug it back into the computer without the phone and see if you get the USB power surge thing again. There may just be a short in the cable.
Of course checking it with a multimeter would be safer, do you have one of those?
Or do you have another Micro-USB you can try charging the phone with?
Click to expand...
Click to collapse
I don't have a different cable (or multimeter) near me at the moment but will give an update as soon as I do. I didn't get the power surge warning when I just plugged in only the cable, but as there is no source that could draw power that seems likely to me.
P.s.: Just bought it in january so generally sending it back shouldn't be a problem - if I can get it unrooted.
majar said:
The problem is that I can't even unroot it since it is not being recognized by the computer (and I get the power surge warning). I will try with the new cable, and then send it back even if it works. might give me problems further down the line if I don't.
Click to expand...
Click to collapse
Yes I kind of forgot about that...
majar said:
I don't have a different cable (or multimeter) near me at the moment but will give an update as soon as I do. I didn't get the power surge warning when I just plugged in only the cable, but as there is no source that could draw power that seems likely to me.
Click to expand...
Click to collapse
Well that's "good" in that we know the cable isn't shorted. I thought maybe some pins or wires were touching inside the cable that would cause a short (+5VDC and GND) even without the cable being plugged into anything.
So it does look like the fault is in the phone somewhere... And that could be just about anything.
Being that it's Amazon they probably will just replace it and not even bother with checking for it being rooted - especially since you can say it's smoking. As far as I know only the carriers will turn on the phone and look it over (not to mention most Amazon employees wouldn't know root it it reached out of the phone and smacked them across the face). Other 3rd party stores just mark it as defective and put it in a box to send back. I'm not sure how Amazon's return process works though.
I had several problems with my EVO (speakers mostly) and had it rooted when I took it in. They just fixed it anyway and even told me they liked what I had done with it a few times.
Hey, just to give an update I didn't get a specific explanation but Amazon replaced the battery, cable & charger. Now its working again. No problems with it being rooted, they even left rooted but installed stock android & kernel.
I'm currently having this problem, i called google, and they transferred me to samsung. And their department that handles this issue is closed on weekends
peacebomber said:
I'm currently having this problem, i called google, and they transferred me to samsung. And their department that handles this issue is closed on weekends
Click to expand...
Click to collapse
any update? i'm having this problem aswell. my phone wont charge through the wall charger but will when connected to a computer... but when it's connected to the computer it says that my usb device (phone) has malfunctioned.
because of that "malfunction" i cant revert back to stock everything and relock everything to get it repaired with bell mobility.
marrrio_ said:
any update? i'm having this problem aswell. my phone wont charge through the wall charger but will when connected to a computer... but when it's connected to the computer it says that my usb device (phone) has malfunctioned.
because of that "malfunction" i cant revert back to stock everything and relock everything to get it repaired with bell mobility.
Click to expand...
Click to collapse
when i sent them my phone i couldn't bring back to stock software but i still shipped it out either way, i actually got an email from samsung today saying a component has been replaced and being shipped out back to to me, so i guess they fixed it with it being rooted, so when i receive it ill let you know
Well I got back my phone today and its charging again. But they restored my phone back to factory setting. So I lost all my pics and phone didn't restore previous apps etc but oh well as long as they fixed it and no questions asked I'm happy
Sent from my Galaxy Nexus using xda app-developers app
So after several weeks trying to figure out what is wrong with my device I came to the conclusion that the USB port on my GNex went bad
here's a few reasons why:
-GNex No longer chargers when plugged in the wall outlet tried several OEM and non OEM USB cables
(but will somewhat charge if the phone is turned off but very slowly and has an error) It shows the battery icon then
it will flash twice the battery charging icon then back to the battery icon with the bolt in the middle and will do that through out the night.
Had a custom rom on there tried changing roms but my computer no longer recognized it and so i've installed removed various drivers
and tried different PC ports and nothing would let it recognize so I manually download a rom on the phone but it wouldn't install.
So I was finally able to odin back to factory stock but that still didn't do anything not only I can no longer go into recovery because it seems to
not have one so I'm stuck and it's getting on my nerves because the only way I can charge it while it's on is plugged into the computer.
I'm my money is that USB port on the phone is malfunctioning so I'm trying to relock the bootloader but can't find a through the terminal, because ADB does not work. Technically the phone still has manufacture warranty. So any help would be appreciated. Thanks guys
Does your computer recognize it in fast boot?
Sent from my Galaxy Nexus using xda app-developers app
I had the exact same issue with an old T989 (T-Mo SGSII). Same symptoms and everything. What got me through the insurance claim was that I told them that the phone was doing an OTA but somehow it failed and it was stuck at the ODIN screen. What really happened was the USB port gave way while restoring to stock which caused the soft brick, but after that the USB port was completely nonfunctional. Try re-positioning the USB cable, the port might be making bad contact with the pins. Other than that, I would just ship it as is since they hardly check that the phones are rooted or in your case, an unlocked bootloader.
No it doesn't recognize it in fastboot or anything it says unknown device. As far as sending it back in I've been on the samsung website trying to request a service repair, but I've also purchased the phone on CL. But I didn't have a problem with it for several weeks so I know it really wasn't a defective unit. Yeah, I thought about reposition the USB cable to no avail.
I didn't think about using that... how did you manage to get an RMA or something to get it replaced
So you can use the device itself fine? Cab you go into play store? Download booot unlocker . it locks/unlocks the bootloader from the phone itself
Sent from my Nexus Prime
Questions go in Q&A
Thread moved
Thanks
FNM
My apologies if it was in the wrong thread. Yes I'm able to use the phone fine and everything it's just the charging and recognition that's causing problems.
Another question what do I need to be able to open a repair request from samsung or how do I go about it. went to the website but all it does is take me to FAQs?
Well unfortunately boot unlocker won't work because I don't have root and I can't root my phone through ADB or anything like that because like before PCs won't recognize phone at all unless there is a method I can use through the terminal editor
I don't want to hi-jack your thread, but I am also having a similar issue.
I am running CM 10.0.0 but the cell phone will charge, but will NOT connect to the computer. I have tried two different cables and on 3 different USB ports on two different computers. I have the Samsung drivers downloaded and installed. I did not have this issue before the unlock/flash of CM. Is this is a known issue? Is there anyway around it?
I'm starting to think its a USB port issue
If it hasn't been said before, this is a very common problem, it even happens with a few Samsung phones. It's not software related, all hardware, the micro USB port is lousy.
Unless you want to work with Samsung, who, based on my experience, will probably want to charge you "because you broke it", there's the incredibly hard-to-find Pogo Dock or the inductive charging mod, which is actually kinda neat I may do that, I already have all the touchstone stuff...
There's also DIY replacement of the USB daughter board or whatever the exact term is.
In any case, Samsung *might* help you, for a decent fee and 2 weeks' (or more) time.
Yes, try to analyze USB port pins for damage, dirt, bent, anything that can cause a lousy connection (or none whatsoever)
Sent from my i9250
Yeah, I mean I would have to figure something out because I can't transfer files and the only to do it is to upload them to the cloud which is not optimal and real pain.
well out of nowhere USB starting working and charging now normally. So that's cool I'm glad now just to wait till ubuntu comes out.
After installing COTR with the KFU, i went and downloaded FFF and the 4.2.2 ROM. After i plugged in the factory cable and plugged it into my computer to get it into recovery mode, After using KFU to send it to recover it froze on the kindle fire splash screen. I turned it off and turned it on again and it went in a endless loop of turning on and off on the kindle fire splash screen the orange one. Confused where i should go from here.
Running Win7 64-bit
What happens when you plug in the factory cable?
it keeps cycling on and off
What's the interval between on and off?
Just pluged it in and now it is stuck at the stock static kindle fire screen. Device now appears as unknown.
When it first comes on, does the kindle fire logo stay brightly lit, or does it go dim at any point?
Starts bright and then goes dim right after. Driver error says code 43.
You need a factory cable.
i have one, that is what i'm using.
ramsv94 said:
i have one, that is what i'm using.
Click to expand...
Click to collapse
Let me rephrase that. You need one that works.
oh dang, well the good thing is SkOrPn is already sending me another cable because he didn't like the one he sent me. Hopefully it works then. Out of curiosity, how do you know the cause is a bad wire? So i know what to look for.
If the factory cable were working properly, the Kindle Fire logo would stay brightly lit, indefinitely. There would be no change in brightness.
[Edit:] The fact that your KF logo goes dim means that it's not staying in fastboot.
soupmagnet said:
Let me rephrase that. You need one that works.
Click to expand...
Click to collapse
I sent him a second cable this morning. The first one was an emergency cable (test cable of different design) that I kept around just in case (I was out of stock when he ordered), however when I assembled it i noticed the case was way too small for the mod and I had to apply tremendous force just to get it to partially close. With that said, I tested that cable over and over multiple times with a very expensive multimeter. But maybe it has a intermittent connection I could not find with a meter, thanks no doubt to the force I used to assemble it. Possibly broke a solder joint is my guess.
Anyway does this cable need to stay connected or just launch Fastboot? When Fastboot launches don't you guys remove the cable and then attach your normal cables? I was told not to keep the cable connected once Fastboot launches and to attach a normal cable for fastboot commands. Is this no longer true or has that never been true?
Sent from my Nexus 7 using Tapatalk 4
SkOrPn said:
Anyway does this cable need to stay connected or just launch Fastboot? When Fastboot launches don't you guys remove the cable and then attach your normal cables? I was told not to keep the cable connected once Fastboot launches and to attach a normal cable for fastboot commands. Is this no longer true or has that never been true?
Click to expand...
Click to collapse
That's correct. Once the device is in fastboot, there's no need to use the cable anymore.
soupmagnet said:
That's correct. Once the device is in fastboot, there's no need to use the cable anymore.
Click to expand...
Click to collapse
Ok, ramsv94 told me that the cable is not "keeping" the device in fastboot. However once the device enters Fastboot couldn't he instantly remove the cable? And if so, if the device does not stay in fastboot mode once the cable is removed, how exactly is that the cables fault? No one has ever mentioned to me that the factory cable is responsible for "keeping" the device locked into fastboot mode. So now I am confused. Since that cable tested good over and over it makes it even more difficult to understand how it could be bad now. Lol...
I think I am going to completely rebuild my Bench Tester with a new female port this weekend. Just in case. Thanks soupmagnet for the quick response.
Sent from my Nexus 7 using Tapatalk 4
SkOrPn said:
Ok, ramsv94 told me that the cable is not "keeping" the device in fastboot. However once the device enters Fastboot couldn't he instantly remove the cable? And if so, if the device does not stay in fastboot mode once the cable is removed, how exactly is that the cables fault? No one has ever mentioned to me that the factory cable is responsible for "keeping" the device locked into fastboot mode. So now I am confused. Since that cable tested good over and over it makes it even more difficult to understand how it could be bad now. Lol...
I think I am going to completely rebuild my Bench Tester with a new female port this weekend. Just in case. Thanks soupmagnet for the quick response.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Here's the thing,
When the device is connected to the USB with the 1 & 4 pins connected, the device will boot into fastboot and stay in fastboot...period. With the stock bootloader, the device cannot start in fastboot, then start to boot normally. If FireFireFire were installed, however, the device would always start in fastboot mode for a few seconds, then proceed to boot normally. This function was added to help people in certain cases where the device is set to a normal bootmode, but without a working shell needed to enable fastboot.
There are two ways to determine whether or not the device is in fastboot. One, is by looking at the Kindle Fire logo at startup. If it is in fastboot, the Kindle Fire logo will be brightly lit and stay brightly lit. The other way is to check the system for what type of device is being connected to the USB. In Linux, this is done with the 'lsusb -v' command by checking the value of "bcdDevice". In Windows, this is done by looking at the device manager.
As astronomically improbable as it would be, ramsv94 has no way of determining, just by looking at the boot logo, that the device ever started up in fastboot and then began to boot normally with the stock bootloader installed.
Nevertheless, it's great that you're concerned about your customers, and your product, but you really have nothing to be worried about. You do good work, your cables are top quality, and this is the first one that I have ever seen that didn't work properly. Hundreds of Kindle Fire owners (including me) owe you a debt of gratitude for your service, and I can only hope that you continue to do so. :good::good:
soupmagnet said:
Here's the thing,
When the device is connected to the USB with the 1 & 4 pins connected, the device will boot into fastboot and stay in fastboot...period. With the stock bootloader, the device cannot start in fastboot, then start to boot normally. If FireFireFire were installed, however, the device would always start in fastboot mode for a few seconds, then proceed to boot normally. This function was added to help people in certain cases where the device is set to a normal bootmode, but without a working shell needed to enable fastboot.
There are two ways to determine whether or not the device is in fastboot. One, is by looking at the Kindle Fire logo at startup. If it is in fastboot, the Kindle Fire logo will be brightly lit and stay brightly lit. The other way is to check the system for what type of device is being connected to the USB. In Linux, this is done with the 'lsusb -v' command by checking the value of "bcdDevice". In Windows, this is done by looking at the device manager.
As astronomically improbable as it would be, ramsv94 has no way of determining, just by looking at the boot logo, that the device ever started up in fastboot and then began to boot normally with the stock bootloader installed.
Nevertheless, it's great that you're concerned about your customers, and your product, but you really have nothing to be worried about. You do good work, your cables are top quality, and this is the first one that I have ever seen that didn't work properly. Hundreds of Kindle Fire owners (including me) owe you a debt of gratitude for your service, and I can only hope that you continue to do so. :good::good:
Click to expand...
Click to collapse
thanks for the props bud... I am not worried any, I just get angry at myself when a tested good cable does not do its job just 3 days after I shipped it. you start to try and find another reason why this could be the case. A few hours ago I ordered two new Sparkfun micro-b breakout boards and I am going to redo my bench tester because this thing has been used thousands of times since late 2011. I test each connector before I solder on the wires, after I solder on the wires and after I hot glue the case together. That's three times during one cable build, so multiply that by 1100 cables and well you get the picture.
Anyway, I cant wait to see what happens when he gets the normal cable I built for him. lol
Can i use KFU to install FFF onto my Kindle or not?
ramsv94 said:
Can i use KFU to install FFF onto my Kindle or not?
Click to expand...
Click to collapse
Do you have access to fastboot?
This is where i am at right now. Kindle screen is lit bright so it is in fast boot mode. It is showing up on my computer as Android ADB Device. KFU says its offline. Attached Picture.
Trying to give new life to a friend's Kindle fire, but it seems to have a weird problem and she has no idea why. I've looked through the forums and I have found several posts that are close, but not the same (and the solutions won't work either) because the KF will just shut down the minute a cable is plugged in.
Here's the array of responses for the various attempts:
The device will charge if it is plugged in (USB cable and AC charger) but no light comes on at all under any circumstance. And it will shut down when plugged in to charge, and will not power up if on the charger. If it is just powering up and you plug it into the charger, the light stays on for a few seconds and the first screen that just says "Kindle Fire" shows up, then it shuts down.
The device will boot if no USB cable is inserted. The device will shut down when you insert a USB cable. The device will not boot with the cable plugged in (AC adapter or computer) and the power button never goes green. With a usb cable plugged into a computer, the computer will not recognize the device (and it shuts down immediately upon the cable being plugged in to the Kindle.) Also, if you just power it up, then plug it into the computer (just like with the power supply above) the light stays on for a few seconds and the first screen that just says "Kindle Fire" shows up, then it shuts down.
When I received it, I noticed that the case had been opened (or at least pried on.) Also, the USB connector was loose. I removed the board, re-soldered the connector (it appears to be intact now, but the connections are TINY so there is a limit to what I'm sure of) and reinstalled the board. Behaves the same way. I performed a 'power button' reset to the device and there was no change. I performed a factory reset and there was no change to the behavior.
Next I purchased the N2A fastboot cable thinking that would allow me to boot the thing and force a real reset (and install a non-kindle version of android), but I went through everything again and there is no change in how it reacts. The moment that USB cable gets plugged into the kindle, it shuts down. I think I followed the instructions properly (they aren't that complicated) but I'm having no success.
I've reset it a couple of different ways and several times with no change.
Any suggestions?
My goal is to get this thing working, install a 'non-kindle' version of android and get it back to her to use as an inexpensive tablet and e-reader, just not tied to Amazon (or BN).
Grant
gfhopper said:
Trying to give new life to a friend's Kindle fire, but it seems to have a weird problem and she has no idea why. I've looked through the forums and I have found several posts that are close, but not the same (and the solutions won't work either) because the KF will just shut down the minute a cable is plugged in.
Here's the array of responses for the various attempts:
The device will charge if it is plugged in (USB cable and AC charger) but no light comes on at all under any circumstance. And it will shut down when plugged in to charge, and will not power up if on the charger. If it is just powering up and you plug it into the charger, the light stays on for a few seconds and the first screen that just says "Kindle Fire" shows up, then it shuts down.
The device will boot if no USB cable is inserted. The device will shut down when you insert a USB cable. The device will not boot with the cable plugged in (AC adapter or computer) and the power button never goes green. With a usb cable plugged into a computer, the computer will not recognize the device (and it shuts down immediately upon the cable being plugged in to the Kindle.) Also, if you just power it up, then plug it into the computer (just like with the power supply above) the light stays on for a few seconds and the first screen that just says "Kindle Fire" shows up, then it shuts down.
When I received it, I noticed that the case had been opened (or at least pried on.) Also, the USB connector was loose. I removed the board, re-soldered the connector (it appears to be intact now, but the connections are TINY so there is a limit to what I'm sure of) and reinstalled the board. Behaves the same way. I performed a 'power button' reset to the device and there was no change. I performed a factory reset and there was no change to the behavior.
Next I purchased the N2A fastboot cable thinking that would allow me to boot the thing and force a real reset (and install a non-kindle version of android), but I went through everything again and there is no change in how it reacts. The moment that USB cable gets plugged into the kindle, it shuts down. I think I followed the instructions properly (they aren't that complicated) but I'm having no success.
I've reset it a couple of different ways and several times with no change.
Any suggestions?
My goal is to get this thing working, install a 'non-kindle' version of android and get it back to her to use as an inexpensive tablet and e-reader, just not tied to Amazon (or BN).
Grant
Click to expand...
Click to collapse
That sounds like a hardware related issue some kind of permanent or near permanent damage.
Thepooch said:
That sounds like a hardware related issue some kind of permanent or near permanent damage.
Click to expand...
Click to collapse
Thank you for the reply!
I'd agree that it could have a hardware component. I don't think it's fatal though since 1) it charges, 2) it powers up and works, 3) the wifi works.
I'd guess that it has something to do with the USB (to serial?) hardware but I don't know where to look on the board (other than tracing the traces but it's a multi layer board....)
I'm comfortable working (or rather 're-working') surface mount components. I have not see any interior/board layout info so I'd have no idea which chips to be looking at or testing.
Any suggestions about what area might be affected or pointers to schematic designs?
Thanks again,
Grant
gfhopper said:
Thank you for the reply!
I'd agree that it could have a hardware component. I don't think it's fatal though since 1) it charges, 2) it powers up and works, 3) the wifi works.
I'd guess that it has something to do with the USB (to serial?) hardware but I don't know where to look on the board (other than tracing the traces but it's a multi layer board....)
I'm comfortable working (or rather 're-working') surface mount components. I have not see any interior/board layout info so I'd have no idea which chips to be looking at or testing.
Any suggestions about what area might be affected or pointers to schematic designs?
Thanks again,
Grant
Click to expand...
Click to collapse
Grant you could attempt usb boot it acts different than any other form of booting the device and may actually fix what is broken do a Soupkit setup, and run usb fix parts install fff and twrp.
There is at least the potential that it could travel the course less traveled and rebuild partitions that may or may not be broken.
Soupkit is here http://forum.xda-developers.com/showthread.php?t=1850038 and you will use one of it`s components firekit.
Rather than attempting to do a physical repair to the board because the components are very small and packed so tightly together.
It`s a medium to high risk approach but if you desire it could lead to benefit.
Truthfully IMO some things are better left alone.
Thepooch said:
Grant you could attempt usb boot it acts different than any other form of booting the device and may actually fix what is broken do a Soupkit setup, and run usb fix parts install fff and twrp.
There is at least the potential that it could travel the course less traveled and rebuild partitions that may or may not be broken.
Soupkit is here http://forum.xda-developers.com/showthread.php?t=1850038 and you will use one of it`s components firekit.
Rather than attempting to do a physical repair to the board because the components are very small and packed so tightly together.
It`s a medium to high risk approach but if you desire it could lead to benefit.
Truthfully IMO some things are better left alone.
Click to expand...
Click to collapse
I think that is a good plan and I very much appreciate the advice.
The fire is nearly useless to her in the present state and she was going to 'toss it' when I suggested the alternative. So, at the very least it's an education for me, and at the very best I'm able to resolve the issue, learn something and get her a working tablet in the end.
If I can get it acting 'normally' that would tell me a lot.
I have a spare 8G thumb drive so I suspect I'm in good shape for tackling this and it will be an interesting change to run linux on something other than a raspberry pi or a server....
Thank you again!
Grant
gfhopper said:
I think that is a good plan and I very much appreciate the advice.
The fire is nearly useless to her in the present state and she was going to 'toss it' when I suggested the alternative. So, at the very least it's an education for me, and at the very best I'm able to resolve the issue, learn something and get her a working tablet in the end.
If I can get it acting 'normally' that would tell me a lot.
I have a spare 8G thumb drive so I suspect I'm in good shape for tackling this and it will be an interesting change to run linux on something other than a raspberry pi or a server....
Thank you again!
Grant
Click to expand...
Click to collapse
If you wish for help with the setup if we can get connected I will give you a hand I made hundreds of these live usb during the test phase of Soupkit there's a little to it but when it's setup it works well.
Thepooch said:
If you wish for help with the setup if we can get connected I will give you a hand I made hundreds of these live usb during the test phase of Soupkit there's a little to it but when it's setup it works well.
Click to expand...
Click to collapse
That would be great! How do we connect?
Grant
gfhopper said:
That would be great! How do we connect?
Grant
Click to expand...
Click to collapse
Teamviewer is the best way.
Hey folks, I have a N7 with some issues. I'm bashing my head against the wall on this one. I bought a 2nd gen N7 with a broken screen from some crook on eBay. He neglected to discuss it's other problems, however this is what I have. I replaced the screen, but even before doing so I found that a USB OTG mouse was not recognized (it works on my 1st gen), then I tried my little BT keyboard, BT wouldn't pair... Plug the tab into a PC and the PC completely ignores it. No device in device manager, I can even go to the port the tab is on is device manager and it shows nothing, not even current draw. The tablet does however charge on the PC, and it for some reason thinks that it is on AC charging, not USB. I have tried this on several computers with almost identical results. On a PC with USB 3 ports though, device manager sees it, just says that the device is unrecognized and may have a hardware problem.
So, I managed to get it to connect MTP one time by slightly twisting the USB cable. I then determine it must have a bad USB port, so I ordered some SMD USB sockets when I got other parts for a different project. I replaced the USB port tonight, and nothing changed, it is exactly the same. No data, always thinks it's on AC. On a whim I tried USB while in the bootloader, and it installs the fastboot drivers just fine and I am able to send fastboot commands.
After finding this, I figure it has to be something software or firmware related, so I flash it via fastboot back to bone stock. Reboot system and still no data connection, still thinks it's always on AC. I'm about at my wits end with it. I know there are other ways to move data to the tablet, but only having access to ADB via wifi is lameo and I happen to use USB host.OTG a lot.
Does anyone know what I am missing? I'm thinking it has to be something in the firmware at a level deeper than most the roms and images go. The PO is had it unlocked and cleanrom flashed. I have since tried AOKP, stock 4.4.4, now PA.
On a side note, if there is no fixing this SOB, do any of you know which of the flo roms have native wifi ADB? At least that will help...
Thanks,
Jason
No one has any ideas? No one else has had this issue? What it seems to me is that it is stuck in "USB fast charge mode" that's the only reason I can think that it would think it was on AC still even when on USB. I have tried three different kernels though now and enabled USB fast charge then disabled it, but it doesn't help.
Is it possible for someone to have put it in fast charge mode and made it stick regardless of kernel changes?
Just looking for ideas. Thanks folks!
Later,
Jason
I have exactly the same issue as yours! I couldn't connect my N7 via USB to PC. Gave me USB device not recognised error. I even fastory reset it. However, one time I did twist the USB cable and my device was recognised and it seemed to work fine during that day. I also managed to flash Android L developer's preview on top of that. The following day I started getting the same issue and haven't been able to resolve ever since. Even in fastboot, my device doesn't get recognised. It's the most frustrating thing ever!
Yeah, it definitely sucks. I was convinced it was the USB socket since twisting brought it alive that one time. However, I replaced my connector and it is the same. I then took it apart again and inspected all the traces and solder joints near the USB connector. I was still certain that the twisting meant it was a physical problem. It wasn't until much later that I found that fastboot worked.
I have done a ton of research trying to find an answer, but most everyone just pawns it off as a driver problem. I have tried every fix those people have offered, but it is never seen by the PC on USB 2, and only shows up as "device not recognized" on USB3. I have tried several different computers, but today I'm going to try an old XP machine. Several people seem convinced these issues are due to Win7. I'll let you know if I find anything.
Later,
Jason
jacampb2 said:
Yeah, it definitely sucks. I was convinced it was the USB socket since twisting brought it alive that one time. However, I replaced my connector and it is the same. I then took it apart again and inspected all the traces and solder joints near the USB connector. I was still certain that the twisting meant it was a physical problem. It wasn't until much later that I found that fastboot worked.
I have done a ton of research trying to find an answer, but most everyone just pawns it off as a driver problem. I have tried every fix those people have offered, but it is never seen by the PC on USB 2, and only shows up as "device not recognized" on USB3. I have tried several different computers, but today I'm going to try an old XP machine. Several people seem convinced these issues are due to Win7. I'll let you know if I find anything.
Later,
Jason
Click to expand...
Click to collapse
Try flashing 4.4.2 factory image. Maybe it starts working. For me, issues started 4.4.4+. currently I am stuck on Anroid L preview
Quick update, I asked Scott at Asus if he could give us any ideas, he said base don everything I told him that I had tried that it seems likely that it is a hardware problem with the USB board. I'm still not convinced, but the USB board is going to be my last resort.
Other than that, I tried the tab on a win XP computer and XP sees it as "unrecognized device" says that the USB needs unplugged/replugged and if that doesn't work to replace the device... I would think that the data pins are shorted or something, but mine works in fastboot, that is what has me stumped!
I'll try flashing 4.4.2.
Thanks,
Jason
Well, I just flashed back to 4.3.0 which looks to be the original software for this device. It did not behave any differently. I guess I am going to have to look into a new USB board. The things are expensive though, hopefully I can catch a decent used one for a good price. I'll let you all know if I order one and if it solves it.
Later,
Jason
New board is expensive. *sigh*
Yes they are, and I wouldn't trust ebay as far as I could throw it. I would hate to buy a used one and find out it has the same issue. I have another email into Scott asking if it is possible to buy parts direct from ASUS, and if so, what the board might cost. I'll keep you posted.
Later,
Jason
I heard back from Scott at Asus. They do not sell any parts. He suggested eBay... I guess I will start a saved search and see if I can catch one for a reasonable price. I can't see dropping $80 on a USB board. I guess if it doesn't fix it I could resell it... Still is retarded. This will make what this tablet has cost me much more than a brand new one Damn the crooked eBay sellers!!!
Later,
Jason
jacampb2 said:
I heard back from Scott at Asus. They do not sell any parts. He suggested eBay... I guess I will start a saved search and see if I can catch one for a reasonable price. I can't see dropping $80 on a USB board. I guess if it doesn't fix it I could resell it... Still is retarded. This will make what this tablet has cost me much more than a brand new one Damn the crooked eBay sellers!!!
Later,
Jason
Click to expand...
Click to collapse
Oh that's awful! I can't believe they don't sell replacement parts! I guess I have to live with a broken N7. I just hope Google pushes official L release OTA to devices running L preview.
I had a similar issue once. Turned out that MTP mode wasn't selected. Storage >Menu button > MTP should be selected.