Database Info

Stock KitKat XXUEND6 Multi-CSC N9005 [GUIDE, ROOT, FIXES, MIRROR - ALL IN ONE PLACE]

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.

Root @ No.1 X6800 (Rugged IP-68 phablet from China)

I tried a Chinese manufacturer
Company = No.1
Model = X6800
{
"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"
}
It's running Android 4.4.4 seems to be 64bit.
Here the official website of that rugged IP-68 (dust,water,shock -proof) smart-phone.
Tech details from their website:
Generales
Model NO.1 X6800
Platform MSM8916 (Snapdragon 410)
CPU frequency 1.3GHz
Operating system Android 4.4.4
ROM 8GB
RAM 1GB
Operation frequency GSM/ 850/900/1800/1900 ; 3G WCDMA 850/900/1900/2100; FDD-LTE: 2100/1900/1800/1700/850/2600/900/800
SIM Dual card dual standby (1 Micro SIM, 1 SIM-4G)
Screen 5.5"
Touch screen Yes
Rear camera 13.0M
Front Camera 5.0M
Bluetooth Bluetooth 4.0
FM Radio Yes
Expansion T-Flash / MicroSD card support 128G
USB Yes,5PIN USB, USB2.0
GPS/AGPS GPS; AGPS;
Wi-Fi Yes; 802.11 b/g/n,Support Hot spot
Flashlight Yes
Light-sensor Yes
Proxy-sensor Yes
G-Sensor Yes
Light-sensor Yes
Proxy-sensor Yes
Feature
Waterproof Support, IP 68
Dustproof Yes
Light-sensor Yes
Pressure proof Yes
Freezeproof Yes
Shockproof Yes
Scratch Proof Yes
High-temperature proof Yes
Machinery Features
Size(L*W*H) 164*88*19.2mm
3.5/2.5mm standard audio jack 3.5mm
Battery 6000 + 800 mAh batteries
USB Port 5pin USB
The manufacturer say (logically) If you change software like update or root then their is no warranty. So that's why i want to inform here what the safe options are to root this rugged phablet..
Anyone got this awesome device rooted in a safe way?

