Related
so... this morning i noticed that trackball isn't functioning... i could move it in any direction and press it, but nothing happened... so i tried to reboot and now it keeps going into fastboot (as it's always pressed)
now, since i'm not anywhere near any of "supported" countries, sending it to back to htc is not an option... is there anything i can do to override going into fastboot and to boot it normally (i don't usually use trackball, i don't really care if it's working, i just want to boot)
can you select to boot normally from fastboot? or hboot
nope...i can't move selection while in fastboot... i'm pressing vol+- but nothing happens... probably because it thinks trackball is pressed all the time...
I had the same thing happen with my power button. I had to send the phone back to be repaired and it took almost two weeks.
I don't know if anything has been posted yet but I remember someone saying the N1 has the same trackball as one of the blackberries. Maybe there is a guide on swapping them or even just disassembling it to clean.
well... sending it back (from serbia to usa) is definitely not an option, partly because it would probably take at least month to get it back, partly because i don't want to risk having to pay duty&tax when it comes back.
disassembling, however, is an option, and i will do it if no one has better idea
thanks for replies anyway...
alt+64 said:
so... this morning i noticed that trackball isn't functioning... i could move it in any direction and press it, but nothing happened... so i tried to reboot and now it keeps going into fastboot (as it's always pressed)
now, since i'm not anywhere near any of "supported" countries, sending it to back to htc is not an option... is there anything i can do to override going into fastboot and to boot it normally (i don't usually use trackball, i don't really care if it's working, i just want to boot)
Click to expand...
Click to collapse
When you press it does it make the clicking noise? if it doesn't, replacing the trackball wont fix your issue. The trackball popple that registers the click when a short is made is depressed fully and is always making a short. you either have to rebend this popple or replace it entirely. You need something similar to this
When you press it does it make the clicking noise?
Click to expand...
Click to collapse
yes it does... click, feedback... everything is exactly the same as it was...
btw... i'm at home now, so i connected it to usb and managed to boot with "fastboot reboot"... problem is that it boots into safe mode (i guess it does it if you hold trackball during whole boot process) so i cant open any 3rd party apps which makes it kinda unusable...
btw2... scrolling with trackball is working normally.. clicking does not
i guess ill take it apart and try to disconnect trackball completely..
any last thoughts before disassembling?
some witchcraft happened today, and my trackball is kinda working now, but phone keeps booting to safe mode...
taking battery out for 2 minutes, as some suggested, didn't help, and neither did holding trackball while booting... any other idea?
did you try factory reset?
yes... no luck...
Help! My atrix now is stuck at the "Rethink Possible" Screen and I only installed SPB 3D Shell.
Suggestions?
reflash the SBF file using RSD lite.
Thanks, but I was looking for something a little less severe.
That's like saying, oh, I've got a bug in my windows -Friend "Better wipe and reinstall windows" that's the only solution! and so forth.
THAT would wipe the phone.
I've made some progress, it seems that the Beautiful Widgets and the SPB are conflicting, and I can get into the desktop but it's black. If I press the search icon, then I get the google page.
It's only stuck at a black home screen. I have this thing set up to the nth degree and I can't bear the thought of doing it all over again, and horking up my wifi and so forth with the flash rom.
Got any suggestions on how to get to a moto blur screen with taps etc?
It's not like I rooted the damn thing or screwed it up that way. Just an install of a 15.00 program messed it up big time.
i couldnt get SPB to work on mine...
Dang. Wish I got the refund in time. The 15 minutes isn't enough. It took me 30 minutes to realize that this launcher has little room for customizing, and there's little things like slow scrolling that make LP better.
Never live in the past but always learn from it.
OK, I could get to "search" mode google etc., so I searched the catalog of apps on the phone and then I found "task Manager" and got in that way. Uninstalled Beautiful widgets and stopped SPB but didn't uninstall it. Then the next time I booted I had complete hang and had to do a hard reset. Oh well, not like it's the most fun part of a phone - setting it up, so maybe I'll do a better job this time.
I never did have to reflash the rom, I knew it wasn't THAT bad.
What's irritating is nearly 90 users read my post and only 3 replied in any way. How irritating.
That's people for you I guess.
jesus the same thing is happening to me right now..
stuck on the rethink possible screen. WTF
Fountainhead931 said:
OK, I could get to "search" mode google etc., so I searched the catalog of apps on the phone and then I found "task Manager" and got in that way. Uninstalled Beautiful widgets and stopped SPB but didn't uninstall it. Then the next time I booted I had complete hang and had to do a hard reset. Oh well, not like it's the most fun part of a phone - setting it up, so maybe I'll do a better job this time.
I never did have to reflash the rom, I knew it wasn't THAT bad.
What's irritating is nearly 90 users read my post and only 3 replied in any way. How irritating.
That's people for you I guess.
Click to expand...
Click to collapse
how did you get to a black desktop?
ok my phone finally got past the Rethink possible screen, but now i'm staring at a blank desktop and can only access the contact/dialer screen... search button will only allow me to search contacts
pressing a bunch of buttons also allowed me to get into the browser.. i'm fine with doing a reset if i can figure out how to get to the settings screen somehow.
you can do a factory reset without doing a reflash by going into android recovery and wiping user data/cache
hold vol down and power on
hit vol down till you get to android recovery
hit vol up
tap lower right of screen
use vol up/down to select wipe data/factory reset
tap ok on lower left
select wipe cache partition
tap ok
select reboot
tap ok
redo everything you jacked up...... only better this time
diedemus said:
you can do a factory reset without doing a reflash by going into android recovery and wiping user data/cache
hold vol down and power on
hit vol down till you get to android recovery
hit vol up
tap lower right of screen
use vol up/down to select wipe data/factory reset
tap ok on lower left
select wipe cache partition
tap ok
select reboot
tap ok
redo everything you jacked up...... only better this time
Click to expand...
Click to collapse
ok, i got the the "android recovery" part, hit vol up, then it says "Entering Android Recovery mode OSD 1" or something like that.. now i see a little green android with the exclamation.. volume up/down does nothing/ there is no option for a reset or anything else... stuck here and afraid to touch any different buttons but the volume buttons aren't giving me any new options..
is it safe to do a battery pull at this point and try again or will it brick my phone?
by the way, my phone is totally stock..
...pulled battery, attempted again, same issue.
OK, here's how i fixed it without any resets..
from the dialer, i held down the search button, used Vlingo to search "Settings", uninstalled SPB, voila, phone back to normal.
thank f'king god.
It is not compatible with Atrix I guess, I have tried to install from PC... It says ur device is not compatible
I tried it out on my Atrix, ran fine with no trouble even after a few reboots. So I don't know if it is SPB itself or if it is conflicting with something you guys have installed.
Same here. Works great for me not one problem so far.
at the screen with the little android guy you tap the bottom right of the touchscreen
I was running an older Paramid version of dunphp's ROM, and right before swtching the ROM my touch screen start to not function. I could not pull the ring up to unlock the screen. I rebooted multiple times. Cleared Dalvik and fixed permissions. It finally worked after attemptiing to unlock it for what seem like abother 500 times.
I was going to change over to his latest Deisre HD ROM anyway. So I did a Task 29, and cleaned and reinstalled everything from scratch. It worked perfectly for about 5 days. Now I am getting the same issue with my touch screen. It just seems to go out. Is this typically what happens when it's about to die?
Never mind. I Task29, and flashed a Windows Mobile ROM just to see, and yeah...it's dead...
cmajewsk said:
Never mind. I Task29, and flashed a Windows Mobile ROM just to see, and yeah...it's dead...
Click to expand...
Click to collapse
You have semi-dead digitizer. But it is nothing you can't temporarily fix every time it happens. Just push red (end call) button really hard for a while and it will get fixed for a while. I recommend you using button savior and lock screen with it and unlock with any other button than red one, it should be permanently fixed then. Please hit the thanks button if I helped you.
lolkoz said:
You have semi-dead digitizer. But it is nothing you can't temporarily fix every time it happens. Just push red (end call) button really hard for a while and it will get fixed for a while. I recommend you using button savior and lock screen with it and unlock with any other button than red one, it should be permanently fixed then. Please hit the thanks button if I helped you.
Click to expand...
Click to collapse
I hit the thanks button as you gave me hope. I am currently using my old TouchPro 2 with an old NRG Titanium Rom on it for the time being, but will try this today. I’ll install “button savior”, but what am I supposed to do with the app? What settings do I run? I think you are totally right about this, as I noticed when I was unlocking my phone, using the green call button worked most often, but now that’s not even working.
cmajewsk said:
I hit the thanks button as you gave me hope. I am currently using my old TouchPro 2 with an old NRG Titanium Rom on it for the time being, but will try this today. I’ll install “button savior”, but what am I supposed to do with the app? What settings do I run? I think you are totally right about this, as I noticed when I was unlocking my phone, using the green call button worked most often, but now that’s not even working.
Click to expand...
Click to collapse
Yes, I have exactly the same problem as you have. My phone was working flawlessly for like a year and a half, but last week all of a sudden the touchscreen sometimes didn't work and sometimes it did. So I tried literally everything, I was fixing my permisions all the time, wiping dalvik, task29, remaking parrtitions, even bought a new sd card. But few days ago I found a solution, by pushing red button really hard (because the digitizer is right behind it) and not using it after. The Button Savior app is a simple app that makes a very little transparent icon on your screen and when you tap it, the menu of buttons will come up (with the same buttons as your hard buttons on your device) so every time you will want to lock the device you will do it on your screen, and won't have to push the hard button and come through all the hassle of pushing the digitizer. I really hope I helped you, as this very same problem was driving my crazy for the past few days.
lolkoz said:
Yes, I have exactly the same problem as you have. My phone was working flawlessly for like a year and a half, but last week all of a sudden the touchscreen sometimes didn't work and sometimes it did. So I tried literally everything, I was fixing my permisions all the time, wiping dalvik, task29, remaking parrtitions, even bought a new sd card. But few days ago I found a solution, by pushing red button really hard (because the digitizer is right behind it) and not using it after. The Button Savior app is a simple app that makes a very little transparent icon on your screen and when you tap it, the menu of buttons will come up (with the same buttons as your hard buttons on your device) so every time you will want to lock the device you will do it on your screen, and won't have to push the hard button and come through all the hassle of pushing the digitizer. I really hope I helped you, as this very same problem was driving my crazy for the past few days.
Click to expand...
Click to collapse
Nah, that didn't work...my digitizer must be completely dead. I held the Red Button for a while and holding it down really hard...made no difference..oh well guess a dumb phone until the Prime comes out....thanks anyway.
cmajewsk said:
Nah, that didn't work...my digitizer must be completely dead. I held the Red Button for a while and holding it down really hard...made no difference..oh well guess a dumb phone until the Prime comes out....thanks anyway.
Click to expand...
Click to collapse
Aww, that's a shame. I really tought it would help. It doesn't work every time, maybe you can try it few more times. If it's not even then going to work, then maybe you should get your digitizer replaced.
Cheers
lolkoz said:
Aww, that's a shame. I really tought it would help. It doesn't work every time, maybe you can try it few more times. If it's not even then going to work, then maybe you should get your digitizer replaced.
Cheers
Click to expand...
Click to collapse
How long do you hold the red button? Also, I am pushing down really hard. I didn't know you could get the digitizer replaced...I wonder who would do that (no way would I send it to HTC and wait a month), and how much that costs...?
HTC sends phones back crazy quick. Atleast that's how it was for me. They actually sent it back the day they got it from what I remember. It did take a while though for the phone to arrive to HTC (this depend who and from where you send it though) If your phone still has warranty I seriously recommended you send it yo HTC. Just remember to flash it 100% stock before sending it.
Sent from my HD2 using XDA App
Well believe it or not, after pressing the Red phone off button for an eternity and applying a ton of pressure, it's working. I am sure it won't be for long. I have a shortcut to lock the phone on the screen. So basically your saying I should stay away from hitting the Red phone off button, or else that will kill it again? What about the other hard buttons?
I am in the UAE at present, so it might be better for me to just order a digitizer and do the repair myself. I see there are a lot of YouTube videos on the subject.
Thanks everyone for your help!
Hey, i need help. I know nothiing about these phones. I came on here and got help last year to make my hd2 windows into an android.... i did all the work, wahtever you wanna call it, flashing or ROM. something like that. Well anyways, over the the past few months, its been getting stuck on the unlock screen. nothing works, then all of a sudden it will swipe and unlock. now its been stuck for two weeks and i have tried everything, taking the battery out and resetting from the small button in the back, but nothing changes.
lovelyxleo said:
Hey, i need help. I know nothiing about these phones. I came on here and got help last year to make my hd2 windows into an android.... i did all the work, wahtever you wanna call it, flashing or ROM. something like that. Well anyways, over the the past few months, its been getting stuck on the unlock screen. nothing works, then all of a sudden it will swipe and unlock. now its been stuck for two weeks and i have tried everything, taking the battery out and resetting from the small button in the back, but nothing changes.
Click to expand...
Click to collapse
you can try this but you will have to press it really really hard and try it multiple times
http://forum.xda-developers.com/showpost.php?p=19458378&postcount=2
Kameirus said:
you can try this but you will have to press it really really hard and try it multiple times
http://forum.xda-developers.com/showpost.php?p=19458378&postcount=2
Click to expand...
Click to collapse
Then once you do above and get the screen working again, you can do what i did and use attached program to remap one of the other buttons (i chose green phone button since i press the phone icon to use the phone anyhow) and remap it to function as the power button and never worry about the screen again
To install: download to computer, then use adb install to install.
Or the simple way, just download straight to phone, navigate to the downloaded folder using a file explorer(astro works well found on the market) and launch it through the file explorer to install.
elesbb said:
Then once you do above and get the screen working again, you can do what i did and use attached program to remap one of the other buttons (i chose green phone button since i press the phone icon to use the phone anyhow) and remap it to function as the power button and never worry about the screen again
Click to expand...
Click to collapse
pssst
you forgot the attachment
Kameirus said:
pssst
you forgot the attachment
Click to expand...
Click to collapse
Not uh! lol thanks Ive edited post
elesbb said:
Not uh! lol thanks Ive edited post
Click to expand...
Click to collapse
..lol....
Yep, I have tried that.... pushing the end button a zillion times. It use to work before, but now it doesnt. I tried the end button, the call button, sliding over the other keys, just tapping on the unlock keys on the screen... but nothing. i do it so much, i pretty much start banging on the keys.....ummm... not sure if that made it worse??
is there anyway i can just reset my phone.... perhaps flash a new rom. I really dont care what is on my phone at this point. phone numbers not saved on sim can be replaced.... i dont care about anything else as far as apps. i just want to be able to use this phone again, whatever it takes. not sure if this is even possible without unlocking the screen first. i am so frustrated i wanna let my rottweiler accidently chew it up, just so i can get a new phone...
i know there is some smarty pants out there that can figure this out... help me pleeeeeeeeeeze!!!!
lovelyxleo said:
Yep, I have tried that.... pushing the end button a zillion times. It use to work before, but now it doesnt. I tried the end button, the call button, sliding over the other keys, just tapping on the unlock keys on the screen... but nothing. i do it so much, i pretty much start banging on the keys.....ummm... not sure if that made it worse??
is there anyway i can just reset my phone.... perhaps flash a new rom. I really dont care what is on my phone at this point. phone numbers not saved on sim can be replaced.... i dont care about anything else as far as apps. i just want to be able to use this phone again, whatever it takes. not sure if this is even possible without unlocking the screen first. i am so frustrated i wanna let my rottweiler accidently chew it up, just so i can get a new phone...
i know there is some smarty pants out there that can figure this out... help me pleeeeeeeeeeze!!!!
Click to expand...
Click to collapse
Nope. Its pretty much hosed. These are classic symptoms of the digitizer cable losing connection with the main board. Pressing the red End key forcefully can sometimes mate the connection back, but otherwise if that doesn't work nothing will. If you're feeling brave, you can take apart the phone piece by piece and reassemble it. That might do the trick. Else, you have to replace the digitizer.
Ok... first of all, what is a digitizer?
Also, is there any way I can connect it to my computer via usb and try to remove the files that i put on there for the rom.... that would just make it a windows phone again. Because Im confused.... is this a phone malfunction or a file issue?
lovelyxleo said:
Ok... first of all, what is a digitizer?
Also, is there any way I can connect it to my computer via usb and try to remove the files that i put on there for the rom.... that would just make it a windows phone again. Because Im confused.... is this a phone malfunction or a file issue?
Click to expand...
Click to collapse
Can you get to the bootloader (stripey screen)? If so, then just flash a stock WinMo ROM from there and it should work.
Well I am able to restart the phone after I take the battery out. So there is a point at the startup while its loading, it says 1-2-3-4 Go Go Go. Not sure if there is anything I can from there.
Oh btw... for a brief few minutes yesterday, the phone did unlock. I got so excited that I started reading all my text messages I missed over the passed 2 weeks and also reviewing missed phone calls. And by that time, the phone locked again. No luck since.
lovelyxleo said:
Well I am able to restart the phone after I take the battery out. So there is a point at the startup while its loading, it says 1-2-3-4 Go Go Go. Not sure if there is anything I can from there.
Oh btw... for a brief few minutes yesterday, the phone did unlock. I got so excited that I started reading all my text messages I missed over the passed 2 weeks and also reviewing missed phone calls. And by that time, the phone locked again. No luck since.
Click to expand...
Click to collapse
Take the battery out, put it back in then hold down the power (end call) and volume down buttons. From here, you can flash a stock ROM via the USB port or flash a stock ROM via your SD card
lovelyxleo said:
Well I am able to restart the phone after I take the battery out. So there is a point at the startup while its loading, it says 1-2-3-4 Go Go Go. Not sure if there is anything I can from there.
Oh btw... for a brief few minutes yesterday, the phone did unlock. I got so excited that I started reading all my text messages I missed over the passed 2 weeks and also reviewing missed phone calls. And by that time, the phone locked again. No luck since.
Click to expand...
Click to collapse
If you remap the call button to the power button, as lung as you don't hit the end key anymore your screen should stay working. It has for me
Sent from my HTC HD2 using Tapatalk
OOOOH... ok how do i remap?
Nigeldg said:
Take the battery out, put it back in then hold down the power (end call) and volume down buttons. From here, you can flash a stock ROM via the USB port or flash a stock ROM via your SD card
Click to expand...
Click to collapse
I have no idea how to flash a stock ROM... any links???
lovelyxleo said:
OOOOH... ok how do i remap?
Click to expand...
Click to collapse
use the attached apk in this post from before and then find the call button inside the program i think its 231 or something like that. Then press apply and voila green key is now your power key
elesbb said:
use the attached apk in this post from before and then find the call button inside the program i think its 231 or something like that. Then press apply and voila green key is now your power key
Click to expand...
Click to collapse
Okk, i can try this... but do i download that file to the computer then to the phone via usb or ?
i see the file, i just dont know what to do with it.
lovelyxleo said:
Okk, i can try this... but do i download that file to the computer then to the phone via usb or ?
i see the file, i just dont know what to do with it.
Click to expand...
Click to collapse
You can eitherdownload to computer, the use adb install to install the program, or download to your phone and use a file browser to navigate to your downloads and install from there. Downloading to your phone is probably the easiest for beginners.
Sent from my HTC HD2 using Tapatalk
i definatly think this is the digitizer problem... same thing heppend to me..
elesbb said:
You can eitherdownload to computer, the use adb install to install the program, or download to your phone and use a file browser to navigate to your downloads and install from there. Downloading to your phone is probably the easiest for beginners.
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
Ok, I can try that. But I am still waiting to get this phone screen to unlock. I guess I cant do anything until then.
Hi Everyone!
Long timer lurker, first time poster!
So, I've popped into the site for years to get tips on how to root/unlock/jailbreak the various devices I have: Apple stuff, Android stuff, etc. I've got the LG V20 and as I've broken it in, I've been increasingly frustrated by the lag and bloat from all of these processes running in the background that Greenify can barely keep up with to shut down over-and-over-again...
Wait. To quote Ruby Rod: "But who CAAAAARES!?!"
I want to Root my Sprint LG V20. I followed the steps that me2151 put in his (excellent) post, step by step. Everything seemed to go fine, got TWRP installed and working, installed the Stock LS997, installed SuperSU.
But the static.
THE STATIC.
It won't go away.
I covered the entire front of the phone and put screen to sleep/woke it up. Still there.
I covered the front and restarted from scratch. Still there.
I installed AT&T H918 Konverged Kernel, then did the above. Still there.
I've started from Step 2-the end x 3 in the last 36 hours; up until 2am last night messing with it. I've searched through the forums and it sounds like folks have gotten past it, but for whatever reason my phone stubbornly isn't snapping to...
I can SEE the setup screens behind the static, like if I work from memory and swipe at the right place/time, I can get to the "set up wifi" screen but then the disruption is too great to type anything.
I hate to be "that guy" that one of you is going to respond with a link to an obvious solution to the problem, but I gotta say I'm at the end of my ability to figure this one out - could use some help, please, thanks (and sorry for being dense, in advance)...!
I'm not sure what is causing this problem for you - but the only advice I can offer is to flash werewolf 1.0 kernel. While some/most prefer the stock kernel for responsiveness and battery life - I do flash werewolf 1.0 when I'm playing with a new rom and want to see what's going on behind the static.
Werewolf-h91x-1.0-Albatross.zip
Lock your screen
Then cover proximity sensor to make 2nd screen sleep. Once sceen is sleeping unlock screen and it will be normal. Easier way to get by it is lock screen then turn phone face down... Walk away for 5 min.
After you get in the 1st time. Set 2nd screen off when main screen is off and a simple lock and unlock of phone will remove static.
And yes it will always be there on stock rom and stock kernel. Custom kernel will fix static but break other things..
Aosp has no static.
Ohhhh, okay....
First: thank you both for your responses - after reading and re-reading your posts, I feel like I know you! Either of you wanna be a godparent? If so, lemme know and I'll PM you when I have kids. And/or get married.
Anywho, that may be my issue, Team DevDigitel - patience (I was putting the screen to sleep with my hand over the sensor and waking it back up in seconds...I'll try 5 minutes to see what happens. Will report back (it's currently re-flashing).
In the meantime, the weirder parts of this exercise have been this:
-when I flash using the stocks from your post (Team DevDigitel) or the original link from me2151, I get the static that won't go away (which, again, sounds like it's my fault)
-when I wipe and flash and install LS997-deODEXd-signed (the one that I read WASN'T based on a Sprint ROM, but a US ROM), no static, but no phone connectivity - blank everything - no MEID, etc.
Curious - when/if I can get through the static, will that connectivity issue still be there, or will it be repaired because it is indeed based on a Stock Sprint ROM vs a generic US one?
Also: when I boot up, the static is on the screen so much that I can't really tell when it's done and at the sprint setup screens (language, etc.)...if I turn the phone over the 5+ minutes, will it still go to sleep that early into the process, or just freeze there?
Thanks again, guys - really appreciate it and I'm learning a lot from reading your exchanges!
:highfive::good::fingers-crossed:
Sigh, tried it - no joy. Steps:
1) Through TWRP, wiped cache, dalvik, system, data, and even internal storage
2) Flashed TeamDevV7.5C.zip off of Ext SD, then wiped dalvik/cache
3) Pressed "back" to Main TWRP and Installed SuperSU-v2.79-201612051815.zip, then wiped dalvik/cache
4) Pressed "back" to Main TWRP and Installed konverged-0.3-v20-h918-7.0..zip, then wiped dalvik/cache
5) Pressed "back" to Main TWRP and Rebooted to System
6) Once System loaded, static across entire screen
7) After it seemed like the screen had gotten to the point of the Sprint installer, behind the lines (I can tell because if I tap the lower right corner, the screen seems to change...until I get to what I think is where it asks to connect to a wifi and the keyboard pops up, but can't tell anything)
8) Tapped power key once to put phone to sleep
9) Put phone face-down on desk
10) Waited 10 minutes like that
11) Tapped power key again while phone still face down on desk
12) Turned phone over, still had static on first and second screens
13) Repeated from #9, but instead of 10 minutes, waited 20 minutes
14) Turned phone back over, and first screen stayed black/nothing, while second screen stayed static
15) Pressed power button multiple times (from 1 tap, 2 taps, 3 taps, 1/2/3/ long presses), and nothing
16) Took battery out and put back in
17) Static screen reloads again
I think I screwed something up somewhere - the sensor trick seems to be working for everyone but me - is there any way to deactivate the second screen via fastboot,or something super-clever like that...?
raenemaker said:
Sigh, tried it - no joy. Steps:
1) Through TWRP, wiped cache, dalvik, system, data, and even internal storage
2) Flashed TeamDevV7.5C.zip off of Ext SD, then wiped dalvik/cache
3) Pressed "back" to Main TWRP and Installed SuperSU-v2.79-201612051815.zip, then wiped dalvik/cache
4) Pressed "back" to Main TWRP and Installed konverged-0.3-v20-h918-7.0..zip, then wiped dalvik/cache
5) Pressed "back" to Main TWRP and Rebooted to System
6) Once System loaded, static across entire screen
7) After it seemed like the screen had gotten to the point of the Sprint installer, behind the lines (I can tell because if I tap the lower right corner, the screen seems to change...until I get to what I think is where it asks to connect to a wifi and the keyboard pops up, but can't tell anything)
8) Tapped power key once to put phone to sleep
9) Put phone face-down on desk
10) Waited 10 minutes like that
11) Tapped power key again while phone still face down on desk
12) Turned phone over, still had static on first and second screens
13) Repeated from #9, but instead of 10 minutes, waited 20 minutes
14) Turned phone back over, and first screen stayed black/nothing, while second screen stayed static
15) Pressed power button multiple times (from 1 tap, 2 taps, 3 taps, 1/2/3/ long presses), and nothing
16) Took battery out and put back in
17) Static screen reloads again
I think I screwed something up somewhere - the sensor trick seems to be working for everyone but me - is there any way to deactivate the second screen via fastboot,or something super-clever like that...?
Click to expand...
Click to collapse
This may be a long shot, but when you pull the battery, do the hard reset with the volume down button held down with the power button until you see the LG logo, then let up for a second on the power button while still holding the volume down, then press down on the power button with the volume down still pressed. You should get the white reset screen--answer YES twice with the volume down button and selecting with the power button. It should boot back into TWRP. Hit REBOOT, then SYSTEM. I honestly don't think you're waiting long enough, even though it might feel like you've been waiting awhile. I know it sounds silly but you really should just put the phone down and find something else to do for a good 15-20 minutes at least.
OK I'm down!
bgibson72 said:
This may be a long shot, but when you pull the battery, do the hard reset with the volume down button held down with the power button until you see the LG logo, then let up for a second on the power button while still holding the volume down, then press down on the power button with the volume down still pressed. You should get the white reset screen--answer YES twice with the volume down button and selecting with the power button. It should boot back into TWRP. Hit REBOOT, then SYSTEM. I honestly don't think you're waiting long enough, even though it might feel like you've been waiting awhile. I know it sounds silly but you really should just put the phone down and find something else to do for a good 15-20 minutes at least.
Click to expand...
Click to collapse
OK thanks - I'll try that!
Sorry, just for clarity...
bgibson72 said:
This may be a long shot, but when you pull the battery, do the hard reset with the volume down button held down with the power button until you see the LG logo, then let up for a second on the power button while still holding the volume down, then press down on the power button with the volume down still pressed. You should get the white reset screen--answer YES twice with the volume down button and selecting with the power button. It should boot back into TWRP. Hit REBOOT, then SYSTEM. I honestly don't think you're waiting long enough, even though it might feel like you've been waiting awhile. I know it sounds silly but you really should just put the phone down and find something else to do for a good 15-20 minutes at least.
Click to expand...
Click to collapse
In case that sounded like I hadn't tried that, I DID do the hard reset to start with and then Did what I listed above, But I didn't wait for 20 minutes.
I'm gonna up the ante, though - because I needed my phone for work, I had Sprint re-provision (if that's the right word) my previous phone as my primary number until I can resolve the LG v20 into stability so I can actually do the procedure and literally leave it all day (or longer) to process. Will circle back!
raenemaker said:
Sigh, tried it - no joy. Steps:
1) Through TWRP, wiped cache, dalvik, system, data, and even internal storage
2) Flashed TeamDevV7.5C.zip off of Ext SD, then wiped dalvik/cache
3) Pressed "back" to Main TWRP and Installed SuperSU-v2.79-201612051815.zip, then wiped dalvik/cache
4) Pressed "back" to Main TWRP and Installed konverged-0.3-v20-h918-7.0..zip, then wiped dalvik/cache
5) Pressed "back" to Main TWRP and Rebooted to System
6) Once System loaded, static across entire screen
7) After it seemed like the screen had gotten to the point of the Sprint installer, behind the lines (I can tell because if I tap the lower right corner, the screen seems to change...until I get to what I think is where it asks to connect to a wifi and the keyboard pops up, but can't tell anything)
8) Tapped power key once to put phone to sleep
9) Put phone face-down on desk
10) Waited 10 minutes like that
11) Tapped power key again while phone still face down on desk
12) Turned phone over, still had static on first and second screens
13) Repeated from #9, but instead of 10 minutes, waited 20 minutes
14) Turned phone back over, and first screen stayed black/nothing, while second screen stayed static
15) Pressed power button multiple times (from 1 tap, 2 taps, 3 taps, 1/2/3/ long presses), and nothing
16) Took battery out and put back in
17) Static screen reloads again
I think I screwed something up somewhere - the sensor trick seems to be working for everyone but me - is there any way to deactivate the second screen via fastboot,or something super-clever like that...?
Click to expand...
Click to collapse
Wow... Did you read my op before doing all of what you did?
Stop at step 2 and reboot and wait.
The knoverged kernel is broken and causes sceen to not work.
Why are you flashing supersu over my 7.5?
One has it built in and 1 uses magisksu..
No reason to do this and its causing issues.
Start over..
Can you message me via hangouts?
[email protected]
Or telegram app? Team DevDigitel
This isnt as hard as your making it.
And the us996 rom is broken without using the konverged kernel. But youll still have some issues.
Static will always be there on the ls997 unless a dev can help sort the boot.img issue with me
Aosp roms wont have static. Maybe your proximity sensor is messed up? You really need to do this from a clean slate. Im willing to video chat and walk you through it.
raenemaker said:
In case that sounded like I hadn't tried that, I DID do the hard reset to start with and then Did what I listed above, But I didn't wait for 20 minutes.
I'm gonna up the ante, though - because I needed my phone for work, I had Sprint re-provision (if that's the right word) my previous phone as my primary number until I can resolve the LG v20 into stability so I can actually do the procedure and literally leave it all day (or longer) to process. Will circle back!
Click to expand...
Click to collapse
OK, sounds good. Although you shouldn't need all day, it's probably not a bad idea. I think a lot of people get panicky, myself included, when they can't get over the hump of getting the phone to boot and get through the static screen. It sounds like you are so close to getting there. Please do let us know how you fared...
EDIT: I'll agree with @midmadn and say that you probably should flash a kernel specifically for the LS997 like Werewolf or the stock kernel. I get a little apprehensive about flashing anything non-LS997 specific. (BAD memories.../shiver/)
bgibson72 said:
OK, sounds good. Although you shouldn't need all day, it's probably not a bad idea. I think a lot of people get panicky, myself included, when they can't get over the hump of getting the phone to boot and get through the static screen. It sounds like you are so close to getting there. Please do let us know how you fared...
EDIT: I'll agree with @midmadn and say that you probably should flash a kernel specifically for the LS997 like Werewolf or the stock kernel. I get a little apprehensive about flashing anything non-LS997 specific. (BAD memories.../shiver/)
Click to expand...
Click to collapse
GAAAAAAHHHHHAHAHAAHAHAHAHAAAA!
THANKS GUYS! Werewolf did it! I can SEEEEEE!!!
Thanks so much!!!! Christ, I thought this thing was a brick, lol!!!
Team DevDigitel said:
Wow... Did you read my op before doing all of what you did?
Stop at step 2 and reboot and wait.
The knoverged kernel is broken and causes sceen to not work.
Why are you flashing supersu over my 7.5?
One has it built in and 1 uses magisksu..
No reason to do this and its causing issues.
Start over..
Can you message me via hangouts?
[email protected]
Or telegram app? Team DevDigitel
This isnt as hard as your making it.
And the us996 rom is broken without using the konverged kernel. But youll still have some issues.
Static will always be there on the ls997 unless a dev can help sort the boot.img issue with me
Aosp roms wont have static. Maybe your proximity sensor is messed up? You really need to do this from a clean slate. Im willing to video chat and walk you through it.
Click to expand...
Click to collapse
------------
Hi - OK, I think the werewolf zip (mentioned below) fixed it, but honestly I have phone service on my old device now, so I can try the above again.
My apologies, I didn't realize I didn't need to install Super SU on top of your ROM (I was erring on the side of overkill, which probably (definitely) glitched things further) -
I'll wipe clean, reinstall, leave off Super SU and konverged and just install 7.5 clean and report back.
Thanks!
raenemaker said:
------------
Hi - OK, I think the werewolf zip (mentioned below) fixed it, but honestly I have phone service on my old device now, so I can try the above again.
My apologies, I didn't realize I didn't need to install Super SU on top of your ROM (I was erring on the side of overkill, which probably (definitely) glitched things further) -
I'll wipe clean, reinstall, leave off Super SU and konverged and just install 7.5 clean and report back.
Thanks!
Click to expand...
Click to collapse
just a heads up if you DONT want to use the werewolf kernel. i have noticed if you cover your proximity sensor with your finger its possible to register a touch on the 2nd screen which will cause it not to sleep. What i recommend is turning main screen off with power button the placing the phone screen down on a flat surface that wont register a touch(i usually use a table with a piece of paper) and it works 99% of the time.
It Worked! But then...
me2151 said:
just a heads up if you DONT want to use the werewolf kernel. i have noticed if you cover your proximity sensor with your finger its possible to register a touch on the 2nd screen which will cause it not to sleep. What i recommend is turning main screen off with power button the placing the phone screen down on a flat surface that wont register a touch(i usually use a table with a piece of paper) and it works 99% of the time.
Click to expand...
Click to collapse
Hi - first: thanks!
Second: I tried the clean installs and kept getting the static. I did the "turn the phone face down on table and put it to sleep/woke it up" thing - still didn't work.
So re-installed werewolf kernel and it worked fine. For a glorious hour or so (and it WAS glorious, lol)...
Then I started installing my apps again from Google Play, got REALLY enthused and called Sprint to switch my primary phone number back to the LG from the old Galaxy Note 3, took it out to a restaurant and...
Touchscreen stopped working. Not entirely sure why - was playing with it, doing stuff like normal, etc, but suddenly when it went to sleep, after it woke back up, like my ex-girlfriend, no matter how much I poked and prodded, no response Sorry, too easy/cheesy.
But instead of being not just a n00b, but also a n00b that did the thing to you guys that I HATE to read (aka "THAT guy"), I did some digging - apparently that's an issue with v1.1 or Werewolf vs v1.0.
So wiped again, reflashed TeamDev v20, flashed Werewolf v1.0 (instead of v1.1).
And: Christmas! Kernel works fine, no moar static, everything SEEMS to be in great shape, but will report back if anything glitches up.
Hey, and I have to say, thanks to all 3 of you - the info you guys put on here is invaluable, and I know how some folks come at you like you're on the clock on their payroll, lol.
I know it's hard work and folks like me (borderline clueless) appreciate it - no joke that when I get my next check, I'll be sending a Thank$ your ways for your help with my thing and in general.
Thanks again!
raenemaker said:
But instead of being not just a n00b, but also a n00b that did the thing to you guys that I HATE to read (aka "THAT guy"), I did some digging - apparently that's an issue with v1.1 or Werewolf vs v1.0.
So wiped again, reflashed TeamDev v20, flashed Werewolf v1.0 (instead of v1.1).
And: Christmas! Kernel works fine, no moar static, everything SEEMS to be in great shape, but will report back if anything glitches up.
Hey, and I have to say, thanks to all 3 of you - the info you guys put on here is invaluable, and I know how some folks come at you like you're on the clock on their payroll, lol.
I know it's hard work and folks like me (borderline clueless) appreciate it - no joke that when I get my next check, I'll be sending a Thank$ your ways for your help with my thing and in general.
Thanks again!
Click to expand...
Click to collapse
Ah crap, I forgot to warn you about that, lol. (Haven't used to Werewolf kernel in awhile--wish they would fix that glitch.) Glad that you found the answer and got your phone back!