Database Info

OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!

OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!
{
"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"
}
Before you start, OTA up to the latest System Update available.
Settings > System Updates > Download & Install the latest available
Thank You all for your support :highfive:
Never Settle :fingers-crossed:​

Introduction​​
Rooting OnePlus 6 would give you additional benefits like you can install special apps, Flash Custom ROMs & Custom Mods, you can streamline your phone performance and many extra features. The real performance of an Android smartphone can only be unlocked once it is rooted.
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: ​
1. Unlocking the Bootloader
2. Installing a Custom Recovery
3. Gaining Root Access
Each new step relies on the previous step so please follow the entire process and a basic summary of each part is described as below:
Unlocking Bootloader​​Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.​
Installing a Custom Recovery​​A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your device (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Gaining Root Access​​You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed and an unlocked bootloader. This, in my opinion, is the a practical and beneficial method for rooting your phone. It will give you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of the entire process. This method will work regardless of any android version on the phone.
If you are confused by anything in this guide, I highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also we would suggest that you read over the whole thread a few times before actually doing anything to the phone.​

Setup, Preparation & Prerequisites​​
Basic tasks that may be referred to throughout this guide:​​Open Command Prompt: Press Shift + Right Click anywhere on the screen and select Open Command Window here
Enter Fastboot/Bootloader Mode: Turn the phone off. Hold volume up + power until the "fastboot" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot > Bootloader from the power menu.]
Enter Recovery Mode: Turn the phone off. Hold volume down + power until the "OnePlus Logo" screen appears. [Alternatively, if Advanced Reboot is enabled, you can press Reboot -> Recovery from the power menu.]
ADB and Fastboot Drivers Installation​1. Download & Update OnePlus 6 Drivers From Here
2. Download & Update Fastboot and ADB Binaries/Drivers from Here
3. Run the .exe file downloaded from above as Administrator.
4. Press 'Y' every time the installer asks for.
5. Continue Driver Installation.
Now, ADB and Fastboot have been installed on your PC and should be Working as desired.
Things To Remember​Show File Extensions
Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery
Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long , but its best to have enough charge in case something goes wrong.
Backup (Optional)
Unlocking the bootloader will/should completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option. Also make sure that from now on, OEM unlocking option is enabled before you reboot as sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.

Unlocking Bootloader​
Turn the phone off. Then boot it into fastboot mode by holding volume up + power or select reboot to bootloader if advanced reboot is activated via developer options. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window on the desktop (Shift + Right Click -> Open Command Window here) and type:
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember this Step will WIPE EVERYTHING off the phone so Backup all your Data
Code:
fastboot oem unlock
You would be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection
Your device will reboot, show you a Secure boot warning, reboot into stock recovery and wipe all data. Once done, your phone will reboot into the OS.
Please continue and follow the next post to install Custom Recovery

Flashing TWRP Recovery​
Downloads:
Official TWRP Image & Installer Zip
Blu_Spark TWRP
Root
Magisk​
Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enable OEM Unlocking
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.
Enable Advanced Reboot
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation.
Download all the files, place Magisk & TWRP installer zip on Device Internal Memory and TWRP img on your PC
Then boot it into fastboot/bootloader mode by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.
Open a new command prompt in the same location and run the following commands:
Code:
fastboot boot twrp-3.2.2-0-enchilada.img
You will temporarily boot into TWRP
Now in TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed.
PS: DO NOT BOOT IN OS JUST YET & CONTINUE TO THE ROOTING POST

Gaining Root Access​
This is a continued post from the above post...
1. Boot into TWRP Recovery
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk to root.
5. Swipe to confirm the flash
6. Reboot System
Keep in mind that the first boot after wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot and might reboot a few times.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Congrats! Your Device now has an unlocked bootloader, a custom recovery installed and is rooted !!
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Enjoy :fingers-crossed:

Making a Nandroid Backup​
Warning: before you make a backup with TWRP you must remove all Lockscreen Security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin/pattern/password will result in an "incorrect pin/pattern/password" message), you'll be forced to perform a factory reset to boot into Android.
To remove lockscreen security go to
Settings > Security > Screen Lock and set it to Swipe/None.
A Nandroid Backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back.
You can also use Nandroid Bckup to create a backup of your favorite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
To Create Nandroid Backup:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 5 to 7 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS

