Finally, I just rooted my m31 phone without twrp!
Yes, I used the path method, and no I did not get any infinity boot loop.
It's working perfectly fine, I even installed some magisk modules already like iOS emoji font and unistalled some annoying samsung/google apps!
I'm not so sure if it will work worldwide, but for ZTO versions (Brazil) it worked.
This will certainly delete all your files. Make a backup of what you consider important and do at your own risk.
If you need any evidence that is working or you just let me know how can I help.
1) First of all, I put my phone on the last firmware version, which for me is M315FXXU2ATIB
If you're using a version before that and you have no OTA update available, you can download the firmware in specific websites like sammobile.com samfrew.com or stockrom.net and update it by yourself using Odin
2) With this firmware applied on your phone, make sure to use the boot.img attached on this post and paste it to your phone. Now go to magisk, and choose install, and then "select and patch a file". Magisk will give you a new file.
3) Unlock developer options, then set OEM unlocking to unlock your bootloader, and enable USB Debugging.
There's a lot of internet pages teaching this step
4) Shutdown your phone. Press and hold volume up and volume down at same time, hold it and then plug usb cable. Release up and down buttons, and on the next screen press Up to go to the bootloader.
5) Once there, open Odin, click on AP and select the magisk_patched.tar it will take like 2 or 3 seconds. You should see PASS on Odin and your M31 is probably restarting at this point. That's all, your M31 is rooted.
Big thanks to stockroom.net for the files!
useful links:
https://www.stockrom.net/2020/10/sm-m315f-b2-zto-10q-m315fxxu2atib.html
https://www.youtube.com/watch?v=M-AoLbShPI8&ab_channel=Rcelltutoriais
WTF
U legend
hi thank you for sharing this, but i want to know the origin of the file attached (boot.img). and can i go back to making my device unrooted ?
evilhilda said:
hi thank you for sharing this, but i want to know the origin of the file attached (boot.img). and can i go back to making my device unrooted ?
Click to expand...
Click to collapse
ok my bad i had to enable OEM unlock, after factory reset, i installed magisk to check ant it's rooted by wanted to make an update, after that the phone restarted and became very slow and unstable
evilhilda said:
ok my bad i had to enable OEM unlock, after factory reset, i installed magisk to check ant it's rooted by wanted to make an update, after that the phone restarted and became very slow and unstable
Click to expand...
Click to collapse
The img attached is the very same img on the AP file, which means is the original img. Is attached just to make it easy instead of make people extract the file manually.
You have to make sure you have the same firmware installed on your phone as the img before doing the process. It's working perfectly fine on my phone. If your phone became unstable you surely can go back to the stock firmware again using Odin, but the problem is probably the update you tried to do considering is not safe to update a root phone
Take a look here for updating a rooted phone
https://forum.xda-developers.com/galaxy-s10/help/how-to-upgrade-losing-root-twrp-t4042893
mvini_ab said:
The img attached is the very same img on the AP file, which means is the original img. Is attached just to make it easy instead of make people extract the file manually.
You have to make sure you have the same firmware installed on your phone as the img before doing the process. It's working perfectly fine on my phone. If your phone became unstable you surely can go back to the stock firmware again using Odin, but the problem is probably the update you tried to do considering is not safe to update a root phone
Take a look here for updating a rooted phone
https://forum.xda-developers.com/galaxy-s10/help/how-to-upgrade-losing-root-twrp-t4042893
Click to expand...
Click to collapse
Thank you for taking some time to explain the origin of the file, your method is working fine, and it is using magisk to root the device, it worked for my device which had the indian firmware, but its the same as the one rolling in brazil, the concern is that after unlocking the bootloader, factory resetting and installing the magisk created boot file, and running the update from magisk manager (because it requires it for some reason) the check comes out negative, i don't remeber exactly what it said but it was all in red and says that the check failed, honestly i don't understant this part maybe i didn't have to let magisk update & restart (also after trying to open build.prop editor for the first time and granting access it crased a restarted again).
Anyway, the main reason for me trying to root my device, was to enable camera2api to be able to use gcam ports properly, in which i failed miserably, apparently exynos processors aren't easy to enable camera2api using terminal, which renders the root futile in my case. I locked the bootloader and flashed the official rom again and it's working fine.
Thank you again and i hope some developer takes his precious time to make a good guide from rooting to usable gcam.
Can we update without losing root and data ?
evilhilda said:
Thank you for taking some time to explain the origin of the file, your method is working fine, and it is using magisk to root the device, it worked for my device which had the indian firmware, but its the same as the one rolling in brazil, the concern is that after unlocking the bootloader, factory resetting and installing the magisk created boot file, and running the update from magisk manager (because it requires it for some reason) the check comes out negative, i don't remeber exactly what it said but it was all in red and says that the check failed, honestly i don't understant this part maybe i didn't have to let magisk update & restart (also after trying to open build.prop editor for the first time and granting access it crased a restarted again).
Anyway, the main reason for me trying to root my device, was to enable camera2api to be able to use gcam ports properly, in which i failed miserably, apparently exynos processors aren't easy to enable camera2api using terminal, which renders the root futile in my case. I locked the bootloader and flashed the official rom again and it's working fine.
Thank you again and i hope some developer takes his precious time to make a good guide from rooting to usable gcam.
Click to expand...
Click to collapse
I don't think it's your fault for not being able to edit build.prop, from what I know it's a known issue with Android 10. You can check that on several websites. Have a look at this pages:
https://didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
And it looks like this guy found a solution by remounting, but I think is risky:
https://forum.xda-developers.com/apps/magisk/how-modify-priv-app-android-10-magisk-20-t4036633
ariefabuzaky said:
Can we update without losing root and data ?
Click to expand...
Click to collapse
That's the lastest version where I live, but I believe if you update it using Odin and the right settings like CSC HOME, yes, you can update without losing root and data.
i think cant access system, i cant uninstall system apps like Vodafone menu or galaxy store :/ am i wrong bro?
dtanil said:
i think cant access system, i cant uninstall system apps like Vodafone menu or galaxy store :/ am i wrong bro?
Click to expand...
Click to collapse
Install Root Checker to check if you actually have root access and made the process correctly. If not, you have to make it again following step by step carefully.
Once the process is finished and you have root access, go to magisk and allow the app you're using to see the system folder to have access through magisk.
To uninstall apps, I advice you to use this app, because at least on my M31, even Lucky Patcher and TitanumBackup wasn't able to uninstall system apps:
https://forum.xda-developers.com/android/apps-games/app-uninstall-apps-t3776235
Let me know if you're still need help
Stitched only patched boot.img. and it worked
gigabyteua said:
Stitched only patched boot.img. and it worked
Click to expand...
Click to collapse
Good to know. Thank you for the feedback
The method does not work on my European version (DBT) with *System as Root*.
Tried to use just the patched boot.img as suggested here (fail message in Odin) and the patched full AP file as suggested on Magisk website (reboots to download until reflashing the stock ROM).
xdausr11 said:
The method does not work on my European version (DBT) with *System as Root*.
Tried to use just the patched boot.img as suggested here (fail message in Odin) and the patched full AP file as suggested on Magisk website (reboots to download until reflashing the stock ROM).
Click to expand...
Click to collapse
you need to patch boot.img from the firmware that is currently installed, and not the one that is offered. Then, after the firmware, immediately go into recovery and do Wipe data / factory reset and Wipe Cache Partition. And then reboot into the system
gigabyteua said:
you need to patch boot.img from the firmware that is currently installed, and not the one that is offered. Then, after the firmware, immediately go into recovery and do Wipe data / factory reset and Wipe Cache Partition. And then reboot into the system
Click to expand...
Click to collapse
I had extracted the boot.img from my current firmware (M315FXXU2ATIC from SEP2020 with One UI 2.1 and new bootloader), patched it, flashed the tar via Odin, here I got the "failed" message in Odin.
Can you reconfirm if your Samsung firmware version has also System as root? Which region do you use?
xdausr11 said:
I had extracted the boot.img from my current firmware (M315FXXU2ATIC from SEP2020 with One UI 2.1 and new bootloader), patched it, flashed the tar via Odin, here I got the "failed" message in Odin.
Can you reconfirm if your Samsung firmware version has also System as root? Which region do you use?
Click to expand...
Click to collapse
Mod edit: Translation
I am from Ukraine, I am not strong in English, please excuse me. I will write in Russian, I hope you will understand.
After many unsuccessful attempts by various methods, I was overcome by paranoia and I began to do everything that was possible, perhaps not necessary.
1. Installed the latest Ukrainian region SEK - M315FXXU2ATIC with One UI 2.1 used CSC_OMC_OXM_M315FOXM2ATI6
2. Copied AP_M315FXXU2ATIC_CL19748244_QB34588175_REV00_user_ low_ship_meta_RKEY_OS10.tar to your phone
3. Installed CANARY from the forum 4pda.ru/forum/index.php?showtopic=774072 registration required to download
4. Patched all AP_M315FXXU2ATIC.
5. Copied magisk_patched.tar to computer
6 Opened magisk_patched.tar in 7zip and removed everything except boot.img vbmeta.img recovery.img.lz4
7. Deleted Google account, made a hard reset in the phone
8. Once again, enter Recovery and again Wipe data / factory reset and Wipe Cache Partition.
9. Initial setup without registration with Google and Samsung
10. Shutdown.
11. Entering the download mode - holding down both volume buttons and then connecting the cable.
in Odin auto reboot - remove the bird
12. I asked for magisk_patched.tar = bootloop
13. Deleted recovery.img.lz4 stitched = bootloop
14. Removed vbmeta.img I only asked for boot.img
15. Reboot as soon as the screen goes out immediately enter recovery
16.Wipe data / factory reset and Wipe Cache Partition again.
17. Finally, from recovery, reboot into the system.
Root received. System files are edited (deleted, renamed, file permissions, folders are created, etc.)
Я из Украины, в английском не силен прошу извинить. Напишу на русском надеюсь разберетесь.
После многих неудачных попыток разными методами меня охватила паранойя и я начал делать все что можно, возможно и не нужное.
1. Установил последнюю украинскую регион SEK - M315FXXU2ATIC с One UI 2.1 использовал CSC_OMC_OXM_M315FOXM2ATI6
2. Скопировал AP_M315FXXU2ATIC_CL19748244_QB34588175_REV00_user_low_ship_meta_RKEY_OS10.tar на телефон
3. Установил CANARY с форума 4pda.ru/forum/index.php?showtopic=774072 для скачивания необходима регистрация
4. Patched всю AP_M315FXXU2ATIC.
5. Скопировал magisk_patched.tar на компьютер
6 Открыл magisk_patched.tar в 7zip и удалил все кроме boot.img vbmeta.img recovery.img.lz4
7. Удалил учетную запись Google, сделал полный сброс (hard reset) в телефоне
8. Еще раз вход в Recovery и снова Wipe data / factory reset and Wipe Cache Partition.
9. Начальная настройка без регистрации в Google и Samsung
10. Выключение.
11. Вход в режим download - зажатые обе кнопки громкости и затем подключение кабеля.
в Odin auto reboot - снять птичку
12. Прошил magisk_patched.tar = bootloop
13. Удалил recovery.img.lz4 прошил = bootloop
14. Удалил vbmeta.img прошил только boot.img
15. Перезагрузка, как только экран погас сразу вход в recovery
16. снова Wipe data / factory reset and Wipe Cache Partition.
17. И наконец из recovery перезагрузка в систему.
Root получен. Системные файлы редактируются (удаляются, переименовываются, права файлам, папки создаются и.т.д.)
@gigabyteua
Just a friendly FYI my friend. If you would please review XDA Rule #4, and post accordingly, we would be very appreciative.
--Regards: Badger50
gigabyteua said:
Mod edit: Translation
Installed the latest Ukrainian region SEK - M315FXXU2ATIC with One UI 2.1 used CSC_OMC_OXM_M315FOXM2ATI6...
Click to expand...
Click to collapse
Thanks for all the details.
Can you reconfirm your firmware version is SAR (system as root) - this is shown in magisk manager.
Can you reconfirm you unlocked bootloader not only in developer mode but also in bootloader (long press volume up)?
Thanks.
xdausr11 said:
Thanks for all the details.
Can you reconfirm your firmware version is SAR (system as root) - this is shown in magisk manager.
Can you reconfirm you unlocked bootloader not only in developer mode but also in bootloader (long press volume up)?
Thanks.
Click to expand...
Click to collapse
yes unlocked in the developer menu and long press in bootloader mode
Related
Everything you do with the device, you do at your own peril and risk.
An unlocked bootloader is required, and the factory unlock is enabled.
1. Install TWRP
2. Install SuperRoot_noverity_nocrypt.zip through TWRP
3. Boot the system.
4. You need to install the APK from PlayStore afterwards https://play.google.com/store/apps/details?id=me.phh.superuser
Now you have root access and full access to the system partitions.
Enjoy Root
If an error "Error 1" is output with the firmware in TWRP. It is necessary to replace BOOT.img, on BOOT.img, from the firmware that you installed before obtaining root access.
Code:
fastboot flash boot boot.img
Acknowledgments:
https://forum.xda-developers.com/p10/development/testers-twrp-t3585256
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Additional materials that can help with troubleshooting. (Here you will find firmware from Huawei.)
The firmware for VTR
The firmware for VKY
SuperRoot_noverity_nocrypt.zip
Entering recovery?
yury_z said:
An unlocked bootloader is required, and the factory unlock is enabled.
1. Install TWRP
2. Install SuperRoot_noverity_nocrypt.zip
3. Download the device.
4. You need to install the APK from PlayStore afterwards https://play.google.com/store/apps/details?id=me.phh.superuser
5. All of you got Root + disabling the protection of system partitions for writing.
Enjoy Root
If an error "Error 1" is output with the firmware in TWRP. It is required to override BOOT.img on BOOT.img from the firmware.
Code:
fastboot flash boot boot.img
Acknowledgments:
https://forum.xda-developers.com/p10/development/testers-twrp-t3585256
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Boot_VTR-L29C10B120
Recovery_VTR-L29C10B120
SuperRoot_noverity_nocrypt.zip
Click to expand...
Click to collapse
How do you enter recovery on P10? It throws out that warning when you press "-" together with power on button. and then boots as normal.
Jaunpetrovics said:
How do you enter recovery on P10? It throws out that warning when you press "-" together with power on button. and then boots as normal.
Click to expand...
Click to collapse
power on button and "+"
Where to copy root .zip?
yury_z said:
power on button and "+"
Click to expand...
Click to collapse
And where to copy root .zip file? When I press Install, I can't seem to see the file, because it's not there and all the normal files except folders seem to be encrypted.. I pasted it in the main view. Where can I find it?
Jaunpetrovics said:
And where to copy root .zip file? When I press Install, I can't seem to see the file, because it's not there and all the normal files except folders seem to be encrypted.. I pasted it in the main view. Where can I find it?
Click to expand...
Click to collapse
Put on the microSD card, below the button select the media.
@yury_z i get an error while installing the zip in twrp. I think is the same error that you said.
I have installed VTR-L09C432B123
What can i do?
Will Boot_VTR-L29C10B120 working in my device?
Thanks
TheBigCatTheory said:
@yury_z i get an error while installing the zip in twrp. I think is the same error that you said.
I have installed VTR-L09C432B123
Thanks
Click to expand...
Click to collapse
BOOT_VTR-L29C432B123
SuperSU
Is possible flash classic SuperSU?
matata86 said:
Is possible flash classic SuperSU?
Click to expand...
Click to collapse
No SuperSU can not get root access on the Huawei P10.
I've tried many ways. Got only a recovery device.
If you disable SELinux, for example, through SELinuxModeChanger. We have full access without SuperSU.
Sorry I'm an old iOS user.
What do you mine by this step : "Download the device."
I checked with "Root checker" I'm now rooted, but I did'nt use these file : "Boot_VTR-L29C10B120 and
Recovery_VTR-L29C10B120" Is it normal ?
Thanks
larecrue said:
I checked with "Root checker" I'm now rooted, but I did'nt use these file : "Boot_VTR-L29C10B120 and
Recovery_VTR-L29C10B120" Is it normal ?
Thanks
Click to expand...
Click to collapse
They are needed to correct mistakes. If you get root access, then you do not need them.
Ok thanks for reply, now I'm rooted, no need custom ROM ? Sombody know the best way to transfert data from iOS to android (sms...)
I already rooted my VTR-L09C432B113 but want to decrypt and unlock the file system. Any solutions? Don't want to flash your boot.img for other device brand.
Did i lose some feature if i root P10? For example if i root my Sony Xperia i'll lose some camera and display technology if i don't backup some files. Thanks in advance.
SebastianAlejandro said:
Did i lose some feature if i root P10? For example if i root my Sony Xperia i'll lose some camera and display technology if i don't backup some files. Thanks in advance.
Click to expand...
Click to collapse
I'm on phh Supersu and didn't lose anything or got malfunction.
EDIT:
Unlocked filesystem is working for me now. I tested it with AdAway - the Hosts file stays after reboot.
If you need the boot.img of VTR-L09C432B113, klick here (extracted from original update.app).
Jannomag said:
I already rooted my VTR-L09C432B113 but want to decrypt and unlock the file system. Any solutions? Don't want to flash your boot.img for other device brand.
Click to expand...
Click to collapse
Install your VTR-L09C432B113 boot.img, then again get the final access using SuperRoot_noverity_nocrypt.zip.
P.S. VTR-L09C432B123 = VTR-L09C432B113 - Bootloaders are the same.
It worked! Thank you. I'm a newby, and managed to do this. If there is any questions - feel free to ask!
Does this work for VTR-AL00?
I just recently got mine from China
xZhongCheng said:
Does this work for VTR-AL00?
I just recently got mine from China
Click to expand...
Click to collapse
TWRP is needed for the Chinese location VTR-AL00. The rest (item 2) is suitable.
yury_z said:
Install your VTR-L09C432B113 boot.img, then again get the final access using SuperRoot_noverity_nocrypt.zip.
P.S. VTR-L09C432B123 = VTR-L09C432B113 - Bootloaders are the same.
Click to expand...
Click to collapse
What about VTR-L09C109B100? Is it safe to follow this method? Thank you!
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Hayleyw2 said:
Here we have root for stock rom Thanks to the Chainfire Team.
Everything done by them so all thanks and credits are for them
Download
https://download.chainfire.eu/1036/CF-Root/CF-Auto-Root/CF-Auto-Root-on7xelte-on7xeltedd-smg610f.zip
Installation
-Enable USB debugging and OEM unlocking in the settings
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue
-Flash the CF-Auto-Root package as AP in ODIN(Comes within the zip file), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
I tested it on my device and it worked normally
I will not be responsible for any damage to your device, but following the steps will normally work normally
I just tested with ROM stock 6.0.1 with security patch from 1 July 2017
.
Click to expand...
Click to collapse
Hi will it work for version 7.0 also
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
How to change Supersu with Magisk?
Razortm said:
it's working fine for me
i have "G610FDDU1BRF2" with android version 7.0 and it gets installed successfully
thanks
Click to expand...
Click to collapse
How to restore stock recovery
Ryan.XM said:
How to restore stock recovery
Click to expand...
Click to collapse
Flash the cf auto root and it will automatically change your recovery into stock.
bjpp21 said:
Flash the cf auto root and it will automatically change your recovery into stock.
Click to expand...
Click to collapse
Ok thanks
I have J7 prime [SM-G610F] with stock andriod 8.1, samsung experience 9.5 and 1 November 2018 security patch will it still work?
I don't think so. I think the J7 with 8.1 is impossible to root? I can't seem to find an answer on this.
lordbaal19 said:
i don't think so. I think the j7 with 8.1 is impossible to root? I can't seem to find an answer on this.
Click to expand...
Click to collapse
its not impossible to root j7 on oreo..just search here in xda and you will find the impossible is really possible.
Well the TWRP thread has no real answers and this method doesn't work either.
I have done it
LordBaal19 said:
Well the TWRP thread has no real answers and this method doesn't work either.
Click to expand...
Click to collapse
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
ernestoi said:
yes, I have made root in my SM-G610m with Android 8.1 and it was with TWRP, and I have learned it from YouTube and in Spanish language.
For now I do not have available Super User. I think this post will work for me
Click to expand...
Click to collapse
Found a way:
LordBaal19 said:
Which one do you recommend? At which point do I have to install it and then I don't need to install no-verity-opt-encrypt-6.0?
EDIT: I think I finally got it. I did it like this:
1. Ok, so the phone as a fresh 8.1.0 system (just flashed the 7.0 and then it updated OTA in a matter of minutes). I enter the phone, enable the developer mode, enable OEM Unlocking and USB Debug.
2. Then I put the phone on download mode, flash the TWRP recovery disabling the auto-reboot on Odin so it doesn't boot to system automatically. This seem important since otherwise the recovery goes back to stock.
3. Then, to get out of download mode I press vol. down and power keys at the same time and the phone turn off. Then I turn on the phone into recovery mode, once in there I swipe into write mode and go to Wipe and select Format Data, type down yes and it says it's done. I go back to TWRP main menu.
4. I connect the cellphone to the PC and in storage I select Mount USB. Then drag the Magisk-v18.0.zip file into the storage that pops up on Windows. Then I saftely remove the device in Windows and go back to the main TWRP menu on the phone. I select Install and install the .zip file without selecting Signature verification or Reboot after is complete. It says is done installing and no errors seems to occur. I employ the button to wipe Cache and Dalvik.
5. I go back again o Wipe and select Format Data, type down yes and it says it's done, again.
5. Then I try to reboot to System, and choose to Do Not Install the TWRP app, and... SUCCESS!! The phone starts again, I config everything and then Magisk is there in the apps. I tried with an app that requires SU and it works!
Thanks for the help.
Click to expand...
Click to collapse
For the files and details check the OP on that thread.
LordBaal19 said:
Found a way:
For the files and details check the OP on that thread.
Click to expand...
Click to collapse
That's the way I have done it. But if you go on Z3X, select the device (SM-G610M), and you perform some activity like repair IMEI, Z3X detects the root, but it does not detect the Super User.
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.
Hello,
I have XEO software from security patch 07.21
And rooted phone.
I try upgrade FW Odin. Choose CSC Home and update...
And telephone not started
Only try three times started and write fault system.
Only wipe data working and starting
How i can in future rooted my telephone, only uses magisk, and safe upgrade to next update without lost data ???
Please help... Thanks
I've never tried it...
[S20_FE SM-G781U/U1_Snapdragon]-[Upgrade Easily Firmware Using Odin]-[Automatically Root Remove Forceencrypt Patch Bluetooth And Fix Safetynet]
Must Have An Unlocked Bootloader To Do This! This An odin tar file I have created to flash along with stock odin firmware to automatically install TWRP recovery along with Disable VBMETA image. The tar file will also automatically install...
forum.xda-developers.com
Thanks for info.
But i think i not good for my model.
I have SM-G781B
Other advaice please...
I try moore times and always i must wipe data
Always if add home CSC ( without delete data ) must later wipe data in menu ( always corrupted data, system )
onken said:
Thanks for info.
But i think i not good for my model.
I have SM-G781B
Other advaice please...
I try moore times and always i must wipe data
Always if add home CSC ( without delete data ) must later wipe data in menu ( always corrupted data, system )
Click to expand...
Click to collapse
If you were rooted while patching the boot.img with magisk you will have to redo it on each odin update with patched AP and Home CSC to keep the root & data.
This is the way I do it but it implies not to use twrp therefore caution is in order regarding modules which could lead to bootloop.
Full House said:
If you were rooted while patching the boot.img with magisk you will have to redo it on each odin update with patched AP and Home CSC to keep the root data.
Click to expand...
Click to collapse
Hello, thanks.
I can use old patched AP for new software ?
onken said:
Hello, thanks.
I can use old patched AP for new software ?
Click to expand...
Click to collapse
No you can't, you have to patch AP each time with magisk before flashing
Full House said:
No you can't, you have to patch AP each time with magisk before flashing
Click to expand...
Click to collapse
Ok.
Thanks for info
Maybe know why not can rooted new mode Samsung A52s ?
I always run this same method and telephone not starting
onken said:
Ok.
Thanks for info
Maybe know why not can rooted new mode Samsung A52s ?
I always run this same method and telephone not starting
Click to expand...
Click to collapse
Have you unlocked the BL?
Didn't you have the camera problem?
If you followed the procedure and it doesn't work maybe the patched AP file was corrupted during the transfer have you eliminated this probability?
I try many times patched. Always not working.
Not only in me.
But about camera not checked but if yes to big problem.
If not can uses later camera for rooted, why possible unlock bootlader permission from Samsung....
unlocking the bootloader doesn't cause an issue with the camera on this phone.
different story on the Galaxy Fold 3 but we are OK to unlock.
once you have patched the AP file DON'T use windows file manager to move it, use ADB pull command.
ADB Push and Pull - Push and Pull Files on Android Using Commands
You can push and pull files on Android using ADB commands. ADB Push and Pull make Android development easy &save time by reducing data retrieving tasks.
www.droidviews.com
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?
jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.