[TWRP OFFICIAL] [3.2.1-0] c9ltechn/SM-C9000 Galaxy C9 Pro - Samsung C9 Pro ROMs, Kernels, Recoveries, & Other

TWRP for C9LTECHN/SM-C9000 Galaxy C9 Pro
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
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 forces Samsung to provide hardware warranty regardless of software status.)
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.)
PLEASE BEFORE YOU FLASH ROMS MAKE A COMPLETE BACKUP OF YOUR SYSTEM INCLUDING EFS SO YOU DO NOT BRICK YOUR MOBILE
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to intall TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock”checkbox/toggle and make sure you Check it or turn it ON.
4) Now Boot your Samsung Android device into Download mode.To Do So Follow the steps below
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not then your device is not connected properly
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Click the Start button on Odin to start Flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up
Your device will automatically reboot when Odin is done flashing. Now You can disconnect your device.
Done!!! TWRP is now installed on your device
NOTE: YOU MAY HAVE TO UNCHECK AUTO REBOOT IN THE OPTIONS TAB IN ODIN
TWRP source code: https://github.com/TeamWin
Source code device tree: https://github.com/travismills82/twrp_android_device_samsung_c9ltechn https://github.com/TeamWin/android_device_samsung_c9ltechn/
TWRP Nougat Download: https://www.androidfilehost.com/?fid=889964283620775437
TWRP Oreo Download: https://www.androidfilehost.com/?fid=1322778262903985796
no-verity-no-encrypt: https://www.androidfilehost.com/?fid=745425885120752506
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Contributors @travis82 @k2wl @deadman96385

I can confirm this works. backup, mount data, restore, otg usb, install.
I am runnung it now

Does this work on a SM-C9000?

Flavio said:
Does this work on a SM-C9000?
Click to expand...
Click to collapse
That's already for C9000. Can't you see the c9ltechn article. That's c9 pro's code

Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?

Flavio said:
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Click to expand...
Click to collapse
You can flash any file still that just an article but you can't mount data anymore or backup data

I can flash files but cannot mount Data. I presume it is still encrypted despite being formatted twice?

Format data and reboot to recovery

ivanox1972 said:
Format data and reboot to recovery
Click to expand...
Click to collapse
So in TWRP format Data and then reboot again in TWRP.
And then flash SuperSU and no_verity?

Ok, I formatted Data twice in TWRP. Mounting Data works.
I flashed SuperSU in TWRP. Mounting Data works.
I flashed no_verity. Mounting Data works.
I rebooted into TWRP. Mounting Data works.
I rebooted into system and then switched off and rebooted into TWRP. Mounting Data does not work.
What am I doing wrong?
Correction:
I have now used this no-verity-no-encrypt_ashyx file:
https://www.androidfilehost.com/?fid=24591000424951049
And now Data stays decrypted!

I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?

I tested it few days, it works perfect and it is perfectly debloated

Please share Travis. Thank you for your work.

travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
can you share it please ???

I presume you would have to flash GApps separately with this ROM?

Flavio said:
I presume you would have to flash GApps separately with this ROM?
Click to expand...
Click to collapse
no god no, HK firmware has gapps built in like normal. I'll tweak it up some more and release it today on a separate thread. Right now I'm trying to get kernels to boot-up since they compile fine.

travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
I am interested, currently I just using the package disabler to disable all bloat samsung app..
do you have flashable s8 systemui for c9pro.. thanks

TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.

travis82 said:
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
Click to expand...
Click to collapse
Awesome work buddy, ill try to make my own ROM for this device :highfive:

will be pushing f2fs and ntfs support soon too when TWRP becomes official.

Related

[RECOVERY][ROOT] TWRP 3.0.2-1 for Samsung Galaxy SM-J710F