Solved !
My No.1 - X6800 is rooted with original stock rom still on it (Android 4.4.4)! Wohoo :angel:
It was easy to realize a way without the need of a computer: KingRoot and SuperSumePro :
(step 1) First use latest KingRoot app (click here to get their)
It can be that Kingroot seems to be jammed at the end, just re-use the root function and it will root the X6800.
After that kingroot rooted the No.1 X6800 :
(step 2) Use the program Super Sume pro (click here to get their)
SupersumePro cost a little bit, but then the X6800 is always rooted with SuperSU root access manager on stock pre-installed rom. (No.1 website doesn't have a 'firmware download' of the X6800 ... yet.)
Has to do with the fact that not everybody is sure about the logging of your device what KingRoot does. Some people do prefer to switch a.s.a.p. to SuperSU instead of keep using KingRoot.
(but big thanks to kingroot to be able to root the device in first place)
ALSO BE SURE TO READ WHAT IS WRITTEN IN APP STORE AT SUPERSUMEPRO, BECAUSE IT"S NOT ONLY ABOUT NOTE4.
I quote:
Warning: Do NOT remove apps from /system/apps or /system/priv-app or it could cause issues. Block them instead from either the command line or with Debloater.

Hi everybody
Please, can you send me folders system/app and system/priv-app from this phone? I cleaned some apps and accidently lost backup of these folders My email is [email protected]
Thank you for help.
Libor

jenkalibor said:
Hi everybody
Please, can you send me folders system/app and system/priv-app from this phone? I cleaned some apps and accidently lost backup of these folders My email is [email protected]
Thank you for help.
Libor
Click to expand...
Click to collapse
I think It's a default Android 4.4.4.
What file manager did you use? Becuase the default file manager doesn't have access to those directories. (not even with a rooted device)
I'm uploading the directories to my Linux computer now with SFTP, but i'm first going to find out if their is any personal info in it. If so then it's a no-go.
Damn you're a lucky guy. Here we go:
Click here for No.1 X6800 system-app
Click here for No.1 X6800 system-priv-app
(ask me for decryption keys)
Useful thing:
Do ask No.1 for a recovery image. I did it too, if we all do then they maybe offer a firmware download for X6800.
Because they do offer downloads with 'firmware' of other models.
I send a email towards their sale = [email protected] and marketing = [email protected] . I cannot find other contact ways then calling on their website.

Hi
I am using Root Explorer, there possible copy/move files in all locations in the phone (with root access of course). Also Total Commander has root permissions, you can try it, it's free.
In these folders are stock app only and they are not touching by using phone (not including any user's data) - you can check their dates. But naturally - recovery image is the best way, I can extracted these apps from there OK, let's wait for official stock ROM.
If you want try handling some apps from/to keep in mind - permissions of apps in these folders must have rw-r--r-- (long tap on app in root explorer -> permissions)

I only use FtpCafe app to goto those directories (transfer them over SFTP to computer to make changes on computer, and transfer it back. That way i always have a backup on computer.
If i use filemanager with rootacces, then I can mess up the system on the X6800 too easily :silly:

jenkalibor said:
Hi
I am using Root Explorer, there possible copy/move files in all locations in the phone (with root access of course). Also Total Commander has root permissions, you can try it, it's free.
In these folders are stock app only and they are not touching by using phone (not including any user's data) - you can check their dates. But naturally - recovery image is the best way, I can extracted these apps from there OK, let's wait for official stock ROM.
If you want try handling some apps from/to keep in mind - permissions of apps in these folders must have rw-r--r-- (long tap on app in root explorer -> permissions)
Click to expand...
Click to collapse
Check your messages. I just send the decryption keys of Mega.
If you can't extract the tar files, and got a windows hell, use 7zip.
And do email No.1, if we X6800 users all do they probably put the firmware online on their downloads site. (I'm a satisfied user of the X6800)

Hello x6800 owners
I started the post: http://forum.xda-developers.com/android/help/1-x2-root-problems-t3107357
I wanted to give any owners/buyers or potential buyers a heads up about this device and link you to my post because the x2 and the x6800 are the same (-battery size and backup battery)
1) the x2 and x6400 are 64-bit hardware with 32-bit kernel (unless there was any update I missed) check with videos of the device on youtube reviews if you don't own, watch for reviews that show benchmark results from Antutu or run this test if you own the device.
2) battery size is a huge 2000mAh- whatever they say, the x2 is advertised as 4000... try 2000 as I have tested. the x6800 is the same, 6000main battery (sticker in videos says 5000) tested by Russians and other users at 4000mAh. the backup is most likely less than 800mAh as well.
3) No.1 wont support warranty claims no matter how you contact them (I and several others have tried after buying from the non genuine shop that claims it is genuine who wont help you). So buy from shops that use PayPal so you get the 180 protection or buy from a store you know and have used for a warranty claim or a shop that is located in your country and have a real 1 year warranty under government law (Australia 1 year anything bought from within Aus)
4) Camera is only 7.7 on my x2 (they use interpolation/upscaling to hit 13MP - meaning software/hardware is making up pixels from your 7.7 Mega pixels based on one of the cheap interpolation techniques... meaning quality is better if you use the 8 MP stock setting or 7.7 (in the "a better camera" apk).
5) water proof of IP68 is a stretch too based on my experience, so don't stick it in water for more than 0 seconds. mine was repaired after falling and coming out the bath immediately, and it came back in a slightly better state but still after less than a min in a swimming pool and now it has no touch capability.
6) no google support - so no movies or youtube for google movie or youtube purchased videos. google apk from 3.x.x version (forget which one) will run but needs some help to get through a video purchase such as hitting "try again" many times.
I doubt the "crush proof" rating on my x2 after having opened up this device and seeing how flimsy it is.
I hope you find this useful
I do like the phone but I am trying the blackview bv5000
read the forum link on the X2 as the issues will be the same and if you want a 64bit phone with 64bit OS try the No.1 x2i or dive in with me and try a blackview bv5000
markatkins

