Database Users

[Q] Please help me

As suggested, starting a new thread.
Hello,
Straight to the point, Rooted UK Atrix, running 2.3.4. no other MOD OR rom or anything, i like motoblur.
Stupidly Used Bloatfreezer to freeze 'home' without having another launcher to return to. Can't use the phone now. Trying to reset (hard or soft i do not know the difference) and the phone reads ''fastboot'' then i toggle down using volume - to android recovery and the phone is coming up with starting rsd protocol x2 and nothing else (using the power + & - methods).
If i leave my phone to just boot it resides on a white screen teasing me with noises of logging in but i cannot see anything.
I'm really lost to be honest, i have no idea what to do and i am not good with terminology either (adw, flashboots, cm7 i have no idea what they are).
I know there are sooo many threads with different answer's so that is why i am starting a new thread.

To factory reset using recovery...
1.Power off the phone, press and hold volume down button, press power button.
2.Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", press Vol up key
3.Wait for the "triangle ! / Android" screen then release the volume down button
*4.Tap on bottom right corner of the screen (may take a few times). a menu will come up
5.Tap on "wipe data/factory reset", and press OK. Another Confirmation screen will come. Press Yes and OK
6.After userdata is cleared, the "reboot system now" option will be highlighted by Default. Press OK.
7.Phone will reboot to initial setup MOTOBLUR screen.
NOTE/If on Android 2.3.4 then replace step #4 with pressing both Volume buttons at the same time. Also, use the Power button to activate the highlighted option instead of looking for the OK.
Sent from Rob's Atrix

atrixuk said:
As suggested, starting a new thread.
Hello,
Straight to the point, Rooted UK Atrix, running 2.3.4. no other MOD OR rom or anything, i like motoblur.
Stupidly Used Bloatfreezer to freeze 'home' without having another launcher to return to. Can't use the phone now. Trying to reset (hard or soft i do not know the difference) and the phone reads ''fastboot'' then i toggle down using volume - to android recovery and the phone is coming up with starting rsd protocol x2 and nothing else (using the power + & - methods).
If i leave my phone to just boot it resides on a white screen teasing me with noises of logging in but i cannot see anything.
I'm really lost to be honest, i have no idea what to do and i am not good with terminology either (adw, flashboots, cm7 i have no idea what they are).
I know there are sooo many threads with different answer's so that is why i am starting a new thread.
Click to expand...
Click to collapse
Can you get to android market via your computer? If so go to it, log in, find a launcher and install to your phone. Once rebooted to the phone, it *should* give you a choice or just automatically choose the new launcher. What does double tapping your home button bring you too? I was able to find my alternative launcher by moving around via that.

