Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
ooMoo said:
Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
Click to expand...
Click to collapse
Download Phone INFO Samsung from Play and check the CSC.
But it might be you are rebooting into DL mode instead of shutting down the phone then starting it in DL mode. I usually remove the battery for a bit and hold the power button for a few secs to make sure the mainboard is completely discharged. Odin (& other methods) all have problems changing BL and Modem if you just do a reboot into DL.
You might want to take a look at Multiboot and Recovery for the possibility of having the ROM you want, rooted etc. AND still have a stock ROM you can choose to boot into for work purposes.
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
[PROBLEM] Rooted > Flashed to U Firmware > Soft Brick > Flashed back to Verizon FW
Hi, relatively new to this, so sorry in advance if I made some obvious mistakes, but my phone is now soft bricked and I can't find a solution.
1) I was on Nougat
2) Rooted with Odin to remove Verizon bloat
3) Didn't really change much, still had MMS issues etc
4) Did a the deep verizon debloat. Started getting an endless message 'IMS Service has stopped'
5) Decided to flash U Firmware to get a non-Verizon, unrooted starting point. Used HOME_CSC to keep data
6) Soft bricked phone (didn't finish install and was stuck on a boot menu with the message 'dm-verity verification failed' )
7) Flashed back to a previous version of Verizon firmware, again, HOME_CSC - (G935VVRS4APH1_CL8875708_QB10880117_REV02_user_low_ship_MULTI_CERT.zip). (Did this twice now, once with PrinceCosmy Odin)
8) Install went well, Verizon logo on boot.
9) Soft brick #2 - I'm being asked for a password to decrypt storage...I set no password for this. So I'm stuck.
Thanks in advance, any support is much appreciated!
The PH1 firmware is very old. You might have better luck flashing to QF2. Honestly, your best bet is to boot into recovery to do a factory reset, then start over completely. That will clear the decryption issue. Then look at the QF2 ROM in this forum.
CVertigo1 said:
The PH1 firmware is very old. You might have better luck flashing to QF2. Honestly, your best bet is to boot into recovery to do a factory reset, then start over completely. That will clear the decryption issue. Then look at the QF2 ROM in this forum.
Click to expand...
Click to collapse
Thanks! I was hoping to not have to reset, but have recently backed it won't be a big deal.
I have two other questions though
a) how do I know which firmware is QF2? (the device was originally on MM but through smart switch I upgraded to Nougat)
b) what's the process for the factory reset? I'm trying via the recovery menu and it isn't working (the MM 6.0.1/ G935UUES4AQC1 install)
Thanks
(UPDATE - OK so I went back to the U firmware, and from that boot menu selected 'Wipe Partition/Cache'. Also did a factory reset which looked like it failed. Still couldn't boot phone though. However I went back to the verizon firmware and there was no passcode prompt now. Phone is factory reset to 6.0.1.
Should I go to QF2 now?
How can I get to a non-verizon firmware?)
OK, I've solved everything I mentioned above by doing as suggested,
I think I had a partition of something somewhere that was no good.
1 - Factory Reset from boot menu (after wiping partition/cache)
2 - Flashed PH1
3 - Verizon bloatware reinstalled and was loading phone properly
4 - Did a factory reset from here via settings
5 - After factory reset, Flashed QC1 w/out HOME_CSC
6 - Now booting properly with a clean(ish), non-Verizon firmware.
I'm still interested in removing as much bloat as possible from Samsung, and am constantly being harassed notified that my Nougat update is downloaded and ready to install!
Hope that helps someone!
Hi ladies/gents,
I've just flashed my Samsung S5 (SM-G900F) with the latest UK BTU stock firmware from sammobile.com for my unlocked device (I've used SIM cards in the device in 3 different countries fine).
I reset the device into Boot mode, cleared the cache and factory reset, then boot the phone into download mode.
Using Odin I flashed the .tar.md5 file under the "AP" section of Odin with auto-reboot & F.Reset Time checked , the process was a success (according to Odin), and then when the phone restart: nothing but being stuck on the Samsung S5 boot flashing boot screen.
I've tried clearing the cache and factory resetting again, as well as installing the AP file again, to no joy.
I'm pretty dumbfounded by this as it seems this is the most straight forward and "safe" flashing to do on the device, yet now I seem to have bricked the phone in doing so.
Most of the advice I can find on the internet to fix the boot loop issue suggests doing the exact process I have just ran through, so I'm pretty close to calling it quits and looking at another brand of smartphone.
If anyone has any advice on how I can try and recovery the use of my phone, I'd be most grateful.
Thanks.
Okay guys/gals in the time it took me to feel sorry for myself and get desperate enough to create a post here the phone seems to have just turned on and working fine
I did restart the phone a bunch of times, but it seems just leaving it 20-30+ minutes does the trick.
Patience is a virtue!
Hi
I am having exactly the same issue with a G900I - tried everything!
Any advice??
So I have a SM-G950W (BMC (Bell) originally but using unlocked on RWS (Rogers)) . Nothing has ever been flashed before except for OTA updates.
I upgraded to the Oreo OTA update and my phone got stuck in a bootloop. Ive tried wiping Cache and Factory resetting and no dice.
I decided to flash the official firmware with odin. I downoaded BMC/RWC/XAC and have tried flashing each of those through the newest Odin (1.13.1). This always ends successfully.
On bootup I get to the Samsung logo and the LED blinks red and the phone reboots. This happens indefinitely.
Ive tried wiping factory and cache again after this and it did not help. If I flash the HOME_CSC instead of CSC It gives me an encryption error and wants me to factory reset, after that I get the same red led bootloop result.
Any ideas on what I can do/ Am I missing any steps?
EDIT: Unsure if this is related but in the recovery menu it says this at the bottom:
fail to open recovery_cause(No such file or directory)
Reboot Recovery Cause is [UNKNOWN]
No support SINGLE-SKU
File based OTA
Supported API: 3
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
[libfs_merger] Error fetching verity device number: no such device or address
[libfs_merger] Couldnt get verity device number!
[libfs_merger] Error removing device mapping: no such device or address
Successfully verified dmverity hash tree
Same issue with SM-G950U1
Hi Mike, I have the same issue that you are reporting and in the recovery menu, it says the same as yours at the bottom. I didn't find any solution for having the phone stop rebooting. Please, if you have found any solution share it. I'll do the same if I can get the phone out of the boot looping. What I have done so far is flash the phone with the last official firmware downloaded with SamFirm.
I'm not sure but the problem might be related to the firmware. I'm now downloading an older firmware (with android 7.0) to check if the phone starts ok with that firmware. I'll let you know if I have good news.
Regards!
EDITED:
I found a solution!!
Hey, just want to share how I stopped the bootlooping.
You will need to flash your phone following this post https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255 and download Firmware from Updato. Do not download the last version of the Firmware, because it will continue doing the bootloop. I've downloaded the following firmware:
Galaxy S8 / SM-G950U1 / 7.0 Nougat(Android ) / December 26, 17
And the phone has started!
Remember to use the last version of Odin from this post https://forum.xda-developers.com/showpost.php?p=75703449&postcount=276
If not you will not be able to flash your phone.
Hope you can fix the phone as I have done!
Let me know when you fix it.
Best!
Hey Mike,
You are not alone. Samsung apparently has messed up another OTA again. I have the same issue after Oreo update. Showed my phone to a certified Samsung repair shop and they said they had several people showing up that day with the same issue and they were not able to fix it. The best bet to contact Samsung Customer Support and they will assist you in sending your phone to a repair center.
I hope there was a faster way to fix the issue.
Hey Mike, I have updated my first answer with a workaround to fix the bootlooping. Let me know if it works in your case that I think was the same as mine.
Regards!
Hey Guys. Having the same exact issue for G955U1. I would to know if what gorito17 suggest fix the issue besides him.