Related
I have an international G930F, baseband (G930FXXU1APEQ), build number (MMB29K.G930FXXS1APGC). I also have a version from the United Arab Emirates if that helps at all. I was recently looking at the TWRP page for the S7 and saw this warning:
"! IMPORTANT ! WARNING #3: It appears that an OTA is being distributed that may be partially flashing devices before checking if they are in an unofficial state. This could leave your device in a half flashed different version state! The message you may see after this is something about DRK verification failing from reports (no screenshot available), and the device WILL NOT BOOT even after flashing a full stock firmware package and wiping in stock recovery! No known solution has been found so far. Root or use custom images knowing this risk. (some have been quoted $250 for repair)"
Can someone shed light on exactly what this is and if I will be ok flashing TWRP? Thanks in advance!
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
The things i tried so far:
1- Reflash with the latest stock firmware. Ticking the NAND erase all and repartition it with pit file also didn't work.
2- Samsung Smart Switch and Kies3. Flash completed but no effect.
3- Flashing any recovery files returns with "Custom binary(recovery) Blocked by R/L".
4- Sent it to my nearest Samsung service centre, they did try to repair it but only to be told that my S6 need a new motherboard the next day, which is out of my budget limit. But i am still hoping to find some other way to fix it, i believe this is just a "soft-brick" not a hard brick device.
Ideas guys? thanks.
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
thereassaad said:
Try to re flash stock odin firmware with erase all ticked ok ,
Good luck ,,
Click to expand...
Click to collapse
Already tried that, still no luck..
mrkage said:
Hello, I have a soft bricked (hopefully thats the case) Samsung Galaxy S6 SM-G920F xme region (Malaysia) with android 6.0.1 latest stock rom.
It started when my device suddenly restarted and got stuck at the samsung logo (first screen).
I am able to boot it into Download Mode, tried reflashing with a fresh stock rom MM 6.0.1 with odin, flashing proccess was completed with no fail but it still stuck at the same screen.
I can't even boot into recovery mode so i can't wipe the cache partition, i noticed the Reactivaction Lock status is ON, i suspect that might be the culprit?
Ideas guys? thanks.
Click to expand...
Click to collapse
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Try Samsung Smart Switch, it has some recovery features that can automate the process for you.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
mrkage said:
Thank you for taking a look at my problem here, i forgot to mention that i did try Samsung Smart Switch and Kies3, both managed to succesfully flashed the stock firmware, it reboots my device and still stuck at the same first screen.
Click to expand...
Click to collapse
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
I believe it is doing that because you have a locked bootloader. Normally that shouldn't be a problem unless you're trying to flash a firmware that is older than what you had.
What stock firmware version/build number did your device have? What firmware version/build number is what you are flashing? If what you're flashing is older it might be downgrading your bootloader, bootloader can't be downgraded on most locked bootloader Samsung devices these days.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
mrkage said:
Don't remember the build number, but it was a 6.0.1 firmware, i flashed it with the same stock firmware version.. but maybe the build number didn't match.
I read somewhere about the engineering bootloader, i know it is not so easy or even possible at the moment to find one for my current firmware version, but let's say if i have it, will it be possible for me to use it to remove the RL on my device?
Click to expand...
Click to collapse
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Did you flash a firmware from a different g920 series device? Or did you flash the firmware for your specific model number and your and carrier?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Only did for my specific model number and carrier
mrkage said:
Only did for my specific model number and carrier
Click to expand...
Click to collapse
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Let me backtrack. Do you know if USB debugging is on?
Did you flash TWRP with a locked bootloader before this happened? Is that what caused the issue?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
mrkage said:
USB debugging and Developer Mode was never turned on that device.
Negative, i did try flashing TWRP but it was after it got stuck at the logo screen and only able to boot into Download Mode, the flashing came back failed with "Custom Binary (recovery) Blocked by RL" message.
Flashing it with the latest stock recovery i found online also gave me the same error message.
Click to expand...
Click to collapse
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Droidriven said:
Just out of curiosity, have you tried booting to safe mode? If any of the apps that you installed before this happened were causing an issue or bootloop before you flashed are still there, it/they could still be causing the bootloop. Remember, I said that it doesn't wipe data unless you are upgrading or downgrading bootloader/baseband, what you flashed wasn't an upgrade or a downgrade so your data is there. Boot to safe mode and disable/uninstall the apps that might be causing the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
Click to expand...
Click to collapse
Didn't try that... but nevermind. I accidentally damaged my screen while trying to dissasemble it last night, a very stupid mistake from me.
Thank you for trying to help me mate. Forum mods can close this thread now. Thanks all.
problem
i have too but with A/L
with very little activity lately for the LGV20, especially with the unlocked US996 variant, I created a TWRP flashable package for the recent US99610k release. this zip flash every partition included in the latest KDZ package with the exception of recovery to keep TWRP. standard disclaimer applies, you do all of this at YOUR OWN risk! because I have not tested this yet, I can't verify whether 10k is rootable or not or if there's Anti-RollBack (ARB), so you need to be root'd before flashing this! failure to do so will probably cause you to lose root and/or lose TWRP! if 10k does have ARB you won't be able to downgrade. stay tuned on this.
NOTE1: you can find the partitions that will be flashed in the updater-script. to be extra cautious you can back up all of the partitions that will be overwritten with the following: dd if=/dev/block/bootdevice/by-name/{partition} of=/external_sd/backup/{partition}.img.
NOTE2: boot partition has been modified only to remove rctd, nothing else so I consider this to still be stock
Instructions:
download US99610.zip file listed below and put on microSD card
download your choice of root and put on microSD card, choose from either Magisk or SuperSU *Note: v12.0 of Magisk does not work with the LGV20 device in general and v14.0 is recommended.
backup any data from internal "SD card"
boot into TWRP (requires TWRP recovery to already be installed)
create a TWRP backup of the device
flash zip from microSD card by using "Install"
FLASH YOUR CHOICE OF ROOT - Flashing root is VERY IMPORTANT BEFORE REBOOTING!
reboot
profit!
Download:
US99610k.zip md5sum: 26da82660579673e5486e0361ff8c6e6
US99610l.zip md5sum: 01423ade5ba4977e1e8ae6d5bc244ecf
US99610n.zip* md5sum: bbde6e972305918712b3c51f03a1be10
US99610o.zip md5sum: 6019e92c6e0b3691689820b43b2b0c5d
US99610p.zip md5sum: 9875e4da163168c84ce479509bf7e19d
US99620f.zip* md5sum: 3AEBED11462D0F4A18D3FB9A4FDE95EB
* - unlocked non-US Cellular
for 20f (Oreo) please see this comment about updating TWRP and /data encryption https://www.reddit.com/r/lgv20/comm...s99610k10l10n10o10p20f_stock_rom_twrp/ed5olp6
Flashing Process (what flashing this zip does):
flash necessary partition images with the exception of recovery (to keep TWRP) from the KDZ
rename /system/recovery-from-boot.p to /system/recovery-from-boot.bak to prevent stock recovery from being installed on boot
wipes dalvik-cache and cache
BIG thanks to @McNutnut on guidance, as well as his script to put all of this together!
also thanks to @bullghost for the KDZ extractor (https://forum.xda-developers.com/showthread.php?t=2600575)
@Tilde88 for the original updater-script template w/root (https://forum.xda-developers.com/v20/development/us996-nrd90m-modded-notsostock-rom-v5-1-t3526542)
On your instructions portion it says h91810q.
storm68 said:
On your instructions portion it says h91810q.
Click to expand...
Click to collapse
haha, thank you for helping me correct that!
Hmmmm. Not tested you say.... Nervous I am. Have time to fix using computer I do not.
I've been running 10k for almost a week now and haven't seen any issues. I can't necessarily speak for this ZIP, though. Taking a glance at it things look good.
One thing I'd like to point out is an issue I saw reported by another user. They stated that after they flashed US Cellar US996 updates their Unlocked US996 device was being picked up as the US Cellular device when attempting to use the LG website bootloader unlock. This is most likely due to the US Cellular bootloader being flashed and the device reporting a US Cellular device ID. This hasn't caused any issues when your device has already been bootloader-unlocked but I would not suggest that users re-lock their bootloader when running this US Cellular firmware as you may risk running into problems unlocking. The same user had also reported that they just flashed the 10f kdz with LGUP to correct the problem but not a risk I'd like to see anyone take. Just a word of caution.
McNutnut said:
....
Click to expand...
Click to collapse
Thanks for the heads up.
Can you confirm what security patch 10k is up to on the 996? Any other documented updates/fixes?
nickthaskater said:
Thanks for the heads up.
Can you confirm what security patch 10k is up to on the 996? Any other documented updates/fixes?
Click to expand...
Click to collapse
September 1st
No documented changes that I've seen.
No issues flashing for me... didn't wipe data, works well.. not sure what the changes are though, looks like the same
leonzwrx said:
No issues flashing for me... didn't wipe data, works well.. not sure what the changes are though, looks like the same
Click to expand...
Click to collapse
If it's just a security update there won't be any visual differences.
I just installed and everything is as it was on 10h, save for the security date.
Thank you.
I flashed from US99610h to US99610k with no issues. I did not flash supersu or magistick after flashing the firmware because I need to use uverse app. So far 24 hours with no issue or crash.
I extracted this modem (actually I just removed everything else from the zip and modified the script file) because I wanted to see if the newer modem fixed some streaming issues I had. I'm on Lineage, but it looks like the modem keeps crashing. It works fine for a few minutes while streaming music but then crashes and takes the WiFi and LTE with it for a few seconds.
Shouldn't this updated modem work with 7.1?
Doug
Hello, my phone stuck in Logo LG. But before I was in the red triangle and I thought that installing this would work well. But now the bootloader has been blocked and I can no longer enter recovery. And I have happened to install by fastboot the recovery stock but I can not find that file anywhere.
Somebody can help me please?
Edit. The LGUP detect the phone but with unknow model. I put the dll in common and doesnt work. I dont know how to unbrick my phone
Edit 2: I think the OEM is blocked, because I tried the "fastboot oem lock" command and it says it was already blocked, then try to unlock it "fastboot oem unlock" and says: FAILED (remote: unknown command). I think it's because the box was unchecked in Settings> General> Development, but the problem is that I can not boot to activate it.
10l has been released for the US Cellular 996: https://lg-firmwares.com/lg-us996-firmwares/
I confirmed with a US Cellular rep that 10l includes:
KRACK Wi-Fi vulnerability fix
BlueBorne fix (for SPLs September 1 or later)
Anyone with enough brains and heart to put together a .zip for the plebs?
nickthaskater said:
10l has been released for the US Cellular 996: https://lg-firmwares.com/lg-us996-firmwares/
I confirmed with a US Cellular rep that 10l includes:
KRACK Wi-Fi vulnerability fix
BlueBorne fix (for SPLs September 1 or later)
Anyone with enough brains and heart to put together a .zip for the plebs?
Click to expand...
Click to collapse
thanks for the update... I've updated the first post to reflect a 10l TWRP ZIP that works just like 10k that you can flash... tested working on my own US996
dimm0k said:
thanks for the update... I've updated the first post to reflect a 10l TWRP ZIP that works just like 10k that you can flash... tested working on my own US996
Click to expand...
Click to collapse
Thank you very much!
Hey, I'm still on Dec 2016 stock using us996 us cellular. I can flash and keep root? That's what it sounds like but just confirming. If I do a clean flash, Magisk 14 works fine? Thx
strifej said:
Hey, I'm still on Dec 2016 stock using us996 us cellular. I can flash and keep root? That's what it sounds like but just confirming. If I do a clean flash, Magisk 14 works fine? Thx
Click to expand...
Click to collapse
Just follow the instructions in the OP. You need to reflash the Magisk 14 image immediately after flashing the 10L zip.
Anyone know if the radio in either one of these is improved? - I have an unlocked US996 (from B&H photo, not US cellular) and regardless if I am using Verizon or AT&T, my current ROM's (US99610f) radio is very weak in weak signal areas - much crappier phones get much better signal in weak areas. I am hoping a new radio has solved this. It is the only thing I dislike about the V20
Also, with my standard unlocked US996 (already bootloader unlocked via LG developer website) am I better off with 10k or 10l ?
WTF? said:
Anyone know if the radio in either one of these is improved? - I have an unlocked US996 (from B&H photo, not US cellular) and regardless if I am using Verizon or AT&T, my current ROM's (US99610f) radio is very weak in weak signal areas - much crappier phones get much better signal in weak areas. I am hoping a new radio has solved this. It is the only thing I dislike about the V20
Also, with my standard unlocked US996 (already bootloader unlocked via LG developer website) am I better off with 10k or 10l ?
Click to expand...
Click to collapse
Be careful, when I flashed this to my unlocked US996 on Verizon I lost all data, and furthermore could not restore stock without uppercut. I think it's bound to US cellular, these firmwares.
R-T-B said:
Be careful, when I flashed this to my unlocked US996 on Verizon I lost all data, and furthermore could not restore stock without uppercut. I think it's bound to US cellular, these firmwares.
Click to expand...
Click to collapse
I'm not sure what you did, no, you shouldn't have lost your data nor is it bound to US Cellular devices. I have the 10L zip running on my unlocked 996 without any issue. I flashed it via TWRP from 10K and didn't lose anything.
Hello wise people of XDA,
This is my first post.
I currently use an S6 G920F United Kindom unlocked as my phone and i have been using this phone for a long time. Now its past its warranty I decided to root the phone and see what i can do with it and get rid of the bloatware. Normally i either use KingoRoot or KingRoot but both failed so I searched around on the internet and came across CF Auto Root. After seeing it was successful for others i jumped on the bandwagon. I rooted it and everything was golden until i came across a problem, it would randomly turn off. This was random and infrequent. but not it happens like 5 times a day so i decided to flash a stock rom. For some strange reason Sam mobile wont let me download a stock Rom so after poking around the internet i have download a few stock roms however they always fail in Odin. Now my phone wont even boot as it says "error occured while updating use smart switch emergency recovery feature" so i go onto the Smart switch PC app and then it doesnt recognise. After 2 days of trying i haven't had any luck so I don't know what to so. Every time I try flashing something, when it fails i get some red text on the phone which I don't understand.
Someone please help me as I cant just buy a new phone and this is the only phone i have got. Any help would be very grateful and please don't hesitate to ask any questions.
Edit:
It says on the Download Screen:
Odin Mode
Product Name: SM-G920F
Current Binary: Custom
System Status: Custom
Reactivation Lock: Off
Secure Download: Enabled
Knox Warranty Woid : 1 (0x0500)
RP SWREV: B:6 K:2 S:2
(When it fails it says) SW REV. Check Fail. Device:6 . Binary: 5
Hopefully that helped.
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Bryan48765 said:
Somewhere in the middle of the firmware version there's either S5 or U5, on the firmware you are trying to flash. On the phone either S6 or U6 is installed, and there's downgrade prevention. You need firmware with S6 or U6. By S6 I don't mean the phone, it is just a version code.
Generally look for the firmware meant for the phone's region, though on websites the displayed region might be incorrect.
If the cellular fails change the firmware or wipe data (not efs!!!!!).
Click to expand...
Click to collapse
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
wasim.1.wt said:
What do I do? I have like 10 different "stock roms" claiming to be United Kindgom BTU at Android 7.0 but all are failing. And I do not know what you mean by S5/6 and U5/6. And now i get a different error message. When it fails it now says Binary: 1. I don't know what to do!
Thanks for the quick reply and appreciate the help.
Click to expand...
Click to collapse
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Bryan48765 said:
The firmware version(s) look like this,
G920FXXU6ERF5 . If there is U6 on the device and the U5 is flashed, it won't work. There are a few firmware 'components' inside the zip or whatever, and all of these must have the same or a higher version in the middle. New firmware might require odin 3.13.1 but should not show this error.
Click to expand...
Click to collapse
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
wasim.1.wt said:
I see. All this time i have been flashing the likes of U1 and U3 . So which version should I be flashing? U5 or U6?
Many Thanks!!!!
Click to expand...
Click to collapse
U6/S6, "Device:6" is in the odin log so it's already 6 and won't return to 5.
Hello
Combination G930F version of protection U6 got a problem in the device refuses to take off the system and recovery only I can access the download mode does not accept any recovery rate or official or any system lower than the protection of U6 did not work full ROM repair I have searched in all Arab and foreign sites I have not found Never my only hope in the Combination Rom
did you manage to solve this? i have the G935f, after odin flash u6 combination file for g935f, i cannot get passed boot screen. top right of screen i see nad acat failed....anyone who can help?
I am also in the same situation with a G930WS. The FRP lock is preventing anything from being flashed. The binary 6 e-fuse gives us limited options for firmware. Stock rom will not boot, custom roms fail. Dr. Fone does not fix this. Clearing the cache a dozen times will not make a difference. Installing numerous applications that can detect the phone and do nothing more than that despite what they rave about - Fail. A combination rom seems like the only option after plenty of wasted time, but there is none (that I have found yet) for Oreo. So if you have updated your bootloader past Nougat, like I have then we are sol until one comes available.. we may be waiting awhile. Grab a new phone, save yourself a headache for now. Merry Xmas.