Database Info

[GUIDE] [K06NTC_A] Just5 Freedom X1 - Flashing Nougat (7.0) & Rooting

Just5 Freedom X1 - Flashing Nougat (7.0) & Rooting
Continue at your own risk, I am not responsible for any damages done to your device.
Some notes before we start off; I've done this on a device with unlocked bootloader, and fall into category of accidentaly formatting everything. Purpose of this thread is to help people who can't find any resources from Google due to lack of any developers or support on it.
First, obtain the firmware for Nougat from NeedROM (requires registration). Unrar the archive using your favourite archival utility such as 7-zip or WinRAR.
Obtain SP Flash Tool, as you'll be needing it to flash your firmware. Choose the "Download" section, and power off your phone entirely. Choose the scatter file from where you extracted your firmware, in this case MT6753_Android_scatter.txt. MAKE SURE YOU SELECT DOWNLOAD ONLY SO YOU WON'T LOSE EVERYTHING INCLUDING NVRAM. Use the "MTK_AllInOne_DA.bin" Download-Agent, and click "Download", and connect your phone via usb to your PC. The tool should start flashing. If you've failed this step, you can retry it with different DA's, or reach out to me.
Once you've flashed, it should take a little while longer to boot than usual, that's okay, as you've just installed a whole new system. If you managed to screw up your NVRAM by formatting everything and have "Invalid IMEI", get MAUI Meta (v9) and attempt to boot into META mode. Select "IMEI Download" from dropdown menu, and from here on it should be super obvious what to do.
OH NO! Modem exception with META tool and can't detect SIM! (unknown baseband)
Remain calm, reflash the firmware with Format All + Download, this will reflash your baseband. Once it's finished, boot into META mode and rewrite IMEI, and you're ready to relaunch your phone. You can do it before or after first boot, doesn't matter.
That's great, but I miss my root!
You may already be aware, that easy root methods such as KingRoot or Framaroot aren't working on these NeedROM firmwares, fortunately you can still root (and without breaking SafetyNet!). You need to obtain Magisk from XDA (get the apk version). Insert your boot.img to your phone's SD card, and select it using the app. Pull the patched image from your phone's SD and boot into fastboot. From here, I suggest you test if it won't brick your device first. To do that, type in fastboot boot patched_boot.img and you should now have temporary root until you restart. You can verify root by either getting a third-party application from the Play Store, or checking the Magisk application. If you got root, you may reboot into fastboot, and type following to make it permanent; fastboot flash patched_boot.img. Congratulations! At this point you've just rooted your device using Magisk, and it doesn't even trigger SafetyNet!
Should you have additional questions, feel free to ask me.
Thank you for reading, hope it helped you either save or update your phone (or root ).
Here's proof of it working;
https://i.imgur.com/lmYC3dr.png (yes I'll spare your bandwidth, by not making it load a huge image)

[guide] Blu Vivo XL4 | | Vivo Xi || Vivo Xi+

The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.

placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed

After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.

Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM

So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now

Thread was opened.

mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?

psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?

mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now

Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ

******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot

Would this work on Blu Vivo XI since same chipset?

sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can

Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.

mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer

Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.

mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof

mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site

IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition

mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!

