Guide: Setting up Android Pay on a rooted Note 5 - T-Mobile Samsung Galaxy Note5

***THIS GUIDE DOES NOT WORK. THIS SIMPLY ALLOWS CARDS TO BE ADDED TO ANDROID PAY. PAYMENTS WILL NOT PROCESS. THIS IS A WORK IN PROCESS.***
Unfortunately us rooted users are unable to use Samsung Pay. Samsung Pay is superior to Android Pay due to its MST feature which allows the use of any card reader to take payments from the phone. Samsung Pay as of this time doesn't support a lot of cards, So Android Pay is a great backup. Just as Samsung tries to stop rooted users from using Samsung Pay, Google tries to stop them as well by blocking Android Pay. This guide will show you how to get around that.
1.) You need a non rooted phone to start.
You can either flash your Note 5 completely back to stock, or use another phone to do it. Whichever phone you use MUST be able to be rooted or this will not work. This guide will assume you will use a second device to setup Android Pay, as I did, so that you don't have to wipe your Note. If you use your Note 5 to do this, just modify the guide as needed.
2.) Download the Android Pay app from the Playstore to your non-rooted phone
3.) Setup Android Pay application fully with all your bank cards and info
4.) Force close Android Pay app
5.) Root the device
6.) Install Titanium Backup
7.) Make a backup of the Android Pay app using Titanium Backup
8.) Move the Titanium Backup folder to either a computer or OTG drive
- If you only backed up Android Pay, there should be 3 files inside of the folder.
9.) Move your Titanium Backup folder to your rooted Note 5
10.) On the Note 5 download and install Titanium Backup
11.) Open Titanium Backup and select: menu - preferences - backup folder location
- Point the backup folder location to wherever you moved the Titanium backup folder to on the phone.
12.) Close and reopen Titanium Backup if it does not automatically do this when you exit settings
13.) Select menu again and then "batch actions"
14.) Select restore missing apps with data
- Android Pay should be the only app being restored
15.) After the app is restored, DO NOT OPEN IT.
16.) Open the superSU app and select: settings - "Enable Superuser" (uncheck the box) and let it finish
17.) Reboot
18.) When the phone boots up, open Android Pay and set it up as normal
19.) Open the superSU app and select: settings - "Enable Superuser" (check the box) and let it finish
20.) Reboot
21.) Done.

This is the sole reason I won't root as I usually do. Losing Pay sucks!

I'd rather have to carry my wallet around with me than have a bon-rooted phone.

i wish i woul dof read into it more i would have never rooted if i knew this i knew i would lose samsung pay but i didnt realize i would lose android pay also...

4thehalibit said:
i wish i woul dof read into it more i would have never rooted if i knew this i knew i would lose samsung pay but i didnt realize i would lose android pay also...
Click to expand...
Click to collapse
So flash stock firmware in odin, won't that restore your ability to use android pay?

pcriz said:
So flash stock firmware in odin, won't that restore your ability to use android pay?
Click to expand...
Click to collapse
Yep that will restore the use of android pay. I am still working on this issue by the way but am in the process of releasing a rom for this phone so that comes first.

