Hi, the image attached shows a strange message that flashes on the screen for a millisecond when booting into recovery, is this normal?
SpeedMod (latest)
Cheers
So... 64 people viewed this and not one of you has seen it, or can recreate it.
Hmmm strange
Does that only happen in recovery?
Sent from my GT-I9000 using XDA App
does the phone work as normal ?? have you tried re flashing the rom or kernel that your running.
if its not making the phone act weird i wouldnt do anything about it,, may just be a bug.
azzledazzle said:
does the phone work as normal ?? have you tried re flashing the rom or kernel that your running.
if its not making the phone act weird i wouldnt do anything about it,, may just be a bug.
Click to expand...
Click to collapse
I was thinking that exact thought as well. If it ain't broke don't fix it.
Mind you that is a weird message. I know when I was playing in cm7 I would get the "kanged" message to indicate it's a test release. But that x.... Message is a real hum dinger
I alsi noticed you have the extra "GT-I9000" popup covering the samsung logo.
Sent from my GT-I9000 using XDA App
Last time I flashed bigmem speedmod I had a graphical blur where your message is displayed. Changed to non big mem and all was well. Happened booting into recovery and normal reboot.
Sorry for the lack of reply, didn't link for updates
The message appears on all reboots, it flashes up just before the standard Samsung Galaxy S screen appears
Yes the phone is working as normal, it just concerns me that 'something' is in there and if so, then my mind figures potential for virus?
Like other I flash and flash with little regards for just what could be in the data, I am trusting the originators a lot here, this is too easy for some 'insert your own obscenity' to place destructive code in there.
Thank you all for the replies, with such a specific name I hoped someone had come across the owner.
Maybe I left the phone out and some 'tard' graffiti tagged it LoL
icejagans said:
I was thinking that exact thought as well. If it ain't broke don't fix it.
Mind you that is a weird message. I know when I was playing in cm7 I would get the "kanged" message to indicate it's a test release. But that x.... Message is a real hum dinger
I alsi noticed you have the extra "GT-I9000" popup covering the samsung logo.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thats is down to timing, the 'name' appears so quick, by the time I hit the button, it was also displaying the next frame containing the normal logos
I'm not sure if you guys noticed it, but what you see on the screen is actually "GALAXY S" which wraps after the second A. It seems like you're having the normal "GALAXY S" message and a zoomed in version of it at the same time on the screen. The same goes for "GT-I9000" on the bottom.
Cheers
podumal said:
I'm not sure if you guys noticed it, but what you see on the screen is actually "GALAXY S" which wraps after the second A. It seems like you're having the normal "GALAXY S" message and a zoomed in version of it at the same time on the screen. The same goes for "GT-I9000" on the bottom.
Cheers
Click to expand...
Click to collapse
BOY do I feel a dumbass, I tried a few combinations of the letters, never thought about Galaxy
Cheers, that has set my mind at rest... for now...
Related
After re flashing, I must of messed something up because when it boots the screen goes fuzzy and blank, you have to press the home button a few times to get the home screen to show, none of the apps work or market place or browser.
I have tried about 4 different versions of the Gingerbread o.s My tab is a sprint, also when the battery icon shows when charging that goes all fuzzy.
Hope some body can help
Thanks
1deej said:
Hope some body can help
Thanks
Click to expand...
Click to collapse
Maybe if you explain yourself better...after re-flashing what??? does the tab go in download mode? did you come from a safe stock GB?? C'mon boy
1deej said:
After re flashing, I must of messed something up because when it boots the screen goes fuzzy and blank, you have to press the home button a few times to get the home screen to show, none of the apps work or market place or browser.
I have tried about 4 different versions of the Gingerbread o.s My tab is a sprint, also when the battery icon shows when charging that goes all fuzzy.
Hope some body can help
Thanks
Click to expand...
Click to collapse
Take another look at this section of forum. Now think, does it look absolutely anything like a section you should be posting a topic in???
Dev forum is for developments, not general discussion or questions and answers, They logically go in, err hmm let me think. "General" and "Q&A".
1deej said:
After re flashing, I must of messed something up because when it boots the screen goes fuzzy and blank, you have to press the home button a few times to get the home screen to show, none of the apps work or market place or browser.
I have tried about 4 different versions of the Gingerbread o.s My tab is a sprint, also when the battery icon shows when charging that goes all fuzzy.
Hope some body can help
Thanks
Click to expand...
Click to collapse
try flashing OS2 Warp, should solve the problem.
Sent from my SCH-I800 using xda premium
Just for any one else who gets stuck, this worked for me http://forum.xda-developers.com/showpost.php?p=17817293&postcount=3
make sure you set re-partition I think this is the but I messed up before I re-partitioned it with a bad rom
Thanks
Sorry for not explaining better, To be honest I wasn't sure what I did to mess it up I was trying all sorts to make it wifi only from sprint!
Thanks
Hi guys. My SGN is permanently freezing while booting. Suddenly the red lines appear and phone is stucked. It stucks on boot logo, or boot animation, or after successfull boot into system. It looks like this:
http://dl.dropbox.com/u/61718936/IMAG0003.jpg
Phone becomes quite hot on the back near camera.
I bought phone with stock 2.3.6. It was running for about 2 hours and i made OTA update to 4.0.4. It started to reboot itself while i was using it. So thought, i might use custom ROM to get rid of this freezes and reboots. But no change. Even on 4.2.1. I reverted back to 2.3.6. I noticed, that these red lines changes and moves (or even whole screen becomes red) while i'm twisting or pressing phone on various places. So i think, there is cold solder joint somewhere on motherboard. Maybe on graphic chip, because i didn't notice this problem while in recovery or download mode.
Can anybody help me with this problem, or point me on right place to look at on motherboard? Thanks in advance.
Seems to be defective device. Check with service center.
Sent from my GT-N7000 using xda premium
If you're able to, run this app to check for errors, I take it you have root. If it crashes mid scan, you've got problems with your emmc.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
Sent from my GT-N7000 using xda premium
Frozen Note
I hope you will find a solution for your problem.
But I have to admit I had to smile ("grinsen" in German is a much better word for it) when I saw your title:
Freezing even when >30°C
i'm not able to run device anymore but i already tried this app for checking emmc and this is the one with that bug. But it doesn't matter, because i was flashing only safe kernels, and i don't think this emmc is problem. I think the culprit is graphic chip, or CPU, or CfRF (Chip for Random Freezes)
I was not able to find any similar problem. Tomorrow, i will try to put device into download mode, flash any custom safe kernel with CWM, leave device in this recovery, and see if it freezes again. If yes, the only option is to get device warmer for a few degrees (300-350°C with my heat station haha ) and i will see if there was any cold solder joint. If not, device will be dead anyway so i have nothing to lose
ThaiDai: you mean grin?
Tuxxperia said:
i'm not able to run device anymore but i already tried this app for checking emmc and this is the one with that bug. But it doesn't matter, because i was flashing only safe kernels, and i don't think this emmc is problem. I think the culprit is graphic chip, or CPU, or CfRF (Chip for Random Freezes)
I was not able to find any similar problem. Tomorrow, i will try to put device into download mode, flash any custom safe kernel with CWM, leave device in this recovery, and see if it freezes again. If yes, the only option is to get device warmer for a few degrees (300-350°C with my heat station haha ) and i will see if there was any cold solder joint. If not, device will be dead anyway so i have nothing to lose
ThaiDai: you mean grin?
Click to expand...
Click to collapse
Hope you find the answer dude, let us know what the outcome is.
Sent from my GT-N7000 using xda premium
Have the same problem with CM9/10 and PA ROM, freeze and getting hot...
The best ROM closest to stable for me is the RocketROM_ICS_XXLPY_v1
I got reboot problem but it is useable with this ROM
I Cant even install a Stock ROM (GB/ICS)... Stuck in Samsung LOGO, or Force Close in many apps...
diasdroid said:
Have the same problem with CM9/10 and PA ROM, freeze and getting hot...
The best ROM closest to stable for me is the RocketROM_ICS_XXLPY_v1
I got reboot problem but it is useable with this ROM
I Cant even install a Stock ROM (GB/ICS)... Stuck in Samsung LOGO, or Force Close in many apps...
Click to expand...
Click to collapse
Have you repartitioned?
Sent from my GT-N7000 using xda premium
guys i've made a small progress. I put a pressure on back side of the phone near camera, and i turned the phone on. It successfully booted to system. When i stopped pushing phones back, red lines appeared immediately and phone freezed. When i start to twist phone in hands, lines were getting bigger or smaller. When i pressed the back cover again, lines disappear (but phone was still frozen).
So now my task is, to find out, which chip is badly soldered.
ThaiDai said:
I hope you will find a solution for your problem.
But I have to admit I had to smile ("grinsen" in German is a much better word for it) when I saw your title:
Freezing even when >30°C
Click to expand...
Click to collapse
Lol perfect device for overclocking....
Sent from my GT-N7000 using Tapatalk 2
warfareonly said:
Lol perfect device for overclocking....
Click to expand...
Click to collapse
few months ago i had Samsung Omnia i900 only working in fridge or when it was freezed with frost spray
this phone is mystery. When the battery is fully charged, it works like a charm. I can twist the phone as much i want, it won't freeze. I don't understand.
My n7000 has also this same problam pl. any one help me..
Tuxxperia said:
this phone is mystery. When the battery is fully charged, it works like a charm. I can twist the phone as much i want, it won't freeze. I don't understand.
Click to expand...
Click to collapse
My galaxy note n7000 has same problem from last 3 days i also not found any solution for this when i use phone without scrow fited on back cover my phone working fine only in 1 % of battey but when i tite scrow in back cover my phone frize at galaxy boot logo or samsung logo with or without red line...pl. any one help me... pl....
You guys started having strange issues with ur notes. Maybe its something like a self destruct programmed on your phones so that after a year or two people will switch their phones. Besides the bigger the phones are getting the more issues they are having.
A phone should be like a device that shouod work flawless, in case of emergency one is needing to make a call and found that the phone freezed.
Sometimes i blame everything to android. Despite years of open development. Its yet not stabilizing, i guess because of it being open source vendors are putting crap in it making it more vulnerable to issues.
I dont rely on android rather i use a cheap phone for calls and text or iphone. Its just good for internet, ebooks, movies, music and camera.
Sent from my GT-N7000 using xda app-developers app
Try pulling out the battery and then let the phone dry like a pair of wet socks. Clean the contacts and fit any loose thing that there may be.
Check your cable, if is loose or not, this way you could find if there were any unwanted sparks applied on the device.
Notice how it gets hot when is plugged in and you're using it? the battery reaches quickly 55 degrees which is not optimum, wait to cool to below this temperature.
My condolences in this sad event. Take care.
I've recently come across a new issue on my T-mobile Galaxy Note 4 that I haven't seen before. I've been searching online as well and can't seem to find anyone else posting about this problem either. I'm not the best but I have some experience. I've recently rooted and flashed tekxodus hybrid n4 5 1 1 rom on my note 4 through TWRP recovery. It took a few tries but everything worked. After using it for 3 days, I decided to turn it off and hard reboot it which I've done plenty of times before. But this time, upon rebooting it starts up and shows the tmobile logo screen and turns black. Vibrates twice as if you plugged it into the charger but remains black, and stays that way. If i plug it into the charger it shows the green battery screen and charges normally. I can enter twrp recovery and download mode as well. But it just can't get past the logo screen. I've also tried using a different note 4 battery from other videos, clearing the cache, delvik-cache, but nothing seems to work. As earlier mentioned, I can't seem to find any other post with this exact problem so I've come to reddit for help. Thank you in advance for any feedback.
You try flashing backup/ Odin stock?
yah its weird when u reboot through the menu. Just take out battery for like 10 seconds and put it back in
Sent from my SM-N910T3 using Tapatalk
Bruce lee roy said:
You try flashing backup/ Odin stock?
Click to expand...
Click to collapse
Yeah, unfortunately that's what I had to do. I was trying to figure any other option other than having to reflash everything. Thanks for the tip though
ayeitschris said:
yah its weird when u reboot through the menu. Just take out battery for like 10 seconds and put it back in
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Yeah, I knew since I could still get into TWRP Recovery and download mode I'd still be able to reflash stock roms. After I did, I did notice that the first "T-Mobile" logo screen lasted a bit longer than it did while it was messed up. I'm still not entirely sure what went wrong, but my only guess is that Tekxodus roms incorporate a app called synapse(possibly rom specific). I think I changed options in it which allowed me to overclock the cpu. I did reboot it a number of times after I set that up, but maybe something was stepped on through game editing apps which create/change app data. But it definitely pays to have back-ups to everything. Thanks for the reply too btw
Try flashing another kernel, sounds like that could be the culprit
JonakaJon said:
Yeah, I knew since I could still get into TWRP Recovery and download mode I'd still be able to reflash stock roms. After I did, I did notice that the first "T-Mobile" logo screen lasted a bit longer than it did while it was messed up. I'm still not entirely sure what went wrong, but my only guess is that Tekxodus roms incorporate a app called synapse(possibly rom specific). I think I changed options in it which allowed me to overclock the cpu. I did reboot it a number of times after I set that up, but maybe something was stepped on through game editing apps which create/change app data. But it definitely pays to have back-ups to everything. Thanks for the reply too btw
Click to expand...
Click to collapse
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
You can stop there! It's the new bootloader. You can roll it back an older one to fix it.
Does the logcat look suspicious? Or is this just a know thing? Thanks for the reply! I could use all the help!
Sent from my Nexus 6 using XDA-Developers mobile app
H4X0R46 said:
Does the logcat look suspicious? Or is this just a know thing? Thanks for the reply! I could use all the help!
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Didn't look at your log. Known issue
DR3W5K1 said:
Didn't look at your log. Known issue
Click to expand...
Click to collapse
Thanks! Seems like it does it with the MOB30I bootloader and the N preview bootloader, strange.
H4X0R46 said:
Thanks! Seems like it does it with the MOB30I bootloader and the N preview bootloader, strange.
Click to expand...
Click to collapse
Try the one before those two
H4X0R46 said:
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
Click to expand...
Click to collapse
Im gonna be honest. You shot yourself in the foot. Any dev that looks at that logcat will not help you due to you having and using lucky patcher. That app will make sure that devs hate you. Sorry man but that is the way it is. Also might want to keep in mind that developers are adding in code that causes issues if it detects things like lucky patcher. Bewteen that and that malware ridden app of ES file manager and your issues could be many.
I will say this. There are tons of system errors all over that log. Might want to start from the ground up and knock out the system errors.
H4X0R46 said:
So I posted about a strange issue with my device lately, when I shut it off, I can't turn it back on right away, I have to wait like, 20 seconds or so before it will show the "Google" splash screen again and boot. My thoughts were that maybe it is just shutting off the screen before the rest of the device ACTUALLY powers off, I messaged someone here on the forums and he told me that very well could be it. I have a logcat here of me powering off the device, is there anything here that seems off or not right? When it comes to logcats, I have no idea what any of this means lol Thanks in advance to anyone who can decipher this logcat.
http://pastebin.com/rDkb6TbQ
Click to expand...
Click to collapse
DR3W5K1 said:
You can stop there! It's the new bootloader. You can roll it back an older one to fix it.
Click to expand...
Click to collapse
Which bootloader? I am running the latest bootloader from the N preview 3 firmware and when I power off my device, about 2 seconds after the screen goes black, I can then press the power button and it comes on just fine real quick. This is the bootloader that makes the "Google" logo bold. No problems here at all.
And out of curiosity, may I ask why you need to power off the device, and then turn it back on immediately? Why not just reboot your device if your on a custom firmware.
zelendel said:
Im gonna be honest. You shot yourself in the foot. Any dev that looks at that logcat will not help you due to you having and using lucky patcher. That app will make sure that devs hate you. Sorry man but that is the way it is. Also might want to keep in mind that developers are adding in code that causes issues if it detects things like lucky patcher. Bewteen that and that malware ridden app of ES file manager and your issues could be many.
I will say this. There are tons of system errors all over that log. Might want to start from the ground up and knock out the system errors.
Click to expand...
Click to collapse
So lucky patcher can cause issues, and es file manager is bad as well? Never knew. I saw that there were lots of errors in my logcat, but not experienced enough to figure out what they mean. Would you advise not using either of these apps then? And with this many issues in the logcat, is that the entire problem? Thanks.
EDIT: I should also add that I'm running the N preview.
christianpeso said:
Which bootloader? I am running the latest bootloader from the N preview 3 firmware and when I power off my device, about 2 seconds after the screen goes black, I can then press the power button and it comes on just fine real quick. This is the bootloader that makes the "Google" logo bold. No problems here at all.
And out of curiosity, may I ask why you need to power off the device, and then turn it back on immediately? Why not just reboot your device if your on a custom firmware.
Click to expand...
Click to collapse
Currently using Android N and the bootloader that comes with it, the one that makes "Google" show in bold. And reasoning would be to either boot into my bootloader and recovery, or to switch to another ROM. (I use multirom)
Another EDIT: I flashed MOB30I and formatted my userdata, clean start. I'm gonna keep an eye on my logcats and see what happens, so far, no errors like you saw in the posted logcat. Thanks Zelendel for mentioning all the errors caused by Lucky Patcher and ES File Manager.
H4X0R46 said:
Currently using Android N and the bootloader that comes with it, the one that makes "Google" show in bold. And reasoning would be to either boot into my bootloader and recovery, or to switch to another ROM. (I use multirom)
Another EDIT: I flashed MOB30I and formatted my userdata, clean start. I'm gonna keep an eye on my logcats and see what happens, so far, no errors like you saw in the posted logcat. Thanks Zelendel for mentioning all the errors caused by Lucky Patcher and ES File Manager.
Click to expand...
Click to collapse
No prob. Sorry for the late reply. Just got off of work. Yes lucky patcher is not only hated but worked against. It is one of the main apps that the Privacy Guard commits were made for. Others have code that won't boot the rom if it gets installed.
Es file explorer has gone to heck. Also avoid anything by the Cheetah company. Same issues.
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
sinajei said:
Hi there!
I was wondering if anyone around here had some ideas on what to do.
My LG G4 had been working fine until today. I unlocked the screen to check my e-mail and it completely froze. It was plugged in at the time, so I unplugged it to see if I could restart it. The charging light was still blinking, the power button didn't respond, absolutely nothing.
I took the battery out, left it for a minute or so and rebooted. It loaded, unlocked, but I could only get to the app menu before it completely froze again. Afterwards, screen went black.
On the third try, it booted up to the LG logo and that's it. It popped up about 3 times and screen went black. No other response whatsoever. I can only try to reboot again only after taking out the battery, but it does the same thing.
I switched the battery with another one of the same model, nothing changed. Computer doesn't recognize it either.
I've looked around for a bit and I can't find anything like my case. The closest thing described is the boot loop. I'm not exactly sure that's my case, but it seems similar to a certain degree.
I got it to boot to recovery mode, but it doesn't do anything. It asks me if I'm sure I want to run it, and in the second 'yes' it freezes up completely again. Screen goes black and does absolutely nothing else.
Added note, phone upgraded to 6.0 yesterday morning. I had no issues with it until now. No app updates were running at freezing time.
I'm considering taking it to the store before I try anything myself, just in case there is still some warranty active.... But any ideas would be greatly appreciated.
Click to expand...
Click to collapse
seems like infamous bootloop... harware issue. send it to tmobile or LG.
raptorddd said:
seems like infamous bootloop... harware issue. send it to tmobile or LG.
Click to expand...
Click to collapse
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
sinajei said:
I was afraid so... Went directly to the T-Mobile store where I bought it and, since the warranty was still active, they exchanged it on the spot.
I just hope this one lasts longer than the other one did...
Thanks!
Click to expand...
Click to collapse
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
raptorddd said:
yeah.. did you know manufacture date on the one affected by bootloop or first 3 serial number.?
Click to expand...
Click to collapse
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
sinajei said:
Yup. Actually still have the box.... the date was 05/2015.
New one's date is 03/2016.
Click to expand...
Click to collapse
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
raptorddd said:
it was a 505.. most will bootloop... new one is. 603. theres hw 1,0 and 1.1.. this you look at software info ... in hidden menu.. in dialer..
Click to expand...
Click to collapse
This one (603) is a HW Version 1.0 ...
sinajei said:
This one (603) is a HW Version 1.0 ...
Click to expand...
Click to collapse
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
raptorddd said:
mines its 601 and same HW 1.0 if they knew they revised 1.0 to 1.1 why not use the 1.1 if they knew this back in october 2015.. theres older phone from 2015 with HW 1.1
Click to expand...
Click to collapse
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
sinajei said:
That is an excellent question...
Btw, does your screen freeze up sometimes? 'Cause mine sometimes goes unresponsive right after I unlock it... I just lock and unlock it again and keeps working just fine, but it's kind of annoying... old one did it and it, now this one does it sometimes too...
Click to expand...
Click to collapse
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
raptorddd said:
yes it does.. but very rare... not to often... but mines does using phone and it freezes then turn off screen and when back it all works... i used power button.. not sure why but it does..but liek i said not to often. its once in a while..
Click to expand...
Click to collapse
Good to know it's not just me then. Guess it's a common screen glitch then.
Thank you for the info!
Well another 505 g4 bites the dust. Playing a game, backed out of it, phone froze, pulled battery, turned on to endless bootloop, pulled battery again, now nothing and I mean nothing, no boot loop, no nothing
Definitely a brick. Computer doesn't recognize or even try to charge it. Hopefully still under warranty.
Sent from my LG-VS980 using Tapatalk