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.
Related
Hey guys
I may sound noob but the fact that my phone is still under android 5.0.1 drives me crazy (recent apps lag etc).
I've been checking for updates (OTA) but "Latest Updates have already been installed" message pops up.
I bought the phone from Cyprus (2nd hand) and as far as I am concerned it is fully stock (non-rooted).
Was my device supposed to receive the 5.1.1 update OTA, since other Note 4s in Cyprus were updated to 5.1.1 ?
Thanks!
Anyone guys ?
Was you phone rooted before? I am not sure of what i am going to say, but maybe if it was rooted you might not get official OTA. Turn off the phone, press POWER + HOME + VOLUME UP, and on the top left corner theres a Knox counter, check if it is 0x0 or 1x1. I am new to this phone and i have heard in some of the 2014/2015 phones if you root even if you unroot you won't be able to update via OTA. Hope it helps
Enviado do meu SM-N910F através de Tapatalk
Dedzdedz said:
Was you phone rooted before? I am not sure of what i am going to say, but maybe if it was rooted you might not get official OTA. Turn off the phone, press POWER + HOME + VOLUME UP, and on the top left corner theres a Knox counter, check if it is 0x0 or 1x1. I am new to this phone and i have heard in some of the 2014/2015 phones if you root even if you unroot you won't be able to update via OTA. Hope it helps
Enviado do meu SM-N910F através de Tapatalk
Click to expand...
Click to collapse
That's incorrect even if you trip your knox counter you can still receive otas, your phone has to be fully stock however to receive the otas. If you go to settings about and software information your device status should be 'official'. Another way to check is to boot into download mode (Volume Down + Home + Power button) and check if all the system are official. If they are then you are good to go.
OTAs are usually released in waves so that might be the problem.
Anyhow you can manually update your phone using Odin.
Download this firmware file : http://www.sammobile.com/firmwares/download/56036/N910FXXU1COI1_N910FVFG1COH5_CYV/
Then extract it and put your phone in download mode and connect it to your PC then run Odin as admin. (Make sure Kies is uninstalled)
Put the file in PDA and flash the firmware to your device.
As i said i was not sure, nice someone showed up to help [emoji1]
Enviado do meu SM-N910F através de Tapatalk
Dedzdedz said:
As i said i was not sure, nice someone showed up to help [emoji1]
Enviado do meu SM-N910F através de Tapatalk
Click to expand...
Click to collapse
Thank you for your time. Appreciate it!
Battlehero said:
That's incorrect even if you trip your knox counter you can still receive otas, your phone has to be fully stock however to receive the otas. If you go to settings about and software information your device status should be 'official'. Another way to check is to boot into download mode (Volume Down + Home + Power button) and check if all the system are official. If they are then you are good to go.
OTAs are usually released in waves so that might be the problem.
Anyhow you can manually update your phone using Odin.
Download this firmware file : http://www.sammobile.com/firmwares/download/56036/N910FXXU1COI1_N910FVFG1COH5_CYV/
Then extract it and put your phone in download mode and connect it to your PC then run Odin as admin. (Make sure Kies is uninstalled)
Put the file in PDA and flash the firmware to your device.
Click to expand...
Click to collapse
First of all thank you for your time!
Device Status in Settings -> About is Official.
So, how can I make sure that this is the right Firmware to flash (as the phone was bought from Cyprus 2nd hand, and Im not sure if the other guy bought it from an other country in Europe) ?
Moreover, If i manually install the firmware file, as you stated, do I need to root the phone or something ? Or the device will be 100% official (its just that you install the update through the pc instead of OTA )?
It seems to be taking too long for the OTA, and that's why I was worried.
Thank you again!
Snake_A said:
First of all thank you for your time!
Device Status in Settings -> About is Official.
So, how can I make sure that this is the right Firmware to flash (as the phone was bought from Cyprus 2nd hand, and Im not sure if the other guy bought it from an other country in Europe) ?
Moreover, If i manually install the firmware file, as you stated, do I need to root the phone or something ? Or the device will be 100% official (its just that you install the update through the pc instead of OTA )?
It seems to be taking too long for the OTA, and that's why I was worried.
Thank you again!
Click to expand...
Click to collapse
The firmware is fully stock, untouched.
You do not need to be rooted to flash the firmware.
You can install this app on your phone and check your CSC
So This is what I get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suppose it is a Greek version. So, which firmware shall i download ? (There are 3 different firmwares : Greece, Greece Cosmote, Greece Vodafone. Greece has no 5.1.1 version only the latter two have.
Snake_A said:
So This is what I get:
I suppose it is a Greek version. So, which firmware shall i download ? (There are 3 different firmwares : Greece, Greece Cosmote, Greece Vodafone. Greece has no 5.1.1 version only the latter two have.
Click to expand...
Click to collapse
Might I ask are you in the UK (Your current operator) If so you can attempt to flash the UK firmware.
If however you are living in Greece then you could flash one of the Greece firmwares and then flash a stock ROM (It will require a custom recovery, tripping KNOX counter) without the bloat.
The choice comes down to you, another last resort if you don't want to trip KNOX would be to flash a neighbouring country's firmware.
Battlehero said:
Might I ask are you in the UK (Your current operator) If so you can attempt to flash the UK firmware.
If however you are living in Greece then you could flash one of the Greece firmwares and then flash a stock ROM (It will require a custom recovery, tripping KNOX counter) without the bloat.
The choice comes down to you, another last resort if you don't want to trip KNOX would be to flash a neighbouring country's firmware.
Click to expand...
Click to collapse
Basically I am from Cyprus but I'm currently studying in the UK. So what's the difference between the various firmwares ? I thought that only the one that is the same as the country you bought the phone is compatible.
Snake_A said:
Basically I am from Cyprus but I'm currently studying in the UK. So what's the difference between the various firmwares ? I thought that only the one that is the same as the country you bought the phone is compatible.
Click to expand...
Click to collapse
Different country firmware can be flashed only sometimes it fails (nothing to worry about) in that case you might have re-package the firmware. Meaning you put the CSC from your country into the firmware.
Anyhow I would you to flash this firmware via Odin:
http://www.sammobile.com/firmwares/download/58473/N910FXXU1COJ3_N910FOXA1COJ3_DBT/
After downloading the firmware extract the file inside (using WinRar or equivalent)
A factory reset might be required to back-up everything from your phone as the internal storage will be wiped.
Uninstall Samsung Kies, install these USB drivers: https://www.androidfilehost.com/?fid=24052804347849220
Download Odin: https://www.androidfilehost.com/?fid=24052804347836222
Power down your phone, hold volume down key + Home key and power on the device. Press volume up to continue when promoted.
Connect your phone to your PC via USB.
Run Odin as admin and and put the extracted firmware file in AP and press start.
The phone should now reboot, let it do it's thing. If after around 10 minutes it's still at the Samsung screen.
Power off the device hold volume up + home + Power the device on and using the volume keys select wipe data and cache, then reboot.
Good luck, as always I must give the disclaimer that anything you do with your device is your responsibility.
Greetings, I have used your services a lot (different ROMS and tutorials) and appreciate all the effort the XDA community has provided to users of all levels. However now, I am unable to find the solution that I have been working on for quite some time.
For the last week or so, I have been trying my best to SIM unlock my S4. I know I could just ask my provider and save the headache of all this but I do find there is a great sense of accomplishment and learning when things are done yourself. I will list the phone's info below and the methods I have tried. I have ran multiple roms on this device: Stock --(wanted to be different)--> Slim ROM --(wanted to try something new)--> Resurrection --(had too many mic issues) --> CyanogenMod (now GPS doesn't work so I might try a new ROM)
S4 - SGH-i337M (jfltecan/jflte)... verified root
CyanogenMod version 11-20160815-NIGHTLY-jflte
Baseband version: I337MVLUGOH1
Build number: cm_jftle-userdebug 4.4.4 KTU84Q e2d38f60cf
Android 4.4.4
Kernal: 3.4.104-cyanogenmod-g8b03f0c
Recovery is via CWM
Locked Network info (via Phone INFO and SIM Card Information app):
Original CSC Code: FMC (Fido Canada)
Active CSC Code: FMC (Fido Canada)
The phone was bought from Fido a couple years back.
Network Operator Code: 302720 (Rogers Wireless - I think this what my Network atm is for emergency calls)
This is all the information I could get, please let me know if you need more info
I tried the popular method of doing this via ServiceMode by dialing #*0011# but nothing shows up on screen when I do that, the numbers don't even disappear (they just sit there taunting me); the same goes for *#197328640#. The only code that I have seen work is *#06# (IMEI). I looked up multiple android codes and either the numbers would stay and nothing would happen but sometimes the numbers would just disappear when i completed the code with no changes on the screen. I have downloaded and ran Service Mode Shortcut and Service Mode app and when I click ServiceMode on them, it says "Not Supported." in a little caption bubble at the bottom of the screen.
I then ran GalaxySim Unlock App and it states "Your device should be unlockable if you downgrade your baseband to MDJ or before. When I click on How to do it?, it pretty much asks me to download a stock version of my phone and try the app again.
I would like some advice on what steps I should take next.
Thank you for your time,
roms4eva
THE SOLUTION FOR ME:
Hi, I am going to leave a summary of what I did to fix my sim! Thanks to @audit13!
All the download links can either be found via google or on some on this thread. The link in post#2 has useful download links within it!
PLEASE MAKE SURE YOU BACK UP ALL YOUR IMPORTANT SELFIES, FILES, VIDEOS, ETC... My steps will require a clean installation, if you do not want a clean installation, just skip step 10 where you have to do a factory restart and just continue as is.
Short instructions - if you are already familiar with the content:
Flash 4.4.2 stock(.tar.md5), flash modem 4.2.2 (.bin) (if you can't, try another odin), flash TWRP (.zip), install SuperUS (.zip), install and run RegionLock Away 1.3 (.apk), reflash 4.4.2 or 5.0.1 if you wanna newer ROMs on.
Long instructions:
Download Stock firmware of 4.4.2 for your provider (via Google)... extract it out until you get the .md5 file out (ie. I337MVLUFNE1_I337MOYAFNE2_I337MVLUFNE1_HOME.tar.md5)
Download modem 4.2.2 for your provider (via post #2) (ie.modem.bin)
Download TWRP (via post #2) (ie. twrp-3.0.2-0-jfltecan.img.tar)
Download SuperUS.zip (via post #2) (ie. SuperSU-v2.79-201612051815.zip) and put it onto your s4 storage (via MTP setting and USB debugging on)
Download Regionlock Away 1.3.apk (via post #2) (ie. RegionLockAway-v1.3.apk) and put it onto your s4 storage (via MTP setting and USB debugging on)
Download Odin v3.12.3 and/or v3.07 (via post#2 or Google) (if one does not work, ie. stays stuck in "file analysis...", try the other odin)
Verify that Odin can recognize your device (plug s4 in via download mode status [Turn off, then hold Down + Power] and see if oden says "Added!!")
Run Odin 3.12.3 w/ administrator powers, make sure your device is "Added!!", click AP and select the .md5 file you downloaded(its the 4.4.2 in step 1).
Give Odin some time as it verifies the md5, then click start once that button is available. Then click start again once it says "Leave CS..." [this one took me an embarrassing two hours to figure out... LOL)
Let the s4 boot up and then restart into recovery (turn off phone, then hold UP Volume + Power), and do a factory reset (select on factory reset/data wip and choose Yes)
Restart the phone and go to download mode again (Down Volume + Power).
Go back to Odin 3.12.3 with admin power and under CP select the modem file for your carrier (modem.bin) and click start. If you are stuck on file analysis... after doing this and it has been over one minute, close Odin 3.12.3 and try it with odin 3.07 with admin power... the modem.bin file goes into Phone section.
While in download mode still, you could restart odin and flash the TWRP with any of the odin programs (odin 3.12 via AP section, or 3.07 via PDA)
start the phone up in recovery mode (UP vol + power), click on install, then find the SuperUS.zip file and install it.
Start the phone up normally with the SIM inside if you haven't put it in yet. (internet connection not required and it doesn't matter if SIM was in or not in the previous steps)
Go to File Manager or File Explorer, find the RegionLockAway-v1.3.apk you put in and run it... make sure you enable the ability for apks to be manually installed.
Go to apps and open the RegionLock Away app.... Click on Region Unlock button and grant it the superUS permissions it requires... then reboot!
The SIM Network Unlock Pin should disappear and your phone is now SIM Unlocked! If it asks again, wait a minute and restart the phone. If that doesn't work, retry the steps or make a thread and someone might be able to help you out.
Repeat step 8 again! You need to reflash! [note that this will remove your TWRP recovery, so reinstall that again like you did in step 13 if you want that. You will also lose root due to reflashing (so install superUS again)
Good luck!
I think ServiceMode is available only on TouchWiz ROMs.
Do you recommend I go back to stock via samsung-updates id=SGH-I337M (selecting Galaxy S 4 (Canada) SGH-I337M FMC I337MVLUGOH1 Android 5.0.1 24.08.2015 4508315)
Flash back to stock 4.4.2, flash 4.2.2 modem, root, run regionlockaway, reflash stock 4.4.2, enjoy your sim unlocked phone. This may help: http://forum.xda-developers.com/showpost.php?p=68889708&postcount=120
Btw, remove the imei from your post.
audit13 said:
Flash back to stock 4.4.2, flash 4.2.2 modem, root, run regionlockaway, reflash stock 4.4.2, enjoy your sim unlocked phone. This may help: http://forum.xda-developers.com/showpost.php?p=68889708&postcount=120
Btw, remove the imei from your post.
Click to expand...
Click to collapse
Thanks, I am currently doing as you have stated.
You also mentioned that I should install the regional unlock app. Will your method as well allow me to have my SIM unlocked? I am trying to use another carrier in another country (Saint Martin) and I am asked for my SIM unlock code.
Will I be able to use other Roms after this or am I stuck with 4.4.2 when I reflash?
roms4eva said:
Thanks, I am currently doing as you have stated.
You also mentioned that I should install the regional unlock app. Will your method as well allow me to have my SIM unlocked? I am trying to use another carrier in another country (Saint Martin) and I am asked for my SIM unlock code.
Will I be able to use other Roms after this or am I stuck with 4.4.2 when I reflash?
Click to expand...
Click to collapse
Yes it's a sim unlock method and you can use other roms as well
Sent from my GT-I9505 using XDA-Developers mobile app
I used the method @audit13 described and unlocked my device without trouble. My device is an I9505 and ran on Straight Talk in the US, so you should have no problem with using the device as you wish. Once you get the device unlocked, you can run any ROM you want. In my case I run AOSP 7.1.1 without trouble.
audit13 said:
Flash back to stock 4.4.2, flash 4.2.2 modem, root, run regionlockaway, reflash stock 4.4.2, enjoy your sim unlocked phone. This may help: http://forum.xda-developers.com/showpost.php?p=68889708&postcount=120
Btw, remove the imei from your post.
Click to expand...
Click to collapse
Hi,
So I did everything you mentioned above. Should I consider my device Stock and unrooted but with SIM unlock? Am I free to install ROMS now?
When I boot up, it asks for my SIM network unlock PIN, as well it says I have an "Invalid SIM card (network locked SIM card inserted)". - should I try the *#0011# method? I have access to ServiceMode now it seems!
I have followed through w/ your instructions... is everything set now? The SIM card is from the Caribbeans and I will not know if it actually works until I arrive there on Jan 2 for schooling.
Android version: 4.4.2
Baseband version: i337MLUFNE1
Kernel Version: 3.4.0-1529758
Build number: KOT49H.I337MVLUFNE1
If you followed the instructions, you should not be prompted for a network unlock code. Are you prompted to enter a SIM pin or network pin?
audit13 said:
If you followed the instructions, you should not be prompted for a network unlock code. Are you prompted to enter a SIM pin or network pin?
Click to expand...
Click to collapse
I am asked for the SIM network unlock PIN.
Did you add a security pin to the SIM card? Did you try different SIM cards?
audit13 said:
Did you add a security pin to the SIM card? Did you try different SIM cards?
Click to expand...
Click to collapse
Hi, when I go to the sim card app, there is a thing called "Secure Pass" on it. The carrier is CHIPPIE. I will try a newer sim card today.
if it helps:
{
"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"
}
should i try your steps again?
Something has gone wrong because you should not be b seeing that screen if the steps were followed. I have used this method to unlock about 7 sgh-i337m phones.
audit13 said:
Something has gone wrong because you should not be b seeing that screen if the steps were followed. I have used this method to unlock about 7 sgh-i337m phones.
Click to expand...
Click to collapse
I have faith in xda users, I shall try it again!
Is the modem and firmware accurate?
Yes, it should be. After flashing the modem, wi-fi and cell service won't work.
audit13 said:
Yes, it should be. After flashing the modem, wi-fi and cell service won't work.
Click to expand...
Click to collapse
Hi, could you link me the 4.2.2 modem?
I am using this zip file found here (and flashed it via CWM on the 1st time i tried it) http://forum.xda-developers.com/showthread.php?t=2318233 and when i try to flash just the modem.bin via odin CP (1st time and now), it stays on the file analysis step and nothing happens. (I also restarted my phone and laptop). I know Odin works b/c i flashed the rom and twrp with it.
I think that may be the wrong one because upon cross checking with this link: http://forum.xda-developers.com/showthread.php?t=2324667 , it seems like the 1st link is for puerto rico, not canada as it claimed.
Also, the download links on the 2nd link are not working...
You need to use the modem I linked. Puerto Rico and Canada have the same s4.
I checked the links and they work for me.
audit13 said:
You need to use the modem I linked. Puerto Rico and Canada have the same s4.
I checked the links and they work for me.
Click to expand...
Click to collapse
i meant the dropbox links here: http://forum.xda-developers.com/showthread.php?t=2324667
{
"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.
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
Hello all,
I'm having the Samsung Galaxy S8 (SM-G950F) the device with the Exynos CPU.
Everything worked fine with Android 9.0 and the One UI 1.0 until I decided to install TWRP and a custom ROM using Odin software.
Lots of things with a custom ROM isn't working correct.
Such as the NFC, apps for e-banking, Netflix etc. I didn't root my device.
So, I need to go back to factory defaults.
I downloaded the proper firmware from sammobile and installed it using Odin.
I extracted the zip file and followed the instructions from sammobile's site.
1. Extract the 5 firmware files (i.e. to folder c:\Odin)
2. Open Odin
3. Power off your phone
4. Reboot Phone in Download Mode
Connect USB-cable to your computer. Hold down Volume up and Volume down at same time. While holding down, connect the USB-cable to your phone
5. Wait until you get a blue sign in Odin
Add the firmware files to their designated slots (AP in AP, BL in BL, CP in CP, HOME_CSC in CSC). Do not tick any extra boxes. The only options to be ticked are F. Reset Time and Auto-Reboot.
Click the start button to begin flashing the firmware update
6. Click the start button to begin flashing the firmware update
Click to expand...
Click to collapse
My phone is working, but now I'm having an issue with my Google account.
My device is not certified.
I found instructions online to fix it but none is working.
What I'm missing here?
The method i used is the proper one or not?
Thank you in advance.
Read this... probably a Samsung Experience center at Best Buy be able to sort it out.
On my Samsung's I never touch the firmware unless there's corruption (not happened so far). Don't even update/upgrade it. Zero issues.
Thank you @blackhawk for your instant reply.
I have done this a few days ago.
The uncertified message is displayed in Google Play settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have used the Device ID app in the device registration website by Google.
When I'm trying to paste my Google Services Framework Device ID the box is turned into red as the screenshot below and a pop up message appears with Value already registered.
The list contains two entries. I don't know what these are regarding.
I'm also having an Android TV box with the same Google account.
Gmail, Google Photos, Google Drive and other Google stuff is working, but Google Pay & Netflix is not working.
I tried also clear the cache and data from Play Store app.
Is there anything else i can do?
You're welcome.
Gookill is a mess. If it's generating any error code messages look them up.
Try deleting the Google account on the phone, reboot and set it up again... I hope this works.
I have done this too.
I removed the Google account, I forced stop the Play Store. I cleared the cache and data. I rebooted my phone and I signed to Google. The message had gone in Store's settings. I tried to access the Google Wallet (Pay) or Netflix with no luck!
The message appeared again!
fatammag said:
I have done this too.
I removed the Google account, I forced stop the Play Store. I cleared the cache and data. I rebooted my phone and I signed to Google. The message had gone in Store's settings. I tried to access the Google Wallet (Pay) or Netflix with no luck!
The message appeared again!
Click to expand...
Click to collapse
Try again but clear Playstore data too. The cause maybe be in other Google apps data.
Don't know...
Thank again @blackhawk
As I said before, I deleted data and cache.
I don't know..
anyone else knows another way of fixing that issue?
fatammag said:
Hello all,
I'm having the Samsung Galaxy S8 (SM-G950F) the device with the Exynos CPU.
Everything worked fine with Android 9.0 and the One UI 1.0 until I decided to install TWRP and a custom ROM using Odin software.
Lots of things with a custom ROM isn't working correct.
Such as the NFC, apps for e-banking, Netflix etc. I didn't root my device.
So, I need to go back to factory defaults.
I downloaded the proper firmware from sammobile and installed it using Odin.
I extracted the zip file and followed the instructions from sammobile's site.
My phone is working, but now I'm having an issue with my Google account.
My device is not certified.
I found instructions online to fix it but none is working.
What I'm missing here?
The method i used is the proper one or not?
Thank you in advance.
Click to expand...
Click to collapse
Hi bro,
Go to setting and turn on developer option by pressing 4to5 times of build number and go back to developer option and turn off OEM Unlock thats it simple.. now better reset/restart your mobile then go and check play store play protection its show device is certified.
fatammag said:
Thank again @blackhawk
As I said before, I deleted data and cache.
I don't know..
anyone else knows another way of fixing that issue?
Click to expand...
Click to collapse
Is your bootloader unlocked? If you're trying to return to bone stock, you'll need to relock the bootloader to pass hardware attestation.
Or...
Root with Magisk and install the Universal SafetyNet Fix module.
V0latyle said:
Is your bootloader unlocked? If you're trying to return to bone stock, you'll need to relock the bootloader to pass hardware attestation.
Or...
Root with Magisk and install the Universal SafetyNet Fix module.
Click to expand...
Click to collapse
Thank you for your reply! @anbalaganaero solution fixed my problem.
anbalaganaero said:
Hi bro,
Go to setting and turn on developer option by pressing 4to5 times of build number and go back to developer option and turn off OEM Unlock thats it simple.. now better reset/restart your mobile then go and check play store play protection its show device is certified.
Click to expand...
Click to collapse
A big thank you! It works!
fatammag said:
Thank you for your reply! @anbalaganaero solution fixed my problem.
A big thank you! It works!
Click to expand...
Click to collapse
Welcome