There Is No TWRP Until Now As Its Been Just 4 Days. But We Don't Need TWRP When We Have Magisk . What I Did :-
1:- Downloaded The Stock Boot Image From Github
2:- Downloaded Latest Magisk Manager And Installed.
3:- Patched Stock Boot Image With Magisk.
Download Here
4:- Flashed The Boot Image Using
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
5:- Rebooted. Dang Its Done:laugh:
Credits :- acervenky for stock image.
Xposed
1:- Download Riru-Core From Here
2:- Download EdXposed From Here
3:- Goto Magisk Click On Modules Click On + Button Than Choose Riru And Do Same From EdXoosed.
4:- Reboot And Install EdXposed Apk From Here
Enjoy
Works.
Installed GravityBox. Running smoothly.
Has anyone tried the european Variant gm1913?
jatinarora said:
Works.
Installed GravityBox. Running smoothly.
Click to expand...
Click to collapse
Which version of gravitybox did you install? I can't find a version for Android P.
sippi90 said:
Has anyone tried the european Variant gm1913?
Click to expand...
Click to collapse
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Does this work with a T-Mobile variant that's bootloader unlocked?
ScottOtis said:
Does this work with a T-Mobile variant that's bootloader unlocked?
Click to expand...
Click to collapse
I don't think so - or it will but you can't use the patched boot image posted by others here. If I understand correctly you'll need to patch your own rom's boot image. I think the T-mobile version is its own model (not the GM1917 that most people here have).
I used the patched boot image for GM1917 on a GM1913 and now my wifi and most settings are broken. And unfortunately I can't find a stock zip flash file to recover anywhere... I guess that's how it is buying the phone on launch day in Europe.
gururoop said:
Which version of gravitybox did you install? I can't find a version for Android P.
Click to expand...
Click to collapse
https://github.com/GravityBox/GravityBox/releases/tag/v9.0.0-beta-11_p
unixunderground said:
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Click to expand...
Click to collapse
Did you solve your issue ?
I got the same when I try, no wifi on the patched boot.
And unfortunately like you I suppose, I wiped and erased the system..... Spend 4h30 trying to solve it ahah
I did find and download the OTA 9.5.4 from XDA dev named
9.5.4-GM21BA-OnePlus7ProOxygen_21.E.08_OTA_008_all_1905150058_12457a8b-FASTBOOT
Click to expand...
Click to collapse
, if you copy and past this name on Google you will find a download link, and I used the All-In-One tools to flash it, you can here this software : here
Because when I tried to flash with the fastboot command, my device was stucked in the Fastboot Mode and could not do anything for 4h30 until I use the All-in-one tools
Hope it can help
How do we keep root if the when there's an OOS update?
After installing Edxposed it fails safetynet check
A.Priori said:
After installing Edxposed it fails safetynet check
Click to expand...
Click to collapse
I'm on gm1917 with patched 9.5.3 (from rom page here) and followed instructions. With gravitybox it has worked well and passes safetynet...
A.Priori said:
After installing Edxposed it fails safetynet check
Click to expand...
Click to collapse
I also faced this, for me not an issue, would be nice if it passed, but I never use no apps that require it. I'd rather the customization than SafetyNet personally, but fair warning.
ERIC
jatinarora said:
Works.
Installed GravityBox. Running smoothly.
Click to expand...
Click to collapse
Yep running fine on my phone with 9.5.4, Magisk 19.2.
Phone is a GM1917
I thought gm1917 is US version which only has 9.5.3 as latest ?
Are you sure you are gm1917?
---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------
tech_head said:
Yep running fine on my phone with 9.5.4, Magisk 19.2.
Phone is a GM1917
Click to expand...
Click to collapse
thought gm1917 is US version which only has 9.5.3 as latest ?
Are you sure you are gm1917?
unixunderground said:
Don't do it, I did and now my device is messed up until I can find a full stock zip. Didn't think to backup my stock boot image unfortunately, with the patched boot image I got here wifi won't work anymore and the settings app became very unstable.
Does anyone have a stock 9.5.4 boot image for GM1913? Or a flashable zip for GM1913? Any help would be much appreciated..
Click to expand...
Click to collapse
From the other thread, that's a sign the wrong boot image was flashed
I am European with GM1913 with patched 9.5.4 and works flawless! Used the image in here:
forum.xda-developers.com/oneplus-7-pro/how-to/guide-root-oneplus-7-pro-patched-boot-t3931205
Noob question: Can someone point me in the right direction on how to update to the recently released 9.5.4 if I am rooted with this method?
Sent from my GM1911 using Tapatalk
Aren't we missing the command of "fastboot oem unlock"? Actually aren't we missing several steps from the instructions? Like these:
1) Become a "Developer" by clicking on "About Phone" from the settings menu.
2) Click on "Build Number" over and over until it says you are now a developer.
3) Go to the "Developer Options" from within the "System" section.
4) Turn ON "OEM Unlocking".
5) Boot into FastBoot menu through one of three methods. The easiest is turning ON "Advanced Reboot", holding the power button until the menu pops up and selecting "Bootloader".
6) Once rebooted, type "fastboot OEM Unlocking" to fully unlock the device. (The device will now wipe everything).
Mix some of the instructions from Kingmohdarif in here at the end or somewhere in there.
Munk0 said:
Aren't we missing the command of "fastboot oem unlock"? Actually aren't we missing several steps from the instructions? Like these:
1) Become a "Developer" by clicking on "About Phone" from the settings menu.
2) Click on "Build Number" over and over until it says you are now a developer.
3) Go to the "Developer Options" from within the "System" section.
4) Turn ON "OEM Unlocking".
5) Boot into FastBoot menu through one of three methods. The easiest is turning ON "Advanced Reboot", holding the power button until the menu pops up and selecting "Bootloader".
6) Once rebooted, type "fastboot OEM Unlocking" to fully unlock the device. (The device will now wipe everything).
Mix some of the instructions from Kingmohdarif in here at the end or somewhere in there.
Click to expand...
Click to collapse
Well yeah OP makes some assumptions.
I typed "fastboot flashing unlock" instead of what you said but maybe both works.
Anyways, as OP said, we don't have TWRP yet so we must do more ourselves. I've extracted the lastest STOCK boot image from version 9.5.5.GM21BA (at the time of writing the last on downloads.oneplus.com and also what my 7 Pro is running right now). I patched it with Magisk 19.2 and flashed it using "fastboot flash boot magisk_patched.img".
Result was successful, latest firmware, Magisk rooted :good:
The patched boot image was too large to include so I uploaded it to some random file hosting site: https://www.file-up.org/z8ka0weyftcv
To extract the stock boot image I used this nice tool: https://github.com/cyxx/extract_android_ota_payload
Related
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?
How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!
EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device
Ah! Will do this immediately when I get home.
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!
droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!
HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk
HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.
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.
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
tatico28 said:
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
Click to expand...
Click to collapse
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Homeboy76 said:
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Click to expand...
Click to collapse
No, I did not, is there a workaround?
tatico28 said:
No, I did not, is there a workaround?
Click to expand...
Click to collapse
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
tatico28 said:
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
Click to expand...
Click to collapse
Hi, what do you mean updating the tools module? tnks
davidvd102dvd said:
Hi, what do you mean updating the tools module? tnks
Click to expand...
Click to collapse
I think he's referring to SDK platform-tools.
Homeboy76 said:
I think he's referring to SDK platform-tools.
Click to expand...
Click to collapse
i though the same but tried without success
davidvd102dvd said:
i though the same but tried without success
Click to expand...
Click to collapse
Ok, then this must be what he is talking about: https://pixelrepair.withgoogle.com/carrier_selection
Yes the SDK Platform- tools, also I had to fastboot flash the boot.img to both a,b slots.
Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
alwynjoshy said:
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
Click to expand...
Click to collapse
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Homeboy76 said:
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Click to expand...
Click to collapse
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
alwynjoshy said:
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
Click to expand...
Click to collapse
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Badger50 said:
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Click to expand...
Click to collapse
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
tatico28 said:
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
Click to expand...
Click to collapse
I tried the way you said but same result. The only thing i didn't do is i flashed only slot A only. But my active slot is A so i think that is not the issue
alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Badger50 said:
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Click to expand...
Click to collapse
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
alwynjoshy said:
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
Click to expand...
Click to collapse
It's a matter of choice really. Many, like myself, like to fastboot the factory images every month to update. Others like the OTA. Functionality is pretty much the same as far as I've seen. However, you can't fastboot an OTA, likewise you can't side load a factory image, and of course, you have to be bootloader unlocked to fastboot the factory images, so keep that in mind as well. I also like using fastboot because you can switch slots to sometimes get rid of errors that occasionally pop up. Good luck with finding your solution whichever way you choose to go. :good:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, enter bootloader do a "fastboot flash init_boot magskpatchedfile.img.
9, reboot and test,
I have removed the _a in the cmd line as it appears its not needed
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum.
Ok,, this how I flashed ,and will flash, the new updates coming out so as not to lose data ,this will NOT do a wipe plus it's faster ,,,,, I know there are multiple other ways but for now I choose this,, hth
1. Download the correct ota file here
https://developers.google.com/android/ota and copy to adb folder
2. Place phone in factory recovery and toggle to apply update from adb,,
3. Open cmd prompt in adb folder type adb sideload factoryota.zip ,,,takes 5-10 minutes to complete, reboot ,,
if rooted,
1 download correct full image zip here
https://developers.google.com/android/images. That matches ota you just flashed,
2 extract the ini.boot.img , patch with magisk and reflash in adb for root
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
Does the screen come on at all? In your other post you said it was black. If there's nothing at all on the screen, your phone is probably bricked.
JimJamer8 said:
it doesnt turn on at all
Click to expand...
Click to collapse
Have you tried a hard reset - hold the power button down for 10 seconds or so until the phone vibrates?
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You didn't try the steps I listed as I never said to flash a rooted bootloader
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You may need to disable Verity and Verification. I flashed my stock image back to the phone using the tool here: https://flash.android.com/ and checked the boxes to disable verity and verification, then followed the steps above. Important to note that booting to Bootloader tells you which slot is active, and running the command fastboot flash init_boot magisk_patched_25205_GUID.img automatically patches the active boot slot. From there you just need to run the Universal Safety net fix from KDrag0n and the latest MagiskHide and you should be good to go
hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Thank you for the help, turned out the _a was screwing me over, works great now!
mnemonical said:
Thank you for the help, turned out the _a was screwing me over, works great now!
Click to expand...
Click to collapse
I know ,,that was messing me up too, it did not work untill I put that part in,, don't ask me why! Lol
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
atom_jack said:
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
Click to expand...
Click to collapse
I'll give it a try
googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
Use the non replace version of revanced and disable stock YT
Hitman478™ said:
Use the non replace version of revanced and disable stock YT
Click to expand...
Click to collapse
Revanced Manager app is just going to black screen after install
hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
googletermsofservice said:
Revanced Manager app is just going to black screen after install
Click to expand...
Click to collapse
I've it installed and it's working without any issue
AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
Use fastboot flash init_boot "image.img" without quotes and without specific the partition, it will goes on the active one, for me it has working at first try
hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
THX, in fact the "fastboot boot" command was used a lot with OnePlus devices because it is safer to boot in the rooted os and when there is an error you can just reboot without the command...and when you install it afterwards with magisk you know it will work
Does Universal Safetynet Fix work?
Just wanted to thank OP. My Pixel 7 arrived about an hour ago, got the bootloader unlocked no problem, then actually I flashed the latest System Image first, then had Magisk patch init_boot.img, flashed that, easy peasy.
hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
It's usually used to temporarily boot a patched boot image and then you can do direct install in magisk manager