Im at a loss here so I come to you guys in desperation. The home button and power button work fine in TWRP but do nothing in the actual operating system. Also the capacitive buttons dont light up or work for that matter. I havent succesfully flashed a custom rom yet as I kept having boot loop issues but I did a fresh install with kies and still no go. Anybody seen anything like this? Its a T-813 if that matters...
Related
Hi all,
seems like my OB is broken. But just in case this is still a repairable issue and since I would of course love to keep my good ol' OB, I'm posting my issue. Maybe there is still hope
It all started after OTA-Update from CM10 nightly to the stable release. I noticed that from time to time the power button did not work after charging the device over night. So for example, the device woultn't wake up when pressing the power button, but reconnecting to the charger did the trick. But then again, I often coudn't turn it back to sleep with the button.
Every time that issue appeared, the OB acted normally after removing the battery for a moment.
But not today.
Again, I couldn't get it to lock when it was active because the power button did not work. So I decided to wait until the screen turned off after the timeout which it actually did. But then again, I couldn't wake it up.
So, starting with the "normal" procedure, I removed the battery for a moment and tried to turn it back on, thinking that it'll be just fine again. But not this time. It didn't react at all. Even after connecting it to the charger - the display turned on and showed the charging animation, but I couldn't get the device to boot.
Next step: Common unbrick procedure. Since it was the only thing I could still do with the OB, I reflashed the good old patched v20n using SmartFlash. I used the exact same program and bin files that I used long ago when I initially rooted the device. So that should have worked like a charm. It didn't.
First try: Flashed with SmartFlash and restored an old nandroid with Zeus ROM on it. Rebooted and... oh great it's stuck already on the LG logo.
Okay, 2nd try: Flashed again but this time just selected the reboot option in CWM. Device boots, plays the animated LG bootlogo and reboots into bootlooop....
So far about my poor OB
Now does anybody have any idea what could have gone wrong with the device?
Of course it could just be a coincidence that these issues started right after the update and the cause may be an ancual failure of the HW button.
But really, how likely is that keeping in mind that my OB worked like a charm all the time before the update?
Any ideas, comments or even suggestions what else I could try?
Smartflash must unbrick the device if the problem is not a hardware problem, if you have tried it and it didn´t work, i am pretty sure that you have to take the phone to warranty.
Anyway, you can try to flash a patched bin/fls with root and recovery, after flash phone will go to recovery, then do a full wipe (Data, cache and dalvik) and reboot.
Reflashed with SmartFlash (to get into CWM), wiped all, booted v20n; no power button, all other HW-Buttons work :/
Hardware problem.
That's what I thought as well, but:
Just managed to restore my Zeus ROM Nandroid image, cleared cache and it booted without problems. Aaand: Power button is working again! Locking/unlocking as well as turning on/off the device entirely works normal!
Now seriously, this issue keeps buggin me - how can something like that happen at all??
I mean, if I would mess with the key mapping and remove the mappings of the power button, it might not work anymore for locking and unlocking the phone. But what could possibly cause that button to not even work for powering on the device? I always thought that must be a hard-wired functionality??
I'm completely stumped on this. I'm new to Custom Roms.
So a long time (a little over year aprox) I bought an GT-N7000 from an at-the-time friend (no longer friends)
He factory reset and installed a custom rom (Paranoid Android) on it. (Such a nice gesture..)
Now, speed forth Christmas last year, I bought a Galaxy Note 3 for myself, and I then sold off the N7000 to my older brother.
Now my brother comes to me and tells me that his phone is acting weird.
I take a look and notice that the phone has apparently partitioned itself into several drives, making the phone run incredibly slow and he keeps getting an annotation going "There's way too little space left!"
Now, as I mentioned I'm new to custom roms and that kind of stuff, but my initial "brilliant" idea was to simply factory reset it, and install the Stock Rom on it.
I grabbed a Stock rom from Sammobile that had a country that at least was english in nature (UK) I unfortunately live in Denmark, and so therefor it was impossible to find a Stock rom that fits it.
I grabbed it, loaded it onto ODIN3 and went into Recovery Download Mode. And I started installing it. Everything went smoothly.
Then when the phone restarted it started boot looping.
I looked and searched everywhere for fixes. Problem was, looking at the first few fixes I've seen include links to .PIT files that are either dated or ancient in nature.
androidayos.com and android.gs both had a fix, but their links was either out dated or not helpful for my specific case.
And so I beseech thee oh mighty XDA Developers.
Have you a solution/help that might be what I need.
I've read that I should go into a recovery mode that allows me to look at the files. (Read that I could do so by holding the Home Button + Power button when it turned on. But such a function didn't seem to work on the N7000.)
I've also tried looking at installing Paranoid Android again, but that requires access into the Recovery Mode. Which I, again, do not have.
PIT files are dated because they never change. They have been the same since device manufacturing date.
So did you reset before odin install? Recovery mode is by pressing the power + vol up + home together.
nokiamodeln91 said:
PIT files are dated because they never change. They have been the same since device manufacturing date.
So did you reset before odin install? Recovery mode is by pressing the power + vol up + home together.
Click to expand...
Click to collapse
Well, I had to flash in phillz to actually get a recovery mode to work.
But I managed to do just that, and then whipe the caches and I could then get the stock rom flashed onto it.
Which then got the phone to work properly.
No failures to report yet.
So for the moment a full-on success story!
So my N910T is stuck on the Welcome screen after flashing back to stock. I flashed C0G2. I'm thinking maybe it was the update or something, but it's like 1.6gigs so I figured it's the full rom.
The reason I flashed back to stock in the first place is because I was messing around, trying different roms, when I ran across one that made my screen seem semi-unresponsive. Nothing I touched would respond. I would touch the screen and it would like up to the touch, but nothing else. If I sit there and play with it long enough I'll accidentally get a button to respond. When I pressed the power button I get the "power off/restart options, but when I press one the phone doesn't power down.
I'm downloading the NIH now (which is 4.4.4) and try flashing it. I don't know what else to do.
Wipe your data partition as well as caches. You can't downgrade and expect it to work like that.
hello, my screen right side 1cm touch screen not working anymore idk how it happend, phone isnt dropped or scrached or damaged. please if anyone know about this help me, how to fix ?
Solved
I have same issue. Everything was working fine until I tried to restore my backup via safestrap recovery. I ended up to a bootloop because the backup was corrupted. The phone got really messed up and didn't charge anymore for some reason. Then I flashed stock JB build via RSD Lite. I used "VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip" file. Phone booted up normally but the backlight of recents app and home buttons were not working. However, the backlight of back and search buttons are working.
I don't mind about the backlights because I would turn them off anyway. The biggest problem is that there is about 1cm thick line on the screen which doesn't regognice touch. Everything else seems to work. I didn't drop the phone or anything like that.
I tried to flash Lineage 14.1 and different kernels but without any luck. Also I just reflashed the stock JB rom via RSD Lite. Still same situation. Is there anything else I could try? Thanks!
EDIT: Whoa!
I was able to fix this and is was very simple. I just followed this YouTube video :good:. I just had to try twice and turn off screen after doing that.
Hi guys,
I was about to flash the resurrection rom on my S10 and somewhere in the process with Magisk when rooting it caused an error so that I wasn't able to get into boot menus with the hardware buttons anymore. I thought this would be fixed when flashing the resurrection rom, but now the rom apparently was an old version leading to the "rev. check fail" error.
I know I could fix this by flashing back to the default, but due to the other issue I am not able to get back into the boot menus and cannot connect the device to my pc.
Do you know whether there are any other options to get into boot menus aside from the typical button combinations (with USB connected device) or adb/pc based solutions?
I fear I caused a hard brick here, but would hope there maybe is a secret button I haven't found yet to fix this.
Any help is greatly appriciated!!!