Restoring a Nandroid Backup​
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 5 to 7 minutes.
5. Reboot system once done
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Password) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue.
Boot into TWRP
Use the TWRP File Manager and Navigate to /data/sytem/ and delete the following files:
locksettings.db
locksettings.db-shm
locksettings.db-wal.
gatekeeper.password.key
gatekeeper.pattern.key
You may or may not have all the above files so delete the ones you have.
Reboot the phone and (if you've set a PIN) enter it to decrypt the storage one more time. After that you can simply unlock your phone with a swipe.
Upon Boot > Go into Settings > Security > set your preferred unlock method
Android will ask you if you want to set a boot-time code too so select as per convenience.

Making an EFS Backup​All too often, we've seen folks who have a corrupted or missing EFS Partition. This results in your IMEI being lost and no cellular activity on the device at all. This can be a royal PITA to fix, and some folks haven't been able to fix it at all. You can take a precautionary measure to safeguard yourself against this by taking a couple of minutes to back up your modemst files.
Download & Open up Terminal Emulator on your phone from here
Once it's open you'll be greeted with a command line prompt, in which you can enter text commands, the first thing you need to do is enable root access by entering this line (press the enter key on your on-screen keyboard after each command to issue it):
Code:
su
If this is the first time you've used Terminal Emulator a Superuser or SuperSU popup will appear, make sure you grant root access.
Now enter these two commands:
Code:
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
Code:
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
This will place two files (modemst1.bin & modemst2.bin) on your internal storage.
Make sure you copy them to your PC and Cloud immediately so that you have a backup there to use if you need to restore it in future.
That's it !! In case you ever need to restore Nanroid or EFS Backups, please continue and follow the next post...

Restoring an EFS Backup​If by chance you end up with a corrupt EFS partition all you need to do is flash the files back to your device using fastboot.
Boot into fastboot mode (power + volume up) and connect your phone to your PC via usb cable.
Keep modemst1.bin and modemst2.bin (backed up earlier) on your desktop and open command window there.
These fastboot commands will restore the files:
Code:
fastboot flash modemst1 modemst1.bin
Code:
fastboot flash modemst2 modemst2.bin
Reboot your device.
Code:
fastboot reboot
Now disconnect phone from PC. Your IMEI should be back.
That's it for this guide, Enjoy :highfive:

Full Stock Rom:
OOS 5.1.3:
AFH
Changelog:
* Updated Android Security Patch To May
* Preloaded OnePlus Switch Application
* Added Configuration for Notch Show/Hide
* Camera - Support Super Slow Motion (720p at 480fps and 1080p at 240fps)
* Camera - Support Quick Capture in Portrait Mode
* Gallery - Support more actions for recently deleted files

Thread Opened for Users to Unlock the device for now, TWRP will be updated as soon as its available.
Thank you for your consideration.

Funk Wizard said:
2. If you want to stay systemless continue without swiping right else Swipe and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
Click to expand...
Click to collapse
These two steps seem a bit conflicting when it comes to enabling system modifications in TWRP. Am I right in that if you don't allow system modifications, you can still flash Magisk and get root access but you won't be able to flash custom ROMs?
---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------
Is there a difference between backing up EFS via a terminal emulator rather than just doing it via TWRP?

KnifeFed said:
These two steps seem a bit conflicting when it comes to enabling system modifications in TWRP. Am I right in that if you don't allow system modifications, you can still flash Magisk and get root access but you won't be able to flash custom ROMs?
---------- Post added at 04:30 AM ---------- Previous post was at 04:28 AM ----------
Is there a difference between backing up EFS via a terminal emulator rather than just doing it via TWRP?
Click to expand...
Click to collapse
Yes you are right, you can still flash Magisk and get root access if you don't allow modifications. Also there should be no difference between the TWRP EFS backup or the Terminal Emulator EFS backup.
I would still recommend both as backup if you mess up TWRP/OS due to encryption issues, besides that the official twrp for the 6 would still take time so for just wanted to keep both options at your disposal :good:

Funk Wizard said:
Flashing TWRP Recovery​
Click to expand...
Click to collapse
Good to see you here.
Being a device with A/B partitioning, there is no separate /recovery partition as it is fused with /boot. Besides, you've to fiddle with active slots to make it installed. I know the guide is work in progress, but the current state may arise confusions.
Regarding this post, what was the OOS version of the initial build?

Titokhan said:
Good to see you here.
Being a device with A/B partitioning, there is no separate /recovery partition as it is fused with /boot. Besides, you've to fiddle with active slots to make it installed. I know the guide is work in progress, but the current state may arise confusions.
Regarding this post, what was the OOS version of the initial build?
Click to expand...
Click to collapse
The initial build was 5.1.0 which was a test build

Funk Wizard said:
The initial build was 5.1.0 which was a test build
Click to expand...
Click to collapse
Thanks for the confirming my initial speculation.
:highfive:

Funk Wizard said:
Gaining Root Access​
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery.
Click to expand...
Click to collapse
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!

jordanlaa said:
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!
Click to expand...
Click to collapse
You can just take the partial OTAs with unlocked bootloader..
But if you install custom recovery ( twrp) ..then you have to flash the full rom zip anytime that you want to upgrade..

jordanlaa said:
I have my device coming next week and want to get involved with Custom Roms and rooting once some of the incredible devs here develop some stable roms. I was thinking of unlocking the bootloader straight out of the box and then stopping there so that when I decide to proceed I won't need to wipe all user data. If I only unlocked the bootloader, am I still able to apply Oneplus OTA updates through the settings app as usual? This is in reference to your warning: "Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing full zips in recovery."
Thanks for your guide Funk Wizard!
Click to expand...
Click to collapse
As and when you get the device follow the below:
1. Boot up the device and check for system updates
2. Update to the latest available 5.1.3 as of today or whatever latest at the time you have the device.
3. Unlock the bootloader
4. Continue with TWRP flash & Root (Magisk) as by next week TWRP will be available
4. Set up the device the way you want now like installing you preferred apps and setup your device.
5. There on whenever an update comes download the full zip and flash it via twrp instead of partial OTA's
I will make a separate thread for instruction on how to update just like my threads on 5T & 5, links on my signature.
Those will be self explanatory and tested instructions as I happen to have the device with me.
For anything else you are free to discuss here, I may not be available all the time due to work schedule however I will answer all your concerns once I have access to xda.
Thank you for your patience :highfive:

[RECOVERY] TWRP 3.2.1 For C701F/DS [STABLE]

Team Win Recovery Project
It's Compatibe with Snapdragon Variants Of C7 Pro Such as C701F and C701F/DD.
If it's not working with your device or you have different model let me know. I would Build a Different Version of Recovery for your Model.
#include <std_disclaimer.h>
{
"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"
}
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy C7 Pro (C701F/DS):
https://androidfilehost.com/?w=files&flid=275664
Sources:
https://github.com/TeamWin
https://github.com/aapav01/android_device_samsung_c7proltedd-twrp
Changelog:
Check #2.
Guide:
Check #3.
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
(You Can donate me Steam Gift Cards)
To contribute:
TWRP Code Review
Github pull requests will be ignored.

Change log:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
June 12, 2018 (twrp-3.2.1-0):
Fixed MTP
Fixed encryption on ASOP ROM (Samsung is unsupported)
Enable NTFS Support
Fixed Mount Issues of partition
Add Support OREO ROMs
Added EFS Backup
And MORE

Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [HOME BUTTON] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [HOME BUTTON] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [HOME BUTTON] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.

dear.......followed procedure....but... ( error is set warranty bit kernel..)...now any soln...pl reply..
thanxs with deep warm regards

I have the SM-C7018 version of this phone and, by following your guide, I was able to set up TWRP on Android 7.0 and flash GAPPS.
Thank you very much for this!
EDIT: Maybe it was just in my case, but for those of you that wish to install GAPPS on this device, keep in mind that you must not reset it to the factory conditions after installing GAPPS, as the Play services will FC once the phone boots up, and you will not be able to use it anymore. I had to re-flash the firmware. Also, I've used the Pico package, ARM x64, Android 7.0.
EDIT 2: Unfortunately, I couldn't manage to get the GApps working. The Google Framework Services would always crash when opening any google application for the first time or when trying to add the account from the Settings Menu. Anyone had any success with adding GApps on the Nougat firmware?

SPG30759 said:
dear.......followed procedure....but... ( error is set warranty bit kernel..)...now any soln...pl reply..
thanxs with deep warm regards
Click to expand...
Click to collapse
it's normal on samsung devices

aapav01 said:
it's normal on samsung devices
Click to expand...
Click to collapse
Hi, I did the steps you mentioned, but after completion I checked with Root Checker app it says "Root not installed properly". Do you know why?

My device is C7010. Can it use your TWRP as well?

c7 PRO c7018
Will this tprw work with c7018 model? and with c7018 + oreo?
aapav01 said:
Team Win Recovery Project
It's Compatibe with Snapdragon Variants Of C7 Pro Such as C701F and C701F/DD.
If it's not working with your device or you have different model let me know. I would Build a Different Version of Recovery for your Model.
#include <std_disclaimer.h>
Special Notes:
1. READ THE GUIDE.
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However, this may not affect you if your country, European Union, for example, forces Samsung to provide hardware warranty regardless of software status.)
More Infos: https://en.m.wikipedia.org/wiki/Rooting_the_Android_operating_system
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.
(DO NOT GET FOOLED.)
5. You HAVE to use newer version of Odin (>3.13) if you want to flash stock ROMs.
Download:
Galaxy C7 Pro (C701F/DS):
https://androidfilehost.com/?w=files&flid=275664
Sources:
https://github.com/TeamWin
https://github.com/aapav01/android_device_samsung_c7proltedd-twrp
Changelog:
Check #2.
Guide:
Check #3.
Show your appreciation:
Click Thanks!, Rate 5-star or/and Donate to me.
(You Can donate me Steam Gift Cards)
To contribute:
TWRP Code Review
Github pull requests will be ignored.
Click to expand...
Click to collapse

