Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
this is what the screen says when i try to flash
no content in your post
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time
i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com
Related
Hey, I recently got a Nexus 6, and instead of installing CM as I usually do, I'm going to try rooting and using Xposed. The trick is that I use Linux exclusively, so I can't use the one-click installers. It's a Nexus, so unlocking is a piece of cake, and I know how to use adb and fastboot to install a custom recovery.
From there, I'm not totally sure what to do. I downloaded the SuperSU zip from chainfire, which I'll install from twrp... Then... Do I need to install busybox or something? I guess I'll have to side load xposed after that?
Also, not sure what the update path will be after that. I guess rooting will break OTA... So what do I do?
Sorry for being such a newb! Thanks!
to root..
fastboot oem unlock to unlock the bootloader
fastboot flash twrp recovery
flash the latest supersu zip within your new recovery
then just reboot, and you have root.
to update, you can flash any updated stock rooted rom, or you can update via fastboot.
@ninjaaron,
Go to the Xposed thread, there's a lot of info > http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
simms22 said:
to root..
fastboot oem unlock to unlock the bootloader
fastboot flash twrp recovery
flash the latest supersu zip within your new recovery
then just reboot, and you have root.
to update, you can flash any updated stock rooted rom, or you can update via fastboot.
Click to expand...
Click to collapse
Thanks for the concise explanation! Can I install a rom from the vendor with fastboot, or will I have to use mod'ed Roms after rooting?
ninjaaron said:
Thanks for the concise explanation! Can I install a rom from the vendor with fastboot, or will I have to use mod'ed Roms after rooting?
Click to expand...
Click to collapse
Depends what you mean by vendor. Only Google release official ROMs and yes they can be flashed via fast boot.
Yes, I was referring to Google when I said " the vendor"
ninjaaron said:
Yes, I was referring to Google when I said " the vendor"
Click to expand...
Click to collapse
Yep. Just needed to clarify because on other android devices, carriers can be vendors
ATTENTION!
You MUST read all the guide BEFORE doing it, if you do it without reading all of it first you may ends up bricking your phone!
Prerequisites:
Asus ZE500KL (may work on ZE500KG, but haven't tested, do it on your own risk) on Marshmallow, NOT LOLLIPOP!
Also, it must have fully booted AT LEAST one time, otherwise, you'll soft-brick it.
If your phone is not on Marshmallow, you can use THIS guide insteadDownload and put the unlocker zip file and the SuperSu zip file in the phone
How To:
1 - Install adb and fastboot driver (follow THIS guide)
Now you can connect the phone to your computer2 - Reboot in fastboot mode with one of the following method:
a -Volume Up while booting upb -With adb, after enabling USB debugging in developer settings, using:
Code:
adb reboot bootloader
Now that you are in bootloader, you have to boot in TWRP,
download THIS recovery (is the twrp one) and boot in to it, using this command:
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
Code:
fastboot boot TWRP-x-x-x-x.img
(Obviusly the recovery name must be the one you downloaded)
IMPORTANT: DON'T FLASH IT OR YOU WILL GET BOOTLOOP!!!
It should automaticaly enter in recovery.
Now you MUST flash FIRST ZE500KL_BootloaderUnlock.zip, otherwise you'll brick your phone
Btw, the recovery will mount your phone's memory, so you can put now the files in the phone, if you forgot to do it before
AFTER you installed the unlocker zip, you can install the SuperSu zip
When the install is complete, clear the cache and reboot your phone, now you can enjoy your root!
Downloads:
Latest @MiauLightouch TWRP - 3.0.0.2 Mirror
Latest SuperSu zip - 2.65 Mirror
Bootloader Unlocker (from @MiauLightouch original post) - Mirror
Credits:
@MiauLightouch for pretty much everything
@LuK1337 , @luca020400 and everyone on #titandev for being awesome
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
MuzgontarAco said:
So.. I'm thinking of buying a ZE500KL and I've been doing some reading on this phone on the forums.. did it really just get unlocked like yesterday? does that mean custom roms from now on?
Click to expand...
Click to collapse
I would recommend Z00L/T, you will get cm13, official unlock at least.
You Say " May Work On ZE500KG" Is ze500kg already receive Marshmallow Update?
MiauLightouch said:
I would recommend Z00L/T, you will get cm13, official unlock at least.
Click to expand...
Click to collapse
thanks for the advice but my choices are poor with about 5 phones in this price range with this one looking waay better.. getting it via contract so yeah..
How to install supersu zip? Tia.
Working! Have you tried to flash Viper4Android? On lollipop this will break Call recording and FM Radio, maybe this will not be a problem on MM?
Seanjhon027 said:
How to install supersu zip? Tia.
Click to expand...
Click to collapse
Inside TWRP there is a big "Install" button, press it and select the zip
what is the meaning of booted
mohamedelkholy said:
what is the meaning of booted
Click to expand...
Click to collapse
context?
until you saw the lock screen, that's what "booted".
stuck waiting for device
C:\Users\Clynt\Desktop\Android M>adb reboot bootloader
C:\Users\Clynt\Desktop\Android M>fastboot boot twrp.img
< waiting for device >
Ok I don't know where I get wrong but I got this error.
Img file name is ok because I renamed it.
Drivers were installed already.
Developers mode is enabled already.
Windows 7 64bit
Tried rooting this using lollipop and everything went well.
thanks!
UPDATE: i got it. it has something to do with the drivers.
Without opening the bootloader.
Notice. I have not tried it.
http://www.asus-zenfone.com/2016/05/how-to-root-asus-zenfone-2-laser-ze50kl-marshmallow.html?m=1
thanl you man i have rooted my zenfone 2 laser
Thanks very much for this guide and your work.
Can I install the new update v13.10.7.1 when I opened bootloader.
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
thanks
thks TS
now my phone its rooted
Muminek111 said:
Without opening the bootloader.
Notice. I have not tried it.
No... when trace a perequisite link Given..
you really need to unlock bootloader first
wulfe13 said:
The twrp recovery is temporary or permanent? If permanent how to go back to stock recovery? Tia
Click to expand...
Click to collapse
i think isnt permanent, this step is needed to boot into twrp then flashing a unlockBL..
to make permanent.. the command must "fastboot flash recovery twrp_X.X.X.X.img"
but make sure to unlock bootloader first...
CMIIW
Click to expand...
Click to collapse
Is it me or everytime I reboot the device after rooted, it's going back to unrooted?
Root is a success tho, great job, OP!
Edit: okay, not every reboot, but after several reboots, then it went back unrooted
Hey all,
So I posted what I did to **** everything up the other day: https://forum.xda-developers.com/ta...ie-tried-to-root-device-t3655848?goto=newpost
I read about 70 different forums posts and concluded (somehow) that i needed to try and flash "twrp_3.1.0" for my T810. Well, for some reason it worked. I now have twrp on my boot-looped device.
Now, I'm trying to install a different recommendation which is the "SuperSU-v2.76" ROM through dragging it onto my tablet via My Computer (Since Odin refuses to load it)
Guess what? Ran into another problem when doing this. My T810 will no longer connect with my PC. It is stating "Device driver software was not successfully installed"... throwing out an error message MTP USB Device Failed.
I came up with the wise idea to simply put the SuperSU file on my brand new 128gb micro SD card. I found a USB adaptor for the card, plugged it into my PC and now My Computer is stating that the Micro SD card only has 1.67mb of space available. Did a bunch of research and found out that the USB adaptor actually has a limitor pre programmed into it so that you cannot adapt large SD cards..
I'm striking out guys. I need help. I'm able to navigate the twrp menu.. is there an option on this screen that will help me? I cannot think of what needs to be done next to get this Tab working....
also
.... yes I have the Samsung USB driver installed for my particular device....
So I ended up running to the store and I bought a 16gb micro SD. It worked, I was able to run the SuperSU-v2.76 flash on my device. Geuss what happened next?
Bootloop again.
Currently trying another suggestion which calls for restoring the tablet to an original OEM flash. Going to try installing the "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" flash and ill post what happens........
NOPE! No good. twrp does not recognize booting MD5 files.... I'm stuck again.
dyrewolv said:
Click to expand...
Click to collapse
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
ashyx said:
You need to flash this version of SuperSU.
http://download.chainfire.eu/1122/SuperSU/SR3-SuperSU-v2.82-SR3-20170813133244.zip
Click to expand...
Click to collapse
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
dyrewolv said:
Hey ashyx,
How does that version of SuperSU differ from the one I just tried to flash?
What causes the tab to bootloop in the first place?
Thanks for your help!!
Click to expand...
Click to collapse
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
ashyx said:
Difficult to explain, but it should prevent the bootloop.
Samsung and Google's updates can break root, so new patched versions need to be released to overcome the issue.
You should consult the Supersu beta thread for the changelog.
Click to expand...
Click to collapse
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
dyrewolv said:
gotcha. I'm 100% brand-new to rooting. After I get SuperSU rooted onto my tab... Can I proceed with installing other custom ROMs?
What's the standard procedure for rooting/flashing devices from one ROM to the next?
I must be ****ing up bad because the last (4) ROM's I've tried have all bootlooped.
I did notice that I forgot to enable developers options when my tab was still OEM.. haven't been able to boot into a menu to change it though
Click to expand...
Click to collapse
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
ashyx said:
You don't need root to be able flash custom roms but you must enable OEM UNLOCK in developer settings or you will encounter FRP Lock and won't be able to boot until you flash the stock firmware.
You will also need to patch dm-verity before installing anything custom. SuperSU and Magisk already do this or you can can flash my boot patch which also disables forced encryption.
Click to expand...
Click to collapse
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
dyrewolv said:
I tried flashing stock firmware in Odin via the file "5.0.2_T810XXU1AOG6_T810XAR1AOG6_XAR" which I found on the stock firmware forum for the T810. Odin failed during the flash...
If I get SuperSU working can I enable OEM UNLOCK?
What is dm-verity?
Click to expand...
Click to collapse
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
ashyx said:
I suggest you flash the latest Marshmallow or Nougat update.
Dm-verity is a security mechanism.
http://updato.com/firmware-archive-select-model?q=Sm-t810&exact=1
Click to expand...
Click to collapse
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
dyrewolv said:
I'm confused. So I should continue with trying to get the correct version of SuperSU flashed first..right? Then figure out what I need; Marshmallow or Nougat? I haven't even got the tablet to get past the Samsung logo, I cannot enable OEM Unlock.. Last night when I tried flashing stuff Odin did not want to cooperate. I get a "FAIL! Complete (Write) operation failed" message. Tried to flash the stock ROM file I listed below with both re-partition unchecked and checked with no success.
Click to expand...
Click to collapse
It probably fails because you can't downgrade.
It's up to you to whether to flash MM or NN.
You will need to update first and then flash twrp and then supersu.
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.
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.