Just got a s/h exec and I think it is faulty. Whats happens is it starts up ok and works for a while and then for no reason that I can think of it goes into a loop which stops it from working.
When I say a loop I'm not sure thats the right terminology but imagine if you tapped the start button and the start menu opens... and then imagine you tapped the tab button , the next item would highlight. If you tapped the tab button again the next item would highlight and so on. Well its as if the tab button is being hit over and over because all the items in the start menu will be highlighted one after the other over and over again.... it just goes round and round in a loop.
Its possible to escape from this and go to another screen but the same looping will go on in that screen too.
If you switch off and leave for a while and come back to it it works ok for a short time and thens starts the carry on again.
Sometimes if you just wait a while it stops, but will start doing it again even if you dont touch anything.
I've noticed one way to force it to stop is to slide the volume button... this seems to stop the loop and allows normal function for a while.... then the crazy looping starts again.
Has anyone seen this or know anything about it.
Nope sorry, maybe you can have it replaced where you bought it as from your post, you can recreate the problem easily.
Side Note : Have you tried Hard Resetting? Or installing another ROM?
I have tried hard resets and factory reset... problem remains.
Will try new ROM.... just trying to figure out how to do it !
weegee said:
I have tried hard resets and factory reset... problem remains.
Will try new ROM.... just trying to figure out how to do it !
Click to expand...
Click to collapse
Just download a new ROM form imate or something, unpack all the files in the ROM update to a directory, put the attached file in same directory.
Enter bootloader mode (Backlight + Power + Reset Hole) you will see SERAIL on the screen but not backlight so look hard.
Plug into PC, the SERIAL will change to USB
Run the attached file. You will see a photo of an S100 but continue anyway....
Hard reset when finished... DOne
ok have installed latest rom... but exec still doing loop loop
Just for arguments sake, can you try installing Imate's newest ROM?
yea thats the one i have just put on.
It seems to be doing the problem less than before. I notice that it does stop if i press the backlight key or move the sound slider.
I'm wondering if there is dust or dirt got in behind the buttons or something like that... although I would have thought other people would have come across this b4 if that was the problem. The machine is one of the first to come out, although I just got it a couple of days ago.
weegee said:
yea thats the one i have just put on.
It seems to be doing the problem less than before. I notice that it does stop if i press the backlight key or move the sound slider.
I'm wondering if there is dust or dirt got in behind the buttons or something like that... although I would have thought other people would have come across this b4 if that was the problem. The machine is one of the first to come out, although I just got it a couple of days ago.
Click to expand...
Click to collapse
If you have tried different ROM flavors and still get the same problem, then it is definitely hardware related. Send your unit in and demand for a new one not a repair
Just been playing around with it again and notice that I can make the problem happen if i press any of the keys on the navigation pad except the top one.... and i can stop the loop by pressing the light button.
Weird or what.
My initial thought on this is maybe its got wet at some point
I have opened the xda up and stripped it down to all its parts. No sign of any dampness or dust dirt etc. Dont see anything missing or broken.
Put back together, but still doing this.
Driving me nuts.... its a great machine but is very tiresom to use with this going on.
Another think I notice about this machine, I have never used it as a phone, but I tried putting a sim card in and There is no sound through the earpiece. Only sound comes from the speakers when you set it to speaker phone.
I suggest just return it and have it replaced. It's probably a faulty button. Probably gets stuck whenever you press it.
Doesnt need a button to be pressed for it to start.. just starts by itself... and can stop by itself too.
Sometimes it can for ages without doing it, other times it does it all the time.
Cant figure if its hardware or software problem
GHOST-IN-THE-MACHINE
Yea... maybe I should get a priest !
I had this problem when i first got mine, if you move the sound slider down, then up, it seems to stop doing it for a while, and it hasn't happened in the last couple of weeks atall, maybe its because its new, and just needs to settle in?
Jay
Well at least I'm not the only one to have it.
My sound slider does stop it happening but only for a while and then it starts up again.
The machine is perfect in every other way, its just an annoyance I could do without.
I've tried everything, even stripped it down and left parts out, like buttons, to see if they are the source, but no difference.
I have the same problem!!!!!!!!!
Someone help please!!!!!!!!!!!!!!!!!!!!!!!
I have same problem. I send to service but until today they can't repair that problem.
My phone is SM-N900V running Android 5.0. It has recently gotten very temperamental. When I swipe to open it, I can feel the vibration as if I can tapped to open an app, and then s finder opens automatically. I can try to close it, but then it just reopens...I can go through this many times and sometimes it will settle down and behave normally for awhile...sometimes for quite awhile. Sometimes, I will get a reaction similar to doing a long press on the screen when at the home page, bringing up a smaller version of the pages, allowing easy movement between pages...and all this with me doing nothing. I have done factory resets (power off...hold home, volume up and power button to get to recovery and select factory reset), and this seems to work for a short while...maybe days, but then the automatic opening of s-finder is sure to return. Not sure if this is a reflection of the touch screen going bad, or home key, or ???? If someone has a thought on this or what might be the part most likely having gone bad, I can try to obtain a replacement and see if it can be fixed, but I really have no idea what might be the most likely culprit or how to better narrow down the problem. I'm wondering if this maybe was related to a recent update??? Is it possible to roll back to an earlier version of Android to see if this solves the problem? Any help is most appreciated.
Regards.
Uninstall last apps or try to remove screen protector or magnetic flip cover. If not good try to open phone and reseat display flex cable.
Sent from my Limited Edition Note 3 LTE using Super Tapatalk
When it happens, try to dial *#111*# and choose LCD test. (you may need to power it off or remove battery to exit that mode)
See if there are ''ghost touches'' appearing, or when you secure on it, if appears some touching marks. If so, note if the screen is hotter on that zone. If so too, then your screen has a defect.
If not, it's a screen cleaning problem, or software problem.
Anyone replaced home button (fingerprint scanner)... My button is dead and in ebay you can order one for 9.99$ ...
lummujaj said:
Anyone replaced home button (fingerprint scanner)... My button is dead and in ebay you can order one for 9.99$ ...
Click to expand...
Click to collapse
Are you sure that the button is actually dead? I've read of a lot of people having the issue whereby the home button stops responding, and I've actually had it happen on my OPT twice myself and it's not been the hardware...
Two quick things to try (if you haven't already)
1) Try a force reboot of your phone (fixed my issue the first time it happened to me) - by this I mean press and hold the power button for ages, until the phone eventually just powers off immediately (without going through the shutdown process) and then power the phone back on.
2) Not sure if you have rooted your phone, or have a custom recovery (TRWP) but if so try wiping the Cache (not the Dalvic / Art Cache, but the other Cache) and reboot (fixed my issue the second time it happened to me).
Hope this helps.
lummujaj said:
Anyone replaced home button (fingerprint scanner)... My button is dead and in ebay you can order one for 9.99$ ...
Click to expand...
Click to collapse
If you have followed all the software solutions, still under warranty then RMA.
I faced this issue once, fixed it pushing around the sensor with my finger nail I did push really hard until it change to home screen it was 6 or 8 week's ago, haven't failed since
Sent from my ONE A2005 using Tapatalk
juststarted said:
Are you sure that the button is actually dead? I've read of a lot of people having the issue whereby the home button stops responding, and I've actually had it happen on my OPT twice myself and it's not been the hardware...
Two quick things to try (if you haven't already)
1) Try a force reboot of your phone (fixed my issue the first time it happened to me) - by this I mean press and hold the power button for ages, until the phone eventually just powers off immediately (without going through the shutdown process) and then power the phone back on.
2) Not sure if you have rooted your phone, or have a custom recovery (TRWP) but if so try wiping the Cache (not the Dalvic / Art Cache, but the other Cache) and reboot (fixed my issue the second time it happened to me).
Hope this helps.
Click to expand...
Click to collapse
None of above have worked for me. I've a rooted A2005 running unofficial CM 13. A couple of days back it just stopped working. I thought it's a bug in the ROM. Changing and clean flashing the ROMs didn't fix the issue. Then I realized it's something serious as I remembered that it may have got some moisture when it was inside the chest pocket of my shirt and I got sweat due to some physical hardwork. I'm still not sure though as to what caused the problem.
I would really appreciate if somebody comes up with a solution. Yes, pressing hard the home button has not worked for me either.
MusadiqManas said:
None of above have worked for me. I've a rooted A2005 running unofficial CM 13. A couple of days back it just stopped working. I thought it's a bug in the ROM. Changing and clean flashing the ROMs didn't fix the issue. Then I realized it's something serious as I remembered that it may have got some moisture when it was inside the chest pocket of my shirt and I got sweat due to some physical hardwork. I'm still not sure though as to what caused the problem.
I would really appreciate if somebody comes up with a solution. Yes, pressing hard the home button has not worked for me either.
Click to expand...
Click to collapse
could really be the moisture like u said.
heard the home button is very sensitive to that.
Mine got broken from moisture too ... I created a thread in oneplus two forum also.. A guy there posted and flamed me for not searching forum bcouse there is a sulution to fix homebutton from moisture broken
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!