OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
erica_renee said:
No clues other then if it onlybruns a few minutes is it getting hot
You can open the back with a credit card. Remove your similar then go along the edge starting acoss the tap taking care and be gentle. The plastic on the back is part of what removes as part of the metal to back cover.
Hope this helps
Click to expand...
Click to collapse
I might try that soon, gonna keep at it. It's not a heat issue; it only runs a few secs before it shuts down. I know it's got something to do with me formating the data and not finishing the reset.
Have to ask, but is the bat flat or does it do it plug in.
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
SmittyRN said:
OK, I've got a buck thirty-seven in loose change and a John Denvers Greatest Hits cassette for whoever can help me out with this one. I was going to return my Icona to stock last night so I could let it update to 3.1; using Thors CWM, I formatted /system then /data with plans to do a factory reset (out of habit from flashing my phone every week or so, I probably didn't need to). Before the data finished formatting, I got called away from my desk to the OR and ended up leaving the tablet alone for the rest of the night.
This morning, I found the tablet powered down; when I booted it, I got the Acer screen, then the android screen, then it powered down. When I tried to use a USB keyboard to get into recovery, I got nothing. When I tried to boot and hold the "-" down to flash update.zip, it would power off before it would get there. Tried to use the hard reset, nothing.
Put my son on the project today while I was working. He tried everything he could find, specifically the 9-step procedure. No luck there, it will power off before he can get anything done. Strange thing is I just picked it up after it has been sitting a while and tried to boot into recovery, and it went into CWM.... for about 5 secs, then powered down. Now it won't boot into recovery, powers down quickly. He said it did that earlier today, so it seems that if you let it sit awhile and boot, it at least will get into recovery initially (I'm gonna explore that theory, letting it rest now).
Anyone got any advice or ideas? I've searched the threads and can't find anyone who has had this problem yet. If the damn thing had screws on the back, I'd take it apart and drain the battery down. Someone throw some genius my way.
Click to expand...
Click to collapse
Well, I let it sit for a while, and instead of holding down the "-" key, I plugged in the keyboard and pressed the home key. Nothing seemed to happen, but when I turned it back on after that it booted up and let me go through the setup screen. Strange, but at least it's working.
shaun298 said:
Have to ask, but is the bat flat or does it do it plug in.
Click to expand...
Click to collapse
Yeah, sorry, I have no idea what you are asking.
tkirton said:
Changing my post...I got a question instead:
When you hold down the "-" key, do you see anything on your screen saying the recovery key was pressed?
Click to expand...
Click to collapse
Yeah, it would say that the recovery key was pressed or whatever, just for about 1 sec, the shut off.
Related
I'm hoping someone can help me. For some wierd reason the other day my phone tunred off on me. When i went to turn it back on it was frozen on the boot screen. Will not go past it. Ive tried holding the power button to get to the magldr menu and reflash my coredroid but cant even do that. I tried a diff battery..nothing. Tried the little yellow button ythe battery and again...nothing Let it sit for 3 days and still the same....
Anyone know how to reset or is this phone just a paper weight now?
Are you using CWM? if then try clearing cache. Format, re-partition will do the trick.
nshivas said:
Are you using CWM? if then try clearing cache. Format, re-partition will do the trick.
Click to expand...
Click to collapse
But I cant get there. It stays stuck on the boot screen. Even when I hold the power button down it does nothing...
check out my thread, it may help
yz.hd said:
check out my thread, it may help
Click to expand...
Click to collapse
cant get into bootloader. totally stuck....cant even get my phone to go from charge only to disk drive to see my files.....
omar...what happens when you pull the battery, put it back in, reboot and hold down the DOWN volume key?
jsmccabe78 said:
omar...what happens when you pull the battery, put it back in, reboot and hold down the DOWN volume key?
Click to expand...
Click to collapse
Nothing. Phones been without a battery since Wednesday. This morining iI thought i'd try to see hwat happens and ..nothing Ive been using a backup phone. My new one got in today. So i'll go home and load the hspl,magldr & rom and like i said give this paper weight to my son as a toy...lol. I wouldve like to unfreeze it and try to sell it to help pay for the deductible atleast. But no biggie....
After booting my tablet for the first time, I connected to the internet. The unit then told me that I needed a system update (4.something). I clicked ok. The system connected and downloaded the update. It seemed to install it. It then attempted to shutdown and it hung up at the final moment and the little activity circle just continued to go round and round.
I forced a shut down and rebooted. Next the "ACER" and the "android" came on the screen in that order. Next the tablet said that it was shutting down and the same thing happened -- it hung up again with little circle. Every time I attempt to reboot it repeats the same cycle. I have tried resetting the unit and holding the power and the volume+ down on reboot, but nothing seems to help.
I tried phone tech support and they sent me to a third party repair that charges even when the unit is under warranty. Acer support was not even accepting emails! This is a strange customer support.
Can anyone help?
Thanks
How long did it hang at the spinning circle? Probably what it was doing was updating you to HC 3.2. Sometimes it can take up to 20 minutes before if finishes.
I suspect maybe you force booted it before it could finish.
The easiest thing, would've been to take it back to the store for a replacement.
However, you might try the factory reset option. I've never used it, but, you'll see a small pinhole near the power button. With power off, press and hold the pinhole (with whatever you can find to fit, mabe a small paperclip) and power on I believe (check your instructions). Hopefully, the failed update didn't mess that up also. But probably did. Or did you already try this method according to your original post?
EDIT: Also, I would check your SD card, and remove what is on there. You can format it in your pc to FAT32. Then install it. This will ensure any garbage is removed from it.
Next, check this link;
http://forum.xda-developers.com/showthread.php?t=1276227
Pay attention to method 2. That might get you up and running, although with an unstable version. But, it will be running and allow you time to get another stable OS on it.
Check back with your progress.
Moscow Desire said:
How long did it hang at the spinning circle? Probably what it was doing was updating you to HC 3.2. Sometimes it can take up to 20 minutes before if finishes.
I suspect maybe you force booted it before it could finish.
The easiest thing, would've been to take it back to the store for a replacement.
However, you might try the factory reset option. I've never used it, but, you'll see a small pinhole near the power button. With power off, press and hold the pinhole (with whatever you can find to fit, mabe a small paperclip) and power on I believe (check your instructions). Hopefully, the failed update didn't mess that up also. But probably did. Or did you already try this method according to your original post?
EDIT: Also, I would check your SD card, and remove what is on there. You can format it in your pc to FAT32. Then install it. This will ensure any garbage is removed from it.
Next, check this link;
http://forum.xda-developers.com/showthread.php?t=1276227
Pay attention to method 2. That might get you up and running, although with an unstable version. But, it will be running and allow you time to get another stable OS on it.
Check back with your progress.
Click to expand...
Click to collapse
I can confirm this will work, the 3.2 update bootlooped my tablet too when i first got it but I just reverted back and even through the force closes was able to root and load CWM then go from there
sent from my Acer Iconia A500 beast of a tablet via XDA app
Thanks for the help. I am returning the unit.
I discovered that the unit was not charging the battery. I initially had pluged in the the unit to charge for 3 hours. After that I tried turning it on. During the numerous restart /shut down attempts, I noticed that the battery icon showed that the battery had not charged at all.
I next charged the unit for straight 10 hours. It still behaved the same way starting and then shutting down. The battery had not charged at all from the 10 hours of being plug in. I checked the charger and it was outputting a full 12 volts.
I called the vendor and will return the unit tomorrow.
Thanks for your attempts to help me.
JW
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
FluffyMittens said:
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
Click to expand...
Click to collapse
I think you've got your terminology mixed up. Bootloader is the mode that comes up by pressing both volume keys while powering on. This is where you flash stuff through RSDLite or use adb server to push and do hacker stuff.
Recovery is the phase where you can do factory wipes and data formatting. I can't get into recovery.
When you flash an SBF, it should be flashing a new recovery. I think the phone is hosed.
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
infazzdar said:
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You've got to be ****ing kidding me.
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
FluffyMittens said:
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
ADB isn't working. I don't think ADB works in bootloader.
You ask me what I have done so far, but I already put all that information in the OP. That is why I was so frustrated with that second guy. If you guys would take time and not skim over my post that I actually thought out and typed ****, you wouldn't have to waste your time asking me what I have done.
I appreciate the ADB suggestion.
Just trying to collect some information. I'm someone that doesn't let a phone just be deemed as bricked. How charged is the battery?
-Edit: Just checked, ADB doesn't work in bootloader. Confirmed by having RSD open and making sure it sees it, and then tried adb devices. Also as a supporting confirmation for the fun of it, ran the one click root.
-Edit: Further thinking about it, was this phone submerged in water or just had moisture in there? There could just be some minerals formed up on the board that a toothbrush would get rid of. I've fixed phones a dozen times. Some phones will turn on and get stuck. Some wont turn on. Some the backlight comes on but no video signal.
Deoxit
My guess is that the buttons aren't working. There's no way to test that since you can only get to the bootloader, but if you can successfully SBF the phone the odds of any of the solid state gear being bad are pretty low. It does seem odd though that you can't make it to the boot animation and get stuck at the boot logo.
I would suggest getting some deoxit (tv tuner cleaner) and spraying it in around the hardkeys on the bottom of the phone. You don't need too much (especially since it might end up behind the screen). Spray that in there and then work the buttons a few dozen times. That should loosen up any corrosion on the switches and let them close the circuit again. If that doesn't do it, I'm out of ideas, but at least you'll have some deoxit lying around (stuff is great for static-y radio/stereo volume control knobs, etc).
The battery is pretty well charged. When I got it in the mail, there was no charge. I cut a USB cable and hooked it up to power. After about 2 minutes, I tried it. It got to bootloader but said battery was too low. I used the cut USB cable and hooked it around the battery pins in the phone and put the battery in, so it charged it at the same time it was tricking the phone into thinking the battery was full.
Also, if you go into Bootloader and then power off the phone, the green LED comes on. I'm assuming that means it's charging? I was skeptical since all we hear is that you're ****ed if your battery runs out at this stage of the game. It was off this morning and had been plugged in with the green LED all night (no USB cable hack).
As for trying adb while RSDLite is open, no go. adb devices shows blank. Motorola OneClick root didn't work either. It just sat there waiting for my phone. I didn't have the balls to plug in my Bionic to see if Motorola OneClick would work (and therefore the problem is with the Droid X).
As for the water damage, who knows. The lady I got it from was surprised when I told her there was moisture under the screen. I'm not her mommy so she didn't have any reason to withhold information from me. I just thought a bag of rice, a $12 battery off Newegg (free shipping, too), might just get me a sellable Droid X out of the deal.
As for the hardware buttons - they feel like they're clicking, but I know that obviously isn't the 100% test whether they're functioning properly or not. The volume buttons and power button obviously do function, since I can use those to get into BL.
Another brain jog idea: Is there an SBF out there that wipes the data and cache, along with all the other **** it puts on? This probably won't work because I still should be able to get into Recovery - something is FUBAR.
Please give up if you feel like giving up. Bricks exist. This may very well be one of them.
P.S. The girl that gave me this dropped her new iPhone 3 days into ownership. It only cracked the back glass, but the point still remains: she may not be the most graceful phone owner on the planet. Who knows what this DX has been through.
Thanks for all your help, guys.
I would try cracking that thing open and seeing if there are any mineral deposits and cleaning them. This means those weird clips and stuff too, just take a toothbrush to the whole thing and see where that gets you.
As with giving up, I'm a pretty bored guy and finding something to do is better then sitting around and watching Star Trek.
I haven't lost a phone once
Edit: Except for this [email protected]*% of an ACN voip phone that I buffer overflowed in attempt to gain root.. That ended badly.
Same problem
I had the same problem with my dx trying to sbf to .602 I ended up flashing the stock stock froyo sbf and upgrading to gingerbread by rooting and flashing CM7 or any other gingerbread rom. You didn't specify whether or not you tried froyo sbf. No idea if this will work for you but its worth a shot if you haven't already tried it. I also had to use RSD lite 4.9 or 4.8 to get the sbf file to work right.
I'd like to toss my problem into this thread if it's alright. The OP is the closest description to my situation I've read. A co-worker brought his phone to me and it would only get to the round red logo and stop there. No bootloop just a freeze at the red logo.
I tried different ways to get to recovery but was only able to get it to the white bootloader screen. (30.04) So I flashed .340 using RSD and it completes and tells me to manually start the phone. But the phone is already at a white logo (not a red one). I do a battery pull to restart the phone and I still can't get the phone to a recovery by holding down home or any other key while powering on. Battery charge is near full.
The owners explanation of how the phone got this way is that he woke up one morning and there was a 'protection mode' transparency on the screen so he rebooted and had the red logo from then on.
So, I can RSD flash just fine but the phone won't get past the black screen with the white and black M logo.
I would try flashing other files or even the Linux CD option but I can't find anything downloadable since mega got shut down.
Any advice would be appreciated.
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
NType3 said:
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down together gets buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
Click to expand...
Click to collapse
1. Would be happy to try .602. Do you know of a working link?
2. It never gets to the eye.
Edit... I found a 602 iso to make a CD boot disk from and used that. The install went perfect but the phone still just boots to a red M logo and freezes there. It doesn't get to the red eye and no button press combo can get it to the recovery screen. I can only get it to the bootloader or let it go to the red logo. The buttons don't feel sticky or anything and the batt is fully charged.
The Fix
Skyroket said:
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Click to expand...
Click to collapse
This will have all sbf working files and linux operating systems along with everything you will need try to sbf one of those preff linux. If this doesn't work and your still stuck! Go to this web page you will need.
Motorola Droid X Motherboard Flex Cable Replacement
Motorola Droid X Keypad Flex Cable Replacement
http://www.repairsuniverse.com/motorola-droid-x-replacement-screens-repair-parts.html
Finally here is how you take it apart with out damaging it.
http://www.youtube.com/watch?v=wo7dXyJhL1U
GL to you enjoy your droid x once ya get it working!
I always have to sbf my dx twice, I always boot loop the first time.
Just fyi, if you bootloop after an sbf, you can pull the battery, boot into stock recovery with the usual key combo format data and you'll be all set: no more bootlooping (or double sbfing!)
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!