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
Related
Unofficial TWRP 3.1.0-0 Moto G5 (cedric)
Latest TWRP changelog :
New features of 3.1.1-0 (adb backup, tweaked MTP startup routines and plenty of bug fixes - for full changelog)
Download Link
twrp-3.1.1-0-cedric.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
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 SuperSU or flash any of the verity disabler zips there in 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
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.1.1-0 Moto G5, Tool/Utility for the Moto G5
Contributors
Santhosh M
Source Code: http://Using prebuilt stock kernel and hence no kernel source available
Version Information
Status: Stable
Stable Release Date: 2017-10-05
Created 2017-03-17
Last Updated 2017-10-05
Reserved
Reserved
Even though I have the plus variant, it's cool to see these features popping up.
Johny Cipeli said:
Even though I have the plus variant, it's cool to see these features popping up.
Click to expand...
Click to collapse
+1
Grt @Santhosh M
Santhosh M said:
Reserved
Click to expand...
Click to collapse
Gonna get that g5+ Bro? it would be awesome if you will be there for support too.
xt1670 model
Hi Santhosh
Will this TWRP work on Moto G5 model xt1670?
If so, can it be rooted using twrp temporary boot?
EDIT: I have tried this several time, I'm always getting stuck at boot, after the first data wipe, only solution is to install stock system again.
I have the Modem Version: M8937_8000.122.02.40R, 32GB
I'm offering to test
Thanks
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
KawaiiNeko said:
Works fine for the most part, though reboot options Bootloader and Power Off doesn't work, just restarts normally.
XT1676
Click to expand...
Click to collapse
Plz share the procedure you had followed.
Did you able to achieve root access?
fAIyaZ said:
Plz share the procedure you had followed.
Did you able to achieve root access?
Click to expand...
Click to collapse
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
KawaiiNeko said:
Unlocked bootloader, flashed twrp, factory reset, good to go. Sadly no root though.
Click to expand...
Click to collapse
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
fAIyaZ said:
Try phh su.
Flash it through twrp: https://superuser.phh.me/superuser.zip
Then installed the phh superuser app: https://play.google.com/store/apps/d....phh.superuser
Click to expand...
Click to collapse
worked perfectly! https://i.imgur.com/71G0cN2.png
I'll get my G5 16gb lunar grey tomorrow and can't wait to root
Thanks for testing out
Bootlooping
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
linsspinho said:
Hi guys, I got bootloop in my moto g5 after TWRP boot/install, should I open a new thread or somebody can help here?
Click to expand...
Click to collapse
Depending on your phone version, you might need to flash system using fastboot.
KawaiiNeko said:
worked perfectly! https://i.imgur.com/71G0cN2.png
Click to expand...
Click to collapse
So i believe TWRP works as intended and root is also achieved via phh/whatever?
If all works fine for you would like you to make reply in the thread with detailed flashing instructions as i am not sure why few in thread have issues
can this version of twrp be used for POTTER version of moto G5 plus?
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
.sirhc said:
After installing TWRP my Phone stucks at the "Your device has been unlocked" screen. My system seems to be gone. I've downloaded the image from the other thread and tried to sideload it, but twrp says it's in the wrong format. TWRP boots fine
(Anyone who can upload a fully working NANDROID or sth like that?)
What can i do :/?
Edit: Solved. Unzipped the firmware and flashed manually via fastboot. Working fine!
But then again at the startup of the recovery, there's the encryption message. What to wipe now, that it'll work? Wiping /data ends in boot loop...
Click to expand...
Click to collapse
Did you tried wiping data, and formatting data? Remember that wiping /data is where your apps and settings are stored, and formatting /data/media is the massive storage... Maybe if you wipe both it would work
Enviado desde mi Moto G (5) Plus mediante Tapatalk
After
fastboot flash recovery twrp.img
I'm booting into recovery, cancel the encryption password verification, swipe to allow modification, wipe & format data -> Bootloop
Flashing system (and only system, not recovery etc) -> Phone boots normally, twrp ist gone ...
Greetings
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.
Here is the last Update B356 for Honor Note 8 Android 7 Emui 5.0.1
Full Stock Rom
Boot_Insecure_B356_Fix-adb_dm-verity.img v3 (Spezial Thanks to franzroy from the Mate 8 Forum)
Rooted with Magisk
Busybox
Adblock (is Disable by Default,turn it on yourself if you want)
Integrated Google Apps (Playstore,Play Service,Gmail,Google, Contacts and Calender Sync....
Download
Requirement:
Bootloader Unlocked
Twrp installed
How to install:
Boot into Twrp (I use 3.1.1-1 Open Kirin Twrp)
Format Data with yes
Wipe all in advanced Wipe System,Data,Internal Memory,Dalvik Cache and Cache.
Install the Rom,enjoy
For People was not working Root (Magisk) download the File from Attachment and flash in Recovery (TWRP)
I do not accept responsibility for Bricked Devices,or any other damage!
Everyone needs to know what he is doing!
Link mirror error.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Now works!!!
Great.
karolingio said:
Link mirror error.
---------- Post added at 09:18 PM ---------- Previous post was at 09:17 PM ----------
Now works!!!
Great.
Click to expand...
Click to collapse
Ok,thanks
Can we install over B353?
Magisk
letschky said:
Ok,thanks
Click to expand...
Click to collapse
Hello,
I install your custom rom and works very well but it is no rooted as default as written in your first post
How can I root it with Magisk ( Magisk manager is already installed )
I saw also that in your zip file(b356) the boot.img as the same size as "boot_insecure_b356...", so I didn't flash it
Am I right ?
Thanks for your help
AD
zorglubzorglub said:
Hello,
I install your custom rom and works very well but it is no rooted as default as written in your first post
How can I root it with Magisk ( Magisk manager is already installed )
I saw also that in your zip file(b356) the boot.img as the same size as "boot_insecure_b356...", so I didn't flash it
Am I right ?
Thanks for your help
AD
Click to expand...
Click to collapse
aha,for me works root with Magisk.
ok you can extract the Rom and in Magisk folder is the Magisk.zip inside.
Copy the Magisk.zip on your SD Card and flash via twrp,i think this fix the issue
coco1476 said:
Can we install over B353?
Click to expand...
Click to collapse
i don´t know,install fresh,fresh install is better,but make a Nandroid Backup and flash the 356 over 353
letschky said:
aha,for me works root with Magisk.
ok you can extract the Rom and in Magisk folder is the Magisk.zip inside.
Copy the Magisk.zip on your SD Card and flash via twrp,i think this fix the issue
Click to expand...
Click to collapse
Hello Letschky,
I use TWRP 3.1.1-1
I tried to install magisk from your custom rom but failed : " boot image patched by othe program, please restore stock boot image" and update process ended with ERROR: 1
The boot image is the one from your custom rom
Could you help me
Best Regards
Alain
zorglubzorglub said:
Hello Letschky,
I use TWRP 3.1.1-1
I tried to install magisk from your custom rom but failed : " boot image patched by othe program, please restore stock boot image" and update process ended with ERROR: 1
The boot image is the one from your custom rom
Could you help me
Best Regards
Alain
Click to expand...
Click to collapse
Before you have the rom installed, you have everything wiped?
Wipe Data with - yes
System,Cache,Dalvik Cache,Data
Reboot again into Recovery
install the rom
for me works without any Problem
letschky said:
Before you have the rom installed, you have everything wiped?
Wipe Data with - yes
System,Cache,Dalvik Cache,Data
Reboot again into Recovery
install the rom
for me works without any Problem
Click to expand...
Click to collapse
****************
Yes I wiped everything the only difference is that I didn't reboot after the WIPE and the INSTALLATION of the ROM
will do it again tonite
Cheers
letschky said:
Before you have the rom installed, you have everything wiped?
Wipe Data with - yes
System,Cache,Dalvik Cache,Data
Reboot again into Recovery
install the rom
for me works without any Problem
Click to expand...
Click to collapse
I did exactly the same as you but without rebooting between all the wipes and the installation of the ROM
Now I did exactly the same as you and I have the same problem : not rooted
during the installation of the rom I saw just after the message "install boot.img" failed to mount /data file exists and and at the end of the installtion "script succeeded result [ E: unknown command [1]]
boot is unlocked
zorglubzorglub said:
I did exactly the same as you but without rebooting between all the wipes and the installation of the ROM
Now I did exactly the same as you and I have the same problem : not rooted
during the installation of the rom I saw just after the message "install boot.img" failed to mount /data file exists and and at the end of the installtion "script succeeded result [ E: unknown command [1]]
boot is unlocked
Click to expand...
Click to collapse
Same for me, but my solution was simple:
1 installed ROM
2 flashed SU via twrp !
That's all folks!
This worked for me.
karolingio said:
Same for me, but my solution was simple:
1 installed ROM
2 flashed SU via twrp !
That's all folks!
This worked for me.
Click to expand...
Click to collapse
Yes I did the same and it works but I wish to test MAGISK but no success
Thanks
zorglubzorglub said:
I did exactly the same as you but without rebooting between all the wipes and the installation of the ROM
Now I did exactly the same as you and I have the same problem : not rooted
during the installation of the rom I saw just after the message "install boot.img" failed to mount /data file exists and and at the end of the installtion "script succeeded result [ E: unknown command [1]]
boot is unlocked
Click to expand...
Click to collapse
the error messages do not matter
but strangely it has just flashed again and it works without problems,
but when it works with supersu also works well
ectract the boot img from tje rom and flash with adb or in twrp and flash the MAGISK.zip again if you want to have MAGISK
Good Afternoon
Loaded B356 last night and for me it works better than the B353 version, seems a lot smoother and I'm loving the magazine covers on my lock screen
Can't get Magisk to work but that does not matter as the phone rooted anyway
I'll carry on road testing and will report back with any issues
Keep up the good work letschky
Hello Letschky.
I've flashed this ROM via TWRP over 356 OTA (it was not completely rooted, it was not possible to mount the /data in TWRP). Wipe and flashing process were successful, but now the reboot to system does not work. The screen is black. ADB can find the device, but it says that the the device is in recovery mode.
Can You please help me.
vimmr said:
Hello Letschky.
I've flashed this ROM via TWRP over 356 OTA (it was not completely rooted, it was not possible to mount the /data in TWRP). Wipe and flashing process were successful, but now the reboot to system does not work. The screen is black. ADB can find the device, but it says that the the device is in recovery mode.
Can You please help me.
Click to expand...
Click to collapse
I advise you to factory reset and reflash the zip that letschky has uploaded
Thats what I did and to be honest its working flawlessly for me, I was previously on B353
On an unrelated side note, can anyone advise if the substratum theme engine works with this ROM
Thanks in advance
Thanks Letschky! I loaded your B356 rom to my honor note 8 last night, looks great.
One issue, the google apps are there, but there is no way to sync the Contacts for Calendar? The option is not there under settings, accounts, google. The option is there for sync app data, sync gmail, sync googlefit, sync people details. But no option for Contacts or Calendar? When I open the phone dialer, there are no contacts!
I loaded the Contacts app from play store, and when I go to add my account it says "the account is already loaded" but still no contacts.
Thanks!
UPDATE: I found this file https://www.apkmirror.com/apk/googl...cts-sync-7-1-2-android-apk-download/download/ and installed it to the phone and now the contacts are appearing in the dialer, but the option to sync contacts is still not appearing in settings, accounts, google.
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
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.