sounds like ya have frozen system files
prolly be easyest to unlock bootloader and push a custom rom to it (they work better than stock anyway

Yes i did freeze the home app.
I really mean thanks to those replied. Unfortunately i have tried the first suggestion but it doesn't let me get to step 3 with the triangle, fast boot - android recovery - can't fast boot 2 etc can't get passed that.
i have just plugged it in the Laptop, taking sim out, and it has started! i thought it was broken!! but unfortunately not 'home' yet...
SO it is at the motoblur login screen, should i log in? press factory reset? Any suggestions?
I'm not sure how to push an app straight to phone so i can install a launcher...
we're nearly there guys!

In addition to what Robkort said a few posts up ^^^ to get into the recovery on 2.3.4 you may have to scroll down once you see fastboot, until you see "Android Recovery" and press vol up - when the android dude comes up, if tapping the bottom right corner doesnt get you into recovery, press BOTH volume buttons at the same time.

It is now up and working with me just simply plugging it in, running moto sync, logging in to market from laptop and sending the launcher app..
Wifi was enabled luckily before i froze home, so when i pressed log in it went 'error' then launcher pro just popped up so now i think i just unfreeze home, turn it off, put my sim in and fingers crossed..
wish me luck!

Yahooooooooooooooooooooooooooooooooooooooooooooooooooooooooo!
It's worrying how much happier i am now that i am back on top with my phone working. Pretty dependant we become!
All my widgets, and motoblur have gone, and some writing is in a different language :/ universal inbox is not there either.
Still Thanks for all the suggestions!
I suggest this thread should be 'FROZEN' or just stay open if anyone ever freezes 'home' without having another launcher installed.
I'm glad i didn't need to flash anything, put other ROMS on, hard reset losing everything, solved pretty simple luckily.

[HELP] My Note rebooted in to some wierd factory mode

Could anyone with knowledge tell me if it is safe to reboot my Galaxy Note when this image is shown?
(see relevant images in the attachements)
A small history to this incident:
While I was at work my Note had started the "in car"-app (don't know what it is called, but it is activaded by voice I think). Which I found a bit odd, but I closed it down. After a few minutes the app started by it self again and at which point I decided to reboot my phone as some software was obviously screwed up.
Said and done I rebooted but instead of getting the regular boot my phone instead entered Factory Mode with the message "Downloading... Do not turn of target!!"
This of course scares me a bit so I haven't had the gut to turn it off or reboot.
Is this something that can be fixed or do I have to return it for service?
/ tonii

toniimirrkare said:
Could anyone with knowledge tell me if it is safe to reboot my Galaxy Note when this image is shown?
(see relevant images in the attachements)
A small history to this incident:
While I was at work my Note had started the "in car"-app (don't know what it is called, but it is activaded by voice I think). Which I found a bit odd, but I closed it down. After a few minutes the app started by it self again and at which point I decided to reboot my phone as some software was obviously screwed up.
Said and done I rebooted but instead of getting the regular boot my phone instead entered Factory Mode with the message "Downloading... Do not turn of target!!"
This of course scares me a bit so I haven't had the gut to turn it off or reboot.
Is this something that can be fixed or do I have to return it for service?
/ tonii
Click to expand...
Click to collapse
Mate, that's just "Download Mode" used for downloading new firmwares on the phone, used in Samsung services as well.
You access that by pressing Volume Down (or up, not sure) + Home + Power. Just pull out the battery and try to reboot it again. It's nothing to worry about, you might have hit the buttons by mistake or if not just some weird Note act-up...

eug3n91 said:
Mate, that's just "Download Mode" used for downloading new firmwares on the phone, used in Samsung services as well.
You access that by pressing Volume Down (or up, not sure) + Home + Power. Just pull out the battery and try to reboot it again. It's nothing to worry about, you might have hit the buttons by mistake or if not just some weird Note act-up...
Click to expand...
Click to collapse
Exactly. Nothing to be worried about there unless it keeps happening without interaction from you then there be something going on.

toniimirrkare said:
Is this something that can be fixed or do I have to return it for service?
Click to expand...
Click to collapse
had a little chuckle at this

eug3n91 said:
Mate, that's just "Download Mode" used for downloading new firmwares on the phone, used in Samsung services as well.
You access that by pressing Volume Down (or up, not sure) + Home + Power. Just pull out the battery and try to reboot it again. It's nothing to worry about, you might have hit the buttons by mistake or if not just some weird Note act-up...
Click to expand...
Click to collapse
Oh. I feel a bit silly right now ^_^
Don't think I hit the "home"-button, but i'm starting to believe it's a bit messed up anyway since the "car"-app is starting by it self. it has happened a couple of times now. I'll wait and see if it happens again, and if so I'll try a factory reset.
Thanks for the quick reply!
/ tonii

toniimirrkare said:
Oh. I feel a bit silly right now ^_^
Don't think I hit the "home"-button, but i'm starting to believe it's a bit messed up anyway since the "car"-app is starting by it self. it has happened a couple of times now. I'll wait and see if it happens again, and if so I'll try a factory reset.
Thanks for the quick reply!
/ tonii
Click to expand...
Click to collapse
That's a bit weird with the car-app, although part of the beauty of Android for nerds like me is solving bugs like that A factory reset should do the trick.
And if you're feeling brave and have plenty of time on your hands, you should start reading about flashing other ROMs, there are a lot of users here and guides who will walk you through it and explain everything you need Once you get something custom on your note, stock firmware will seem utterly unworthy
Best of luck solving your problem

panyan said:
had a little chuckle at this
Click to expand...
Click to collapse
Heh, good for you
I'm not that experienced with Samsung, and by the text on the phone I thought it could be bricked if I rebooted

eug3n91 said:
That's a bit weird with the car-app, although part of the beauty of Android for nerds like me is solving bugs like that A factory reset should do the trick.
And if you're feeling brave and have plenty of time on your hands, you should start reading about flashing other ROMs, there are a lot of users here and guides who will walk you through it and explain everything you need Once you get something custom on your note, stock firmware will seem utterly unworthy
Best of luck solving your problem
Click to expand...
Click to collapse
Thank you!
I'll consider trying other roms when and if I get tired of the one Samsung provides!
Have just had it about two months, and coming from the HTC Wildfire this phone is a beast! ^_^

eug3n91 said:
That's a bit weird with the car-app, although part of the beauty of Android for nerds like me is solving bugs like that A factory reset should do the trick.
And if you're feeling brave and have plenty of time on your hands, you should start reading about flashing other ROMs, there are a lot of users here and guides who will walk you through it and explain everything you need Once you get something custom on your note, stock firmware will seem utterly unworthy
Best of luck solving your problem
Click to expand...
Click to collapse
:/ I had an issue similar to this with the car mode constantly opening up, and it was thinking it was charging when it wasn't, it wouldn't connect to the computer via usb, etc. Ended up being a bad USB port but Amazon shipped me a new one for free. Hopefully that's not the case for you, but if it starts to get worse... ( I had mine for only two and a half months)

toniimirrkare said:
Oh. I feel a bit silly right now ^_^
Don't think I hit the "home"-button, but i'm starting to believe it's a bit messed up anyway since the "car"-app is starting by it self. it has happened a couple of times now. I'll wait and see if it happens again, and if so I'll try a factory reset.
Thanks for the quick reply!
/ tonii
Click to expand...
Click to collapse
Don't fret just yet. Give it time so dat u strt undstanding ur fone
Remember these:
1) Press and hold Power button for about 10 secs to reset (its like a computer restart). Also called soft reset. U could do this when ur fone behaves unusually like hanging, draining too much batt, etc.
2) Vol up+Home+Power until u see the Samsung logo takes u to Recovery Mode. From here u may factory reset ur device. Also called hard reset. Do this when soft reset doesn't solve a small problem. Remember to make backups 1st.
3) Vol down+Home+Power brings u to Download mode. U may use this when u need to flash a ROM urslf (once u have read ample info abt it, be warned)
4) Two other ways to hard reset ur device:
a) Select Settings>Privacy>Factory data reset
b)From ur dialer, enter just key in *2767*3855#

