Related
Ok, I have been waiting for this phone for a while now (Sero plan, had to wait to Oct 1st)
Finally get it and it is acting up, not a good first impression.
Phone seems to "freeze". The screen just becomes unresponsive. Nothing is reflected as being done but I think the phone is still operating because when I took out the battery and restarted the phone, my txt draft was different from when the screen locked up (I was randomly pressing buttons on the keyboard after the screen locked)
The screen does not black out, it just freezes randomly. I can't press any buttons to do anything, I can only power off the screen and power it back on in which case it comes back to the frozen screen. My only option is to then take out the battery. Anyone have this occur to them? I don't like the idea of having to go to a store for a replacement 2 days after I received the phone..
jordan1122 said:
Ok, I have been waiting for this phone for a while now (Sero plan, had to wait to Oct 1st)
Finally get it and it is acting up, not a good first impression.
Phone seems to "freeze". The screen just becomes unresponsive. Nothing is reflected as being done but I think the phone is still operating because when I took out the battery and restarted the phone, my txt draft was different from when the screen locked up (I was randomly pressing buttons on the keyboard after the screen locked)
The screen does not black out, it just freezes randomly. I can't press any buttons to do anything, I can only power off the screen and power it back on in which case it comes back to the frozen screen. My only option is to then take out the battery. Anyone have this occur to them? I don't like the idea of having to go to a store for a replacement 2 days after I received the phone..
Click to expand...
Click to collapse
Sorry I don't have a solution to your problem, but...
I'd do a factory reset before you take it back, back everything up, do the reset, and then restore it. A factory reset can work wonders for some odd problems.
http://forum.xda-developers.com/showthread.php?p=8448259#post8448259
Easiest way to restore is to use Clockwork Recovery on a rooted phone. 1 option to back everything up, wipe all the caches in Clockwork, factory reset the phone, restore the backup in Clockwork. Shouldn't take more than 15 mins. See the developers forum on instructions on how to root and install Clockwork.
I agree your first step should be a backup/reset. If that doesn't fix the problem then swap it with a new one. I had serious freezing issues with my first Epic and eventually had to return it for a new one. Second one has run perfectly since.
zetterwing said:
I agree your first step should be a backup/reset. If that doesn't fix the problem then swap it with a new one. I had serious freezing issues with my first Epic and eventually had to return it for a new one. Second one has run perfectly since.
Click to expand...
Click to collapse
Agreed. Freezing is a hardware defect. Backup. Wipe. Check it out.
i've noticed this freeze always occurs on my phone when my it's idle. It seems to only occur when I leave the GPS on and it appears to be searching causing it to freeze.
Hi all,
I have had loads of problems with this phone, so I decided to do a factory reset.
It rebooted as normal until it got to the Motoblur setup page
It asks for the Motoblur details to be entered, but once you have entered them and pressed the 'next' button, it goes back to the previous screen instead of the next step and then gets stuck in a never ending loop.
I've tried skipping the sign in process but instead of skipping it, it just goes back to the first Motoblur account setup screen instead.
Out of desperation, I have tried to make several new Motoblur accounts but every single time, it gets to 80% completion, then stops.
I have even left running all night (plugged in) and it still freezes at 80%
I can't do another factory reset because it won't get past the Motoblur setup screen.
I've tried to do a hard reset by holding x and powering the phone on but this doesn't work. It just brings up the triangle and android robot but it does not go to the next step despite me leaving it for several minutes.
Only had it for 7 weeks and am awaiting a response from Expansys on what to do.
Any help from you guys will be greatly appreciated.
Apply a debrand image of your system and do a full wipe
phorenzik said:
I've tried to do a hard reset by holding x and powering the phone on but this doesn't work. It just brings up the triangle and android robot but it does not go to the next step despite me leaving it for several minutes.
Click to expand...
Click to collapse
Have you pressed the @ key when you get to this step with the robot and the triangle? That should bring up the reset menu, and then you use the volume and camera buttons to choose and select the option you require.
Cheers,
Steve.
StevePritchard said:
Have you pressed the @ key when you get to this step with the robot and the triangle? That should bring up the reset menu, and then you use the volume and camera buttons to choose and select the option you require.
Cheers,
Steve.
Click to expand...
Click to collapse
I didn't know you had to press @
Thanks
I've done a hard reset, but I still have the exact same problem.
If I try to input my proper Motoblur details it instantly says connection failed (it doesn't seem to even try to connect as fails the instant you press 'next)
Creating a new account hangs at 80%
Any more ideas before I throw it against a wall?
I notice there was an option to boot from SD in the recovey mode.
Would this allow me to boot an official motorola rom?
If so, where would I get the rom from?
A walkthorugh on exactly how to do this would be appreciated if this method could fix my issues.
I'm really annoyed because I sold my HD2 for this phone and I'm regretting it.
Thanks
phorenzik said:
I didn't know you had to press @
Thanks
I've done a hard reset, but I still have the exact same problem.
If I try to input my proper Motoblur details it instantly says connection failed (it doesn't seem to even try to connect as fails the instant you press 'next)
Creating a new account hangs at 80%
Any more ideas before I throw it against a wall?
Thanks
Click to expand...
Click to collapse
I think you need internet connection in order to validate your account or create a new one. Check your APN settings first, or do it on wifi.
Hi,
I've tried it whilst connected to my wifi router. I've even tried it via the data connection but nothing happens.
It seems that despite the data/wifi connections being there, it just ignores them.
I think this is the issue. It's not connecting and I don't know why
The phone displays the wifi/3G data symbols in the task bar but it doesn't seem to be using them during the Motoblur setup
Mine is dead too!!!
Hello everybody,
Greetings from sunny, flooded, blown away, Queensland Australia!
Long time lurker, first time poster...
I have a...
Vodafone-Australian-2.2-Milestone2
2 weeks old and its an expensive paper weight. It was rooted and thats about it, had a bunch of root required apps on there, installed the bootstrap, but hadnt installed Xrecovery yet.
I was playing around the other day. changing settings, installing and uninstalling a heap of apps, testing them. Some app suggested I restart or it restarted itself, cant recall, and that was the end. Boots until it gets past the M, and then its just bootloop city.
Won't register on comp in RSD or anything. Will boot to stock recovery and cleared cache and data several times, but that didnt fix anything. Won't even charge the battery. It will run an update but has to be signed. Problem is, we havent had any updates yet on these phones in Australia and there are no custom roms. What update.zip could I get to try to fix it, because I think thats about my only hope.
While recovery was wiping the data and cache it would stop frequently and each time I would touch the ok in the bottom corner of the screen and it would continue, and seemingly despite the 10 or more stops, completes fine. Surely thats not normal.
Out of ideas, I would just send it back with a story but the vodafone boot animation is replaced with disco flashing lights. and thats all it does, non-stop. Do you think they will notice someone has been tinkering?
Ideas? Thoughts?
Oh, and forgot to mention, when I first got it I had the same problem with the Motorola sign in wizard on startup, for quite a while, cant remember how I got around it though. Stop trying to sign in and just get out of that wizard, install ADW Launcher or similar and dont go near any Moto apps. You are only required to do a Gmail sign in, not Moto.
That's the problem though.
I'm stuck at the Motoblur sign in and it will not skip.
Whenever I select skip, it just goes back to the motoblur sign in page instead of going to the home screen.
Basically, in a nutshell, this is what's wrong:
I can't sign in to motoblur (gets stuck in a loop)
I can't create a new motoblur account (crashes at 80% every time)
I can't skip the sign in process (takes me back to the motoblur sign in page instead of loading home screen)
This is my first and last Motorola phone. Not good at all.
So what happens if you press press home or back repeatedly instead of skip? And if all fails reflash new SBF
benking1972 said:
So what happens if you press press home or back repeatedly instead of skip? And if all fails reflash new SBF
Click to expand...
Click to collapse
It just goes back to the motoblur setup/signin screen no matter how many time I press home, back or skip. It's as if a dll is missing and it's unable to boot to the home screen.
How do I flash a new SBF?
Motorola have agreed to let me return it but if I can do it myself I'd rather do it.
I have found this guide http://forum.xda-developers.com/showthread.php?p=11155476#post11155476
but the link to the UK SBF is dead
Yeah, that's the one, and the link to UK SBF works fine for me. If you can't get it to flash that way, then you are going to have to do it the way I am about to do mine, which is...
http://forum.xda-developers.com/showthread.php?t=804088
Failing that, send it back and be done with it.
since its so new id send it back. you shouldnt be having this problem at all. the milestone 2 is a very solid phone. i had mine running for 90 days straight not even a reboot or crash or anything lol. sounds like you just got a duff one. with any piece of technology theres bound to be a few that slip through the net. even if you find a fix for your problem you dont know what is causing it. and if youve had problems before then somethings obviously wrong. since theyve agreed to let you return it then thats your best option.
Probably i should send mine one back as well.
Bought a new Milestone 2 yesterday (from ebay, Chinese guys but as per retail package phones are for UK market). Put the SIM in just to check before wiping out everything from my old Defy. Made a call, checked the version and the menu and put the SIM back to Defy to backup all I needed. Plugged Milestone to the mains. 3 hours later found promising "Fully charged" on the screen and put the SIM in. That was it... Since I can't power the phone whatever I do. I thought the Power button went off as I tried to perform hard reset (x+Pwr), BRM (Arrow up+Pwr) and nothing happent at all. But then I put the phone on the charger again and the Power button worked fine switching the screen off and back on.
Any other methods to get the phone running?
UPDATE: It's strange and weird, but I've just had an idea to remove SD card and it worked - the phone powered on immediately!! Formatted the card using card reader, put it back - the phone works flawlessly. Fantastic! =))
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
It sounds like you're suffering from some sort of hardware failure. You need to send your phone in for repair/replacement.
The Unnamed Time Lord said:
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
Click to expand...
Click to collapse
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Same issue here...
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
then i shut it down, pulled the battery and then back, and restarted: the phone goes directly to that black backlit screen, i tried several times and tried recovery with no luck, so i thought my phone was messed up although i did have some haptic feedback, well in fact the phone was actually booting, but just not showing anything else than the backlit screen; i waited a minute or so to the booting completes (still shows nothing), then i lock/unlock the screen again and there it is, asking for the pin code.
I tried to go to the recovery again to try to wipe dalvik-cache, i know for sure it goes to recovery, but with a totally black screen, not even backlit this time; the trackpad is too sensitive in the recovery to just blindly navigate in the menu, so it is not useable at all.
Then i had the idea to go to Rom Manager, i reflashed the rom from my sd-card, and enabling wipe dalvik-cache, which worked (all through a black screen). After a few minutes i "felt" it rebooting (vibrating) but still back to that black backlit screen, and i locked/unlocked it again and back it was asking pin code...
I also tried to roll back recovery to 3.0.2.4, since i remember i updated it a few weeks ago, but still the same issue.
I don't know what else to do without accessing the recovery, i wanted to try another kernel, or remove the trackpad wake... is there a way to do it via a script? I guess it's what Rom manager does...
Next step will be a total wipe, but i need to make some room on my sdcard for backup purposes first...
If anyone has an idea to sort this out, i'm highly interested...
I'll try to get a logcat, maybe could give a hint
Edit: Virtuous sense 2.0.0 (used it with no issue since it came out, could it be a hw issue?)
Edit2 : attached logcat
Is the pin screen differant than the usual one ie white number keys? If it is that's the sim lock screen you need to call the carrier to get the code or find out the default. Or just get a new sim lol
nah it's the 4 digit pin code, i didn't lose it btw, it's still working and i can use the phone, but i have a black backlit screen whenever i want to wake the phone, and thus when i receive a phone call, i don't know who it is and i blindly press/swipe the screen to answer, because if i want to use the same trick of locking /unlocking, it doesnt work as the lock button is also used to reject a call...
Maybe rip and reinstall the phone app?
asim0 said:
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
Click to expand...
Click to collapse
I have the same exact problem as this EXCEPT, it's intermittent. Sometimes when I wake the phone I get an all black but backlight screen, and other times it's fine. I'm on CM7.1.
But a superwipe and reflash will probably fix it. Also don't restore system data on TB
I know i still can use wipe data + cache + dalvik through rom manager, and i always used to superwipe before switching roms, but how can i do that now when the recovery is all blacked out?
can anyone guide me to a script or something i could do while the phone is active, to tell him to reboot to recovery and flash that superwipe?
anyway i'll try the regular wipe and keep the thread updated
---------- Post added at 02:42 PM ---------- Previous post was at 02:35 PM ----------
SuperDave81 said:
EXCEPT, it's intermittent.
Click to expand...
Click to collapse
On my side if i leave the phone locked more than 30 seconds, it happens 100% of the time; also I noticed that now the backlight blinks 2 or 3 times (1 second blinking) when locked, first a few minutes after locking, and then randomly, about 3 or 4 times per hour; I guess it's getting worse;
I've read on another thread that it could be video cable getting loose, but since mine is still under guarantee, i won't open it right now just to check, if i can't fix by wiping / superwiping (when i know how to), i'll use that guarantee, which is one month left (lucky me)
EDIT: one other thing that makes me think it's no hardware, when the black screen appears because of a phone call or a message, the ringtone and notification sound are both half as loud as they should be, this is all really strange
after backing up my data, i reflashed the rom via Rom Manager, and I wiped data and cache (which equals to factory reset) this time: the first screen that should show the pin code numpad was already a black (backlit) screen!!
Also, thinking about it, i realised that the "flash rom from sdcard" menu in Rom Manager is in fact "Flash ZIP from sdcard": the zip doesn't have to be a ROM!!
So I tried flashing a new kernel this way, also some framework modifications (extended settings, removed TP wake, etc...) they all install Ok, but still this black screen...
Also I was about to flash SuperWipeG2.zip this way, but if it doesn't fix my problem, I will be stuck with a blacked out recovery, as SuperWipe wipes everything including /system; so if anyone has an idea to tell Rom Manager to flash two zips (Superwipe then Rom) i'll be willing to try, or a script to do that;
Maybe i'll have a look of the scripts in Superwipe and in the rom, and put both zips together... don't know if it's possible?
Maybe I'll try the Superwipe alone if I can get a spare phone, just in case...
Other thing:I used the phone's gps for more than 5 hours with the screen lit, and it never flickered even once; so it's hard to believe it's a screen connection issue...
Just to keep this updated, everything i did, including superwipe didn't change this issue, so i sent it back to the technical support (under guarantee) and I got it back today; the report that came with it says the screen has been replaced; so it was hardware finally...
Hi, i have same problem.. Black screen in recovery and during the boot. When the system boots, screen is OK. Sometimes i have also blackscreen when I want to use HW keyboard. I tried 4ext, reflash older versions of CW but still the same. I can see a screen through Android Screen Monitor and I can cotrol it. But phone is blak, only backlight. Can somebody say, how to solve this issue?
So, for other, if you cant see screen, you can use Android Screen Monitor for Windows and connect phone through USB and see a screen.
G1ForFun said:
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Click to expand...
Click to collapse
WAIT one minute... they don't care? where was I when this meeting took place?
I had this issue as well on a spare G2 I had.
The screen was just black but you could tell it was lit, hardware keys were lit as well.
The phone was actually my brothers and it rooted w/ CM7.
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
I never attempted to get it replaced and kind of wish I did now if they don't care about the device being rooted.
I purchased my G2 before he had his, and it's never had the issue so not sure what to think of it.
Saintfyre said:
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
Click to expand...
Click to collapse
I think I have similar issue, can you post where you found those instructions?
Thanks in advance!
http://www.youtube.com/watch?v=u-dR8CHEGjY&feature=youtube_gdata_player
Sent from my HTC Vision using XDA Premium App
I used the same tutorial to change the LCD but after I put the new its just the backlight but nothing else... I will give it another go maybe and have a look again at those ribbon cables! I guess...
---------- Post added at 10:59 AM ---------- Previous post was at 10:09 AM ----------
I found on ebay: HTC-Desire-Z-T-Mobile-G2-A7272-Slide-Flex-Cable-Ribbon
or I found also with the chassis for a bit more.
Thinking to buy this, it would be great if anyone could confirm that it would help "my condition" ?
THanks in advance!
In terms of cables, yes the flex cables are what you want.
Sent from my T-Mobile G2
I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.
Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by
Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?
You have safestrap installed, correct? If so, what version?
Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?
Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.
Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.
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!