This is TWRP 3.0.2-1 ported from official SM-J700 to SM-J710 using stock kernel (zImage) from SM-J710FN, and it fortunately works (atleast to root this thing).
Disclaimer: Flashing this gon' trip knox & you lose your (device's) warranty.
Built from official SM-J700F recovery
Kernel & Device Tree from SM-J710F 6.0.1
No "SEANDROID ***" red warning
Flash via ODIN & enjoy
TWRP: https://www.androidfilehost.com/?fid=24533103863141296
Kernel: https://www.androidfilehost.com/?fid=24533103863141293 (Stock 6.0.1 with disabled dm-verity & encryption)
Note: As per my experiences, it is recommended to flash the Kernel, then recovery, then "FORMAT DATA" (not just wipe) to disable encryption. Otherwise, TWRP will not be able to mount /data.
I flashed this SuperSU in system-less mode & I was rooted with no (visible) issues. Anything else like backing up, I didn't try.
EDIT:
If you want to keep encryption, simply flash recovery & upload SuperSU package via sideload.
EDIT:
Recommended Installation Flow:
Flash TWRP via ODIN
Flash Kernel via ODIN
Reboot to Recovery (TWRP)
Wipe > Format Data > "yes"
Reboot to Recovery (TWRP)
Flash latest SuperSU zip (anything > 2.46)
@vaibhavpandeyvpz
OMG!! you did it :good:
Thank you soo much...
Edit
Cannot boot into recovery mode just gets stuck on Galaxy J7(6) logo?
Disable DM-Verity & Encryption
Prince Chandela said:
@vaibhavpandeyvpz
OMG!! you did it :good:
Thank you soo much...
Edit
Cannot boot into recovery mode just gets stuck on Galaxy J7(6) logo?
Click to expand...
Click to collapse
I, myself have recently met this issue just now. The /data encryption & dm-verity might be causing such issue. Please check updated download links in post to download extracted kernel image from 6.0.1 stock ROM with modifed ramdisk and slightly updated TWRP which now boots fine everytime I try to as of yet.
vaibhavpandeyvpz said:
I, myself have recently met this issue just now. The /data encryption & dm-verity might be causing such issue. Please check updated download links in post to download extracted kernel image from 6.0.1 stock ROM with modifed ramdisk and slightly updated TWRP which now boots fine everytime I try to as of yet.
Click to expand...
Click to collapse
This didn't work i was able to boot in recovery but i can't see files and folders in storage (OTG,Internal,External)
On top of this
DEVICE DOESN'T BOOT now stuck on boot animation
Prince Chandela said:
This didn't work i was able to boot in recovery but i can't see files and folders in storage (OTG,Internal,External)
On top of this
DEVICE DOESN'T BOOT now stuck on boot animation
Click to expand...
Click to collapse
When I was stuck at the bootloader logo, I rebooted to Download mode and did hit Cancel to restart normally.
EDIT:
If you want to restore original recovery, I can provide you with the stock image as well from SM-J710FN.
EDIT:
If you want to root but can't see your files within, you can always sideload.
vaibhavpandeyvpz said:
When I was stuck at the bootloader logo, I rebooted to Download mode and did hit Cancel to restart normally.
EDIT:
If you want to restore original recovery, I can provide you with the stock image as well from SM-J710FN.
EDIT:
If you want to root but can't see your files within, you can always sideload.
Click to expand...
Click to collapse
Please provide me stock recovery and kernel image.
EDIT
i no longer need them. the cause of boot loop was your kernel. I tried to sideload supersu zip but i still can't get rooted this is because twrp can't access /data partition and supersu requires that in system less root.
vaibhavpandeyvpz said:
This is TWRP 3.0.2-1 ported from official SM-J700 to SM-J710 using stock kernel (zImage) from SM-J700FN, and it fortunately works (atleast to root this thing).
Disclaimer: Flashing this gon' trip knox & you lose your (device's) warranty.
Built from official SM-J700F recovery
Kernel & Device Tree from stock 6.0.1 recovery
No "SEANDROID ***" red warning
Flash via ODIN & enjoy
TWRP: https://www.androidfilehost.com/?fid=24533103863141296
Kernel: https://www.androidfilehost.com/?fid=24533103863141293 (Stock 6.0.1 with disabled dm-verity & encryption)
Note: As per my experiences, it is recommended to flash the Kernel, then recovery, then "FORMAT DATA" (not just wipe) to disable encryption. Otherwise, TWRP will not be able to mount /data.
I flashed this SuperSU in system-less mode & I was rooted with no (visible) issues. Anything else like backing up, I didn't try.
EDIT:
If you want to keep encryption, simply flash recovery & upload SuperSU package via sideload.
Click to expand...
Click to collapse
why you don't use j710 kernel and dt image to build it to have fully working twrp ?
messi2050 said:
why you don't use j710 kernel and dt image to build it to have fully working twrp ?
Click to expand...
Click to collapse
It's already using the kernel from the new device, it was a typo. Edited OP.
Prince Chandela said:
Please provide me stock recovery and kernel image.
EDIT
i no longer need them. the cause of boot loop was your kernel. I tried to sideload supersu zip but i still can't get rooted this is because twrp can't access /data partition and supersu requires that in system less root.
Click to expand...
Click to collapse
TWRP cannot access the /data partition because it is encrypted. I did "FORMAT DATA", then rebooted to recovery via TWRP > Reboot > Recovery. Now the TWRP should be able to mount /data and you could install supersu.
vaibhavpandeyvpz said:
TWRP cannot access the /data partition because it is encrypted. I did "FORMAT DATA", then rebooted to recovery via TWRP > Reboot > Recovery. Now the TWRP should be able to mount /data and you could install supersu.
Click to expand...
Click to collapse
But this will wipe all my apps but I'm not using a screen lock nor i setup storage encryption. i don't wanna lose my apps.
Edit:
OP it's mentioned to sideload supersu and it will work with encryption but it didn't
Prince Chandela said:
But this will wipe all my apps but I'm not using a screen lock nor i setup storage encryption. i don't wanna lose my apps.
Click to expand...
Click to collapse
I do understand that it will wipe all the data over the phone. But as per my experiences with S7 & S7E, encryption is enabled by default on Android 6.0 MM. Unless you disable encryption & reformat data, TWRP won't be able to mount /data. The kernel image I posted does not encrypt the /data partition so that you would be able to mount it in TWRP. But after flashing kernel, a FORMAT DATA is required to flush previously encrypted /data. I am sorry, but this is how things seems to work with Android 6.0. Unless TWRP includes support for encrypted partitions, we need to wipe it fully to be able to access it.
vaibhavpandeyvpz said:
I do understand that it will wipe all the data over the phone. But as per my experiences with S7 & S7E, encryption is enabled by default on Android 6.0 MM. Unless you disable encryption & reformat data, TWRP won't be able to mount /data. The kernel image I posted does not encrypt the /data partition so that you would be able to mount it in TWRP. But after flashing kernel, a FORMAT DATA is required to flush previously encrypted /data. I am sorry, but this is how things seems to work with Android 6.0. Unless TWRP includes support for encrypted partitions, we need to wipe it fully to be able to access it.
Click to expand...
Click to collapse
Okay i understand :good:
Is there any way to backup apps with their data without root?
@vaibhavpandeyvpz
I tried to flash kernel then twrp and then wiping /data partition but twrp cannot wipe data partition?
How do I flash this to my device?
@vaibhavpandeyvpz
Any updates?
when iflash Twrp File Via Ordin its fail
ithink becuse secure download is enabled
or fap lock is on ?
help please
isee that massage in download mode (coustom binary(recovery) blocked by fap lock)
thelastbad said:
when iflash Twrp File Via Ordin its fail
ithink becuse secure download is enabled
or fap lock is on ?
help please
isee that massage in download mode (coustom binary(recovery) blocked by fap lock)
Click to expand...
Click to collapse
Table build number 7 times to enable developer option then goto developer option and enable OEM-Unlock
Also follow this thread for further process
Prince Chandela said:
Table build number 7 times to enable developer option then goto developer option and enable OEM-Unlock
Also follow this thread for further process
Click to expand...
Click to collapse
it works now irooted mm thank you ^_^
---------- Post added at 02:16 PM ---------- Previous post was at 02:03 PM ----------
thelastbad said:
it works now irooted mm thank you ^_^
Click to expand...
Click to collapse
are there is root hacks program or wifi hacks?
Is there a root for my j7 2016 sm-j710gn
Sent from my SM-J710GN using XDA-Developers mobile app
Anybody pls help me
I want to root sm-j710gn ,
I try sm-j710f twrp now stcuck logo