StygiAn TrepidAtioN said:
Don't fret just yet. Give it time so dat u strt undstanding ur fone
Remember these:
1) Press and hold Power button for about 10 secs to reset (its like a computer restart). Also called soft reset. U could do this when ur fone behaves unusually like hanging, draining too much batt, etc.
2) Vol up+Home+Power until u see the Samsung logo takes u to Recovery Mode. From here u may factory reset ur device. Also called hard reset. Do this when soft reset doesn't solve a small problem. Remember to make backups 1st.
3) Vol down+Home+Power brings u to Download mode. U may use this when u need to flash a ROM urslf (once u have read ample info abt it, be warned)
4) Two other ways to hard reset ur device:
a) Select Settings>Privacy>Factory data reset
b)From ur dialer, enter just key in *2767*3855#
Click to expand...
Click to collapse
Many thanks for the tips!
Much appreciated

Tab 4 7" home button acts weird

So the home button on my Tab 4 7" started to act weird earlier today when I noticed it doesn't do what I set it to do in Nova. Pretty much nothing happened when I pressed it, except sometimes it would act kinda like the back button. Anyway, I uninstalled Nova but I didnt realise I had the stock launcher frozen (with Titanium) so I had to do a factory reset from the recovery screen.
Pretty much nothing changed, the home button doesnt do what it's supposed to (however it worked when I used it to access the recovery menu). Basically, when I press it, the leftmost "thing" on the screen is selected(?). Pics below.
Has anyone experienced this? What should I try to do?
i.imgur.com/v3XVuZ1.jpg
i.imgur.com/idWVa10.jpg