Can I use this to port TWRP for 10.or G
Specs of 10.or G
Snap 626
4gb ram
Also pls reply what hardware needs to be same for porting.
And does kernel matter in Porting these images???
Thanx in advance

@aapav01 plz make twrp for C7000 oreo
tnks

a7 2015
Can build for me this same rom its humble request

Thank you!

c7 pro twrp for oreo
hi
i have series gapps problem .
can you plz make one for c7 pro sm-c7018 oreo .
twrp has no version for it .
baseband version: c7018zmu2cri1
buildnumber: r16nw.c7018zmu2cri1.
2018/09/14
ty

phone stucked at samsung logo and set bit : kernal
I followed same step and my phone isnt booting now
stucked at samsung logo and yellow top right says set bit: kernal
please help

try this
ashokrathi said:
I followed same step and my phone isnt booting now
stucked at samsung logo and yellow top right says set bit: kernal
please help
Click to expand...
Click to collapse
try pressing vol down and power at same time time then phone goes to power off then switch from vol down to vol up holding the power button now as soon as screen display starts leave both buttons it will now boot into twrp recovery go to wipe format data and type yes then flash no dm verity and magisk as per instruction given

My device is C7010. Can it use your TWRP as well?

aapav01 said:
Guides:
Notice: It may wipe all your data including those in internal storage.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [HOME BUTTON] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [HOME BUTTON] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [HOME BUTTON] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the latest dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage. Now you can either reboot into system or root, flash custom ROMs via TWRP.
Part 3 - HOW-TO ROOT:
1. Download the flashable zip.
- Option 1: Magisk
- Option 2: SuperSU
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Part 3a - HOW-TO FLASH CUSTOM ROMS:
1. Download the flashable zip.
2. Transfer the zip to your phone.
3. Go to "Install" menu of TWRP and flash the zip.
Simple.
Click to expand...
Click to collapse
I want to try this but my phone (c701f-ds) never boots into download mode or recovery mode consistently. I bricked the phone trying to root it throught the magisk app, using this very version of twrp. I got it back. I was able to flash the original stock oreo rom using odin
But to get the phone back I didn't go through the (blue screen) Download Mode, Instaed I got into the recovery envoronment (very hit and miss) then chose to reboot into bootloader mode, where I saw it yellow at the top of the screen "download mode" but not the blue screen of the usual download mode.
In this bootloader/download mode environment I connected the phone to the laptop. Odin recognised the phone and I loaded the stock rom into AP, and the appropriate files into the other boxes (I used Home_CSC instead of CSS, essentila for getting VOLTE to work). It flashed successfully. (a status bar appeared on the phone which corresponded to the download process)
But that wasn't the method that anyone else recommended.
I would try flashing the twrp tar file in the same way but there is no guarentee I could get into the twrp environment since holding [VOLUME UP] + [HOME BUTTON] + [POWER] doesn't always, or even often, get me into recovery mode.
I can use adb to reboot into recovery and from there get into bootloader/download mode but not again if the os doesnt load
Any advice?
And you say that eventhough the phone is already in download mode, that after you connect the phone to the pc where odin is loaded and has initialized the tar file, you have to press and hold [VOLUME UP] + [HOME BUTTON] + [POWER] and then press start on Odin. Then continue to hold these 3 buttons till the phone reboots into twrp. Why not just press start on odin without holding these 3 buttons? If the phone just shuts off after flashing twrp, would turning it on by holding those 3 buttons bring the phone (except mine perhaps) into twrp recovery?
What happens if the phone doesn't boot into recovery/twrp? Is it bricked? And if it does boot into the os, could you use adb to get into twrp?
I am being cautious due to the difficulty in getting the phone back after bricking it last time and because there is no guarentee that an ke combos will definitely get my phone into recovery or download mode.
Help is appreciated.

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"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"
}
Any thoughts please?

