Related
last night i went to sleep with m galaxy s6 g920f STOCK 5.1.1 had a fair amount of battery left in t. When a woke up in the morning my phone was dead i thought the battery would have been consumed . I plugged it in charged it . Now when i try to turn it on it just jo to "samsung Galxy s6" logo ,screen becomes a bit yellowish and the phone restarts same thing is happening again and again.
Now i have tried to reinstall to odin, then going into recovery factory reset cache but same results. anyone please help this phone was running stock os so... i have searchd the web but there are no ways to fix it ...
Regards
any help please !
guys i need your help please
I would suggest you download a ROM from Sammmobile that corresponds to your country and install that via ODIN and if that doesn't work try one from a different country or one tha is unknown (I.E. that doesn't belong to a any country), I softbricked my phone trying to install H3G for UK and for what ever reason it would not install. However...
I downloaded one called BTU and that worked using this app SamFirm. To get my version I installed type the Model number SM-G920F and Region BTU to download, once it has downloaded then decrypt the file by clicking the Decrypt button and unzip the decrypted file and then use ODIN to install that one. Using the SamFirm app downlaods it faster and gets the latest from Samsung as far as I am concerned. Good Luck.
protonpower said:
I would suggest you download a ROM from Sammmobile that corresponds to your country and install that via ODIN and if that doesn't work try one from a different country or one tha is unknown (I.E. that doesn't belong to a any country), I softbricked my phone trying to install H3G for UK and for what ever reason it would not install. However...
I downloaded one called BTU and that worked using this app SamFirm. To get my version I installed type the Model number SM-G920F and Region BTU to download, once it has downloaded then decrypt the file by clicking the Decrypt button and unzip the decrypted file and then use ODIN to install that one. Using the SamFirm app downlaods it faster and gets the latest from Samsung as far as I am concerned. Good Luck.
Click to expand...
Click to collapse
Thank you very much for your reply i have tried flashing 6 stock firmwares but to no avail ? Can you suggest anything else ?
M.Nabeel said:
Thank you very much for your reply i have tried flashing 6 stock firmwares but to no avail ? Can you suggest anything else ?
Click to expand...
Click to collapse
The only thing I can think of is trying one from your country and trying any other one. You can use the SamFirm software to download different versions, else I think your phone is broken for some unknown reason and you will have to get it fixed under the warranty. Or install the Samsung Smart Switch from samsung and get the firmware installed that way via the Emergency Software and recovery mode, but it will wipe everything and do a factory reset. Also you will need the serial number and model number of your phone.
After installing a custom ROM on my galaxy s6 it would no longer recognize my SIM card. I did wipe every option in TWRP recovery before flashing the ROM which might have something to do with the issue. The phone states "No SIM Card - No Service" in the top left of the lock screen, it also wont let me call any numbers to edit things in the phone. I have done some research and it sounds like I have wiped the sim and lost the IMEI/EFS data and therefore no longer have access to my sim. I was wondering if there was any possible fix or should I just send it off to Samsung to get repaired?
Did you back up the EFS partition, and put it somewhere safe? If not, you have a paperweight.
Repair won't be covered under warranty.
Sent from my SM-G920F using Tapatalk
Unfortunately I didn't back up the EFS partition. Situation is looking bad. :l
Try dialnig *#06# and see does it shows IMEI and sn, alo try *#0011# select stack 1 and check whether IMEI is OK, or NG.
Also what does it say in phone settings under baseband? Do you have mobile networks menu in settings?
You can try Smart Switch emergency initialization with sn of the phone if IMEI is ok (it will install latest stock fw for your phone) and see if that helps.
When I typed in "*#06#" The SN number was shown however the IMEI number was not. When I typed in "*#0011#" There was nothing but blank spaces separated by grey lines, I tried selecting row 1 however nothing happened. My base band version is "Unknown" listed under settings. I do however have the network settings listed in settings. In Smart Switch when I try to run the device initialization it states that my s6 "doesn't support initialising". I have flashed three different downloads of the stock rom to my phone using ODIN and have had no luck with any of them.
well Smart Switch always says that S6 is not supported, but initialization can be done anyway, just dont connect the phone until it asks you to do so, instructions below:
http://forum.xda-developers.com/galaxy-s6/help/how-to-smart-switch-emergency-t3383448
What is your model anyway, do you know which region fw was originaly on the phone, and which sv rev is shown in the download mode?
does in recovery mode says anything about DRK?
Unfortunately Smart Switch says that "'SM-G920F' does not support initialing. Please contact out service center." Even when I have entered the correct S/N and device model, as well as not plugging in the phone. My device model is the SM-G920F. I don't know the original region FW that was originally on the phone, however it was purchased in the UK and that is where I am have been ever since I bought the phone. The SWREV is: "B:3 K:2 S:2" in download mode. I currently have TWRP recovery installed so is there a place for me to search for the DRK in TWRP? Or should I re-flash the stock recovery using Odin?
that is weird, I reinitialized my g920f many times without any issue. DRK error is usually shown in stock recovery. does the phone boots up with stock fw, and are you using any custom kernel?
i got the same problem when I flashed xtrolite and alexis custom ROM on my S6, both ROM after flashing I got no service.
But I did a full stock backup in TWRP.
baseband unknown means that there is a problem with modem part of fw. and I dont know what fw you flashed. you said that you tried to flash stock, but it doesn`t work, but a little more details would maybe make a difference, like which fw, and what exactly is happening, what does about the phone menu says.
So far, since baseband is unknown I would try to flash modem fw with odin (for exact fw that is in the phone). before that usb settings should be set to CP, by dialing *#0808#
or if you decide tu run custom fw, you can always try asking in that rom thread, maybe someone already had issues like that with that rom and fixed them, or the developer of that rom can help fix it.
Boot your s6 to download and flash stock rom via odin from samsung it maybe work
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Paachan said:
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Click to expand...
Click to collapse
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
Well this reply isn't really that helpful...
1st she doesn't care anymore because as mentioned she already has a new phone and said I can just keep it or throw it away.
2nd even if it's bricked there are ways to get it back to working, I soft bricked my old HTC M8 once and restored it.
3rd If you're a noob with this just don't reply, I've never had experience with Samsung phones before thats why I'm seeking for help, if it comes to HTC or LG phones I usually get things done myself. Not in this case tho.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
*Detection* said:
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
Click to expand...
Click to collapse
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
audit13 said:
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
Click to expand...
Click to collapse
so in this case with the DBT version it's just the default customization file from Samsung, am I right?
Flashing either Home_CSC or CSC didn't had any effect on the S7 tho, it's still stuck in Boot loop with FRP Lock.
Let's say the phone is soft bricked, is there any way to get it back working, so I can flash the stock firmware afterwards`?
Paachan said:
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
Click to expand...
Click to collapse
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
*Detection* said:
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
Click to expand...
Click to collapse
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
audit13 said:
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
Click to expand...
Click to collapse
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Sounds like you have tried all you can on your own. Maybe take it to a cell repair shop and have them try to force flash the phone using hardware such as an octopusbox?
Paachan said:
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
Click to expand...
Click to collapse
Yep G930F is International Exynos so you should be good
Some people have problems downgrading from 7.0 to 6.0, what I meant was flash the latest available firmware for DBT, which is 7.0
2018-04-23
Germany
7.0
G930FXXS2DRDI
As above, the bootloader can be a pain to downgrade, so always try unbricking with the latest firmware available
Same process as I posted above, only using the firmware in this post ^^
Good luck
---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------
Paachan said:
I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an indicator)
Click to expand...
Click to collapse
Yea that doesn't sound good, possibly a faulty motherboard, they seem to be quite a high % of hardware faults of the S7 on XDA, at least that is the outcome of sending them in for repair, but also could be the repair centres way of making the most £
Paachan said:
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Click to expand...
Click to collapse
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Matty1993 said:
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Click to expand...
Click to collapse
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
{
"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"
}
Sorry for my late reply!
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
I'm not 100% sure about this, but that firmware states S2 not U2
See here, my BL is B:2 but all of the firmware files I can successfully flash are U2
Matty1993 said:
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Click to expand...
Click to collapse
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Also maybe download U2 firmware aswell as S2 firmware
Matty1993 said:
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Click to expand...
Click to collapse
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
*Detection* said:
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
Click to expand...
Click to collapse
Or that also maybe yeah try U2 firmware instead of S2 as far as im aware S2 is the first of the B:2 binary updates
After FLASING Stock Rom on Samsung Galaxy S7 the device REBOOT after " NO COMMAND "
My device is SAMSUNG GALAXY S7 (G930F)
1. I installed TWRP (twrp-3.2.3-0-herolte.img) via ODIN ver. 3.14 .
2. I had make format all via TWRP.
3. I installed SUPERUSER (BETA-SuperSU-v2.71-20160331103524)
4. I installed NO-VERIFY-OPT-ENCRYPT (no-verity-opt-encrypt-3.1)
5. I installed via ODIN the STOCK ROM of my country and region (COSMOTE-GREECE).
- The device after the succefull install (via ODIN) reboots and after erasing shows (in blue screen) the message "NO COMMAND" or "ERROR" and reboots.
- After reboot doing always the same procedure.
- Any help will be avaible because i been using this phone for my work.
george_1234 said:
My device is SAMSUNG GALAXY S7 (G930F)
1. I installed TWRP (twrp-3.2.3-0-herolte.img) via ODIN ver. 3.14 .
2. I had make format all via TWRP.
3. I installed SUPERUSER (BETA-SuperSU-v2.71-20160331103524)
4. I installed NO-VERIFY-OPT-ENCRYPT (no-verity-opt-encrypt-3.1)
5. I installed via ODIN the STOCK ROM of my country and region (COSMOTE-GREECE).
- The device after the succefull install (via ODIN) reboots and after erasing shows (in blue screen) the message "NO COMMAND" or "ERROR" and reboots.
- After reboot doing always the same procedure.
- Any help will be avaible because i been using this phone for my work.
Click to expand...
Click to collapse
Use Odin to install the latest firmware for you country, then use CF-Auto root, do not use SuperSU it no longer works.
george_1234 said:
My device is SAMSUNG GALAXY S7 (G930F)
1. I installed TWRP (twrp-3.2.3-0-herolte.img) via ODIN ver. 3.14 .
2. I had make format all via TWRP.
3. I installed SUPERUSER (BETA-SuperSU-v2.71-20160331103524)
4. I installed NO-VERIFY-OPT-ENCRYPT (no-verity-opt-encrypt-3.1)
5. I installed via ODIN the STOCK ROM of my country and region (COSMOTE-GREECE).
- The device after the succefull install (via ODIN) reboots and after erasing shows (in blue screen) the message "NO COMMAND" or "ERROR" and reboots.
- After reboot doing always the same procedure.
- Any help will be avaible because i been using this phone for my work.
Click to expand...
Click to collapse
You installed SuperSU at some point. Your Knox efuse is already tripped.
1. Flash your latest Oreo stock firmware and reboot. Do not touch the system anymore. If you don't want to root then you're done.
If it doesn't boot, wipe cache from stock recovery. Sometimes stock ROMs flashed from Odin don't boot until you do it.
If you see No Command, hold power and tap volume up once to bring up the menu.
2. Enable developer options, go to dev options and enable OEM unlock. Your bootloader is now unlocked.
3. Flash the latest TWRP through Odin
4. Reboot to TWRP and KEEP SYSTEM READ ONLY. Swiping to allow modifications will trip dm-verity in the stock ROM
5. (recommended but optional) Disable forced encryption. This requires wiping the internal storage. Mandatory for AOSP.
6. Wipe cache
7. Flash the latest Magisk from topjohnwu's GitHub
8. Reboot. If you don't have Magisk Manager installed already, download it from topjohnwu's GitHub.
9. Open Magisk Manager and let the initial setup complete.
10. Your device is now properly rooted with a modern, open source, systemless implementation.
Ok... i am done all of this (I install the update of Greece (COS) rom from sammobile) but the device cant found network (i cant make calls) but the IMEI shows up regularry in seetings.
With CHECK IMEI i found a code for my phone that is SM-G930FZDAOMN .
The last three digits (OMN) maybe is from vodafone in Italy because the phone came from this country.
I download the right ROM from sammobile for this, but i cannot install it via ODIN. (sboot.bin FAIL).
Any ideas ?
george_1234 said:
Ok... i am done all of this (I install the update of Greece (COS) rom from sammobile) but the device cant found network (i cant make calls) but the IMEI shows up regularry in seetings.
With CHECK IMEI i found a code for my phone that is SM-G930FZDAOMN .
The last three digits (OMN) maybe is from vodafone in Italy because the phone came from this country.
I download the right ROM from sammobile for this, but i cannot install it via ODIN. (sboot.bin FAIL).
Any ideas ?
Click to expand...
Click to collapse
Perhaps you need to register your carrier manually in network settings. Try cleaning your SIM card.
What do you mean ? How i can clean my sim card ?
george_1234 said:
What do you mean ? How i can clean my sim card ?
Click to expand...
Click to collapse
sboot.bin FAIL>>>> means you are trying to flash the wrong firmware.
This is the firmware for your device ....HERE.....
Greece unbranded (EUR) open to all networks.
Not registering on network with Stock Firmware, is a network provider problem, not a firmware problem.
Τhe same ...
Sboot fail...
george_1234 said:
Τhe same ...
Sboot fail...
Click to expand...
Click to collapse
SamFirm Tool, takes firmware direct from Samsung servers.
1. Extract from zip file
2. Run as admin, SamFirm application.exe
3. Leave everything as default
4. Model is SM-G930F (type exactly like that)
5. Region is EUR or COS (which ever firmware you want)
6. Hit check "update"
7. Hit "download"
8. Allow to download and decrypt.
9. 5 files, place in correct place in Odin, (use odin 3.13 not 3.14)
10. Only 1 CSC file needs to be used.
11. You know how to flash so can do the rest yourself?
Samfirm is attached to this post.
ok...
The EUR rom is on.
- But "NOT PHONE SERVICES ALLOWED"
- I check IMEI ... not stolen ...
- #*78# not working at all.
george_1234 said:
ok...
The EUR rom is on.
- But "NOT PHONE SERVICES ALLOWED"
- I check IMEI ... not stolen ...
- #*78# not working at all.
Click to expand...
Click to collapse
Ok, is the phone locked to a network?
Try manual Network selection in settings?
Try a different SIM card
This error is a problem with the SIM card or Network Provider (your mobile account).
I try ...
No solution ...
Is there a posibility to lock the device for Greece Providers ?
george_1234 said:
Is there a posibility to lock the device for Greece Providers ?
Click to expand...
Click to collapse
No
If the firmware is working then the problem is with the Sim card or network.
What network are you using?
Cos
(cosmote)
I alleady installed the right firmware
but still " NO PHONE SERVICES ALLOWED".
Ι try a sim card that is not registering at any network because is very old and not in use any more.
I clear cache from device app telephone and the same from card app.
Then i use my new sim from cosmote.
Well working for 2g and 3g but only for HSPA+ mode.
When i try for 4g/3g/2g and modile data lost the signal and never find it again. Only by the same way.
I put the new sim on XIAOMI MI A3 and 4g works fine.
I noticed that the device getting very warm with no reason and the battery from 14% goes down at once. This is very strange because i change the battery 6 months ago..
Do you thing is from motherboard because i am thinking to change that too ?
george_1234 said:
I noticed that the device getting very warm with no reason and the battery from 14% goes down at once. This is very strange because i change the battery 6 months ago..
Do you thing is from motherboard because i am thinking to change that too ?
Click to expand...
Click to collapse
George, you never mentioned this in your first post!
If you have messed about changing batteries (or if a "repair" shop did it) then yes it can be all sorts of hardware problems. The phone is not designed to be opened once it leaves the factory. Many users have reported problems when people change the battery.
It would be cheaper to buy a new S7 second hand as a new mother board would cost the same and there is no guarantee the problem would be fixed.
I repair Samsung phones and they are VERY difficult to repair without the correct equipment. The phones (as with iPhone) are very sensitive to any type of tampering.
I'm sorry I can't help you any further.
george_1234 said:
Cos
(cosmote)
I alleady installed the right firmware
but still " NO PHONE SERVICES ALLOWED".
Click to expand...
Click to collapse
Try taking your phone to a repair shop, perhaps your SIM card slot is damaged. And next time use Magisk instead of SuperSU, it's no longer reliable since 2.77
Let's Get Started by saying: I'm not resoponsible for brick, loss or any damage to your phone. So backup!
Pre Requirements:
a. A Windows PC with internet connection.
b. Odin Patched Here
c. HOME CSC file of Indian / Thailand / Vietnam Region. You can get firmware of your phone from samfw.com or any other website.
Make sure that the bootloader version on your phone and the one you download are same. For example, A515FXXU4CTJ1 has bootloader version 4 (that's fifth digit from the right). So you have to download a firmware which has same bootloader version.
P.S. We don't need full firmware, Only the file name beginning by "HOME_CSC" is needed.
Working:
1. Eject the SIM Card(s)
2. Go to Settings -> Apps -> Calendar -> Storage -> Clear Data.
3. Put your phone into download mode.
4. Run the Odin....exe (downloaded in step b) as administrator
5. Click CSC and select the HOME_CSC file obtained from step c in Pre-Req.
6. Click "Start".
7. When phone reboots, Repeat step 2.
All done. You can insert SIM Card(s) and use Call Recording.
Notes:
You'll be ondifferent region's CSC after this.
Phone will not factory reset and you won't lose any data after this.
You might not be able to get system updates after this. In order to get them you'd have to flash your region's CSC, then update, then flash custom CSC again.
Tested working on:
Samsung A51 (Android 10)
Samsung A50 (Android 10)
Samsung M21 (Android 11)
You tell
zubair1836 said:
Let's Get Started by saying: I'm not resoponsible for brick, loss or any damage to your phone. So backup!
Click to expand...
Click to collapse
Hi I tried your message but I got an error on my phone along the lines of : secure check fail cache (1). I tried with the odin version you linked and I was thinking about trying a version v3.14 patched that I found here on XDA. Any ideas?
My phone is fine it does seem to restart to a thing with the cyan download background saying "An error has occured..." but I can restart and then hit volume key saying 'reset phone' which just boots the phone normally.
n4noAbyss said:
Hi I tried your message but I got an error on my phone along the lines of : secure check fail cache (1). I tried with the odin version you linked and a version v3.14 patched that I found here on XDA. Any ideas?
My phone is fine it does seem to restart to a thing with the cyan download background saying "An error has occured..." but I can restart and then hit volume key saying 'reset phone' which just boots the phone normally.
Click to expand...
Click to collapse
This happens when you use a non Patched odin. Make sure you're using the one from link in OP. BTW, which phone is it?
zubair1836 said:
This happens when you use a non Patched odin. Make sure you're using the one from link in OP. BTW, which phone is it?
Click to expand...
Click to collapse
It's G991U1, with 1ATLI so I downloaded 1AUB8 (THL) to try to flash the HOME_CSC, I'm 100% sure I tried with the odin you linked (also your one has same CRC SHA-1 as the the one linked in the XDA thread). Maybe I need to try with the updated patcheD odin (v3.14.1_3B) I didn't do that yet.
n4noAbyss said:
It's G991U1, with 1ATLI so I downloaded 1AUB8 (THL) to try to flash the HOME_CSC, I'm 100% sure I tried with the odin you linked (also your one has same CRC SHA-1 as the the one linked in the XDA thread). Maybe I need to try with the updated patcheD odin (v3.14.1_3B) I didn't do that yet.
Click to expand...
Click to collapse
I believe everything's right then. Can't identify the issue though.
I guess, trying updated version might help.
Good luck!
If problem persists after trying updated version. Please share screen when phone is in download mode.
I had kept this thread in my bookmarks since I was buying the A52 4G on Amazon.ca and absolutely wanted Call Recordings (officially we shouldn't be able to get the A52 4G in Canada, only the 5G version is officially here, so it's an import).
But as luck would have it, it's the SM-A525M and already has Call Recording enabled in it. So that saves me some trouble. But thanks for this guide! I may not have needed it in the end, but would've totally relied on it otherwise.
If I'm understanding this right, my firmware is A525MUBS1AUD1. Brazil's ? It's Android so it has every languages built-in regardless and there's no carrier specific apps in it either, so that's great.
tried on A52 4G all flashed fine
but the csc did not changed and no call recorder
tridi001 said:
tried on A52 4G all flashed fine
but the csc did not changed and no call recorder
Click to expand...
Click to collapse
Well, That's unlucky then; it's unavailable on certain devices.