Anyone? :crying:

skullzhunter said:
So the home button on my Tab 4 7" started to act weird earlier today when I noticed it doesn't do what I set it to do in Nova. Pretty much nothing happened when I pressed it, except sometimes it would act kinda like the back button. Anyway, I uninstalled Nova but I didnt realise I had the stock launcher frozen (with Titanium) so I had to do a factory reset from the recovery screen.
Pretty much nothing changed, the home button doesnt do what it's supposed to (however it worked when I used it to access the recovery menu). Basically, when I press it, the leftmost "thing" on the screen is selected(?). Pics below.
Has anyone experienced this? What should I try to do?
i.imgur.com/v3XVuZ1.jpg
i.imgur.com/idWVa10.jpg
Click to expand...
Click to collapse
Looks like a hardware problem, i have that problem with my S4, was for a hit, and when I press "home" touch the screen somehow.

Try this
skullzhunter said:
So the home button on my Tab 4 7" started to act weird earlier today when I noticed it doesn't do what I set it to do in Nova. Pretty much nothing happened when I pressed it, except sometimes it would act kinda like the back button. Anyway, I uninstalled Nova but I didnt realise I had the stock launcher frozen (with Titanium) so I had to do a factory reset from the recovery screen.
Pretty much nothing changed, the home button doesnt do what it's supposed to (however it worked when I used it to access the recovery menu). Basically, when I press it, the leftmost "thing" on the screen is selected(?). Pics below.
Has anyone experienced this? What should I try to do?
i.imgur.com/v3XVuZ1.jpg
i.imgur.com/idWVa10.jpg
Click to expand...
Click to collapse
Try this
1.download virus guard and scan phone
2.do hard reset
3.instal custon mod
4.if all of this doesn't solve ypur problem then u have to take your device to service center.

N00b Here w/Question on Sprint LGV20 w/Dirty Santa Root (Stuck on Static!)

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!

"Unfortunately, system UI has stopped" - and that's just the start!!

Hi all,
Hope I might be able to get some advice. Excuse me up front if I butcher the jargon and/or description of the issue, I am but a simple (very, some might say) mobile phone user. I know nothing of the mystical world of 'rooting', and other Andriody black art.
So, here goes.
My wife owns a Samsung Galaxy S5 which hasn't been modified (except for the installation of a few extra apps) since the day it left the Vodafone shop. Today, for no apparent/obvious reason, the following is happening:
Switch phone on, boots into home screen when "Unfortunately, system UI has stopped” message is displayed. Click 'OK', messages disappears for approx 2 seconds and then comes back. Too short a time to do anything else with the phone.
After around a minute, the phone then reboots itself.
Once rebooted -> home screen -> "Unfortunately, system UI has stopped” -> repeat.
The only thing I could see happening, in between pressing the 'OK' button dozens of times, was some automatic App updates (Facebook Messenger and Facebook Pages Manager, were the two I saw).
The back of the phone is also getting pretty damned hot - related?
I've read a few 'Help me' pages online and managed to get the phone into Safe Mode thinking I could at least have a little look around while it was stabile. Wrong. The message and endless reboot cycles still occurred.
I'm loathed to do a full reset as I can't extract the photos from the phone - the phone won't stay 'up' long enough for me to copy them onto my laptop. The phone connects and is recognised but when it reboots itself Windows Explorer cracks it.
I know a lot people say "I didn't do anything", the only thing I've done to the phone prior to this issue was to remove the rear cover and re-seat the SD card (Sandisk Ultra 32Gb, if that's any use).
I really appreciate the time you hopefully take to read this and (hopefully) help out an old boy like me. Thanks heaps in advance.