I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.

akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.

strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)

who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.

TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.

who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition

[Stock ROM][Combination][RMM state solution][GUIDE AIO] and many more for M30s

What's currently included in this thread :-
TWRP (With/without magisk)
Installing EdXposed
Root with magisk (not recommended due to bootloops, use twrp with magisk)
RMM state Prenormal solution
Stock and combination firmware and Kernal source Gdrive links
Tools for flashing and downloading latest firmware
Post 2
Hide bootloader unlocked warning message
DeGoogle & debloat M30s and install MicroG
Enable Haptic feedback on m30s (or any other samsung phone)
BACKUP YOUR EFS PARTITION BEFORE DOING ANYTHING​If EFSpartition is corrupted or lost, you would not be able to get calls and wifi and your IMEI will be permanently lost.
There is currently no way of restoring corrupted EFS partition since it is device specific, so flashing stock firmware will also be useless
Here is one guide. follow this or any other that works for you.
Here is another (droid view.com/restore-efs-imei-galaxy-s7/)
OR You can Backup all partitions using twrp (nandroid backup) and store in someplace safe (make sure to tick all partitions including EFS)
This is an excellent guide regarding EFS (thanks to @PlayingPoise). I HIGHLY RECOMMEND READING IT BEFORE PROCEEDING.
TWRP (With/without magisk) (huge thanks to @santhoosh)
Thread
there are two .tar files, flash the one you need
Pro Tip: I would recommend Smalipatcher module to reboot directly into magisk system.
Installing EdXposed
See This for installation video OR This Or This for installation guide.
This, for official website
And This for github!
NOTE: v0.4.6.0_beta from github requires custom magisk otherwise the system wont boot since github hosts alpha versions, so i advice to follow the video tutorial since it has installed the most stable EdXposed
Rooting with Magisk (Currently causing random bootloops since custom Kernal is req., i recommend flashing twrp with magisk)
From magisk official repo and This Link, Both are same, but i just wanted to make AIO thread)
thanks to @santhoosh and @topjohnwu
Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
* Allow bootloader unlocking in Developer options → OEM unlocking
* Reboot your device to download mode. Either use adb reboot download, or use turn off m30s, press vol+ and vol- simultaneously (while powered off) and connect to pc.
* Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
* Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
* Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
* if there is no OEM unlock option, set phone's date to 7+ days and back and now see.
* Your bootloader now accepts unofficial images in download mode.
Instructions
* Download the firmware for your device.
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
* Install the latest Magisk Manager
* In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
* Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
* Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
* Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
* Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
* We now want to boot into the stock recovery to factory reset our device.
* Full data wipe is mandatory! Do not skip this step.
* Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the Vol up and power to boot to recovery . Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
* Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
* This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
* The device will automatically reboot for the first time it boots. This is completely normal and done by design.
* After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
* You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
* Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
Additional Info
* Magisk actually patches 3 partitions on your device:
vbmeta: replace with empty vbmeta image to disable partition verification
boot: remove the signature of the image to prevent soft bricks
recovery: this is where Magisk is actually installed
* Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
* If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
* If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC
used instead of CSC)
RMM state Prenormal solution
Flash stock firmware
Boot up WITH sim inserted, CONNECT to internet during setup (or you can connect after setting up, but perform below operations only when connected to internet).
Enable developer options and go to them.
Now connect to internet and go to dev options, now set date 8 days back and check dev options for OEM unlocking
if it's still not there set date to today and again 8 days back and again check.
This worked for me and OEM unlocking was there and RMM state was changed to checking.
(what we are doing is fooling phone to believe that sim was inserted for more than 7 days)
Stock and combination firmware and Kernal source
Below are Gdrive links for Combination firmware for (M307FXXU1ASH9) and (M307FXXU2ASK2) and ROM M307FXXU1ASHI, M307FXXU2ASL2, M307FXXS2ATB3 (FOR INS ONLY, for other regions, use frija or samfirm).
I have also uploaded Kernal source for M307FXXU2ASL2 on gdrive for faster download.
Tools included
The following tools are also included in the shared folder, they are up to date as of FEB 2020, but i have attached links to original threads of xda to give credits and in case they are updated, you can download them from there. (As i said, this is AIO thread to find tools, none of them are my creation)
Frija, Samfirm continued and Samfirm are Tools for downloading Official firmware from samsung servers with high speed (so no to sammobile and other ****ty premium websites)
Frija thanks to @invmini, Github
SamFirm thanks to @zxz0O0, Github
SamFirm_continued, Github
Odin
Patched Odin by @realbbb
Frija not working ? install both vcredist_x00 for your device !
(check your windows settings to know which version to install)
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-m307f) and your CSC : (mine is INS).
(All models on samfrew: https://samfrew.com/model/SM-M307F/).
Thanks to @BK
Other Tools
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Samsung firmware naming convention and explanation (Outdated)
SM-M307F - Galaxy M30s Samfrew
Extract Samsung PIT File from Samsung Firmware -> www.droid views.com/extract-samsung-pit-file-from-firmware (remove space b/w "droid" and "views")
NAND Erase Samsung Devices in Odin -> www.droid views.com/nand-erase-odin-samsung-firmware (remove space b/w "droid" and "views")
Latest Odin Downloader: https://odindownloader.com/category/download
Samsung USB Driver: https://samsungusbdriver.com/category/download
Samsung Firmware: https://firmwarefile.com/category/samsung
Links​LINK (Pm me if link is dead. If there is error like "try after some time", make a copy of file to your drive and then download)

Hide bootloader unlocked warning message
See Here
DeGoogle & debloat M30s and install MicroG
Here
Enable Haptic feedback on m30s (or any other samsung phone) (thanks to ak****)
1- download "Settings database Editor" from playstore.
2- scroll to bottom and find "haptic_feedback_enabled" and change it to 1

Just in case

great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )

