Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please:
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port
We will have to try soon... It's the perfect set up for flashaholics
Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk
I can't make it work
fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Superb, I missed it in this great smarphone
acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?
there is only one TWRP in your folder. can you point me to another. I'll try no worries
acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....
BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/
BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?
Fistly, I am not responsible to any harm done to your device. You should know what you are doing.
Secondly, this WILL TRIGGER KNOX irreversibly.
You will also have to format your internal memory in case you have never done this before.
KEEP THAT IN MIND
So you are going to need twrp for exynos: here
Latest Magisk installer zip: here
Odin: here
Not entirely sure if it is required but force encryption disabler: here
1) Go to developer settings in your phone and enable "OEM unlocking". Transfer the magisk zip onto the device and the encryption disabler zip.
2) Shut down your phone and hold power button+home button+volume down to turn it on. press volume up and plug it into your pc directly (without a hub)
3) Open odin and load in the AP section the TWRP file (it's an .img.tar). Disable auto reboot and flash
4) Hold power+home+volume down and, after it leaves download mode, change from volume up to volume up.
5) REALLY IMPORTANT IN ORDER TO KEEP SAFETY NET is to press "keep system read only"
6) IN CASE YOU CAN'T READ THE INTERNAL STORAGE OF YOUR PHONE (check that by pressing on install and checking internal storage), go to format-->format data and type yes. It explains there that, by doing so, you will remove encryption.
7) Now go to install and flash the encryption disabler and then the magisk zip
In theory, if all of this has been properly done, magisk su will be installed and your safety net will be in green.
If you have any questions, don't hesitate to ask.
Looking forward to any sugestions.
Here is proof that this works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is for version 7.0 of android and model 930f? in stock rom works as it is?
I'm on Oreo, and I tried to follow this.
I tried mounting USB OTG just to flash the encryption disabler and magisk but I had the verification failed error.
I don't have backup of my files (non-rooted so can't use Titanium backup). I also can't access data / internal storage using TWRP but I can't format my phone given my lack of backup. Any other way to fix this?
Why would you flash TWRP?
Won't that modify a partition? Or is TWRP present for only one reboot when selecting not to modify /system?
Do we need to unlock BootLoader anymore?
Would it not be beneficial for puerile if you posted a method to check if encryption was enabled and active, prior to performing these steps?
Thank you
That is what I am thinking about too...
I am on OREo as well. So, best would be to launch TWRP temporarily and flash then, isn't it?
I would do it this way as I have done it 5 mins ago with Sony xperia M5 E5603.
1. Backup DRM keys - if possible....
2. UNlock Bootloader
3. Boot TWRP remotely
4. Flash magisk
Is it that way? I dont wanna brick or loose my S7!!
Hi, I have TWRP and supersu now, is there a way to install magisk without unroot my phone ? Can i install Magisk and than leave supersu or i need first remove supersu and than install Magisk ?
Does this work on the canadian version of the s7 edge? Model number. sm-935w8?
Neemia86 said:
Hi, I have TWRP and supersu now, is there a way to install magisk without unroot my phone ? Can i install Magisk and than leave supersu or i need first remove supersu and than install Magisk ?
Click to expand...
Click to collapse
I was wondering about that as well.
Me too. But this thread seems to be abandoned
Neemia86 said:
Hi, I have TWRP and supersu now, is there a way to install magisk without unroot my phone ? Can i install Magisk and than leave supersu or i need first remove supersu and than install Magisk ?
Click to expand...
Click to collapse
Since you have TWRP installed, uninstall SuperSU and clean up it's files since they will trigger safetynet. Flash latest Magisk, no problem
Shani Ace said:
I was wondering about that as well.
Click to expand...
Click to collapse
Bluecharge said:
Me too. But this thread seems to be abandoned
Click to expand...
Click to collapse
Hello everyone,
I am quite desperate, trying to root my phone so that I can get access to my phone internal memory to run a photo recovery program.
I have been really stupid and I made the mistake to not back up my files of my internal memory before doing the format data step (amongst probably many other stupid things, let's agree I've been making things worse and worse).
I have followed the guide in this thread.
Phone details:
Samsung Galaxy S7 edge
SM-G935F
Android 8.0
Activities done:
- Developer mode
- USB debugging
-OEM unlocking
- Reboot
- Download mode
- ODIN
- AP: TWRP
- Reboot
- Got into recovery mode
- Got into TWRP (keep system read only)
- could not read internal storage of the phone
- format --> format data --> yes (to remove encryption) (FORGOT TO BACKUP FIRST)
I did not dare to proceed to step 7:
7) Now go to install and flash the encryption disabler and then the magisk zip
So right now I'm still in the TWRP after recovery mode reboot, having just formata data the internal memory (but with keep system read only).
--> Can I safely move on to step 7?
--> Should I try something else?
--> How do I do step 7? ((7) Now go to install and flash the encryption disabler and then the magisk zip --> Where do I put the encryption disabler and after magisk? Is this Odin again?)
I hope someone is willing to help me.
I realize I should not be messing with these things since I am not experienced/knowledgeable in this at all, but it is kind of a last resort hail mary step for me to try to recover my photos.
Thank you kindly for any help or suggestions.
Eve
Eve2019 said:
Hello everyone,
I am quite desperate, trying to root my phone so that I can get access to my phone internal memory to run a photo recovery program.
I have been really stupid and I made the mistake to not back up my files of my internal memory before doing the format data step (amongst probably many other stupid things, let's agree I've been making things worse and worse).
I have followed the guide in this thread.
Phone details:
Samsung Galaxy S7 edge
SM-G935F
Android 8.0
Activities done:
- Developer mode
- USB debugging
-OEM unlocking
- Reboot
- Download mode
- ODIN
- AP: TWRP
- Reboot
- Got into recovery mode
- Got into TWRP (keep system read only)
- could not read internal storage of the phone
- format --> format data --> yes (to remove encryption) (FORGOT TO BACKUP FIRST)
I did not dare to proceed to step 7:
7) Now go to install and flash the encryption disabler and then the magisk zip
So right now I'm still in the TWRP after recovery mode reboot, having just formata data the internal memory (but with keep system read only).
--> Can I safely move on to step 7?
--> Should I try something else?
--> How do I do step 7? ((7) Now go to install and flash the encryption disabler and then the magisk zip --> Where do I put the encryption disabler and after magisk? Is this Odin again?)
I hope someone is willing to help me.
I realize I should not be messing with these things since I am not experienced/knowledgeable in this at all, but it is kind of a last resort hail mary step for me to try to recover my photos.
Thank you kindly for any help or suggestions.
Eve
Click to expand...
Click to collapse
After u removed data encryption via format data ,reboot to recovery yet again, since there is fixed modded TWRP by tkgg1996 there is no need for encryption zip.
Download fixed twrp by tkgg1996 here
https://mega.nz/#!oFd2RIpa!M2JYNFiurMlDp_jAblE8a4E2qQEYZ-yMXx8eMHhBZ7I
Then, in twrp click install and in bottom right corner select image file press it and now find downloaded twrp from link above select the image and select recovery,after it's done reboot to recovery again and no more worry about encryption ever again. Now u can flash whatever u want
You don't really need to flash magisk ,it is only if u wanna hide root and device to be certified in play store. But can't hurt anyway and it's the best root option. Flash magisk 18.1 in recovery
Scorpionea said:
After u removed data encryption via format data ,reboot to recovery yet again, since there is fixed modded TWRP by tkgg1996 there is no need for encryption zip.
Download fixed twrp by tkgg1996 here
Then, in twrp click install and in bottom right corner select image file press it and now find downloaded twrp from link above select the image and select recovery,after it's done reboot to recovery again and no more worry about encryption ever again. Now u can flash whatever u want
You don't really need to flash magisk ,it is only if u wanna hide root and device to be certified in play store. But can't hurt anyway and it's the best root option. Flash magisk 18.1 in recovery
Click to expand...
Click to collapse
Thank you very much Scorpionea!
I managed to get the right version of TWRP installed.
- However, I seem to still not have root access? (Or at least Diskdigger photo recovery tells me).
- I also do not manage to install Magisk (I tried several ways, with image, zip, magisk manager). Unfortunately I cannot post an image yet. The error message says: updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v18.1.zip
Updating partition details...
Failed to mount /data (Invalid argument)
...done
- In TWRP my internal memory shows up as 0 (does not mount?)
- I bought an sd card and tried to install Magisk from there, same lack of result. The SD card does show up in TWRP
Thank you very much for taking the time to help, I really appreciate it
Eve
Eve2019 said:
Thank you very much Scorpionea!
I managed to get the right version of TWRP installed.
- However, I seem to still not have root access? (Or at least Diskdigger photo recovery tells me).
- I also do not manage to install Magisk (I tried several ways, with image, zip, magisk manager). Unfortunately I cannot post an image yet. The error message says: updater process ended with ERROR: 1
Error installing zip file '/external_sd/Magisk-v18.1.zip
Updating partition details...
Failed to mount /data (Invalid argument)
...done
- In TWRP my internal memory shows up as 0 (does not mount?)
- I bought an sd card and tried to install Magisk from there, same lack of result. The SD card does show up in TWRP
Thank you very much for taking the time to help, I really appreciate it
Eve
Click to expand...
Click to collapse
It seems encryption is still there, you must format data in twrp again ( remember doing this you will lose all data )Format data type yes, when done reboot to recovery again and should be all good
You must use modded twrp if I don't wanna see anymore internal storage at 0. Then try flashing magisk again
Hi, i unistalled supersu completly, but when i try to flash magisk zip from TWRP i got an error;
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Anyone could help me ?
Samsung s7 edge exynos 935F with Android 8.0 onboard
PS: safetynet test passed
hey plzzz need help i am trying to find twrp for my s7edge exynos cpu its saying not to flash twrp on s7edge mine s7edge plzz anyone can link me dl to files i need like twrp and magisk for my phone plzzz i be super thank full info
s7edge SM-G935F exynos cpu not snapdragon cheers in advance
---------- Post added at 08:46 PM ---------- Previous post was at 08:21 PM ----------
pllzzzzzz some one help i flash the img file then when i do the thing it goes to red screen plzz baddly need magisk root so i can spoof pokemon go plzz can some one add rar file for me with all right files for my phone the phone info is galaxy s7 edge SM-G935F cpu exnyos not snapdragon also bought phone in australia plzzz help me
Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
kapmino269 said:
Thank you very much for building twrp but there are bugs :
1- After I make steps all is done I power off it but when I open it isnot boot & i see a message All the words I understood that "you flash unauthornized boot.img & recovery img and return the phone to the company to fix the phone" and phone didnot boot I recognize that when I open internet in phone samsung detect the change in phone so i solved it by:
:good: I repeat the steps but after i connect to internet , i activate magisk and close wifi and download afwall on my sdcard from appkpure by pc and install the app an enable firewall and solved but there message that rules not apply but in fact it is applied and all is done . SOLVED
2-When I close phone and recharge it, it isnot recharged but it continue rebooting not to system but just recharge windows and poweroff and agian to recharge window And so on .
I coulding solve but I sure the error is in boot.img or in another . NOT SOLVED
Sorry for my english.................
Click to expand...
Click to collapse
Thanks for all the info, but does TWRP actually boot?
kapmino269 said:
Twrp is very very good and backup and restore and mount are good but there are bugs in system not in recovery addition the last:
3- the percentage of battery when charging,it isnot change . NOT SOLVED
What is the reason ?
Click to expand...
Click to collapse
Percentage doesn't change in twrp or when power off?
kapmino269 said:
SORRY MR ashyx there isn't bugs in system my charger was cut and it is the reason of rebooting to recovery. But bugs in recovery brightness control and backup encryption.
And your build is good ask twrp.me to make it official.
Click to expand...
Click to collapse
You will need to Format (not wipe) /data to remove encryption and mount the data partition. Samsung encryption isn't supported yet by TWRP.
Brightness isn't a deal breaker, but I'll look into it.
Could you do me a favour and post the recovery.log so I can check it over?
kapmino269 said:
And I forget said that all afwall versions above 2.9.9 doesn't work and Samsung will lock the phone and you should download afwall with date 5/2018
Click to expand...
Click to collapse
What do you need AFwall for?
kapmino269 said:
To prevent Samsung apps detect the change on the boot.img and recovery.img and so on and I told you at first that after flashing and activate magisk I set wifi on and when I power off the device and open it ,I couldn't open phone on any mode ,there is message apear to me told if I boot to system it said as I remember and I understand that "there is boot.img flash to phone by unauthorized way please return device to company or someone you buy the device from him to fix the phone " and replacing when reboot recovery boot.img by recovery. img and as I remember the screen was blue and the text was written in black and red. so I flash sammobile stock with Odin and repeat your twrp installing steps and activate magisk and close wifi and put afwall 2.9.9 (above versions didn't work ) and the error didn't appear again .
Click to expand...
Click to collapse
I don't think that you need AFwall. When you see that message boot to TWRP and format your device, install Magisk and the Oreo encryption disabler.
This should prevent this message appearing again.
Also disable securitylogagent apk.
Can this be used to flash GSI?
Jason Grewal said:
Can this be used to flash GSI?
Click to expand...
Click to collapse
As posted in the OP :
Update 8/12/2018
Current status - Beta (Tested working)
Treble supported
Bugs: brightness slider
Click to expand...
Click to collapse
kapmino269 said:
sorry I see another error in restore in TWRP .
all partitions restored but when I finish restore twrp said unable to mount /system and I couldn't reboot system
Click to expand...
Click to collapse
Have you tried backing up only system again then immediately restoring?
Also which media are you restoring from?
Also need the recovery log after failure.
kapmino269 said:
A1 :No , I will try backup system and system image only.
A2 :I restore from usb otg .
A3 :It success in restore efs boot vendor and others but system not mount and tried to return system again .
££i flash sammobile rom and install magisk as you tell and restore all phone partitions Except system and system image ££ The phone open again.
###I will try restore system again and i will sent you recovery.log BUT WHICH MEDIA I SHOULD USE USB OTG OR SDCARD ###
I am sorry for disturb.
Click to expand...
Click to collapse
Can you try backing up just system, not system image to internal storage then try restore?
kapmino269 said:
ok, I will try .
I would ask you about something else but sending you private message unanable I need to ask you but i couldnot because the question is about something else twrp for j415f how to send the issue to you
Click to expand...
Click to collapse
If it's related to this device then just post it. I don't accept pm's.
kapmino269 said:
A-Restoring system only and other partition is done and succeed and faster from internal storage but if i copy it to pc or sdcard Is all files will copied or not or Error will apper after copy (restoring again).
Thanks for your help .
1- it is related to j415f some apps like busybox and linux deploy and afwall(new version) grant root access but didnot run.
2- #
Another problem :
no,it isnot .it related to wlan monitor mode for gt-i9500 (internal (bcm4335 ) or external (TL-WN22N) ) , I tried linux deploy kali hunter nexmon others ,and please reply if you could help me or reach me to someone help me .
#
please reply me quickly about (2) to delete it
SORRY I havenot any way to reach you except this .
Click to expand...
Click to collapse
1. Isn't really related to twrp but magisk itself. Better posting in the magisk thread.
2. Unfortunately can't help you with this as I don't mess around too much with that kind of stuff.
I wouldnt dare to do anything on this before everything is 100% clear and failproof. This phone behaves like its about to collapse every second idk why but it feels like that
kapmino269 said:
Thank you very much for your help and your interest .
Please ,Can you fix restoring system from usb otg ? and all files you need from me i will send you it ,
you must make your twrp ideal and make it official in #twrp.me# like Alberto86(recognise developer) : make gt-i9500 twrp and ge officialty .
surendrajat(member ) : Make SM-J737S twrp it is in #twrpbuilder.github.io#
I think you should publish the recovery in this sites at the nearest time. I think also you should make video on youtube to make your project spread out faster ,because there are people donot know xda ,I tried to make video but my presentation was very bad so i delete it from youtube .
And Sorry for distrubt
Click to expand...
Click to collapse
I don't think there is anything to fix regarding the restorating of a backup from OTG.
It's just simply a case of some media is not suitable for backup and restore.
I've even seen reports of certain MicroSD cards causing issues with TWRP.
It's likely that if you try a different USB stick you won't have any issues.
As regarding making it official. I will consider it. However I have many, many builds of TWRP for a lot of other devices that are not official either.
This is due to the fact I do not like the convoluted system of getting it made official.
I have discussed this previously with teamwin and asked for a proper submissions page to no avail.
kapmino269 said:
Ok as you like but you can improve twrp .
I mean :
1 -Could you compress encryption disable and
rmm bybass and recovery in twrp.tar file to flash it by odin in one step wihout following install steps that you write , Steps may be difficult with others , With me I try serval times to success and i know some skills about android but others may donot know .
2 - Why your twrp depend on magisk install
,if magisk doesnot install phone doesnot reboot system , I think twrp should not be depend on root & If some one need twrp and doesnot need root.
3 - Busy box i cannot install it in my phone why ,?
Click to expand...
Click to collapse
No I cannot make an all in one to flash in ODIN.
Firstly because its not possible. Odin cannot run scripts, only recovery can.
Secondly if people cannot follow instructions then maybe they shouldn't be attempting to modify their device.
TWRP doesn't depend on Magisk, your device does.
Samsung incorporate many security hurdles to prevent hacking and modification.
These security blocks need to be patched or the device will not boot.
These blocks can be patched manually, however Magisk can patch most of these during the root process.
I have no idea why you cannot install busybox on your device as you have not provided any info of the issue.
In any case busybox is included with Magisk. To use it install the busybox module by osm0sis.
kapmino269 said:
picture
Click to expand...
Click to collapse
I see what your saying, however I will keep things as they are. I'd prefer people to have an understanding of what they are installing and I believe it's simple enough.
Unfortunately I can't help with the busybox issue. However as I stated you can use the busy module provided by osm0sis.
He keeps everything up to date and is highly recommended.
kapmino269 said:
I face issue :
I test j4+ snd s4 security in lookscreen :
1- In j4+ : if I delete /data/system/locksetting.db or all contain locksetting name in twrp buy terminal or file manager or script.
2 -add delete *.key on s4 .
Is there solution from system or twrp to prevent lock screen crack or it hash stolen to crack not tell me (chattr).
Thank you
Click to expand...
Click to collapse
If I'm reading it correctly you want a way of preventing the lockscreen credentials from being deleted.
The only way is to remove TWRP Tbh so no one had access to the file system.
Also this isn't really a twrp related issue and a little off topic.
However I have been looking at possible ways to password TWRP thus preventing access at all.
But even that could be circumvented by simply flashing another version of TWRP.
The only safe way is to remove twrp, unroot your device and disable OEM unlock.
kapmino269 said:
1 - I donot have any ways to reach you and you is the developer of twrp for j4+ and Know all about it and you donot accept pm , I could make
thread and you answer me in it but this issue in twrp so all is well .
2 - I want twrp and root ,Is there any solve ,I have idea may success sent me it may be sucess or not
it is
1- make data partition not mount or read only on twrp .
2- when I need to install something I will mount it by writing command in system terminal only (that command or script or program doesnot be found in twrp ) to be mounted in recovery mode .
3- I mean that data not mount in twrp without enable mounting in system and twrp doesnot have permission to mount data without system access .
but how this will acheive without you man .
another idea the same but replace mounting by read only
Click to expand...
Click to collapse
If you don't want data to be mounted in twrp then why not just leave it encrypted. Then only you have access to it via the OS?
Failing that just remove the mount entry for /data from the fstab.
This way data will only be available and mountable by using terminal commands.
The other way is to only install twrp when you need it.
For example you could use a script which you could run to flash twrp when booted to the OS each time you need it or if you prefer use something like flashify.
When you are done with twrp, simply use the restore option to restore the stock recovery.
This way only you have access to /data.
how to do this on galaxy J4?pls. help
i have a lock bootloader in download mode
Has anyone tried any gsi?
I tried havoc os 2.0 didn't work.
THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Grab these two files (Big Thanks to @mac12m99, @33bca (Offain on AFH) XDA Profile
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
Code:
adb reboot bootloader
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2. Boot up that TWRP.img file you downloaded above in this color
Type:
Code:
fastboot boot twrp-3.2.3-0-daisy_zero.img
It would boot into TWRP
2a. Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Code:
fastboot flash aboot aboot_9.6.4.img
Then type:
Code:
fastboot reboot
4. Afterwards you shall go back to bootloader quickly
Type:
Code:
fastboot erase system
Type:
Code:
fastboot erase userdata
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
Code:
fastboot flash system GSI.img
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
Code:
fastboot flash userdata userdata.img
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .
reserved
Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks
GaryFisher88 said:
Hi,
Can someone place a link to userdata from 10.0.4.0?
Official link isnt availible right know....
thanks
Click to expand...
Click to collapse
Not yet released to do so. Try the one from the dump.
Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter
It worked out the way you did.
only does not work for gcam and fingerprint reader
junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
If you have goodix fp yes need to install daisy_global_images_V9.6.11.0.ODLMIFF first but If you have fpc fingerprint no need , work in pie base stock
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse
Flavien125 said:
Hello and thank you for the guide, everything works except the fingerprint reader, a solution? I followed the guide to the letter
Click to expand...
Click to collapse
junior473 said:
It worked out the way you did.
only does not work for gcam and fingerprint reader
Click to expand...
Click to collapse
junior473 said:
Now it worked, starting the process installed daisy_global_images_V9.6.11.0.ODLMIFF via xiaomiflash first
Click to expand...
Click to collapse
Everything works for me on RR at least
InfinityXDA said:
Everything works for me on RR at least
Click to expand...
Click to collapse
yes, for me too now
Except the notch
When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Ithao said:
When you get an update from Resurrection Remix (RR) or the original rom, is there any way to install the .zip update through TWRP?
Click to expand...
Click to collapse
You must completely erase system with
Code:
fastboot erase system
and
Code:
fastboot erase userdata
and then flash the new version of RR
Code:
fastboot flash system “rr.img”
and reflash the userdata.img
Code:
fastboot flash userdata “userdata.img”
Otherwise you can’t update the stock version of the ROM that came with the device unless you provide a full store of 10.0.4.0 and test RR from there
The stable version of the stock ROM for RR is 10.0.3.0.
rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
Did you switch to RR from 10.0.4.0
rosiepie said:
Everything working except fingerprint.
Which sucks, because I chose this phone over others specifically because of the positioning of the scanner
Click to expand...
Click to collapse
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
InfinityXDA said:
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Click to expand...
Click to collapse
try Genom kernel
i had included autofix for wifi)
eremitein said:
fp will be work if you install 9.6.11 fw + fix for modem + disable encryption and then flash RR
---------- Post added at 04:38 AM ---------- Previous post was at 04:32 AM ----------
try Genom kernel
i had included autofix for wifi)
Click to expand...
Click to collapse
I have no problems what so ever I went to RR from 10.0.3.0!
can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader
barumbads said:
can anyone please give me download link of userdata.img, i dont known how to extract it from the 1.0.0.4.0 rom
also, im kinda confused at part 4, do i wait it to reboot or should i directly go to bootloader
Click to expand...
Click to collapse
Use the 10.0.3.0 userdata file.That's what i used too
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
InfinityXDA said:
THIS REQUIRES YOUR DEVICE TO BE COMPLETELY RESTORED, PLEASE BACK UP DATA BEFORE DOING THIS.
THIS HAS ONLY BEEN TESTED ON RESURRECTION REMIX YOU CAN TEST OTHER GSI'S WITH THIS (TELL ME YOUR RESULTS BELOW)
NO CUSTOM KERNELS CAN BE APPLIED RIGHT NOW
THIS DEVICE HAS A "AB" BOOT SET SO PLEASE GET "AB" GSI'S
Grab these two files (Big Thanks to @Zerovoid from 4PDA, @Seryioo, and @mac12m99)
Fixed SDCard Support TWRP Image File (Download this and put this on your SDCard and Computer)-
Original Fixed TWRP XDA Post
Fixed SDCard Support TWRP Installer Zip (Download and put this on your SDCard)-
Fixed TWRP .zip Installer
But I got TWRP on with magisk.
THIS WILL WIPE YOUR DEVICE I'M DEFINITELY NOT RESPONSIBLE FOR LOST DATA, SD CARDS, ETC ONCE AGAIN
Start with the phone being on with USB Debugging enabled with platform tools etc. correctly and bootloader unlocked
Type:
1. So flash the 10.0.4.0 ROM to get a fresh start (this is highly recommended) folder through MiFlash using the flash_all.bat, this process has to be done so backup your data before erasing.
1a. After it is done flashing it restarts, hurry and hold power + volume down to boot back into the bootloader
2.Boot up that TWRP.img file you downloaded above in this color
Type:
It would boot into TWRP
2a.Tap install and find your SD Card, find the fixed-twrp-installer-daisy.zip in this color above where ever you put it on your SD Card and install it, this process takes a few minutes when finished DO NOT HIT REBOOT SYSTEM!
2b. Hit the home button back to TWRP home screen and tap reboot >>> bootloader
3. Download this to your computer -
aboot.img
3a. Type:
Then type:
4. Afterwards you shall go back to bootloader quickly
Type:
Type:
5.Open the 10.0.4.0 folder you flashed above in #1 with MiFlash and have the "userdata.img" handy from that folder.
Download (download the one with latest date and that says "arm64" and "ab") or use the Resurrection Remix Pie ROM you have, now you will have to have those files handy.
6. Flash the Resurrection Remix or GSI (No other ROM yet tested) to system
Type:
This process takes a minute
7. Flash the userdata.img from the 10.0.4.0 folder (This is important!)
Type:
7a. Go back to TWRP
8. Download this .zip file below and put it on your SD Card (by mounting SD Card in TWRP) in a place you will remember
The .zip file is located here find the "disable force encryption" BIG THANKS TO @eremitein
9. Boot to TWRP (Power+Volume Up keybind) flashing the encryption file above on #8 that you have on your SD Card
10. Boot to the system, check the storage in settings it may say that you have 8GB
11. Be careful hitting the wrong things may damage your device, but below follow this tap directions
11a Go back to TWRP and follow below!
11b. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "System" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
11c. From the TWRP home screen tap...... Wipe>>>>Advanced Wipe, Check "Data" then tap Repair or Change File System>>>>Resize File System>>>> Swipe to Resize
12. Boot up to system and check if the storage is fixed
13. Flash your GApps through TWRP for Google Services Functionality, I highly recommend micro, nano or pico.
14. Now flash Magisk zip (optional)
DO NOT FLASH A KERNEL IT WILL MESS UP WIFI TALK ABOUT IT IN THAT KERNELS THREAD
Code Aurora Fourm (CAF Kernel)
Justice Kernel
Have fun with your GSI, nothing is buggy on RR so far. The fullscreen has been fixed!
Please tag me below upon what GSI's work with this method and make sure you hit that thanks button it took me awhile to put this together with multiple extreme failures .
Click to expand...
Click to collapse
I have installed the gsi and it's working perfectly but now i wabt to get twrp on the phone how do i do it(i don't have encryption)?
a lot of thank for that.... iam waiting for that...lots of thank you admin...
If something goes wrong can we flash stock ROM and get the phone fixed? Does resizing the system/data partition affect the process of recovering the phone?
Team Win Recovery Project 3.3.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
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.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: Note 10(Exynos variants - N970/971/975/976/N/F/B)
Download
Sources:
TWRP Tree and kernel source
Changelog:
15.12.2019
- Updated TWRP for Android 10.0
- From now on no more Magisk Prepatched images (if you need it patch it byself or flash my kernel where patched recovery is not needed)
22.09.2019
-Reverted MTP Changes from last build since for some mtp dont worked in system
21.09.2019
- Fixed the bug that mtp dont worked any more on TWRP when usb cable got disconnected and reconnected
- Modded Kernel for have MTP in TWRP, Samsung Roms and GSI roms (for GSI Roms flash GSI_MTP_ENABLER.zip)
- Reverted FFS MTP changes since new way is more stable
14.09.2019
- Fixed MTP using FFS_MTP in recovery (Thx to @bigbiff for add FFS MTP support on TWRP 3.3.0. FFS_MTP dont corrupts large files like the mtp used by samsung in the roms)
- Removed File Based backups because the phone refuses to boot from filebased backups since they breaks the rootfs
27.08.2019
-Initial Release
Bugs:
-No one
Telegram Group
https://t.me/twrp_n10
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy Note 10 (Exynos), Kernel for the Samsung Galaxy Note 10+
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2019-08-27
Created 2019-08-27
Last Updated 2019-12-15
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with power + vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field (if you want to patch twrp byself patch the downloaded tar in magisk manager. patched tar is in downloads folder after patch)
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp
flash the disabler that is on TWRP download link
flash my kernel avaiable here
press reboot to system in twrp.
so all builds are uploaded unpatched. for magisk you can patch it byself with magisk manager
Beware of multidisabler 1.3 at this moment, it has some bug
oggi21 said:
Beware of multidisabler 1.3 at this moment, it has some bug
Click to expand...
Click to collapse
then ian needs to fix it. i saw only he added note 10 support.
geiti94 said:
so all builds are uploaded unpatched. for magisk you can patch it byself with magisk manager
Click to expand...
Click to collapse
so you do the patch with magisk and ap rom flash via odin route still?
its old school jsut just fllash twrp via odin
Deezy88 said:
so you do the patch with magisk and ap rom flash via odin route still?
its old school jsut just fllash twrp via odin
Click to expand...
Click to collapse
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
geiti94 said:
then ian needs to fix it. i saw only he added note 10 support.
Click to expand...
Click to collapse
Yeah, he said he gonna fix it today
so i added in download folder byself a n10 disabler because i saw that ians one will never ever work because my twrp use busybox and not toolbox (i like it easyers for dev thats why busybox is added)
that zip disables encrpytion, fix secure storage, removed 2 libs for not let the phone fall under prenormal state etc
geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow?
Deezy88 said:
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow
---------- Post added at 11:49 AM ---------- Previous post was at 11:49 AM ----------
do it with Carney and patch it then flash the patch with odin,can it patch right now with a note 8,im getting my note 10+ tomorrow?
Click to expand...
Click to collapse
yes you can
so since i am not all the time here on xda here is a telegram group link. use it for report bugs etc since i dont read all the time the complete thread here https://t.me/twrp_n10
thank you that was fast!
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
geiti94 said:
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
Click to expand...
Click to collapse
V2 worked like a charm! :good:
geiti94 said:
so multidisabler is updated to v2 and stock rom boots again normaly sammy added 2 more encryption in the n10 that needed to get disabled
Magisk Patched builds are now uploaded too for the one that dont wants to patch byself
Click to expand...
Click to collapse
Great job geiti. Just waiting for rom release.:good::good:
geiti94 said:
in magisk manager select "select file for patch" and select then the downloaded tar. after patch you have a new tar in downloads folder of your phone
Click to expand...
Click to collapse
So, clear me if I have something miss-understand:
1. If flash rom cook: unlock OEM, flash twrp and then flash rom cook
2. If using stock root: unlock OEM, flash twrp and then patch AP with magisk and flash as Dr Ketan guide to flash Magisk?
namfat said:
So, clear me if I have something miss-understand:
1. If flash rom cook: unlock OEM, flash twrp and then flash rom cook
2. If using stock root: unlock OEM, flash twrp and then patch AP with magisk and flash as Dr Ketan guide to flash Magisk?
Click to expand...
Click to collapse
I think you're wrong for the number 2. If you wanted stock root with twrp. AFAIK you need to. Patch the AP from stock rom. Patch the twrp recovery.img . Then replace the stock patched recovery from AP patched with the patched twrp. Then you can follow dr.ketan's guide but use this new patched AP with the patched twrp inside
great now i have to spend 1000 bux to get this.
white7561 said:
I think you're wrong for the number 2. If you wanted stock root with twrp. AFAIK you need to. Patch the AP from stock rom. Patch the twrp recovery.img . Then replace the stock patched recovery from AP patched with the patched twrp. Then you can follow dr.ketan's guide but use this new patched AP with the patched twrp inside
Click to expand...
Click to collapse
Many thanks, got it.[emoji8][emoji8]
Sent from my SM-N975F using Tapatalk