[TWRP + ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0) (Boost Mobile) - Samsung Galaxy J7 Questions & Answers

TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737p) (Oreo 8.0)​
THIS IS A TWRP PORT THAT HAS BEEN MADE POSSIBLE BY:
@Dark98 for compiling the TWRP.img
@☆KØŁØЯΛĐØ☆ provided device files + porting TWRP
@topjohnwu for Magisk
DISCLAIMER: THIS IS NOT AN ODIN FLASHABLE TWRP. THIS IS NOT AN OFFICIAL TWRP. IT WAS BUILT USING FILES FROM R16NW.J737PVPU1ARG3. IT MAY OR MAY NOT WORK ON DEVICES WITH A DIFFERENT BOOTLOADER VERSION
You must have root access. I am currently working on making an Odin-flashable .tar for TWRP devs. Hopefully it will be available soon. Until then, root your device with Magisk. SuperSU is dead..
There is a downside & an upside to porting TWRP. The downside is that after you flash TWRP, you will lose root. The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip. It's a very delicate process & you will need to pay attention or else you will bootloop & start over. (twrp.zip posted below)
In order to flash, you need an app that will do so without booting into recovery. Flashify is the ideal choice for this procedure. View attachment com.cgollner.flashify.apk Flash TWRP in Flashify but do not reboot from the app. Power off your device & boot into TWRP manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Boot into TWRP for the first time
- Swipe to allow modifications
- Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once wipe is completed, go to TWRP home screen & Reboot > Power Off
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to restart.​First boot is to clear out the /Data partition to make room for your new recovery. Second boot is to secure it.​
Now that you have secured TWRP, go ahead & make a backup of your Boot + System + Data partitions. Keep in mind that you've lost root access so the backup will be "stock" firmware with TWRP.
------------------------------------------------------------------------------------------------------------------------------
Now to get root back
(In TWRP)
You will now flash Magisk-v18.1. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks. YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
In this order, flash:
- View attachment Magisk-v18.1(18100).zip
- View attachment no-verity-opt-encrypt-6.0.zip
- View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Now reboot device normally. If you do not flash the verity & RMM zip files in order, you will fυck your sh¡t up & have to start over.
PROOF OF TWRP PORT:
View attachment 4731317 View attachment 4731316 View attachment 4731315 View attachment 4731314
When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager. Allow Magisk to install the update, not TWRP.
Extract the twrp.img from the .zip View attachment J737P_TWRP.zip
This is for the Galaxy J7 Refine (SM-J737P) (RUNNING OREO 8.0) (J737PVPU1ARG3)

work for j737t and j737t1?

juniorgerman said:
work for j737t and j737t1?
Click to expand...
Click to collapse
Negative. As with other TWRP Recoveries, this is device specific. It could potentially work with the Sprint variant but as far as flashing it on GSM devices, that's not going to respond all too well lol

Thread posted in the incorrect section.
Dev thread is here - https://forum.xda-developers.com/galaxy-j7/development/twrp-root-galaxy-j7-refine-8-0-boost-t3916575
Please continue the discussion there.
Thread closed.
Camo.

Related

[Guide] Step by Step Installation of Android Pie Custom Roms