[How to] Root, TWRP, Flash A300FU / A300Y Noob friendly guide

Bevor you do something with your Device do a Backup of all your Data (Contacts, Pic´s ect.) outside of your Device (in a Cloud or on your PC)​I'm not responsible for bricked devices, dead SD Cards, broken phone chargers etc.​You do all at your own Risk!​
If you are new, just work the first 3 steps from top to bottom.​
Flash Root & Odin3:
At the https://autoroot.chainfire.eu/ site you can Download the the Root File for your Device (Link to A300FU). When you Downloaded the "CF-Auto-Root-xxx.zip" File unzip it. In this zip you will find the Odin3xxx.exe and the Root .tar.md5 File
You need this Odin3 tool also for TWRP and going Back to Stock Rom
For Root: Make sure your device is in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3xxx.exe file, press the PDA/AP button, select the Root .tar.md5 file, and click Start, never interrupt this action! You can find more detailed instructions and assistance at [CENTRAL] CF-Auto-Root Thread
Flash TWRP:
You can Download the TWRP File at the [RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A3(2015) SM-A300F/FU/G/H/M Thread. I recommend the Build from Post 80 it has working MTP & OTG for the FU Device!
To Install Start download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the TWRPxxx.tar file, and click Start, never interrupt this action! After Reboot you can get there by holding VolUp+Home+Power when the device is turned off.
There are also a TWRP 2.8.7.0 and a TWRP 3.0.0-0 but both have small bugs so i recommend TWRP 3.0.2-1 only if you have Problems try to downgrade
TWRP Bugs:
TWRP 2.8.7.0 Can only Install CM12.1 ROMs, it has no MTP & no OTG
TWRP 3.0.0-0 Can only Install CM13 ROM & it has no MTP but OTG is Working
TWRP 3.0.2-1 Can not install @cbolumar ROMs and the Build from Opening Post has no OTG
TWRP 3.1.0 Only tested with LineageOS, it still has no MTP!!!
Flash a Custom ROM:
You can Install a ROM now with TWRP you can enter TWRP by holding VolUp+Home+Power when the device is turned off.
In TWRP IT IS HIGHLY RECOMMEND TO DO FIRST A BACKUP! (I Recommend to placed at the SD Card)
Backup -> Storage : Micro SDcard -> Ok -> [x] Boot, [x] System, [x] Data, [x] Cache, [x] Recovery, [x] EFS, [x] MODEM, [x] APNHLOS -> Swipe to Backup
If anything goes wrong you can easy Restore your Device in TWRP without losing anything, so it's also recommended to Backup your Custom ROM
Now you need your Custom Rom, Google Apps like Opengapps for ARM and i recommend latest Magisk[/URL, OR (if you prefer) [URL="http://download.chainfire.eu/supersu"]SuperSU to Manage Root Access.
Place this zip Files at your Device (I Recommend to placed at the SD Card)
Now you enter TWRP and go to:
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Cache -> Swipe to Wipe
Now go back to main menu and select:
Install -> Storage : Micro SDcard -> Ok -> now choose your ROM zip first, you can "Add More Zips" and choose Gapps zip and if you want you can Add direct Magsik OR SuperSU zip as well -> Swipe to Confirm Flash
After placing files the Device need a Reboot, at the First Start it will Install your Rom, so be patiently at first start!
Flash Xposed:
Magisk user on Android M (6.x) or better follow this Thread [2018.5.6][Magisk] Systemless Xposed v89.3/v90.2-beta3 (SDK 21-27) by topjohnwu
SuperSU user on Android M (6.x) or better follow this Thread [OFFICIAL] Xposed for Lollipop/Marshmallow/Nougat/Oreo [v90-beta3, 2018/01/29]
info:
SDK 21: Android 5.0 | SDK 22: Android 5.1 | SDK 23: Android 6.0 | SDK 24: Android 7.0 | SDK 25: Android 7.1 | SDK 26: Android 8.0 | SDK 27: Android 8.1
at CM12.1 ROM's Offical Xposed works fine.
Download the "sdk22-arm" zip, and Install it with TWRP first start need a long time! be patient!
After the Framework is installed you install the "XposedInstaller" apk, done.
For stock rom you should visit [UNOFFICIAL] Xposed for Samsung Lollipop by arter97 but it´s for deodex'ed ROMs for this you should visit [Deodex][SM-A300] Deodex Thread for Samsung Galaxy A3
emtepe35 said:
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Click to expand...
Click to collapse
Flash Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.
You should not try to Flash 4.x ROMs it could Brick your Device!
With a Stock Marshmallow ROM it is recommended to use a Custom Kernel
A300FU / A300Y Custom Kernel:
Kraken Kernel R1 from @bulgar
Will only work with at Stock Marshmallow (6.x) ROM
-soon- LineageOS Support
hadesKernel from @corsicanu
Will only work with at Stock Marshmallow (6.x) ROM
A300FU / A300Y Modification:
[MOD][Stock Rom] Enable More Quick Tiles on Touchwiz from @astrit1
Will only work with at Stock Lollipop (5.x) ROM
There are still the following Bugs:
No Bugs
[ROM][A300FU][6.0.1] [GS]Mod from @[GS]
There are still the following Bugs:
Private Mode Not Work
WHASISTROM We have a simple stock rom [A300FU/OL3/OJ5] from @nowheel Discontinued
nowheel said:
Bad news i abbandoned project.. after my hdd is broken with project and all whasistrom file, work document and other.
Click to expand...
Click to collapse
A300FU / A300Y Custom ROMs:
Check also in All Samsung Galaxy A3 (2015)'s ROMs Thread from @Falaysia
-Recommended-
LineageOS 15.1 Unofficial for Samsung Galaxy A3 (2015) from @vl_w
There are still the following Bugs:
* FM works only on headphones
* Unable to capture video in 1080p (only 720р works)
* Incorrectly work with secondary sim (incall sound issues)
* On FU and H doesn't adjusting flahlight brightness
* On H incorrectly detecting battery temperature
* Hardware keystore doesn't work (only software)
* NFC sometimes doesn't work
LineageOS 14.1 Unofficial for Samsung Galaxy A3 from @vl_w
There are still the following Bugs:
no Bugs
CyanogenMod 12.1 for Samsung Galaxy A3 from @evilracer123 Discontinued
Meizirkki said:
OP is no longer working on a300fu
Click to expand...
Click to collapse
In the Opening Post is not the latest Build!
This is the post with the last Build from 19th January 2016
evilracer123 said:
Here's the newest build:
https://mega.nz/#!OcJ0BKKQ!hkQN4SnzY-40tm9v79vzP_erZxIxtpa0_jPwMvLQaiU
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-Folders are not displayed correctly with LCD density 260 DPI (can be Fixed by changing it to 240 DPI)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
-for some users gps are not Working
at my device:
-Cast screen is not Working
CyanogenMod 12.1 Resurrection Remix from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by open integrated Kernel Adiutor and allow Root access)
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
CyanogenMod 12.1 from @cbolumar Discontinued
garbanura said:
he switched to a5 and abandoned a3 for good, i know from first hand sorry.
Click to expand...
Click to collapse
There are still the following Bugs:
-SoD´s (can be Fixed for the most users by using CPU Awake - Wake Lock with Unlimited time & Activate on Reboot (Clean Master turns it off btw) or Wake Lock - PowerManager with "PARTIAL_WAKE_LOCK")
-Preview in stock camera (can be Fixed by change Resolution to 16:9 in Settings)
-FM Radio not Working (can be Fiexed by using Spirit2)
-When screen is off touch buttons still working, at touch the phone vibrates.
-USB Conection adb only working MTP, PTP, OTG or UMS not Working (you can use MTP and OTG in TWRP 3.0.2-1 Recovery)
-for some users "com.qualcomm.timeservice" fc time to time (can be Fixed by disable the automatic services in Time settings)
at my device:
-Cast screen is not Working
Note: can only installed with TWRP 2.8.7.0 after installing you can upgrade your Recovery to TWRP 3.0.2-1
Hope this will Help to answering the most Questions
By the way i'm not a Dev, i'm only a regular user that wants to help!
You will also get Information and Help at the Everything Samsung a3 Thread :good:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
King-V said:
Nice guide. Which one would you recommend between the CM12.1 and CM12.1 RR?
Also, for downgrading TWRP, you just need to flash the older version, right?
Click to expand...
Click to collapse
Definitely CM12.1 RR!
Right just flash first TWRP 2.8.7.0 via Odin3 install the ROM and than Flash TWRP 3.0.2-1 via Odin3, btw. the Build from post 80 has a working MTP and OTG in TWRP (only in TWRP not at the ROM!)
And you can anytime time flash TWRP 2.8.7.0 again if you have to Install new
So only good ROM for daily driver will be @mygalaxya cm13?
emtepe35 said:
So only good ROM for daily driver will be @mygalaxya cm13?
Click to expand...
Click to collapse
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Jonny_Hood said:
This could need some time, i recommend to try CyanogenMod 12.1 Resurrection Remix, or a Stock MM with aresKernel :good:
Click to expand...
Click to collapse
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
emtepe35 said:
It's lot to do with RR to make it stable without SOD etc. (I really need normal usb connection for daily usage)
What's twrp should I use with stock mm to flash ares kernel and can I go back to lollipop via odin? (Mygalaxya's cm13 needs LP bootloader and modem)
Click to expand...
Click to collapse
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Jonny_Hood said:
Best is TWRP 3.0.2-1 and yes you can go back anytime via odin
Click to expand...
Click to collapse
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
emtepe35 said:
Thanks I tried this but I flashed wrong firmware and wifi was broken but I know how to repair it.
Tomorrow I'll try flash compatible firmware and try again.
After flash MM and reflash LP it was a bootloop in first boot. I went to download mode and flash twrp then restore backup and it boots up.
Thanks
Click to expand...
Click to collapse
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Jonny_Hood said:
This Bootloop thing happened at my Device sometimes too, if i flashed a stock ROM via Odin, thats why i started to Wipe all Partitions via TWRP before flashing, that works for me flawless
Than happy flashing tomorrow
Click to expand...
Click to collapse
OK I've got one last question the wipe in twrp means it deleting it to zero and if I accidentally go to system and not to download I'll get hard brick? Or wipe means it restoring it to factory files? Wipe modem too?
Sorry for noob questoms but I want to be sure before do anything
emtepe35 said:
Wipe in twrp means it deleting it to zero?
Click to expand...
Click to collapse
Yes
emtepe35 said:
If I accidentally go to system and not to download I'll get hard brick?
Click to expand...
Click to collapse
No it will not brick, if you accidentally go to system it will stuck at A3 logo, than you can go to Download Mode with pressing "VolDown+Home+Power" for 30 Sec
emtepe35 said:
Or wipe means it restoring it to factory files? Wipe modem too?
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> [x] Dalvik / ART Cache, [x] System, [x] Data, [x] Internal Storage, [x] Cache -> Swipe to Wipe -> go back -> go back -> Format Data -> yes
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Razvan said:
Added to Sticky Roll-Up Thread
Cheers
Razvan
Forum Moderator
Click to expand...
Click to collapse
Thank you very much
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
emtepe35 said:
What about stock marshmallow xposed?
Sorry I'm noob and I can't find it alone.
Click to expand...
Click to collapse
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Jonny_Hood said:
As far i know, it will not working with Stock MM.
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
emtepe35 said:
I had a LP stock Samsung touch wiz and it was working. Some people tells they have MM xposed. I'll try to ask them
Click to expand...
Click to collapse
Let me know if and how it work
I'm happy with this.
Working only on MM touchwiz (tested by me on A300FU with TWRP 3.0.2-1)
How to install:
- Install this Xposed Installer App version http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
- Make a nandroid backup
- Copy the Xposed file and the uninstaller to your sdcard
- Flash "xposed-vxx.x-sdkxx-tw-armxx-custom-build-by-wanam-xxxxxxxx.zip" through a custom recovery (TWRP/CWM...)
- Reboot and Waiiiiiiiiit, it may take several minutes to boot up depending on your Rom size.
xposed.zip download (ARM SDK23)
https://www.androidfilehost.com/?fid=24591000424962808
Official thread link:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
InfamousMykol said:
Hi, what I have to do to downgrade my A300FU to lollipop (Brand Italy Vodafone)?
Click to expand...
Click to collapse
Stock ROM:
Download your Firmware at Sammobile than i recommend you to Wipe all (Advanced Wipe) in TWRP except the SDcard!
Boot your Device in ODIN download mode (you can get there by holding VolDown+Home+Power when the device is turned off), then start the Odin3xxx.exe file, press the PDA/AP button, select the .tar.md5 file, and click Start, never interrupt this action!
After doing this you lose TWRP and Root so if you need it you have to install it new.