pcriz said:
So flash stock firmware in odin, won't that restore your ability to use android pay?
Click to expand...
Click to collapse
It would. However, it's possible that your phone will never go into "deep sleep" again if you have a completely stock device with KNOX tripped (due to a bug in the samsung kernel.)
The bug is easily worked around if your device is rooted or has a custom kernel.
With all this, it's still possible to have an "almost stock" device that's rooted "part time" and android pay will work (I will not support this. Hopefully one of your RC's will grab this and walk people through difficulties they experience. I don't use a ''T" variant myself and don't monitor these threads frequently:
Restore the device via ODIN to stock. Boot the device normally and get things configured.
Install TWRP via ODIN (and remove the ODIN option to reboot the device after flashing)
Manually reboot after ODIN is done and IMMEDIATELY boot into TWRP. (Not sure about the "T" variant, but some Note5 variants will overwrite TWRP with the stock recovery if they boot normally and TWRP is installed.)
From TWRP, either get an adb shell or run the following command via TWRP's advanced->terminal command:
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
From within TWRP, after the above step is performed, install SuperSU 2.67. That will install a systemless root, and perform steps for working around the deep sleep bug.
Reboot the phone. It's now rooted and android pay won't work.... In additional, a few video apps won't work (such as netflix.) To deal with the video issue, install a root capable file explorer and delete (not rename) /system/lib/liboemcrypto.so.
Reboot again without the liboemcrypto.so.
Now, when you want to use android pay, you have to disable superuser (Go into the supersu app and uncheck the box for enabling superuser) and then reboot with superuser disabled. if you haven't rebooted with superuser disabled, android pay won't work. If supersu complains about updating a supersu binary, ignore it.
I'd suggest leaving the device in a state with superuser disabled. When you need to do something that requires root, re-enable superuser, ignore the update message from supersu, and do whatever you need... and then disable superuser again.
Xposed, as always, will cripple android pay.
Be careful modifying or changing system files. Many of the changes will cause "safetynet" (the security used by android pay) to fail.
If you have something that requires superuser ALWAYS be enabled, this obviously won't work for you. If you only need root to do some minor changes (like override properties on bootup, make CSC changes, etc) then this method is fine.

garyd9 said:
It would. However, it's possible that your phone will never go into "deep sleep" again if you have a completely stock device with KNOX tripped (due to a bug in the samsung kernel.)
The bug is easily worked around if your device is rooted or has a custom kernel.
With all this, it's still possible to have an "almost stock" device that's rooted "part time" and android pay will work (I will not support this. Hopefully one of your RC's will grab this and walk people through difficulties they experience. I don't use a ''T" variant myself and don't monitor these threads frequently:
Restore the device via ODIN to stock. Boot the device normally and get things configured.
Install TWRP via ODIN (and remove the ODIN option to reboot the device after flashing)
Manually reboot after ODIN is done and IMMEDIATELY boot into TWRP. (Not sure about the "T" variant, but some Note5 variants will overwrite TWRP with the stock recovery if they boot normally and TWRP is installed.)
From TWRP, either get an adb shell or run the following command via TWRP's advanced->terminal command:
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
From within TWRP, after the above step is performed, install SuperSU 2.67. That will install a systemless root, and perform steps for working around the deep sleep bug.
Reboot the phone. It's now rooted and android pay won't work.... In additional, a few video apps won't work (such as netflix.) To deal with the video issue, install a root capable file explorer and delete (not rename) /system/lib/liboemcrypto.so.
Reboot again without the liboemcrypto.so.
Now, when you want to use android pay, you have to disable superuser (Go into the supersu app and uncheck the box for enabling superuser) and then reboot with superuser disabled. if you haven't rebooted with superuser disabled, android pay won't work. If supersu complains about updating a supersu binary, ignore it.
I'd suggest leaving the device in a state with superuser disabled. When you need to do something that requires root, re-enable superuser, ignore the update message from supersu, and do whatever you need... and then disable superuser again.
Xposed, as always, will cripple android pay.
Be careful modifying or changing system files. Many of the changes will cause "safetynet" (the security used by android pay) to fail.
If you have something that requires superuser ALWAYS be enabled, this obviously won't work for you. If you only need root to do some minor changes (like override properties on bootup, make CSC changes, etc) then this method is fine.
Click to expand...
Click to collapse
I appreciate the write up, the no deep sleep thing is a for sure issue? That sucks
Sent from my SM-N920T using Tapatalk

pcriz said:
I appreciate the write up, the no deep sleep thing is a for sure issue? That sucks
Click to expand...
Click to collapse
Wow. Did you REALLY have to quote my ENTIRE post? Do you realize how annoying that is to read from a mobile device? Do you know you can edit the quote (to trim it down) in tapatalk when replying?
Anyway, the "no deep sleep" thing - I'm guessing that you're referring to the "However, it's possible that your phone will never go into "deep sleep" again if you have a completely stock device with KNOX tripped " line in my message. (You could have made that clear by editing down the quote to only include that sentence.)
If so, it is true with "C" and "I" variant devices once KNOX is tripped. I can't confirm it with the "T" variant (as I don't have one), but it would be consistent with the other devices. That's why I typed "It's possible.."

garyd9 said:
Wow. Did you REALLY have to quote my ENTIRE post? Do you realize how annoying that is to read from a mobile device? Do you know you can edit the quote (to trim it down) in tapatalk when replying?
Anyway, the "no deep sleep" thing - I'm guessing that you're referring to the "However, it's possible that your phone will never go into "deep sleep" again if you have a completely stock device with KNOX tripped " line in my message. (You could have made that clear by editing down the quote to only include that sentence.)
If so, it is true with "C" and "I" variant devices once KNOX is tripped. I can't confirm it with the "T" variant (as I don't have one), but it would be consistent with the other devices. That's why I typed "It's possible.."
Click to expand...
Click to collapse
Yes, really I did. The edit button in my Tapatalk app causes the app to FC for me since the last update, but then again why am I explaining myself. Keep your advice, not only does my debit card work since buying the Note 5, it seems to work even better since the last security update /s. Not to mention your level of smug makes it a little hard to digest anything worth while from that post. Cheers compadre.
garyd9 said:
It would. However, it's possible that your phone will never go into "deep sleep" again if you have a completely stock device with KNOX tripped (due to a bug in the samsung kernel.)
The bug is easily worked around if your device is rooted or has a custom kernel.
With all this, it's still possible to have an "almost stock" device that's rooted "part time" and android pay will work (I will not support this. Hopefully one of your RC's will grab this and walk people through difficulties they experience. I don't use a ''T" variant myself and don't monitor these threads frequently:
Restore the device via ODIN to stock. Boot the device normally and get things configured.
Install TWRP via ODIN (and remove the ODIN option to reboot the device after flashing)
Manually reboot after ODIN is done and IMMEDIATELY boot into TWRP. (Not sure about the "T" variant, but some Note5 variants will overwrite TWRP with the stock recovery if they boot normally and TWRP is installed.)
From TWRP, either get an adb shell or run the following command via TWRP's advanced->terminal command:
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
From within TWRP, after the above step is performed, install SuperSU 2.67. That will install a systemless root, and perform steps for working around the deep sleep bug.
Reboot the phone. It's now rooted and android pay won't work.... In additional, a few video apps won't work (such as netflix.) To deal with the video issue, install a root capable file explorer and delete (not rename) /system/lib/liboemcrypto.so.
Reboot again without the liboemcrypto.so.
Now, when you want to use android pay, you have to disable superuser (Go into the supersu app and uncheck the box for enabling superuser) and then reboot with superuser disabled. if you haven't rebooted with superuser disabled, android pay won't work. If supersu complains about updating a supersu binary, ignore it.
I'd suggest leaving the device in a state with superuser disabled. When you need to do something that requires root, re-enable superuser, ignore the update message from supersu, and do whatever you need... and then disable superuser again.
Xposed, as always, will cripple android pay.
Be careful modifying or changing system files. Many of the changes will cause "safetynet" (the security used by android pay) to fail.
If you have something that requires superuser ALWAYS be enabled, this obviously won't work for you. If you only need root to do some minor changes (like override properties on bootup, make CSC changes, etc) then this method is fine.
Click to expand...
Click to collapse
{
"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"
}
Sent from my SM-N920T using Tapatalk

Related

[Guide] Root Galaxy Core Prime VE (G361H)

here you will find how to root and unroot your galaxy core prime VE.
DON'T try it on other variants, this is only for the G361H.
DO THIS at YOUR OWN RISK, I'm NOT RESPONSIBLE FOR ANY DAMAGE HAPPENS TO YOUR PHONE
It's prefered to use the TWRP method..
How To Root:
Method 1 : pre- rooted rom
1-Get the pre-rooted ROM from here
2-Download Odin 3.09.
3-If the ROM file that you downloaded is in .ZIP format extract it.
4-Extract Odin.
5-Run Odin as administrator.
6-Put the ROM in the AP field.
7-Put your phone into download mode, Power off the phone then use the three button combo to do that (power+home+vol down).
8-Press vol up.
9-Connect your phone to your PC using the USB data cable.
10-Once Odin detects your phone (it'll show a yellow box), press start.
11-The flashing operation will start, it might take upto 5 minutes depending on your PC's CPU speed.
12-The phone will reboot multiple times, it's normal.
13-The first reboot will take long, it might stay long on the Samsung logo or on optimizing apps, it's normal to take up to ten minutes.
14-Check your root status using any root app.
{
"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"
}
#notice: apps stored on SD might be temporary unavailable after rooting using the pre- rooted ROM method, however, they'll work again by their own.
Method 2: by using TWRP recovery
1-Flash TWRP recovery on your phone, follow this Link to install TWRP on your phone, go for method 2.
2-Reboot to TWRP recovery.
3-Select Reboot.
4-Then select system.
5-TWRP will tell you that you aren't rooted, and it'll ask you if you want to root, slide the slider to root.
6-wait a little bit for it to root your phone.
7-Your phone will reboot.
8-Look for superSU app in your phone's app drawer, open it.
9-Select the playstore method, using the other option will make you start the rooting process from the beginning .
10-PlayStore will open showing superSU app page, update the app.
11-After updating the app, open it, it'll ask about updating the root binary, press continue.
12-Select the normal method.
13-Wait a little bit.
14-After it success, press reboot.
15-Check your root status using any root app.
16-Enjoy root access on your core prime, don't forget to press the thanks button :good:
help
Hi. I installed TWRP as instructed. Next I went to reboot, then system. my phone just rebooted, it didn't ask me about phone not being rooted! Help!
RizziM said:
Hi. I installed TWRP as instructed. Next I went to reboot, then system. my phone just rebooted, it didn't ask me about phone not being rooted! Help!
Click to expand...
Click to collapse
Try mounting system partition then rebooting.
Very good.
Rooting failed?
HI,
I love the details in your guide.
I installed TWRP and then went into reboot > system. I then swiped to install the binary, which it did. Once it rebooted, a notification appeared for SuperSU. I click it and it said SuperSU's su binary is not present, this is a fatal error!
I would appreciate any further help
DJames23 said:
HI,
I love the details in your guide.
I installed TWRP and then went into reboot > system. I then swiped to install the binary, which it did. Once it rebooted, a notification appeared for SuperSU. I click it and it said SuperSU's su binary is not present, this is a fatal error!
I would appreciate any further help
Click to expand...
Click to collapse
Did you update superSU app from playstore, and made it update it's root binary?
TWRP adds a basic root binary that enable the latest superSU app to install it's fully working root binary.
Hi, thanks for your quick reply.
I clicked notification which opened the supersu installer. It then said "SuperSU's su binary is not present, this is a fatal error!"
I then clicked OK and the application closed.
Reopening the app still gives the same message
DJames23 said:
Hi, thanks for your quick reply.
I clicked notification which opened the supersu installer. It then said "SuperSU's su binary is not present, this is a fatal error!"
I then clicked OK and the application closed.
Reopening the app still gives the same message
Click to expand...
Click to collapse
Update superSU manually from playstore, it should tell you if superSU binary isn't installed and might offer you an option to install it uaing TWRP, you can go for this method, or you can try repeating the post method again, as TWRP will ask you agian to root if the root binary wasn't installed. However don't worry, rooting using TWRP sometimes mistakenly miss somethings which cause to fail, but repeating the process will solve it..
Mr said:
Update superSU manually from playstore, it should tell you if superSU binary isn't installed and might offer you an option to install it uaing TWRP, you can go for this method, or you can try repeating the post method again, as TWRP will ask you agian to root if the root binary wasn't installed. However don't worry, rooting using TWRP sometimes mistakenly miss somethings which cause to fail, but repeating the process will solve it..
Click to expand...
Click to collapse
SuperSU updated automatically, I did try after it updated and I did try re-rooting from TWRP. It rebooted after I clicked system under reboot section. I saw a previous comment about mounting the system partition. I mounted it and reboot, but it was no longer mounted after rebooting (by clicking reboot then recovery in TWRP). I then tried mounting without rebooting, this produced the same outcome. The phone reboots normally into the os. I also tried using SuperSU to fully unroot. I then tried TWRP again (both without mounting system partition and with mounting system partition). The phone still reboot into the OS. I do believe that I could restart from the beginning if I was able to uninstall SuperSU, but I can't as it was installed as a system app by TWRP.
I appreciate your help and hope you can find a way to make this work.
DJames23 said:
SuperSU updated automatically, I did try after it updated and I did try re-rooting from TWRP. It rebooted after I clicked system under reboot section. I saw a previous comment about mounting the system partition. I mounted it and reboot, but it was no longer mounted after rebooting (by clicking reboot then recovery in TWRP). I then tried mounting without rebooting, this produced the same outcome. The phone reboots normally into the os. I also tried using SuperSU to fully unroot. I then tried TWRP again (both without mounting system partition and with mounting system partition). The phone still reboot into the OS. I do believe that I could restart from the beginning if I was able to uninstall SuperSU, but I can't as it was installed as a system app by TWRP.
I appreciate your help and hope you can find a way to make this work.
Click to expand...
Click to collapse
It's seems that you must flash superSU flashable Zip..you can find it on the web
hey i installed cyanogenmod 12.1, and my phone is now looking like it's not rooted anymore, what method should i use to root it again ?
crackpot360 said:
hey i installed cyanogenmod 12.1, and my phone is now looking like it's not rooted anymore, what method should i use to root it again ?
Click to expand...
Click to collapse
Hey crackpot360,
Open settings, scroll to the bottom and tap "About device", then tap build number until you unlock developer options.
Now open "Developer options" (above "About device") and scroll down to "root access". Change it to the "apps" setting.
Now, when an app requests superuser permissions it will ask you just as any other superuser app would. You can also choose to allow permanently.
When an app uses superuser it will show a "#" symbol in the Status bar.
To revoke permissions in the future, open the privacy settings, tap "Privacy guard", then tap the menu button at the top and select "Advanced". Then scroll all the way to the right to control the superuser access of apps.
I hope this helps
A thanks would be great
DJames23 said:
Hey crackpot360,
Open settings, scroll to the bottom and tap "About device", then tap build number until you unlock developer options.
Now open "Developer options" (above "About device") and scroll down to "root access". Change it to the "apps" setting.
Now, when an app requests superuser permissions it will ask you just as any other superuser app would. You can also choose to allow permanently.
When an app uses superuser it will show a "#" symbol in the Status bar.
To revoke permissions in the future, open the privacy settings, tap "Privacy guard", then tap the menu button at the top and select "Advanced". Then scroll all the way to the right to control the superuser access of apps.
I hope this helps
A thanks would be great
Click to expand...
Click to collapse
OK thanks for the reply first of all,
secondly, Ive already solved the problem by flashing supersu through recovery and updating binaries for it, but now my question is, should i follow through with your steps or just let it be? because everything as of right now is working fine.
Thanks again.
Is there any way to remove "Kernel is not seandroid enforcing" and "Recovery is not seandroid enforcing" on the top of the screen on boot splash? I have already installed TWRP and flashed Lineage on it. Phone boots and works just as expected, it is just that little detail that bugs me.
Hi guys please help me,my phone (sm g361h) cant see a PC (when i connect phone with PC phone cant connect only charge )sorry for bad English
---------- Post added at 07:29 PM ---------- Previous post was at 07:14 PM ----------
ZikRiAlloH said:
Hi guys please help me,my phone (sm g361h) cant see a PC (when i connect phone with PC phone cant connect only charge )sorry for bad English
Click to expand...
Click to collapse
This problem not from PC any different phone easy connect with my PC and I can i root this device without PC
Mr said:
Try mounting system partition then rebooting.
Click to expand...
Click to collapse
I have the same problem. Can you tell me how to mount my system partition?
I went to mount, then i checked system and clicked the internal storage. After that i went to system=>reboot but it just rebooted. It didn't asked me whether or not my phone is rooted!!
For those who want to root their Samsung Galaxy phone, I recommended to use the TWRP method. Hell man I tried the pre-rooted rom but it mess up my phone like it stop and stuck at samsung logo after rebooting for indefinite time. Luckily though I fix it just installing the Stock ROM. Then use the TWRP method to root my phone. Now it is rooted and updated and working fine. BTW, if the SuperSU asking for installation by Google Play Market or TWRP, use the TWRP because SuperSU is not available in store. It will download the binary of supersu and it will go to twrp recovery and just swipe it and it will install after that it will reboot. After that your phone will be rooted. Just download some root checker app in playstore to see if it is totally rooted. That's it, thanks.

[GUIDE to ROOT] for new users, step by step, main aspects clarified

INTRODUCTION (don't skip it if you want understand what you are reading)
Here we are, as promised.
A guide for beginners who hardly understand all the brief steps described in guides: root Galaxy S5 G-900V, unlock-bootloaders, etc. thanks for everyone who helped me with big patience (jrkruse, Bryanx86, XeCuTioN, youdoofus and all other guys) and who developed the scripts/guides. This guide is to help you keep focusing there
I'll try to be as brief as possible, remembering me when I entered in theis world without knowing this phone, and eager of flashing quickly the desidered ROM. I admit I've spent different days and a bounch bad words around figuring out all the obstacles that appeared time by time: you should know from the beginning that a small variation of the process described here may force you start from zero, loosing an amount of time, and that there are different phone models and also with different chipset, so you need carefully understand which phone you have before learning the process or losing time with wrong experiments, they will not work.
Anyway this guide will help many figuring out different aspects of phone, useful to everyone who is appraching flash the S5, it's a collection of important things I've read arond and experimented myself.
PHONE:
I have a S5 G900V with Toshiba chipset "CID11", and I tested all the following only on this phone, for questions/explanations read this article:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I'm not going to give any support to other versions, but post me if I forgot something
DEFINITIONS:
PHONE: unfortunately there are a moltitude of Galaxy S5 released, they are dedicated to particular geographic areas and particular service operators, the 900V is created for Verizon brand and it has a native ROM with SIM locked. If you bought one with SIM unlocked (and you may even read under "about" it is a 900F for example! check the right one starting the download mode) and you want root it/upgrade you should consider that the first rom uploaded to begin the following process is Verizion original, and it contains SIM lock: you will not use your phone later till you flash the final desidered rom! Chances are also, if you have like I do a CID11 chipset, the SD card will stop be recognized, and that's a boring thing. EDIT: the SD card will work, it was my phone with the SD gold contacts spoiled, accurately I lift them up and sd worked always later.
CHIPSET: as I know there are two variants around, one with Chipset Sasmung "eMMC" and one with Toshiba "eMMC". Before you start you need to read the file /sys/block/mmcblk0/device/cid under the root path, the first two bytes will be 11 or 15, if you have 15 you're lucky and you may even remove the locked bootloader, if you have 11 there are not solutions yet for unlock, but you can install Marshmellow 6.0.1 (unrooted/without root). To check the file CID I suggest to install xplore from Lonelycatgames (you may find a copy around, google it and download apk, open the folder root, the path /sys/block/mmcblk0/device/ and at file cid push long and use the hex editor.
BOOTLOADER: The Verizon phones accept ROMs only containing their certificate (it's more complex but let's say it's like that), they are called stock ROM (ROMs coming from brend, original, untouched). To load other custom roms you need to unlock the Bootloader to avoid checks on certifications, and this is possible only if you have a CID 15 and only after rooting phone, and unlock bootloader. Then you will you are able to flash TWRP which is a nice console for upload any kind of rom.
Anyway, anyCID, there is a "workaround" called Safestrap that loads a TWRP console instead of the classic Android operative system (OS).. and it happens when you will reboot from its Safestrap applications: the console will load instead of Android on next reboot, and when you will reboot from Safestrap console, itself will restores Android the next boot. It's the only way to load ROMS when your CID is 11, but only very particular releases (read about down); and the way to unlock bootloader on CID15. We're waiting that someone in future will unlock also the CID11..
the "bootloader" or "download mode" can be opened only from phone switched off by pressing VolDwn+Home and when u sure u're pressing them correctly then press power keeping them pressed(!) until u see the bootloader, press then volume up.
"recovery console" or "recovery" is reached from phone switched off in the same way, but pressing Volup+Home (the power) until u see the recovery.
ROM: it's a file containing usually the kernel, the system with main applications (excluded google apps), some scripts (commands) to cancel datas before installing.
GOOGLE APPS: you have to flash them after flashed the rom (if the rom asking explicitly for them because made without (it means it doesn't contain inside any google apps that may be crucial for booting), or.. you have to flash them if you're targeting the final result (the last flash) and you want have apps updated in your "new flashed phone". It's not necessary when u're in process of root phone/unlocking.
FLASH A BOOT IMAGE/package: it's a file used to replace the bootloader, when it's needed, for example if you are upgrading from Lollipop to Marshmellow the bootloader can't stay in lollipop version, the versions should match, be sure to have both compatible already downloaded.
ROOT: it means gain the administrators privileges to edit system files on phone.
TWRP: it's a smart console to manage the phone with full control, allows to change the Android versions and many other things.
RECCOMENDATIONS:
1) have battery on phone around 100%, looks because it seems that at lower values make the phone react sometime unexpectly (power safe) during operations, that means you may loose after a lot time to figure out what problem occured/process skipped.
2) During the flashing, in download mode, the phone may not be charged from USB, and the PC power is much less powerful then the charger, you may see a quite impressive battery draining even when connected to PC, this is why is better to start near 100%.
3) During update, the USB up/downs may use lot of CPU of your PC due to driver recognition, keep then your Windows "clean" for the process, no apps in backgroud which use lot of RAM and CPU (for example browsers with many tabs opened), so the driver detection could be faster, avoid programming interruptions (for example installing apps in root.bat)
NOTICE: any time u'll use Odin you don't need to change its flags/settings (for example auto reboot), leave them as they are. If you uploaded something wrong/not certifed under download mode and the phone refuses that, you need to switch off the phone and restart in download mode again, it's not up to software Odin in your PC; you can leave it opened.
Odin will check the checksum of files that are loaded, so for big rom files you have to be patient and give it time to read all file.
When Odin is open and USB connected, you have to see the phone connected by COM, if it doesn't connect the phone may be bricked or you have to install the latest Samsung drivers (!! **you can't forget installing them if it's the first time using a Samsung device!!)
HOW IT WORKS:
useful to understand how is reached the goal here to prevent bricks, solve easier problems, find yourself an overcome. This root kit targets to install 3 applications on the phone, then use a temporary "bricked" kernel to allow edit system files and root the phone before it loads all Android, then restore the previous kernel working, and it ends by using applications installed before to install Safestrap into boot, to have a TWRP console even if the phone is locked.
As the Safestrap substitute the normal Android boot, if there is any problem on the process (=Safestrap will not boot when it's supposed to boot = you started it from its application) the phone may brick here, because when Safestrap stars it need to restore Android normal usage: if it will hapen the Android won't load again, the phone is bricked, read in that section how to solve it.
The first application, Kingoroot,it's made for allow the root permission into other two applications, it's a supervisor. If you use it gently and its installation succeded ok in the beginning of root.bat it will be enough for do all the job (even if the main Guide author suggest to buy SuperSUme).
Busybox it's a software that allows Safestrap to install, whothout it Safestrap won't work.
Safestrap it's a simple application, that if used in right way (I failed lot of times, but I always recovered my phone) permits to have a powerful console on next reboot.
IMPORTANT:
Whne in process, wait always that the USB drivers finishing detecting phone and become "stable" (CPU and hard disk aren't working, keep check them to be sure, as well the icon of the phone should appear in Windows resouces). You may need to start from zero if u miss this, a really stupid reason to lose time.
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
PROCEDURE:
1) Open OK3_ROOT_V5.exe in one folder, if you use windows with particular language and not latin chars avoid to extract it on desktop, prefer a path like C:\galaxy for example.
2) Switch off phone, remove SIM card and SD, switch on in recovery mode and wipe data system and cache, then boot to bootloader
2) open Odin, open under AP G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 and wait until it finished read file, connect phone USB, be sure phone is recognized, start flashing. Wait until phone boots, wait until it shows the beginning screen.
3) choose english, then wi fi button down, then skip the connetcion and everything else asked, insert any fake name.
4) When setup ends don't activate Wi fi, go to settings, about, press 8 times build number, get the development menu active, go into it and enable usb debug, wait for popup and allow your PC always, then disable the verify usb application installation in the same menu. The driver may set itself again after this, wait some seconds befor go over and be sure the phone is seen by Windows resources, when you see the icon of the phone on Windows file explorer and the CPU is low again it's time to run root.bat, not before! Go into OK3_ROOT folder, run root.bat, a black old DOS window will open (this is not Odin! Not confuse this window and what you read there with Odin messages, please!) and follow the steps you read in this new DOS window..
it will install apps, reboot in download mode and show you a new Odin window, select NK2_kernel.tar and flash it, now put your eyes over DOS window of root.bat, it should recognize your firmware and after some seconds display a full page of ########, if it doesn't something went wrong, you need to go to recovery console, wipe everything, and flash again the main big flash (=start from zero).
If succeed, and you will read it in the DOS window, as the last step, you have to disconnect USB, pull battery, switch phone on in download mode and flash VZW_BOK3_KERNEL_ONLY.tar with Odin
5) After reboot open KingRoot application already installed, Click The Up Arrows a couple of time until you get to Try It and yes click Try It, then on the main circle, go back with arrow and you will have confirm that is rooted. Close Kingroot, open busybox free app, allow the root access, click on install (even if it start scannig) and wait some seconds, when it say it completed close it. Open Safestrap, allow root, click on install, the app will quit itself, open it again and click on install, it will quit again. Now reboot phone by the power key, hen rebooted open again Safestrap and now you'll be finally ready to click on the button "Reboot to recovery". Before doing it be ready to organize the next step, like files for unlocking bootloader or flashing a locked phone to 6.0.1.
END rooting phone procedure.
BRICK/RECOVERY: if it happens during root, before you upload any other ROM, there may be three ways to solve that:
Pull the battery out (it's almost safe) and:
1) Light: go under download mode and flash VZW_BOK3_KERNEL_ONLY.tar, see if the phones later boot up normally.
Chances are, with "dirty" chache data that lead the phone to brick, you can't start the root.bat procedure again succesfully (use root2.bat to avoid the install of the three applications that supposed already installed). Then you may try to:
2) medium: go under recovery console, wipe data and cache, boot fom there to download mode and flash again VZW_BOK3_KERNEL_ONLY.tar.
Or, if still not successful:
3) Strong: go under recovery console, wipe data and cache, boot fom there to download mode and flash flash full G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 (that means start from zero)
SAFESTRAP WORLD:
WARNING: you should follow at the letter the above process above, any difference may result in a fail of Safestrap recovery to open and phone bricked at samsung logo (+custom). If so don't worry, you have just to start the download mode and flash VZW_BPB1_KERNEL_ONLY.tar.md5 again to see the phone working. But chances you probably now have to repeat all the procedure from zero because your phone is "dirty" and Safestrap won't work more, proceed to what I called "strong" reflashing in brick section.
NOTICE: when you reboot to Safestrap, after Samsung logo, you need to wait 5-10 seconds to see Safestrap.
FLASH FIRE METHOD:
You may prefer to use FF (Flash Fire) to flash your room, it is a app (apk) that needs t be installed on phone when the phone works in normal mode, it allows you to create a list of different "orders" to execute exactly one after the other after you give it the final "ok". The app reboot the phone and starting itself to flash. It may be faster then Safestrap, but when I tried once it didn't work for me, it flashed partially and rebooted before it finished, I had a soft brick and I should restart from zero. Probably it was me pretending to flash something wrong, there is only one way to upload 6.0.1 on a CID11 phone and I did only once with Safestrap.
For dealing with FF you need the phone rooted, after you followed the process above you don't need to install Busybox, neither Safestrap, but you need to find and install SuperSUme.apk, which is another "root manager" program as Kingoroot is, but FF doesn't work with Kingoroot.
After loading kingoroot copy the Flashfire apk and SuperSUme in your phone, install both of them, start first SuperSUme, allow the root, and let it remove Kingoroot in its procedure, when it finished launch FF and let him the root as well.
You need to find these two apk, google them, since SUperSUme is available only paying you should know what you are doing. I used these versons and they worked: supersume-6.0.apk, flashfire-0-50-android-apk-download (notice there is 0.52, but I tested 0.50)
PS: if you feel this useful, please thank me pressing the button
For uploading 6.0.1 to my locked phone I folowed this guide:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I would just add that having the SD card "not recognized" I simply copied files of ROM and GAPPS into the phone folder accessed by Windows resources. And when I reboot to Safestrap I flashed as last step the GAPPS, nothing more to add.
When you wipe Data you actually don't delete the /sdcard folder, so the ROM files are safe there.
if you accidentally delete files under safestrap you can upload them by adb, but it will be really slow (around 500KB/s), here is the command: adb push /path/to/local/filename.zip /sdcard/filename.zip
You may evaluate to flash also this before GAPPS:
Tethering_Fix_Knox_Removal_Slight_Debloat_V2.zip to remove Knox and useless apps from this ROM
If you need to put your default system language (the ROM is in english) download from google MoreLocale 2, open a DOS windows with the path to the folder of root.bat, activate the developer menu (point N°4 of post above), connect the USB, and type
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
Do you know any details about the new pf4 modem?
no, Im not that expert, here is just a guide to help people into the process..
thank you for the great guide. I was able to root my phone with the clear instruction.
However, I am running into one trouble.
When my phone is setting up the language and etc, it requires me to insert sim or wifi. I can't skip that step without doing one or the other. When I do turn on the wifi, the phone then upgrades itself to android 5.0 but the root is still there. I am using T-mobile sim card.
Is there a way to get around the check up? I made sure to follow all the steps correctly too.
if u're talking about the first beginning steps, after the first big ROM loaded, yes you can skip. Select wi fi button, but after skip all the rest. I've never had to connect to internet or inserted a sim card for the process.
I connected/inserted sim only after the flash to desidered rom
thewebsiteisdown said:
Do you know any details about the new pf4 modem?
Click to expand...
Click to collapse
What kind of details did you want to know? Mine works fine.
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Bryanx86 said:
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Click to expand...
Click to collapse
I added the FF guide
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
nachoalt said:
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
Click to expand...
Click to collapse
you didn't read well the first post. Read it back.
Barabba11 said:
INTRODUCTION (don't skip it if you want understand what you are reading)
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Seems like the file name for OK3_ROOT_V5.exe changed. They call it GS5_LOLLIROOT.tar.gz now (must unzip twice to get all the files) but I looks like what is needed is in this zipped file.
Might take the plunge tomorrow so wish me luck, and thanks again for the explanation!
By "run root.bat" in point 4 do you mean "3 - Root Process.bat"?
Thanks for clarifications
Barabba11,
Since you seems to have a genuine desire of helping people, (and because I want to have my phone rooted), I want to comment your instructions and also try to find what I did wrong, since my phone is locked in the black “Samsung Galaxy S5” screen when trying to accomplish step 4 (no worries, I have been there before…).
Here I go…
FILES YOU NEED
Samsung Drivers: No comments here, straight forward thing to accomplish.
From the original post Here, under “Installing PB1”:
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
{
"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"
}
From the same previously mentioned post, now under “Rooting Instructions”:
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
Then, under “crc” folder you will find:
And finally, “System” folder is empty.
At this stage my series of comments:
1. I don’t see anything called OK3_ROOT_V5.exe mentioned in step 4 of your procedure. I assume you’re referring to the zipped file GS5_LOLLIROOT_BLACKCAT.7z but since almost every suggestion here indicates to read thoroughly, I don’t want to miss any detail. Can you please confirm if what you call OK3_ROOT folder is the unzipped GS5_LOLLIROOT_BLACKCAT.7z?
2. I don’t see anything called root.bat in the unzipped folders above, mentioned in the same step 4. Can you confirm which one of the .bat files are you referring to? Is it 1 - Install APK's.bat, 2 - Flash NK2.bat, 3 - Root Process.bat or 4 - Flash PB1.bat?
Since my phone got stuck in the black screen when reaching this point and I had to get back to square 1, I’ll wait for comments.
Warmest regards, it is really appreciated what you do here, it is just my humble opinion that detailed instructions in plain English, with proper file names, punctuation etc, would save this world a lot of time and frustration, leaving you developers more time to deal with the important stuff, I’ll be happy to help rewriting or reviewing anything in this regard.
PD: Not sure if the images are going to appear, I don't see them in the preview. If that's the case, you can check here
This thread is out of date since the rooting method has entirely been changed
Can you please indicate where can I find the updated method? Rgds
I'm sorry for the inconvenience, since they changed the main files I'm disoriented too. If they removed the bat files it means everything is different now, and honestly I'm hearing now about that..
Would know too why they changed the process, it was working, complicated but working, and I still have my phone at unrooted Android 6 waiting for a major update, like root or Android7.. I don't have enough time to experiment something that may appear useless for me later.
Anyway reading the instructions may warn you about different aspects to consider.. and reduce the waste of time if some conditions happened.
Kindly write in this thread they way you proceed and I'll have care to edit the first post reminding it. Thank you
Great thread, need some help still
How do I check my chipset when I don't have root access? I downloaded xplore but I need root access to check the root folder.
go into the xplore settings and change the root inside, I've no-rooted phone and I can see it. In the beginning, it's just a way for them to push you install rooting apps
If I root my S5 900V using this method can I then reflash it with 4.4.2?

[Rom][Rooted_ALL_Carriers_Nougat_S8+BRB1_SafeStrap][SamFail][V5 Bootloaders]

My method is a little different than the actual SamFAIL method so please to tell me it says this in their thread. I feel my procedure is the best method for the S8+ and this method may not work on the other models so please follow there own set of directions. This method allows you to obtain root by simply flashing a modified system.img using only odin. These images include all carrier files and will work on all carriers. These roms should be stable and you can probably just use these as your daily rom. ​
What Is Safestrap
Safestrap is a Bootstrap / Recovery for locked bootloader phones. Safestrap is now based on TWRP Recovery (a touch based recovery) and you can perform .zip installs, backups and restores here.
{
"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"
}
Downloads V5 Bootloaders SamFail Method For Installation Using Odin
G955USQS5BRB1_ODIN_SAMFAIL_V5_Bootloader.7z Samsung Rom
G955USQS5BRB1_GOOGLE_ODIN_SAMFAIL_V5_Bootloader.7z Googgle Apps Rom
Directions Samfail Method Or If Coming From Stock Unrooted/Rooted Phone
This may wipe your phone
Unzip An Use Files From G955USQS5BRB1_ODIN_SAMFAIL_V5_Bootloader.7z Or G955USQS5BRB1_GOOGLE_ODIN_SAMFAIL_V5_Bootloader.7z
Reboot phone to download mode
Use the Odin3_v3.13 provide above or in above zips
1. In odin select BL_V5_PART_1_AND_3.tar.md5 and load in BL slot of odin do not change the options make sure Auto Reboot and F.Reset Time are checked Click Start
2. Phone will automatically reboot as soon as phone powers off hold buttons to reboot back to download
3. In odin make sure to click reset button then in AP slot in odin choose AP_SYSTEM_IMAGE_PART_2.tar.md5 make sure Auto Reboot and F.Reset Time are checked Click Start
4. When don flashing it will say fail in odin and phone will reboot. Reboot phone to download. If phone reboots to upload mode force it to reboot too download mode
5. In odin make sure to click reset button then in BL slot in odin choose BL_V5_PART_1_AND_3.tar.md5 make sure Auto Reboot and F.Reset Time are checked Click Start
6. When done flashing phone will reboot. If phone gets stuck on boot animation for more than 10 minutes force reboot to recovery and wipe cache if this dont work then you will have to wipe data
Downloads V5 Bootloaders Safestrap Method For Installation Using System Image Via Safestrap
G955USQS5BRB1_SAMSUNG_SAFESTRAP_SYS_IMAGE.7z Samsung Rom
G955USQS5BRB1_GOOGLE_SAFESTRAP_SYS_IMAGE.7z Google Apps Rom
Directions Safestrap Method Or If Coming From Rom That Already Has Safestrap Installed
This may wipe your phone
Unzip An Use Files From G955USQS5BRB1_GOOGLE_SAFESTRAP_SYS_IMAGE.7z Or G955USQS5BRB1_SAMSUNG_SAFESTRAP_SYS_IMAGE.7z
Copy System.img To Phone
Reboot Phone To Safestrap
1. In Safestrap choose install select install image and select System.img you copied to phone and flash to system
2. When finished reboot phone to bootloader
3. In BL slot in odin flash BL_V5_PART_1_AND_3.tar.md5
Older Downloads Version 2 Bootloaders
G955USQS2BQL1_ROOTED_ODEX_ODIN_FIRMWARE.zip
Odin3_v3.13.zip
Features
Pre Rooted With Latest SuperSu
SafeStrap Preinstalled
Patched Flashfire No More Having Too Set The Date Back
Xposed Framework Install
Wifi Passwords And Bluetooth Pairings Fixed
Wifi Hotspot Tethering Enable
Work on V5 Bootloaders
This thread is simply to get you rooted with a working rom.
This thread is not a rom request or features request.
If you dont like the rom that this method installs then install whatever you want.
Yes the 80 percent battery bug is still present in this method.
The screen gets a funny tint every once in awhile simple turn screen off and back on. This is not roms fault it is Eng Combo Firmware.
Sometimes FlashFire fails to achieve root or gets stuck acquiring root. A reboot usually fixes it sometimes it takes a couple reboots.
Kernel panics happen and will cause your phone to reboot to upload mode. If this happens simple hold the keys to reboot to download mode then from there reboot phone.
This is system root so safetynet apps will not work nor will samsung apps like Pay, Secure Folder, Pass. There is no work around
All Credit Goes To The SamFAIL Team their original thread can be found here
Any donations should directed to them​First and foremost, SHOUTOUTS!
- @partcyborg for finding the root method!
- @me2151 for testing on Note 8 and facilitating root on the Note 8!
- @elliwigy for being great help and original S8 root
- @Bsober for... Always testing my stuff
- @LiquidT for testing
- @Chainfire For opening the door to make this root useful. He will be missed! (no he is not dead, just retired.)
- @samsung for the amazing phone and leaving rediculous loopholes open for us to root!
Click to expand...
Click to collapse
How To Get SnapChat Working​Disable Xposed by toggling off in the Xposed installer reboot
Click on SuperSu app and goto settings and Uncheck Enable superuser
Now Install SnapChat and login
Now open SuperSu app it will say something su binary occupied just click on settings click on Check Enable superuser
Now it will say it was unsuccessful to reboot just ignore click on settings go to cleanup and click Reinstall
Now copy View attachment Superuser.apk to your phone install
Open Supersu app let it updated SU Binary choose normal
If All this fails or you want to skip these steps then just download latested SuperSU Systemode zip and install in safestrap
Create your own system.img.ext4 odin flashable image​
If you want to make a odin flashable system.img of your phones system image
Download
S8_Backup_System_Image.zip
MD5_TAR_TOOL.zip
FSTRIM Apk
Directions
Copy S8_Backup_System_Image.zip to phone
Unzip MD5_TAR_TOOL.zip on your computer
Install FSTRIM Apk on your phone
Run Fstrim and select system to trim
Once system trimmed use flashfire choose add zip and choose S8_Backup_System_Image.zip DO NOT MOUNT system when it ask
Click flash
This will take several minutes when phone reboots you should have a folder on your internal storage named System_Img_Backup and inside should be a system.img.ext4 file around 4.59 gig
Copy the system.img.ext4 file and place it in the MD5_TAR_TOOL. folder on your computer and place it in the Place_Files_Here folder
Run the ImgToTar.MD5.bat inside the MD5_TAR_TOOL. folder on your computer
This process will take 10 to 20 minutes to complete
Once done there will be a folder in the MD5_TAR_TOOL. folder on your computer called AP_SYSTEM_IMG_PART_1 and inside that folder will be a AP_SYSTEM_IMG_PART_1.tar.md5 which will contain your system.img from your phone
Just replace the Above AP..._PART_1 file with your newly created AP_SYSTEM_IMG_PART_1.tar.md5 and follow procedure in port 1 and now you can flash your system.img in odin its good if you bootloop your phone with a mod or something
I will try this tonight thanks for the guide
Update: I Just Tried It with the provided odex FW, Its Working For me On
S8+ Att Varriant
Mark805 said:
I will try this tonight thanks for the guide
Update: I Just Tried It with the provided odex FW, Its Working For me On
S8+ Att Varriant
Click to expand...
Click to collapse
I have confirmation from of course Verizon T-Mobile and Now AT&T. Just need someone from Sprint to try it. Does your volte, wifcalling , etc work ok on AT&T?
im allredy rooted can i flash with flashfire and can you make a full stock google rom flashable with flash fire im willing to test
robert ballard said:
im allredy rooted can i flash with flashfire and can you make a full stock google rom flashable with flash fire im willing to test
Click to expand...
Click to collapse
Since you didnt read the OP I will help you out on your request by posting what the OP says
jrkruse said:
This thread is simply to get you rooted with a working rom.
This thread is not a rom request or features request.
If you dont like the rom that this method installs then install whatever you want.
Yes the 80 percent battery bug is still present in this method.
The screen gets a funny tint every once in awhile simple turn screen off and back on. This is not roms fault it is Eng Combo Firmware.
Sometimes FlashFire fails to achieve root or gets stuck acquiring root. A reboot usually fixes it sometimes it takes a couple reboots.
Kernel panics happen and will cause your phone to reboot to upload mode. If this happens simple hold the keys to reboot to download mode then from there reboot phone.
This is system root so safetynet apps will not work nor will samsung apps like Pay, Secure Folder, Pass. There is no work around
Click to expand...
Click to collapse
check out my other threads I have what your asking for
Hey i have this fw with baseband l6
service provider used to say Xax/att/att but i got a security warning
from the device maintenance security window i clicked resolve now and it reset my phone it went to recovery for a brief moment I thought I was going to get a boot loop but it started up and my service provider is att/att/att now nd it booted with all the att bloat also i had knox dissabled thru the build prop but now it says 2.8. Did i get a ota or what happened?
Originally my phone is s8+ att unlocked
Mark805 said:
Hey i have this fw with baseband l6 modem used to say
Xxa/att/att but i got a security warning from the device maintenance security window i clicked resolve now and it reset my phone it went to recovery for a brief moment I thought I was going to get a boot loop but it started up and my modem is att/att/att and it booted with all the bloat
And knox says 2.8
Did i get a ota or what happened
Originally my phone is s8+ att unlocked
Click to expand...
Click to collapse
Wouldn't you want it that way. WiFi calling and all that volte won't work if your phone is XAA. Your rooted delete your bloat
jrkruse said:
Wouldn't you want it that way. WiFi calling and all that volte won't work if your phone is XAA. Your rooted delete your bloat
Click to expand...
Click to collapse
Yeah just found it to be wierd i went into the tri dump menu and im able to disable low battery dump i dont think i was able to in the other firmware
I just wanted confirmation that it's nothing wierd happening before I re flash my phone
Mark805 said:
I just wanted confirmation that it's nothing wierd happening before I re flash my phone
Click to expand...
Click to collapse
I have not heard of this happening later on your csc code is usually set on install. You can always change your csc back if you want
I tried this root method again, still SD issues
Hell-Razor said:
I tried this root method again, still SD issues
Click to expand...
Click to collapse
Your not trying to use encrypted storage are you? Other than that dont know what to tell you I have no problems with my 128 gig sd card
So i been running same fw no issues after the csc reset maybe I triggered it by going thru settings disabling apps
jrkruse said:
Your not trying to use encrypted storage are you? Other than that dont know what to tell you I have no problems with my 128 gig sd card
Click to expand...
Click to collapse
No. No encryption. I just wanted to state I'm not saying I don't appreciate your rom still please don't take it that way.
If your 128 works, can you link me which one you're using? I'll snag it off Amazon quick
Hell-Razor said:
No. No encryption. I just wanted to state I'm not saying I don't appreciate your rom still please don't take it that way.
If your 128 works, can you link me which one you're using? I'll snag it off Amazon quick
Click to expand...
Click to collapse
So what does it do? Reboot to upload mode when you insert It? Or just not read it?
jrkruse said:
So what does it do? Reboot to upload mode when you insert It? Or just not read it?
Click to expand...
Click to collapse
The phone will randomly read it. Like I can play a song for a minute or 30 seconds then it stops and I get the symbol at the top that says an SD card was inserted. The same when I'm trying to pull stuff off of or put stuff on... It will work for a little bit then unmount itself and remount. I saw that Google play may have something to do with it (other forums) but I've been trying to run traces on it to see and so far I don't see any error messages.
Hell-Razor said:
The phone will randomly read it. Like I can play a song for a minute or 30 seconds then it stops and I get the symbol at the top that says an SD card was inserted. The same when I'm trying to pull stuff off of or put stuff on... It will work for a little bit then unmount itself and remount. I saw that Google play may have something to do with it (other forums) but I've been trying to run traces on it to see and so far I don't see any error messages.
Click to expand...
Click to collapse
Have you tried reformatting it?
jrkruse said:
Have you tried reformatting it?
Click to expand...
Click to collapse
Yes. And checking it for errors and formatting it on other phones and formatting it on my computer. Everything else except this phone seems to accept it.
Hell-Razor said:
Yes. And checking it for errors and formatting it on other phones and formatting it on my computer. Everything else except this phone seems to accept it.
Click to expand...
Click to collapse
Try flashing some different combo firmware I have some listed in my rom thread

Help with Securitynet and play protect

I am unable to download some apps, especially banking apps due to CTS profile and basic integrity failing securitynet...also, my device (oneplus 6) is showing the Google play protect certificate is invalid.
I have never rooted my device or installed Magisk (or any other rooting software) ... the max I had done was open the Developer Options (and hardly used any). I dont know how to go about this without having to do a hard factory reset... even then, I am not sure if the required apps will function on the phone.
Any help with this will be much appreciated.
{
"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"
}
SafetyNet appears to fail on some bootloader-unlocked devices, even if the device has not been modified in any other way. Your phone seems to be one of these.
jwoegerbauer said:
SafetyNet appears to fail on some bootloader-unlocked devices, even if the device has not been modified in any other way. Your phone seems to be one of these.
Click to expand...
Click to collapse
Thanks for the reply..but how do I work around this? Do I have to do a factory reset or get a new phone?
There is a solution but you are gonna need magisk manager and framework installed. If you already have it then skip this step, if you don't say it here I'll help
1) What model is your phone?
gabtit7 said:
There is a solution but you are gonna need magisk manager and framework installed. If you already have it then skip this step, if you don't say it here I'll help
1) What model is your phone?
Click to expand...
Click to collapse
No I dont have magisk manager and framework installed.
Phone model is - Oneplus 6 (A6003), with the latest OS version 10.3.7
Tell me your android version before getting started
for failing the safetynet test i will suppose you have twrp install as recovery, if you dont go here
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
then from your mobile phone go here
How to Install and Download Magisk Manager APK v26.1 [Guide]
Download Magisk Manager APK Latest Version and How to Install Magisk 24 via TWRP to Root, use Magisk Hide and Uninstall Magisk Complete Guide in 2023
magiskroot.net
and download the magisk manager, you need to have unknown sources enabled
On the top of the screen you will see info about magisk manager and the framework
install the framework
FROM NOW ON YOU CONTINUE ON YOUR OWN RISK, THERE IS A CHANCE YOUR PHONE GETS BRICKED
even if it does get bricked contact me here i'll still try to help
Now here is the weird part
once you click the install button it will prompt you with some options
1) disable the "Recovery Mode" option
2) select direct install (if possible), else select download zip file only
if you selected direct install then you should ust reboot and the magisk part is ready
If you selected the "only zip file" option:
1) check the "Downloads" folder in your file manager and you should find a magisk21.x.zip file
2) boot in twrp
3) after you enter password go from main menu to install
4) navigate to the folder with the zip
5) select the zip and disable the "Zip signature verification" option and swipe the bar on the bottom. Just let the process finish and reboot
2 options at this part
1) your phone booted up normally
2) your phone got bricked
I'll continue to help but tell me how did it go till this part to get around any problems occured till now
gabtit7 said:
Tell me your android version before getting started
for failing the safetynet test i will suppose you have twrp install as recovery, if you dont go here
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
then from your mobile phone go here
How to Install and Download Magisk Manager APK v26.1 [Guide]
Download Magisk Manager APK Latest Version and How to Install Magisk 24 via TWRP to Root, use Magisk Hide and Uninstall Magisk Complete Guide in 2023
magiskroot.net
and download the magisk manager, you need to have unknown sources enabled
On the top of the screen you will see info about magisk manager and the framework
install the framework
FROM NOW ON YOU CONTINUE ON YOUR OWN RISK, THERE IS A CHANCE YOUR PHONE GETS BRICKED
even if it does get bricked contact me here i'll still try to help
Now here is the weird part
once you click the install button it will prompt you with some options
1) disable the "Recovery Mode" option
2) select direct install (if possible), else select download zip file only
if you selected direct install then you should ust reboot and the magisk part is ready
If you selected the "only zip file" option:
1) check the "Downloads" folder in your file manager and you should find a magisk21.x.zip file
2) boot in twrp
3) after you enter password go from main menu to install
4) navigate to the folder with the zip
5) select the zip and disable the "Zip signature verification" option and swipe the bar on the bottom. Just let the process finish and reboot
2 options at this part
1) your phone booted up normally
2) your phone got bricked
I'll continue to help but tell me how did it go till this part to get around any problems occured till now
Click to expand...
Click to collapse
Is it safe to install TWRP to backup all apps, docs, pics and videos?
shahz19 said:
Is it safe to install TWRP to backup all apps, docs, pics and videos?
Click to expand...
Click to collapse
Android version is 10
gabtit7 said:
Tell me your android version before getting started
for failing the safetynet test i will suppose you have twrp install as recovery, if you dont go here
How to install TWRP recovery on Android smartphones
Installing TWRP on an Android device is the first step towards custom development.
www.xda-developers.com
then from your mobile phone go here
How to Install and Download Magisk Manager APK v26.1 [Guide]
Download Magisk Manager APK Latest Version and How to Install Magisk 24 via TWRP to Root, use Magisk Hide and Uninstall Magisk Complete Guide in 2023
magiskroot.net
and download the magisk manager, you need to have unknown sources enabled
On the top of the screen you will see info about magisk manager and the framework
install the framework
FROM NOW ON YOU CONTINUE ON YOUR OWN RISK, THERE IS A CHANCE YOUR PHONE GETS BRICKED
even if it does get bricked contact me here i'll still try to help
Now here is the weird part
once you click the install button it will prompt you with some options
1) disable the "Recovery Mode" option
2) select direct install (if possible), else select download zip file only
if you selected direct install then you should ust reboot and the magisk part is ready
If you selected the "only zip file" option:
1) check the "Downloads" folder in your file manager and you should find a magisk21.x.zip file
2) boot in twrp
3) after you enter password go from main menu to install
4) navigate to the folder with the zip
5) select the zip and disable the "Zip signature verification" option and swipe the bar on the bottom. Just let the process finish and reboot
2 options at this part
1) your phone booted up normally
2) your phone got bricked
I'll continue to help but tell me how did it go till this part to get around any problems occured till now
Click to expand...
Click to collapse
Android version is 10
shahz19 said:
Android version is 10
Click to expand...
Click to collapse
For backing up you could use twrp but if rooted i recommend migrate-GPE
2) android version is ok you can do the steps i wrote on the first reply
gabtit7 said:
For backing up you could use twrp but if rooted i recommend migrate-GPE
2) android version is ok you can do the steps i wrote on the first reply
Click to expand...
Click to collapse
Is all of this safe? I dont want to brick my phone as i use it quite extensively for work... dont have the money to spend on a new phone...
google play works on my phone, i can access my gmail accounts, but my device shows as uncertified... I have even registered by device ID on Google
If you use your phone a lot, especially for business, i recommend to back off and dont root with magisk (thats what magisk does)
btw rooting is the only way to bypass the safetynet
The only reason im telling you to not continue is because i dont know much about the phone's model
I have a Xiaomi Redmi Note 8, the older versions of magiks bricked it (v20), now (v21) there is no problem
Also, i saw on the safetynet test you failed both ctsprofile and basicIntegrity, which i dont know if the solution i told would fix it
A Much easier solution is to search around these forums
OnePlus 6
OnePlus has consistently made the fastest phones on the market. They continue that trend with the OnePlus 6. The OnePlus 6 has a 6.28" display with a 1080x2280p resolution. The Snapdragon 845 chipset is paired with 6/8GB of RAM and 64/128GB of storage. The main camera is 16+20MP and the selfie...
forum.xda-developers.com
and either find a thread to help you or create one
somebidy will Definitely help you as they use the same phone model
Sorry for any inconvenience
shahz19 said:
google play works on my phone, i can access my gmail accounts, but my device shows as uncertified... I have even registered by device ID on Google
Click to expand...
Click to collapse
About this go to google playstore and search for netflix, you will not find it
gabtit7 said:
If you use your phone a lot, especially for business, i recommend to back off and dont root with magisk (thats what magisk does)
btw rooting is the only way to bypass the safetynet
The only reason im telling you to not continue is because i dont know much about the phone's model
I have a Xiaomi Redmi Note 8, the older versions of magiks bricked it (v20), now (v21) there is no problem
Also, i saw on the safetynet test you failed both ctsprofile and basicIntegrity, which i dont know if the solution i told would fix it
A Much easier solution is to search around these forums
OnePlus 6
OnePlus has consistently made the fastest phones on the market. They continue that trend with the OnePlus 6. The OnePlus 6 has a 6.28" display with a 1080x2280p resolution. The Snapdragon 845 chipset is paired with 6/8GB of RAM and 64/128GB of storage. The main camera is 16+20MP and the selfie...
forum.xda-developers.com
and either find a thread to help you or create one
somebidy will Definitely help you as they use the same phone model
Sorry for any inconvenience
Click to expand...
Click to collapse
thanks... will do
gabtit7 said:
About this go to google playstore and search for netflix, you will not find it
Click to expand...
Click to collapse
you are right..its not there...luckily, I have Netflix installed from before but am not updating it for fear it may not work after updating it.
So how do i go about certifying my device even after registering it with Google?
@shahz19
STOP LISTENING TO @gabtit7
IT'S ABSOLUTE NONSENSE WHAT HE/SHE TELLS YOU HERE / SEDUCES YOU TO DO: IT'S A VERY OUTDATED KNOWLEDGE HE/SHE HAS FROM THE STATE OF THINGS.
THE SAFETYNET API NOW NO LONGER QUERIES CTS PROFILE ON ANDROID DEVICE BUT SUCH ONE STORED ON GOOGLE SERVERS: MAGISK CAN'T PREVENT THIS. THE DEVELOPER OF MAGISK HAS ALREADY ADMITTED THAT! THE CAT-AND-MOUSE GAME HAS ENDED!
Nah, this still works
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Release v1.1.1 · kdrag0n/safetynet-fix
Changes Removed security patch fixup to fix CTS profile mismatches on some devices Some devices will now need to use MagiskHide Props Config in addition to this module in order to pass CTS profil...
github.com
As long as they don't remove the fall back to basic check
shahz19 said:
Thanks for the reply..but how do I work around this? Do I have to do a factory reset or get a new phone?
Click to expand...
Click to collapse
If you are rooted via Magisk even if you do factory reset you will fail SafetyNet Test ...
Try downloading Magisk Module or Xposed Module that "fix" SafetyNet
Hi. I have the same phone and exectly the same issue. Any fix?

