Related
Hi
Here is the way i used to flash the firmware, i advise to backup all your data before the flash.
All the files here are provided without any waranty.
Flash at your own risks.
Remember that go back to 4.3 is impossible after this procedure.
You may too void your knox counter when you attempt to root your device...
Click the pictures to open the root of the Mirror and find others goodies.
- Flash The Firmware :
First: Set the reactivation lock setting of your phone to OFF.
Be sure the battery of the phone is full.
- Uninstall Kies if you have it on your computer to avoid conflicts.
- Download PC Odin and Install / update the drivers from Samsung[/URL], that's all you need.
- Best and safe way is to use the original stock usb3 cable and make the job on a portable computer with his own power supply (battery connected).
1 - Download the latest repacked rom in this folder and extract it.
This is pure stock rom with only Multi-CSC OXXEND2 added.
Currently, this rom contain 19 Country Codes:
BGL, CYO, ERO, MSR, ORX, PHE, ROM, SEB, SEE, SIO, TEB, TOP, TPH, TRA, TSR, TWO, XEF, XEH, XSK
As it have a small sized hidden partition there is no need of any PIT File. More safe in my opinion.
If you need another CSC, maybe one of then is yours:
The Multi-CSC VFGENA4, 19 Country Codes:
ATL, CNX, CYV, MOB, MTL, OMN, PRO, SIM, SWC, TCL, TOP, VD2, VDC, VDF, VDH, VDI, VGR, VOD, XFV
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OLBEND1, 10 Country Codes:
GLB, MM1, SIN, SMA, STH, THL, XME, XSP, XTC, XTE (Asia)
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OXAEND1, 5 Country Codes:
BTU, DBT, ITV, XEF, XEO
As it have a small sized hidden partition there is no need of any PIT File.
The Multi-CSC OJVENB2, 3 Country Codes:
KSA, XFM, XSI
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ITVEND1, 1 Country Code:
ITV (Italy)
As it have a small sized hidden partition there is no need of any PIT File.
The CSC ZZHENE3, 1 Country Code:
TGY (Hong Kong) - The attached modem ZHUENE2 is here.
As it have a small sized hidden partition there is no need of any PIT File.
The CSC VNZDMJ4, 1 Country Code:
VNZ (New Zealand)
The csc parts are from 4.3 rom but are confirmed working fine.
As it have a small sized hidden partition there is no need of any PIT File.
Three others CSC for specifics operators in France.
As they have a small sized hidden partition there is no need of any PIT File.
Check at the bottom of this post for French thread.
Just grab the one you want and put it in CSC in PC ODIN during the same flash process and it first flash the CSC inclued in the firmware, and then overwrite the CSC with the one you added.
2 - Download CF Auto Root for KitKat from Chainfire ODIN version.
Extract the tar.md5 file inside the zip to use with pc odin.
3 - Download the custom recovery PhilZ Touch ODIN version.
I advise to apply this unlock procedure before anything to avoid flash errors:
-> You need Triangle Away from Chainfire with a root acces granted.
Free version is avaible but consider to support the dev for his great job...
a/ Install the app on your phone.
b/ Run Triangle Away and Reset Flash Counter - Follow exactly what the program ask.
At the time to choose the way to reboot after the reset is done in recovery, choose reboot in download mode and then start the flash process immediatly.
4 - In download mode flash the file that you had previously downloaded N9005-hlte_PDA-xxxxxxx_CSC-xxxxxxx_MODEMS-xxxxxxx_REPACK.tar.md5 with PC Odin in AP.
Do not forget to check/enable the Phone Bootloader Update option in pc odin. (seems working nevertheless without this option ticked)
Leave all others one by default.
Make sure re-partition is NOT ticked.
If you have an error (size error - Your phone may mismatch with this rom, another Samsung lock...) as odin fail at the end of the flash process.
- Shutdown the phone, disconnect the battery, disconnect the phone from your computer and wait a minute, return to download mode.
- Download and flash the file wich contain the CSC that you want.
5 - Auto self-reboot, let the stock recovery do his work completly (the green android man).
If you don't want to install root and a custom recovery, you can stop here.
6 - Go back download mode, flash the PhilZ Touch recovery with pc odin in AP.
7 - Again, in download flash, CF Auto Root with pc odin in AP, let the installation process terminate.
Note: If you were previously rooted, jump this step and download, If not yet done, SuperSu to update by flashing the file in custom recovery..
In this case, re-flash CF Auto Root will loose all your settings of SuperSu...
8 - Download the fix for the ExtSdCard issue and flash it in custom recovery.
This is a Google security restriction, unnecessary to wait for a fix from Google, just from developpers of apps. Quick way is to apply this fix.
9 - Don't forget BusyBox which should be usefull too.
- About Mobile Odin :
As Mobile Odin seems to be unable to update the bootloader, don't use this one to avoid brick issues when operate with a different rom version than you have.
If you are already on the same firmware, you can use Mobile Odin to re-flash the rom or any other single part:
- Copy the file on your phone.
- Open this file in Mobile Odin.
- Enable EverRoot and Inject Superuser (SuperSu) in case of a system flashing.
- Choose to reboot in Recovery when you flash System and Cache partitions. If not, you may have problems regarding the CSC.
- Start Flashing.
- Do not skip md5 check to gain a little time. (For the life of your phone...)
- Issues :
All theses solutions were tested by me and worked for me, but without any other warranty.
The CSC region code or version are invisibles, the CSC folder is missing in system/.
The stock samsung keyboard crash often once booted.
You need another CSC (warning, you wil loose all your datas and settings, change for another CSC perform a wipe of the phone)
- Check here for the file you need, download and extract it.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_CSC_xxxxxxx_RECOVERY-xxxxxxx_REPACK.tar.md5 with pc odin in CSC.
The Modem is not updated.
Download and extract the .tar.md5 modem file.
-> Apply the Unlock Procedure.
- Flash the file that you had previously downloaded N9005-hlte_MODEMS_xxxxxxx_REPACK.tar.md5 with pc odin in CP.
- Reboot normally.
The Bootloader is not updated.
You can check by using this app.
-> Download and extract the .tar.md5 bootloader file.
-> Apply the Unlock Procedure.
- Flash the file N9005-hlte_BL_xxxxxxx_REPACK.tar.md5 with pc odin in BL and check/enable the Phone Bootloader Update option.
- Reboot normally.
Flash player doesn't work anymore.
-> Install Firefox last up to date version and the original latest apk from adobe, nothing else to do.
-> If you prefer Dolphin, download the special version of adobe flash player, more here.
Maybe someone make an xposed module later, it should be a dream...
This fix seems working with this rom (bootloop efs corrupted related).
Not personally affected, just tested the flash.
Download here too.
After all this procedure, you should be fine, upgraded and with all yours datas and settings...
At this state, i just made a wipe of the cache and dalvik cache with phil'z recovery.
- Tune :
- Enable Init.d Support.
- To simply restore the sound at the (de)connection of the charger, you can install this app.
- If you want an imaged battery, you can use RECOVERY - SystemUI N9005 xxxxxxx MOD tkari4-Version by tkari4 based on the guide from parkhyb.
Basically revert to the old 4.3 style for battery and network icons.
{
"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"
}
Just Flash the mod with any custom recovery.
To revert back to the original situation, just flash in custom recovery the file RECOVERY - SystemUI xxxxxxx ODEX STOCK. (STOCK ODEX version)
You can use my blue battery mod. (I reworked a little the graphics for a better scale.) Just extract the .rar archive and install normally the apk Inside, you need too a working Xposed Framework installed.
You can find other Xposed compatibles battery Mods here.
Just reboot once installed.
Many Thanks to tkari4 for keeping alive his mod. :good:
- The repacks i made still works fine.
The rom repacks are made by me with this tool.
Many thanks and credits to all the persons who made this possible.
Notes:
As i do not have the time to download/extract all the roms, if someone needs another CSC repack for him or just to share, please post here with a link for the extracted CSC files only (cache.img.ext4 - hidden.img.ext4) related and with all the details (region, full code name, original rom it come from ... )
To unpack a .tar.md5 file, simply rename it as .tar and extract the content with any good archive software.
I will centralize here.
All others requests in any another form will be ignored, thanks for understanding.
To keep as simply and clear as possible, i will maintain on the Mirror and on thread only the latest updated rom, so if you put elsewhere any link from here, it may be broken in the time, the only ones which would be permanent is the one of the folder and the one of this thread. If you Mirror any file, thanks to keep credits.
Keep a local copy of the downloaded files if you think you will need then later as the content should be updated here.
I maintain the updates only for multi-csc repacks and keep others ones in the mirror, if you need one of theses mono-csc wich is not updated with the latest recovery avaible, simply ask here...
French users, clone thread is here.
Just press thanks if i helped.
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
polish_pat said:
Did you search the forum before posting? because if you did, you'd see that there are 500 thread about this already.
Click to expand...
Click to collapse
Yes, every day i do.
And i saw no thread that talk about merging two différents roms to make a new one for a specific country, centralize all the majors tools with direct download links for correct versions to avoid confusions between JB & KK, that i often saw, and attached xda threads, and too provide others files needed at the same place for my device (n9005)
Maybe i had read the forum more often than you think...
Sincerly.
Perhaps you should look again
http://forum.xda-developers.com/showthread.php?t=2617932
http://forum.xda-developers.com/showthread.php?t=2631395
http://forum.xda-developers.com/showthread.php?t=2614787
http://forum.xda-developers.com/showthread.php?t=2618633
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
I made also my Rom N9005XXUENA7_OXXENA5_XXUENA2_ NoBootloader whit this TOOL from A.S._id Dev. Thanks @A.S._id
Only this files:
boot.img
cache.img.ext4 -->from NA6 (OXX)
hidden.img.ext4 -->from NA6 (OXX)
modem.bin
NON-HLOS.bin
recovery.img
system.img.ext4
Whitout Bootloader (5 files). Work well whit BL XXUENA6 and no Knox appl's.
At first boot, after enter whit my language, I have my csc TPH automatic, alright.
It's very good this [TOOL] TAR.MD5 PACKAGER and easy to make changes whit.
Anyway, thanks by Your work.
Best Regards
Valente
=======================================================================================
polish_pat said:
Did you search the forum before posting?
Click to expand...
Click to collapse
polish_pat said:
Perhaps you should look again
Click to expand...
Click to collapse
Hi Dear @polish_pat
Please, we have a MODERATION to see all Member's work. Not censure this Member. He have rights like You.
Thank You
polish_pat said:
Perhaps you should look again
....................
these are just thread in general section, hit in the past 24 hours, i didnt even get the ones in FAQ nor in dev section, i'm sure i could add about 10 more just by looking at the first page of each. If your thread is not getting hits from anybody, must be for a reason. Just sayin'
Click to expand...
Click to collapse
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Le [email protected] said:
You made a thread, Others made a thread, i made a thread too, i just wanted to simply share my experience in another form, without any other pretention.
You seems to have a problem about that, not me.
You have time to waste, not me.
I'm not interested to play to the one that has the biggest.
Sincerly
Click to expand...
Click to collapse
i made a thread a month ago, when it was relevant and nobody else did it.
Le [email protected] said:
Hi,
Set the reactivation lock setting of your phone to OFF.:
Click to expand...
Click to collapse
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
johnvicencio said:
How do you do that on 4.3? (It's not on security setting).
Samsung Galaxy Note 3 T-Mobile USA.
Click to expand...
Click to collapse
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Le [email protected] said:
I found it easly in security settings.
Maybe because you are on a Galaxy Note 3 T-Mobile USA, i have the HLTE international one.
In any case, check this video at about 2.30 mn
Click to expand...
Click to collapse
I see thank you. That doesn't exist on T-Mobile USA at least not on 4.3.
1 - Download the official Poland rom...
2 - Download any NA7 rom...
To this step's We have here a MIRROR on MEGA Host.
Updated the op with a link to the repacked rom and refreshed the guide.
So it is more easy and simple, i think.
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Pierre118 said:
Good and informative First Post. Thanks!
Maybe you can do the same with the update that came out today
Click to expand...
Click to collapse
Op Updated
No need to repack the whole firmware as all which is needed is Inside.
I am currently upload the rom to mirror it ...
Just made a new repack for the multi-csc.
Just flashed over the NA7 rom by following my guide and all went fine.
No full wipes.
Just made a wipe in dalvik cache and cache in recovery once done.
Great and complete Guide. Useful this ALL IN ONE PLACE. Bookmarked.
Thanks
I QUOTE from my THREAD next useful posts by @letama and @Le [email protected]
After this question to a member that not managed to flash the Bootloader NB3:
ValenteL said:
What Rom have You installed? If You have flashed the XXUENB3 why You are in NA6 BL?
Click to expand...
Click to collapse
letama said:
There is a catch in going from NA6 to NB3, it seems bootloader flashing is ignored now in NA6 BL if your rom status is custom. Solution is triangle away, reflash na6 stock, then make sure that you status is official before flashing NB3.
Click to expand...
Click to collapse
Le [email protected] said:
I was on NA7 BL previously flashed over NA6 BL without any problem.
Followed your trick and flashed my own made NB3 flashable file.
I did not any reflash, just reseted with triangle away.
And it worked, i am now on NB3 BL.
Updated my thread too..
Thanks.
Click to expand...
Click to collapse
letama said:
Thanks, good to know that reflashing pure stock is not mandatory, so the bootloader checks custom status flag only and not the whole firmware. Great, will save time for next one .
Click to expand...
Click to collapse
Updated the OP with a new version of Flash Player i found on xda wich work with Firefox too now.
Hi @Le [email protected]
Only for this time: Do not forget to check/enable the Phone Bootloader Update option in pc odin.
I don't understand why, if we flash a complete Rom whit a new bootloader. We not update the bootloader installed. Why You have this opinion now?
Thank You
Hi ValenteL
I saw (here or on other frenchs forums, no links to provide, forgot then) twice posts of somes personnes who don't have checked the option and have updated their bootloader and others one who don't had bootloader update and got soft brick issues as the rest was updated (JellyBean to Kitkat essentially)
It is usually advised here to check this option.
I not personnally took the risk to bypass this option in pc odin and always used it, so i can not confirm if it is important, effective or not.
There is this option in pc odin, i think too this is not for nothing at all.
For all this reasons, i prefer advise to enable this option when flashing a new rom, and it cost nothing to do.
Personnaly, i think it is important to do when using multi-files roms as the first Poland Leaked KitKat, but the bootloader update must be done automatically when flashing a single file rom which contain Inside all the needed parts.
Of course we can have problems when the knox is trigerred or the status of the rom is to custom, then somes parts seems to be 'jumped' when flashing. I feel this fact is increasing in the time.
When i bought my note 3, Under JellyBean, in France, i updated the rom with the latest version of JellyBean avaible on sam mobile for my country (XEF) and had no issue after the flash.
I got problem when i starded to flashed KitKat from others countries as the XEF one is not yet avaible and as i am a little an impatient flash-addict.
I wonder sometimes if i could have all this problems if were more patient and waiting for an upated version for my country.
At this time i identified three parts wich seems locked (not a secret).
CSC -> Ok, Samsung do not want i flash from another country, new policy from Samsung to lock by geographics sectors.
Modem -> Ok, region lock again.
Bootloader -> Why ? Does samsung want to block customs rom such CM, roots and others sames things? And knox related certainly too.
Samsung want to control and limit me a lot, to make more money with me.
Me, i want to be able to do ALL what i want with the device i bought, this is mine, as i can do with my Note 1.
There is a lot of chances that samsung never see again my money...
Time to bed here.
Sincerly
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
---------- Post added at 09:22 PM ---------- Previous post was at 08:36 PM ----------
Pierre118 said:
@ Le [email protected], Mega gives me a error when trying to download BOOTLOADER_N9005XXUENB3_REPACK.rar. Is there something wrong with the file?
Click to expand...
Click to collapse
Never mind, Mega had a problem. Download is ok now.
I can't keep my mirror up due to increasing need for more space with all the projects I'm working on, sorry guys.
DOWNLOAD
You can find Odin at:
https://build.nethunter.com/samsung-tools
I am no longer hosting firmware for the Note 3. fw.updato.com provides an alternative, and allows wget/curl. (with --referer="link to the download page"))
Example:
N900W8VLU2DPG1 - MTA clicked on at http://updato.com/firmware-archive-select-model?q=N900W8
Code:
wget "http://fws01.updato.com/GALAXYNOTE3/SM-N900W8/BMC/SM-N900W8_1_20160729160241_v4dg1gvbce.zip" --referer="http://updato.com/firmware-archive-select-model?record=3C39D6E6701111E69B2DFA163EE8F90B"
READ INSTRUCTIONS BELOW, OR IT WON'T STICK AFTER FLASHING!
Each zip file contains a _HOME.tar.md5 containing each flashable partition of your device. You can flash the entire tar.md5 for a complete factory restore, or you can extract individual partitions and re-tar them to make individual flashable partition files. There's a tool for tarring them here:
https://build.nethunter.com/samsung-tools/img2tar.zip
GETTING YOUR FIRMWARE TO STICK
When flashing bootloaders (BL) and modems (CP), you must cold boot your phone for the flash to succeed.
To perform a cold boot into Odin, follow these instructions carefully:
Power down your phone
Unplug any cables from your phone
Pull the back cover off and remove the battery completely
Place the battery back in your phone (there is no need to wait)
Place 1 finger on volume down key, and 1 finger on home key
While holding those keys down, place another finger on the power key
Release the finger from the power key when you feel a vibrate
Release your other fingers once you see the Odin warning screen
You may plug your phone cable back into the phone now, or after the next step
Press volume up key to enter Download mode
SOME ODIN OPTIONS EXPLAINED
Auto Reboot - Once the firmware finishes flashing, the phone will attempt to reboot into your current ROM
Re-Partition - Used to flash a PIT file over the current one. See more information below.
F. Reset Time - Enabled by default. Not entirely sure what it does yet.
Nand Erase All - May have different effects on other devices. On the Note 3, it wipes the just the userdata partition to zeros. (your ROM settings, apps, and internal storage)
Phone Bootloader Update - Doesn't seem necessary to select when flashing bootloaders from cold boot, so unsure of purpose.
Phone EFS Clear - Reformats your EFS partition. This deletes calibration data and some small caches, you will want to flash full stock ROM when using this so it can properly restore itself. It's safe to use, and won't wipe your IMEI.
I advise not touching the other options!
When flashing firmware, you can and should leave the default options selected. Confirm that it is just Auto Reboot and F. Reset Time.
RE-PARTITIONING
Re-partitioning may be necessary in the rare scenario that updating to a newer firmware requires more storage than is available in the current layout.
It is possible to back up your PIT file (partition layout) for flashing in Odin later on or sharing with others that are having trouble flashing firmware that you were able to successfully flash.
PIT files are model specific!
Do not flash a PIT file for N9005 on an N900W8 for example. The partition layout will end up pointing to the wrong locations and you'll end up with a blank IMEI / EFS partition or worse.
If you want to back up your PIT file, you must have a rooted phone or be in TWRP which is an environment already running with root privileges.
Executing these commands will back up your PIT to a file (your-device-name.pit) on your internal storage:
su
dd if=/dev/block/mmcblk0 of="/sdcard/$(getprop ro.product.name).pit" bs=16 skip=1088 count=257
You can open the PIT file in a text editor and make sure it starts with v˜4 to be ensure validity.
Restoring a PIT file is as simple as using the PIT tab in Odin and putting it in the box there, then selecting the Re-Partition checkbox in Options tab. Re-Partitioning will not delete any data, however if your PIT file varies from your previous then partition locations may point to completely different places resulting in a no longer functioning modem or worse, a bricked phone.
WIPING YOUR DATA FOR RESALE
You can use the Nand Erase All option in Odin to make your Userdata partition unrecoverable. When the Userdata partition is nand secure erased, all data on it becomes zeros.
In order for Nand Erase option to work, you need to fill an Odin slot. Flashing your bootloader in the BL slot is usually a safe method.
Most ROMs (kernel boot images actually) can't recover from this and will not boot. In order to fix this you have to boot into a recovery.
In TWRP: Go to Wipe -> Format Data -> type "yes" -> Go
In stock recovery: Use the "factory data reset" option
Both of these perform identical procedures that restore a proper format and ext4 layout to your Userdata partition.
ROMs should now be able to boot.
You can confirm through TWRP that your userdata partition has indeed been secure erased by typing in adb or terminal:
hexdump /dev/block/platform/msm_sdcc.1/by-name/userdata
It should display:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
After a few minutes it should complete. The asterisk means that hexdump found that same last row of data (0000...) repeating.
CHANGES
2016-02-26 - Add Nordic SM-N9005XX firmware N9005XXUGPOK2
2016-01-12 - Add SM-N9005XX firmware N9005XXUGBOL3 and N9005XXUGBOJ2 (modem)
2016-01-01 - Add Mexican SM-N900W8UB firmware N900W8UBU2DOL1 and N900W8UBU2DOK1 (modem)
2016-01-01 - Add T-Mobile SM-N900T firmware N900TUVUFOL1
2016-01-01 - Add Exynos SM-N900XX firmware N900XXUEBOL2
2015-12-18 - Add Exynos SM-N900UB firmware N900UBUEBOK1
2015-12-15 - Add Exynos SM-N900XX firmware N900XXUEBOK7 and N900XXUEBOK3 (modem)
2015-12-15 - Add Exynos SM-N900ZS firmware N900ZSUEBOK3 and N900XXUEBOK3 (modem)
2015-12-15 - Add SM-N9005DX firmware N9005DXUGBOK3
2015-12-15 - Add SM-N9005XX firmware N9005XXUGBOK9 and N9005XXUGBOD3 (modem)
2015-12-15 - Add SM-N9005ZS firmware N9005ZSUGOK2
2015-12-15 - Add KT Corporation SM-N900K firmware N900KKKU0GOK3 & N900KKKUGOJ4 (modem) (thanks to Freyelis)
2015-12-11 - Add SK Telecom SM-N900S firmware N900SKSU0GOK3 & N900SKSU0GOJ4 (modem)
2015-12-11 - Add LG Uplus SM-N900L firmware N900LKLU0GOK3
2015-12-02 - Add Sprint SM-N900P firmware N900PVPUEOK2
Why
fingerprinted said:
Why
Click to expand...
Click to collapse
Maybe I just wanna fit in with everybody else!!!!!!!!11
It just seems like a better idea to make all the latest modems and bootloaders for every variant easily available for people who don't want to wipe their custom ROMs or in case of emergencies.
Everything seems to be spread out among multiple threads, and some variants don't even have firmware threads.
Also this post gives me somewhere to send people to when I need it, regardless of what Note 3 variant they have!
Your profile made me chuckle, interests :single females
fingerprinted said:
Your profile made me chuckle, interests :single females
Click to expand...
Click to collapse
Its kinda look cute and honest. Btw,Thanks for a great work.
You are a very organized man, amazing work. Thank you
+1 very neat thread and you can get the files easily. Oh almost forgot to mention that your guide is very detailed.
There are numerous threads regarding Bootloader and Modems, but none as good as this .
Thanks for the effort mate, while this is supposed to be for Note 3, some information inside has a lot of stuff inside worthy of forwarding people to, pretty much a lot of general Samsung stuff explained.
:good:
EDIT: just wanted to add one thing. Sammy tends to confuse us, and we tend to inherit that confusion to other users. I.e, CP and BL are not consistently the same, we have right now K6 as a BL, but the modem seems still to be K1.
We should have a way to identify the real internals through *OUR* naming conventions.
guys
I am facing very low gsm signals after installing a custom rom
I cleaned flashed it wiping al that was needed
Anyway to check if i am using a wrong modem where i am located?
Question
I am having SM-n900k. Can I flash bootloaders from another model? I am sick of korean language in the download mode.
5.1.1 BL and CP?
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
HazeMC said:
I using N900W8 (hltcan) on 5.1.1 and im facing some Camera issues, some memers suggested me to update my BL.
This is my BL and CP version; n900w8UBUCNH1
im trying to flash OK6 BL and CP but odin fails every time (FAILED! auth)
(Does OK6 is a newer version? maybe thats the problem)
I've already disabled Device manager, remote controls and reactivation lock.
This:
BL UBU2DOI2
CP UBU2DOE4
are a newer version than UBUCNH1? do they work on 5.1.1?
thanks in advance!
Click to expand...
Click to collapse
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
sajmon1983 said:
Whats the lastest bootloader and modem for sm-n9005
im using cm13
now i have
CP_N9005XXUGPOF3.tar.md5
BL_N9005XXUGPOF3.tar.md5
Click to expand...
Click to collapse
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
is there any reason to update to the latest bootloader/modem?
(I use XSP firmware. haven't been able to find or make my own BL or CP files)
jcadduono said:
For N9005XX, OK6 is the latest bootloader, OJ1 is the latest modem. XXUGP series is specific to Nordic regions like Finland, Sweden, etc. only as far as I can tell.
There's probably no difference in bootloader and modem code between the XXUGB and XXUGP series.
In any case, OI2 is the latest bootloader and modem for the N9005XXUGP Nordic firmware. I will add it to the mirror soon. (it's added now)
Click to expand...
Click to collapse
I cant find the link for the differences, but apparently they do actually differ, if i'm not wrong, it has something to do with a different development tree. People have reported issues flashing non-nordic roms after the nordic ones itself, but only when the values change.
jcadduono said:
yes those are the ones you should flash if you want to update. for N900W8, CNxx is KitKat (4.4), 2DOxx is Lollipop (5.0)
OK6 is for international/N9005XX models only, which is why it failed auth, and good thing it does or you'd have bricked your phone!
your camera issues are more likely related to incompatible kernel and proprietary .so files (they need to match up)
these are a few possible paths that commands can take to the hardware, sorted by most common to least common AFAIK:
1. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> hardware
2. android -> kernel -> hardware
3. android -> translation layer & extra functions libraries (proprietary .so files) -> kernel -> firmware -> hardware
4. android -> kernel -> firmware -> hardware
see the firmware stage of communication. sometimes this firmware is included as part of the kernel, and the respective kernel drivers will flash the firmware for you if it needs updating. sometimes, very rarely, the firmware will be part of the modem or bootloader binaries instead of flashed from kernel. this is a situation where updating bootloader/modem could potentially help.
this is only from reading lots of samsung kernel sources, so some of it is only assumed. i can't know everything.
if anyone wants to share more accurate information than what i can provide, we would all be thankful!
Click to expand...
Click to collapse
Thanks for a very complete response!
I've realised that the front camera has the same issue recording video, so as far i understand you response, i will try to update the kernel, or try a different rom.
Thanks mate.
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
yes ok
jorioux said:
I flashed AP_N900W8VLU2DOH1_KERNEL.tar.md5 using Odin, on my N900W8, and when it reboot it get stuck and wont boot into the ROM. What is wrong?
Click to expand...
Click to collapse
If you are on 5.0 LL you have to use DOI2
In this thread, You can share the Mega-Links of new firmware's (OFFICIAL STOCK) for the Galaxy S8 (so: NO CUSTOM ROM's and/or ROOT-talk)...
How to flash firmware to your phone:
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
{
"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"
}
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
1. Extract (un-rar) the firmware file (i.e. to folder c:\Odin) ***
2. Download Odin v3.13.1
3. Extract Odin ZIP file (i.e. to folder c:\Odin)
4. Open Odin v3.13.1
5. Reboot Phone in Download Mode (press and hold Bixby + Power + Volume Down buttons)
6. Connect phone and wait until you get a blue sign in Odin
7. Add the firmware files to their designated slots
8. Make sure re-partition is NOT ticked
9. Click the start button, sit back and wait few minutes
Below a video with the "How to flash"; thanks @ISF for making this tutorial:
https://www.youtube.com/watch?v=2y0ZZxcNVnE
*** You can always find the LATEST firmware in msg #2
Latest Firmware Multi-CSC OXM
This ROM is the latest ROM for Multi-CSC OXM released 21 feb 18, and can be used for ALL CSC's mentioned in Multi-CSC OXM!
This is official Samsung ROM, so KNOX won't be triggered!
Change CSC for i.e. use Samsung Pay
Your data will stay intact, but it's possible you get "com.android.***** has stopped" -> Then a Factory Reset is needed (in Recovery)!
What's new:
* Android 8.0.0
* February security patches (Samsung Android Security Updates)
Samsung Experience 9.0 upgrade with Android Oreo
Samsung Experience 9.0 brings you Android Oreo, with exciting new features from Samsung and Google based on feedback from users like you.
We recommend that you back up your important data to keep it safe during the upgrade.
Some apps, including Samsung Pay, Samsung Internet, Samsung Notes, and Email, should be updated individually before you can update your OS.
Here’s what’s new.
Biometrics
To improve your security, features that use biometrics (face, fingerprints, and irises) are only available when you use a secure screen lock type (pattern, PIN, or password). When you switch to a non-secure screen lock type (Swipe or None), biometric authentication is suspended for unlocking and for verification in apps like Samsung Pay and Samsung Pass. If you're using biometrics now without a secure screen lock type, you'll be able to continue after the upgrade, but changing to a secure screen lock type is recommended.
Quick Panel
- Manage notifications for each app with notification categories (supported apps only).
- Icons will be shown at the bottom of the notification panel for notifications that aren't currently visible.
Home Screen
- Touch and hold an app to display shortcuts to common or recommended tasks within the app (supported apps only).
- Notification badges on app icons are linked with the notification panel. Clear a notification in one location, and it will also be cleared in the other location.
Samsung Keyboard
- The toolbar gives quick access to useful functions.
- The GIF keyboard lets you send GIFs.
- More high-contrast keyboards are available.
System Performance
- Background services are limited to improve performance and battery life.
- Currently running apps will always be shown in the notification panel.
Edge screen
- Improved font size, color, and other settings for better Edge panel visibility.
- Touch and hold the Edge panel handle to change its position.
- Added 3 more Edge lighting effects and color customization for apps.
Lock Screen and Always On Display
- New clock styles for the Lock screen and Always On Display.
- Adjust the transparency of notifications to get the look you want.
Smart View
- Let your phone's screen go dark when mirroring to another screen.
Samsung account
- Control your account settings and profile information for multiple apps.
- Tap your profile picture on the main Settings page to access your profile information and account settings.
Samsung Cloud
- View and manage photos and notes stored only in Samsung Cloud.
- Store any type of file in Samsung Cloud Drive.
- Select specific items to delete or restore from your backups.
- See how big each backup is and how many items it contains.
Samsung Dual Messenger
- Install a second copy of a messaging app so you can use two accounts at the same time. For apps that verify accounts using phone numbers, you'll need a different phone number for each account.
- Touch and hold a messaging app on the Home or Apps screen to install the second account or go to Settings - Advanced features - Dual Messenger.
Find My Mobile
- Back up Secure Folder to Samsung Cloud remotely when your phone is lost.
- Lock Samsung Pass using Find My Mobile.
Samsung DeX
- See more apps at once by changing the app list view to full-screen.
- Use Game launcher in Samsung DeX for a full-screen gaming experience.
- Added support for 2 additional Samsung covers (LED View Cover, Clear View Standing Cover).
Other improvements
- Bluetooth now supports high-quality audio codecs, including AAC and Sony LDAC.
- Video player includes auto repeat and 2x speed option.
- Voice Recorder provides smart tips to conveniently block calls while recording.
- Email lets you flag Microsoft Exchange ActiveSync emails.
- Samsung Health's new sticky notification lets you see your step count at a glance.
- Clock now includes a Landscape mode and timer sound options.
- The digital clock widget goes directly to the Clock app when you tap it.
- Samsung Pass added the ability to manage usernames and passwords in third-party apps.
Model SM-G950F
Model name Galaxy S8
Country Multi-CSC OXM
Version Android 8.0.0
Changelist 12993647
Build date Mon, 19 Feb 2018 14:32:41 +0000
Security Patch Level 2018-02-01
Multi-CSC OXM
PDA G950FXXU1CRB7
CSC G950FOXM1CRAP
Details for download with SamFirm:
UN-ZIP the archive and place the files in the designated slots in Odin 3.13.1
HOME_CSC_OXM -> data will stay intact
CSC_OXM -> device will be resetted (NOT included in archive for "smaller archive" due to "download limitations" MegaNZ)
This package contains the HOME_CSC of OXM Multi-CSC, which include the following CSC's: ACR AFG AFR ARO ATO AUT BGL BNG BRI BTC BTU CAC CAM CEL CHO COO DBT DKR ECT EGY EON ETL EUR GLB ILO INS ITV KSA LAO LUX LYS MID MM1 MWD MYM NEE NPL ORX PAK PCL PHE PHN PTR ROM SEB SEE SEK SER SIN SKZ SLK SMA STH THL THR TMC TPA TPH TTT TUN TUR WTL XEF XEH XEO XEU XFA XFE XME XSG XSP XTC XXV ZTO
New Multi-CSC -> OXM
The European model of the S8/S8+ (SM-G950F + SM-G955F) will get a Multi-CSC -> OXM
This Multi-CSC was already used in the Note 7, and will now be continued on the S8/S8+
OXM Multi-CSC, which include the following CSC's: ACR AFG AFR ARO ATO AUT BGL BNG BRI BTC BTU CAC CAM CEL CHO COO DBT DKR ECT EGY EON ETL EUR GLB ILO INS ITV KSA LAO LUX LYS MID MM1 MWD MYM NEE NPL ORX PAK PCL PHE PHN PTR ROM SEB SEE SEK SER SIN SKZ SLK SMA STH THL THR TMC TPA TPH TTT TUN TUR WTL XEF XEH XEO XEU XFA XFE XME XSG XSP XTC XXV ZTO
G950FXXU1AQDG (Netherlands - PHN)
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
This ROM is the latest ROM for Netherlands (PHN) released 28 apr 17, and can be used for ALL CSC's mentioned in Multi-CSC OXM!
This is official Samsung ROM, so KNOX won't be triggered!
Note: after install of this ROM, you will receive OTA-updates!
Your data will stay intact, but it's possible you get "com.android.***** has stopped" -> Then a Factory Reset is needed (in Recovery)!
What's new:
* Android 7.0
* April security patches (Samsung Android Security Updates)
* Stability Improvements
* Fix Colour optimalisation
Model SM-G950F
Model name Galaxy S8
Country Netherlands
Version Android 7.0
Changelist 11168760
Build date Tue, 25 Apr 2017 23:49:41 +0000
Security Patch Level 2017-04-01
Product code PHN
PDA G950FXXU1AQDG
CSC G950FOXM1AQDG
Download for install with Odin 3.12.3: MegaNZ
UN-ZIP the archive and place the files in the designated slots in Odin 3.12.3
This package contains the HOME_CSC of OXM Multi-CSC, which include the following CSC's: ACR AFG AFR ARO ATO AUT BGL BNG BRI BTU CAC CAM CHO COO DBT DKR ECT EGY EON ETL EUR ILO INS ITV KSA LAO LUX MID MWD MYM NEE NPL ORX PAK PHE PHN ROM SEB SEE SEK SER SKZ SLK THL THR TPA TPH TTT TUN TUR XEF XEH XEO XEU XFE XME XSG XSP XTC XXV ZTO
my s8 is not booting into download mode and i am unable to reset my phone . it says firmware restrictions applied
could you make a photo?
Thread cleaned up a bit.
Please stay focussed on the topic.
Thanks!
maik005 said:
could you make a photo?
Click to expand...
Click to collapse
http://imgur.com/a/gt84z
kalas87 said:
http://imgur.com/a/gt84z
Click to expand...
Click to collapse
What is your provider/country/CSC ?
Could you do a *#1234# and give the info after CSC (or make a screenshot)?
henklbr said:
In this thread, You can share the Mega-Links of new firmware's (OFFICIAL STOCK) for the Galaxy S8 (so: NO CUSTOM ROM's and/or ROOT-talk)...
How to flash firmware to your phone:
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
1. Extract (un-rar) the firmware file (i.e. to folder c:\Odin) ***
2. Download Odin v3.12.3
3. Extract Odin ZIP file (i.e. to folder c:\Odin)
4. Open Odin v3.12.3
5. Reboot Phone in Download Mode (press and hold Bixby + Power + Volume Down buttons)
6. Connect phone and wait until you get a blue sign in Odin
7. Add the firmware files to their designated slots
8. Make sure re-partition is NOT ticked
9. Click the start button, sit back and wait few minutes
*** You can always find the LATEST firmware in msg #2
Click to expand...
Click to collapse
How do I get the black settings menu like you have in your picture?
zach.flodman said:
How do I get the black settings menu like you have in your picture?
Click to expand...
Click to collapse
Install a "black theme" in the Theme Store ?
Can I install this if my S8 has no ROM installed and only TWRP? Can I just flash it from download mode?
fisher6 said:
Can I install this if my S8 has no ROM installed and only TWRP? Can I just flash it from download mode?
Click to expand...
Click to collapse
Yes. But you have to use the CSC_ file and NOT the HOME_CSC file.
And of course all other files (AP,BL,CP)
maik005 said:
Yes. But you have to use the CSC_ file and NOT the HOME_CSC file.
And of course all other files (AP,BL,CP)
Click to expand...
Click to collapse
Thanks for the reply, what about this warning: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
I only have access to TWRP and no*OS installed.
Ignore it. This is only if you flash with the HOME_CS to update your current original ROM and keep your data.
If you flash with normal CSC_ your device is resettled anyway..
WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
It's necessary activate pin i never did it before??
maik005 said:
Ignore it. This is only if you flash with the HOME_CS to update your current original ROM and keep your data.
If you flash with normal CSC_ your device is resettled anyway..
Click to expand...
Click to collapse
Worked like a charm! Thanks!
Great to see @henklbr on the Galaxy S8 scene with the latest Stock ROM thread.
henklbr said:
What is your provider/country/CSC ?
Could you do a *#1234# and give the info after CSC (or make a screenshot)?
Click to expand...
Click to collapse
http://imgur.com/a/A3jah
i flashed a BTU firmware from sam mobile , originally it was PAN
all functions are working but it says developer mode is enabled but not showing in the list and phone is not booting into download mode and not getting factory reset
I am stuck now it says custom FRP blocked, tried flashing stock firmware but still its not resolved any help?
Hi everybody, here is a little comprehensive guide on how to change your CSC for the Galaxy S8 & S8+.:good:
It all started when I noticed I could not use Samsung Pay (Spay). Bit by bit managed to work up some theories on how to do it on any device.
CSC(Consumer Software Customization) denotes a specific geographical region or carrier branding of your phone. Samsung verifies this in order to allow the use of Spay.
Some important notes:
1. Your phone will be wiped clean in the process, so backup important stuff.
2. Not sure if all countries support Samsung Pay.
3. Avoid partial firmware flashes, they can mess things up.
4. Be really careful picking up the right files for this process.
5. This will not trip Knox.
6. This method might work on other S8/S8+ variants, feel free to test it.
7. Most roms are Multi-CSC, so straight flashing it might not work and you can end up with another unwanted CSC.
8. You can use this guide to upgrade/downgrade from Nougat/Oreo.
Let’s begin: There are two scenarios we can start with…
1. Nougat/Oreo with Bootloader V1
2. Nougat/Oreo with Bootloader V2
About your Bootloader version:
Early 2018 Samsung launched a bootloader update (V2) mainly to fix Spectre and Meltdown vulnerabilities, as according to this XDA post. For what I know, there is no way to downgrade your bootloader version so far, so be careful selecting the files when changing your CSC.
I noticed a quick tell sign to know if your bootloader is already in V2: If you see the legend “Volume Down Key + Power Key for more than 7 secs: Cancel (restart phone)” at the bottom of the screen when in Download Mode, you are already in V2 bootloader. Otherwise you may still be in V1 (Which is way easier to find files for).
Recommended sources for the required files:
1. Firmware: SamMobile S8-S8+, Updato
2. Combination File: Firmware Gem Flash S8-S8+, Easy Firmware (I found Bootloader V2 Combination file here)
Required files:
S8 with Nougat/Oreo and Bootloader V1
• A Nougat/Oreo Firmware containing the CSC that you want, and still containing V1 Bootloader: This can be distinguished in the name of the file/firmware version, it should have G950FXXU1 on it (U1 is for Bootloader V1).
• Combination file specific for V1 Bootloader: This can be distinguished in the name of the file, it should have G950FXXU1 on it (U1 is for Bootloader V1).
S8+ with Nougat/Oreo and Bootloader V1
• A Nougat/Oreo Firmware containing the CSC that you want, and still containing V1 Bootloader: This can be distinguished in the name of the file/firmware version, it should have G955FXXU1 on it (U1 is for Bootloader V1).
• Combination file specific for V1 Bootloader: This can be distinguished in the name of the file, it should have G955FXXU1 on it (U1 is for Bootloader V1).
S8 with Nougat/Oreo and Bootloader V2
• A Nougat/Oreo Firmware containing the CSC that you want, and still containing V2 Bootloader: This can be distinguished in the name of the file/firmware version, it should have G950FXXU2 on it (U2 is for Bootloader V2).
• Combination file specific for V2 Bootloader: This can be distinguished in the name of the file, it should have G950FXXU2 on it (U2 is for Bootloader V2).
S8+ with Nougat/Oreo and Bootloader V2
• A Nougat/Oreo Firmware containing the CSC that you want, and still containing V2 Bootloader: This can be distinguished in the name of the file/firmware version, it should have G955FXXU2 on it (U2 is for Bootloader V2).
• Combination file specific for V2 Bootloader: This can be distinguished in the name of the file, it should have G955FXXU2 on it (U2 is for Bootloader V2).
Steps:
*I will assume you already have the abovementioned files.
1. Enter download mode by turning off the phone then pressing Vol Down + Bixby + Power, then press volume up.
2. Flash the downloaded firmware with the latest version of Odin (Available here):
Use the AP, BL, CP and CSC file (Not Home CSC, regular CSC).
Wait for it to boot.
3. Turn off the phone.
4. This is the tricky part:
a. Download 7zip for Windows.
b. Rename the Home_CSC that came with your firmware, removing the md5 extension and leaving it at .tar, thus making it a .tar file.
c. Expand the files in a new folder.
d. Delete a file named “Hidden”
e. Select remaining files and create a new Tar file with the name of the original .tar.md5 file with 7zip.5. Odin Flash the downloaded combination file on AP, and the newly created Home CSC tar file on CSC.
6. Boot into factory mode.
7. Select IMEI option at the bottom of the screen to bring up the dial pad, then dial *#243203855#
8. Select your new CSC code, and wait for it to install and reboot.
9. Wait for phone to reboot and clean memory.
10. Re-enter download mode.
11. Odin flash the firmware again:
Use the AP, BL, CP and CSC file (Use the recently created file again, the one without the hidden file).
12. Reboot and setup your phone.
13. You should be in the desired CSC now.
Regarding S9/s9+ method compatibility:
Not sure at all if this can be similarly done with the S9/S9+, but I would be more than happy to check that for you if you send me a test phone, lol.
Thanks to arthurbxp for all the complimenting knowledge on the matter.
DISCLAIMER:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because your phone failed. Please do some research if you have any concerns about this method and before flashing/using it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
hey mate thanks for the guide. Both websites needs paid memberships for downloading though. Any free sources?
capuagenclik said:
hey mate thanks for the guide. Both websites needs paid memberships for downloading though. Any free sources?
Click to expand...
Click to collapse
Hey there, no problem.
I would look for the name of the specific file you need and Google it. Share the name with me, I will kindly help you look for it. Plus, I might still have paid access to them, wouldn't mind sharing them with you.
Settings - About phone - Soiftware information - service provider software
Have you screenshots of that before and after?
Does the last CSC change?
And, afte I have done all that.
If I then flash a unmodified Firmware from Samsung AP,BL,CP and CSC
or HOME_CSC will that change the CSC back?
maik005 said:
Settings - About phone - Soiftware information - service provider software
Have you screenshots of that before and after?
Does the last CSC change?
And, afte I have done all that.
If I then flash a unmodified Firmware from Samsung AP,BL,CP and CSC
or HOME_CSC will that change the CSC back?
Click to expand...
Click to collapse
I don't have screenshots, but the process is very straight forward.
After all, if you flash everything and CSC you might end up with another csc(the firmware default's one). That's why at the end you should flash home CSC.
Hi / Hola
@yojosefo
Eng:
Hi!
I can see you're from Mexico, can you answer me just one doubt?
My phone is a S8 SM-G950FD with United Arab Emirates firmware, its dual SIM, with this procedure, could I lost this feature or is it compatible with muy phone, i want to change it to Mexico's firmware 'cause Spay and Members?
I was looking for V2 Combination file but I couldnt be able to find some page without "premium" downloads, can you upload it to GDrive if you have it?
Please?.
-------------------------------------------------
Spa:
Hola!
Veo que eres de Mexico, puedes responderme una duda que tengo?
Mi teléfono es un S8 SM-G950FD con firmware de los Emiratos Arabes Unidos, es dual SIM, con este procedimiento puedo perder esa función o este procedimiento es 100% compatible con mi telefono, quiero cambiarlo al firmware de mexico por el Spay y Members?
Estuve buscando el archivo de combinacion v2, pero no encuentro ninguna pagina que no tenga descargas premium, si lo tienes, lo podrias subir a Google Drive?
Por favor?
vok01 said:
@yojosefo
Eng:
Hi!
I can see you're from Mexico, can you answer me just one doubt?
My phone is a S8 SM-G950FD with United Arab Emirates firmware, its dual SIM, with this procedure, could I lost this feature or is it compatible with muy phone, i want to change it to Mexico's firmware 'cause Spay and Members?
I was looking for V2 Combination file but I couldnt be able to find some page without "premium" downloads, can you upload it to GDrive if you have it?
Please?.
-------------------------------------------------
Spa:
Hola!
Veo que eres de Mexico, puedes responderme una duda que tengo?
Mi teléfono es un S8 SM-G950FD con firmware de los Emiratos Arabes Unidos, es dual SIM, con este procedimiento puedo perder esa función o este procedimiento es 100% compatible con mi telefono, quiero cambiarlo al firmware de mexico por el Spay y Members?
Estuve buscando el archivo de combinacion v2, pero no encuentro ninguna pagina que no tenga descargas premium, si lo tienes, lo podrias subir a Google Drive?
Por favor?
Click to expand...
Click to collapse
Hi there, hope u are doing fine.
To my understanding, if possible, you will lose that functionality... You may try to find all the files required to do the change, and then keep the dual sim capability.
Can you post the required combination file to see if I still have access to the download?
Regards....
yojosefo said:
Hi there, hope u are doing fine.
To my understanding, if possible, you will lose that functionality... You may try to find all the files required to do the change, and then keep the dual sim capability.
Can you post the required combination file to see if I still have access to the download?
Regards....
Click to expand...
Click to collapse
According with my bootloader, I need B:2 (Binnary 2... I guess, Im in May patch) combination file, I was looking for it before and I get 2 files (One with 2Gb of size and other with 760Mb) but Im not sure which is the correct file.
I'll attach an image with the full information about the phone and the firmware.
{
"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"
}
And these are the combination file that I found in easy-firmware, but... I need to use FD or F? (My model is FD)
Easy-Firmware
Gem-Flash
Sorry, maybe are dumb questions but its my first time with samsung phones
Edit:
I tried to do this:
e. Select remaining files and create a new Tar file with the name of the original .tar.md5 file with 7zip.
Click to expand...
Click to collapse
And the new md5 file shows launch an error: "Md5 Error. Binary is invalid", how can I create that md5 file
vok01 said:
According with my bootloader, I need B:2 (Binnary 2... I guess, Im in May patch) combination file, I was looking for it before and I get 2 files (One with 2Gb of size and other with 760Mb) but Im not sure which is the correct file.
I'll attach an image with the full information about the phone and the firmware.
View attachment 4526211
And these are the combination file that I found in easy-firmware, but... I need to use FD or F? (My model is FD)
View attachment 4526213
View attachment 4526214
Easy-Firmware
Gem-Flash
Sorry, maybe are dumb questions but its my first time with samsung phones
Edit:
I tried to do this:
And the new md5 file shows launch an error: "Md5 Error. Binary is invalid", how can I create that md5 file
Click to expand...
Click to collapse
remove the .md5 at the End.
There is no valid md5 signature in that nee created file and that is ok.
I don't have the hidden file inside my original firmware's HOME_CSC tar file.
hey is it possible you can help me? I need the combination file for s8 g950f with v2 bootloader, uk version if that makes any difference.. the site he gave only allows me to download it with a subscription
https://www.youtube.com/watch?v=WgpR-cNQEzA
U2 combination file for 950f
Lao Mayer said:
I don't have the hidden file inside my original firmware's HOME_CSC tar file.
Click to expand...
Click to collapse
Me too, downloaded firmware few times to ensure any help?
Which FW?
Hello!
I'm a proud new owner of S8! As all of you, also suffer of not having a working samsung pay.
This is the information of my phone:
S8 Dual Sim, United Arab Emirates, just like @vok01
Product Code: SM-G950FZDDXSG
PDA: G950FXXU2CRF7
CSC: G950FOXM2CRF7
Baseband: G950FXXU2CRF1
Bootloader: G950FXXU2CRF7
I'm from Mexico, samsung pay should be working. I've downloaded this two firmwares:
Iusacell: Sam-mobile: galaxy-s8/SM-G950F/IUS/download/G950FXXU2CRF7/224757/
Which shares the same PDA number.
Telcel: Sam-mobile: galaxy-s8/SM-G950F/TCE/download/G950FXXU2CRED/221673/
PDA is different.
My carrier is Telcel. My guess is it does not matter which one I choose, but I better ask before. I'm not interested in dual sim functionality.
Edit: So, I basically need to flash the phone 3 times?
1) Normally
2) With edited files / enter IMEI mode
3) Once again with edited files
Finally was able to download the FW, but there is no hidden file within HOME_CSC
Foocampo said:
Finally was able to download the FW, but there is no hidden file within HOME_CSC
Click to expand...
Click to collapse
That's strange, in that case and if you feel adventurous you could try straight flashing it, since the hidden image file you need to remove causes an error. If you dont see the file, perhaps you will get no error...
I did the flashing process, the CSC code changed correctly, but still unable to use samsung pay:
Unable to connect to Samsung Pay temporarily. Try again later.
Maybe changing the SPay Framework?
@yojosefo
Just a couple quick questions.
I'm in the following firmware: G950FXXS3CRG1
AP: AP_G950FXXS3CRG1_CL13760092_QB18691377_REV00_user_low_ship_meta.tar
BL: BL_G950FXXS3CRG1_CL13760092_QB18691377_REV00_user_low_ship.tar
CP: CP_G950FXXS3CRG1_CP10026852_CL13760092_QB18691377_REV00_user_low_ship.tar
CSC: CSC_OXM_G950FOXM3CRG1_CL13760092_QB18691377_REV00_user_low_ship.tar.md5
AFAIK it has the new bootloader (version 3).
Do you know if that's correct?
Do you know if there is a combination file with that bootloader version I could use to change CSC?
Thank you very much for any help you could provide.
Update: These CSC files don't have the "hidden" file inside. Just like @Foocampo said.
ImpheOtus said:
@yojosefo
Just a couple quick questions.
I'm in the following firmware: G950FXXS3CRG1
AP: AP_G950FXXS3CRG1_CL13760092_QB18691377_REV00_user_low_ship_meta.tar
BL: BL_G950FXXS3CRG1_CL13760092_QB18691377_REV00_user_low_ship.tar
CP: CP_G950FXXS3CRG1_CP10026852_CL13760092_QB18691377_REV00_user_low_ship.tar
CSC: CSC_OXM_G950FOXM3CRG1_CL13760092_QB18691377_REV00_user_low_ship.tar.md5
AFAIK it has the new bootloader (version 3).
Do you know if that's correct?
Do you know if there is a combination file with that bootloader version I could use to change CSC?
Thank you very much for any help you could provide.
Update: These CSC files don't have the "hidden" file inside. Just like @Foocampo said.
Click to expand...
Click to collapse
It seems is getting harder and harder. I did a quick look up for a U3 combination and nada.
While searching this topic, I found this topic regarding U3 Bootloader limitations, I think is important to keep this in mind.
Perhaps wait for a combination file for U3 and use the same rom (if it has your wanted CSC).
yojosefo said:
It seems is getting harder and harder. I did a quick look up for a U3 combination and nada.
While searching this topic, I found this topic regarding U3 Bootloader limitations, I think is important to keep this in mind.
Perhaps wait for a combination file for U3 and use the same rom (if it has your wanted CSC).
Click to expand...
Click to collapse
That's what I'm going to do.
I'll wait for a new firmware based on bootloader v3 with MXO region, as I'm trying to use Samsung Pay but still have a bloatware-free experience.
Thanks for the feedback.
BTW: The thread you provided has been closed as the OP theory has been stated to just be a myth
Since a lot of people will have their Galaxy S22 Ultra soon and I myself am thinking about either getting an S21 Ultra or S22 Ultra, I wanted to summarise a lot of information I found out during researching as Samsung devices are quite different from OnePlus or Google devices in that they don't support fastboot but only ODIN.
If you've enjoyed it or it has helped you, a thumbs or or thanks is always appreciated! Feel free to share and link to this thread for newbies to Samsung devices like I am
Which ODIN version to use?There are a lot of ODIN versions out there. Even reputable sources seem to copy & paste files without checking them first. The lastest version is v3.14.1. Any newer version as of now is a hoax as they simply renamed the version to v3.14.4 without any changes
How to check if you have a trustworthy version?
First of all: it should be version v3.14.1.
In the ZIP file there is a file called "odin.ini". The second line should be"Title=odin“. If not, some website has changed that.
In the same .ini file there should NOT be a:
[UIOption]
LED=0
(Someone apparently ticked that checkbox in ODIN, saved it and uploaded it. The default .ini file does not contain it unless you checked it yourself in ODIN.)
In the ZIP file there should NOT be a file called "cpprest141_2_10.dll“. This is a Microsoft file that is not malicious, but doesn't belong in there.
Since most ODIN files are copy and paste, it should be easy to identify whether you have the right version or not. (Source)
ODIN: AP, BL, CP, CSCPeople love to spread information without questioning it. So I came across thing like "BL" stands for bloatware etc. No, it does not.
BL (Bootloader)
This contains all bootloader relevant files (like the BIOS on your PC). This is quite essential as a broken bootloader can brick your device permanently.
AP (Application Processor or PDA)
This contains Android and all relevant files you might know from other device manufacturers. As of now, most devices use a "payload.bin" inside the firmware ZIP. This is exactly that but you can simply unzip the .tar file without needing any tool like Payload Dumper. Though, unzipping it does not help you at all since you can't flash the .img file separately.
CP (Core Processor)
CP contains modem files. On other devices it is included in the payload.bin as "modem.img". Here it is inside CP.tar
CSC (Consumer Software Customization)
CSC contains the country and carrier specific stuff like which apps are pre-installed, which bands are available, 4G/5G, VoWiFi, VoLTE etc. Nowadays it is a multi-CSC but more on that later.
PIT (Partition Information Table)
This contains the partitions if you ever need to re-partition your device. It can be used in the PIT section in ODIN but on newer devices it is contained within the CSC.tar file. So you probably never ever have to worry about it.
(Source)
What is the deal with CSC and Home_CSC?
CSC and Home_CSC are pretty similar. They mostly contain similar files and are flashed by selecting them in the CSC slot. You never ever have or can flash both simultaneously!
CSC
Flashes the CSC part including the PIT file, meaning it will wipe the device entirely and reformat the super partition containing everything from /boot, /system and /vendor
Home_CSC
Flashes the CSC but without the PIT file, meaning it will simply update the firmware but NOT wipe your device. This is what to use for an update. Use the other CSC for a full wipe
What about F. Reset Time, Auto Reboot and Userdata in ODIN?You should not have to check any boxes if you just want to root. Some people claim to disable "auto reboot". That is a relict from the past and is copy & pasted. Disabling auto reboot will prevent the device from rebooting automatically after an ODIN flash. For stock firmwares and rooting it is not necessary. If you do not want to reboot automatically (because of a custom recovery etc.) you may disable it. But you don't need to do it for rooting.
F. Reset Time is enabled automatically and resets the flashing counter. There is no reason to not do it afaik. So you don't need to deal with that.
Userdata is not used on newer devices as it is included in the AP file and used if you use the CSC file to wipe your device. It should be left empty on newer devices.
(Source)
Multi-CSC and why changing the CSC is mostly deprecatedA lot of questions are asked everyday about the CSC. There are different CSCs for different countries and carriers. Here in Austria we have ATO (Open Austria) for unbranded devices, MAX for T-Mobile devices (now called Magenta here) and so on. Nowadays, there are multi CSC firmware like OXM. They contain many CSC codes within it.
If you go into Settings > About phone > Software information > Service provider software revision you'll find different CSC codes: AAA/BBB/CCC/DDD
AAA is the current CSC
BBB is the best CSC for SIM card 1
CCC is the best CSC for SIM card 2 (if dual SIM is possible)
DDD is the factory CSC that cannot be changed
e.g. DBT/MAX/MOB/ATO meaning DBT (Open Germany) is the current CSC, MAX (Magenta Austria) is the CSC for SIM card 1, MOB (A1 Austria) for SIM card 2 and the device has a factory CSC for Open Austria.
(Source)
With Android 12 changing the CSC is afaik impossible.
If the multi CSC contains both CSC codes (like if I want to switch from MAX to ATO), flashing the same multi CSC firmware in ODIN will do nothing as it is the same firmware.
Very important: the multi CSC firmware is the same for every CSC included. If I were to download ATO and MAX firmwares, I will get the same OXM file with the same SHA256 hash (checked it myself). Flashing it would either update your phone (Home_CSC) or wipe it (CSC) and not change the CSC as it will find your current CSC in the multi CSC and leave it as-is.
A device with XEF (France) will always be XEF even with a different SIM card. Despite showing "XEF" it will use the appropriate settings for the carrier as long as the multi-CSC (e. g. OXM) contains the necessary files.
Some builds are released only for a certain amount of CSC codes or with a different minor revision (see down below under "Firmware" for an explanation). For example: MAX has minor revision 5, but ATO has 7 now. I could flash ATO revision 7 on my MAX device, but wouldn't receive any OTA updates until I have a firmware that exists for MAX (so either I have to flash minor revision 5 or wait until the next update). Multiple CSCs can be asynchronous despite having the same base firmware. MAX could have more minor updates (e. g. the carrier wanted something fixed) while others are fine at revision 1. That's why some CSC codes have more updates listed and some receive the update earlier.
DBT for example could be the first to get the new March security patch and other CSCs will follow. Though other CSC codes might have a higher minor revision as there were changes being made afterwards. In some cases DBT will receive another update with these changes, in other cases DBT revision 3 is the latest while other CSC codes are at revision 9. The changelogs are almost always equal though so there is no information to the public on what has changed.
Think of it like an upgrade path. Major steps are always synced, but minor ones can be CSC specific until a new update syncs them again.
More information can be read here: Source
Multi-CSC Release Cycle
{
"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"
}
Multi-CSC firmwares are a "master" firmware that contains multiple CSCs. For the S21 Ultra it is called "OXM in Europe. Inside that firmware can be different regions like DBT, AUT, HUI and so on. An update usually isn't released at the same time for everyone. In this example graph above you can see how the release usually goes:
One or a few "open" CSCs for unlocked devices starts rolling out, usually DBT (Open Germany)
Other open CSCs and carrier CSCs (e. g. ATL for Vodafone Spain) start rolling out)
After that, sometimes specific carrier patches are released that increment the firmware version but is only available for a specific CSC code.
At the end of the month, sometimes minor bug fixes are also released to one or multiple CSC codes.
Next month we start that cycle again. All patches that have been released along the way are now integrated and released. (Example: HUI got an update at the end of the month, but that fix is not included in any other firmware. Next month that patch will be included along with the new security patch for every CSC).
Think of it like a GitHub project. You publish a stable release for everyone, fix a bug for a specific device, release that bug fix as a minor release only for those affected, then on the next stable release upstream that fix to the release. Doesn't make sense to include a minor hotfix immediately for a 2019 MacBook Pro if the fix is only for the 2022 MacBook Air, right?
In that regard: you can always flash any OXM firmware on a device using OXM. I could flash a DBT (Open Germany) firmware on an ATL (Vodafone Spain) device and it will work. I can even grab the security patch release at the beginning of the month before it is widely rolled out and flash it using ODIN.
People saying how happy they are because they get their updates early or others who complain about waiting weeks for it. The latters ones could fix it by manually flashing the released firmware. But keep in mind: if you still can receive software updates on your device (e. g. not rooted) then you need to be on an update path that is supported.
Say I update to the carrier fix release intended only for HUI on my DBT device. It'll work and I can update next month with ODIN as usual. BUT: Samsung's on-device software update won't show any update. Why? Because it checks DBT and if I'm on a minor release not intended for DBT, it won't give me an update path. It will search for an update from release A to release B but by flashing the carrier fix only for HUI, I'm between those. Something like A1. Since DBT doesn't have an update path from A1 to B, it won't show any updates until I'm back on B (and ready for B > C next month and so on).
Tripping KNOXIf you unlock your bootloader, KNOW will be tripped. I'm simply gonna quote another post here as it explains the impact very well (and I hereby explicitly state that I'm not affiliated in the service the source advertises. I do not vouch for or endorse the use of UNSAMLOCK).
- Knox will be tripped after a custom binary flash.
- Samsung Pass, Samsung Pay will never work after root. Safetynet, Samsung Health and Secure folder could be fixed.
(Source)
Click to expand...
Click to collapse
So if you flash a signed Samsung firmware, it shouldn't trip KNOX. If you flash an unsigned firmware, it will trip it. But as a general rule of advice: signed firmware are flashable in ODIN with a locked bootloader. If you unlock the bootloader, you are at risk of tripping KNOX and you are responsible for that happening either way. No matter what I or someone else says on XDA or any other website. So never unlock the bootloader if you can't accept tripping KNOX.
People say it is a physical fuse that is blown. I can't confirm if this is true but it could also simply be a part of security key stored within the device and deleted when unlocked. Since there is no way of backing it up, it will be lost for good (much like the /persist partition on devices that contains sensor data and is unique and never deleted or else your device becomes messed up permanently). There is no way of knowing but keep that in mind.
Firmware
Firmware versions
The firmware numbers actually have meaning. Something like "G998BXXU4BVB1/G998BOXM4BVB1/G998BXXU4BVB1" means build version/CSC version/baseband version.
The first letters are the model version (G998B = S21 Ultra). The last letters (e. g. G998BXXU4BVB1) can be read as follows:
U4 B V B 1
↓ ↓ ↓
Boot loader version
Android version
Year
Month
Minor revision
For this example that means:
U4: bootloader version 4 (you can't use any firmware with a lower version than what you have)
B: Android version 2 (for the S21 Ultra that shipped with Android 11, B is Android 12)
V: 2022 (W = 2023, X = 2024, etc.)
B: February (A = January,..., L = December)
1: minor revision 1 (this is a hexadecimal that can be 1–F, with F being version 16)
The firmware information including the colour coding comes from the CheckFirm app (Source). The provided information and the colour coding is awesome so I took that information and condensed it even further.
How do I check for firmware updates?
There are websites out there listing/hosting the firmware files that are easy to find. Other methods are:
CheckFirm: https://play.google.com/store/apps/details?id=com.illusion.checkfirm
You can try to scan for a new firmware. It uses other users to find a new firmware but according to the dev, it might be able to scan automatically in the future (though no ETA)
Use Samsung's own version.xml: https://fota-cloud-dn.ospserver.net/firmware/DBT/SM-G998B/version.xml
This is an example (replace DBT with the CSC code and SM-G998B with your model version. It will list all firmwares with the newest firmware number at the top.
Use Samsung's changelog: https://doc.samsungmobile.com/sm-g998b/dbt/doc.html
This is an example (replace DBT with the CSC code and SM-G998B with your model version.
Or ultimately use a firmware downloader like Frija on Windows, SamloaderKotlin on Windows, macOS, Linux or Android (thanks @alecxs) or something that requires a bit of setup though works on non-Windows devices aswell like samfirm.js (NodeJS) or Samloader (Python).
(Thanks to topjohnwu for listing those firmware downloading options: source)
Rooting, OTA updates while being rooted and what not to doThere is a lot of misunderstanding regarding rooting and OTA updates afterwards. I'm not explaining how to root your device. There are a lot of XDA threads out there. But I'm going to explain some important information that is not explained well very often.
When is your bootloader acutally unlocked?
Simply toggling "OEM unlock", going into download mode and unlocking the bootloader will not actually unlock it. There is a reason why after enabling the bootloader unlock in download mode, you should go to the developer settings and "confirm" it.
By opening up the developer settings and checking the "OEM unlock" toggle, the bootloader actually becomes unleashed and accepts non-signed images. Meaning an AP file modified by Magisk will now be accepted. If you do not do this, it will not.
If you flash in ODIN, always flash AP, CP, BL and CSC!
As explained by topjohnwu: if you just flash the modified AP file to root your device without selecting CP, BL or CSC, ODIN could shrink the /data partition. Always flash all of them (not like on other devices "fastboot boot boot.img" but everything!
OTA updates are gone...sort of
If you are rooted, you can't use Samsung's built in OTA updater anymore. That's why you should update your firmware before rooting. You can and may update it via ODIN though:
Patch the AP file in Magisk
Flash the modified AP, CP, BL and Home_CSC (HOME_CSC NOT and I repeat NOT the normal CSC)
Let it reboot and you're up-to-date
(Source)
Do not restore the stock boot image!
topjohnwu also states to not flash the stock boot image (stock AP) as it could brick your device. There should be no reason to unroot (you can leave Magisk and simply not use it). If you flash the stock AP, your device won't boot (probably because it fails to verify the unmodified system). I could flash the modified AP (with CP, BL and Home_CSC) back and it worked fine but YMMV. And what if you've installed some module and you're bootlooping now?
I'm in a bootloop!
Since TWRP never supported decryption on Samsung devices (thanks @alecxs) and you probably don't want to stay unencrypted, you can't use TWRP. There are two ways of fixing a bootloop caused by a Magisk module:
Via ADB debugging:
Use adb on your PC (lot of tutorials out there), and type in:
adb shell
magisk --remove-modules
However: that requires you to have adb debugging enabled and to have your PC already confirmed as a computer that is allowed to connect via adb. If you have not done this, do this:
Boot into safe mode:
Much like Cydia Substrate back on the iPhone, you may disable Magisk and its modules during boot:
If you use the device's hardware keys to boot into safe mode by pressing certain keys during booting (look it up, it varies from device to device. It can be volume up/down etc.), Magisk will disable all modules and you can remove them safely without every having to need TWRP, enable ADB debugging beforehand or needing to start from scratch. Everything is explained in the source link down below.
(Source)
Does my device have a ramdisk or not?
Most threads you find about this were at a time when some devices had it and other didn't. To stop you from searching hours about whether this is the case for the S21 or S22 series: they have a ramdisk and system-as-root. There is no need for hijacking the /recovery partition and always boot into recovery to boot into the system with root. You can just root your device with the patched AP file and you're good to go!
Just please stop wiping /cache in recovery!There is no use in wiping /cache in recovery. It is simply a cache partition for updates and is not used on a live system. There is no use in doing that and you're just wasting your time. But there is a cache that can be wiped and rebuilt: the dalvik-cache. (Source)
Dalvik cache/ARTThis is no Samsung specific but actually very good to know:
Android converts system apps in the background since Android 10 I believe. Meaning that the system apps are only really optimised, if the Dalvik cache has been built. This doesn't apply to user apps from the Play Store as they are re-compiled during installation. When does Android do this?
If your device is at 100%, plugged in and not in use. But if you're like me and not charging your device past 80%, it will not be built(!)
To force it, the easiest solution is to use Galaxy App Booster which does exactly that: https://galaxystore.samsung.com/pre...session_id=W_2323c8f409a1da0534d7dcad55e671fb
Or you can force it with root or via adb without root, you can use "adb shell" and then enter:
Code:
cmd package bg-dexopt-job
after an update and it will populate /data/dalvik-cache with arm and arm64 folders.
After an update, you can (but don't have to) delete the folders "arm" and "arm64" inside /data/dalvik-cache (DON'T DELETE the "dalvik-cache" folder itself), reboot and then execute the command above in a terminal with root access. This is the only relevant caching that Android does. It has nothing to do with /cache.
You may also check the folder: usually there are about 200+ files inside arm64. If you've only got a few dozens, the cache probably hasn't been built yet. Keep in mind that since Android 11 building the cache doesn't take a few minutes like Android 10 but sometimes half an hour or an hour as it uses few resources to not slow the device down during optimisation. That makes it quite user-transparent.
Fix Netflix, Amazon Prime,... playback issuesOn my OnePlus 7T Pro I had no issues using any of these services (if MagiskHide or now Zygisk is active). Though on my S21 Ultra it always failed to play whatever I did. Turns out that Widevine L1 is good as long as you're not rooted. It works with an unlocked bootloader but fails if you have installed Magisk no matter what you do.
Turns out there is a Magisk module called liboemcrypto disabler by @ianmacd which essentially removes the file and forces Widevine L3 for as long as the module is active. With this module I could get every streaming app to work again including my cable company's own TV app. You won't have anything higher than SD quality but I have to admit that Netflix and Amazon Prime look okay. It definitely is better than nothing and I just found this by coincidence.
So if you experience playback issues while being rooted, give this module a try
Note: Since the Magisk repo is obsolete, the only flashable ZIP I've found is from a fork found here: https://github.com/ScRuFFy7/liboemcryptodisabler. You can create the module yourself though, but for a flash-and-forget-ZIP this is the only ZIP I could find.
General InformationLast, but not least: Samsung devices aren't A/B devices. There is no mirrored partition or anything else. You just have your good old super partition and if it is messed up, you need to reflash it. No A/B stuff here.
I may update this thread in the future
Reserved
Reserved 2
Macusercom said:
Reserved 2
Click to expand...
Click to collapse
Spoiler: Hey!!
Macusercom said:
Reserved 2
Click to expand...
Click to collapse
Hi
Good info for new samsung usres!
Have you any report anyone have rooted Exynos as well SD with routine magisk patched methos? I have seen another thread how to root but I think no one yet confirmed (unless I have missed)
dr.ketan said:
Hi
Good info for new samsung usres!
Have you any report anyone have rooted Exynos as well SD with routine magisk patched methos? I have seen another thread how to root but I think no one yet confirmed (unless I have missed)
Click to expand...
Click to collapse
Thanks!
I don't think so. We'll have to wait and see if a new Magisk update is needed but since Android 12 works fine on the S21 Ultra, I don't think the S22 Ultra wouldn't work. But as of now, I have not read anything about a successful root but also nothing about not being successful.
Macusercom said:
Thanks!
I don't think so. We'll have to wait and see if a new Magisk update is needed but since Android 12 works fine on the S21 Ultra, I don't think the S22 Ultra wouldn't work. But as of now, I have not read anything about a successful root but also nothing about not being successful.
Click to expand...
Click to collapse
Thanks for info. Yes, I don't expect too that it won't work but we never know when samsung give us surprises!
One major thing I have noted on S22 is system partition is now having f2fs format instead of ext4 and as of now we can't extract stock firmware because of this. (I don't know if any available tool can do it)
dr.ketan said:
Thanks for info. Yes, I don't expect too that it won't work but we never know when samsung give us surprises!
One major thing I have noted on S22 is system partition is now having f2fs format instead of ext4 and as of now we can't extract stock firmware because of this. (I don't know if any available tool can do it)
Click to expand...
Click to collapse
Dr. ketan: Does f2fs format affect magisk root?
donkeyman1234 said:
Dr. ketan: Does f2fs format affect magisk root?
Click to expand...
Click to collapse
No, it shouldn't.
Glad to hear that.
dr.ketan said:
No, it shouldn't.
Click to expand...
Click to collapse
dr.ketan said:
Thanks for info. Yes, I don't expect too that it won't work but we never know when samsung give us surprises!
One major thing I have noted on S22 is system partition is now having f2fs format instead of ext4 and as of now we can't extract stock firmware because of this. (I don't know if any available tool can do it)
Click to expand...
Click to collapse
I've just checked the AP file of the S22 Ultra firmware. Magisk is able to patch the boot.img and goes straight through.
Not(e) S22 Ultra specific, but good to know (sorry for the pun )
Magisk can patch the extracted boot.img without lz4
Magisk can't patch boot.img.lz4
Magisk can patch the AP.tar that included boot.img.lz4 and stores it without compressing in the modified AP.tar
Hasn't f2fs been adopted way earlier with the Note 10? I can't seem to extract the S21 Ultra or S22 Ultra firmware with EXT4 extractor in any case. I can just decompress lz4
Macusercom said:
I've just checked the AP file of the S22 Ultra firmware. Magisk is able to patch the boot.img and goes straight through.
Not(e) S22 Ultra specific, but good to know (sorry for the pun )
Magisk can patch the extracted boot.img without lz4
Magisk can't patch boot.img.lz4
Magisk can patch the AP.tar that included boot.img.lz4 and stores it without compressing in the modified AP.tar
Hasn't f2fs been adopted way earlier with the Note 10? I can't seem to extract the S21 Ultra or S22 Ultra firmware with EXT4 extractor in any case. I can just decompress lz4
Click to expand...
Click to collapse
Yes, file can be patched with magisk, still we need to confirm if patched file working fine or not as no one yet confirm it (at least in my knowledge)
F2fs adopted earlier was for "data" this is first time for "system" (and also for "vendor")
Since oneui 4.0 recent update I have seen S21 also added support for system f2fs (fstab showing both) but yet still system is ext4 formatted and that's why no issue extracting S21 firmware (just two days ago I released rom with latest base VB1 Feb security patch)
dr.ketan said:
Yes, file can be patched with magisk, still we need to confirm if patched file working fine or not as no one yet confirm it (at least in my knowledge)
F2fs adopted earlier was for "data" this is first time for "system" (and also for "vendor")
Since oneui 4.0 recent update I have seen S21 also added support for system f2fs (fstab showing both) but yet still system is ext4 formatted and that's why no issue extracting S21 firmware (just two days ago I released rom with latest base VB1 Feb security patch)
Click to expand...
Click to collapse
Also, Samsung removed the system_ext folder and put it into its own img file. I mounted both system.img/system_ext.img, and copied both into an N20U system folder created by superr kitchen for my N20U. I was able to deodex framework-res.apk ans SystemUI.apk. I made mods to SystemUI, but cannot test as I do not have an S22U.
gcrutchr said:
Also, Samsung removed the system_ext folder and put it into its own img file. I mounted both system.img/system_ext.img, and copied both into an N20U system folder created by superr kitchen for my N20U. I was able to deodex framework-res.apk ans SystemUI.apk. I made mods to SystemUI, but cannot test as I do not have an S22U.
Click to expand...
Click to collapse
What you have used to extract system.img of S22?
dr.ketan said:
What you have used to extract system.img of S22?
Click to expand...
Click to collapse
superr kitchen. will extract .img files but will not extract contents
gcrutchr said:
superr kitchen. will extract .img files but will not extract contents
Click to expand...
Click to collapse
What I mean is how you have extracted SystemUI and Framework-res , as kitchen not able to extract it
dr.ketan said:
What I mean is how you have extracted SystemUI and Framework-res , as kitchen not able to extract it
Click to expand...
Click to collapse
I used Fedora to mount both .img files.
After copy S22 system.img/system_ext contents into N20U folder, I used superr to deodex system folder. Then copy SystemUI.apk and framework-res.apk to my development folder
sudo mount -o loop system_ext.img tmp
sudo mount -o loop system.img tmp2
As a general information in case anyone was wondering. Root on the S22 Ultra GM-S908B variant has been confirmed: https://forum.xda-developers.com/t/...-firmware-noob-friendly.4404283/post-86473679
Just to update : Today have got hand on demo and I can confirm indian users will get S908E and also OEM unlock option already available in dev settings out of box.
Question: I'm looking to get a newer laptop and was looking at the Surface Pro 7 or 8. I know ODIN won't work on the Surface Pro X, but has anyone used it on a SP7/8? I can't see why it won't work. It uses the same i5 processor and 64-bit OS as a full size/normal laptop.