Database Users

[Q] What did I do to my I9500 (probs with 4.3, ODIN, recovery, etc.)?

This is where my I9500 is right now:
AP: I9500UBUBMG9
CP: I9500UBUEMK1
CSC: I9500UUBBMG9
I know that MK1 is from 4.3 and MG9 from 4.2.2. So I'll tell you how my phone got there:
Last week I flashed stock 4.3 (and did a backup in CWM recovery before flashing.) To my dismay, everything with 4.3 was very laggy and unresponsive; services were stopping left-and-right. A battery-pull/hard-restart had no effect. The lag was so bad that it took me 2 to 3 minutes to properly shut it down each time.
So at that point, I planned to reflash 4.2 (I was not aware of the problems of downgrading after upgrading to 4.3.) In trying to do so, ODIN (on my PC) would just freeze partway through, never completing the process and giving me some error message. In trying to reenter ODIN mode, I'd get the yellow triangle screen each time.
After some searching of the forums here, I found and did something (I can't remember exactly what it was) but I managed to enter ODIN mode. This time I tried reflashing again. Same thing, of course. But this second time around I noticed the "warranty bit: 1" thing that I hadn't noticed before (I figured it had to be something to do with knox that I had read about in upgrading to 4.3.) Here's my current screen in ODIN mode:
PRODUCT NAME: GT-I9500
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
WARRANTY BIT: 1
Anyway, rather than keep messing around with ODIN, I thought I would just restore the backup I made. But instead of entering recovery, I kept getting the yellow triangle. Finally, as a last-ditch effort, I ended up reflashing CWM Recovery through ODIN. Then I was able to successfully enter recovery mode, restore my backup image. Now my phone runs just as it did before (just with a different baseband version.)
What does all this mean for my device?
Any ideas why 4.3 was crashing everything? Is there something different I should do before I reflashing 4.3? Or should I wait for a more stable 4.3.x? (I assum the errors I experienced in ODIN were due to trying to downgrade to 4.2. I would certainly hope to use ODIN in the future to flash new versions.)

1. You cant come back from 4.3 to 4.2.2
2. You void ur warranty for the step 1
3. ODIN didnt finish any process for the step 1 too.
4. You could come back to 4.2.2 coz u restored one backup. You still having new bootloader (warranty bit:1) with old 4.2.2 firmware.
5. Go to Apps - Settings - More - About device and make us a screenshot pls
4. Conect ur phone to Kies (android 4.2.2) or Kies 3 (android 4.3) and tell us what appears close CSC btw (). We need know ur zone code and download the correct firmware for ur region

Joku1981 said:
1. You cant come back from 4.3 to 4.2.2
2. You void ur warranty for the step 1
3. ODIN didnt finish any process for the step 1 too.
4. You could come back to 4.2.2 coz u restored one backup. You still having new bootloader (warranty bit:1) with old 4.2.2 firmware.
5. Go to Apps - Settings - More - About device and make us a screenshot pls
4. Conect ur phone to Kies (android 4.2.2) or Kies 3 (android 4.3) and tell us what appears close CSC btw (). We need know ur zone code and download the correct firmware for ur region
Click to expand...
Click to collapse
From Kies:
{
"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"
}
TPA is Panama, right? When I flashed 4.3, it was indeed "TPA" (so I'm really clueless why it was so laggy and unusable.)
From my phone:

mathyou9 said:
From Kies:
TPA is Panama, right? When I flashed 4.3, it was indeed "TPA" (so I'm really clueless why it was so laggy and unusable.)
From my phone:
Click to expand...
Click to collapse
- You cant receive OTA updates or Kies updates (u see it in the screenshot u attached before) how u have the phone now
- I will tell my steps and u can do what u wish later:
1. Download and unrar correct firmware for ur phone -> HERE (I dunno where u download it, anyway if u have it u dont need download it again)
1. Make a Internal Memory backup
2. Go to Custom Recovery and make a full wipe (data, system, cache and dalvick cache) and reboot ur phone in DOWNLOAD MODE
3. Open Odin with ur PC
4. Flash the firmware by PDA/AP button
5. Click START button
6. Wait till the process finish and ur phone will reboot
7. Ur phone will go perfect now i think
8. Good luck

Joku1981 said:
- You cant receive OTA updates or Kies updates (u see it in the screenshot u attached before) how u have the phone now
- I will tell my steps and u can do what u wish later:
1. Download and unrar correct firmware for ur phone -> HERE (I dunno where u download it, anyway if u have it u dont need download it again)
1. Make a Internal Memory backup
2. Go to Custom Recovery and make a full wipe (data, system, cache and dalvick cache) and reboot ur phone in DOWNLOAD MODE
3. Open Odin with ur PC
4. Flash the firmware by PDA/AP button
5. Click START button
6. Wait till the process finish and ur phone will reboot
7. Ur phone will go perfect now i think
8. Good luck
Click to expand...
Click to collapse
OMFG! I completely mis-remembered what I actually did (I can't even believe it!) Thank you for jogging my memory.
Initially I wasn't too keen on the 8-hour ETA for downloading 4.3, so I reflashed stock 4.2 in ODIN. And it was through Kies that I installed 4.3. Obviously in its stock 4.2 state, Kies recognized it as "updatable" and initiated the download/update of 4.3. So the whole unstable installation I had is even more perplexing. Oh well. I'm downloading 4.3 now and will try updating through ODIN. I'll report back. Thanks.

Up and running 4.3 without any issues. Thanks.

can i downgrade from 4.3 to 4.2.2 without any issue, includingwith 4.3 bootloader, using the latest 4.3 modem, the devices it's running great, no problem so far, and yes TPA is for Panama also PBS, CPA, CPW

Nougat w/ working Samsung Pay STEP BY STEP Guide

UPDATE: There is another set of instructions from user derektm. below which make a lot of sense. I didn't have a good understanding of how multi-csc roms functioned before.
This is a step by step guide on how to properly upgrade to Nougat while retaining Samsung Pay functionality. Thanks to user jhunkab for basically pointing everything out in another thread.
NOTES:
***YOU WILL BE WIPING THE PHONE*** UNLESS YOU ALREADY HAVE 6.0.1 DBT INSTALLED W/ SAMSUNG PAY ACTIVATED YOU CAN SKIP TO STEP 17.
STEPS
1. Download SAMFIRM 0.3.5
2. Download Odin 3.12.3
3. Open Samfirm
4. In "region" field enter DBT, press Check Update. You should now get a response for Android 6.0.1. Click Download (decrypt automatically checked)
5. Unzip file once downloaded
6. Backup anything you need on your phone (you will be completely wiping it)
7. Power down phone
8. Boot into flash (while holding down volume down+home button press and hold power button until blue screen appears. press volume up to continue) You should now be at a blue screen that says Downloading
9. Connect phone via micro USB to your computer and open Odin 3.12.3
10. You will now be selecting all files that you previously unzipped from the 6.0.1 DBT firmware. BL+AP+CP+CSC (**NOT HOME_CSC**)
11. Click Options tab in Odin, check Re-Partition
12. Once BL+AP+CP+CSC is loaded into Odin, press Start. Your phone will now begin flashing. Once Odin says it's finished, you can exit out of the program.
13. Wait until phone finishes flashing and boots up (this can take up to 5-10 minutes. be patient you are not in a bootloop)
14. Add WIFI, Google account, setup a fingerprint. don't bother with cloud recovery at this point (google/samsung)
15. Go to apkmirror.com and download Samsung Pay/Samsung Pay Framework from August 4th 2016 release. Install Framework first, then Samsung Pay (you will be prompted by security because they are side loaded)
16. Open Samsung Pay, go through the registration process, and add all your debit/credit cards. UPDATE application through settings>about. Verify that fingerprint authentication is initiating properly by pretending you are purchasing something. If you see the countdown, it's working.
17. Open Samfirm AGAIN
18. in Region enter BTU and press Check Update. It should populate with Android 7 firmware. Click download.
19. Unzip the file and open Odin
20. Repeat the same process for the BTU firmware EXCEPT instead of using CSC file you will now use HOME_CSC. (this is the HOME_CSC from the BTU firmware NOT the DBT one) **MAKE SURE RE-PARTITION IS NOT CHECKED IN OPTIONS TAB**
21. Press Start to flash Nougat BTU firmware.
22. Once it's finished, you are all set. You should now be on Nougat while still retaining your newly setup Samsung Pay from 6.0.1. Open the app to make sure everything is fine. If it goes back to registration or you do not see the Samsung Pay app, you did not flash correctly.
23. Restore your apps/cloud data and go about your life.
Enjoy.

How about directly downloading 7 (BTU) and installing Samsung pay? Will that work?
Edit: Never mind, I am already on DBT for 6.0.1 with everything setup, I will just follow steps from 17 onwards.
Can you elaborate step 23 a little (How-to)?

Step 23 just means restore from whatever backup you had... or don't. However you want to set it up

Thanks for posting these steps. I successfully updated after being on the beta with the DBT CSC code. Not sure if other people have this problem, but I am still unable to load an American Express card. This problem has existed for some time though. Otherwise the steps above seemed to work fine.

Ruturaj001 said:
How about directly downloading 7 (BTU) and installing Samsung pay? Will that work?
Edit: Never mind, I am already on DBT for 6.0.1 with everything setup, I will just follow steps from 17 onwards.
Can you elaborate step 23 a little (How-to)?
Click to expand...
Click to collapse
Were you successful in starting from step 17? I'm in the same boat (DBT and already updated/setup) and will probably try this tonight.

This worked for me as well. I was already on DBT so I started at step 17.

Guys you are perfectly fine skipping to step 17 if you have DBT with samsung pay set up. Just flash BUT with HOME_CSC

oplix said:
Step 23 just means restore from whatever backup you had... or don't. However you want to set it up
Click to expand...
Click to collapse
Thank you for making this thread.
Backup of google account, apps, local data (pictures and all)?
Will this update will work as an OTA update or flashing new ROM?
As Samsung pay app will retain data, I thought it works like OTA update.
Edit: Never mind. I am too dumb. You are flashing DBT first which is resetting everything.
One more question, will I receive OTA updates in future? (for UK or Germany Version)?
HalVllVler said:
Were you successful in starting from step 17? I'm in the same boat (DBT and already updated/setup) and will probably try this tonight.
Click to expand...
Click to collapse
I haven't tried yet but others did. And it seems to works. I just had mac yesterday. Bringing my work laptop to home today to flash update.
sstrunks84 said:
This worked for me as well. I was already on DBT so I started at step 17.
Click to expand...
Click to collapse
oplix said:
Guys you are perfectly fine skipping to step 17 if you have DBT with samsung pay set up. Judy flash BUT with HOME_CSC
Click to expand...
Click to collapse
Thank you sstrunks84 and oplix for letting me know.
Did it reset your phone? Data, accounts, applications?

@Ruturaj001 all data stayed intact, and didn't have to restore or setup anything over again.

sstrunks84 said:
@Ruturaj001 all data stayed intact, and didn't have to restore or setup anything over again.
Click to expand...
Click to collapse
That is great news, thanks. I am planning to flash it tomorrow.
Edit: Flashed it, everything works like a charm.

you saved my day bro...
i did everything right by my own... but the real trick from you is Samsung Pay/Framework apk dated August 4th. I was using most latest version and it didnt help.
Thank you very much.

Hey, everyone, I am having problem with installing theme, is anyone else is having one too?
Edit: I think I had that problem since I went from olympic edition to normal one. Flashed original Germany firmware. Everything works.

Thanks for the great research and directions. Started at Step 17 after already being updated on DBT. All went smoothly and SPay seems intact.

for me, all went well until i flashed nougat and it asked me that samsung pay be updated before it can be used. I gave "Later" to that and that was it, neither does the app open nor can it be updated from any of the stores. So I went ahead and flashed BTU with CSC and Re.Partition checked and decided to give up on Samsung Pay or until they announce it officially.

RamanRJN said:
for me, all went well until i flashed nougat and it asked me that samsung pay be updated before it can be used. I gave "Later" to that and that was it, neither does the app open nor can it be updated from any of the stores. So I went ahead and flashed BTU with CSC and Re.Partition checked and decided to give up on Samsung Pay or until they announce it officially.
Click to expand...
Click to collapse
You need to update it before flashing nougat. Look through the steps again.

Edit 2/23: Updated and reduced steps. Easier now.
BTU firmware is Multi CSC and has DBT CSC.... You guys are all doing it wrong if your setting up Samsung pay on MM and then flashing the HOME_CSC to prevent full wipe....
Proper way:
1) Flash MM DBT first using AP, BL, CP, and CSC. (The only reason for this is to set the phone to DBT CSC.) Allow phone to boot, go back to download mode (dont have to set anything up)
2) Flash BTU Nougat using AP, BL, CP, and CSC. (NOT Home_CSC).
Now you have clean, factory and OTA friendly Nougat BTU with DBT set as CSC (since BTU is multi csc, it doesnt change your csc from DBT, even using the normal CSC file for full wipe.) Set phone up and proceed....
{
"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"
}
3) Install this SPay APK: https://drive.google.com/file/d/0B0Z0JzkNunQ5Z0pkOFhFbUNaLVk/view?usp=sharing It is untouched and was put on my phone by the SPay app itsself when it updated. The versions on APK mirror for some reason are different and do not work correctly. They are from an incorrect region or something.
5) Now go into Samsung Pay, add all your cards, and update to latest version, if there is one. Note: Samsung pay may fail the first startup and complain about a server connection issue. Force close the app and start over. Its normal.
6) Done.
I have received additional updates through the Samsung pay app since I set this up several weeks ago. So updates are not an issue and you will always have latest version.