How to root a system without knowing a bit about rooting? Plz Help

Respected Forum Members and Readers,
I am an Android Rooting Enthusiast and I am totally new to this realm of hacking into the device and gaining its full access. I have just known about it through videos on youtube and have myself tried to root my device Samsung Galaxy J7 Pro by following videos not knowing really how the things work in actual and ended up losing original firmware. But since then I have been trying to find how to actually root a system by even reading the Book on Hacking by XDA Developers written by Jason Tyler. I have somewhat came to know the internal working but I am also a bit afraid as to try again to root my device as i really don't know how to do it till now and this time i can really not lose my device. But i still want to gain access of it and explore the infinite advantages of having a rooted device. Plz if anybody can help me walk my way through it.
Rooting a device's Android simply means to add "superuser" ( AKA root ) functionality to Android OS, will say add an Android user with elevated rights ( comparable to Administrator in Windows OS).
Because your phone runs Android 7 ( Nougat ) IMO the most easiest method to root your device's Android: Replace Android's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5.
jwoegerbauer said:
Rooting a device's Android simply means to add "superuser" ( AKA root ) functionality to Android OS, will say add an Android user with elevated rights ( comparable to Administrator in Windows OS).
Because your phone runs Android 7 ( Nougat ) IMO the most easiest method to root your device's Android: Replace Android's Toybox binary - what is a restricted version by default - by unrestricted Toybox v0.8.5.
Click to expand...
Click to collapse
Thank You So Much for your reply but I am sorry as i might have said i just do not know anything about these technical terms like IMO and how to replace Android's Toybox Binary..., i would be really grateful if you could help me by elaborating a bit more as to what I have to exactly do.. Thank You Again
Arihant0908 said:
Respected Forum Members and Readers,
I am an Android Rooting Enthusiast and I am totally new to this realm of hacking into the device and gaining its full access. I have just known about it through videos on youtube and have myself tried to root my device Samsung Galaxy J7 Pro by following videos not knowing really how the things work in actual and ended up losing original firmware. But since then I have been trying to find how to actually root a system by even reading the Book on Hacking by XDA Developers written by Jason Tyler. I have somewhat came to know the internal working but I am also a bit afraid as to try again to root my device as i really don't know how to do it till now and this time i can really not lose my device. But i still want to gain access of it and explore the infinite advantages of having a rooted device. Plz if anybody can help me walk my way through it.
Click to expand...
Click to collapse
it's very simple, i will try to be less technical but bear with me,
so, rooting is simply gaining access to systems core, by core i mean ability to access, modify and write into system (structure and file).
it is a great responsibility, as a simple stupid move can cause system to crash and may also brick your device.
------------------------------ but, don't worry as we here in XDA are there to help you,
as, the device in question is a Samsung j7 pro, normal rooting methods will not work as Samsung by default make it difficult to root it's phone.
you may refer this article to root your phone click here.
----------------------------- but it's some what technical so, i will explain, what is written there in next post.
so, about what's in the article,
--------------------- first things first, you may cause damage to your device so, just to make sure i will not be responsible for any damage.
let's begin, what i will tell you about?
ODIN (a software by Samsung to flash original firmware {that comes with phone})
TWRP(custom recovery, a tool that is installed (flashed using odin )on phone to flash custom rom)
Some tweaks files like RMM State By-Pass.zip and no-verity-opt-encrypt don't think much about them, they just bypass some restriction set by Samsung so, that rooting is successful. you can flash them through TWRP.
you can get link through the article for all required files so,
Download Samsung driver from here,
install them on your PC
download ODIN from here,
after it, open settings app >> about phone >> software info >> then click build number 5-10 times till you are a developer option appears.
after enabling developer option go to developer option, find it using search bar in settings app, it should be inside about phone section.
inside developer option enable USB debugging and also enable OEM unlock option.
after enabling OEM unlock option -----part 2 below.
this was part one if you got all till now you are good to go,
Connect your USB cable with PC. Switch off your device. Then, enter into Download mode. To do this; press and hold down the Volume Down +Home+ Power buttons and connect your micro USB Cable.
{
"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"
}
Press the Volume Up button to continue when you see the warning message.
Now, connect the Samsung Galaxy J7 Pro mobile to the computer via USB cable.
download and extract odin downloaded earlier.
launch odin by clicking on odin.exe file
After connecting the Samsung device, click on the PDA/PA button to browse/search and get the TWRP from where you saved it on your PC. Also, navigate to “options” and save settings like shown below.​
after all this your phone should reboot automatically, and voila you have successfully flashed twrp on your device.
now power off your phone,
boot into twrp by pressing Volume Up + Home+ Power Button
then, it will boot into twrp.
Select Wipe->Advance Wipe->Select Cache Data
Return to Home of TWRP select Install
Select Magisk.zip (you can download magisk from github of magisk or from here )
slide to install.
same process for RMM State By-Pass.zip and no-verity-opt-encrypt install file one by one.
after all the process you should reboot into system.
then download magisk app and now you have root access, enjoy and like the post if you want.
@[email protected]
Thank You for taking pains to elaborate the process. i just want to ask one question are you sure this method won't brick my device this time. Sorry i am being like that because the phone i have mentioned is my mother's so she would be really pissed if it does not go right. And if my device gets stuck in boot loop rather being bricked can it still be recovered...
Arihant0908 said:
@[email protected]
Thank You for taking pains to elaborate the process. i just want to ask one question are you sure this method won't brick my device this time. Sorry i am being like that because the phone i have mentioned is my mother's so she would be really pissed if it does not go right.
Click to expand...
Click to collapse
don't worry bro if you follow every step properly it will not brick, but to be on safe side backup internal storage and app data before starting to root your moms phone.
and if some thing goes wrong i am here for you, generally speaking phones does not brick during magisk installation.
[email protected] said:
and if some thing goes wrong i am here for you, generally speaking phones does not brick during magisk installation.
Click to expand...
Click to collapse
And do have to download rmm and no verity encrypt files or should i leave them.... and how to download their required versions along with the right twrp version
bro first use odin to flash twrp
then use twrp to flash magisk then rmm then no verity encrypt each after other no reboot.
Arihant0908 said:
And do have to download rmm and no verity encrypt files or should i leave them.... and how to download them
Click to expand...
Click to collapse
download from website
Root Samsung Galaxy J7 Pro SM-J730F/FM/GM Pie 9.0 using TWRP and Magisk
Most of the people thought, When mobile get slow, we can rectify this by rooting. Nope. There are plenty of optimizations available without root. Even
www.androidinfotech.com
One last thing, do I require to download Samsung USB Driver even if ODIN is able to detect my device
Arihant0908 said:
One last thing, do I require to download Samsung USB Driver even if ODIN is able to detect my device
Click to expand...
Click to collapse
no and yes, if twrp flashes properly no
else yes
@Arihant0908
take note that in order to root Android by means of Magisk, as recommended / advised by @[email protected], neither ODIN nor TWRP is needed: flashing TWRP in this case - as a necessary prerequisite - is an absolute overkill.
All you need is to install Magisk Root app.
jwoegerbauer said:
@Arihant0908
take note that in order to root Android by means of Magisk, as recommended / advised by @[email protected], neither ODIN nor TWRP is needed: flashing TWRP in this case - as a necessary prerequisite - is an absolute overkill.
All you need is to install Magisk Root app.
Click to expand...
Click to collapse
take note mr./mrs. @jwoegerbauer
if you know anything about magisk then you should know that it is not a one click root tool, you need to flash magisk for you to gain root access.
next, yes you only need to boot twrp but in case of samsung we need custom recovery to fix errors so it's good to have it flashed. odin helps remove complexity, and is safe to use.
i was trying to provide best stable and tested path and don't interfere if you don't know anything about topic, i humble request not to confuse people @jwoegerbauer
[email protected] said:
take note mr./mrs. @jwoegerbauer
if you know anything about magisk then you should know that it is not a one click root tool, you need to flash magisk for you to gain root access.
next, yes you only need to boot twrp but in case of samsung we need custom recovery to fix errors so it's good to have it flashed. odin helps remove complexity, and is safe to use.
i was trying to provide best stable and tested path and don't interfere if you don't know anything about topic, i humble request not to confuse people @jwoegerbauer
Click to expand...
Click to collapse
Ok so... in the end what i have understood is that:
1. I need to have Magisk.zip, RMM and no verity encrypt files on Phone.
2. I need TWRP, odin and android usb driver by samsung for windows 10 installed on pc.
3. I need to first flash TWRP using odin. Boot up my device
4. Then boot to TWRP, wipe cache, and flash Magisk.zip, RMM and no verity one by one as in one thing at a time using TWRP. Boot up and install magisk app.
If i missed something, disordered anything or have any suggestions then plz reply. Thank You
Arihant0908 said:
Ok so... in the end what i have understood is that:
1. I need to have RMM and no verity encrypt files on Phone.
2. I need TWRP, odin and android usb driver by samsung for windows 10 installed on pc.
3. I need to first flash TWRP using odin. Boot up my device
4. Then boot to TWRP, wipe cache, and flash RMM and no verity. Boot up and install magisk app.
If i missed something, disordered anything or have any suggestions then plz reply. Thank You
Click to expand...
Click to collapse
on 4th point first flash magisk zip file download from
https://github.com/topjohnwu/Magisk (click on code and download)
flash magisk zip through TWRP then RMM and no verity encrypt file
then boot
if magisk app is present after booting then no need to download app else download the app from google
[email protected] said:
on 4th point first flash magisk zip file download from
https://github.com/topjohnwu/Magisk (click on code and download)
flash magisk zip through TWRP then RMM and no verity encrypt file
then boot
if magisk app is present after booting then no need to download app else download the app from google
Click to expand...
Click to collapse
which magisk zip do i have to download... magisk, magisk beta, magisk canary
Moreover i am unable to select right TWRP specific to my device on its official page twrp.me . My device Model Number is SM-J730GM.
jwoegerbauer said:
@Arihant0908
take note that in order to root Android by means of Magisk, as recommended / advised by @[email protected], neither ODIN nor TWRP is needed: flashing TWRP in this case - as a necessary prerequisite - is an absolute overkill.
All you need is to install Magisk Root app.
Click to expand...
Click to collapse
Totally agree with this.

Categories

Resources