[Guide]How to root Samsung Galaxy C9 pro (SM-C9000)

Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste
Code:
.\adb devices
to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type
Code:
.\adb push AP_C9000ZHU1CSC1_CL14667562_QB22709761_REV00_user_low_ship_MULTI_CERT_meta.tar.md5 /sdcard/
.(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type
Code:
.\adb pull /sdcard/download/magisk_patched.tar
This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.

Lojcs said:
Hi! After struggling in rooting my C9 pro (SM-C9000, TGY) due to the lack of a proper guide, I decided to provide my guide to the community.
Of course, I don't take responsibility for damages etc. etc. Read the entirety of the guide before doing anything.
Useful shortcuts: Holding down power+volume down for a couple seconds force reboots from almost anywhere. Vol up+home+power while booting boots into recovery. Vol down+home+power boots into download (odin) mode.
Step 1) Fetch the required files(sorry I can't post direct links):
Nougat 7.1.1 firmware from sammobile
Oreo 8.0 firmware from sammobile
Odin https://www.xda-developers.com/update-firmware-any-samsung-phone/
Magisk Manager https://www.xda-developers.com/how-to-install-magisk/ (The link that says "Download the latest Magisk Manager APK here")
ADB https://www.xda-developers.com/install-adb-windows-macos-linux/
CROM Service apk from apkmirror
Step 2) Prepare the files
Unlock developer options on your phone by spamming Build Number in Settings> About Phone> Software Information. Enable USB debugging from developer options. Connect your phone to your PC via cable. Extract ADB (platform-tools) on your desktop (or other location). Extract Oreo firmware. There should be 5 files. Copy the one that starts with AP into platform-tools folder. Open the platform-tools folder. Hold down shift and right click inside the folder. Choose "Open PowerShell window here" from the context menu. Type or copy-paste to start ADB. On your phone, check "always allow on this PC" and click OK when prompted. Enter the code again and check if a device appears on the list. Then type .(Change the name of the file corresponding to yours. You can change the destination to another folder in your phone. Ex. /sdcard/download/) This will transfer the file from your PC to your phone. Do not drag and drop the file. This might corrupt it, causing a bootloop upon installiation. (Happened to me initially. Recovered & used the push command to get it to work.). Transfer Magisk Manager's apk to your phone or download it directly from your phone(you can drag and drop this one, as it won't install if corrupted(it won't corrupt)). Install Magisk Manager on the phone(Enable sideloading if asked). In the app, touch the topmost install button and touch install again in the next screen. You will have two options: "Download zip only" and "Select and patch a file". Choose "Select and patch a file", then locate the AP file you transferred to the device. Magisk manager will patch the file and generate magisk_patched.tar in /sdcard/download/. In ADB, type This will transfer it to the platform-tools folder. Again, don't use windows explorer to transfer. That will most certainly corrupt the file.
Step 2.5) Backup
Backup your data (you can use smart switch desktop program paired with mobile app to backup most of the stuff). Remove your google account from the device.
Step 3) Install Nougat 7.1.1
Extract Nougat 7.1.1 firmware. Extract odin. Run Odin.exe (might have version in name). Click OK. Factory reset your phone (You can do so from settings or recovery mode.). After the reset, reboot into download mode. It will ask if you're sure you want to install unofficial software, choose continue (If I don't recall incorrectly, the button for that was vol up). Plug your phone into your PC. Odin log should say "added!!" and you should see your device in one of the rectangles above. Now select the tar.md5 files extracted from the 7.1.1 firmware. Click the BL button, locate the BL_etcetc.tar.md5 file, click open. It will check the md5 for a second then let you click the next button. After choosing the BL(bootloader), AP(system), CP(radio) and CSC(localization) files (USERDATA button should remain empty, HOME_CSC file has no use) make sure only F.reset time and auto reboot are selected in options. Click start to begin. After flashing, it will do another factory reset and show you the setup.
Step 4) Unlock Bootloader
Skip everything in setup, then unlock develper options and you should see "OEM Unlocking" option that was removed in OREO firmware in there. Enable it. Next transfer the CROM service apk to your device (or download it directly). Install the app. Open it. Unlock the bootloader. (This step is required because C9000 is a Chinese phone)
Step 5) Install Oreo again
Boot into download and connect to odin. You can use the reset button to empty the buttons. Now select BL, CP and CSC files from the extracted oreo firmware. For AP, choose magisk_patched.tar . Start. If the installiation fails, you didn't unlock the Bootloader properly. The phone will reboot and factory reset a couple times. When it boots up, you'll have magisk installed.
Step 6) Things to do after rooting(optional)
First of all, magisk can hide root from Google, but not Samsung. Samsung Health, Knox secure container, Maximum power saving mode and Samsung pay won't work after you root. NFC will keep turning on on its own unless you uninstall Samsung pay. A samsung package (I'm not sure about the name but I think it was security log agent) will keep sending an unblockable notification offering to unroot. Uninstall that too, and you'll have a stable experience.
Recovering from fails:
If download mode refuses to install because of unofficial binaries, the bootloader isn't properly unlocked. Wait a couple seconds and force reboot with the key combination. Since it couldn't flash the system, that should reboot back to download mode (or recovery. in that case, choose "reboot to bootloader"). Install the official firmware, unlock bootloader and try again.
If the magisk_patched.tar file gets corruped and you flash the corrupted file successfully, your device will get into a bootloop. After the install, odin orders the phone to reboot into recovery to factory reset, but since the system image is corrupted, it won't be able to boot and produce a kernel panic. This will cause the phone to reboot, which will fail and cause it to try to reboot again. Since the phone doesn't get past the splash screen, this bootloop cannot be interrupted by button shortcuts. You should wait for the battery to die out for the bootloop to end. (It should take a day at max. Wrap a towel around it to block the vibration sounds if you want) After battery gets depleted, you need to perform a quick maneuver. You should plug the phone into a power supply (preferably your computer) while holding down volume down+home+power buttons. If you do it right, it will boot into download mode. (Otherwise, it will bootloop again. Simply unplug, wait for it to stop and try again) Flash the official firmware and repatch the AP file. Just in case you run into this issue, I recommend having less than 10% charge in your phone while flashing, just to make the wait time shorter.
Important: Check your firmware's baseband version from settings before flashing. In C9000ZHU1CSC1, CSC1 is the system and U1 is the bootloader version. Compare the bootloader version to the firmware you're going to flash and make sure they match. You can't downgrade bootloader versions. Flashing a previous version will brick your phone. (Probably permanently) This shouldn't be an issue since sm-C9000 has only one bootloader version, but check it anyways just to be sure.
Click to expand...
Click to collapse
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?

