Ive veen trying to root my sm-t380 to the point of even creating my own modded boot.img with security set to 0. When i felt like everything had been done correctly, magisk flashed successfully, and there were no bootloops, I go to magisk manager and see that only the ramdisk was modified. Sar and a/b were both no and the root status showed up as na. No app could detect the root.
What went wrong?
P.S SuperSU systemless dident work either
P.P.S SuperSU system puts me in a bootloop that lasts for around 15 minutes per bootloop
Bump
/\
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
jwoegerbauer said:
The most simple method to detect Android is rooted:
Code:
adb devices
adb shell
You should now see either a ‘$’ or a ‘#’. The # means Android is rooted.
Click to expand...
Click to collapse
i know how to check, my problem is my device is **** and cant be rooted. Ive heard multiple places that say the sm-t380 is a sort of "touchy" device. It dosent like rooting AT ALL
Any updates with this? I'm trying to root with the latest OS this tablet has but is not picking magisk like it patch the BOOT.img perfectly but when I flash it with odin is not detecting anything.
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
flya258 said:
I went through many guides for T380 and I get to the same point as OP and Barto604. TWRP installed success, Magisk-patched boot.img flashed success, system launches successfully, Magisk app shows "Installed N/A, Ramdisk Yes, A/B No, SAR No"
I tried running adb devices; adb shell and it shows $ so not rooted
Click to expand...
Click to collapse
Hi I am reading through the xda treads have the same thing after patching the boot except my device in root checker says successfully rooted. What I did was switch from supersu to magisk( switch superuser app). I noticed the superuser binaries have to be installed or it will not work.
In my situation I just went inside supersu app and selected switch superuser app, then supersu uninstalls itself then reboot phone and open magisk app. root checker says successfully rooted.
I don't know if I am doing it right but my phone still says successfully rooted??
Related
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
As far as I'm aware the rom should be pre rooted and all you'll need to do is install supersu from googleplay and then update the su binaries from within the supersu app.
Set it to option 4 (apps and abd) and go about installing supersu first as the app from googleplay and if no joy then as a flashable zip file.
Beamed in by telepathy.
amitrider04 said:
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
Click to expand...
Click to collapse
Did you try to flash the addonsu.zip from LineageOS website?
You must flash it to get root access in LineageOS 14.1
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Flash a stock firmware and start over.
Beamed in by telepathy.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
Are you sure you flashed the correct addonsu???
As far as i remember, the s3 doesn't have 64x, flash the normal arm version (arm32x).
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
flash supersu.zip 2.79 with twrp it worked for me
Thanks it also worked for me:laugh:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Zwolly said:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Click to expand...
Click to collapse
It works, you will get an error in recovery, but when you boot, you will get root access normally, i don't why the error happens, but it's harmless anyway.
Root fix
I'm not sure if you have fixed it yet but just in case if this helps the way I got around this is by simply downloading the latest super su zip from the official site and manually flashing via twrp kinda sucks but it works the first boot took a little though so if you try this and it takes forever for your device to not just wait because it can take up to 15 min the first time. So basically as long as you have twrp you are rooted technically it's just based on the rom wether they chose to support it if not the zip always works but you need the app too.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
S3 has arm32. So neither x86 not x64 would work. You should've flashed addonsu.zip for 32.
Sent from my Pixel XL using Tapatalk
I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.
Here's how to root the Pixel 3 running on official and stock Android 10 release, step by step :
(not tested on Pixel 3 XL but it might work the same, just use the right firmware for your device)
What do you need :
> Pixel 3 phone with Android 10
> Unlocked bootloader on your Pixel device
> Latest ADB and FASTBOOT tools on your computer
1 ) Download the latest Android 10 factory image for your device ("Blueline" is the regular Pixel 3) :
Link > Android 10 factory image
2 ) Extract the "boot.img" file on your phone
3 ) Download latest Magisk Manager application on your phone and install it :
Link > https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched
5 ) Enable adb debugging on your Pixel phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
9 ) When i'ts done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings and rebooting your phone.
Note that this guide is actually for using adaway. I don't know if it will work for any other root related feature on your phone.
Great guide, thanks!
ibolito said:
11 ) Open your Magisk Manager app and chek if everything is good, and it should be ! You can now install Adaway after you enable Systemless root in the Magisk settings.
Click to expand...
Click to collapse
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
bafforosso said:
Great guide, thanks!
I would just add not to forget to reboot again after enabling Systemless hosts in the Magisk settings and before installing Adaway (or after installing any other module)
Click to expand...
Click to collapse
Thanks its done!
I get a "This site can't be reached" message when I click the link for magisk manager in step 3. Not sure if anyone else sees it.
Thank you for making this guide!
Thanks, works perfectly!
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Oberbergler said:
I think my boot.img was not patched successfully. The original file has 64 mb while the patched one has only 30 mb. I've already pdated to Android 10. When I try to path the boot.img I get the following error: FAILED (remote: Not allowed to flash (bootb))
Could anyone please send me his patched boot.img?
Click to expand...
Click to collapse
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
If I updated via ota adb side load to 10. But used the boot.img from the factory image, would this explain why it did boot, however not one app would start. The system ui would then crash. Just trying to figure out where I screwed up. Thank you.
ibolito said:
Don't worry the new patched boot.img is 30mb, that's absolutely normal. Make sure you have unlocked your bootloader and that your phone's firmware matches the one you used to extract the boot.img. And also make sure your files are all in the same folder (adb and fastboot files + patched boot.img) and, most important of all, check if your platform tools (adb and fastboot) are up to date, then tell us if you managed to make it work.
Click to expand...
Click to collapse
Thanks man Everything was right but I forgot to update adb and fastboot. Now I have root
ignore me -- im idiot.
i am not sure if my pixel 3 is really rooted. all the apps requiring root says they are granted root access, but, for example, i cannot modify system files with a root file manager at all unlike i could with android 9. how can i confirm it is surely rooted?
So I have a problem, maybe someone can help me with.
Back in March I made the following post:
"I was running on the original September Update since I got the phone, I used this guide when I first rooted https://www.xda-developers.com/googl...r-root-magisk/
Today I decided it was time to update so I used this guide https://www.xda-developers.com/flash...-google-pixel/
Then I wanted to reroot my phone. So I bootet the TWRP image and flashed the magisk 18.1 zip. But after that I softbricked my phone and it wouldn't boot anymore.
So in my panic I flashed the TWRP zip and my phone worked again, but now everytime I try to flash the magsik zip the same thing happens, bootloop and back to flashing twrp.zip. "
After that didn't work, I tried flashing the magisk uninstaller, through twrp, but it exited with "Error 1" everytime. (Running TWRP 3.3.0)
So i decided to give up, because I had some personal stuff to take care of, but after Android 10 came out yesterday, I decided to give this another go.
I flashed the factory image without "-w" and everything is working fine. So today I followed this guide, double checked everything but after I flash the patched boot image I get stuck with a bootloop again... I can flash back the original boot image and everything works so it's not a huge deal, but right now I can't use google pay, because it says I'm rooted.
Any idea what I could do? Can't run the uninstaller and can't reroot... ???
thanks!
Have you checked if your patched boot.img matches the firmware on your phone?
Well it's the same one I used to flash the firmware.
I flashed yesterday without an issue and today I loaded that boot.img onto my phone, used the canary magisk manager to patch it and then transfered it back to my PC to flash it.
Edit: I'm thinking this might have to do with the fact that I couldn't uninstall magisk before.
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
GohanBurner said:
I went back to Pie because Viper4Android doesn't work on 10. No matter what version. The Legacy version I usually use keeps asking me to install the driver like it had on previous phones when installs were borked.
Click to expand...
Click to collapse
I had it working before I bodged a magisk module install
No luck here. The steps SEEM to work perfectly. Flashed the modified boot image, booted up fine, but magisk says it's still not installed. No root.
- Latest magisk canary
- Used the same firmware
- No errors anywhere along the way
Hey Mac users, I had to use the command fastboot flash boot_b magisk_patched.img
To get the patched image over to my phone. It worked out great. I was able to reboot,
and see the root in Magisk Manager.
YMMV
Thanks, worked like a charm on Linux with latest platform-tools! I thought I'd have to wait a lot longer to get root back on my device.
I have also tried this multiple times. No errors, but I can't edit system files or add modules.
WAS WORKING FINE WITH:
- OOS HD01AA 10.0.7 (global)
- Stock recovery (with no ADB)
- Rooted via Magisk (had some modules installed/ active)
- EdXposed & modules working fine
- Arter kernel
- Renovate ICE (v.11) Magisk ROM
WHAT I DID:
- Downloaded OTA update HD01AA 10.0.8 (did not install or reboot yet)
- Update Magisk from v20.3 to 20.4 (direct download - did not reboot yet)
- Ensured "forced encryption/ DM-Verity" etc were ticked active (the 3rd option was unticked/ inactive)
- Used Magisk Manager to "install to inactive slot (after OTA)". (No Magisk modules inactivated or uninstalled).
- Rebooted
MY PROBLEM:
- Bootloop (I can still access stock recovery menu & Bootloader/ Fastboot)
SOLUTIONS TRIED:
- Deleted cache
- Changed active slot to A &/ or B etc - neither worked
- (Resorted to, unfortunately) Reset system data (both slots A & B; but my internal data pics vids hopefully remain intact)
I'm looking to recover my previous OOS/ data if possible or retrieve the OTA update I was trying to install.
I don't have any external back-up unfortunately. My Titanium/ contacts back up are all on the "internal memory". I would like to avoid MSM tool reset thereby loosing all.
Did you have renovate ice enabled when you updated?
If so that's what's causing the problem.
Use the adb enabled recovery and remove the module
Sent from my OnePlus7TPro using XDA Labs
Yes - Renovate ICE was still enabled during the update.
Where do I get the correct version ADB enabled recovery from please? (I checked on XDA here but cannot find one for my OOS version).
elmor0 said:
Yes - Renovate ICE was still enabled during the update.
Where do I get the correct version ADB enabled recovery from please? (I checked on XDA here but cannot find one for my OOS version).
Click to expand...
Click to collapse
Never install OTA when you have modules enabled.
I guess you have to clean flash OxygenOS
elmor0 said:
Yes - Renovate ICE was still enabled during the update.
Where do I get the correct version ADB enabled recovery from please? (I checked on XDA here but cannot find one for my OOS version).
Click to expand...
Click to collapse
Try making your own or just try flashing one of those from the thread
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
(I'm using VMware as on Mac)
I have seemingly flashed stock recovery with ADB enabled (as per message on cmd window) --> when I type "adb shell" in cmd - nothing happens. I have opened the cmd window within the platform-tools folder. I have tried both in ??fastboot mode as well as in recovery mode.
Is there any way that I can confirm that I have successfully enabled adb visually on the phone itself? When I reboot to recovery it still looks exactly like stock recovery (so how to know adb enabled?).
I am trying to install either the 10.0.7 or 10.0.8 firmware .zip (I have both files). I cannot get past the 1+ start screen bootloop.
I managed to get out of bootloop by "flashboot flash boot boot.img" (my old 10.0.5 boot.img). My OOS update however succeeded to 10.0.8 global during this mess-up.
Now I had no reception signal or WiFi --> extracted & flashed boot.img of OOS 10.0.8 --> WiFi & reception signal now working fine.
I have up-to-date Magisk manager installed & managed to patch the stock boot.img.
Should I "flashboot flash" or "flashboot boot" (or both) the magisk_patched.img? I tried both ways, sometimes bootloop returned, other times rebooted fine but not rooted anymore.
Magisk (v20.4) is not installed --> when I try installation, I only get 2 options:
- Download .zip only (how to flash this if root gone?)
- Select & patch a file (which I have already done to generate the magisk_patched.img)
I am unable to flash the downloaded Magisk 20.4 .zip file as no longer rooted.
I'm not getting the option of "direct download" in Magisk. Force encryption/ AVB/ dm-verity are all ticked to preserve.
I cannot get ADB shell to work/ nor uninstall my previous Magisk modules (which may be causing the failure to re-root).
I managed to boot to modified TWRP recovery but nothing mounts therefore again unable to flash the downloaded Magisk.zip.
Please help (with step-by-step details) to gain root again - many thanks.
elmor0 said:
I managed to get out of bootloop by "flashboot flash boot boot.img" (my old 10.0.5 boot.img). My OOS update however succeeded to 10.0.8 global during this mess-up.
Now I had no reception signal or WiFi --> extracted & flashed boot.img of OOS 10.0.8 --> WiFi & reception signal now working fine.
I have up-to-date Magisk manager installed & managed to patch the stock boot.img.
Should I "flashboot flash" or "flashboot boot" (or both) the magisk_patched.img? I tried both ways, sometimes bootloop returned, other times rebooted fine but not rooted anymore.
Magisk (v20.4) is not installed --> when I try installation, I only get 2 options:
- Download .zip only (how to flash this if root gone?)
- Select & patch a file (which I have already done to generate the magisk_patched.img)
I am unable to flash the downloaded Magisk 20.4 .zip file as no longer rooted.
I'm not getting the option of "direct download" in Magisk. Force encryption/ AVB/ dm-verity are all ticked to preserve.
I cannot get ADB shell to work/ nor uninstall my previous Magisk modules (which may be causing the failure to re-root).
I managed to boot to modified TWRP recovery but nothing mounts therefore again unable to flash the downloaded Magisk.zip.
Please help (with step-by-step details) to gain root again - many thanks.
Click to expand...
Click to collapse
The rogue module is still in /data/adb/modules, unrooting does not remove the installation that's why you still have bootloop.
There are 3 ways;
1. Modded recovery
2. Boot stock img and do a factory reset
3. The slightly complicated way;
Basically booting a rooted image and in booting process it runs a command in root shell which removes the modules.
https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
If you're having problems, try tagging him with your patched image, maybe he can help you.
Sent from my OnePlus7TPro using XDA Labs
Thanks for the suggestions.
OPTION 1: I have tried with modded recoveries:
- Modded TWRP does not show or mount anything at all (slot A or B); shows 0 GB; any folders I can see I cannot delete or add any files to.
- Modded stock recovery (i.e with ADB enabled) just doesn't seem to ?flash or I'm doing something wrong for ADB shell to work. On the CMD window it says modified stock recovery has been flashed fine. Do I try the ADB shell commands in the same CMD folder?
(a step-by-step guide of how to use ADB shell in this context would really be appreciated).
OPTION 2 will wipe internal (personal) data so not keen on this (especially now that I cannot back-up my data with Titanium due to lack of root).
OPTION 3 - looks complicated for me; will try if having no luck with above 2.
elmor0 said:
Thanks for the suggestions.
OPTION 1: I have tried with modded recoveries:
- Modded TWRP does not show or mount anything at all (slot A or B); shows 0 GB; any folders I can see I cannot delete or add any files to.
- Modded stock recovery (i.e with ADB enabled) just doesn't seem to ?flash or I'm doing something wrong for ADB shell to work. On the CMD window it says modified stock recovery has been flashed fine. Do I try the ADB shell commands in the same CMD folder?
(a step-by-step guide of how to use ADB shell in this context would really be appreciated).
OPTION 2 will wipe internal (personal) data so not keen on this (especially now that I cannot back-up my data with Titanium due to lack of root).
OPTION 3 - looks complicated for me; will try if having no luck with above 2.
Click to expand...
Click to collapse
Don't bother with TWRP, it's not functional.
After flashing the modded recovery, enter recovery and type "adb shell", it should change to a #.
Sent from my OnePlus7TPro using XDA Labs
I'm getting there I think - baby steps.
Mistake I did with modded stock recovery was that I was not in recovery mode (which looks the same as un-modified stock recovery) whilst trying "adb shell" via CMD.
Initially, I got messages of adb server version does not match client & daemon cannot connect etc. Executing "adb kill-server" seemed to get rid of these errors.
Finally I could "adb shell" to generate the #.
When I try "ls -Ral data/adb/modules" I get message of "no such file or directory".
Just trying "ls -Ral data/" gives me:
- total 0 drwxr-xr-x 2 root root 40 2020-02-15
drwxr-xr-x 28 root root 1100 1970-01-01
How shall I proceed next?
elmor0 said:
I'm getting there I think - baby steps.
Mistake I did with modded stock recovery was that I was not in recovery mode (which looks the same as un-modified stock recovery) whilst trying "adb shell" via CMD.
Initially, I got messages of adb server version does not match client & daemon cannot connect etc. Executing "adb kill-server" seemed to get rid of these errors.
Finally I could "adb shell" to generate the #.
When I try "ls -Ral data/adb/modules" I get message of "no such file or directory".
Just trying "ls -Ral data/" gives me:
- total 0 drwxr-xr-x 2 root root 40 2020-02-15
drwxr-xr-x 28 root root 1100 1970-01-01
How shall I proceed next?
Click to expand...
Click to collapse
Do you get to enter a pin when entering recovery? If not you're most likely using a recovery for an older version/other version.
Sent from my OnePlus7TPro using XDA Labs
elmor0 said:
I'm getting there I think - baby steps.
Mistake I did with modded stock recovery was that I was not in recovery mode (which looks the same as un-modified stock recovery) whilst trying "adb shell" via CMD.
Initially, I got messages of adb server version does not match client & daemon cannot connect etc. Executing "adb kill-server" seemed to get rid of these errors.
Finally I could "adb shell" to generate the #.
When I try "ls -Ral data/adb/modules" I get message of "no such file or directory".
Just trying "ls -Ral data/" gives me:
- total 0 drwxr-xr-x 2 root root 40 2020-02-15
drwxr-xr-x 28 root root 1100 1970-01-01
How shall I proceed next?
Click to expand...
Click to collapse
Try /data/adb/modules. A "/" is missing
Tried to make my own modified recovery.img with ADB enabled using s3axel's instructions --> clearly I messed up as ended up with Qualcomm crash-dump error.
Thankfully, GrayJack's ADB enabled recovery worked. I managed to delete the culprit Magisk modules (Renovate ICE; xXx from previous installation; ?viper4android etc) by following this guide guide.
Now the patched Magisk .img flashed fine; rooted again (yay) - thank you @ Lossyx for persisting with me.
Back on Renovate-ICE (v.12 now) & arter97 kernel.
Phew!
What would i Do after Unlocking Bootloader?
Please provide Required file Links
Thanks in Advance
Bump :fingers-crossed:
@blanksh07
To root Android unlocking device's boot-loader is NOT needed: You always can obtain a temporary root by patching adbd.
0
The above link didn't worked for rooting.
Anyone else tell me how to root this device or how to add it to xda device list?
@blanksh07
The Oppo K3 is based on Android 9, hence I think it has dm-verity/AVB enabled by default. As long as this lock isn't got disabled NOTHING will work as expected.
@jwoegerbauer
How can I disable this and is there any twrp available for this phone so I can flash magisk..!?
blanksh07 said:
@jwoegerbauer
How can I disable this and is there any twrp available for this phone so I can flash magisk..!?
Click to expand...
Click to collapse
1.
Code:
adb devices
adb disable-verity
adb reboot
2.
I never installed TWRP nor Magisk in order to root a phone. Yes, this may in the end lead to a positive result, but is in my opinion an unnecessary overkill with regards to get installed 1 ( ONE ) binary in Android - the su binary what is ~100 KB of size.
BTW: You compile TWRP by yourself. How-to is described here.
1. I have tried above abd commands and got an erro "verity cannot be disabled/enabled - USER build".
2. When I try to reboot to bootloader, the fastboot screen flash for 2 seconds and rebooted to system , any help with that?
you can see tutorial in here.
https://www.getdroidtips.com/root-oppo-k3/
0
No luck!