Step by Step Installation of/Upgrade to Android Pie Custom Roms
Following this guide, you will lose all your data if haven't backed it up yet!!
Also NO USING GSI PIE!!!
Requirements:
- Twrp is already installed.
What you need:
- LineageosTWRP (Attached to thread)
- Custom Rom (can be found here)
- Open Gapps (Pico or Nano)
Only if Root is wanted: Chose either of them
Magisk(Recommended) or SuperSU
- A brain and a body
- The Knowledge that you will wipe your phone by doing this. Be Warned.
Installation:
1. Backup all the files that you have either by copying them to a usb drive ,a micro SD or your computer.
2. Check that all files are copied successfully and can be opened or viewed.
( Some apps have a cloud synchonisation feature, use it if you have it as an option since it is really helpful!)
3. Now, get your preferred rom, gapps and if wanted, your root method ready, also unzip the twrp file aswell.
Copy them to your micro SD.
4. Boot into twrp via adb or by using some app(root needed).
In Twrp, go into wipe option, then select change file system. Change file System to ext4.
4.1 Now use Twrp Reboot-Menu Option to reboot into recovery(twrp) again.
4.2 Wipe system, data, cache and dalvik-cache partitions using the Wipe option
5. Go into Install Option and Press on "Install IMG" , select pietwrp image and flash it. (The name should be lineagerecovery.img or something if downloaded via telegram)
(If you don't have it yet and are in the Lenovo P2 Telegram group, type #pietwrp in chat and make sure to safe it to your download folder. Otherwise it's also attached to this thread.)
6. Reboot back to recovery like you did in step 4.1.
7. Now install your rom and gapps.
8. Wipe cache and then reboot .
9. Setup your phone and Enjoy.
( For Root, reboot to recovery. Flash your Root Method, wipe cache and reboot)
Enjoy and thank your Devs
FAQ
Q: Instructions unclear, phone stuck in bootloop
A: Either do this:
Download this folder and use one of the two ".bat" files. Boot into Bootloader via Volume Down and Power Button. --
It will flash S048 Firmware of our Lenovo P2, after the flash-process is finished it will boot up on its own. Recommended: Do all the ota updates via ota app.
Or: Boot into bootloader, via adb cmd prompt use: fastboot boot lineagerecovery.img , then use reboot menu to reboot into twrp. Clean Wipe phone(Wipe system,data, cache and dalvik-cache Partitions) and try flashing your Rom etc. again.
Q: Instructions unclear, hardbricked my phone!!
A: Thaat shouldn't have happened. Did you screw up somewhere?...
Luckily you backed up your most important files!

[GUIDE][OP7][9.0/10.0/11.0] Unlock Bootloader | TWRP | Root with Magisk | Update