khankk42 said:
Have you tried this method and phone working fine will there will be any problem if i use this method for rooting c9000?
Click to expand...
Click to collapse
Yes, I did root my SM-C9000 using this method, and it is working nicely. Obviously I lost access to Secure Folder and Samsung Pay. You should be able to install the Play Store version of Samsung Health. Maximum Power Saving froze the phone the first two times I enabled it, but it's working fine now. One unexpected caveat is that mobile hotspot started to turn itself off if mobile data is enabled even though my carrier has no restrictions on using hotspot. You can't share your data connection using Bluetooth or usb cable neither. You can still use the hotspot for creating a local network. Other than those, I didn't experience any problems after rooting. While I was rooting, I did the mistake of using MTP to transfer the image and as a result my phone bootlooped for half a day but if you follow the instructions, that won't be a problem.
Of course, I don't guarantee anything and don't take responsibility, but there is no reason anything should go wrong.

My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?

otocu said:
My base band R16NW.C9000ZHU1CSC1, model number SM-C9000, android 8.0.0...
I have never rooted any phones in my life. What should i do? I search on internet but i didnt found any spesific things about "R16NW.C9000ZHU1CSC1" can you help me? Those options will work for me to ?
Click to expand...
Click to collapse
Sorry for responding late. Yes, that is the exact model that I have and rooted using the method in the post. If you feel confident, you can follow trough it and root your phone. You can grab the required firmware from Sammobile. Keep in mind that after rooting some features might stop working (like hotspot and knox-related features). Good luck!

I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!

cherrio128 said:
I got the same model of Samsung phone. I follow the steps but till step five, when i press open the files in odin and press start button, the odin will disappear in my computer. Then i try again and it failed. My phone shows: unsuppoted dev types. Here are my photos. Do you have any ideas? And i dunno how can i redo it again to root my phone. Would love to see helps from you, thanks!
Click to expand...
Click to collapse
Sorry for the late response. Searching that on the internet, it seems you might be using an old version of Odin. Please make sure you're using 3.13.1 and try again