Your instructions are all good. Didn't know about the multi-csc

oplix said:
Hi working instructions have been posted please do not hijack
Click to expand...
Click to collapse
Its not hijacking its better information. This is a community to help each other and if the method can be improved then I am sure it is welcomed by the other members. :good:

derektm. said:
Its not hijacking its better information. This is a community to help each other and if the method can be improved then I am sure it is welcomed by the other members. :good:
Click to expand...
Click to collapse
This is not "better" information. The correct procedure is posted already. Do not confuse people. Someone was confused and you decided to add additional conflicting information.

oplix said:
This is not "better" information. The correct procedure is posted already. Do not confuse people. Someone was confused and you decided to add additional conflicting information.
Click to expand...
Click to collapse
Don´t be like that, there's no correct procedure in phone hacking world, his instructions seems clearer and also make more sense since you get a just wiped Nougat build in the phone and not an updated one.
Welcome to the internet, if you don't like listening to others you shouldn't be here.

[SM-G955N] Samsung Galaxy S8+ Korean 128GB + 6GB Support Thread

{
"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 was just a bit confused with the sheer amount of small threads that try to answer questions regarding the Korean variant of our beloved device with consistent questions and answers floating around, so this guide aims to consolidate those threads as it seems like we need a unified thread for this variant.
System Specs provided by @murtaza02
Model Number: SM-G955N
Country of Production: South Korea
Carriers: LG U+, SK Telecom, KT
2G: 900, 1800, 1900 MHz
3G (UMTS/HSPA): 850, 1900, 2100 MHz
4G (LTE): B1, B2, B3, B4, B5, B7, B8, B12, B13, B17, B18, B19, B20, B25, B26, B28, B38, B39, B40, B41, B46
SoC: Samsung Exynos 9 Octa (8895)
RAM/Internal: 4GB / 64GB or 6GB / 128GB

Flashing a ROM​
Yes, you can actually flash any ROM on your device! ROM developers should be informed to use the model number from TWRP to determine what device you are running, to distinguish between the S8 and the S8+.
Our device reports back "dream2lte" in TWRP but the actual model number of our device is "dream2lteks" with a model number of SM-G955N.
Do not flash a ROM that edited the build.prop for the SM-G955N without full system prop modifications implemented, or else Magisk Hide would NOT work.
The steps are simple to flash a custom SM-G955N ROM but must be followed to the T:
1. You've got to trip KNOX, which will void the warranty! But we imported our phones, so who we kidding? You've got no warranty anyways!
2. Once you spent a few heartfelt minutes thinking about the pros and cons, you will have to flash @jesec's TWRP on your device following ALL instructions of his guide, including flashing the decrypt ZIP. https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
3. Pick your ROM, if the ROM requests you to flash BL and CP, you CANNOT flash the G955F versions, as we have a completely different bootloader!!! If they have the G955N variants, then feel free to update it if you want, as this step is NOT mandatory. It IS safe to flash a 955F kernel on your 955N!
4. Place the ROM zip into your MicroSD and the CSC Flasher, but do NOT use TWRP to transfer these files. MTP will stop working Midway (all variants of the S8+, roughly at 1.5gb) so I suggest doing it before going to recovery, or if it's too late, just use a microSD adapter and add it in there. Recommended drive format: exFAT.
5. Flash the ROM as you would from TWRP, depending on your ROM, it may have a debloat Aroma menu. If there's a way to update the BL and CP inside the Aroma menu, DO NOT. Some ROMs ask if you would like to flash a CSC (that you're not interested in), so pick DBT (Germany) unbranded.
6. After flashing the ROM, depending on your ROM, you may need to reboot back into recovery using Reboot -> Recovery to avoid the Device or Resource is Busy error in TWRP...to flash the CSC package.
7. It is highly recommended to use unbranded CSCs but it is not 100%. If you are in Canada like me, the CSC package for Rogers Wireless (RWC) under XAC causes a ton of keyboard force closes and random reboots. While the XAC unbranded default CSC runs better but still has keyboard force closes. There may be an error with mounting and unmounting /preload, a non existent partition on our variant...which is perfectly okay!
8. Ensure that you remember the above steps when you're dirty flashing a ROM update, because if you forget to flash the same CSC from the previous flash, you will lose CSC benefits like VoLTE, LTE-A and wifi calling until you factory reset!
9. If you're looking for root, you MUST reflash Magisk v12+, or else you won't get any MagiskSU green flags. Seems to be happening mostly on our Korean variant.
10. You're done!