[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!)

Unofficial TWRP for Moto G5S Plus (Sanders)​
Additional Features over Official TWRP:
Supports flashing of both 32bit and 64bit ROMs and Kernels.
OREO Images/ROMs support.
Decryption and Encryption support.
No SuperSU by default.
No TWRP app.
No HTC Dumlock cruft.
Updated pigz compressor (slightly faster and more tolerant of corruption).
NTFS support(Both Read and Write).
Covers more partitions for nandroid backup (OEM, FSG and FSC).
Experimental support for SD cards that are partitioned for partial adopted storage and partial removable storage.
Faster I/O performance.
Fixed Gapps/aroma freeze issues.
IMPORTANT!!! : READ INSTRUCTIONS CAREFULLY BEFORE PROCEEDING TO FLASHING PROCESS..!!
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either Magisk or flash any of the verity disabler zips available on xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Flashing Instructions:
Using Existing TWRP:
Reboot to recovery > Click on Install > Install Image > recovery > select recovery image and flash > reboot to recovery
Other Methods(Fastboot) :
Make sure you have unlocked bootloader
Reboot to bootloader
Enter following command in terminal: fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary boot)
Incase your device is encrypted (while coming from stock rom), Follow these steps to decrypt:
Reboot to recovery > cancel the password prompt > mount all partitions > Format Data/Userdata (on f2fs) > Reboot Recovery > Mount all partitions again > Flash Magisk > Reboot
Now you are free to use Stock ROM (Decrypted) or Flash any custom rom you want.
Download Links: https://www.androidfilehost.com/?w=files&flid=216298
TWRP Themes: Check 3rd post
Known Issues: None || Report if you find any.
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][Sanders] TWRP-3.2.1-r20 (64bit Supported!), Tool/Utility for the Moto G5S Plus
Contributors
CheckYourScreen
Source Code: https://github.com/CheckYourScreen/twrp_device_motorola_sanders
Version Information
Status: Stable
Current Stable Version: r20
Stable Release Date: 2018-04-04
Created 2017-10-26
Last Updated 2018-04-04
|| Changelog ||
r20:
Fixed Encryption support on custom roms.
Updated kernel
Updated build fingerprint for latest bootloader support.
Reverted pigz changes.
Switched back to original twrp themes. (TWRP Themes can be found in 3rd post )
Various bug fixes and improvements.
r16:
Fixed compatibility with New Bootloader (C2.07-December patch)
Merged october patches in kernel.
Various twrp upstream patches and fixes.
Fixed remote wipe process (Earlier remote wipe issued from play account wasnt processed due to twrp)
r15:
Added 64bit Support (You can flash both 32bit/64bit roms or kernels with it).
Fixed Encryption Support! (No need to format data to decrypt and mount).
Updated to 3.2.1 upstream changes with full oreo support.
Remove android reboot during password check on multiple wrong inputs.
r9:
Fixed F2FS mount issues(You can flash magisk modules or SuperSu now).
Enabled NTFS Write Support (You can make backups on sdcard/pendrives formatted on NTFS).
Fixed size of various partitions.
Switched to LZMA compression to decrease size.
r7: Initial Public Release
|| Themes ||
Here are some of the twrp themes:
Preview images: https://photos.app.goo.gl/DLrfDseGzfxE8Uq93
Download link: https://androidfilehost.com/?w=files&flid=233551
:good:
Only one that has actually be working for me ever since I got the phone. Thank you for your efforts.
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Well my guess is that the kernel in the present twrp is from the -26 firmware posted in the other thread. That firmware was US Retail also. The OP in the other thread states in can be used on other models. But I am not going to tell you that because I do not know. I have not found any other firmware for the sanders model.
Ae3NerdGod said:
this seems to suffer from the same thing the stock rom/kernel suffers from, the weird f2fs bug that makes certain mounts fail. geneticengineer has shared a kernel that fixes this in stock rom , maybe you could get in touch with him about how he updated f2fs
Click to expand...
Click to collapse
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
revengineer said:
Thank you for your work, this seems to work well on my device. If you would like to swap the kernel, I posted a newer firmware NPS26.116-45 here:https://forum.xda-developers.com/showpost.php?p=74325160&postcount=33
Click to expand...
Click to collapse
Schrotty35 said:
But its for xt1806 only i think. Not real help. The most user here are outside usa.
Click to expand...
Click to collapse
Stock kernel is same in both the firmwares.
-45 is just for US variant, i dont recommend you to even flash that firmware on other variants.
CheckYourScreen said:
Afaik it doesnt affect TWRP, you just need to be on a custom kernel if you are running stock rom.
Twrp has nothing to do with it.
If you face any problem flashing anything then post a screenshot or log.
Click to expand...
Click to collapse
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Ae3NerdGod said:
but i have a custom stock kernel, and things that fail in TWRP work in flashfire or magiskmanager
its mostly magisk modules im having problems with, ill reproduce an error when i get the chance
Click to expand...
Click to collapse
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
CheckYourScreen said:
Flash the magisk module via twrp > take screenshot when flashing completes > go to advance section of twrp and take recovery log > reboot system > send that screenshot and recovery log here.
Click to expand...
Click to collapse
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Ae3NerdGod said:
will do, it happens with every magisk package i try. they used to fail in stock too till i used geneticengineers kernel from telegram now they work
didnt know you could screenshot in recovery, i assume its the same buttons
Click to expand...
Click to collapse
Yes, same buttons to take a screenshot in TWRP
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
gewe said:
TWRP backup is frozen at 13% completed. The progress bar is still showing its animation.
I unlocked the bootloader, and then rebooted. Android came up with the language selection screen. I powered off, connected the phone to the PC, and booted into TWRP (not flashed yet):
Code:
fastboot boot twrp-3.1.1-sanders-r7.img
I did not let TWRP format /data.
Then I started a backup, selecting all partitions, so that I could always go back after flashing TWRP and Magisk.
Does anyone know why backup is stuck at 13%? Last log line says "Backing up System..."
I tapped "Cancel" after two hours. That stopped the progress bar animation, but not the backup itself.
BTW: I used TWRP from this thread, the one in another thread freezes at the TWRP boot logo.
Edit: after two hours I killed the backup by powering down (the only way it seemed). On retry it froze at 21%.
Edit 2: Retried, this time backing up everything except system. No problem. I then tried to backup system. Frozen at 1%. What is the problem here?
Edit 3: Finally, a complete backup of system! Only one to go: system_image. But unfortunately that froze at 0%. Every subsequent try freezes at 1666MB (40%). The card has over 30GB free. I tried backup to USB-OTG, but that also froze.
Click to expand...
Click to collapse
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
CheckYourScreen said:
Might be due to data partition being encrypted, you cant write anything in it without decrypting it first.
Format data and reboot recovery, then make the backup. You can flash magisk after taking the backup.
Btw r9 new release on its way with some really important changes
Click to expand...
Click to collapse
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
gewe said:
I was not trying to write the backup to the data partition, but to external SD card (tried OTG-USB as well without success).
I have flashed TWRP, formatted the data partition, and flashed Magisk. I have not tried to create a new backup yet. First I want to find out why Magisk does not pass the Safetynet check.
Can't wait to see what r9 brings. Thanks for your efforts. :good:
Click to expand...
Click to collapse
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
lilcdroid said:
Magisk won't pass safety net with stock boot.img (kernel). Here is a modified kernel.
https://forum.xda-developers.com/showthread.php?p=73930507
After flashing new kernel Magisk passes no problem.
Sent by way of magic
Click to expand...
Click to collapse
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Brycearuuni said:
When I flash this my WiFi stops working completely. I'm running aosp extended rom. I'm not sure if I can achieve battery life as good as I can on the stock ROM as I can on this one so im not sure what I should do about that..
Click to expand...
Click to collapse
Sorry I wasn't aware you weren't still on stock. That kernel will only work on stock. I would verify with the maintainer of AOSP extended ROM that the kernel is patched to work with Magisk.
Sent by way of magic

