Recently I have really began to notice a few things with my nexus 7. They are really starting to bug me, so any help I can get would be great.
The first thing that I have noticed is charging port is crooked.I do not know how it happened, but it doesn't seem to want to have a charger in it very long. Its touchy, and the cable is ALWAYS falling out. I've tried fixing it several times, but nothing seems to really work.
The next problem I have is my screen has a spot where the backlight bleeds a little. It is in the middle-left part of the screen, so I'm wondering if there is a screw or something that is too tight in there.
The final problem is no matter how hard I try, the OTA update will not work. It will just say ERROR and nothing else. I will reboot and be in 4.2.2 again. Resetting the "googleservicesframework.apk" will let me download it again, but the same problem arises afterwards. I was rooted, but when it errored the first time I did a factory reset and it still didn't work afterwards.
Once again any help is appreciated, thanks in advance!
I can't help you with your hardware problems but you can install 4.3 manually instead of OTA.
The micro USB port is on its way out. Needs to either be Rma'ed or if you can't/won't send it in there are guides that will show you how to replace the USB/headphone I/O port
Sent from my Nexus 4 using Tapatalk 4 Beta
Hi
New here so sorry my first post is a question but I have an issue with no obvious (possible?) solution so any help is much appreciated.
Earlier today I went to use my nexus 4 and found myself unable to enter my pin to unlock the device. Various areas of the touchscreen have become mostly unresponsive, especially where the number 5 is which is not responding at all. I am totally at a loss as to how this has happened as the alarm on the phone woke me this morning and I was able to disable it without issue and it was working perfectly last night. It has not been dropped, had anything spilled on it etc. so this problem has no obvious cause.
I was able to restore a nandroid backup I had made last week with the Nexus Root Toolkit but this has made no difference, the touchscreen is almost totally unusable when I boot into the TWRP recovery.
My first question is, is it possible to use my pc (via some software or something) connected via usb cable to enter the pin to unlock my phone as without being able to unlock the device after it has booted its storage is not visible in windows explorer.
My second question is what can I do about the touchscreen if any of the few probably useless ideas I have (flashing stock etc.) don't fix the problem? Is it possible for this sort of hardware issue to be replaced?
Thanks
PS Just wanna say a big thank you to many of the members of this forum for all the excellent work they do investigating and developing the many apps, tools and other things that have been produced, it's certainly made owning my nexus more enjoyable than it perhaps could have been.
Don't know how I managed to miss so many posts with roughly the same problem.
Anyway, definitely not a software issue which I think means I need to replace the digitizer, thankfully it's nowhere near as expensive as I expected.
Hey XDA, Really need some help here, i'll bullet point my problem for ease of reading:
- 1st Nexus 4 bought from google had wi-fi issues so got replacement
- 2nd replacement nexus 4 was good for about 2 weeks
- randomly screen touches weren't recognized by phone so reboot fixed that
- got worse and more frequent
- now my phone does not recognize screen touches at all
- phone is completely unusable, power volume buttons work though.
- need to ask XDA before another replacement ///
WHAT I'VE TRIED:
- i was on stock, so i tried to reflash stock to get rid of gravity stock and stock kernel
- rebooting phone 3950280359283 times.
- cleared caches.
- asked google play support, they're clueless.
- problem was here before i was unrooted, on complete stock 4.4.2
- also wondering whether its a software or hardware problem. i assume hardware however.
- i still have warranty
ANY IDEAS?!? thanks.
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Creepyficate said:
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Click to expand...
Click to collapse
My screen works now. However it will still come back every now and then and is fixed by a reboot. When i made this thread it did not work for a whole day, so my device will probably breakdown again. When I use TWRP it does not recognize touches. A good decider. So i guess it is hardware?
I think so, but wait for another reply confirming that.
I'd say it's a hardware issue. Definitely get it replaced again.
Kaleptik said:
I'd say it's a hardware issue. Definitely get it replaced again.
Click to expand...
Click to collapse
Lmao. You're definitely right. It's really annoying they sent me another device with a WORSE problem. Gonna ask google for some sort of compensation. I don't really have time to fiddle with devices re-rooting them transferring all my data again and so on. Too much work.
First and foremost I already have the drivers installed properly on the computer the OEM cable and a few others to be sure it wasnt a cord or computer issue.. But when i plug the phone into the computer the nexus doesn't show up either as i mass storage device or even in device manager. To see where I'm coming from I bought the nexus online and the seller sold it for parts and said the phone was in alright condition and said that it works in excellent condition before he wiped the phone and that it had no OS and that he didnt know how to fix. So I thought it was just a simple fix and bought it. Lucky the phone came with twrp already so i plugged in the phone and nothing happened, and I tried sideload and also didnt work. like i said before i installed all the drivers and everything so thats not the problem. I tried the Nexus Root Toolkit and didnt work. I even did the OG way by manually using fastboot but the computer didnt detect the phone. The only method i have left to use is the OTG method so i wouldn't need the computer. Has anyone had this problem before? I searched everywhere to see if anyone had this problem but couldn't. But if you guys already made a thread for this specific problem shoe me. Im thinking its a hardware issue something to do with the port
That's a tough one hopefully it reads OTG and you can flash something. I would grab latest udated twrp and flash first in current recovery. A lot of the new stuff requires it.
this happened to me after owning my Nexus 6P for almost a year. When I plugged the phone into my computer's USB port. Windows didn't acknowledge it BUT the phone was charging.
turns out I needed to get my daughterboard/USB port changed. Sent it in to HUAWEI and they did it for free under warranty (I was without a phone for like 8 days).
I am actually starting to have this problem now... I am certain I am well out of warranty. Plus... I don't trust Huawei.
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.