Database Users

[Q] [q] lg l3 e405 start-up problem

Hi everyone, I'm new here. I have a problem with my LG L3 E405. Last night, I dropped my phone from the second floor of my house. When I reinserted the battery and restarted the phone, a error screen came up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
....Then I could not use my phone anymore. I searched on forum for my problem. Luckily, I found a post about "UNBRICK YOUR LG OPTIMUS L3 E405". I followed the instructions and my phone worked after that. However, when I restart the phone, the error screen
comes up again. Please help............:crying::crying::crying:

Just to be sure, and not, god forbid, to insult you, when you performed the unbricking procedure, you were familiar with the fact that unbricking is not unbreaking?
I'm asking since I myself wasn't aware of the definition of brick / soft-brick / hard-brick until recently, and until I learned about these, whenever I heard "brick" I thought the meaning was "break".
If you were familiar, will you please explain when the phone worked during the unbricking procedure?
Is it really worked regularly until you restarted it?

need4steer said:
Just to be sure, and not, god forbid, to insult you, when you performed the unbricking procedure, you were familiar with the fact that unbricking is not unbreaking?
I'm asking since I myself wasn't aware of the definition of brick / soft-brick / hard-brick until recently, and until I learned about these, whenever I heard "brick" I thought the meaning was "break".
If you were familiar, will you please explain when the phone worked during the unbricking procedure?
Is it really worked regularly until you restarted it?
Click to expand...
Click to collapse
Yes, my phone worked normally until I restarted it. Only when I restart the phone, the srceen message that I mentioned above will appear. . I look forward to your help.

I'll be glad if I'll manage to help you out.
Please explain in detail the procedure of the unbricking, and elaborate in detail what happened to your phone in the appropriate steps of it.

Here is hoanganspk comment:
hoanganspk said:
Sorry for border you. Because I'm a new member in this forum, I cannot post threat with outside link.
I carefully followed this instruction to unbrick my phone.
http://krazeefly.blogspot.com/2012/09/how-to-unbrick-your-android-phone.html
a
Then, my phone worked well until I restarted. Hope to hear your rely
Click to expand...
Click to collapse
@hoanganspk: You''re not bothering me at all. I hope I'll be able to help you out.
Did you try to enter emergency mode and then flashing your firmware?
If not, please do so - power off your phone, clicking volume up + volume down + power button simultaneously, entering "emergency mode" and only then connecting your phone to your PC.
If you did so, please explain what happened after you received the "FINISHED" status in Software update [KDZ]?
Did your phone was able to enter your stock firmware after all the restarts that Software update [KDZ] did during the flash procedure?
If so, you can root you phone, install CWM, try booting into CWM within the app, when you're already inside you stock ROM, and before you're restarting yourself, and then trying wiping data/factory reset, formatting /system, wiping Dalvik Cache, and then retrying flashing the stock firmware in emergency mode.
I hope I was clear enough.
The most important thing for me to know is if you flashed your stock ROM inside emergency mode, and not, as written in the link you provided, in your OS. BTW, the phone mode setting should be DIAG and not some other setting.
Anyway, I look forward for your reply.
Feel free to ask guidance to any step of the procedure I posted above.

need4steer said:
Here is hoanganspk comment:
@hoanganspk: You''re not bothering me at all. I hope I'll be able to help you out.
Did you try to enter emergency mode and then flashing your firmware?
If not, please do so - power off your phone, clicking volume up + volume down + power button simultaneously, entering "emergency mode" and only then connecting your phone to your PC.
If you did so, please explain what happened after you received the "FINISHED" status in Software update [KDZ]?
Did your phone was able to enter your stock firmware after all the restarts that Software update [KDZ] did during the flash procedure?
If so, you can root you phone, install CWM, try booting into CWM within the app, when you're already inside you stock ROM, and before you're restarting yourself, and then trying wiping data/factory reset, formatting /system, wiping Dalvik Cache, and then retrying flashing the stock firmware in emergency mode.
I hope I was clear enough.
The most important thing for me to know is if you flashed your stock ROM inside emergency mode, and not, as written in the link you provided, in your OS. BTW, the phone mode setting should be DIAG and not some other setting.
Anyway, I look forward for your reply.
Feel free to ask guidance to any step of the procedure I posted above.
Click to expand...
Click to collapse
Hey guy. T tried to unbrick my phone with your instruction again and again then my phone have worked. Million thanks for your help :good::good::good:

Thanks a lot for your confirmation.
BTW, you did it the exact same way again and again, and after a few times of it, it just worked?
If you changed something, please explain so others, including me, will know for the sake of solving this kind of a problem.

[Q] Need Help restoring Nexus 10!!

Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I finally figured out the problem... I had to completely flah the stock image from fastboot, but my drivers were not up-to-date... so I guess it was kinda my own fault... sorry.... but let it be a cautionary tale for everyone, DRIVERS DO MATTER!!

Mancini_Rafael said:
Hello everybody, this is my first post and I'm kind od a noob on this whole thing, so bare with me here...
Here's the thing, I have a Nexus 10 (my baby), and like a lot of people i was very excited to the update for the infamous 4.4 KitKat.
Yesterday the update downloaded itself automatically and I installed it. So far so good, right?
Wrong! Cause now my nexus won't work. I personally think that the OS got corrupted on the process of update, and now i can't turn it on.
When i try to turn it on normally (power button only), nothing happens.
I can however enter in download mode and on that other mode that shows the options (image below). I can't however enter on recovery mode, when i try to, it only goes dark, as if it doesn't exist (that's where im getting the whole "corrupted OS" idea).
To make matter worse, I'm pretty sure that the option Usb debugging, was turned off before all this happened, and i think that's the reason why the next step didn't work either.
I tried unlocking the bootloader again (even tough it already appears as unlocked) and also tried to flash the stock recovery that i download from the developers page of google itself, but when i try to do it, it show that my device is not connected (actually it says "waiting for device").
I also tried flashing it trough odin3.07 but it also won't work, that's cause when it seems that the process will start, Odin crashes, and i dont know why (skyes wasnt the reason cause I dont even have it on my pc).
Anyway, that's my problem. I really hope someone can shed some light on me and help me. Thanks
View attachment 2410610
View attachment 2410611
View attachment 2410612
View attachment 2410613
Click to expand...
Click to collapse
Pm'ed you.
Sent from my Galaxy Nexus using XDA Premium HD app

I like wugfresh's Nexus Root Toolkit.

I had the same problem.
As suggested above, get the wugfresh nexus root toolkit. That has the option of flashing a stock rom from a soft-bricked device so long as you can get to the bootloader (which is where you are).

I had the same issue - I'm wondering how many others are getting this too. I'm in no way conversant with this kind of technical challenge so I had a few hours of stress thinking my tablet was knackered.
I tried mskips and wug's toolkits on my bootcamp partition in but couldnt get them to work. I tried following the manual fastboot recovery then ADB sideloading the image but that kept failing too.
In the end, I use the mac toolkits (here: http://forum.xda-developers.com/showthread.php?t=2063042) to get back to android 4.2, then let the device receive OTAs. The 4.4 OTA installed fine this way around.

Errors while trying to update LG-E612

So I got this phone off a friend and I factory reset it which all worked fine, then I thought I would update it before I got to far. I have not had any success, I have even scoured the forums and the internet without any success so I'm hoping that someone with some experience may be able to assist or point out something I am missing. The phone is stuck in Download mode - I can't get it to boot to the rom at all.
I have a feeling there may be corruption on the phone - You'll see why a little further down, however I cannot be sure.
I am stuck in Download Mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried every method to get the update to work that I can find.
I started off by installing all the LG apps and Drivers. The phone is recognised from what I can tell.
I downloaded a couple of stock roms
When I open LG Mobile Support Tool - It says the software is up to date. When I go to 'Options' the only option I get is 'Update Recovery' which I chose and let it download and start installing. Once it gets to 4% is stops. I have pulled the battery and tried over and over again but it keeps stopping the update at 4%. I have even tried removing the battery completely and continuing the install but the same thing happens.
So I tried this over and over with no success. I tried with battery, without battery, I tried getting in Emergency Mode with no success. I tried booting into the OS with no success. So I continued surfing looking for answers.
I found KDZ and thought this might be the missing piece of the puzzle, however this kept crashing every time I tried loading info from the phone and even when I skipped that and just tried installing the ROM.
And the data in the log file looks out of place...
I played around with this hoping to get it to work, but I couldn't. I tried CDMA and it kept failing and it wouldn't even attempt to install the ROM.
So the next one I gave a shot was LG Flash Tool 2014.
This is the only info I can get to pull from the phone.
I am out of options and I'd really like to get this sorted without having to send it off for repair. I see there is an IMEI error - Does anyone know a way for me to repair it?
Any suggestions or experiences you can share that may help would be really great.

Jack_Bauer_AUS said:
So I got this phone off a friend and I factory reset it which all worked fine, then I thought I would update it before I got to far. I have not had any success, I have even scoured the forums and the internet without any success so I'm hoping that someone with some experience may be able to assist or point out something I am missing. The phone is stuck in Download mode - I can't get it to boot to the rom at all.
I have a feeling there may be corruption on the phone - You'll see why a little further down, however I cannot be sure.
I am stuck in Download Mode
I have tried every method to get the update to work that I can find.
I started off by installing all the LG apps and Drivers. The phone is recognised from what I can tell.
I downloaded a couple of stock roms
When I open LG Mobile Support Tool - It says the software is up to date. When I go to 'Options' the only option I get is 'Update Recovery' which I chose and let it download and start installing. Once it gets to 4% is stops. I have pulled the battery and tried over and over again but it keeps stopping the update at 4%. I have even tried removing the battery completely and continuing the install but the same thing happens.
So I tried this over and over with no success. I tried with battery, without battery, I tried getting in Emergency Mode with no success. I tried booting into the OS with no success. So I continued surfing looking for answers.
I found KDZ and thought this might be the missing piece of the puzzle, however this kept crashing every time I tried loading info from the phone and even when I skipped that and just tried installing the ROM.
And the data in the log file looks out of place...
I played around with this hoping to get it to work, but I couldn't. I tried CDMA and it kept failing and it wouldn't even attempt to install the ROM.
So the next one I gave a shot was LG Flash Tool 2014.
This is the only info I can get to pull from the phone.
I am out of options and I'd really like to get this sorted without having to send it off for repair. I see there is an IMEI error - Does anyone know a way for me to repair it?
Any suggestions or experiences you can share that may help would be really great.
Click to expand...
Click to collapse
I haven't viewed the images, but try this
-Goto download mode.
-Open KDZ updater
-Select the kdz, select 3QCT (something like that) and DIAG (forgot the options, its been long since I flashed a stock ROM)
-Flash the kdz
-KDZ updater will crash, it is quite normal
-Do a hard reset (remove battery, put it back, vol - + power + home, when it vibrates remove power and hold on vol - and home for another 5 sec)
-Hopefully, it should boot..
Sent from my Moto G XT1033 using Tapatalk

Make sure you have drivers installed BEFORE conecting the phone.
Also the only flasher that worked for me is this: http://forum.xda-developers.com/showthread.php?t=2409308

Tmobile samsung galaxy s7 upload mode

My tmobile galaxy s7 got stuck on something like bbl error and in the center of the screen the android logo and the sbl error and upload mode nothing else not able to get on download mode or recovery mode totally stuck need help odin not able to flash anything none of the latest firmware nothing,..
Ehat i did was i flash with odin a verizon firmware or something like fof6 combo firmware with the latest tmobile firmware found on androidfilehost.
My phone is now bricked or what i call softbricked i need any kind of help on how to flash or a tool to forcely flash something to unbrick and be able to restore stock firmware any nice developer please help i still paying this s7 and i really want to revive my phone any help will be greatly appreciated?

I'm no expert by any means, just a dude that was in the same position a few weeks ago.
First you'll want to get ODIN, which is your flashing tool:
http://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
Next you need to find the stock firmware. Lots of sites will have it but 99% of them use some kind of bandwidth throttling crap. The firmware is 4.5gb uncompressed and about 2gb compressed. So if you can find someone hosting the firmware on their Google Drive that's your fastest bet, otherwise it'll take hours or days to download.
The latest firmware at the time of this post is G935TUVU4APIA. You don't necessarily need the latest, you just need to get your phone restored. If there is newer firmware available than what you flash to your phone, when your phone successfully boots you'll get an update to the latest.
Wish I could find a direct link for you but it seems these will always be moving around. That being said search for TMB-G935TUVU4APIA-20160927113301.zip. That was the file I downloaded and it contained the 5 files listed below, which you should extract to your preferred location on your PC:
AP_G935TUVU3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5
BL_G935TUVU3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVU3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_TMB_G935TTMB3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMB3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5 (optional)
The first 4 of the 5 listed above are the important ones. The 5th file, "HOME_CSC...", from what I understand preserves your data should you need to flash over a working phone, but we'll ignore that file for this task. Note the "AP", "BL", "CP", etc., at the beginning of each filename - more on that shortly.
Finally, the home stretch.
* Power off your phone completely. If you're boot looping hold VOL DOWN and POWER.
* Boot into recovery mode by pressing and holding VOL DOWN, HOME and POWER at the same time. Release when you see recovery mode warning.
* Connect your phone to your PC.
* Open ODIN and make sure the phone is recognized. It will show up under ID:COM and have some assigned COM port like 9 or 10.
* Click on the BL button and select the BL_G935TUVU3APG1_CL8439036_QB10213096_REV02_user_low_ship_MULTI_CERT.tar.md5 file from your extracted firmware package.
* Repeat this process for AP, CP, and CSC files.
* Once all files are selected click START.
After some time your phone will be flashed with the stock firmware and everything should be back to the way it was when you purchased it. Hope that helps!
---------- Post added at 11:26 PM ---------- Previous post was at 11:20 PM ----------
Sorry man, I can't read! Missed the part where you said you already tried ODIN.
You may want to do a factory reset first before flashing. I think you hold VOL UP, HOME and POWER to get there. Follow the steps to do a factory reset. Then try ODIN again with stock T-Mobile firmware.

tmobile s7 upload mode
the problem here is when I press vol up or vol down it goes straight to this
sbl error upload mode
and Odin detects as download mode but cant not flash anything I do have the latest firmware.
I will attach the picture of the actual error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

https://imageshack.com/i/pnI8ZKLZj

tmobile s7 upload mode
this was the file I flashed before this happens
found it on android filehost under the search of G930T
https://www.androidfilehost.com/?fid=529152257862666887
it may give some directions thanks

Sorry my friend, wish I could help here. It looks like your bootloader is jacked. Did you mean "sbl" instead "bbl" error? I think that's the secondary bootloader. And from the file you linked it appears you flashed the Galaxy S7 "flat" (G930T) firmware onto your Galaxy S7 Edge (G935T). Never thought that would be a brickable operation but apparently so. Unless someone's dealt with this before your only option may be to return the phone and see if they can either reflash it with some other proprietary tool or exchange it. I don't know how to push the stock boot.bin and sbl.bin onto these phones but maybe someone here does.

tmobile s7 upload mode
yes sir is a flat version of the s7
and what you are saying is correct.
well I will sit and wait for something to come up wit a light thanks...

well I think I fried thos device just gonna sit and wait for a developer to find some source of code to reboot this thing

does anyone knows how to fix this problem " SBL error upload mode " ? please........... thanks

SM-G906S Soft Bricked with Boot Loops & Re-activation lock on.....PLEASE HELP!!!

Please bare with me as this is a little bit long because I think I need to tell you everything up to now I have done to recover my phone so you can give me the most accurate advice to fix it.
I have a Galaxy S5 G906S & had the following stock firmware installed & worked well & I have left the reactivation lock on.
PDA: G906SKSU1ANK1
CSC: G906SSKC1ANK1
Google play was updating some apps & suddenly the phone went in to a boot loop. I tried to get in to recovery mode but didn't work. I tried many tutorials and guides from this site but couldn’t get the phone to recovery mode. So I installed latest USB drivers & flashed above mentioned KitKat 4.4.2 ANK1 successfully. Still the boot loop and no recovery mode. Removed the battery and tried & nothing, no recovery mode. I got to know that the phone is soft bricked.
Then I came across this thread, describing you should do a firmware install using Nand Erase All , Re-partition & Phone EFS Clear in ODIN 3.09...using Pit file and Stock ROM.
https://forum.xda-developers.com/sho....php?t=2610757
I got the SM-G906S PIT file from the following thread @ #1398
https://forum.xda-developers.com/gal...807639/page140
Using Odin 3.12 flashed as described in the previous thread. It failed giving me the following results....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After failing that I again flashed stock ANK1 firmware using Odin 3.12 normal settings and everything went well. Still phone goes into boot loops. No recovery mode either. But this time after exiting Odin 3.12 while the USB cable still plugged in to the PC I removed the battery & again tried to go to the recovery mode. This time it worked!!!
I cleared the cache & factory reset the phone & rebooted. Phone booted past the Samsung logo till the page where it shows LTE-A X3 logo and briefly came to the language selection page for the KitKat OS and then completely shut down and battery charging logo was displayed on screen as the phone is still connected to PC.
I removed the phone from PC and tried to reboot again. Boot loops happen again and no recovery menu booting. Here the phone ran on battery power only.
Switched off the phone & connected to wall power outlet and rebooted. Again, boot loop appears and I removed and re install the battery and then try to go to the recovery menu & again it works. Clear the cache & factory reset the phone and reboot. As before the phone boot till the language selection page and shuts down and battery charging logo was displayed on screen as the phone is still connected to wall socket.
But if I try to boot to recovery mode while the phone running on battery power only it just goes on with the boot loop without going to the recovery menu even when the keys are pressed. Only “recovery booting” appears in blue color when the Volume Up, Home and Power keys are pressed.
By this stage I am skeptical to whether I have damaged the partitions of the phone since I used a PIT file to re partition according to above thread & failed. But I do not know for sure.
Then I again flashed stock ANK1 above, hoping it would work but still the same results.
Reading for some more information I got to know that while the reactivation lock is on you cannot flash any ROM to the phone. Is that true?
Then I came across this thread
https://forum.xda-developers.com/note-4-tmobile/help/reactivation-lock-soft-brick-t3144253
According to the above thread you can remove the reactivation lock on soft bricked G906S phones using TWRP Recovery. Then I downloaded necessary files from the following thread....
https://forum.xda-developers.com/galaxy-s5/development/recovery-twrp-recovery-v2-8-7-0-t3199011
downloaded the following file for KitKat .
KK & LP : Old versions (V1 ~ V4) (trlte port) ----> G906SKL_TWRP_3.0.0-0_PORT_V4.tar
using Odin 3.12.3 flashed the TWRP tar file according to the https://forum.xda-developers.com/note-4-tmobile/help/reactivation-lock-soft-brick-t3144253 thread @ #3.
Flashing TWRP failed as follows....
Phone's download mode menu on top says "secure check fail: recovery"
Since the Odin is mentioning a PIT file & I haven't given it one above, I again tried to flash TWRP with another PIT file but that also failed as well giving the message "re-partition operation failed" in Odin log.
I've tried flashing with Kies too but never got a code for it & the serial of the phone doesn't work with both Kies & SmartSwitch.
These are the things I have tried to fix my phone but still no luck.
What else can I do to fix my phone?
Getting the phone back to ANK1 (Android 4.4.2 KitKat) would be enough.
Please advice me on what to do next.
Thanks much in advance.

tlcd said:
I am new here & not much experienced. Particulars of my phone is as follows....
Click to expand...
Click to collapse
I don't have this variant and the SM-G906S is also known as the Galaxy S5 Prime as well.
Here's just a handful of threads that's specific to your device and may be helpful for what you are looking for. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=2807639
https://forum.xda-developers.com/showthread.php?t=3115735
https://forum.xda-developers.com/showthread.php?t=3115008
https://forum.xda-developers.com/showthread.php?t=3441811
https://forum.xda-developers.com/showthread.php?t=3441007
(I also had found a few odd references regarding this specific devices charging port easily going bad but, I can't state that this is definitely the case for you.)
If all else fails and, you don't receive any responses from any of the above threads, your next best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Ibuprophen said:
I don't have this variant and the SM-G906S is also known as the Galaxy S5 Prime as well.
Here's just a handful of threads that's specific to your device and may be helpful for what you are looking for. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=2807639
https://forum.xda-developers.com/showthread.php?t=3115735
https://forum.xda-developers.com/showthread.php?t=3115008
https://forum.xda-developers.com/showthread.php?t=3441811
https://forum.xda-developers.com/showthread.php?t=3441007
(I also had found a few odd references regarding this specific devices charging port easily going bad but, I can't state that this is definitely the case for you.)
If all else fails and, you don't receive any responses from any of the above threads, your next best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thank you very much for the reply. I did like you said and have received one reply from one of the threads you asked me to post. I have also updated my post above with all the new things I have tried. Thanks much again.

SM-G906S Soft Bricked with Boot Loops & Re-activation lock on...PLEASE HELP - SOLVED
Solution was posted at the following thread
https://forum.xda-developers.com/ga...ner-thread-t2807639/post77083953#post77083953