[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

[HELP] Galaxy S7 G930A Forgot Pattern Unlock

Here is some info from my recovery menu
Samsung/heroqlteuc/heroqlteatt
8.0.0/R16NW/G930AUCU4CRE4
user/release-keys
I have a stock AT&T Galaxy S7 G930a I think on Oreo. I broke the screen around April 2017 and haven't used it since then. I just repaired the screen but I cant remember my pattern unlock and I want avoid wiping/reset because I want the data on the phone. ADB Debugging is off, bootloader isnt unlocked, it's not rooted and it's on stock recovery. What are my options to get past the pattern unlock screen to recover data without wiping/reset?
Things I've tried
"Samsung Find My Phone" to unlock the screen and while my device is listed it cant connect to the phone.
"Where's my Android" - cant find the device most likely because I've updated my Google password since 2017 and I believe Google will log you out of any device using your old password.
Deleting gatekeeper/pattern/pin files through ADB shell wont work cause ADB Debugging is off
Dr. Fone PC Software - Galaxy S7 isnt listed as supported devices
If I have no option but to reset/wipe I'm willing to use file recovery software like EaseUs to recover my deleted phone data. I've used this software to recover data on a couple corrupted hard drives and it's a must have for me now. I dont know how well it works for phones and it requires root tho. Can this phone be rooted once I reset/wipe? If so, what are the steps I would need to take?
Any guidance would be greatly appreciated

Is there another google account linked to the device? Looking at your current situation, you probably don't have any choice to wipe the device.
This specific model you mentioned (G930A) is a US model & has a Snapdragon processor. Meaning that, the bootloader is locked and cannot be unlocked to install a custom recovery with root.
You probably can use this, but it requires a data wipe, so not really useful..
[LOCKED BOOTLOADER] Temporary TWRP 3.3.1 for Samsung Galaxy S7 (Snapdragon) G930XX
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
There is this but not sure if it would help you.
[Rom][ALL_CARRIERS_G930_CRF1][Stock_Oreo_Hybrid][Safestrap_Preinstalled]
This is for All Carriers. You Do Not Need To Be Rooted To Install This Rom You Must Be On Stock CRF1 Oreo Firmware Before Starting This Takes Some Patience To Install What Is Safestrap Safestrap is a Bootstrap / Recovery for locked bootloader...
forum.xda-developers.com
All the best!

riojosepha said:
Is there another google account linked to the device? Looking at your current situation, you probably don't have any choice to wipe the device.
Click to expand...
Click to collapse
Nope, but I found this thread that I replied to the OP. How would I know what bootloader I'm on? It's said you need to be on V4
[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery] | XDA Developers Forums (xda-developers.com)
I guess you can root and install custom recovery somewhat but they require wipe. My question is at step 9 of the instructions. Here are the instructions below with my question.
"Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask "
Now right before step 9 wipe and format, while I have TWRP open can I install Aroma File Manager zip or send adb commands to delete gatekeeper, pin, pattern unlock files, then reboot so I can get past my phones unlock pattern? This is all I'm trying to accomplish. I just want to confirm before I process because I don't want to wipe my data. 'm trying to recover pictures and videos from this phone.

KayKay919 said:
Nope, but I found this thread that I replied to the OP. How would I know what bootloader I'm on? It's said you need to be on V4
[Easy_Root/Unroot][Any_Oreo/Nougat_Firmware_V4_Bootloaders][Tmp_Twrp_Recovery] | XDA Developers Forums (xda-developers.com)
I guess you can root and install custom recovery somewhat but they require wipe. My question is at step 9 of the instructions. Here are the instructions below with my question.
"Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask "
Now right before step 9 wipe and format, while I have TWRP open can I install Aroma File Manager zip or send adb commands to delete gatekeeper, pin, pattern unlock files, then reboot so I can get past my phones unlock pattern? This is all I'm trying to accomplish. I just want to confirm before I process because I don't want to wipe my data. 'm trying to recover pictures and videos from this phone.
Click to expand...
Click to collapse
Don't install any aroma file manager, you can just plug your phone into your computer and then your data would be mounted onto your computer.
I hope everything goes well!
EDIT: You are on V4 or Binary 4 as noted in G930AUCU(4)CRE4 (the 4 meaning version 4 or binary 4)