Code:
#include <std_disclaimer.h>
/*
*
* 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 in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
This thread is dedicated to newbies and rooting, so if you're familiar with the whole procedure, you're done
Just ask questions about every step and you'll receive help!
Downloads
TWRP Installer ZIP and TWRP IMG for Android 9/10: https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
TWRP for Android 11(including instructions, thank's to @Nebrassy ): https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
TWRP Installer ZIP = For example twrp-3.4.0-10-guacamole-unified-installer-mauronofrio.zip
TWRP IMG = For example twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
Check for Pie or Q TWRP IMG! If you have Android Pie, choose Pie TWRP IMG, if you have Android Q, choose Q TWRP IMG.
The TWRP Installer ZIP works on Android Pie(9)/Q(10)
Magisk ZIP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hints
If you need to update TWRP or Magisk, always keep older versions of both in hand(Magisk canary or beta may have issues)
Remove your lockscreen protection which also removes encryption to prebvent mounting issues within TWRP
Before proceeding
Your Windows PC should already recognized your device with the USB cable
Use an USB cable provided with the phone
Make sure your Windows Explorer is set up to have file extensions enabled to avoid file name issues
This process will FORMAT/WIPE/DELETE your internal storage and every file of your phone, so please back it off your device at first!
Also keep a boot.img from your current system in place if anything went wrong so you can flash it via fastboot, see "Rooting without TWRP" for how to get it.
Rooting with TWRP (Android 9/10)​
Steps for unlocked bootloader with TWRP AND Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP installer ZIP" and "Magisk ZIP" to the phones internal storage.
5. Copy the "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP installer ZIP" from your phones storage from step 4.
13. Hit "install" and navigate to the "TWRP installer ZIP" file and select it for installation(dont boot the system now!).
14. Go back and flash "Magisk ZIP" the same way as for TWRP Zip otherwise your device will not boot!
15. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP and Magisk:highfive:
Steps for unlocked bootloader with TWRP WITHOUT Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP IMG" to the phones internal storage.
5. Copy the latest "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP IMG" from your phones storage from step 4
13. Navigate to advanced menu within TWRP, click on "Install Recovery Ramdisk" and select the "TWRP IMG". This will patch the boot image which does Magisk otherwise.
14. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP:highfive:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting without TWRP (Android 9/10/11)​
Also useful to get stock recovery and kernel --> Recovery is within boot.img on A/B devices like OP7
Refer here for unlocking the bootloader.
1. Download the payload dumper tool to your PC from here and extract it
2. Download the FULL OxygenOS Rom zip(The version your phone is running) and extract the payload.bin
3. Put payload.bin to "payload_input" folder o the extracted tool
4. Run payload_dumper.exe from the tool's folder
5. Extracted img files are in "payload_output" folder
6. Now you have your own boot.img for your Rom
7. Copy it to your phone
8. Patch the boot.img with Magisk directly on your device: Magisk Manager App -> hit install after your Magisk version -> hit "Select and Patch a file"
9. Copy the patched boot.img (it should be in the Download folder of your device named something like "magisk_patched-22100_bjjRn.img") back to your PC
10. Reboot your device to fastboot
11. Flash the patched magisk_patched-22100_bjjRn.img
Code:
fastboot flash boot_a magisk_patched-22100_bjjRn.img
fastboot flash boot_b magisk_patched-22100_bjjRn.img
12. Reboot your device. Now you have your phone rooted without the need of TWRP (Check with Magisk Manager App)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update your rooted OxygenOS (Android 9/10)​Steps for UPDATE OxygenOS via OTA and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
3. Go to Android settings -> system -> system update and hit "Download & Install Now", don't reboot yet!
4. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
5. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit "install to inactive slot"
6. Reboot your device
7. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via OTA and you keep TWRP and Root:highfive:
Steps for UPDATE OxygenOS via local upgrade and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version ->hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via local upgrade and you keep TWRP and Root:highfive:
If you have any issues, just feel free to ask!
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Kollachi said:
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Click to expand...
Click to collapse
I made it a little bit more clear, thanks, that's an common issue across several devices and requested often enough
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
AxelM said:
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
Click to expand...
Click to collapse
There's something different after unlocking the bootloader(which is the same). Twrp and magisk installation is different due to treble.
For EFS you can backup with twrp or local terminal
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=512
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Camack said:
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Click to expand...
Click to collapse
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
strongst said:
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
Click to expand...
Click to collapse
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Camack said:
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Click to expand...
Click to collapse
You need to do all steps. I recommend to flash the custom kernel when you've sucessfully booted the device at first.
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
murti52 said:
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
Click to expand...
Click to collapse
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
strongst said:
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
murti52 said:
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
Click to expand...
Click to collapse
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
strongst said:
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
Click to expand...
Click to collapse
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
murti52 said:
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
Click to expand...
Click to collapse
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
strongst said:
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
murti52 said:
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
Click to expand...
Click to collapse
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
strongst said:
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
Click to expand...
Click to collapse
Then there must be some issue with my flashing sequence. Btw, The service centre repaired the issue and i have rooted it and using bluespark with stock rom. I'll give the zip another try later on when a new update comes. Thanks for the help
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Jacckz said:
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Click to expand...
Click to collapse
A good and quick overview and comparison with oneplus 7 pro https://sparrowsnews.com/2019/08/13/difference-between-f2fs-and-ext4-file-system/

[Guide][Root Magisk Only][OTA Compatible] Moto G6 Play

* Warranty is void
* I'm not responsible for any damage to your phone in mistaking anything specified here
* This guide requires intermediate knowledge
I'm posting this guide because I haven't found any special thread about it, and had to search multiple threads and websites to get a conclusion in how to root Magisk only (without flashing TWRP or any other custom recovery). Focused in not decrypting the phone, or modify any system partition for a full OTA compatibility.
Requirements:
* ADB/Fastboot & Motorola USB drivers installed - (PC)
* Unlocked bootloader - (Phone)
* Stock rom - (Phone)
* Magisk Manager (latest stable version installed on your phone)
* TWRP (compatible to the Moto G6 Play model) - please refer to this thread for more details. ***(Of course, you won't flash it!)
*** PLEASE! REFER TO THE UPDATES BELOW!!! ***
Tutorial:
1. Reboot to bootloader
2. Boot into downloaded TWRP using Fastboot code:
Code:
fastboot boot twrp_downloaded.img
(on TWRP ignore any password by canceling)
3. Backup stock boot image using:
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
4. Reboot system using ADB code:
Code:
adb reboot system
5. After rebooted, copy backed up stockboot.img to the phone internal memory
6. Install and open Magisk Manager, click [Instal] > [Install] > [Select and Patch a File] and select stockboot.img on internal memory.
7. After boot image patched, copy magisk_patched.img from phone Download folder to PC
8. Reboot to bootloader and flash magisk_patched.img to phone using Fastboot code:
Code:
fastboot flash boot magisk_patched.img
9. After done, reboot system using fastboot code:
Code:
fastboot reboot
10. All done! Open Magisk Manager and check root! For future OTA updates already rooted with Magisk, I recommend this post: https:// www. the custom droid .com/install-ota-update-rooted-android-device-guide/ - (remove spaces )
[UPDATE 1]
I've noticed that Moto G6 simply forces reboot system before update the device, if we go to restore images in Magisk to try it out tutorial post from 10., it'll simply be removed after that.
Even doing so and going ahead to update the device losing Magisk, and still have to back up once more the new updated boot image and patch it on Magisk following my guide above, I got a bootloop patching the newest OTA with Magisk 20.0 (latest).
After almost losing indefinitely root access, I got it done, downgrading Magisk to 19.3.
For doing so, download Magisk 19.3 zip file from GitHub repository and copy it to the SD Card, boot up into TWRP using fastboot (without flashing) then proceed as read-only, after that, install Magisk 19.3 zip file to patch the OTA updated boot image, then it's done. Root it's working properly without updating Magisk.
I don't know exactly why the latest Magisk it is breaking the OTA updated boot image... Whatever, it's a good approach to get root access back after the recent OTA!
I still need to check if this workaround will be working on new OTA's. That's it.
[UPDATE 2]
After recent update - January 2020, my rooting workaround supporting OTA is working properly as followed solution on UPDATE 1, above.
I didn't test using latest Magisk 20.3 apk due the bootloop when patching boot image in Magisk 20. Don't know if that bug has been fixed...
Updating Magisk after successfully rooted using solution above will not result in a bootloop, but I do recommend downgrade Magisk when new OTA is released.
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
gabardal said:
Hello, thank you for this guide. I'm having trouble with the last step, as I also am having a bootloop with the boot image patched with the latest Magisk. Would you care to elaborate on how do I install Magisk 19.3? Since I boot TWRP, but cant find the Downloads folder from the phone, where I put the Magisk-v19.3.zip file. Cheers!
Click to expand...
Click to collapse
First, if you have the actual boot backup, you'll need to flash it to fix bootloop.
Remember to boot into TWRP (without flashing) to flash it.
* Follow the samples above for the codes if necessary.
After fixing bootloop all you'll need to do is download the Magisk-v19.3.zip from “Magisk GitHub releases” and place it on the external sd card.
Then boot into TWRP (always without flashing) and flash the zip file using TWRP. (Remember to flash to boot image).
It'll simply patch your boot, after that, reboot, if successfully booted go check Magisk.

Modified OP6, wasn't sure what I changed. Found a txt file with the answer- Bootloader, TWRP Blue_spark, Magisk. They reset, so very uncertain here.

Okay, so as above. I modified my OnePlus 6 in summer 2019 when I bought it, and kept Lineage OS (unsure what version if it matters); I modified the bootloader, installed TWRP Blue_Spark for recovery and rooted using magisk. I made a nandroid backup but it was on the sd card partition and I've at some point wiped it.
Again, no custom rom. I only know because I thankfully made a text file explaining what I did. I used this thread.
OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!
OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !! Before you start, OTA up to the latest System Update available. Settings > System Updates > Download & Install the latest available Thank You all for your...
forum.xda-developers.com
If you click the text file copied into the spoiler you can see pretty much exactly what I did, if you want:
Spoiler: Click here to see text document, including links to XDA threads, about what I did.
Models: A6000 (Asian model which I have), A6003 (which is for EU, where I live).
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device!
If you want to use partial OTAs, you must first flash a full OTA that it applies to
and then flash the partial OTA from stock recovery.
Flashing partial OTAs from TWRP will either fail or soft brick your device.
You can return to a usable state by flashing full zips in recovery.
OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !!
OnePlus 6: Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup !! Before you start, OTA up to the latest System Update available. Settings > System Updates > Download & Install the latest available Thank You all for your...
forum.xda-developers.com
Used this guide to:
1. unlock OnePlus 6 Bootloader
2. flash TWRP as a custom recovery (I used Blu_Spark TWRP as it had better backup options)
3. Magisk root (unrooter)
If you need to run CMD from a directory then check file:
How to open CMD command window in specific directory -Noted.txt
The versions of TWRP Blu_Spark I used were:
twrp-3.2.3-x_blu_spark_v9.91_op6.img
twrp-3.2.3-x_blu_spark_v9.91_op6.zip
Always make sure you use latest version, but make sure you're updated to the latest oxygenOS
NANDROID Backup (from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643):
Create:
1. Boot into TWRP Recovery .
2. Go to Backup Menu and select all the listed partitions.
3. Name the Backup if needed (Optional)
4. Swipe to take Backup.
This proces should take 5 to 7 minutes depending upon the size of data.
5. Reboot System when done.
Your Nandroid will be stored in the Backup Folder inside TWRP Folder /sdcard/TWRP/BACKUPS
NANDROID RESTORE:
1. Boot into TWRP Recovery
2. Go to Restore Menu and select the backup you want to restore.
3. Select the partitions you want to restore.
4. Swipe to Restore. The process will take 5 to 7 minutes.
5. Reboot system once done
Found this, not sure if its relevant to OTA updates deleting twrp (blu_spark version, FTR)
Just to add a note to you for next ota.
After ota is installed go to magisk manager
Press download
Search for twrp a/b
Install (don't reboot)
Now go to main screen and press install
Choose to inactive slot (after ota)
This way you keep both twrp and root
My problems (potentially): I was getting OTA lineage updates and people said they were actually fine with this and wouldn't cause a problem, and they certainly seemed to be fine for a time.
However, at some point over two years my recovery has been reverted to presumably stock recovery and TWRP is missing. I'm not 100% sure how this happened but I'm assuming it was when I installed Android 10 OTA, or potentially did some kind of reset. I'm now unsure if I can simply install TWRP without some kind of problem.
Any Insite into what likely caused that and if it could be problematic would be appreciated. It's definitely gone. I didn't install to both A/B.
My root also stopped working as I can remember substratum themes breaking permanantely after an update, but they just became disabled and substratum remained benign and installed. I'm assuming this was with the Android 10 update, or when I lost TWRP (?) - but I'm not sure how I installed Magisk as I don't mention in the instructions file I found in the spoiler. According to the thread:
Gaining Root Access
You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries or by Flashing Magisk Zip for a system less root. A custom recovery is necessary to do this.
Click to expand...
Click to collapse
My bootloader remains unlocked and I have USB debugging enabled.
TLDR: I was just wondering whether my Android version 10.3.10, the fact my TWRP recovery has been reset, my magisk root is gone and I'm not sure if it persists, means that I might encounter problems installing TWRP, Magisk and custom ROMS.
Will they be persistent and problematic somewhere or are they gone?
Should I unlock my bootloader again when request, or skip that step. Would it matter?
Also any reccomendations on a decent custom ROM for the OnePlus 6? I'm ideally looking for security/privacy and to move away from google as much as possible. I've always flashed ROMS and loved LineageOS, or moreso, CyanogenMod on Nugget iirc was the peak for me, but I never bothered on this phone for some reason.
I'm sick of feeling my data is being stolen, whether that be anaytics, physically, etc etc. It seems like it's being pepetually eroded further and further and I want to feel my phone is free and cool like I used to.

Tutorial : Root Galaxy S10 Series Android 12 One UI 4.1 Stock Firmware

Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk ​Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 - UI 4.1 Latest Version (I tested G970FXXSGHWC2) ​(Without combination keys for active Magisk after normal restart – Without press power key for warning massage booting) ​
How to root:
1. Extract your downloaded Rom and patch AP file with magisk (Recovery Mod)
2. Go to download mode.
3. Uncheck auto reboot in Odin.
4. Flash your patched AP file with BL CP CSC.
5. When flash passed, again we should go to download mode.
6. Hold volume down and power key, and after vibration release power key and hold Bixby key and volume down for going to download mod again.
7. Reset Odin and again uncheck auto reboot, put twrp recovery,
To AP and flash, it.
8. When passed, we need again reset and go to twrp recovery, volume down power key, after vibration release volume down and hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release.
9. We should be in twrp recovery mod, format data, rename magisk.apk to magisk.zip, copy magisk.zip, kernel, multi disabler and twrp boot logo to the sd card.
10. Mount your sd card and install first magsik.zip, then multi disabler, twrp boot logo and finally kernel.zip
11. Restart to system.
12. After booting to android 12 open the magisk app and let download the latest version.
13. When download finished open magisk, you will see one massage for install complete magisk after reboot in 5 seconds, cancel it and go to setting and active Zygisk and Magisk Hide, rename it.
14. When magisk hide process finished. Open again magisk, you will see the reboot massage again.
15. Tap ok and wait for rebooting.
Fix Internal Storage Size:
First Format Data.
If it doesn't work :
Boot into TWRP recovery.​
Select Wipe » Advanced Wipe.​
Tick/check the Data partition.​
Select Repair or Change File System button.​
And lastly, select Resize File System button. (Let TWRP resize your file system. It might take some time, have patience)​
After reboot, your galaxy is rooted without any problem. And you can install modules zips. And enjoy your root same stock Rom without any opened bootloader warning massage first of booting android. And without press power key after that.
---------------------------------------------------------------------------------------------------------
UPDATED (G970FXXSGHWC2) Android 12 - One UI 4.1 - March 2023​​For update your android without losing data, follow these steps:​1. Download: One of Kernels - Multidisabler Samsung 3.5 - TWRP Bootlogo Patch - Magisk - Odin 3.14.1-3B Patched.
2. In Odin uncheck Auto reboot, flash (BL - Patched AP File with Magisk - CP - Home CSC).
3. Reboot manual to download mode again, Flash TWRP Recovery in AP slot.
4. Reboot to TWRP recovery, flash Magisk.zip, Kernel and Multidisabler then TWRP Bootlogo.
5. Reboot to system and finished.
Download the latest Firmware version for your galaxy here: https://samfirms.com
Download the latest TWRP recovery version for your galaxy here: https://twrp.me/Devices/Samsung/​Download the latest Magisk version for your galaxy here: https://github.com/topjohnwu/Magisk/releases​
Special Thanks to Ambasadii Dev. And CruelKernel Develop Team For Kernels. Magisk Dev. TeamWin For TWRP Recovery And Odin3 Patched.​
Happy to see your post!
I have Android 11 FUL1, with Magisk 23000 (last versioin with Magisk Hide and Modules) and last Official Twrp and I want to pass to Android 12.
So my question:
May I patch android 12 AP file G970FOXMEGVA4 and patch also twrp but under Android 11 and Magisk 23000?
My aim is to maintain the Twrp already present and to avoid to install stock Android 12 only to patch AP file and twrp.
Then I should start immediately with Odin, AP patched, twrp patched, multidisabler, kernel and all the orther things.
Is this possible?
And just for info, your kernel is the same as Ambasadii rom?
will try but, what to do with Downloaded Kernel?
Hello everybody, thans for the work.
I tried your method but it's not working for me.
All is good until step 7.
At Step 8, the phone restarts good on TWRP but a script is executing and the phone restarts.
On this restart, i do like you explain (hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release) but the phone don't restarts in TWRP and the phone vibrate instead, then the phone is freeze on SAMSUNG logo
EDIT : A resolved it by flashing the CSC file instead of the CSC HOME file.
is.Mehrdad said:
Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk
Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 Latest Version (I tested G970FOXMEGVA4)
(Without combination keys for active Magisk after normal restart – Without press power key for warning massage booting)
Sorry For Bad ENGLISH
https://1drv.ms/w/s!AiUnkR9HkhduiqRfflrkvHqg5Ai_lQ?e=fIGiFi​
Downloads:
1. Download the latest stock ROM for your galaxy here: https://samfirms.com
2. Magist the Latest Version 24.0: https://bit.ly/3rYnEzQ
3. Kernel: https://bit.ly/3o55bR1
4. TWRP Recovery, The Latest Version: https://bit.ly/3ADTk1F
5. MultiDisabler: https://bit.ly/3r693mY
6. TWRP Boot logo: https://bit.ly/33TNrRT
7. Odin 3.14.4: https://bit.ly/3o67YcG
How to root:
1. Extract your downloaded Rom and patch AP file with magisk (Recovery Mod)
2. Go to download mode.
3. Uncheck auto reboot in Odin.
4. Flash your patched AP file with BL CP CSC.
5. When flash passed, again we should go to download mod.
6. Hold volume down and power key, and after vibration release power key and hold Bixby key and volume down for going to download mod again.
7. Reset Odin and again uncheck auto reboot, put twrp recovery,
To AP and flash, it.
8. When passed, we need again reset and go to twrp recovery, volume down power key, after vibration release volume down and hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release.
9. We should be in twrp recovery mod, wipe data, rename magisk.apk to magisk.zip, copy magisk.zip, kernel, multi disabler and twrp boot logo to the sd card.
10. Mount your sd card and install first magsik.zip, then multi disabler, twrp boot logo and finally kernel.zip
11. Restart to system.
12. After booting to android 12 open the magisk app and let download the latest version.
13. When download finished open magisk, you will see one massage for install complete magisk after reboot in 5 seconds, cancel it and go to setting and active Zygisk and Magisk Hide, rename magisk to “manage” (without R).
14. When magisk hide process finished. Open again magisk, you will see the reboot massage again.
15. Tap ok and wait for rebooting.
After reboot, your galaxy is rooted without any problem. And you can install modules zips. And enjoy your root same stock Rom without any opened bootloader warnning massage first of booting android. And without press power key after that. ​
Click to expand...
Click to collapse
Fantastic instructions! Worked like a charm....except that my internal storage has gone from 128gb, to 32gb.
How can this be resolved?
I notice that the instructions did not include flashing vbmeta. Could this be problem?
BlaqqSL8 said:
Fantastic instructions! Worked like a charm....except that my internal storage has gone from 128gb, to 32gb.
How can this be resolved?
I notice that the instructions did not include flashing vbmeta. Could this be problem?
Click to expand...
Click to collapse
After step 8 you are in TWRP Recovery, You must “Format Data” in TWRP then again boot your device to TWRP recovery. After Wipe data, vbmeta and your storage will be fixed.​
Be careful, After Wipe Data don't boot in OS, because you must pass other steps before boot to OS.​
bruram said:
Happy to see your post!
I have Android 11 FUL1, with Magisk 23000 (last versioin with Magisk Hide and Modules) and last Official Twrp and I want to pass to Android 12.
So my question:
May I patch android 12 AP file G970FOXMEGVA4 and patch also twrp but under Android 11 and Magisk 23000?
My aim is to maintain the Twrp already present and to avoid to install stock Android 12 only to patch AP file and twrp.
Then I should start immediately with Odin, AP patched, twrp patched, multidisabler, kernel and all the orther things.
Is this possible?
And just for info, your kernel is the same as Ambasadii rom?
Click to expand...
Click to collapse
No, not working, you should install multidisabler and other files in twrp recovery.
Kernel is same
DelNero said:
Hello everybody, thans for the work.
I tried your method but it's not working for me.
All is good until step 7.
At Step 8, the phone restarts good on TWRP but a script is executing and the phone restarts.
On this restart, i do like you explain (hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release) but the phone don't restarts in TWRP and the phone vibrate instead, then the phone is freeze on SAMSUNG logo
EDIT : A resolved it by flashing the CSC file instead of the CSC HOME file.
Click to expand...
Click to collapse
Happy for resolved problem.
But I wrote in step 4 CSC File, Not CSC Home.
4. Flash your patched AP file with BL CP CSC.
is.Mehrdad said:
After step 8 you are in TWRP Recovery, You must “Wipe Data” in TWRP then again boot your device to TWRP recovery. After Wipe data, vbmeta and your storage will be fixed.​
Be careful, After Wipe Data don't boot in OS, because you must pass other steps before boot to OS.​
Click to expand...
Click to collapse
Thanks for the quick reply.
Just one more thing: Can I flash vbmeta in the CP slot, at the same time as flashing TWRP in the AP slot? Or do I have to flash them individually?
BlaqqSL8 said:
Thanks for the quick reply.
Just one more thing: Can I flash vbmeta in the CP slot, at the same time as flashing TWRP in the AP slot? Or do I have to flash them individually?
Click to expand...
Click to collapse
I don't think so
What is exactly the problem with vbmeta ?
is.Mehrdad said:
I don't think so
What is exactly the problem with vbmeta ?
Click to expand...
Click to collapse
There's no problem with vbmeta that I know of. It's just that, following your instructions, I still only have 32gb of internal storage instead of 128gb.
It would really help if you could update your instructions to include flashing the vbmeta file either via Odin, or using vbmeta.img in TWRP.
BlaqqSL8 said:
There's no problem with vbmeta that I know of. It's just that, following your instructions, I still only have 32gb of internal storage instead of 128gb.
It would really help if you could update your instructions to include flashing the vbmeta file either via Odin, or using vbmeta.img in TWRP.
Click to expand...
Click to collapse
Test this, if not working, I will test again all of my files.
After flash your patched AP, Boot to TWRP and mount all of your partitions, then restart again to twrp recovery and then do Wipe Data and again reboot to recovery for flash other files.
Boot into TWRP recovery.​
Select Wipe » Advanced Wipe.​
Tick/check the Data partition.​
Select Repair or Change File System button.​
And lastly, select Resize File System button. (Let TWRP resize your file system. It might take some time, have patience)​
is.Mehrdad said:
Test this, if not working, I will test again all of my files.
After flash your patched AP, Boot to TWRP and mount all of your partitions, then restart again to twrp recovery and then do Wipe Data and again reboot to recovery for flash other files.
Boot into TWRP recovery.​
Select Wipe » Advanced Wipe.​
Tick/check the Data partition.​
Select Repair or Change File System button.​
And lastly, select Resize File System button. (Let TWRP resize your file system. It might take some time, have patience)​
Click to expand...
Click to collapse
From reading many posts\instructions on how to install\root A12, I think that, where you say "WIPE DATA", It should be FORMAT DATA - YES.
I'm going to try it that way, and will let you know ow it goes.
BlaqqSL8 said:
From reading many posts\instructions on how to install\root A12, I think that, where you say "WIPE DATA", It should be FORMAT DATA - YES.
I'm going to try it that way, and will let you know ow it goes.
Click to expand...
Click to collapse
Thanks, I edited my post to Format Data.
So I followed all the steps. I did everything and everything worked as it should. However, when I get to magisk wanting to update, it does so, patches everything successfully but on restart, I get a bootloop.
Hello. Does anybody try to do it on USA Snapdragon model?
How do we install magisk with ap file?
patched ap file I did as you said but it won't load. It gets stuck loading system.img.
VenfefulRat said:
So I followed all the steps. I did everything and everything worked as it should. However, when I get to magisk wanting to update, it does so, patches everything successfully but on restart, I get a bootloop.
Click to expand...
Click to collapse
Same thing here....
Impossibile to update magisk
Gamras606 said:
patched ap file I did as you said but it won't load. It gets stuck loading system.img.
Click to expand...
Click to collapse
Uninstall Samsung drivers and install it again, reboot your pc and check it again with another USB port.

Categories

Resources