[RECOVERY LOCKED/Nougat/7.0][G892U/A] Safestrap Recovery v4.11 B01 [Dec 10, 2019]

Samsung Galaxy S8 Active (Snapdragon)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.11-B01 [Nougat:7.0]
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 3.3.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
APK install:
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
APK:
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
Flashable zip:
Flash using Safestrap recovery or FlashFire.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again.
DOWNLOADS:
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 Active G892U (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.11-B01-CRUISERLTE-SS-FF-flashable.zip
LATEST APK: Safestrap-4.09-B01-CRUISERLTE.apk
androidfilehost
CONFIRM THAT YOU ARE USING A SAMSUNG GALAXY S8 Active G892A (Snapdragon) [Nougat:7.0]
LATEST ZIP: Safestrap-4.11-B01-CRUISERLTEATT-SS-FF-flashable.zip
LATEST APK: None
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode, DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery.
@jrkruse for pointing me that S8 has permissive root. @partcyborg for getting root on S8.
CHANGELOG:
4.11-B01 [2019-04-19]
- TWRP updated to 3.3.1.
- Add proper G892A device support.
- Clean up hijack.
- Fix datamedia mount.
- Enhanced Safestrap logo.
- More stuff I forgot, lol
4.09-B01 [2019-04-19]
- TWRP updated to 3.3.0.
- Fix reboot function
- Add reboot to safestrap button in reboot menu
- Add Edl button in reboot menu
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
4.08-B01 [2019-03-01]
- TWRP updated to 3.2.3.
- Fix datamedia mount.
- Add hijack-backup during image flashing.
- Major code clean up
- Initial release.
BUGS:
- ROM-slots not working for now.
Great job. I will try to flash stock oreo and this safestrap via this safestrap. So i review to keep it on stock oreo.
After test, it works fine. But I can't keep it with stock oreo.
Can you enable adbd insecure on twrp? Thanks.
quanqw said:
Can you enable adbd insecure on twrp? Thanks.
Click to expand...
Click to collapse
Not sure.
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
epiphany74721 said:
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
Click to expand...
Click to collapse
That's normal click recovery to go-to safestrap. Bte this is supposed to be for US variants kinda lucky you didn't brick as the model it's for is listed in the title
epiphany74721 said:
does it work on s8 sc-02j docomo it just say safestrap is disabled recovery and continue but when i choose recovery its still TWRP
Click to expand...
Click to collapse
You device is unlocked right? why you need safestrap?
afaneh92 said:
You device is unlocked right? why you need safestrap?
Click to expand...
Click to collapse
i got data mount issue on twrp cant install rom i want to replace it with safestrap recovery
epiphany74721 said:
i got data mount issue on twrp cant install rom i want to replace it with safestrap recovery
Click to expand...
Click to collapse
Type this in terminal or in twrp terminal then copy output or take screen shot.
"ls -al /dev/block/platform/soc/1da4000.ufshc/by-name"
I will make twrp for you.
afaneh92 said:
Type this in terminal or in twrp terminal then copy output or take screen shot.
"ls -al /dev/block/platform/soc/1da4000.ufshc/by-name"
I will make twrp for you.
Click to expand...
Click to collapse
here sorry for the late reply a little busy ang my imei is corrupted also cant install s8 docomo 8.0 all corrupted in samfirm wont install oreo also
epiphany74721 said:
here sorry for the late reply a little busy ang my imei is corrupted also cant install s8 docomo 8.0 all corrupted in samfirm wont install oreo also
Click to expand...
Click to collapse
First safestrap not working on oreo/pie without permissive kernel. Try this
https://www.google.com/amp/s/forum....rnel-permissive-patcher-android-t3506338/amp/
I will make you twrp soon. Will pm you when its ready.
Edit: no need to build new twrp for your device, data encrypted on oreo/pie.
After booting in TWRP download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
afaneh92 said:
First safestrap not working on oreo/pie without permissive kernel. Try this
https://www.google.com/amp/s/forum....rnel-permissive-patcher-android-t3506338/amp/
I will make you twrp soon. Will pm you when its ready.
Edit: no need to build new twrp for your device, data encrypted on oreo/pie.
After booting in TWRP download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
Click to expand...
Click to collapse
I switched to s8 dual g9500. It has twrp from @jesen but it has an issue. Can you fix it?
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
quanqw said:
I switched to s8 dual g9500. It has twrp from @jesen but it has an issue. Can you fix it?
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-s8-s8-snapdragon-t3636718
Click to expand...
Click to collapse
You should ask in that thread
4.09-B01 is up
- TWRP updated to 3.3.0.
- Fix reboot function.
- Add reboot to safestrap button in reboot menu.
- Add Edl button in reboot menu.
- Move Boot Options to advanced menu items.
- Safestrap app: Update topjohnwu's libsu to 2.4.0.
- Safestrap app: Update install recovery function.
Damn, needs root. I misread the post at first so ignore my previous question.
Hi,
I just installed this on my g892a, however it fails to mount /data. It looks like it's trying to mount /dev/block/sda24, however, on my phone it's actually /dev/block/sda23:
I tried changing the partition in /etc/safestrap/ss.config but that didn't do anything
Is there anything I can do to get it to mount, or do you need to recompile twrp?
Thanks!
cd109876 said:
Hi,
I just installed this on my g892a, however it fails to mount /data. It looks like it's trying to mount /dev/block/sda24, however, on my phone it's actually /dev/block/sda23:
I tried changing the partition in /etc/safestrap/ss.config but that didn't do anything
Is there anything I can do to get it to mount, or do you need to recompile twrp?
Thanks!
Click to expand...
Click to collapse
You need to edit twrp.fstab and ss.config in twrp recovery too.
I will try to add support for G892A in the next build.
afaneh92 said:
You need to edit twrp.fstab and ss.config in twrp recovery too.
I will try to add support for G892A in the next build.
Click to expand...
Click to collapse
Alright, I haven't built twrp / safestrap before so I'm having some trouble figuring it out, but I don't want to bug you with that. I do have a question though - when i get this working, could i flash a rom (to the stock rom slot) like a stock oreo rom with the same bootloader revision and keep safestrap installed? And then if I wanted to I could restore the backup of the nougat rooted rom? It looks like it can be done with the regular s8, but I'm confused as to whether it would work here or what I would need to do.
cd109876 said:
Alright, I haven't built twrp / safestrap before so I'm having some trouble figuring it out, but I don't want to bug you with that. I do have a question though - when i get this working, could i flash a rom (to the stock rom slot) like a stock oreo rom with the same bootloader revision and keep safestrap installed? And then if I wanted to I could restore the backup of the nougat rooted rom? It looks like it can be done with the regular s8, but I'm confused as to whether it would work here or what I would need to do.
Click to expand...
Click to collapse
Rom slot is broken on arm64 devices.
You can use stock slot only.

Galaxy SII custom firmware / root in 2021

I have a Samsung Galaxy SII ( GT-I9100 ) which was retrieved from a dumpster. I love the removable battery. I would like to know what custom firmware you recommend for it. I could also use any tutorials you recommend to flash it. I have looked at some but I wonder which is best for my requirements:
* The latest Android release is unimportant (I can live with Android 5.0 to be honest)
* Having Google bundled apps is unimportant (all Google apps will be uninstalled, if present).
* I want the good reliability / stability and no alpha or beta releases.
I am only interested in root access & reliable firmware with which I can install open-source apps from f-droid.org. Thanks for any suggestions.
comfortable said:
I have a Samsung Galaxy SII ( GT-I9100 ) which was retrieved from a dumpster. I love the removable battery. I would like to know what custom firmware you recommend for it. I could also use any tutorials you recommend to flash it. I have looked at some but I wonder which is best for my requirements:
* The latest Android release is unimportant (I can live with Android 5.0 to be honest)
* Having Google bundled apps is unimportant (all Google apps will be uninstalled, if present).
* I want the good reliability / stability and no alpha or beta releases.
I am only interested in root access & reliable firmware with which I can install open-source apps from f-droid.org. Thanks for any suggestions.
Click to expand...
Click to collapse
Lineage OS 17.1 Android 10, that works pretty well.
[ROM][UNOFFICIAL][10.0.0][r41][I9100] LineageOS 17.1
/* ** Your warranty is now void. ** ** We are not responsible for bricked devices, dead SD cards, ** thermonuclear war, or you getting fired because the alarm app failed. Please ** do some research if you have any concerns about features included...
forum.xda-developers.com
Another opportunity for you would be replicant. It is based on LineageOS, but tries to run on free-software only and a mainlined kernel. They don't ship with any google apps and and offer Android 6 (currently upgrading to Android 9 for all of their devices.
You will need modified TWRP to flash this and do not ask me why.
You need odin 3.07 as it is the last version of odin that supports S II.
Odin 3.07 https://odindownloader.com/download/odin3-v3-07
Update offically to 4.1.2, Delete All Samsung and Google accounts, go to settings and phone information, click 7 times build number(Just randomly click All numbers 7x and you will eventually done), go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Pit: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN Options tab:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
10. Flash the modified TWRP here https://androidfilehost.com/?fid=8889791610682894303 by Transferring TWRP.img to phone via USB cable≧Flash≧select image≧this image
11.Go to home and Reboot≧recovery
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
well gapps also not builded in in lineageos.
Thanks for all the responses. All the choices sound like they will get the job done. I'm currently deciding which one to try first.
jjgvv said:
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
Click to expand...
Click to collapse
Much appreciated. I was preparing all the files you mentioned but got a broken link on this one. Could you re-check please?
comfortable said:
Thanks for all the responses. All the choices sound like they will get the job done. I'm currently deciding which one to try first.
Much appreciated. I was preparing all the files you mentioned but got a broken link on this one. Could you re-check please?
Click to expand...
Click to collapse
lineage-17.1-20210107-UNOFFICIAL-i9100.zip | by rINanDO for Galaxy S2
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
jjgvv said:
go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Click to expand...
Click to collapse
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
comfortable said:
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
Click to expand...
Click to collapse
you are not carrier locked or sth?
comfortable said:
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
Click to expand...
Click to collapse
I will give you a alternative way. first, update to 4.1.2
then, install rashr https://m.apkpure.com/root-rashr-flash-tool/de.mkrtchyan.recoverytools but do not open it . you need to install it first because Otherwise installation will be blocked by kingroot.
then you guessed that root by kingroot https://kingroot.en.uptodown.com/android
Tutorial https://www.google.com/url?sa=t&sou...BMAF6BAgIEAE&usg=AOvVaw3cA8ZHKR3yqQaY6NvHnO4I
Then you can open rashr. download this TWRP as rashr only flashes.img files. https://www.androidfilehost.com/?fid=8889791610682894303
select RECOVERY FROM STORAGE and select the .img TWRP.
it will ask you to reboot recovery .
in recovery you wipe All in advanced wipe except microsd and USB otg. Then transfer the .zip rom to phone by dumping it into internal storage using a computer. Flash it by flash button and selecting the zip, but do not Install gapps. select Reboot and Pay attention here: Do not install TWRP app! Uncheck All prompt to install TWRP app and reboot system.
jjgvv said:
You will need modified TWRP to flash this and do not ask me why.
You need odin 3.07 as it is the last version of odin that supports S II.
Odin 3.07 https://odindownloader.com/download/odin3-v3-07
Update offically to 4.1.2, Delete All Samsung and Google accounts, go to settings and phone information, click 7 times build number(Just randomly click All numbers 7x and you will eventually done), go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Pit: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN Options tab:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
10. Flash the modified TWRP here https://androidfilehost.com/?fid=8889791610682894303 by Transferring TWRP.img to phone via USB cable≧Flash≧select image≧this image
11.Go to home and Reboot≧recovery
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
Click to expand...
Click to collapse
↑quoted from Lineage 17.1 Thread and modified
jjgvv said:
you are not carrier locked or sth?
Click to expand...
Click to collapse
Not sure. I haven't put a SIM card in this thing at all. Does having no OEM Unlock option mean that it's locked to a single carrier? I literally found this phone in the dumpster and I will be using it on wi-fi (occasionally) and offline (mostly).
Re: Kingroot
Not keen on this at all since I have read it is malware.
comfortable said:
Not sure. I haven't put a SIM card in this thing at all. Does having no OEM Unlock option mean that it's locked to a single carrier? I literally found this phone in the dumpster and I will be using it on wi-fi (occasionally) and offline (mostly).
Re: Kingroot
Not keen on this at all since I have read it is malware.
Click to expand...
Click to collapse
try other 1 click root apps then
model number is I9100 or What I mean? or I9100g? it is different
jjgvv said:
model number is I9100 or What I mean? or I9100g? it is different
Click to expand...
Click to collapse
GT-I9100. There is no G
I will try with Samsung drivers later tonight & see if the first method works. I am not keen on many of those 'easy' rooting apps, but I appreciate the help. I have big trust issues with them.
glad to see that, also one click root apps can do whatever they want like installing a malicious app without permission and hack device, though I bite the bullet and tried on my xperia c.
very reasonable doubt
Lineage is installed. However, it is still unrooted. Does anyone have any tips for getting this rooted?
=======
* I have tried the Magisk app and patching "boot.img" several times. That resulted in an error: Unsupported / invalid file, or words to that effect.
* I have tried downloading the Magisk zip file using the Magisk app. I tried flashing that freshly-downloaded Magisk zip file in TWRP. No go. Error: 1
* I have tried downloading various Magisk zip files off Github and flashing in TWRP. No go. Error: 1
* I have tried the official TWRP app that seemed to insist on downloading an official I9100 TWRP file. I flashed this TWRP file using my existing TWRP Recovery. After that, I couldn't get into Recovery at all (using the 3 finger salute). It would always just boot LineageOS instead.
=======
So I decided to start-over. I started up Odin again and started from scratch. I have spent most of the day dicking-around here. Now I am back to having LineageOS installed without root again. I tried Magisk again. No go. Same error 1. Still no root.
I can't recall a time where installing custom firmware and rooting was 100% smooth. Even when flashing in Odin all the checkboxes were greyed-out, so I couldn't even select an option if I tried. I don't know why.
Anyway, any tips to get root are greatly appreciated! SuperSU?:
comfortable said:
Lineage is installed. However, it is still unrooted. Does anyone have any tips for getting this rooted?
=======
* I have tried the Magisk app and patching "boot.img" several times. That resulted in an error: Unsupported / invalid file, or words to that effect.
* I have tried downloading the Magisk zip file using the Magisk app. I tried flashing that freshly-downloaded Magisk zip file in TWRP. No go. Error: 1
* I have tried downloading various Magisk zip files off Github and flashing in TWRP. No go. Error: 1
* I have tried the official TWRP app that seemed to insist on downloading an official I9100 TWRP file. I flashed this TWRP file using my existing TWRP Recovery. After that, I couldn't get into Recovery at all (using the 3 finger salute). It would always just boot LineageOS instead.
=======
So I decided to start-over. I started up Odin again and started from scratch. I have spent most of the day dicking-around here. Now I am back to having LineageOS installed without root again. I tried Magisk again. No go. Same error 1. Still no root.
I can't recall a time where installing custom firmware and rooting was 100% smooth. Even when flashing in Odin all the checkboxes were greyed-out, so I couldn't even select an option if I tried. I don't know why.
Anyway, any tips to get root are greatly appreciated! SuperSU?:
Click to expand...
Click to collapse
You could either try heimdall (alternativ to odin, if odin does not work for you: https://www.glassechidna.com.au/heimdall/
or even try CF-Autoroot: https://desktop.firmware.mobi/

Categories

Resources