Frequently Asked Questions (Buyer's Questions)​
Q: I'm planning to buy this phone but not planning to root it, what kind of bloat are there.?
Custom SK Telecom Bootanimation with sound
One full folder of Korean applications from the carrier, including Samsung bloat that are all Korean-region bounded.
An out of place second carrier label in the lock screen (bottom left)
Settings has two extra options, T roaming and T security. You can get rid of the T security shortcut in Settings by disabling the T membership app using Package Disabler Pro (Samsung) on Play Store. T roaming cannot be removed. Depending on your device's original carrier, you may get the KT service provider entry.
Camera can't disable shutter noise. Korean law.
Bootloader is Korean. Unchangeable.
Q: Are there any carrier markings on the device?
Yes, but really unnoticeable. There are no FCC markings at the back of the phone but just a line of text, and at the end of that line of text just says SKT. It is as natural as a phone that tells you where it was manufactured.
Q: Can I Odin a stock SM-G955F firmware or CSC file?
No, you can't flash anything SM-G955F in any slot of Odin. Doing so will just fail or secure flash error.
Q: Can I use a CSC from a company that sells S8+'s with Qualcomm on my Exynos device?
Yes, but it may need some testing. In Canada, if you have the proper CSC, I confirmed to get VoLTE and Wifi Calling after flashing the RWC CSC. But the XAC CSC may not enable Wifi Calling but will enable VoLTE. LTE-A is almost supported on all CSCs, so you don't have to worry about that.
Q: If I flash an SM-G955F ROM on my device, will it affect my RAM or storage?
No. You will retain 128GB and 6GB RAM on any ROM.
Q: Can I disable bloat apps without rooting?
Yes, but you may have to use a paid app, linked here: https://play.google.com/store/apps/details?id=com.ospolice.packagedisablerpro&hl=en
Search for "SKT" and it is safe to disable them all. Disabling T membership as stated above will disable the Settings shortcut to it to, but T roaming will not disappear.

YouTube Videos (Miscellanous)​
He says "Chinese" but he later rectified it in the comments.

Reserved 4 ?

Thanks for the amazing guide. All working. Btw I saw that latest batstock rom is version 1 not 1.1?
My device now shows that its 955f is that OK? I installed the ilo israel csc so how can I update the rom with that csc without loosing data? Thanks!

There was a system update today. Anyone know the changes?
Sent from my SM-G955N using Tapatalk

BTW I did not reflash magisk, just downloaded magisk manager from play store and install from there.

bidav1 said:
Thanks for the amazing guide. All working. Btw I saw that latest batstock rom is version 1 not 1.1?
My device now shows that its 955f is that OK? I installed the ilo israel csc so how can I update the rom with that csc without loosing data? Thanks!
Click to expand...
Click to collapse
Yeah I'm in the testers chat on the Telegram link but the model number is just a build.prop check.
As long as you update the ROM with the CSC before booting up, you won't lose any data.
bidav1 said:
BTW I did not reflash magisk, just downloaded magisk manager from play store and install from there.
Click to expand...
Click to collapse
Were you able to obtain root? Depending on your set up, you may not have any root like what happened to me, so I had to reflash. Also I tried a no root option from BatStock and if it doesn't patch your boot image, then you'd be stuck on the Samsung logo indefinitely.

forsberg78 said:
There was a system update today. Anyone know the changes?
Click to expand...
Click to collapse
Do you know the system update's binary letters? Or just post a screenshot.

nicholaschum said:
Yeah I'm in the testers chat on the Telegram link but the model number is just a build.prop check.
As long as you update the ROM with the CSC before booting up, you won't lose any data.
Were you able to obtain root? Depending on your set up, you may not have any root like what happened to me, so I had to reflash. Also I tried a no root option from BatStock and if it doesn't patch your boot image, then you'd be stuck on the Samsung logo indefinitely.
Click to expand...
Click to collapse
I was able to fully obtain rom. what I did is after the phone booted up (after the rom installation), I downloaded magisk manager from app store, then clicked on install inside the manager. when the phone booted up afterwards i was fully rooted. also checked with root info and various root apps.
just one thing is not clear to me. now i'm on batstock 1.0 with stock kernel and untouched bl and modem. and with ILO csc from the csc tool.
now when i want to upgrade to batstock 1.1, say a dirty flash to keep data. what are the steps?
1. copy the zip file of the rom and the zip file of the csc tool to sd
2. reboot to twrp, install the rom file dirty flash and not to reboot
3. before reboot, install the csc zip file in twrp
4. reboot
did i get that alright?
thank you !

bidav1 said:
I was able to fully obtain rom. what I did is after the phone booted up (after the rom installation), I downloaded magisk manager from app store, then clicked on install inside the manager. when the phone booted up afterwards i was fully rooted. also checked with root info and various root apps.
just one thing is not clear to me. now i'm on batstock 1.0 with stock kernel and untouched bl and modem. and with ILO csc from the csc tool.
now when i want to upgrade to batstock 1.1, say a dirty flash to keep data. what are the steps?
1. copy the zip file of the rom and the zip file of the csc tool to sd
2. reboot to twrp, install the rom file dirty flash and not to reboot
3. before reboot, install the csc zip file in twrp
4. reboot
did i get that alright?
thank you !
Click to expand...
Click to collapse
Yes that's correct, because a dirty flash is going to wipe the CSC, since the CSC is located in the /system folder, the ROM upgrade will wipe system and you lose your CSC, but the preferences are stored in /data, so your procedure is correct. If you get any resource is busy errors in aroma, reboot recovery before flashing the CSC

thanks ! any news about the update that rolled out today for unrooted devices?

Thanks for the thread mate.. I was also thinking of making this up...
I have Korean model s8 + kt 64gb.. I am on CarHD 1.3.. Everything is working perfectly.. Before i tried flashing renovate rom 2 bit every time i was struck at samsung logo.. I tried flashing everything like magshik .. Ok thats not the question...I study in china and brought Korean KT version online
I yesterday broke the screen of my phone..now can anyone suggest me what should i do. Can i go to service center and ask them to repair the phone... I just want that i get replaced the screen and get my water resistant back..
My one friend called Samsung care here in china to enquire about the screen replacement and they said that if touch is working then it will cost me around 120 us doller and if touch is not working then cost me 250 us doller....
Can anybody can give me some ideas or suggestions please? Thanks in advance

nicholaschum said:
Do you know the system update's binary letters? Or just post a screenshot.
Click to expand...
Click to collapse
This is the version now
Sent from my SM-G955N using Tapatalk

forsberg78 said:
This is the version now
Click to expand...
Click to collapse
Bluetooth connectivity fixes and some stability features

Just be sure to look at the last 4 characters to see what the new version code is, in this case, AQEB.

DireWolf619 said:
Thanks for the thread mate.. I was also thinking of making this up...
I have Korean model s8 + kt 64gb.. I am on CarHD 1.3.. Everything is working perfectly.. Before i tried flashing renovate rom 2 bit every time i was struck at samsung logo.. I tried flashing everything like magshik .. Ok thats not the question...I study in china and brought Korean KT version online
I yesterday broke the screen of my phone..now can anyone suggest me what should i do. Can i go to service center and ask them to repair the phone... I just want that i get replaced the screen and get my water resistant back..
My one friend called Samsung care here in china to enquire about the screen replacement and they said that if touch is working then it will cost me around 120 us doller and if touch is not working then cost me 250 us doller....
Can anybody can give me some ideas or suggestions please? Thanks in advance
Click to expand...
Click to collapse
The reason it got stuck on the Samsung logo was because, as I listed in my main threads, they used the wrong way of detecting model, so it was not installing a kernel for your device and you were booting with no kernel.
Unfortunately, that's what happens if you import a device. But I'm not so sure if Samsung China would be able to help you since your device is not from China. Maybe if you go to a small shop, you could inquire prices there, or watch a video and buy a new screen for yourself maybe.

nicholaschum said:
The reason it got stuck on the Samsung logo was because, as I listed in my main threads, they used the wrong way of detecting model, so it was not installing a kernel for your device and you were booting with no kernel.
Unfortunately, that's what happens if you import a device. But I'm not so sure if Samsung China would be able to help you since your device is not from China. Maybe if you go to a small shop, you could inquire prices there, or watch a video and buy a new screen for yourself maybe.
Click to expand...
Click to collapse
Yeah i will go to service center tomorrow...i am afraid to go to small shop because i think they won't be able to provide water resistant after opening the phone...

DireWolf619 said:
Yeah i will go to service center tomorrow...i am afraid to go to small shop because i think they won't be able to provide water resistant after opening the phone...
Click to expand...
Click to collapse
As far as I know with my experience of small shops in Hong Kong, they have kits to apply back on the device for waterproofing.

Advice on S7e Firmware from UAE to BTU

Hopefully you guys might take a mo whilst we are in lockdown to just give me a few pointers please
Original S7e screen bust 6 months ago so i purchased a rekon S7e from Amazon Uk, all seemed well and i re applied my backups from my old phone to the replacement phone, after a few days of getting the phone the same as the original i realised the phone had a UAE csc, annoying at best but as i needed a working phone i kind of let it slide and carried on using the phone, apart from Samsung Health showing UAE adverts and pay showing UAE info the phone seemed ok.... actually add to that it has recieved no updates since Oct 2019 either, i have tried all ways to get security updates and phone os updates but to no avail, it just says it is up to date which i know is wrong as security updates have been released since last year
Now in lockdown and its raining its time to hopefully get the thing back on track, could you guys advise on what exact files i need so i dont brick or trip knox please
dev mode no issues
usb config no isuues
i have grabbed the latest UAE files
i have grabbed the latest UK BTU files
odin installed
do i need to mix and match files from both downloads ? just use the BTU files ?? if you guys could please give me some info on which set of files i need to load into odin it would be much appreciated
if you need csc pda numbers no probs just shout, i have never messed with android firmware before, all i want to do is get a Uk updating phone again
Thanks if you can help and stay safe

norsane said:
Hopefully you guys might take a mo whilst we are in lockdown to just give me a few pointers please
Original S7e screen bust 6 months ago so i purchased a rekon S7e from Amazon Uk, all seemed well and i re applied my backups from my old phone to the replacement phone, after a few days of getting the phone the same as the original i realised the phone had a UAE csc, annoying at best but as i needed a working phone i kind of let it slide and carried on using the phone, apart from Samsung Health showing UAE adverts and pay showing UAE info the phone seemed ok.... actually add to that it has recieved no updates since Oct 2019 either, i have tried all ways to get security updates and phone os updates but to no avail, it just says it is up to date which i know is wrong as security updates have been released since last year
Now in lockdown and its raining its time to hopefully get the thing back on track, could you guys advise on what exact files i need so i dont brick or trip knox please
dev mode no issues
usb config no isuues
i have grabbed the latest UAE files
i have grabbed the latest UK BTU files
odin installed
do i need to mix and match files from both downloads ? just use the BTU files ?? if you guys could please give me some info on which set of files i need to load into odin it would be much appreciated
if you need csc pda numbers no probs just shout, i have never messed with android firmware before, all i want to do is get a Uk updating phone again
Thanks if you can help and stay safe
Click to expand...
Click to collapse
Well, there is a saying which goes like this ;
"Don't try to fix which isn't broken"
You can make calls.. your phone works in all aspects.
Except that you dislike some uae built-in apps
Just disable those apps..
But if you have decided you want to jump in the "pseudo effect of update feels good" ship .. then i can't stop you.. its ur phone
But trust me you WON'T WANT TO HAVE LATEST UPDATES because i did what you want to do and now suffer
Okay but if you want to flash latest rom for your current country follow these steps.
1. See which rom/firmware is currently installed in your phone .. i.e : build numbers , and copy paste them here and also note them down so you can remember..
2. Since you want to get in this ship you need to ENABLE OEM UNLOCK AND USB DEBUGGING IN DEVELOPER OPTIONS, just to stay safe ** i will tell you why later **
3. Download latest odin from here i.e 3.14.4 https://technastic.com/odin-download-samsung-latest-all-versions/
4. Download latest firmware for your current country from here :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/BTU/
(if it is uk then there are 2 csc for uk .. btu and xeu)
5. *Important* make a backup of everything in your phone, then turn it off and go in recovery mode (by holding vol up + home + power buttons while its off)
Factory data reset and wipe cache.. then turn off phone..
6. Then put your phone in download mode while its off (by holding vol down + home + power buttons)
7. Run odin as admin on your pc, extract the firmware file you downloaded earlier.. it will give 4 files .. BL , AP , CP , CSC..
Select correct files corresponding to the boxes in odin..
*In odin options don't select any option other then F.reset time*
*USE CSC (NOT HOME CSC) IN CSC BOX..
8. Connect your phone to pc while in download mode (odin should detect the port.. if not install samsung drivers or smart switch for pc)
9. Press on start button to begin flashing.. once odin says success unplug your phone .. it will still be in download mode .. so hold vol down + home + power button to force reboot (once phone screen goes black immediately change from holding vol down to vol up + home + power .. this will put you in recovery mode.. do a factory data wipe + clear cache, then reboot phone)
**WARNING : DON'T UNPLUG YOUR PHONE WHILE ODIN IS FLASHING OR BEFORE IT SAYS SUCCESS ! **
10. Configure your settings and restore your data .. you should have btu csc now
*IMPORTANT*
*FLASHING A SECOND HAND BOUGHT PHONE (WHICH COULD BE PATCHED/MODIFIED BY A HARDWARE BOX) THROUGH ODIN CAN MAKE IT A HARD BRICK BUT IF OEM UNLOCK IS ENABLED YOU CAN FIX IT EASILY BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!*
*FLASHING TO LATEST FIRMWARE WILL CAUSE BOOTLOADER VERSION UPDATE AND YOU WILL BE STUCK WITH THAT BOOTLOADER (SINCE YOU CANNOT DOWNGRADE/FLASH ANY OTHER ROM WITH LOWER BOOTLOADER NUMBER OR EVEN TROUBLESHOOT USING A COMBINATION ROM*
*LATEST FIRMWARES HAVE SERIOUS PERFORMANCE/BATTERY ISSUES FROM MY EXPERIENCE AND YOU CAN DOWNGRADE ONCE YOU UPDATE TO A HIGHER BOOTLOADER NUMBER ! TRY EVERYTHING ON YOUR OWN RISK ! *
Sent from my S7 Edge using XDA Labs

shah22 said:
)
*IMPORTANT*
*FLASHING A SECOND HAND BOUGHT PHONE (WHICH COULD BE PATCHED/MODIFIED BY A HARDWARE BOX) THROUGH ODIN CAN MAKE IT A HARD BRICK BUT IF OEM UNLOCK IS ENABLED YOU CAN FIX IT EASILY BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!*
*FLASHING TO LATEST FIRMWARE WILL CAUSE BOOTLOADER VERSION UPDATE AND YOU WILL BE STUCK WITH THAT BOOTLOADER (SINCE YOU CANNOT DOWNGRADE/FLASH ANY OTHER ROM WITH LOWER BOOTLOADER NUMBER OR EVEN TROUBLESHOOT USING A COMBINATION ROM*
*LATEST FIRMWARE HAVE SERIOUS PERFORMANCE/BATTERY ISSUES FROM MY EXPERIENCE, TRY EVERYTHING ON YOUR OWN RISK! *
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Thanks Shah
Yup it definately is a second hand phone, the rear o2 blood sensor has a very dim red light on all the time, i read a software update cured that ?? which is another reason i wanted to try and get the phone to update
what does concern me, how can i tell if the phone has patched certs or IMEI ?? is there a way of finding this out ?? that does appear to be the only thing that at present i cannot find out
If any of this helps i would appreciate you taking a look
product name hero2ltexx
manufacture date 20160506
knox warranty bit 0x0
product code SM-G935FZSLXSG
PDA G935FXXS6ESH5
CSC G935FOJV6ESH5
BASEBAND G935FXXU6ASG1
BOOTLOADER G935FXXS6ESH5

norsane said:
Thanks Shah
Yup it definately is a second hand phone, the rear o2 blood sensor has a very dim red light on all the time, i read a software update cured that ?? which is another reason i wanted to try and get the phone to update
what does concern me, how can i tell if the phone has patched certs or IMEI ?? is there a way of finding this out ?? that does appear to be the only thing that at present i cannot find out
If any of this helps i would appreciate you taking a look
product name hero2ltexx
manufacture date 20160506
knox warranty bit 0x0
product code SM-G935FZSLXSG
PDA G935FXXS6ESH5
CSC G935FOJV6ESH5
BASEBAND G935FXXU6ASG1
BOOTLOADER G935FXXS6ESH5
Click to expand...
Click to collapse
Install phone info app.. send the csc and firmware tab screenshot..
Then go in download mode and send a pic of it too..
Edit : i am on XSG too.. but i never had any sensor light bug ever !
Sent from my S7 Edge using XDA Labs

shah22 said:
Install phone info app.. send the csc and firmware tab screenshot..
Then go in download mode and send a pic of it too..
Edit : i am on XSG too.. but i never had any sensor light bug ever !
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
How do i send a pic of Download mode, if the phones in download mode does it still capture ??

Product Code: SM-G935FZSLXSG
PDA: G935FXXS6ESH5
CSC: G935FOJV6ESH5
Baseband: G935FXXU6ASG1
Bootloader: G935FXXS6ESH5
Download option
Current Binary : Samsung official
System status : Official
FRP Lock : Off
Secure Download : Enabled
Warranty void : 0 (0x0000)
RP SWREV : B:6 K:4 S:5

Hey I need some help too, surprisingly I'm also in UAE I'm on the black diamond ROM running Moro kernel, my only problem is the sim card isn't working how do i make this work

norsane said:
Product Code: SM-G935FZSLXSG
PDA: G935FXXS6ESH5
CSC: G935FOJV6ESH5
Baseband: G935FXXU6ASG1
Bootloader: G935FXXS6ESH5
Download option
Current Binary : Samsung official
System status : Official
FRP Lock : Off
Secure Download : Enabled
Warranty void : 0 (0x0000)
RP SWREV : B:6 K:4 S:5
Click to expand...
Click to collapse
Ok it looks un-tempered.. you can try flashing btu
Alandc said:
Hey I need some help too, surprisingly I'm also in UAE I'm on the black diamond ROM running Moro kernel, my only problem is the sim card isn't working how do i make this work
Click to expand...
Click to collapse
Do other sim cards work ? Is phone's imei displaying correctly ?
Sent from my S7 Edge using XDA Labs

shah22 said:
Well, there is a saying which goes like this ;
"Don't try to fix which isn't broken"
You can make calls.. your phone works in all aspects.
Except that you dislike some uae built-in apps
Just disable those apps..
But if you have decided you want to jump in the "pseudo effect of update feels good" ship .. then i can't stop you.. its ur phone
But trust me you WON'T WANT TO HAVE LATEST UPDATES because i did what you want to do and now suffer
Okay but if you want to flash latest rom for your current country follow these steps.
1. See which rom/firmware is currently installed in your phone .. i.e : build numbers , and copy paste them here and also note them down so you can remember..
2. Since you want to get in this ship you need to ENABLE OEM UNLOCK AND USB DEBUGGING IN DEVELOPER OPTIONS, just to stay safe ** i will tell you why later **
3. Download latest odin from here i.e 3.14.4 https://technastic.com/odin-download-samsung-latest-all-versions/
4. Download latest firmware for your current country from here :
https://www.sammobile.com/samsung/galaxy-s7-edge/firmware/SM-G935F/BTU/
(if it is uk then there are 2 csc for uk .. btu and xeu)
5. *Important* make a backup of everything in your phone, then turn it off and go in recovery mode (by holding vol up + home + power buttons while its off)
Factory data reset and wipe cache.. then turn off phone..
6. Then put your phone in download mode while its off (by holding vol down + home + power buttons)
7. Run odin as admin on your pc, extract the firmware file you downloaded earlier.. it will give 4 files .. BL , AP , CP , CSC..
Select correct files corresponding to the boxes in odin..
*In odin options don't select any option other then F.reset time*
*USE CSC (NOT HOME CSC) IN CSC BOX..
8. Connect your phone to pc while in download mode (odin should detect the port.. if not install samsung drivers or smart switch for pc)
9. Press on start button to begin flashing.. once odin says success unplug your phone .. it will still be in download mode .. so hold vol down + home + power button to force reboot (once phone screen goes black immediately change from holding vol down to vol up + home + power .. this will put you in recovery mode.. do a factory data wipe + clear cache, then reboot phone)
**WARNING : DON'T UNPLUG YOUR PHONE WHILE ODIN IS FLASHING OR BEFORE IT SAYS SUCCESS ! **
10. Configure your settings and restore your data .. you should have btu csc now
*IMPORTANT*
*FLASHING A SECOND HAND BOUGHT PHONE (WHICH COULD BE PATCHED/MODIFIED BY A HARDWARE BOX) THROUGH ODIN CAN MAKE IT A HARD BRICK BUT IF OEM UNLOCK IS ENABLED YOU CAN FIX IT EASILY BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!*
*FLASHING TO LATEST FIRMWARE WILL CAUSE BOOTLOADER VERSION UPDATE AND YOU WILL BE STUCK WITH THAT BOOTLOADER (SINCE YOU CANNOT DOWNGRADE/FLASH ANY OTHER ROM WITH LOWER BOOTLOADER NUMBER OR EVEN TROUBLESHOOT USING A COMBINATION ROM*
*LATEST FIRMWARES HAVE SERIOUS PERFORMANCE/BATTERY ISSUES FROM MY EXPERIENCE AND YOU CAN DOWNGRADE ONCE YOU UPDATE TO A HIGHER BOOTLOADER NUMBER ! TRY EVERYTHING ON YOUR OWN RISK ! *
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Can you explain that a little further?
"BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!"
I have an SM-G935FD Galaxy S7 edge phone from Malaysia. I have it in Greece and as soon as I got it in my hands I let it go all the updates until Android 8. And then installed a custom rom. Since then I can't make or receive any calls and sometimes it recognize my sim card (Cosmote) and sometimes it doesn't. Even the times that recognize my network operator I still can't make or receive calls. And of course I don't have any data.
What I have done:
1. Flashed original Malaysian and Indonesian firmware with no luck
2. Activated and deactivated volte
3. Tried different sim card
4. Flashed original Greek firmware (which I thought it would solve my problem but nothing). At root files it has all the network operators enebled as normal.
5. Tried several custom ROMs from Android 7 to 10. The only one that had some result was Floyd 10. The result was that for a minute I had data and couple of sms came from missed calls. But then again nothing. And since the first time I installed it, when I reinstalled Floyd not even for a minute.
6. Tampered customer.xml file for csc folder as a friend from Floyd rom thread suggested but still nothing
7. With a different sim from different provider I have data almost all the time but no calls at all
do all that has something to do with what you stated above? because it pretty much looks like i ve lost network
Thanks

achkap said:
Can you explain that a little further?
"BUT IF SOME CERTIFICATES/IMEI WAS PATCHED THEN YOU WILL LOSE NETWORK !!"
I have an SM-G935FD Galaxy S7 edge phone from Malaysia. I have it in Greece and as soon as I got it in my hands I let it go all the updates until Android 8. And then installed a custom rom. Since then I can't make or receive any calls and sometimes it recognize my sim card (Cosmote) and sometimes it doesn't. Even the times that recognize my network operator I still can't make or receive calls. And of course I don't have any data.
What I have done:
1. Flashed original Malaysian and Indonesian firmware with no luck
2. Activated and deactivated volte
3. Tried different sim card
4. Flashed original Greek firmware (which I thought it would solve my problem but nothing). At root files it has all the network operators enebled as normal.
5. Tried several custom ROMs from Android 7 to 10. The only one that had some result was Floyd 10. The result was that for a minute I had data and couple of sms came from missed calls. But then again nothing. And since the first time I installed it, when I reinstalled Floyd not even for a minute.
6. Tampered customer.xml file for csc folder as a friend from Floyd rom thread suggested but still nothing
7. With a different sim from different provider I have data almost all the time but no calls at all
do all that has something to do with what you stated above? because it pretty much looks like i ve lost network
Thanks
Click to expand...
Click to collapse
If you bought it second hand then yes, it certificates/imei may have been patched using a hardware box and reflashing or even factory formatting results in network loss.. it may only be fixed by a box (or a local repair shop having box)
The other reason can be that your efs partition got corrupted and if you don't have a backup of efs before you rooted/customized your phone then ur out of luck mate..
Even if you had efs backup you would have been still out of luck because you made the mistake of "updating" to latest binary firmware and we need combination rom to fully repair network issues (and combination roms are not being available/leaked online for latest binaries)
Also a box can fix this too (or a local repair shop having box)
Can you tell if your imei is displayed correctly and if its different from the one printed on the phone's back or phone's packaging ? (If you got any)
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
If you bought it second hand then yes, it certificates/imei may have been patched using a hardware box and reflashing or even factory formatting results in network loss.. it may only be fixed by a box (or a local repair shop having box)
The other reason can be that your efs partition got corrupted and if you don't have a backup of efs before you rooted/customized your phone then ur out of luck mate..
Even if you had efs backup you would have been still out of luck because you made the mistake of "updating" to latest binary firmware and we need combination rom to fully repair network issues (and combination roms are not being available/leaked online for latest binaries)
Also a box can fix this too (or a local repair shop having box)
Can you tell if your imei is displayed correctly and if its different from the one printed on the phone's back or phone's packaging ? (If you got any)
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Both my IMEI and efs are alright. I'm trying all this time to find a way to patch the certificates because on the one hand I don't have 120euros top but z3x and in the other I live on an island in Greece where there aren't any Samsung repair shops. I found halabtech tool and I patched certificates with that but I'm not sure that it is ok for my phone. Anyway network didn't came back after that.
Anyway after I saw your post I searched a lot and in found done threads that say that only at Android 6 the certificates can be patched. Any help would be appreciated...

achkap said:
Both my IMEI and efs are alright. I'm trying all this time to find a way to patch the certificates because on the one hand I don't have 120euros top but z3x and in the other I live on an island in Greece where there aren't any Samsung repair shops. I found halabtech tool and I patched certificates with that but I'm not sure that it is ok for my phone. Anyway network didn't came back after that.
Anyway after I saw your post I searched a lot and in found done threads that say that only at Android 6 the certificates can be patched. Any help would be appreciated...
Click to expand...
Click to collapse
If you need to patch certs then your imei's aren't alright lol, your imei's are either changed or blacklisted which is causing the issues, and yes downgrading to android 6 is necessary for patching certs.. but i think you need a hardware box for that..
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
If you need to patch certs then your imei's aren't alright lol, your imei's are either changed or blacklisted which is causing the issues, and yes downgrading to android 6 is necessary for patching certs.. but i think you need a hardware box for that..
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
So if the IMEI is the same and not blacklisted then there is no need for the patch? I bought the phone from a friend of mine, who he didn't do anything to the phone. Not even the updates. When I took it I let it update to Android 8, flashed twrp and then an Android 10 rom. A process I have done a million times until now, just not on this phone. At no point I lost the IMEI. So although I don't have the packaging I'm pretty sure that it is the same. I checked and it is not blacklisted either.
Any idea what could be then?
And again thank you for your time

achkap said:
So if the IMEI is the same and not blacklisted then there is no need for the patch? I bought the phone from a friend of mine, who he didn't do anything to the phone. Not even the updates. When I took it I let it update to Android 8, flashed twrp and then an Android 10 rom. A process I have done a million times until now. At any point I lost the IMEI. So although I don't have the box I'm pretty sure that it is the same. I checked and it is not blacklisted either.
Any idea what could be then?
And again thank you for your time
Click to expand...
Click to collapse
Yes, you can't verify that imei's are the same since you don't have original phone packaging, ask your friend to confirm..
And if imei's are okay then its efs bug/corruption, which i told in above post, you should have done backup before modifying phone.. but even if you got backup you cannot restore efs because you are on latest binaries and you need latest combination roms for successfully repairing efs, which sadly aren't available, so yeah sorry but hate to say can't guide further
Thats why i ask peeps to NOT get on latest firmware train lol and ALWAYS make efs backup before doing anything to your phone !
Btw, can you tell me which is the current firmware's build number ?
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Yes, you can't verify that imei's are the same since you don't have original phone packaging, ask your friend to confirm..
And if imei's are okay then its efs bug/corruption, which i told in above post, you should have done backup before modifying phone.. but even if you got backup you cannot restore efs because you are on latest binaries and you need latest combination roms for successfully repairing efs, which sadly aren't available, so yeah sorry but hate to say can't guide further
Thats why i ask peeps to NOT get on latest firmware train lol and ALWAYS make efs backup before doing anything to your phone !
Btw, can you tell me which is the current firmware's build number ?
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
So i dialed *#06# and it shows both my imei and sn. This isn't a sign that everything is ok? Is there a way to test if my efs is corrupted?
I'm sending you screenshots of about phone to see my build and android version.
View attachment 5025621
{
"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"
}
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk

achkap said:
So i dialed *#06# and it shows both my imei and sn. This isn't a sign that everything is ok? Is there a way to test if my efs is corrupted?
I'm sending you screenshots of about phone to see my build and android version.
View attachment 5025621View attachment 5025625
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
And the thing that troubles me most is that with a SIM card from a different provider I have data connection but no calls. Would that happen with corrupted efs?
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk

achkap said:
And the thing that troubles me most is that with a SIM card from a different provider I have data connection but no calls. Would that happen with corrupted efs?
Στάλθηκε από το SM-G935F μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
So yeah imei may still be okay but you can't verify that this wasn't changed or such, by the looks of it its either a changed imei which lost its certs when reflashing..
Or a bugged/corrupted efs which isn't letting you connect to the networks.. and it can only be resolved as i said by combination rom and efs backup..
Since your binary is the latest 8th, there is no combination rom available for it
Btw you could try this guide here .. who knows it may work lol..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
So yeah imei may still be okay but you can't verify that this wasn't changed or such, by the looks of it its either a changed imei which lost its certs when reflashing..
Or a bugged/corrupted efs which isn't letting you connect to the networks.. and it can only be resolved as i said by combination rom and efs backup..
Since your binary is the latest 8th, there is no combination rom available for it
Btw you could try this guide here .. who knows it may work lol..
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Is there a way to downgrade to Android 7?

achkap said:
Is there a way to downgrade to Android 7?
Click to expand...
Click to collapse
Nope, not by conventional means.. a hardware box .. possibly but still no guarantee..
Thats why one should always research before immediately hopping in the "latest is best" train.. because often then not, it isn't the best if not the worst
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Nope, not by conventional means.. a hardware box .. possibly but still no guarantee..
Thats why one should always research before immediately hopping in the "latest is best" train.. because often then not, it isn't the best if not the worst
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
I'm flashing my phones since 2012. Never I had a problem like that. That's why I hurried to change rom. Anyway. Thank you for your help. You clarified several things for me. I think I'm going to try the above method you told me. The phone isn't usable anyway....
Thanks again

Failing installing TWRP with Only Official Released Binaries Allowed

Hey.
I unlocked the bootloader (unlock oem under developer options, and with vol up + down when plugging the usb cable in + vol up for 5sec)
When I try to flash the according TWRP tar I get an error on my tab5se, it says "Only official released binaries are allowed to be flashed(recovery)
And Odin says "Fail! (Auth)"
I got no clue where to go from here.
I want to install Lineage 17.1 onto the Tab5se.
{
"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"
}

lvlanson said:
When I try to flash the according TWRP tar I get an error on my tab5se, it says "Only official released binaries are allowed to be flashed(recovery)
Click to expand...
Click to collapse
LuK1337's Instructions need to be followed exactly, dont add anything, dont skip anything (Dont wipe anything unless listed). Did you flash the VBMeta image?

OhioYJ said:
LuK1337's Instructions need to be followed exactly, dont add anything, dont skip anything (Dont wipe anything unless listed). Did you flash the VBMeta image?
Click to expand...
Click to collapse
I was following faulty instructions. I came across this post a little later and added the VBMeta after I managed to install TWRP. Weirdly I did work and I could manage to install Lineage OS17.1 by now.
Thanks for your assistance

lvlanson said:
I was following faulty instructions. I came across this post a little later and added the VBMeta after I managed to install TWRP. Weirdly I did work and I could manage to install Lineage OS17.1 by now.
Thanks for your assistance
Click to expand...
Click to collapse
When that happens it means you skipped a step, usually this means you didnt flash something and boot system to verify OEM unlocking is still on, or atleast thats my experience.

I'm having the same message, but in an early stage. I can't even flash vbmeta.tar. Any idea how to solve this?

svierkant said:
I'm having the same message, but in an early stage. I can't even flash vbmeta.tar. Any idea how to solve this?
Click to expand...
Click to collapse
have you found a solution?

kaho_tam said:
have you found a solution?
Click to expand...
Click to collapse
i need some help , i currently have an s8 everytime i try to flash twrp i get an error saying "only official binaries are allowed to be flashed (recovery) .i downloaded a new stock firmware an flashed it an everything went fine ,but when i went to flash twrp i got the same error (please help)

romell0018 said:
i need some help , i currently have an s8 everytime i try to flash twrp i get an error saying "only official binaries are allowed to be flashed (recovery) .i downloaded a new stock firmware an flashed it an everything went fine ,but when i went to flash twrp i got the same error (please help)
Click to expand...
Click to collapse
i got same problem. my usb debug is on and oem unlock is on. already flashed the stock firmware and when i try to install twrp in odin i got error of only official binary allowed. please help

Same
ling12fanny said:
i got same problem. my usb debug is on and oem unlock is on. already flashed the stock firmware and when i try to install twrp in odin i got error of only official binary allowed. please help
Click to expand...
Click to collapse
Same problem for me as well, S9+ G956F/DS

oh man, I'm having the exact same issue and all I could find (none of which has worked) is to somehow get rid of the triggered Knox security (boo, Samsung). I'll update you all if I manage to get something working but... I think it's a lost cause so far

Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc).
Thank you XDA.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc). If one may face problems, contact me on my whatsapp: +92 3159006552.
Thank you XDA.
Click to expand...
Click to collapse
I got super excited and immediately wanted to test it out but I still get FAIL in Odin when I try to flash TWRP and "Only official released binaries are allowed to be flashed (RECOVERY)" at the bot left in Download mode under all the text. Weirdly enough though, every time I change the date and restart the phone, it goes back to 28 June 2021 (this may be when I tried installing the stock firmware again but it didn't work either... why can't I just connect to the Samsung servers and automatically get the correct version for my phone, which also doesn't have stuff like jackpotlte in the description... I know I can get the correct firmware from sammobile but I feel like it should be more REAL )

nasko7 said:
I got super excited and immediately wanted to test it out but I still get FAIL in Odin when I try to flash TWRP and "Only official released binaries are allowed to be flashed (RECOVERY)" at the bot left in Download mode under all the text. Weirdly enough though, every time I change the date and restart the phone, it goes back to 28 June 2021 (this may be when I tried installing the stock firmware again but it didn't work either... why can't I just connect to the Samsung servers and automatically get the correct version for my phone, which also doesn't have stuff like jackpotlte in the description... I know I can get the correct firmware from sammobile but I feel like it should be more REAL )
Click to expand...
Click to collapse
Was the wifi turned on when you changed the date? Please Turn the wi-fi on, and then repeat the same requirements I mentioned above. When you're in Downloading mode install TWRP and IA it will be done.
It will definately work out, It was showing me the exact same issue but then I changed the date, powered off, booted it into download mode and installed the TWRP and even setted up the ROM (Noble ROM 1.5 By AlexisXDA). Also once you change the date to 2 August 2019, and you confirm it's changed. Then you have to turn the phone off and boot it into download mode (dont restart) but download TWRP via Odin and boot into the RECOVERY MODE directly.
Also if OEM unlock option is not being displayed in DEV options, changing the date to 2 August 2019 will show automatically unhide the option. The point when TWRP will be installed successfully, still don't let in boot to the system, go to the Recovery mode) i.e new TWRP.
Try to repeat the methods with the WI-FI on and let me know here again.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc). If one may face problems, contact me on my whatsapp: +92 3159006552.
Thank you XDA.
Click to expand...
Click to collapse
2 August 2019 doesn't always work. To find out what date you should change to, go to
"About Phone" and search for Android Security Patch Level, at the very bottom of the list.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc). If one may face problems, contact me on my whatsapp: +92 3159006552.
Thank you XDA.
Click to expand...
Click to collapse
Can't believe this actually worked.. thank you.

I was working with my tablet SM-T295 after I noticed that start lag after android 11 update, so.. I tried to downgrade it from 11 to 9, and that using TWRP, after backup data, I flashed it, and Odin exe said that the operation successfully done, but my tablet didn't did because it saying SECURTY FAIL : RECOVERY.img , so I tried booting it, and it surprisingly booted up! But I let it turned on until I goes to eat first, and I'm back... I founded that she turned off herself, I tried booting it up but it saying this...(jpeg)
Really need help, this is my main device.

El Khalil Bouzelmate said:
I was working with my tablet SM-T295 after I noticed that start lag after android 11 update, so.. I tried to downgrade it from 11 to 9, and that using TWRP, after backup data, I flashed it, and Odin exe said that the operation successfully done, but my tablet didn't did because it saying SECURTY FAIL : RECOVERY.img , so I tried booting it, and it surprisingly booted up! But I let it turned on until I goes to eat first, and I'm back... I founded that she turned off herself, I tried booting it up but it saying this...(jpeg)
Really need help, this is my main device.
View attachment 5558213
Click to expand...
Click to collapse
Have seen such messages in the past but don't remember the exact sequence of steps.
Always try flashing the vbmeta file from Odin whenever you get an official error. If error still persists, then flash TWRP once and then the stock recovery.

i'm stuck while installing vbmeta with odin :
<ID:0/003> vbmeta.img

Usually you can't flash your device with custom os using Odin directly, you need at least a recovery mode like TWRP, the first thing you need is TWRP recovery for your device model, then install it in your device using Odin toolkit, after that you gonna remove the nand from your device by deleting system data using TWRP, but be sure you already had the Firmware galaxy tab S5e in your PC in case you want to use your tablet again, after deleting sys data, cache...get an SD card (at least 4gb) and put the custom os in the SD card, then put it in your tablet, and select install option in TWRP, select the custom os, and start installing the os.

Alyaan Khalique said:
Hi XDA Forums,
I SOLVED THIS ISSUE:
All we've to do it to turn the phone on and fulfil these 3 requirements: All these 3 requirements can be found in the settings of the phone (Hereby I'm talking specifically about Samsung devices) and for mine it's Samsung Galaxy S9+.
- Enable Developer Mode, enable USB Debugging.
- From the same developer option, enable the OEM Unlocking (however may require reboot and reset).
- When the device reboots, turn on the device, go to the phone, go to the phone's settings and change the date manually to 2 August 2019.
Once you've change the date which is the last step then you can go back to the DOWNLOAD mode and install your demanded files (Recovery etc).
Thank you XDA.
Click to expand...
Click to collapse
i want to kiss you all over your face, its 6:36 in the morning, i've been trying to fix this problem for the past 6 hours