BK said:
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
Click to expand...
Click to collapse
Are you talking about the frija and samfirm part?
I think i took it from some other thread which i cant find now. (maybe s10 or note10 ones)
Edit: Gave credits to you

How to flash Combination firmware?
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.

nobody_nowhere said:
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
Click to expand...
Click to collapse
it's currently impossible to install a test/debugging firmware without a samsung dev account that work as an authorization to flash combination files.

Sm-m307f/ds
Hi i got OTG update and my phone didnt restart after that, i have been trying to find the right Stock firmware for my Samsung M30S SM-m307F/DS but i couldnt find the right one, can you please help me out with the link of the right firmware for my phone.
Thanks

Watch this video broo...you will get to know how to download all latest updated frimware

[GUIDE]Universal Rom , Recovery And Kernel Flashing Guide For All Roms , Recoveries , Kernels

TWRP Flashing GUIDE (Linux-Only)
{
"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"
}
Before following this guide, make sure you have followed the rom flashing guide below the post below or xiaomi.eu rom flashing guide.
If you have followed the flashing guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Steps to install
Then go to your custom rom download thread and check the date of rom file (In this case derpfest) and choose the recovery version closest to the release date of your rom.
Download the latest platform-tools for linux from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" comes out Method 3:- Turn off your device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" comes out
4. Connect your device to the PC
5. Open a terminal window in the folder where you extracted the binaries from the archive from step 1
Easy method: Open the folder, and open a terminal in the folder itself. Terminal will open a window directly in the folder location
6. Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
7. Type this command in the terminal window, but don't press Enter yet, just type it and leave a space at the end:
fastboot flash recovery_
Don't write the "_". This only indicates the space you should leave at the end.
8. Now, drag the image file (yourrecoveryhere.img) to the terminal window and drop it above the window . This will make you copy your exact location for convenience.
fastboot flash recovery "home/user/location/to/your/file/yourrecoveryhere.img""
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
9. Press Enter and wait a few seconds . Once it shows that it is successfully flashed hold the Vol Up + Power button , once the device restarts release the power button and keep the Vol Up button pressed , after a few seconds the TTWRP logo will show , release the Vol Up button now.
DONE! You've started perfectly in recovery
This guide applies to all recoveries:
NOTE:
If your rom mentions to use a specific recovery then use that instead
To flash shrp recovery you have to extract the .img from the zip file of the recovery that you downloaded ,then flash it in the same way as told above , make sure after booting in the recovery you flash the zip file of the shrp recovery from which you extracted the .img file in the recovery itself.
DO NOT USE ORANGE FOX RECOVERY ! It is deprecated and unmaintained so it wont be updated in future .
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Download Link
TWRP Download (If your rom mentions to use NSE TWRP then use the NSE TWRP with the closest android Version to your rom's android version or else if it doesn't specifically mention any twrp version then use the normal TWRP , the one without NSE in its name, with the closest android version to your rom's android version ):
https://www.pling.com/p/1346294/
SHRP Download:
https://sourceforge.net/projects/shrp/files/Beryllium/
Enjoy !
---------------------------------------------------------------------------------------------------------------------------
TWRP Flashing Guide (Windows-Only)
Before following this guide, make sure you have followed the rom flashing guide below the post below or xiaomi.eu rom flashing guide.
If you have followed the flashing guide then you may continue.
Hello Amigos,
You can use this guide to install other recovery than TWRP also.(Other recoveries are listed in the guide itself)
Steps to install
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers , android bootloader interface and click install.
Then go to your custom rom download thread and check the date of rom file (In this case derpfest) and choose the recovery version closest to the release date of your rom.
Make sure you have the bootloader unlocked before you start. There are many guides on the internet for that.
Download the latest platform-tools from the Android developer site and extract the zip in an easily accessible folder
Download the recovery image file
Restart your device to fastboot mode
Method 1:
Using this adb command if you have USB debugging active on your device:
adb reboot bootloader
Method 2:
- Turn off your device
- After it has completely turned off, press and hold Vol - and the Power button at the same time until the word "FASTBOOT" comes out Method 3:- Turn off your device
- Press and hold Vol - button
- Connect the USB cable (previously connected to the PC) to the device and press and hold the button until the word "FASTBOOT" comes out
4. Connect your device to the PC
5. Open a cmd window in the folder where you extracted the binaries from the zip from step 1
Easy method: Open the folder, and without leaving it, type "cmd" in the address bar of the file explorer and press enter. Command promt will open a window directly in the folder location
6. Verify that your device is recognized by fastboot using this command:
fastboot devices
If your device has been detected (a serial number followed by the word fastboot), you can continue. Otherwise, check if the drivers are installed correctly, although if you used Mi Unlock and were able to unlock the device correctly on the PC you are using, you should not have problems with that.
7. Type this command in the cmd window, but don't press Enter yet, just type it and leave a space at the end:
fastboot flash recovery_
Don't write the "_". This only indicates the space you should leave at the end.
This is how it should look when you write it:
8. Now, drag the image file (yourrecoveryhere.img) to the command window and drop it above the window. This will make you copy your exact location for convenience.
- The result should be this:
Code:
fastboot flash recovery "C:\location\to\your\file\yourrecoveryhere.img"
Quotation marks are only added if the entire location has spaces.
Otherwise, it is displayed without quotation marks.
9. Press Enter and wait a few seconds . Once it shows that it is successfully flashed hold the Vol Up + Power button , once the device restarts release the power button and keep the Vol Up button pressed , after a few seconds the TWRP logo will show , release the Vol Up button now.
DONE! You've started perfectly in recovery
This guide applies to all recoveries:
NOTE:
If your rom mentions to use a specific recovery then use that instead
To flash shrp recovery you have to extract the .img from the zip file of the recovery that you downloaded ,then flash it in the same way as told above , make sure after booting in the recovery you flash the zip file of the shrp recovery from which you extracted the .img file in the recovery itself.
DO NOT USE ORANGE FOX RECOVERY ! It is deprecated and unmaintained so it wont be updated in future .
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Download Link
TWRP Download (If your rom mentions to use NSE TWRP then use the NSE TWRP with the closest android Version to your rom's android version or else if it doesn't specifically mention any twrp version then use the normal TWRP , the one without NSE in its name, with the closest android version to your rom's android version ):
Recovery For Poco F1
Team Win Recovery ProjectWht Works : * EVERYTHINGS *BUG : * You Tell Me *
www.pling.com
SHRP Download:
https://sourceforge.net/projects/shrp/files/Beryllium/
Enjoy !
---------------------------------------------------------------------------------------------------------------------------
ROM Flashing GUIDE (Windows-Only)
First of all unlock bootloader of your device . Search net for more info.
After this install adb drivers from here: https://forum.xda-developers.com/t/...reborn-v2-0-adb-fastboot-and-drivers.3854109/
Choose skip install for adb and install google drivers.
Connect your device in fastboot mode to your pc.
Go into device manager , right click on unrecognized android device , choose update drivers , let me pick from a list of drivers , select adb drivers and click install.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Check the date of file.
Then go to xiaomifirmwareupdater.com and select rom archive and select your device.
Then MIUI downloads page will appear. type fastboot in search and look for a MIUI global version released
as the same or very close to the Custom ROM date (in this case it is this)
Download the fastboot version according to the date.
Go into the stock rom folder and double click on flash_all.bat(all data will be lost) .
Or open cmd in the folder and type flash_all.bat in cmd and hit enter.(This method allows to look for errors)
A cmd window will popup with fastboot commands automatically and after complete flashing of rom will close automatically. (approx. 20-25 mins)
Let the device boot into MIUI.
Once it boots, power it off . Then press the vol down + power button until fastboot in orange letters appear.
Then follow the twrp flashing guide from here
Then flash the ROM according to the instructions.
NOTE:
Make sure to always extract and move the stock rom folder in root of C: drive (this helps avoid flashing errors)The path should look something like this:
C:\beryllium_global_images_YourVersionhere
Then flash the stock rom.
Clean Flashing a ROM:
I hope you have followed the entire guide above before doing this step.
Reboot to recovery.
Format data.
Flash ROM file.
Wipe Dalvik Cache.
Reboot and enjoy.
Everytime you do a clean flash, you must redo all the steps above.
If a rom does not include flashing instructions, it requires a clean flash.
If a rom mentions to wipe something in advanced wipe , then wipe ONLY that and nothing else.
If rom mentions clean flash and not wiping of anything else then dont be smart to wipe anything unecessary.
If your rom mentions to use a specific recovery then use that instead
Always flash magisk after the first boot of your rom
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device
Enjoy!
---------------------------------------------------------------------------------------------------------------------------
ROM Flashing GUIDE (Linux-Only)
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
First of all unlock bootloader of your device . Search net for more info.
Then go to your custom rom download thread and check the date of rom file(In this case derpfest).
Check the date of file.
Then go to xiaomifirmwareupdater.com and select rom archive and select your device.
Then MIUI downloads page will appear. type fastboot in search and look for a MIUI global version released
as the same or very close to the Custom ROM date (in this case it is this)
Download the fastboot version according to the date.
Go into the stock rom folder and right click in empty area then select open terminal here then type this command:
./flash_all.sh
A terminal window will popup with fastboot commands automatically and after complete flashing of rom will close automatically. (approx. 20-25 mins)
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
Then follow the twrp flashing guide from here
Then flash the ROM according to the instructions.
NOTE:
Make sure to always extract and move the stock rom folder in root of home directory (this helps avoid flashing errors)The path should look something like this:
home\beryllium_global_images_YourVersionhere
Then flash the stock rom.
Clean Flashing a ROM:
I hope you have followed the entire guide above before doing this step.
Reboot to recovery.
Format data.
Flash ROM file.
Wipe Dalvik Cache.
Reboot and enjoy.
Everytime you do a clean flash, you must redo all the steps above.
If a rom does not include flashing instructions, it requires a clean flash.
If a rom mentions to wipe something in advanced wipe , then wipe ONLY that and nothing else.
If rom mentions clean flash and not wiping of anything else then dont be smart to wipe anything unecessary.
If your rom mentions to use a specific recovery then use that instead
Always flash magisk after the first boot of your rom
If mtp not working or device not getting detected as a portable device in any recovery then watch this guide here: GUIDE
Do not replace the recovery or try to update recovery that comes with roms. This can brick your device.
Enjoy!
---------------------------------------------------------------------------------------------------------------------------
Kernel Flashing GUIDE:
Always Flash a custom kernel after the first boot of the device in a rom which was clean flashed.
Always take a backup of your rom's boot.img incase something goes wrong.
NGK Kernel:
Download the latest nse version (if your rom is nse rom)
Then store it somewhere in your internal storage
Boot to twrp
Flash NGK NSE kernel zip
Wipe Cache Dalvik
Reboot To Syste,
NOTE:
If your rom doesnt mention if it is a nse or se rom then you may download both nse and se versions of the kernel . Then boot into twrp and flash nse version as above . If your device gets bricked , bootlooping , restart to recovery or fastboot , Then boot into recovery again and flash se version as above . After this your problem should be fixed . Still if something goes wrong , boot into recovery and flash boot.img of your rom.
LawRun Kernel:
Download the kernel version according to this index:
10-11-12 in the name here mentions the android versions supported . Android Version supported in this version of kernel is android 10 ,11,12 or android q , android r and android s.
09 , P or Pie here in the name mentions android version supported . Android Version supported in this version of kernel is android 9 or android pie.
10 or Q in the name mentions android 10 is supported.
10-2-13 in the name here mentions that android 10 to android 13 roms are supported
Store the kernel zip somewhere in your internal storage
Boot into twrp
Flash LawRun Kernel Zip
Wipe Cache Dalvik
Reboot to System
If something goes wrong , boot into recovery and flash boot.img of your rom.
NOTE:
Do check the kernel version and description at the download page of the kernel to know whether it is overclocked or not.
Genos Kernel:
Download the kernel version according to this index:
If there is nothing in the name only R21 or Rxx or r17.1re or rXXre or r16.0_evol or rXX_evol or r11_evolution or rXX_evolution or r16.1_evo or rXX_evo (xx corresponding to the version of the kernel) then it supports MIUI , OOS (Oxygen OS) , AOSP (Custom Roms).
If there is r12_non_oos or rXX_non_oos in the name (xx corresponding to the version of the kernel) then it doesnt support OOS (Oxygen OS) and only supports MIUI,AOSP(Custom Roms)
If there is r12_oos or rXX_oos or r12_evol_oos or rXX_evol_oos in the name (xx corresponding to the version of the kernel) then it only supports OOS (Oxygen OS) and dosent support MIUI,AOSP(Custom Roms)
Store the kernel zip somewhere in your internal storage
Boot into twrp
Flash Genos Kernel Zip
Wipe Cache Dalvik
Reboot to System
If something goes wrong , boot into recovery and flash boot.img of your rom.
Enjoy !
---------------------------------------------------------------------------------------------------------------------------