Related
Only had mine 3 weeks and its broken already. I have been using a desktop charger and have not been forcing it in at all, not once, I have always been very gentle inserting it it, anyway it no longer charges, it looks like the connectors have pushed themselves back so they are not flush anymore and thus no longer connecting to charge or sync.
Not happy about this at all, I had my desktop charger for my HD2 for 18 months with no problems at all, this suggest a very weak connector.
!!! BE CAREFUL !!!
Going to call in at Phones4you and see if they will swap it, I don't hold out much hope though.
Wow bad luck man, but really you don't need the F word to express your frustration.
stoolzo said:
Only had mine 3 weeks and its broken already. I have been using a desktop charger and have not been forcing it in at all, not once, I have always been very gentle inserting it it, anyway it no longer charges, it looks like the connectors have pushed themselves back so they are not flush anymore and thus no longer connecting to charge or sync.
Not happy about this at all, I had my desktop charger for my HD2 for 18 months with no problems at all, this suggest a very weak connector.
!!! BE CAREFUL !!!
Going to call in at Phones4you and see if they will swap it, I don't hold out much hope though.
Click to expand...
Click to collapse
was it an official desktop charger or 3rd party?
DO a factory reset using code *2767*3855#
(please not this will wipe everything including built in memory, so do backup before you proceed. Backup possible by moving content of internal memory to SD card by copy paste in file manager)
I had a problem when my phone stopped charging after I upgraded firmware, It would also launch Connected to computer screen when it wasnt . Thought its dead.
Did factory reset using this code and its working flawlessly ever since. Seems to be some kind of bug which happens out of nowhere as 2 people I know have experienced this after upgrading to KE2.
stoney73 said:
was it an official desktop charger or 3rd party?
Click to expand...
Click to collapse
I was going to ask exactly the same thing...
I think the OP means that the micro usb receptacle has come away from the board and has been pushed back into the body of the phone. I hope this is not going to turn out to be a common problem as it's something that seemed plague to the Nokia N900 and it took ages for Nokia to acknowledge a design/production fault.
great advice, now it wont boot at all, just goes round in circles....
F**cked.....
anyone got any ideas?
Hi, the charger isnt really the issue, i haven't had any problems inserting the phone into the charger, ie no resistance which suggests to me it was week or loose and has gradually pushed it self back over the last 2 weeks since I have had the charger. If thats the case it would have done this with any charger or cable.
Just spoke to phones4you, they are going to exchange it for me, they didnt even grumble after I told them what happened which I thought was odd, heading off now to pick it up.
Will be interesting to see if your wifi is any better on the new phone stoolzo. Maybe you could let us know. Thanks.
good old phones4you
got it already, yes I really have. Phones4you are just round the corner in PC world. Will check my wifi tonight and report back on the other thread.
Please change the thread title. All type of people view xda.
Sent from my GT-I9100 using XDA App
remove and reinsert battery
i had this issue when running custom kernels. somehow doesnt happen with stock.
issue happens like this:
u go to bed while charging
u wake up and the phoneis off or very hot with battery and temperature warning
u reboot and it doesnt reboot, doesn't boot, just goes in circle battery display/reboot cause it doesnt seem to charge neither have enough power to boot.
removing battery + cable then putting both back = it boots again and charge normally
stoolzo said:
Hi, the charger isnt really the issue, i haven't had any problems inserting the phone into the charger, ie no resistance which suggests to me it was week or loose and has gradually pushed it self back over the last 2 weeks since I have had the charger. If thats the case it would have done this with any charger or cable.
Just spoke to phones4you, they are going to exchange it for me, they didnt even grumble after I told them what happened which I thought was odd, heading off now to pick it up.
Click to expand...
Click to collapse
************************************************************
Yeah, did all the usual things, I have bricked phones before and always managed to turn them around but we have no CMR to flash anything from ROOT/SD so when it wouldn't boot after a factory reset I knew I was in trouble
The MHL port being loose was the tell tale sign of a fault as I hadn't misused it at all. When I compared it to my new phone I got today it was defo a little further back, just enough to prevent it connecting.
Good old phones4you, fault report to phone exchange in under an hour, impressive.
Just in case the charger had anything to do with this I am going to get rid, dont think it did but I don't want to risk it.
its this one:
http://www.mobilefun.co.uk/desk-dock-for-samsung-galaxy-s2-i9100-p29488.htm
Really weird.. Out of nowhere , the bottom right corner of my screen has become almost totally unresponsive to touch. The L and the backspace button on my keyboard are nearly unusable.. Anyone have any idea as to how I may be able to fix this? Its like there is a 2 inch by 1cm gap on my touch screen that doesn't respond to touch.. Thanks guys
Sent from my Nexus 4 using Tapatalk 2
Warranty exchange..
Wish I could... Bought the phone through tmobile and I'm getting the run around.
Sent from my Nexus 4 using Tapatalk 2
I have the same problem, but its a band across upper 1/3 of the screen causing weird typing and such, but only in portrait.
Sent from my Nexus 4 using xda app-developers app
Nexus 4 touch screen defect (dead zone, phantom touch)
I have the same problem, I have a permanent ~1cm tall dead zone spanning the width of my Nexus 4, right about the location of the SIM card tray.
On occasion it is not a dead zone, but rather a "very haunted zone" where there are MANY phantom clicks/drags on different areas of the dead zone in VERY QUICK SUCCESSION. When this happens I have found that constantly resetting the phone (maybe 5-6 times) until it returns to normal (see: dead zone) is the only way to fix it.
That whole situation can take up to an hour to sort out, especially since during the orgy of phantom clicks/drags on the dead zone, the touchscreen is essentially a write off and turning it off is next to impossible, meaning that my phone is bricked for a portion of the day. This happens arbitrarily about once every 5 days.
I purchased my phone from Australia one month ago. Was not aware of any problem until I had returned to where I am currently living in China. I'm absolutely gutted that my first android experience has soured, especially after shirking apple because of (living through years of) their own hardware/software issues.
Why can't I just have a quality, working piece of tech?
So far the warranty options available:
1) Store I bought it from says: Send it to LG Australia (1 non-international warranty)
2) Google says: No google store purchase number, no return
3) LG China? - Can't find any information about LG warranty claims in China.
If I send it back to Australia for repair I will be waiting without phone for weeks, AND I'll get taxed at least $100 by greedy China customs when the phone comes back in. (not to mention the postage there and back)
The problem has become worse and worse as have used the phone. Can any of ye android bros possibly offer any sort of advice or even better, a fix, for solving this problem?
tobiakazmer said:
I have the same problem, but its a band across upper 1/3 of the screen causing weird typing and such, but only in portrait.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have this right now. It's about a third of an inch located near the middle of the screen. It spans the entire width of the screen.
I sure hope it's just a software and not a hardware issue. I bought this in the US and I am now halfway around the world.
I had the same problem. For me it was right where the middle row of keys on the keyboard are or where the ring is on the lock screen.
5mm thick bar across the screen. I sent it back to be fixed and it's been fine ever since touch wood.
They replaced the entire screen on mine. This is definitely a hardware issue. I did a factory reset before I sent it back and the problem was still there.
Digitiser is too close to surface I think causing problems.
Sent from my Nexus 4 using xda app-developers app
Guys i have the same problem since this morning.
I tried everything change roms 4.3 / 4,4 and finally returned to stock.
Nothing worked although i had never the same problem before.
So i tried my last chance. Changed radio image with the help of a Toolkit of our forum ( thanks N-Cry Toolkit )
It seems to be fixed for now , i just rebooted.
Hope it will be ok and you could fix yours too
Hey!
denpeirazei said:
Guys i have the same problem since this morning.
I tried everything change roms 4.3 / 4,4 and finally returned to stock.
Nothing worked although i had never the same problem before.
So i tried my last chance. Changed radio image with the help of a Toolkit of our forum ( thanks N-Cry Toolkit )
It seems to be fixed for now , i just rebooted.
Hope it will be ok and you could fix yours too
Click to expand...
Click to collapse
This really worked for you?
em.faris said:
This really worked for you?
Click to expand...
Click to collapse
Well it worked. I cant understand the reason yet but it keeps showing after some time. I m trying changing roms / baseband / bootloader and return to stock trying to identify when it doesnt work and why. It's really annoying and i m tired of it.
denpeirazei said:
Well it worked. I cant understand the reason yet but it keeps showing after some time. I m trying changing roms / baseband / bootloader and return to stock trying to identify when it doesnt work and why. It's really annoying and i m tired of it.
Click to expand...
Click to collapse
well for me its a hardware issue, but since you said it worked fine when you changed the baseband it really surprised me up
actually happy, cuz there are many users who has this problem.
do keep us updated when you find your fix for this. will be of much help may be in future if something goes wrong on my N4
em.faris said:
well for me its a hardware issue, but since you said it worked fine when you changed the baseband it really surprised me up
actually happy, cuz there are many users who has this problem.
do keep us updated when you find your fix for this. will be of much help may be in future if something goes wrong on my N4
Click to expand...
Click to collapse
Had the same touch screen issue for months; had a dead spot in the middle of the screen that would interfere with browsing and games.
Updated OTA to stock KitKat just last week and the problem went away. Hope you guys get lucky as well. :cyclops:
Possible Deadzone fix!
capcanuck said:
Really weird.. Out of nowhere , the bottom right corner of my screen has become almost totally unresponsive to touch. The L and the backspace button on my keyboard are nearly unusable.. Anyone have any idea as to how I may be able to fix this? Its like there is a 2 inch by 1cm gap on my touch screen that doesn't respond to touch.. Thanks guys
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ok... i created an account here because ive had this same problem for the past month at least, but I think i found a fix. It may take a few people to try it as well to see if its definitive.
I have the same 1cm high deadzone spanning the width of my device just lower than halfway from the top.
My troubleshooting led me to this: If its hardware, its only because the software is telling it something it shouldnt be. I'm sure nothing is broken (i.e., from being dropped, etc.) Something is wrong, for sure, but not broken per se.
I took screen shots of temperature and voltage (using CPU-Z app) trying to figure it out. I paid attention to when it happened and when it did not. I boiled it down to two possibilities: temperature and/or voltage (i can explain how i came to this conclusion if you want... would take a bit more explanation).
I charge my phone with the charger plugged into the wall typically. I live in asia so the voltage is a lot higher (but within the appropriate range of the phone). Yet, lately when i go to sleep, I plug my phone into my laptop to charge, rather than the wall... when i wake up the problem isnt there. About 2 hours later or so the problem comes back.
I tried this for a week (charging my phone with my laptop) and the problem is dissipating. As quickly as it escalated (getting gradually worse) it is now getting gradually better.
Try it and see if it works for you. At night when your phone is nearly dead, charge your phone with your USB port attached to your laptop. Try this for a few days. Maybe it will help. Im still troubleshooting specifics to see if it is definitive.
UPDATE: today, the day of writing this, i haven't had the problem at all and it's been nearly 7 hours and the 3rd consecutive night of charging with USB on my laptop.
Nexus 4 - 4.4.2
My dead zone appeared post-Lollipop update
I created an account for the purpose of also reporting this "dead zone" issue.
I elected, on the Tuesday before Thanksgiving, to opt into the OTA Lollipop update. During the process of updating, I noticed my battery drained all the way to 0, while I thought nothing of it.
When the update was complete, I started to notice a dead zone in the middle of my screen when in portrait mode.
Actually, my dead zone spans an inch of my screen.
I have performed several hard resets, soft resets, learned about the ADK & adb, and downgraded all the way to 4.2.
I took the phone, this morning, to a cell repair shop and the technician said that it's not a hardware issue (although I'm not sure he's right).
So, that's my story. If I find a solution, I'll post it.
these dead spots IMO , are because of bad battery or bad charging ...
have any of you facing these issues have used any wall charger other than the default nexus 4 LG charger ?? maybe ur battery was not charged the way its suppose to be .. or maybe ur battery is getting bad.. can sm1 with the problem replace the battery and see if the problem get solved ???and u can try charging it from the original lg charger for 12hrs straight .. it may(temporary) fix the problem /...
Any new ideas for this post? Or is it dead.
Shubhamqweasd said:
these dead spots IMO , are because of bad battery or bad charging ...
have any of you facing these issues have used any wall charger other than the default nexus 4 LG charger ?? maybe ur battery was not charged the way its suppose to be .. or maybe ur battery is getting bad.. can sm1 with the problem replace the battery and see if the problem get solved ???and u can try charging it from the original lg charger for 12hrs straight .. it may(temporary) fix the problem /...
Click to expand...
Click to collapse
i could try the battery replacement on my nexus, when i get the time, ill get back to you if it works....
ok got the dreaded dead spot where the sim card is, i can't unlock my phone. i dont have usb debug enabled, i can push/pull files in recovery but not much more.
ive tried to change the dpi to move the pattern away from the dead zone by editing build.prop manually and pushing it to the phone but cm13 doesn't seem to take the change to build.prop so the dpi is stuck at 320.
now, im trying to set up usb otg and unlock my phone using a wired mouse and y-cable. but quanta doesn't have otg for marshmallow enabled out of the box and i dont have root access to enable it in an app.
is there a file that i can edit and push to the phone to enable otg_hack?
techparkour12 said:
i could try the battery replacement on my nexus, when i get the time, ill get back to you if it works....
Click to expand...
Click to collapse
Did you ever try this?
buffering.... said:
Did you ever try this?
Click to expand...
Click to collapse
i did it, battery has nothing to do with the screen, its better to just replace it.
I am running SACs23 4.3V4.2 rom. I have been having now issues. I plugged my phone in to charge for a couple of hours. Came back and the notification light was blinking for sms. I unplugged the phone and pushed the power button. The screen would not turn on. The notification light died out and now nothing. I have tried booting into recovery, hard reset, and pulling the battery. When I plug the phone back in with or without a battery there is no charging indication. The phone is lifeless. Not sure what to do, I have never seen this. When I plug it into the computer, nothing happens. I can not get into recovery or download mode...the phone does nothing. Any suggestions or ideas?:crying:
The micro USB charging port appears to be not working. You can buy it on Ebay for $10 and replace it yourself. Fairly straightforward.
stupid question but I have to ask, have you tried a different usb cable?
dewrust said:
stupid question but I have to ask, have you tried a different usb cable?
Click to expand...
Click to collapse
Yes. Charging port works fine. 2hrs later, I put the battery back in and it booted. Used my phone for the next 24hrs and then put it on charger. Woke up this morning and same thing. Very odd!
This happens to me when ever I don't use the original charger
Can you get into your recovery? Sacs, has an update to v4.3 in his op that's working very well if you can download it on PC and transfer to your sd card. Dirty flash it and see what happens. My guess is, you are having the same boot lag issues as most others were having and there is a zip file you can flash in Sac's OP for that also for v4.2.
If you can get into your recovery, dirty flash his update.
Your phone, charger port and wire are fine. It's the lag everyone was getting to get the screen to come up.
Sac's is doing one more update so it may be a few minutes before the link is up, but here is the direct link for you..
http://www.androidfilehost.com/?fid=23212708291682600
Until the update is reuploaded, for the heck of it, dirty flash v4.2 and DO NOT select any of the lockscreen effects like lightening or blue orb. The lag has been narrowed down to possibly being that problem.
Lag issue flash file to be flashed in recovery
https://www.dropbox.com/s/gy2d6ajg30utnjd/lag_fix.zip
Try pulling the battery and leaving out for say ten minutes or so
Some clarification:
1. I 've pulled the battery and waited from 10min to 3hours. No change.
2. Plugging into computer and the phone nor computer responds to eachother.
3. I am using the original Sammy charger.
4. This is the 2nd time this has happened but after 24hrs of being off it still will not respond to anything.
5. I took it to Sprint today and they ordered me a replacement phone. They had 3 of their best techs troubleshooting for 2hrs and couldn't find anything wrong with the phone, except for that it doesn't do anything.:crying:
6. I am hoping my new phone doesn't suffer the same fate. I can honestly say this is my 3rd Sammy phone and the 1st time I've had to take it back for anything and I am always flashing new roms from trusted devs.
This one has me puzzeled! Oh, this happened after I updated to MJA software and firmware but no KNOX! So, maybe I am having an issue with the new MJA....sounds like a lot of phones (various carriers) are. I'll update if I learn anything new.
cyiam39 said:
Some clarification:
1. I 've pulled the battery and waited from 10min to 3hours. No change.
2. Plugging into computer and the phone nor computer responds to eachother.
3. I am using the original Sammy charger.
4. This is the 2nd time this has happened but after 24hrs of being off it still will not respond to anything.
5. I took it to Sprint today and they ordered me a replacement phone. They had 3 of their best techs troubleshooting for 2hrs and couldn't find anything wrong with the phone, except for that it doesn't do anything.:crying:
6. I am hoping my new phone doesn't suffer the same fate. I can honestly say this is my 3rd Sammy phone and the 1st time I've had to take it back for anything and I am always flashing new roms from trusted devs.
This one has me puzzeled! Oh, this happened after I updated to MJA software and firmware but no KNOX! So, maybe I am having an issue with the new MJA....sounds like a lot of phones (various carriers) are. I'll update if I learn anything new.
Click to expand...
Click to collapse
Sprint just issued an update today that is suppose to fix this issue. If you can get back to stock take the OTA and see if it helps. You have the sleep of death issue and the mk2 OTA mentions sleep issues as the main fix. Hopefully this is what they are fixing.
Sent from my GT-N5110 using Tapatalk 4
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...
Hello,
I got an old Nexus 7 from my sister and would like to use, but I cant get it to work. It does nothing, no screen flicker/backlight showing, nothing. The only thing that somewhat works is that I can get ist to show up in Linux as NvFlash with Lsusb.
The Nexus 7 never had a custom rom or root, it was completly stock. It was mostly used in the original dock. I did already swap the battery, I did try all buttom combos I could find on the web, but still I cant anything else than showing up as nvflash. I can hear some noisy if I put my ear near the tegra cpu, once I tried to power it via button pressing.
Do you have any idea on how to revive this thing?
You can try the Nexus Root Toolkit and see if it can Unroot (this flashes the stock os) with the Bricked radio button selected, but I would not be hopeful.
Sent from my LGLS992 using Tapatalk
Nachoztyle said:
Hello,
I got an old Nexus 7 from my sister and would like to use, but I cant get it to work. It does nothing, no screen flicker/backlight showing, nothing. The only thing that somewhat works is that I can get ist to show up in Linux as NvFlash with Lsusb.
The Nexus 7 never had a custom rom or root, it was completly stock. It was mostly used in the original dock. I did already swap the battery, I did try all buttom combos I could find on the web, but still I cant anything else than showing up as nvflash. I can hear some noisy if I put my ear near the tegra cpu, once I tried to power it via button pressing.
Do you have any idea on how to revive this thing?
Click to expand...
Click to collapse
You may have to use nvflash to flash the bootloader. Search with Google. There are some results which may help.
Hi, thank you both for your reply. I will try it next week, since I am currently not at home. @tnsmani dont I need some special files because of the encryption? I havent got those :/
Nachoztyle said:
Hi, thank you both for your reply. I will try it next week, since I am currently not at home. @tnsmani dont I need some special files because of the encryption? I havent got those :/
Click to expand...
Click to collapse
That's why I said search with Google.
So I searched Google, but all the results I found say it is not possible to reflash the bootloader without the blob file since it used a device specific key. I guess I am out of luck then :/
Nachoztyle said:
So I searched Google, but all the results I found say it is not possible to reflash the bootloader without the blob file since it used a device specific key. I guess I am out of luck then :/
Click to expand...
Click to collapse
Hi, Nachoztyle...
Mmm, from your description, it certainly doesn't sound promising. If the bootloader is corrupted or erased, the device is hardbricked, and a motherboard replacement would be required to render the device bootable again.
APX/NVflash mode is pretty much a non-starter if you haven't, at some point in the past, created your own unique 'flatline' blobs for your own specific N7.
However...
My own N7, which I sometimes completely forget about whilst it's lying on my desk, frequently runs out of power/charge, and when it does, the device appears completely and utterly dead.
So when I plug it into the charger, nothing happens. This happened recently, a few days ago, actually ~ I tried to power it on, and nothing happened. As usual, I plugged it in to my mains charger; I use an Amazon Kindle charger, output rated at 5volts/1.8amps, which I'm fairly certain is roughly equivalent to the original charger which shipped with the N7 back in 2012.
And nothing happened. I unplugged it and replugged it back in again, several times - and still no screen response.
So, I left it connected to the charger, overnight. The following morning, my N7 booted up.
I've had this happen before with my N7, that when the battery dies, it can take a bit of 'coaxing' back into life, sometimes with several plugging and unpluggings into the charger, and sometimes with different chargers and USB cables.
So, in conclusion then, it might be worth tinkering around with different chargers and/or different USB cables. Even with my 5volt/1.8amp Kindle charger, it can still take a good 12-16 hours before I can actually use it.
Rgrds,
Ged.
Sadly the device was always used stock and the flatline blobs never created.
I will play around with some chargers, I got a couple different ones, including the original one flying around.