simarjoshlib said:
Hi all,
Hope I might be able to get some advice. Excuse me up front if I butcher the jargon and/or description of the issue, I am but a simple (very, some might say) mobile phone user. I know nothing of the mystical world of 'rooting', and other Andriody black art.
So, here goes.
My wife owns a Samsung Galaxy S5 which hasn't been modified (except for the installation of a few extra apps) since the day it left the Vodafone shop. Today, for no apparent/obvious reason, the following is happening:
Switch phone on, boots into home screen when "Unfortunately, system UI has stopped” message is displayed. Click 'OK', messages disappears for approx 2 seconds and then comes back. Too short a time to do anything else with the phone.
After around a minute, the phone then reboots itself.
Once rebooted -> home screen -> "Unfortunately, system UI has stopped” -> repeat.
The only thing I could see happening, in between pressing the 'OK' button dozens of times, was some automatic App updates (Facebook Messenger and Facebook Pages Manager, were the two I saw).
The back of the phone is also getting pretty damned hot - related?
I've read a few 'Help me' pages online and managed to get the phone into Safe Mode thinking I could at least have a little look around while it was stabile. Wrong. The message and endless reboot cycles still occurred.
I'm loathed to do a full reset as I can't extract the photos from the phone - the phone won't stay 'up' long enough for me to copy them onto my laptop. The phone connects and is recognised but when it reboots itself Windows Explorer cracks it.
I know a lot people say "I didn't do anything", the only thing I've done to the phone prior to this issue was to remove the rear cover and re-seat the SD card (Sandisk Ultra 32Gb, if that's any use).
I really appreciate the time you hopefully take to read this and (hopefully) help out an old boy like me. Thanks heaps in advance.
Click to expand...
Click to collapse
sorry to hear about your luck mate, but im sure we can figure a way around this issue. The first thing id try is wiping the cache and dalvik cache. that can be done by turning the phone completely off (in your case, probably just pull the battery and put it back after a few seconds), then hold volume +, the home button and power. the phone should vibrate and when it does, continue holding the first two, but release the power button. then itll boot into factory recovery. You use the volume buttons to navigate the menu, and power to select. Go to wipe cache, confirm wipe and reboot

Hi, thanks for the reply. I've just followed your suggested action but unfortunately the phone is still doing exactly the same thing.

simarjoshlib said:
Hi, thanks for the reply. I've just followed your suggested action but unfortunately the phone is still doing exactly the same thing.
Click to expand...
Click to collapse
np. ok, so you should be able to connect the phone to your computer in recovery and mount it so you can get the pictures off. After youve grabbed everything you need from the phone, then nuke it with Odin and the correct tar.md5 file and see what s what at that point

I agree. You might as well root it at that point.

youdoofus said:
np. ok, so you should be able to connect the phone to your computer in recovery and mount it so you can get the pictures off. After youve grabbed everything you need from the phone, then nuke it with Odin and the correct tar.md5 file and see what s what at that point
Click to expand...
Click to collapse
Assume you mean the 'mount/system' option from the system menu (hold volume +, the home button and power)? If so, I select this option and it doesn't appear to do anything. It seems to accept the entry by confirming the action at the bottom of the screen. So, I select 'boot' (top option), the phone starts as usual and then begins the cycle of - error message -> reboot, etc, etc after approx 15-20 seconds.
Is there no way to access the internal physical memory of the phone (even by force) to access the data stored there? Thanks again.

simarjoshlib said:
Assume you mean the 'mount/system' option from the system menu (hold volume +, the home button and power)? If so, I select this option and it doesn't appear to do anything. It seems to accept the entry by confirming the action at the bottom of the screen. So, I select 'boot' (top option), the phone starts as usual and then begins the cycle of - error message -> reboot, etc, etc after approx 15-20 seconds.
Is there no way to access the internal physical memory of the phone (even by force) to access the data stored there? Thanks again.
Click to expand...
Click to collapse
wait, you can actually see this stuff on the screen to select from?