IMPORTANT - READ THIS FIRST:
The Note FE comes with dm-verity check and forced encryption enabled. You will need to remove this extra layer of security for root access. To disable dm-verity and forced encryption you must install TWRP recovery first on your Note FE. Note that disabling forced encryption and dm-verity requires a factory reset from TWRP recovery, so you should backup your data (internal storage) before you begin.
The next stage then will be to root the device by flashing the SuperSU zip via TWRP recovery. SU will also ensure that dm-verity and forced encryption remains disabled. Bear in mind, however, that a factory reset will restore them again.
WHAT YOU WILL NEED:
Download Odin and drivers here: https://build.nethunter.com/samsung-tools/
Download TWRP for Note 7 Exynos: there are two versions: Korean and International:
Korean version: https://dl.twrp.me/graceltekor/
International: https://dl.twrp.me/gracelte/
Download the latest version of SuperSu here: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip?retrieve_file=1
You should also download the stock firmware appropriate to your version of Note FE, just in case. Variants S & L can be found on Sammobile, and variant K is available here: https://www.androidfilehost.com/?fid=817550096634784008
ROOTING YOUR NOTE FE:
Read these instructions through carefully before you begin.
(1) Install TWRP Recovery on your Note FE via Odin.
(2) Boot your Note FE into TWRP recovery as follows:
(a) First switch off your device.
(b) Now Press and hold “Home + Power + Volume Up” buttons for a few seconds and as soon as you see your device’s logo on-screen, release the three buttons altogether. Your device will boot into TWRP recovery.
(3) Upon booting into TWRP recovery for the first time, you’ll get a prompt to allow system modifications. You should swipe right to allow this.
(4) On the TWRP main menu, select WIPE then select “Format Data”. You will need to type yes in order to proceed. This will clean wipe the entire internal storage on your Note FE (make sure you have backed-up your important files safe to restore later).
(5) Still in TWRP recovery, you should now connect your Note FE to the PC. (TWRP supports MTP connection so you’ll be able transfer files to the device.) Wait until your Note FE appears on your PC desktop (may take a while first time). You can now transfer the SuperSU zip to your Note FE.
(6) Go back to the TWRP main menu and select “Install” this time. Now you can flash the SuperSU zip.
(7) Reboot your Note FE.
You should now be rooted. Test using an appropriate app.
It would be helpful to others if you reported your experience and the outcome here.
Good luck.
Thanks again for using your device to test this bro!
sent from my Note FE, S8 plus, S7 edge or S6
Thanks alot
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
malaccio said:
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
Click to expand...
Click to collapse
Yeap just did it.
having a problem booting into twrp after the flash, it stuck on the Samsung logo, Home + Power + Volume Up don't get me anywhere.
any idea will it be the TWRP version, my phone is K version, BTW i can flash stock version back with no problem
iraqgsm said:
having a problem booting into twrp after the flash, it stuck on the Samsung logo, Home + Power + Volume Up don't get me anywhere.
any idea will it be the TWRP version, my phone is K version, BTW i can flash stock version back with no problem
Click to expand...
Click to collapse
Are you letting it boot into system then trying to boot into twrp or trying to boot direct to twrp after it flashes?
sent from my Note FE, S8 plus, S7 edge or S6
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
wow N7FE cant use old N7 twrp??
malaccio said:
thank you very much!
to restore original firmware even if knox counter 01 I need to flash the stock firmware using Odin?
Click to expand...
Click to collapse
Yes. Good thing too.
iraqgsm said:
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
Click to expand...
Click to collapse
Still in bootloop?
iraqgsm said:
I did both and still freeze on the logo screen if I attempt to access recovery. I did it like 40 times still doing the same and flashed the stock and redid again and still the same.
OEM unlock on, and USB debugging on and Odin flash showing successful, not sure what am missing, I did it before in other note 7.
Click to expand...
Click to collapse
Two possibilities why it's not working for you:
Try flashing TWRP with USB debugging off.
Are you placing the TWRP file in the right slot (AP) in Odin?
The last one is obvious, but it's strange that TWRP doesn't open for you.
kenpaci said:
wow N7FE cant use old N7 twrp??
Click to expand...
Click to collapse
Well, it works. But there may be minor problems. If we get enough reports we should be able to isolate these and see what can be done to correct them.
These are early days with FE so there will be little personal data on them yet. So this is a good time for some experimentation, especially as flashing stock is known to be successful.
zamzenos said:
Two possibilities why it's not working for you:
Try flashing TWRP with USB debugging off.
Are you placing the TWRP file in the right slot (AP) in Odin?
The last one is obvious, but it's strange that TWRP doesn't open for you.
Click to expand...
Click to collapse
I will try with USB debugging and I did place it in the AP slot
---------- Post added at 07:05 PM ---------- Previous post was at 06:13 PM ----------
still no go with usb bugging off,
a question that is the only twrp version that is working for you now right
iraqgsm said:
I will try with USB debugging and I did place it in the AP slot
---------- Post added at 07:05 PM ---------- Previous post was at 06:13 PM ----------
still no go with usb bugging off,
a question that is the only twrp version that is working for you now right
Click to expand...
Click to collapse
I used "twrp-3.1.1-0-gracelte.img.tar".
Are you formatting data? If you are, try flashing without allowing modifications and without formatting data. You won't be able to make use of TWRP in that mode, but try it and see what happens.
One last try: If the above fails, try entering stock recovery after you flash the stock firmware.
Finally, I have the K variant. It might be that the problem occurs because you have a different variant.
You could get the TWRP app (check the TWRP site). There is a specific version for korean telecoms (graceltekor). I've dloaded it and will give it a try tomorrow. But you should test the above suggestions first.
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
this version of twrp is newer than the one you have on the first post, it worked perfectly thank you
Click to expand...
Click to collapse
iraqgsm said:
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
this version of twrp is newer than the one you have on the first post, it worked perfectly thank you
Click to expand...
Click to collapse
Which version did you use? I've just flashed the korean version myself. No problems. I'm amending the OP to give people a choice.
Glad it worked for you. Hope this will encourage others to take the plunge.
Click to expand...
Click to collapse
zamzenos said:
I used "twrp-3.1.1-0-gracelte.img.tar".
Are you formatting data? If you are, try flashing without allowing modifications and without formatting data. You won't be able to make use of TWRP in that mode, but try it and see what happens.
One last try: If the above fails, try entering stock recovery after you flash the stock firmware.
Finally, I have the K variant. It might be that the problem occurs because you have a different variant.
You could get the TWRP app (check the TWRP site). There is a specific version for korean telecoms (graceltekor). I've dloaded it and will give it a try tomorrow. But you should test the above suggestions first.
Click to expand...
Click to collapse
zamzenos said:
iraqgsm said:
Which version did you use? I've just flashed the korean version myself. No problems. I'm amending the OP to give people a choice.
Glad it worked for you. Hope this will encourage others to take the plunge.
Click to expand...
Click to collapse
the twrp-3.1.1-0-gracelte.img.tar worked.
twrp-3.0.2-1-graceltexx.tar.md5 didnt work
honestly, it was easy thank you
Click to expand...
Click to collapse
iraqgsm said:
zamzenos said:
the twrp-3.1.1-0-gracelte.img.tar worked.
twrp-3.0.2-1-graceltexx.tar.md5 didnt work
honestly, it was easy thank you
Click to expand...
Click to collapse
There's a 3.1.1-0 version of the korean version (graceltekor) too. Use the new link I added to the OP. I've tried both today, now that I have a better idea of what is involved. Both work fine, seems to be no difference between them - I mean, for our purposes.
But it's really good to have full root. Honestly never expected it to be this good.
Click to expand...
Click to collapse
BerndausLB said:
Link is dead.
I have SM-N935K and need the stock firmware please.
Any help (working link) is highly appreciated.
Thank you.
Click to expand...
Click to collapse
Only link I had: http://fixedfirmware.blogspot.ie/2017/07/samsung-galaxy-note-7-fe-sm-n935skl.html.
Try this link (haven't tried this myself): https://www.androidfilehost.com/?fid=817550096634784008
Google for it otherwise. But you may be able to use one of the other variants. There was a discussion here. Not sure of the outcome, though.
Related
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yea go ahead. Its totally safe to root. No issues or bugs faced till now. Follow this thread : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
I have rooted and flashed TWRP v 2.8.0.1. I am hoping someone compiles a working CWM recovery for our device.
mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.
Okay I will, thanks.
Though what's strange is the version number. I went to the official site of TWRP and the version was 2.8.0.0, but on the root thread, the version is 2.8.0.1.
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
marcviado said:
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.
Click to expand...
Click to collapse
Yup current TWRP v2.8 has some issues while flashing KK ROMS and taking too much time to clear cache. The device reboots automatically while taking a TWRP system backup.
We need a CWM recovery ASAP :fingers-crossed:
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
Same here.
Thanks a ton I wanted to rollback to the previous version. I didnt have the latest system backup after the OTA update.
KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
No problems with this one right?
mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
v2.7 is relatively bugless as compared to v2.8
mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
Nope, works as expected
Okay, I need a little help here. I flashed the old twrp via fastboot but then got the mismatched partition size error. Well I thought what the hell, and I selected recovery from the menu, but the problem is that the phone doesn't go into recovery, just reboots. What should I do?
EDIT: I also tried rebooting via recovery when the phone wasn't connected to the laptop. If i press the power button on any of the options - normal powerup, recovery, factory or barcodes - the phone switches off.
EDIT 2: I tried getting into recovery via adb, but all I get is a 'no command' message when the phone reboots. A quick google search showed me that the no command message means that the phone still has the stock recovery. It seems like twrp isn't flashing. Any ideas!?
Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.
elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.
Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.
elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.
I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method
EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.
S7 G930T Flat Odin Factory FIrmware Downloads
G930TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I had to look this up so thought I'd share This is for Tmobile Versions
Example: G930TUVS8CRJ1 (5th # from right is 8, BL version - this is found in Settings>About Phone>Software Information>Baseband Version)
Which Oreo versions are safe (ver 4):
G930TUVU4CRI2 Oct 1, 2018
G930TUVU4CRF1 June 28, 2018
Not safe (ver 8):
G930TUVS8CRJ1 Oct 26, 2018 release date
---------- Post added at 02:55 AM ---------- Previous post was at 02:49 AM ----------
BTW nice work as always Jr! Oh, & almost forgot ...your last comment saved my @zz!!! I wasn't aware of the ver 8 issue, and the fact that u can't downgrade!! DAMN Samsung!!!!! I was seriously about to try this latest update just to try & figure out RCS not working on CRF1 & randomly came across this! THANKS! (BTW if you know anything about RCS on s7 or services/apks needed for functionality on CRF1 please pm me!)
On another note, let's have a contest to see who can hold on to the S7 the longest as their primary phone
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
FranMLG said:
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
Click to expand...
Click to collapse
No magisk requires custom boot.img
Sent using some kind of device I modified
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Thanks for the effort and providing root for T-Mobile. Perhaps I am an unlucky person. By the time I discovered this thread, my phone was already updated to G930TUVS8CRJ1 version. I am wondering if there is any hope for V8 bootloader to root their phone in near future. Here is my humble request if you could provide root for V8 update. TIA.
jrkruse said:
No magisk requires custom boot.img
Sent using some kind of device I modified
Click to expand...
Click to collapse
can we do full backup after setting up the phone and then restore it without any bugs and issues?
zfk110 said:
can we do full backup after setting up the phone and then restore it without any bugs and issues?
Click to expand...
Click to collapse
Do a system.img backup
Sent using some kind of device I modified
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
boofbatch said:
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
Click to expand...
Click to collapse
You have to update bootloaders and firmware as well so its better to update to oreo first
Sent using some kind of device I modified
working fine.
update: gonna have to switch back to u firmware because even when i unroot the phone, certain games wont work or connect to server. i cant install magisk to bypass safetynet or hide magisk after installing so root isnt even seeming worth it on this device. might as well stick to the u firmware and disable the apps I dont need and disable ota update so that i dont get the v8 bootloader update. It was fun while it lasted.
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
That's exactly what happened to me, I did not know
FranMLG said:
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
That's exactly what happened to me, I did not know
Click to expand...
Click to collapse
yikes sorry to hear that
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
zfk110 said:
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
Click to expand...
Click to collapse
Enjoy Stock
Sent using some kind of device I modified
jrkruse said:
Enjoy Stock
Sent using some kind of device I modified
Click to expand...
Click to collapse
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
zfk110 said:
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
Click to expand...
Click to collapse
Im just waiting on them to email me the passwords
Sent using some kind of device I modified
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
marvelv94 said:
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
Click to expand...
Click to collapse
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
jrkruse said:
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
Click to expand...
Click to collapse
It is not blacklisted ...i already checked...any help?
Just want to share my personal experience in hopes it may help someone.
I have T-MOBILE version GM1915.
This is only after you have successfully unlocked your bootloader.
I downloaded the twrp from @mauronofrio twrp thread.
fastboot twrp.img then choose recovery while in bootloader. Plugged in USB otg and restarted recovery. Pushed reboot button to change to unmodified slot took a backup of boot system and vendor img files. Then since I had the full ota package for us unlocked/global on my drive I chose to install it. Once done I switched back to original slot and installed it again. Reboot and stock 9.5.3.
Make sure to flash to both slots or you will most likely get Qualcomm crash dump error.
If anyone can please take a backup of the unmodified boot partition and link it here. I have system and vendor but we need stock boot.img to help others and so we can patch it and TMobile users won't have to flash twrp just to root.
twinnfamous said:
Just want to share my personal experience in hopes it may help someone.
I have T-MOBILE version GM1915.
This is only after you have successfully unlocked your bootloader.
I downloaded the twrp from @mauronofrio twrp thread.
fastboot twrp.img then choose recovery while in bootloader. Plugged in USB otg and restarted recovery. Pushed reboot button to change to unmodified slot took a backup of boot system and vendor I'm going files. Then since I had the full ota package for us unlocked/global on my drive I chose to install it. Once done I switched back to original slot and installed it again. Reboot and stock 9.5.3.
Make sure to flash to both slots or you will most likely get Qualcomm crash dump error.
Click to expand...
Click to collapse
This definitely seems promising! Should I order a USB OTG cable to attempt this in the future?
T_VASS said:
This definitely seems promising! Should I order a USB OTG cable to attempt this in the future?
Click to expand...
Click to collapse
The USB otg is only because of decryption.
I bought a SanDisk 128 gb dual USB type-C from Best buy 35 out the door
twinnfamous said:
Just want to share my personal experience in hopes it may help someone.
I have T-MOBILE version GM1915.
This is only after you have successfully unlocked your bootloader.
I downloaded the twrp from @mauronofrio twrp thread.
fastboot twrp.img then choose recovery while in bootloader. Plugged in USB otg and restarted recovery. Pushed reboot button to change to unmodified slot took a backup of boot system and vendor I'm going files. Then since I had the full ota package for us unlocked/global on my drive I chose to install it. Once done I switched back to original slot and installed it again. Reboot and stock 9.5.3.
Make sure to flash to both slots or you will most likely get Qualcomm crash dump error.
Click to expand...
Click to collapse
Tyvm for This I can just wipe the system and flash the global version from my USB flash drive
Exathi said:
Tyvm for This I can just wipe the system and flash the global version from my USB flash drive
Click to expand...
Click to collapse
I can only confirm the 9.5.3 will work.
Also no need to wipe system. After it boots to os you can factory reset to get rid of TMobile apps that we're stored in data
twinnfamous said:
I can only confirm the 9.5.3 will work.
Also no need to wipe system. After it boots to os you can factory reset to get rid of TMobile apps that we're stored in data
Click to expand...
Click to collapse
Sweet thanks I Downloaded the OxygenOS ROM from the OnePlus website is that sufficient?
twinnfamous said:
The USB otg is only because of decryption.
I bought a SanDisk 128 gb dual USB type-C from Best buy 35 out the door
Click to expand...
Click to collapse
I get my unlock token from OnePlus tomorrow afternoon. I've never used an OTG but have this one from my Pixel 3 XL with the flash drive attached you think it will work?
Edit: I just plugged it in and I'm able to explore the files on it so I'm thinking it will work.
bp328i said:
I get my unlock token from OnePlus tomorrow afternoon. I've never used an OTG but have this one from my Pixel 3 XL with the flash drive attached you think it will work?
Edit: I just plugged it in and I'm able to explore the files on it so I'm thinking it will work.
Click to expand...
Click to collapse
This will work I'm going to use that can we also just do an Local update with an unlocked bootloader on the TMobile variant?
Exathi said:
This will work I'm going to use that can we also just do an Local update with an unlocked bootloader on the TMobile variant?
Click to expand...
Click to collapse
TMobile variant software does not support the option for local upgrade.
twinnfamous said:
TMobile variant software does not support the option for local upgrade.
Click to expand...
Click to collapse
I actually got the option to flash from local storage to show by installing the stock apps found around online. This was just me tinkering briefly but it did have issues seeing the files in root, not sure if the T-Mobile one is using a different structure. I do note if you try this method mobile data breaks, I didn't have time to play with it more as I was leaving in vacation and needed a working phone so I factory reset.
I was planning on trying to flash the Android q beta then downgrading to the stock rom. I know it was a folly but was bored.
bp328i said:
I get my unlock token from OnePlus tomorrow afternoon. I've never used an OTG but have this one from my Pixel 3 XL with the flash drive attached you think it will work?
Edit: I just plugged it in and I'm able to explore the files on it so I'm thinking it will work.
Click to expand...
Click to collapse
Yes if u can explore files u should be good
Has anyone else successfully tried this? I'll have my bin tomorrow night but it's been sometime since I flashed or modded a device.
T_VASS said:
Has anyone else successfully tried this? I'll have my bin tomorrow night but it's been sometime since I flashed or modded a device.
Click to expand...
Click to collapse
nope, tried it last night and got the qualcomm error, now I think my device is hosed for a while. I can get into stock recovery and twrp though.
phab3k said:
nope, tried it last night and got the qualcomm error, now I think my device is hosed for a while. I can get into stock recovery and twrp though.
Click to expand...
Click to collapse
Guess you didn't read the part about flashing the 9.5.3 ota to both slots.
I'm Allready on the 9.5.4 now. Also please ask if not sure about something that way we can avoid issues.
twinnfamous said:
Guess you didn't read the part about flashing the 9.5.3 ota to both slots.
I'm Allready on the 9.5.4 now. Also please ask if not sure about something that way we can avoid issues.
Click to expand...
Click to collapse
i did, problem is when I flashed one side, I got an error about the /data partition when I tried to flash either partition. If the error can be overcome, I'm sure flashing the stock image will be possible.
phab3k said:
i did, problem is when I flashed one side, I got an error about the /data partition when I tried to flash either partition. If the error can be overcome, I'm sure flashing the stock image will be possible.
Click to expand...
Click to collapse
The data error doesn't pertain to the system or other partitions Just data.
Also did you use USB otg once you were in twrp.
twinnfamous said:
The data error doesn't pertain to the system or other partitions Just data.
Also did you use USB otg once you were in twrp.
Click to expand...
Click to collapse
yep, I used my otg adapter from my pixel and a flash drive. when I'm in twrp I can browse and select the file and flashing appears to work, but when I first try to flash after switching to non active partition I get an error. I'm using the stock image from oneplus, OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_fc480574576b4843.zip, filesize is about 2.1GB.
phab3k said:
yep, I used my otg adapter from my pixel and a flash drive. when I'm in twrp I can browse and select the file and flashing appears to work, but when I first try to flash after switching to non active partition I get an error. I'm using the stock image from oneplus, OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_fc480574576b4843.zip, filesize is about 2.1GB.
Click to expand...
Click to collapse
Erase the whole system and flash the ota from your flashdrive through TWRP
I'm waiting for the MSM Tool to make the switch, it's just faster, easier and more safe!
SmileBigNow said:
I'm waiting for the MSM Tool to make the switch, it's just faster, easier and more safe!
Click to expand...
Click to collapse
Will you be able to override T-Mobile sim unlock?
I'm just trying to go around paying for device in full and 40 days.
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.