X1 and X2 are smaller/flatter then X6800. So maybe a bit more weak. The Blackview is way more fragile then No.1 X6800.
(1) how can i see if it has 64bit kernel/software. 32bit is fine. I mean look at desktop/server usage, 64bit has only impact when memory is bigger then 4 Gigabyte, and when you use heavy apps who need it. A Phablet rarely need 64bit power. But hey, that's my opinion.
(2) Can you give sources? Besides, any rechargable battery get less capacity everytime it's charged. Here it runs 3 days, or one and a half intensive day.
(3) For warranty, you need to contact the seller, not the manufacturer.
(4) Do you've sources about the pixels of the camera's. (but you're talking about another model, not the X6800)
(5) My X6800 has been 5 minutes under water, without any problems. Also being outside in the Dutch rain, no problem. Of course you must be sure that the rubber flaps on power & headphone sockets are closed.
(6) No google support? I have google support here. I installed youtube without any problem. (i don't buy movies on youtube, i download them)
Only thing i want is...Some tool to fully backup to a rom image.
Original bootloader (turn it on with volume up + powerbutton) has only update , factory reset and wipe cache options.

Meanwhile I give it a try to start from scratch in learning how to create a custom rom for the X6800.
I prefer Cyanogenmod (I like the privacy settings).
If someone else have the combination:
-having a No.1 X6800 device
-having CM rom creation skills
Then feel free to give a reply here on Cyanogenmod forum.
Because i really need to learn everything from scratch as enduser, and i don't have a factory default rom (No.1 just don't reply to rom requests). So I'm extremely careful, i don't want to brick my X6800 because i make a mistake in creating CM image.

Ok folks...Forget it.
My No.1 - X6800 is already broken.
The outside is really strong. Nothing wrong with that.
But the inside of the X6800 is like playmobil.(fragile as low budget Chinese electronics)
My X6800 fall out of my hoody. Dropped down like 40 centimeters on a hard floor, and the phone is perfect from the outside, but it sucks from the inside.
The speaker is broken, and it doesn't vibrate anymore. So a phone that is useless to get a telephone call, unless you want to look at the screen constantly..
So bye bye No.1 X6800.
Ooh and the company No.1 is not cool. If you try to contact them in China they never give a answer.
Now i try a CAT S40... Slow cpu (snapdragon 210) , low pixels of screen and camera, but rugged as hell with Android 5.1.

Exit No.1 - X6800.

ROM Official NO.1 X6800 version_S517_YUTONG_X6800_RM68200_GT9157_OV8865_GC2235_M012_d157783_CS_20150831120025
ROM Android 4.4.4 NO.1 X-MEN X2 QMSCT flash
QMSCT flash-ROM Official NO.1 X-MEN X2 version: S517_YUTONG_A8_X2_RM68200_FT5336_OV8865_GC2235__CS_20150129095439
---------- Post added at 01:07 AM ---------- Previous post was at 12:47 AM ----------
TWRP 2.8.7.0 NO.1 X6800
TWRP 2.8.7.0 for NO.1 X6800.zip

ALBERJ said:
ROM Official NO.1 X6800 version_S517_YUTONG_X6800_RM68200_GT9157_OV8865_GC2235_M012_d157783_CS_20150831120025
ROM Android 4.4.4 NO.1 X-MEN X2 QMSCT flash
QMSCT flash-ROM Official NO.1 X-MEN X2 version: S517_YUTONG_A8_X2_RM68200_FT5336_OV8865_GC2235__CS_20150129095439
---------- Post added at 01:07 AM ---------- Previous post was at 12:47 AM ----------
TWRP 2.8.7.0 NO.1 X6800
TWRP 2.8.7.0 for NO.1 X6800.zip
Click to expand...
Click to collapse
MANUAL ACTUALIZACION NO.1 X-men X2, X6800.pdf

TUTORIAL ACTUALIZAR MEDIANTE RECOVERY TWRP
Backup hecho con TWRP de la ROM Original que venia instala.
da y de la ROM Actualizada. Con ROOT.
Para instalar TWRP por ADB, entrar en modo FastBoot encender el teléfono manteniendo el Botón Volumen MENOS pulsado a la vez que la de Encendido. Para salir del modo FastBoot mantener pulsado el botón de Encendido hasta que se reinicie.
Entrar en modo Recovery encender el teléfono manteniendo el Botón Volumen MAS pulsado a la vez que la de Encendido
Backup TWRP Original y Actualizado ROMs X6800

@jeroensky
I had the same problem with mine after falling on a hard surface. However I was able to fix it. After disassembling the phone completely I found a ribbon cable that got disconnected from the main board. After reconnecting everything was working again.
Definitely not the best design for a rugged phone but it's great for the price. Also the water proof works but I'd recommend to check all the seals before trying it.

A530F | Repacked stock firmware "All In One" by hypo59 | OXM CSC | Odin3

Hello guys !
Comfort level of this thread: ★ ★ ★ ★ ☆
Below you will find my "All In One" 4CSD4 OXM package, based on the multi CSC A530FXXU4CSD4 stock firmware. In order to live a better PC experience with Odin3, I have repacked the original package. It integrates:
userdata component suppression (third party apps will not be installed during flashing process: see end of post for apps list)
rebuilt AP/BL/CP tar.md5 archives in one single tar.md5 archive
Samsung USB drivers v1.5.65.0 installation file
Odin3 v3.13.1, prepared for avoiding bad usage (.ini file modification)
Home (data keep) & CSC (data wipe) tar.md5 archives
All components are untouched, it is just a reorganisation of them. Moreover, "untouched" also means flashing process will not tamper your knox, so if your knox is 0x0 before flash, it will be knox 0x0 after
Here are the firmware features:
Android version: Pie 9
build date: 2019-04-05
changelist: 15784452
PDA version: A530FXXU4CSD4
modem (CP) version: A530FXXU4CSD4
bootloader (BL) version: A530FXXU4CSD4
CSC version: A530FOXM4CSD4 (available CSC: see end of the post)
fingerprint: samsung / jackpotltexx / jackpotlte: 9 / PPR1.180610.011 / A530FXXU4CSD4: user / release-keys
security patch date: 2019-04-01
kernel version: 4.4.111-15784452
To flash, just use Odin3 within my package (install Samsung USB drivers before if not done yet):
fill AP with AP.BL.CP.[...].tar.md5 archive
fill CSC with Home[...].tar.md5 archive if you want data keep, or with CSC[...].tar.md5 archive if you choose data wipe
Download link: https://mega.nz/#F!10YA0KQI!H5bumLtA856IlEk8iZxGfQ
sha512 fingerprint: c937c1925ba976ba366b424999ed3acdea8113fd321eeac19bcb855b016dd6b75dec9a4d37cf408a72d517b1eb77f6196e2d240c9998c24eb983b32303c9bc1c
Have fun !
Available CSC: ARO, ATO, AUT, BGL, CAC, CHO, COO, DBT, EON, EUR, ITV, NEE, ORX, PHE, PHN, ROM, SEB, SEE, SEK, SER, SKZ, TPA, TPH, TTT, XEF, XEH, XEO, XEU, XEZ, ZTO, BTU, CPW, TEB
Apps list included in userdata component (so won't be flashed, as explained above):
Google Drive https://play.google.com/store/apps/details?id=com.google.android.apps.docs
Google Duo https://play.google.com/store/apps/details?id=com.google.android.apps.tachyon
Google Photos https://play.google.com/store/apps/details?id=com.google.android.apps.photos
Samsung Calculator https://play.google.com/store/apps/details?id=com.sec.android.app.popupcalculator
Samsung Email https://play.google.com/store/apps/details?id=com.samsung.android.email.provider
Samsung Health https://play.google.com/store/apps/details?id=com.sec.android.app.shealth
Samsung Internet Browser https://play.google.com/store/apps/details?id=com.sec.android.app.sbrowser
Samsung Members https://play.google.com/store/apps/details?id=com.samsung.android.voc
Samsung Music https://play.google.com/store/apps/details?id=com.sec.android.app.music
Samsung Notes https://play.google.com/store/apps/details?id=com.samsung.android.app.notes
Samsung Pay https://play.google.com/store/apps/details?id=com.samsung.android.spay
Samsung Video Library https://play.google.com/store/apps/details?id=com.samsung.android.videolist
Samsung Voice Recorder https://play.google.com/store/apps/details?id=com.sec.android.app.voicenote
SmartThings https://play.google.com/store/apps/details?id=com.samsung.android.oneconnect
All AIO packages within this thread (by date, newest first)
U9 CTA4: https://forum.xda-developers.com/showpost.php?p=81770383&postcount=76
U8 CSK3: https://forum.xda-developers.com/showpost.php?p=81139243&postcount=57
U7 CSI3: https://forum.xda-developers.com/showpost.php?p=80446421&postcount=42
U7 CSH4: https://forum.xda-developers.com/showpost.php?p=80143946&postcount=39
U6 CSF6: https://forum.xda-developers.com/showpost.php?p=79827464&postcount=38
U5 CSE3: https://forum.xda-developers.com/showpost.php?p=79583255&postcount=31

info
thanks for everything
I would like to know using odin where I put the files?
if on BL or AP etc.

Hello ! Just put it on AP, then go flash.

hypo59 said:
Hello ! Just put it on AP, then go flash.
Click to expand...
Click to collapse
sorry for my ignorance but there are two rows
are they the same?

Two rows ? Can you be more precise ? A screenshot would be great to see what you are talking about. Thanks.

hypo59 said:
Two rows ? Can you be more precise ? A screenshot would be great to see what you are talking about. Thanks.
Click to expand...
Click to collapse
they are only duplicates on Mega
okay thanks

No duplicate on MEGA: one is Home and one is CSC. Make your choice.

I've just renamed files in Mega for easy access. Thanks for your point :good:

Something wrong in Odin3 compatibility: links temporary removed until resolution (few days).

Hi guys !
I am working on the 4CSD4 firmware, more recent than 4CSC6 one, completely rebuild for better PC experience with Odin3.
It will integrate:
# userdata component suppression (third party apps not installed during flashing process)
# rebuilt AP/BL/CP tar.md5 archive
# Samsung USB drivers installation integration
# Odin3 v3.13.1 integration, prepared for avoiding bad usage
# Home & CSC tar.md5 archives
I have successfully tested it on my A8 2018. I should share it to you soon in the week.
For now: no Heimdall version yet, I will build it next.

Done ! I have modified thread title because of use of new firmware (4CSD4) and use of just Odin3 for now (not Heimdall yet), and I have completely modified first post. Sorry for inconvenience.

Do I wonder if this firmware can be applied to the SM-A530F? I want to change CSC to XXV, do you have any Firmwave to help me do that? Thank you!

Hello ! My AIO package is for A530F but with OXM CSC, not OLM/XXV. You should download the 4CSD4 OLM/XXV from here: https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/XXV/download/A530FXXU4CSD4/267308/

Thank you! I downloaded and used the OLSD4 OLM / XXV firmware with odin. But I was caught in THL CSC without switching to XXV / XXV, XXV / XXV as the original settings.

Good for you for the flash. For your CSC, to have it back to XXV without being rooted (keeping knox to 0x0), I think you should flash a single CSC firmware with wipe option and without your sim card, and after the OLM/XXV 4UCSD4 firmware with wipe option and with your XXV sim card.
In the first flash (single CSC), you will wipe your data (and CSC data too), and the process will install single CSC.
In the second one, you will wipe again your data and CSC data, install multiple CSC in your system, but with the sim card you will be with XXV CSC.
Envoyé de mon SM-A530F en utilisant Tapatalk

Single 4CSD4 CSC firmware: https://www.sammobile.com/firmwares/galaxy-a8/SM-A530F/BAT/download/A530FXXU4CSD4/268134/. It is UWE CSC, and it seems to be a single CSC firmware. I will verify as possible.
It is also possible that you will have to tick repartition option in Odin3 within the two flash processes, to use the PIT file inside CSC tar.md5 archives. Why ? Because probably the cache partition has different size from one to second. I will check it too.
Let me time for this week
Envoyé de mon SM-A530F en utilisant Tapatalk

No, after check I can tell UWE CSC is not a single one. With the BOG one (CSC from french company), I think that we should go on. I have downloaded it, I have now to check it. I will tell you soon.

it would be also kind to have csc file updated for call recording enabled

ziatnine said:
it would be also kind to have csc file updated for call recording enabled
Click to expand...
Click to collapse
Hello ! If I tamper CSC, it will be corrupted and not recognized by Odin, so flash will fail. My aim is to be stock to keep Knox 0x0. So no tamper of components.

hypo59 said:
Hello ! If I tamper CSC, it will be corrupted and not recognized by Odin, so flash will fail. My aim is to be stock to keep Knox 0x0. So no tamper of components.
Click to expand...
Click to collapse
that's sad
I thought knox is ticking only when BL/Recovery is getting touched...
I assumed since Odin is not altering either of them, it's fine to feed it with a customized image. I didn't know it check the integrity or something.
Anyway, I flashed this one of yours with HOME_CSC, it works fine. Funny, but WiFi calling is now magically working, as well as VoLTE, which I haven't seen in an original stock ROM.

Ulefone Power 5 - TWRP v3.3.1 + Root + Decrypt

Ok, I'll start right away. I can't post links because I have never posted on XDA before, but I can tell you where to get what the title says. Just google for "needrom CarelMinnaar" and you will find the link under my name.
I've made a "pack" to get the Ulefone Power 5 MF2 (MF2 is the 6GB version, although the steps should also work for the MF1 4GB version) Rooted with Magisk (v20.3) and Magisk Manager (v7.5.1) while also installing TWRP (v3.3.1) and getting rid of the Forced Encryption, DM-Verity and Disk Quota - all at the same time... This will not revert back to the factory recovery mode if you follow the steps in my readme file (inculded in the .rar file).
This work is heavilly based/reliant on Topjohnwu, Jcadduono, Zackptg5 and Hadenix - they deserve the credit and thanks for their hard work. I have tested, ported and combined all this to make it work on the Ulefone Power 5 (and in the process took a few days to brick my device a few times until I get it perfectly right so you don't have to struggle / go through the headaches).
As with anything you do – it is at your own risk, not mine.
You can download it over at NeedROM: Just google for "needrom CarelMinnaar" and you will find the link under my name. This will ensure your internal storage is decrypted, so you should be able to back it up, etc. I wish I could post it here, but I'm not very active posting on here, maybe someone else wants to put up the link...

Mano isso é show , alguém poderia fazer um tutorial do ulefone Power 5 tem muita gente usando e querendo modificar eu msm já modifiquei tanto que quero de novo mais quero mais novidades, vlw o post

Hey man, thanks for your work! I had planned to reprogram the whole vendor partition, but I will try your work first!
This is the file you uploaded?

General Rooting, ODIN, Firmware, CSC Information And Myths Debunked / Noob's Guide To Samsung Devices

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, CSC​People 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 deprecated​A 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 KNOX​If 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 do​There 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/ART​This 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 issues​On 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 Information​Last, 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.