Related
Hello XDA Community!
I made a post about this issue before, but have more details so hopefully someone can help me figure out this issue.
My phone even when unplugged from my PC continuously says USB Connected/ USB Debugging in the notification menu.
Also, when I try and reboot the phone, instead of booting even to the Vibrant logo screen, the loading circle continuously blinks on and off, without actually booting.
As I type this, I am not holding down the power button, and the loading circle is blinking on and off by itself....
I used to be able to turn the phone on into recovery mode in the past, but now when I try to reboot into recovery I get a big yellow picture that says "Downloading"
The only way the phone will turn on is if it is plugged in.
I am fairly certain that this reboot issue and the USB issue are correlated in some way.
Did anyone else have this issue with their phones? And if so, how did you solve it?
Another thing I have just discovered...
When the phone is on and idle, the USB Connection notification will constantly blink on and off, which is why I think the phone would do the same when trying to power on!
Is this a hardware issue or a software issue?
I have not flashed anything in a very long time before this issue started happening so I believe a restore is unnecessary .
Someone please help me! This is very annoying, not only do I have NO notification bar because of the constant USB Connection notification turning on and off, I cannot turn on my phone at all unless it is plugged in!
ACK!
Take it back
I carry the insurance, so personally if this was happening to me I would not even mess with it. It sounds like you have a genuine problem with the phone and it needs to be replaced.
If it is possible to do try a nandroid backup of your phone to make getting back to where you are on your new device easier. Then take your phone back to stock with the recovery image here -->
http://forum.xda-developers.com/showthread.php?t=734475 (Thank you justanothercrowd)
One you have a stock device see if you are still having the issue. If you are take it back as defective. Even if you don't have the insurance, that sounds like a factory defect and should be covered by the factory warranty. The insurance just makes the process easier and makes sure they just give you a swap out at the store rather than having to wait for repairs. It also covers things the warranty does not, such as screen breakage - which is the specific reason I carry the insurance.
Ah crap wish I had insurance.... Do I have to do that whole odin procedure or is there a one click un root procedure as well?
Sent from my SGH-T959 using XDA App
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
I actually have not had reason to go back to stock, or even use odin yet at this point. My only roms were .zip files that I flashed via clockwork recovery.
I would say that your best best it to just follow the instructions on justanothercrowd's thread very carefully and deliberately. You are already having issues with reboots and your USB port, so this is not the time to deviate into experiments.
So to cut you off and just answer you next three questions:
Q) Can I just . . .
A) No! Just follow the directions exactly.
Q) But can I . . .
A) No! Just follow the directions exactly.
Q) Do I have to . . .
A) Hey look, Just follow the damn directions exactly!
Sorry, I can't help much beyond that. You chose to modify your phone and risk that you would not have issues, just like the rest of us here. In your case you did have issues. Now you have to get it back to stock so they don't have any reason to claim you caused this or that your warranty is void. I hope all goes well and it works out for you. Let as know and keep us posted. Good luck.
Lo N Slo said:
Nevermind i just read through that link you posted. So when i go to a t mobile store do i have to unroot or can i just hide my root applications until i get a new phone?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
We must have been typing at the same time LOL.
There is a thread on unrooting, and basically it is just deleting a few things. After doing this you should not have any non-stock applications on the phone and there would be no reason to think it was rooted unless they went digging on the file system. Personally, I would delete those telltale files just in case, it looks a little suspicious to bring in a phone that looks like it has not been used since you bought it, but they have no proof you did anything and you can claim that you first did a factory reset to see if it would fix the problem.
Just want to keep this thread going, as I am having the exact same issue as the OP as of today. It happened out of the blue, and I haven't flashed anything new to my phone since JI6 was released, other than that, it's just a stock, rooted phone.
Hoping someone has an idea, but I will likely get it replaced under warranty, since the GPS has never worked either.
damnit damnit damnit I really wish I had warranty.
Random question about clockword mod recoveries.
If I were to do a backup right now, and save that file to my computer, could I restore that file later on a different phone after I root my replacement?
I don't have that many mods flashed, and I know all of the apps can be synced, but still it would be sooo convenient .
I believe that is how it works, so yes. It should be no different then when you clone a hard drive to put the image on multiple computers for easy distribution.
It is (just like the cloning metaphor) hardware specific. Just like I could not purchase a upgrade computer and expect a cloned image to work, don't expect to create a Vibrant backup and restore it on a Captivate.
That said, you should be able to restore your backup to new (identical) hardware.
By the way, what is the warranty on these? I thought it was a year for defects. I didn't think the Vibrant had been around long enough yet for anyone to be off warranty.
it should be a year, but there was also the option for a purchased warranty. I did not purchase a warranty, so I should be good on just my manufacturer's defect warranty
Being discussed here:
http://forum.xda-developers.com/showthread.php?t=817643
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
symbiiote said:
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
Click to expand...
Click to collapse
What ROM are you using. Sometimes its just a kernel problem, I've been testing different kernels with different ROMS, and some of them wont let you turn on wifi. Try a different ROM then.
Hey thanks for the replie, ive used pac rom 4.2.2 and cfx rom 4.2.2
symbiiote said:
Hey thanks for the replie, ive used pac rom 4.2.2 and cfx rom 4.2.2
Click to expand...
Click to collapse
Try a stable-ish rom. Like Dark Unicorn Resurrected --->http://forum.xda-developers.com/showthread.php?t=1716558 (Second Post). Or Synthetic.Nightmare's AOSPX -----> http://forum.xda-developers.com/showthread.php?t=1684835
If that doesn't work try going to a stable GB rom (Like CyanogenMod 7.2.0) If that doesn't work then just donate your phone to someone that could use the parts
I tried cm7 and no go, click on turn wifi on and it reboots... x(
Sent from my A500 using Tapatalk HD
Awwwww man. That sucks. If it won't work on cm7. Then try a GB sense rom. If it doesn't work there. Revert to stock all over again. If it won't work there. Then your screwed man. Hope it works though.
Sent from my myTouch 4g using xda app-developers app
N_otori0us_ said:
What ROM are you using. Sometimes its just a kernel problem, I've been testing different kernels with different ROMS, and some of them wont let you turn on wifi. Try a different ROM then.
Click to expand...
Click to collapse
symbiiote said:
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
Click to expand...
Click to collapse
N_otori0us_ said:
Awwwww man. That sucks. If it won't work on cm7. Then try a GB sense rom. If it doesn't work there. Revert to stock all over again. If it won't work there. Then your screwed man. Hope it works though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
zygh0st said:
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
Click to expand...
Click to collapse
Wow, thanks for the detailed reply. ill defiantly try this out, ill get back to you. [Update] ive checked and theres no firmware folder in system, and in system/lib/modules there is a bcm4329.ko file. (im on CM7)
Are you interested in a trade? I cant use phone with no Wi-Fi
Sent from my A500 using Tapatalk HD
Fixed my wifi!
symbiiote said:
Are you interested in a trade? I cant use phone with no Wi-Fi
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
Just FYI, I was in the same boat. I bought a used and heavily abused Mytouch 4g just to pull the motherboard and use it to fix my wife's hard bricked (no power whatsover) mytouch. It worked fine for a day or so, then started having random reboots and wifi failure (i.e. on the stock ROM it would cycle on & off repeatedly, then reboot, and on CM7 it would just not turn on, or occasionally show 'error' if I forced the driver to load.
I tried everything: rooting and installing multiple ROMs, multiple kernels, flashing to stock unrooted, flashing to stock Froyo unrooted, and it never resolved. In the dmesg I would get an error "dhsdsio_probe_attach: si_attach failed!" every time I tried to enable wifi. I even tried different radios, not really expecting much, but just to cover my bases. I took the phone apart multiple times looking for loose cables, damaged ribbons, etc, but never found anything, although occasionally wifi would return for a few hours, then disappear again. Often it came back right after flashing a new rom or factory reset, but even without installing any apps, it would eventually fail, so it wasn't an app issue.
Then... I discovered another thread where people with the Motorola Atrix discovered that a well placed piece of plastic would resolve their failing wifi by applying pressure in just the right spot - most likely due to a loose or failing solder connection. I dug around online and found a photo showing exactly where the Broadcom 4329 chip is in our phones (it is right behind the microphone on the underside of the motherboard), and discovered that by squeezing hard with one finger just to the left of the trackpad, and the other directly behind on the back of the phone, I could get wifi to enable and scan. Letting go would drop the scan. Give that a shot and see if it makes a difference. If so, read on...
I found that people with iPhones with a failed Broadcom 4329 module (same chip) had had some success in reflowing the motherboard. Not having any expertise in that area, I was surprised to find that a common solution was to use an oven to heat the motherboard up in order to soften the solder and do a poor-man's "reflow". I can't post links yet, but if you google "iphone WiFi Repair: Oven Fix" you'll find a great video describing how to to it and why it works.
So I went for it. I took it apart one last time (plenty of take apart videos online to show how this is done), pulled out just the motherboard, stripped everything off that wasn't permanently attached (including removing/unlatching the metal covers on front & back & all ribbons), got a cookie sheet and some aluminum foil, put the foil loosely around the rest of the motherboard (shiny side out) and ripped an opening just around the chip. Then raised the mother board off of the cookie sheet with little foil balls (per instructions online for laptop reflowing) and baked at 360 for 8 minutes, shutting off the heat and cracking the oven door slightly for 20 minutes to cool it slowly, then open all the way for another 20 minutes, out, reassembled, and now I have a working wifi chip.
Crazy, yes, but if you are about to toss the phone, it might be worth a shot as a last resort. Not a 100% success rate when you search online for people trying this, some people have destroyed their phones, but it worked for me!
Keep in mind, I just did this about 2 hours ago, so there's still the possibility it was a short-lived solution. I will try to check back in here in a week or two to confirm that it 'took'.
UPDATE 1: One day later, and zero reboots, 100% reliable wifi. It has never been so stable.
zygh0st said:
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
Click to expand...
Click to collapse
I think WiFi should have worked on cyanogen7 or a sense Rom....
That's why I figured it was a hardware problems.
Also can you compile kernels for me? I don't know How to properly. :'(
Sent from my HTC Glacier
A little more info in case it helps anyone diagnose a different issue, below were some handy-dandy commands I used to check the driver situation:
Try to turn on wifi (obviously it will fail)
Then in terminal emulator (download one from the play store if not installed), type
$ lsmod
if nothing is returned, the driver isn't loaded. If you get "bcm4329" listed as 'live', then your driver is loaded. Its probably not a driver compatibility problem (not 100% on that, since I'm new to all of this).
If your driver isn't loading, it still might not be a bad driver. It might just have been because the chip wasn't detected. Type the following to give permissions and manually load the bcm4329 driver:
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# insmod /system/lib/modules/bcm4329.ko
if it returns an error/fail, you've got the wrong bcm4329.ko file/driver installed or maybe a corrupted file. Try reflashing the ROM, or replacing the bcm4329.ko file with one that is compatible with the ROM/kernel you are using.
If not, then
# exit
then check again with
$ lsmod
If the driver shows up now, then at least you know it can load. Then try connecting again. If it still doesn't connect, this might help the process of elimination.
go back to terminal emulator immediately after trying to connect
type in dmesg
scroll up a little ways and look for the a series of phrases 'wifi_set_power: 1', etc. If you see it trying to connect, then a few lines down, see the error "dhdsdio_probe_attach: si_attach failed!" shortly after it loads the Dongle Host Driver, then it isn't finding the chip. You probably have the same loose connection problem I had (above), and may have to do something physically to your phone if you want wifi back. I'd try the 'squeeze test' first to confirm before taking it apart.
I hope that is helpful. I spent way too much time figuring this out, and would have loved to have found this info somewhere in one spot online.
its def a kernel problem because i rely on wifi everyday since i tether to my pc and once i tried a kernel that should fix headphone heat up. didnt know if it did but it broke the wifi. would not switch on so i switch back to a next kernel n wifi works. roms like carbon, cm10.2 everlov gives kernel with wifi working. hope this help if someone end up in this boat again
http://forum.xda-developers.com/showpost.php?p=41652708&postcount=3
Just a quick link to N_otori0us_'s posts on kernels if you wanted to try other ones.
tonyMEGAphone said:
http://forum.xda-developers.com/showpost.php?p=41652708&postcount=3
Just a quick link to N_otori0us_'s posts on kernels if you wanted to try other ones.
Click to expand...
Click to collapse
There's more kernels for Gingerbread in the second post too. The one's in the 3rd post were just common things I've seen people asking for,
my friend just gave me a new motherboard, works fine now.
followup on the oven solution
After a week - wifi still working, but not without some intervention. It crapped out again after 2 days, and I re-baked it (the first time I chickened out and didn't keep it at 385 for the full 8 minutes). It has stayed fairly consistent, but started acting up again over the weekend, so I grabbed a tiny square of some sort of soft compressable insulation material from a tablet I was fixing, and placed it right over the broadcom chip to keep it compressed and applying a little pressure. So far that has held and worked well.
I have a feeling its a matter of time before this eventually fails again, too. I don't think there is anything that can be done to permanently fix lead-free solder paste that has started to develop micro 'whiskers', according to what I've dug up online. Reflowing and pressure seem to work temporarily to re-establish a connection. If I knew how to remove the solder and re-apply a solder paste with some lead content, I'd do it. That would probably be a permanent fix. That or a new motherboard ala simbiiote.
[UPDATE 2] Killed it. Apparently re-baking every few days at slightly hotter temperatures eventually will fry your motherboard. Don't go past 400 degrees, and use an oven thermometer to get an accurate idea of what the real temp is. Now back hunting for broken ebay phones to replace the motherboard. Oh well, it was good while it lasted.
I have a rooted Nexus 7 running JDQ39. It is no longer recognized by my laptop or desktop, regardless of the cable I use. I have used the same laptop/desktop for months without issue. I think it's a hardware failure but I'm open to suggestion.
Anyway, I bought it through the Playstore so I called them for support and they said they could see that I "may be using a rooted device" and told me that I would have to contact the manufacturer or carrier but if unroot and still encounter the issue they will be glad to "take a look". They followed the conversation with the email below.
So it's interesting (but not surprising) that they can tell remotely.
Anyway, any suggestions on how to get back to stock/unrooted without a PC connection?
Thanks
[email protected]
X:XX PM (7 minutes ago)
to me
Hey there Xxx,
Thanks for contacting Google Play! According to our records, it appears you may be using a rooted device. Unfortunately, our ability to troubleshoot issues with rooted devices is limited. They may have altered functionality depending on how the device has been modified and we're not able to see what's happening with the device. For assistance with rooted devices, we recommend contacting your device manufacturer or carrier. However, if you unroot your device and still encounter this issue, please let me know and I will be happy to take a look.
If your device isn't rooted, please let me know, and I'm happy to see what I can do to assist you further. Thank you for your understanding.
Thanks,
Click to expand...
Click to collapse
I dont know about "calling in". But if you downloaded any app requiring root from the play store to that device, it would be a dead giveaway. Titanium backup, super su, rom manager............and the list goes on. That is most likely the reason the last line says "If you're not rooted". They are not "calling in", but simply looking at thier records (app history).
To the main problem, have you tried an alternate cable? I see you have tried multiple pc's, so the cable is the next step. That possibility needs to be eliminated before you can move on to a hardware and/or software failure.
Sent from my Nexus 7 using xda premium
junksecret said:
I have a rooted Nexus 7 running JDQ39. It is no longer recognized by my laptop or desktop, regardless of the cable I use. I have used the same laptop/desktop for months without issue. I think it's a hardware failure but I'm open to suggestion.
Anyway, I bought it through the Playstore so I called them for support and they said they could see that I "may be using a rooted device" and told me that I would have to contact the manufacturer or carrier but if unroot and still encounter the issue they will be glad to "take a look". They followed the conversation with the email below.
So it's interesting (but not surprising) that they can tell remotely.
Anyway, any suggestions on how to get back to stock/unrooted without a PC connection?
Thanks
Click to expand...
Click to collapse
I'd agree with the person above: they likely flagged some root-requiring apps you have on your device and went by that. Google's policy on roots is pretty forgiving, though, to say the least.
In any event, there are some on-device methods you could pursue, but we need to know more about your setup on that side as well. In a similar vein as to what previous poster asked (namely about testing computers and cables), could you link us the method you used to root your device and also post what recovery you're using (stock, TWRP, CWM, etc.) and if you have your bootloader unlocked?
Rirere said:
I'd agree with the person above: they likely flagged some root-requiring apps you have on your device and went by that. Google's policy on roots is pretty forgiving, though, to say the least.
In any event, there are some on-device methods you could pursue, but we need to know more about your setup on that side as well. In a similar vein as to what previous poster asked (namely about testing computers and cables), could you link us the method you used to root your device and also post what recovery you're using (stock, TWRP, CWM, etc.) and if you have your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for the reply, I think I've exhausted the cable and usb port/pc/drivers as the cause. I actually now remember I hooked it up to my stereo and plugged into a cheap charger and got a pretty good spark at the micro usb and the tablet shut off. I left it plugged in and powered back up and thought all was fine. I now think that may have fried something in the micrco usb although it does charge thru it.
I think I rooted using wugfresh's rootkit, this is my 3rd N7 so not positive. I do have the bootloader unlocked and am running CWM Touch recovery.
Any links to a no-pc back to stock would be great!
Thanks
junksecret said:
Thanks for the reply, I think I've exhausted the cable and usb port/pc/drivers as the cause. I actually now remember I hooked it up to my stereo and plugged into a cheap charger and got a pretty good spark at the micro usb and the tablet shut off. I left it plugged in and powered back up and thought all was fine. I now think that may have fried something in the micrco usb although it does charge thru it.
I think I rooted using wugfresh's rootkit, this is my 3rd N7 so not positive. I do have the bootloader unlocked and am running CWM Touch recovery.
Any links to a no-pc back to stock would be great!
Thanks
Click to expand...
Click to collapse
Sent from my Nexus 7 using xda premium
Now we are getting somewhere. It seems you may have shorted a data pin when you plugged it in. I personally never use cheapo chargers. You could try replacing the USB port. If i am not mistaken, it is not soldered to the motherboard, but instead is soldered to its own harness and connected to the mobo via flex cable.
Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal
sooooooo, does nobody have an idea lying around somewhere?
Fachtal said:
Hello everybody,
- On monday i ran into a strange problem with my N910F. At first it was just not charging whatsoever.
- after the phone ran out of power, i attempted to charge it which gave me a brick with a black screen, vibrating short every two seconds
- Fine by me i thought, went and got a replacement battery (after checking simple stuff like the physical state of the battery (normal) and killing the batterystats (which i heard both yay and nay about so i decided to give it a try).
- Replacement battery charged overnight on the USB Port of my computer (2.0, for the completionists) went smooth (didn't turn it on, just had this bubble animation of charging).
- Turned it on this morning (booting apparently took 3% off my battery) and all well so far.
- finally in my chair at work i plugged it into my power cable (genuine Samsung FastCharging adapter that came with the phone itself) and nothing happened
- tried another adapter (some cheapo 1A adapter) which started charging around 10secs after connecting but decided to stop charging after a couple of minutes
- some shaking and gentle knocking brought back the charging symbol for some seconds, seemed like some loose contact or a broken cable so i felt fancy and plugged the very same cable (the one originally shipped with the phone) to my laptop. started charging instantly and no shaking or knocking stopped this (so no loose contact or broken cable at all)
This is the story until now, put together as complete and organized as possible. For now i'm stuck to charge my phone on the laptop or computer which seems to work. In this progress above i tested around 7 chargers, 3 laptops, 2 computers, 10 cables and 3 screens with both batteries, although the workaround i have now is only tested with the genuine cable as i was just done with testing for the night.
Now for my questions (apart from a touch with the magical fix-everything tool):
- What i see as possible causes based on my very shallow knowledge are either the microUSB port on the phone or the power distribution unit. Anyone has an idea what to check?
- As i have no idea how deep the OS goes, could it be a software issue by any chance?
Even though the device is only ~9 months old, I don't like the idea of going through Samsung for this one as i tripped KNOX already.
Hope there's still hope for me
Cheers,
Fachtal
Click to expand...
Click to collapse
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app
Tripping Knox does not necessarily mean that you've lost warranty.
Battlehero said:
You seemed to have tried using the cheap charger which allowed you to charge after shaking it a bit, have you tried purchasing a new genuine charger?
Sent from my trltexx using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.
Fachtal said:
I tried around 7 adapters (from cheap ones to genuine galaxy S3, Note2, and Note4), around 10 different cables (again, from cheap ones to genuine samsung cables), 3 Laptops (again with all cables), 2 computers (all cables) abd one of those mobile charging battery things.
The only thing that works is either the genuine cable on my computer or the same cables on my screen at work.
@geevh that's news to me. As far as i heard is tripping know equal to losing warranty.
Click to expand...
Click to collapse
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app
Battlehero said:
Have you tried to flash stock firmware, in case it's the kernel?
KNOX warranty shouldn't void your warrant in the EU as I have gotten two knox tripped devices repaired from Samsung before.
Sent from my SM-N910F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal
Fachtal said:
I just flashed the official ROM using Odin. Had some problems getting the phone connected while in DL mode (didn't work at all while in normal android mode).
This seemed to be a dirty flash (already was on stock Rom, just put CWM on, rooted the phone and replaced the kernel to have SELinux permissive for Viper4Droid) as it didn't go through the setup process and was like before.
Anyway, charging still doesn't work. Is there anything else I can test? I'm nearly at the point where I migrate back to my old SGS3 and have the N910F sent to the carrier (well, in the end it will go to Samsung) to get it fixed.
Thanks about the whole Knox false knowledge.
Cheers, Fachtal
Click to expand...
Click to collapse
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck
Battlehero said:
I would just give the device in for repairs but make sure to flash a full stock rom and factory reset before giving the phone, since you have already tried everything else.
Good luck
Click to expand...
Click to collapse
Well, flashing stock ROM seems to be slightly less relaxing than I thought. It feels like I have to connect the phone to the pc, put it on the table in a very specific position/way and then hope that it doesn't disconnect halfway through flashing...
This has become quite an adventure so far and I hope I'll get this done so i can get rid of this very expensive paperweight
Thanks for all the help so far, I guess I'll add the explanation from my carrier/Samsung as soon as I (hopefully) get my device back.
Fachtal
PMIC or Charging IC is probably broken on the mainboard, i hear more N4's have this problem.
Best is to send it for warranty or let the components be replaced by a "good" repair shop.
Most service centers don't check knox status so i would go for that, if all fails take it for repairs if the costs are not too high.
Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal
Fachtal said:
Hi guys, back for a rather unexpected "solution"
When i finally freed up some time to actually get to the carrier shop to get my phone fixed, I was in for a rather embarrasing experience.
The lady in the shop pulled a charging cable and an adapter out of a box, plugged my phone in and it suddenly charged as if nothing ever happened. Now, some time later, it still works perfectly fine, as if there never were problems...
I have absolutely no idea on what happened. Before going to the shop i obviously flashed the stock rom yet again (with the usual wipe user data/cache/dalvik procedure).
Now, on what i had when the problems started: stock BOC5 ROM, touch CWM, rooted and with a custom kernel for SEAndroid permissive (emotion something i believe the kernel was called). Now during my rather extensive troubleshooting I actually flashed the stock ROM at least once and the issue persisted, which is why i just stood there, staring on my charging phone, my jaw somewhere on its way to the ground, unable to form any proper words :silly:
So basically, does someone have a possible explanation to clear this up? If not, I'll consider this thread solved i guess^^
In the meantime, I downgraded to Stock 4.4.4 with CWM, root and xposed (which i really missed on Lolli) and I'd say I'm happy with this :victory:
Fachtal
Click to expand...
Click to collapse
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.
ludoke said:
It's sound strange but a couple of years ago i read somewhere,forgotten where and about the specific device. The thing was that phone wasn't charging eather ,and now it comes.....the solution was turnig around the charger in te power socket.
Click to expand...
Click to collapse
this indeed sounds strange. And honestly, i didn't pay attention on the orientation of the power adapter (although my stock samsung one is always in the same orientation because the cable goes out on the side (which means it worked in the same direction as it didn't before).
The only even remotely considerable approach would be that the custom kernel along with this synapse app somehow screwed with the power intake and i forgot to wipe everything when i first flashed stock over it, meaning that synapse still had its fingers in the system screwing around with that.
But then again, as I seem to be the only one with this problem and this custom kernel had more than just a few users I don't think this is the way it went (I don't even use an unusual collection of root Apps which could cause some sort of malfunctioning combination of effects).
I had a few evenings just thinking about this and draw some simple mindmaps/schematics to make some sort of a sense...
Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.
Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.
XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/
XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha
angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.