Related
Hi, I found a way to fix this bootloop which happens after you flash the latest ota update if you have unlocked and rooted your stock rom.
I own a HTC E8 China Unicom [M8Sw - dual sim], but I think it will work on other variants.
It is the SU binary/files which are preventing the phone from updating correctly.
You can also restore a clean unrooted TWRP backup and do the OTA update.. it will work just fine.
This tutorial is for those who don't want to lose their app data and modifications.
To be able to update... you need to fully unroot the phone before. Well, this was previously not possible due to system write protection.
(There are also other methods of unrooting. (deleting the SU files manually with the file manager of TWRP recovery) This doesn't work, I have tried it myself..often cause bootloops.)
But now we have a custom recovery mod which enables us to write to the system partition and thus can fully unroot with SuperSU app itself.
Requirements:
-some expertise with adb/flashing/twrp recovery management will be needed.
-stock firmware.zip, inside the OTA zip file, where you will find you stock recovery,boot image, etc
-Stock ROM, rooted with no modified existing system files
-TWRP Recovery from @Captain_Throwback works fine. I used the 2.8.6.0 one. http://forum.xda-developers.com/one-e8/orig-development/recovery-twrp-touch-recovery-t3060188
-untouched Stock Kernel Modules (IMPORTANT)
-SchKernel Extra 3.3, to gain write permission to /system http://forum.xda-developers.com/one-e8/general/schkernel-extra-3-3-t3200090
[UPDATE: SchKernel Extra has been updated to 3.5 and the old one is not available for download on the other thread. You can find attached at the bottom of this section ver3.3 which I had used. Please don't use ver3.5 as a user has reported having bootloop with that.)
-Battery +80 charge recommended...the process gonna demand a lot of power.
-Patience... loads of it....
Disclaimer: I am not responsible if you brick or damage you phone!!
Before you flash anything, be sure to have a working twrp full backup of you phone! In case anything goes wrong.
STEPS:
1. Copy the untouched kernel 'modules' folder [found in system/lib/ in your phone] to another location ( for e.g. to your internal phone memory), you're gonna need it later.
2. Flash the twrp recovery if you haven't already and boot into TWRP recovery.
3. flash SchKernel Extra 3.3 kernel mod. It will launch the aroma installer. There will be options as overclocking/underclocking etc..
I left everything on STOCK option, disabled Swipe2sleep, unselected the everything in the optional addition page. Then went to install it.
4. Reboot, and open SuperSU app, go into setting, tap the FULL UNROOT option, this might take a while. The first time, when the unrooting notice shows and it seems that the app is not doing anything, you might be required to exit the app by pressing home button. Then open the app again and redo FULL UNROOT option. If you exit the app and when re-opening it, the "unrooting notice" is still there, then it means it is working. This might take a bit of trial and error.
5. Ultimately, SuperSU app will close. Then you will need to reboot. You will see that SuperSU is gone and that you have no root access.
6. Now, turn it off again to go to fastboot. Connect to PC and flash the stock boot.img via adb to restore the stock kernel.
8. Then, in twrp recovery, mount /system partition and got to advanced >> file manager..
9. Now browse to /system/lib/ and delete the 'modules folder'.
This is because the SchKernel Extra 3.3 kernel mod flashed previously has modified your kernel modules and when you will try to update the OTA, the stock recovery will report that the kernel modules (xxxxx.ko) has be modified and it will stop the OTA update process.
10. Remember the previous untouched stock 'modules' folder you copied previously, now move it to /system/lib/HERE , to replace the deleted folder.
[DO STEP 9 BEFORE - Don't try to overwrite the folder, it won't be possible. It said operation failed for me. ]
Optional: You might also want to delete su.d folder in \system and init.d folder in system\etc
these files were for the custom kernel and won't be needed anymore.
11. Reboot into fastboot mode, connect to PC (if not already), flash stock recovery.
12. Now, you're good to flash the OTA updates. :good:
-Download it, if not already done.
If ever you have downloaded from PC and copied it to phone, and for whatever reason the phone is not detecting the zip file and asking for install.
Just move it to you exeternal SD card and rename it to "ptt.zip" , go into stock recovery and go down the list to "apply update from SD card"
and it should flash the zip file. When done, select the reboot option and it will say reboot to flash firmware.zip and the will boot. :fingers-crossed:
When booting it will take some time (3 to 8 mins), and then go to the "Android is updating - optimizing apps" screen. This might take a lot of time if you have a lot of apps installed. The phone might get really hot during this process.
When the OS finally boot completely there will be an "HTC" screen and an exclamatin mark in the notification bar. NO WORRIES, it is the just the update working. It will go away when the update is fully processed.
After OTA update is done, you can make a twrp backup of the unrooted system, so that you can restore it for future OTA updates.
If some steps are confusing, feel free to ask for any clarification
Hope I helped you. Don't forget to hit thanks
problem
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?
neekless said:
hi after i flashed SchKernel Extra 3.3 my phone just turned off and won't turn on. what should i do?
Click to expand...
Click to collapse
how did you flash it exactly?
Did you flash it thought TWRP recovery?
also...what variant of HTC e8 are you using?
Thank you for this guide. :good:
For the newbies, here are exact instructions for each step. TWRP is required; presumably you have this because you've rooted your phone. (If you haven't rooted your phone, what are you doing here?)
Note that rebooting to TWRP can be accomplished in several ways:
Long-press the power button; when prompted choose Reboot. When the screen goes black, press and hold the Volume Down key. This will take you to hboot; from there choose Recovery.
Enable developer mode from settings, plug in to a computer, and issue the command adb reboot recovery.
Also note that it is prudent to do a full TWRP backup to external storage (microSD, USB OTG) before anything else, so you have a good recovery point if things go wrong.
To copy the system/lib/modules directory, you can use a root-enabled file explorer or TWRP. To do it in TWRP:
Reboot to TWRP.
In TWRP, select Mount. Make sure that system is checked.
Back to the main TWRP menu, select Advanced.
In the advanced menu, select File Manager. Then navigate to /system/lib/modules.
Tap on Select, then Copy Folder. Navigate to a new location - I used /sdcard/Backup - and tap Select again. Don't use your external SD or USB-OTG, they may not preserve permissions correctly.
To flash the SchKernel Extra, copy the ZIP file to your device, reboot into TWRP, and select Install. From there, navigate to where you copied the ZIP file and select it; then follow the prompts as sanijsnj specified.
Removing SuperSU works exactly as described. Don't forget to reboot at the end (although it may not be necessary).
To flash the stock boot, in a cmd window where you have the Android SDK, typically in the sub-folder platform-tools enter: fastboot flash boot boot.img (boot.img from the OTA ZIP).
To delete and restore /system/lib/modules, follow the steps above, starting of course from your saved 'modules' directory and copying to /system/lib.
To flash the stock recovery, again in the cmd window enter: fastboot flash recovery recovery.img (recovery.img from the OTA ZIP).
Hi guys,
Here is my complete foolproof guide on how to update your system. Please note that there may be other maybe easier ways that cut-out some steps but this worked for me. It is intended for Noobies so I apologise to more advanced users if it seems tedious and long-winded. But that's how Noobies like it with everything explained in detail.
IMPORTANT NOTE: If you have previously used parallel apps then before doing any of this process you must delete user 999 from the system, otherwise you backups will not work!!!
From a terminal window (I use terminal emulator from play store ) type su and enter. Now type the command pm remove-user 999 and enter. Now you shouldn't have to worry about parallel apps messing up your backups.
Thanks to @dgunn for this :good:
https://forum.xda-developers.com/on...estore-999-t3801632/post76760812#post76760812
Also, please note that I have NEVER previously installed an un-official twrp on my device (wanted to wait for official ), however, I was unlocked, and rooted with magisk v16.0 and on stock oos 5.1.5 before beginning this upgrade process.
If you already have an un-official twrp installed, then I cannot guarantee that this guide will work for you. It might, it might not
Disclaimer: This is a guide for helping others. It is your choice to follow it and I take no responsibility for any problems you encounter as a result of following this guide. You do it at your own risk
Ok, lets get started......................
Actually, before we do let's get one thing clear that is confusing a lot of people regarding fastboot and twrp. There are 2 ways of putting twrp recovery onto your phone. A temporary way (disappears after rebooting and goes back to stock recovery) and a permanent way (the best way that stays put - what we all want right?). This guide assumes that you don't currently have twrp on your phone.
In order to put a permanent official twrp on your phone, first we have to boot (NOT flash!) into a temporary version of twrp. The fastboot command for this is "fastboot boot path_to_temporary_twrp.img" (without the quotes of course )
The difference between temporary twrp and permanent twrp is in whether we either fastboot boot or fastboot flash.
Ok, let's begin
First of all, as a precaution, disable all security on your device like pin, pattern, password, fingerprint. Make sure that when you wake your phone it goes straight to the homescreen without any prompts for pins etc etc. May not be needed but it's what I did
1. Download the following files to the following locations....
a. Official oxygen OS 5.1.6 zip file (full zip) > to root of sdcard .
b. Official twrp installer ZIP file > to root of sdcard. (This is our permanent twrp file)
c. Magisk root zip file (I used v 16.0 but v16.4 zip file should be okay too) > to root of sdcard.
d. Official twrp installer IMG file > to your PC in the same folder as your fastboot files. (This is our temporary twrp file)
These files are available for download in other threads on XDA just search for them.
Once that is done proceed as follows.....
2. Go to settings>system updates and click the gear icon in the top right and choose "local upgrade" and then select the Oxygen 5.1.6 zip file from your sdcard. The system will now begin to update itself. Once finished it will prompt you to reboot, do this, and the system will boot back up into Oxygen OS 5.1.6 :good:
3. Now, long press your power button and select reboot and select bootloader option and your phone will reboot into bootloader (fastboot) mode.
4. On your PC go to your fastboot folder and open a command prompt in that folder (don't forget you previously put the temporary twrp image file in here)
5. Now plug your phone into the PC
6. At the command prompt enter following command fastboot devices
and your phone should show up as connected and recognised.
7. We are now going to boot the phone into the temporary twrp. Type the following command fastboot boot <name of temporary twrp file (from your fastboot folder)>.img
8. Your phone will now boot into the temporary twrp recovery and from here we can now flash the permanent version of twrp that we previously put on our sdcard.
9. On your phone, select Install, then find the twrp zip file on the root of your sdcard, select it and swipe to flash.
10. Once this has flashed successfully, we now need to reboot into this new permanent recovery. DO NOT REBOOT TO SYSTEM AT THIS POINT! Now, select "Reboot" option and select "Recovery". Your phone will now reboot into the new permanent twrp. You can now forget about the other temporary twrp from earlier
11. Once the phone goes back into recovery select Install option and find the Magisk root zip file on your sdcard and select it. Now swipe to flash it. After successfully flashing Magisk, you are now ready to enjoy the fruits of your labours
Go back to the twrp homepage and select Reboot>system.
The system will now boot normally and if you have followed these steps to a Tee you will be on OOS 5.1.6 and rooted!
I have also done a successful twrp backup without any error messages. Your previous data will be untouched and you can now set-up your security again.
One final thing to note - because the boot and recovery partitions are now combined, this means that everytime you flash something to your boot partition, your new permanent twrp recovery will be lost and you will have to re-install twrp again from scratch initially through fastboot.
Enjoy
carlos67 said:
From a terminal window (I use terminal emulator from play store ) type su and enter. Now type the command pm remove_user 999 and enter. Now you shouldn't have to worry about parallel apps messing up your backups.
Click to expand...
Click to collapse
I bet the terminal command should be:
pm remove-user 999
I've made almost the same without problem
After many years of being actively involved in unlocking, flashing, and tinkering. I feel I'm starting from scratch. This quick guide is exactly what I've been waiting for as I'm in the same situation with being simply unlocked and rooted lol. I'll be replicating these steps shortly ?.
Only thing I'm wondering, once everything is done and running... If I flash a rom with the official "permanent" twrp, it's gone gone? Let's just say, renovate ice ROM?
Maybe it's the 16 hour day I worked and lack of sleep... But having it replaced upon a single rom flash and carrying the name "permanent" seems like 2 opposing ideas lol
Kiddman said:
I bet the terminal command should be:
pm remove-user 999
Click to expand...
Click to collapse
Yes, well spotted and corrected :good:
InflatedTitan said:
After many years of being actively involved in unlocking, flashing, and tinkering. I feel I'm starting from scratch. This quick guide is exactly what I've been waiting for as I'm in the same situation with being simply unlocked and rooted lol. I'll be replicating these steps shortly ?.
Only thing I'm wondering, once everything is done and running... If I flash a rom with the official "permanent" twrp, it's gone gone? Let's just say, renovate ice ROM?
Maybe it's the 16 hour day I worked and lack of sleep... But having it replaced upon a single rom flash and carrying the name "permanent" seems like 2 opposing ideas lol
Click to expand...
Click to collapse
If you were to flash a full OTA official update then yes, your "permanent" twrp will be gone because the boot partition gets flashed to stock and you'd need to re-install twrp starting in fastboot. However, for custom rom flashes, it depends if their is a kernel bundled in with the rom. If not then twrp should remain, if yes then as with official update, re-install twrp.
It's more normal for a custom rom to simply overwrite system partition without touching boot partition and twrp, but, sometimes custom rom's like Renovate come bundled with a kernel (TBalden's) and wipe out twrp.
If I'm wrong on this I stand to be corrected.
Kiddman said:
I bet the terminal command should be:
pm remove-user 999
Click to expand...
Click to collapse
Yes you are correct because this was my finding and thank you OP for not giving credit
My findings of the 255 error (999)
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
dgunn said:
Yes you are correct because this was my finding and thank you OP for not giving credit
My findings of the 255 error (999)
https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
Click to expand...
Click to collapse
My apologies, an oversight, corrected
carlos67 said:
My apologies, an oversight, corrected
Click to expand...
Click to collapse
Thank you sir. And great write up btw
Something to note is the Renovate ICE 1.0 magisk module messed with the text in settings on OOS 5.1.6. It went back to normal when I disabled that module.
I thought it was the VoEnabler module initially but I wasnt correct.
I put the zip in the root folder (Not the actual folder named root) but the local upgrade isn't showing anything in there.
I'm on 5.1.5 rooted with Magisk 16.0 and have 5.7 magisk manager installed along with xposed and gravity box.
Any idea why my local upgrade isn't detecting the upgrade zip? I downloaded it from Funk Wizards post. I got clicked the "official" link for OOS 5.1.6
I have a custom kernel and magisk installed, can I still follow this guide?
surface13 said:
I put the zip in the root folder (Not the actual folder named root) but the local upgrade isn't showing anything in there.
I'm on 5.1.5 rooted with Magisk 16.0 and have 5.7 magisk manager installed along with xposed and gravity box.
Any idea why my local upgrade isn't detecting the upgrade zip? I downloaded it from Funk Wizards post. I got clicked the "official" link for OOS 5.1.6
Click to expand...
Click to collapse
Figured it out, it was because the ro.product.device=OnePlus 6 instead of OnePlus6 in the build.prop file.
I had originally changed it to sailfish to see if I can get Daydream working. When I changed it back I accidentally added a space =/
Anyone done this on a phone with unofficial TWRP to start out yet?
Lownita said:
I have a custom kernel and magisk installed, can I still follow this guide?
Click to expand...
Click to collapse
Yes you can.
Considering that many of us have been rooted with patched boot image and no custom recovery, this guide is very well written.
Simple Guide is Already available | No Root | No Rom
youtube.com/watch?v=a7rh4NpYD7E
I followed the above youtube guide . Very simple .
Steps :
Install VPN app like Surf Easy Android VPN
Change Region to Canada or Germany
Again try to update the Oxygen OS
It will show in update available .
"
2. Go to settings>system updates and click the gear icon in the top right and choose "local upgrade" and then select the Oxygen 5.1.6 zip file from your sdcard. The system will now begin to update itself. Once finished it will prompt you to reboot, do this, and the system will boot back up into Oxygen OS 5.1.6
"
After that I got constant reboot with the message " System UI has stopped"
x111 said:
"
2. Go to settings>system updates and click the gear icon in the top right and choose "local upgrade" and then select the Oxygen 5.1.6 zip file from your sdcard. The system will now begin to update itself. Once finished it will prompt you to reboot, do this, and the system will boot back up into Oxygen OS 5.1.6
"
After that I got constant reboot with the message " System UI has stopped"
Click to expand...
Click to collapse
Could be a corrupt download file. I suggest you do the following.....
Re-download the file and check it's good using an MD5 checker app/tool. Then, boot your phone into bootloader (fastboot) mode by powering off first and then pressing and holding the vol up button.
Then follow steps 4-to-10 in my guide for installing (1st) temporary twrp and then (2nd) permanent twrp. Once you have permanent twrp and are booted into it you should then copy the "new" download zip for the OTA that you md5 checked from your PC onto the root of your sdcard and install it by flashing the zip file in twrp. Now you should reboot to system which will change the active slot to the updated OOS you just flashed and then if you want boot back into recovery to flash a custom kernel (if you so wish) and Magisk root zip (again if you so wish).
carlos67 said:
Could be a corrupt download file. I suggest you do the following.....
Re-download the file and check it's good using an MD5 checker app/tool. Then, boot your phone into bootloader (fastboot) mode by powering off first and then pressing and holding the vol up button.
Then follow steps 4-to-10 in my guide for installing (1st) temporary twrp and then (2nd) permanent twrp. Once you have permanent twrp and are booted into it you should then copy the "new" download zip for the OTA that you md5 checked from your PC onto the root of your sdcard and install it by flashing the zip file in twrp. Now you should reboot to system which will change the active slot to the updated OOS you just flashed and then if you want boot back into recovery to flash a custom kernel (if you so wish) and Magisk root zip (again if you so wish).
Click to expand...
Click to collapse
Thanks for response.
https://forum.xda-developers.com/showpost.php?p=76773727&postcount=153
Followed the procedure: Installed EX Kernel as well. Now I'm getting a popup message after every reboot: There's an internal problem with your device. Contact your manufacturer for details.
No issues as such but I'm getting this message everytime I reboot. Any suggestions?
hello xda,
This tutorial shows you that how to make your device fully functional with root.
but most of the peoples question is to pass SafetyNet, make their device status "Official" and also to work with Private Mode after root and with custom kernel. And here is the answer ,
BEFORE BEGIN, BACKUP YOUR DATA AND DOWNLOAD CORRECT FILES. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSE TO YOUR DEVICE BY THIS PROCEDURE!!!
1. Download and flash stock oreo firmware via ODIN.
2. After boot, Turn on developer mode and turn on OEM Unlock.
3. turn off your device and get in to download mode.
4. Flash latest TWRP recovery via ODIN.
6. Get in to twrp recovery and format data and again boot into twrp.
7. first flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk", thirdly flash "TGP kernel v6.8.0".
8. After boot, update magisk app itself ( Latest v17.1 ).
9. download and install any root browser app ( root explorer recommanded) and give the root permission.
10. Navigate to /system/priv-app/PersonalPageService and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
11. Navigate to /system/app/sysscope and delete the apk file and replace with modified apk
( Do not forget to set correct permission "rw-r-r" or chmod 644).
12. Reboot the device.
13. Now you can check SafetyNet, System Status and private mode.
NOTE :
DO NOT ATTEMPT TO INSTALL SYSTEM UPDATE. BECAUSE YOU MAY HAVE INSTALLED CUSTOM RECOVERY. SO THE UPDATE WILL PROBABLY FAIL.
YOU CAN OBTAIN UPDATE PACKAGE AT "/data/fota".
YOU CAN ALSO RIDE WITH BANKING APPS AND OTHER APPS WITH ROOT.
CAUTION :
●DO NOT FLASH CF SU.
●DO NOT ATTEMPT TO FLASH SYSTEM UPDATE.
●DO NOT INSTALL XPOSED FRAMEWORK. THIS WILL TRIGGER SAFETYNET.
KNOWN BUGS : NOTHING YET. TESTED ON GALAXY S7 (EXYNOS).
Files
( sysscope, PersonalPageService ) : https://drive.google.com/folderview?id=1ekOXMNMYGhaMke58y_xkVMFiAvP-Ncpm
no-verity-opt-encrypt-6.0 :
https://androidfilehost.com/?fid=817906626617949632
TGP Kernel v6.8.0 :
https://androidfilehost.com/?fid=1322778262903992351
Systemless magisk :
https://www.google.lk/amp/s/forum.x...-magisk-v7-universal-systemless-t3473445/amp/
second method:
Download (e.g. with SamFirm (v0.3.6)) and flash stock oreo firmware via Odin
After boot, Turn on developer mode and turn on OEM Unlock.
Turn off your device and get in to download mode.
Flash latest TWRP recovery via ODIN.
Get in to twrp recovery and format data and again boot into twrp.
First flash "no-verity-opt-encrypt-6.0", secondly flash "latest magisk"
After boot install latest magisk manager
In magisk manager install the module Xposed Framework (SDK 26) systemless
Install XposedInstaller_3.1.5-Magisk from https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
In XposedInstaller-App install Firefds Kit [Oreo]
Start Firefds Kit [Oreo] and enable in Security hack "Fake system status"
Now the system status is official and you can download the OTA-Update.
To get ctsProfile: true and basicIntegrity: true you have to deactivate Xposed in the XposedInstaller-App (disable Xposed Status) and disable the module in magisk manager
But the interessting question would be how to install OTA updates without loosing root.
Because, if you go in the xposed method, It will probably trigger SafetyNet. So you couldn't be able to ride with updates, banking apps and etc.
This is why I placed modified Sysscope in order to make official.
And yes, stock private mode checks for custom binary or custom kernel. So the best way to modify the apk to work with custom binary.
Unfortunately, you cannot be able to install system updates via recovery. But, you can extract the fota.zip and place those files manually at your own risk. But I recommend you not to do.
DO NOT INSTALL XPOSED. IT WILL TRIGGER SAFETYNET. EVEN THOU SYSTEMLESS METHOD WOULDN'T HELP.
What should I do to get root again after the OTA?
Reflash magisk to regain root access
Are there any news to this topic?
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.
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 2023For 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.