Hey guys
I am currently having Android 6.0.1 installed on my Oneplus X (Security Patch: Nov. 2016). Unfortunately i lost my root privileges while updating the phone, and KingRoot isn't yet able to enable root again. TWRP also doesn't really work for me, because always when I'm trying to install it via fastboot it says error (remote: dtb not found), guess I'm trying to install an incompatible version, so in case you know the right version or where to find it please tell me. But if you - just like me - don't know the right version or if it even doesn't exist i developed a Plan B. I wanted to 'hack' my own phone via DIrtyCow and enable root. Wich also works for like 80%. If I'm executing the command run-as -exec whoami i get the respone that I'm the root account, in comparison if i just type whoami it says that I'm the user shell. BUT if I'm trying run-as -exec su it says that it hasn't found su so, my question is: How can I install su, or just execute something that gives me root privileges when I'm already haven 'semi-root' privileges?
TheAustrian1337 said:
Hey guys
I am currently having Android 6.0.1 installed on my Oneplus X (Security Patch: Nov. 2016). Unfortunately i lost my root privileges while updating the phone, and KingRoot isn't yet able to enable root again. TWRP also doesn't really work for me, because always when I'm trying to install it via fastboot it says error (remote: dtb not found), guess I'm trying to install an incompatible version, so in case you know the right version or where to find it please tell me. But if you - just like me - don't know the right version or if it even doesn't exist i developed a Plan B. I wanted to 'hack' my own phone via DIrtyCow and enable root. Wich also works for like 80%. If I'm executing the command run-as -exec whoami i get the respone that I'm the root account, in comparison if i just type whoami it says that I'm the user shell. BUT if I'm trying run-as -exec su it says that it hasn't found su so, my question is: How can I install su, or just execute something that gives me root privileges when I'm already haven 'semi-root' privileges?
Click to expand...
Click to collapse
100 millions question which ROM you are on right now? And build date please.
farooque7508 said:
100 millions question which ROM you are on right now? And build date please.
Click to expand...
Click to collapse
Currently I'm on the Stock Rom.. but I also had Cyanogenmod on it. The BuildNumber is ONE E1003_14_161107, the Kernel Version is 3.4.0-perf-ge4f53e4/[email protected] #1/Mon Nov 7 15:13:33 CST 2016
Hope these informations help you.. if not feel free to ask for further details
EDIT: Here's a screenshot from the Phone-Info section in the preferences (i didn't want to write the baseband version here ) :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TheAustrian1337 said:
Currently I'm on the Stock Rom.. but I also had Cyanogenmod on it. The BuildNumber is ONE E1003_14_161107, the Kernel Version is 3.4.0-perf-ge4f53e4/[email protected] #1/Mon Nov 7 15:13:33 CST 2016
Hope these informations help you.. if not feel free to ask for further details
EDIT: Here's a screenshot from the Phone-Info section in the preferences (i didn't want to write the baseband version here ) :
Click to expand...
Click to collapse
Did you tried flashing modified SuperSU.zip?
TheAustrian1337 said:
Currently I'm on the Stock Rom.. but I also had Cyanogenmod on it. The BuildNumber is ONE E1003_14_161107, the Kernel Version is 3.4.0-perf-ge4f53e4/[email protected] #1/Mon Nov 7 15:13:33 CST 2016
Hope these informations help you.. if not feel free to ask for further details
EDIT: Here's a screenshot from the Phone-Info section in the preferences (i didn't want to write the baseband version here ) :
Click to expand...
Click to collapse
tRy flashing this unofficial twrp for oos 3.x.x in fastboot mode https://www.androidfilehost.com/?fid=457095661767115910 after that try flashing this modded SuperSU for oos 3.x.x https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
Be sure you have USB Debugging and OEM unlock ON on the dev option.
Verify if fastboot command is OK. Try ion an old Win7 if you can.
Post the result here.
WORKS!!
The modified TWRP and SuperSU worked fine for me I flashed it via fastboot within WIndows 7. THANK YOU SOO MUCH <3 <3 <3 <3
TheAustrian1337 said:
The modified TWRP and SuperSU worked fine for me I flashed it via fastboot within WIndows 7. THANK YOU SOO MUCH <3 <3 <3 <3
Click to expand...
Click to collapse
Glad it did. thanks button is in lower right corner lol
link broken
cva_kabil said:
Glad it did. thanks button is in lower right corner lol
Click to expand...
Click to collapse
hey the link for the modded supersu: https://drive.google.com/file/d/0B4K...RuVnRjUUE/view doesn't work anymore. Could you please reupload it?
Related
somebody got root?
CWMRecovery or TWRP no more?
so soon compile)
I also would like to know
Does anyone have stock recovery?
hello
I too am interested
standak14 said:
Does anyone have stock recovery?
Click to expand...
Click to collapse
https://docs.google.com/folder/d/0B6WBFlAKqe30YnFxVHVHMFo1X0k/edit
SPSPaWn said:
https://docs.google.com/folder/d/0B6WBFlAKqe30YnFxVHVHMFo1X0k/edit
Click to expand...
Click to collapse
Thanks. Currently there are no recovery does not work? Thank you for your work
ТAMPERED - shows that the guarantee came off ( as in the last boot from SGS4 - WARANTY BIT 1)
But in our case, it can be cured, only writes RELOCKED - and thus guarantee in place) (handed over to RELOCKED than one device )
1. Set the boot (unsecured) - fastboot flash boot boot_init.img
2 . Boot and enable developer mode ( repeatedly click on the " Version - > Advanced- > Build Number " )
3 . Download the revone: http://revolutionary.io/revone
4 . Load on the device - adb push revone /data/local/tmp/
5 . We go in the shell - adb shell (c boot unsecured all root- s commands work without root )
6. In shell :
cd /data/local/tmp
chmod 755 revone
./revone -t - TAMPERED disappear before your next intervention
7. Being in shell reboot into fastboot - reboot bootloader
8. Flash stock boot and recovery
fastboot flash boot boot_stock.img
fastboot flash recovery recovery_stock.img
9. Lock bootloader
fastboot oem lock
10 . EVERYTHING in the loader will only write RELOCKED
P.S. For those who have unlocked the bootloader and who writes TAMPERED
development HTC Desire 601/ZARA in my drive
+1 Owner of Zara looking for SU...
Make us a sectiooon, please xda!
And SPSPaWn, have you rooted your zara yet?
Hello! I am searching for su too. Any help is welcome.
Root is. But without CWMRecovery description will be. Difficult)
Dumps did everything. Even deodex did too) stuck on recover
p.s. Compiled pieces 20 neither went. Maybe put the protection (
Concerning CMWRecovery or TWRPRecovery thoughts ran!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who is strong in linux all thoughts are welcome, the development environment and source CM - 10.1, 10.2, Jellybean ready for compilation .......
all recovery - it is not possible to get there, go into overdrive (fastboot erase cache - does not help ((((
repository development HTC Zara - http://goo.gl/PpKL8T - who can continue in tandem?)
p.s. no custom recovery obtaining root (safely) is not possible)
SPSPaWn said:
Concerning CMWRecovery or TWRPRecovery thoughts ran!
View attachment 2401666
Who is strong in linux all thoughts are welcome, the development environment and source CM - 10.1, 10.2, Jellybean ready for compilation .......
all recovery - it is not possible to get there, go into overdrive (fastboot erase cache - does not help ((((
repository development HTC Zara - http://goo.gl/PpKL8T - who can continue in tandem?)
p.s. no custom recovery obtaining root (safely) is not possible)
Click to expand...
Click to collapse
Regarding the screenshot, did you succesfully obtain root access?
djtinxo said:
Regarding the screenshot, did you succesfully obtain root access?
Click to expand...
Click to collapse
Yes, but root it is temporary
SPSPaWn said:
Yes, but root it is temporary
Click to expand...
Click to collapse
Instructions, please
standak14 said:
Instructions, please
Click to expand...
Click to collapse
instructions will not be
not yet compile recovery
SPSPaWn said:
instructions will not be
not yet compile recovery
Click to expand...
Click to collapse
Maybe someone in this thread
http://forum.xda-developers.com/showthread.php?t=2456795&page=2
Click to expand...
Click to collapse
could help you to make custom recovery for this device
I'm looking forward for custom ROM on this device cause I'm planning to buy one
Guys who are nice enough and have spare time, please do a clean system dump for me for some sort of dev purpose, I mean in factory reset status. Use cwm and do a backup, zip/7zip it and upload it to google drive or dropbox. Thanks.
**
TheEndHK said:
Guys who are nice enough and have spare time, please do a clean system dump for me for some sort of dev purpose, I mean in factory reset status. Use cwm and do a backup, zip/7zip it and upload it to google drive or dropbox. Thanks.
Click to expand...
Click to collapse
Is it possible to use CWM, because Desire 601 is not yet fully rooted as mentioned by SPSPaWn?
He said he could only obtain temporary root, is it possible/safe to install CWM?
NEW: CF-Auto-Root flashable: http://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip
Will update this post soon-ish!
--- old post follows ---
This took a few hours more than I had hoped, because it's both the first firmware on a new Android version as well as 64-bit. While there have been 64-bit builds of the SuperSU binary for a while now, they were untested until now, and unsurprisingly there were a few (minor) issues to fix before it worked properly.
As such, this root includes SuperSU v2.18, which is a special build for the Nexus 9, which you should definitely not try to put on any other device, nor should you put an older version of SuperSU on the Nexus 9.
I have not yet updated the CF-Auto-Root framework to be able to patch the kernels live (needed on 5.0) or support 64-bit, so this is a more manual root than usual.
It pretty much comes down do:
- enable oem unlocking in Android's developer options
- fastboot oem unlock
- fastboot boot inject.img
- fastboot flash boot patched.img
The included README.TXT is a little bit more extensive, but not by much, and if you don't know what the above does then maybe you shouldn't bother (yet).
Please note that many root apps will have issues with both Android 5.0 as well as 64-bit. There may also be more issues with SuperSU on 64-bit that I have not found yet.
Guess it's time to fix up CFAR and update the new How-To SU with all the 5.0 specifics. That'll all take some time, though.
Click to expand...
Click to collapse
^^^ from my G+
Download:
http://download.chainfire.eu/592/CF-Root1/Nexus9-root-SuperSU-v2.18.zip
Knew it wouldn't take long! Thanks!
This came faster than my tablet
Awesome. Just got mine today and already unlocked, just waiting on word from you to root. Can't wait!
Sent from my Nexus 9
can’t wait
need root so bad
Boom
Rooted ?
nexus 9 rooted ty so much
A quick video guide for those of you that prefer visual aids.
Now we need busybox
Can't get it to work...
Booted both images just as instructed. Then first full boot after booting the images, it won't accept touch at the encryption screen. Hold the power button then it reboots and boots fine. Open SuperSU app and it says no root binary... I'm still fidgeting with it.
leviwhite9 said:
Booted both images just as instructed. Then first full boot after booting the images, it won't accept touch at the encryption screen. Hold the power button then it reboots and boots fine. Open SuperSU app and it says no root binary... I'm still fidgeting with it.
Click to expand...
Click to collapse
had the same issue. went back to the stock boot.img, disabled security and set to swipe, reflashed inject.img & patched.img. worked good, turned security back on but didnt choose to enforce on start up. guessing might be an issue with that..? havent tried with that re-enabled.
Oh yea!! Trying it right now!
eurominican said:
Oh yea!! Trying it right now!
Click to expand...
Click to collapse
Working good
Already edodexed the ROM
renzyyy said:
had the same issue. went back to the stock boot.img, disabled security and set to swipe, reflashed inject.img & patched.img. worked good, turned security back on but didnt choose to enforce on start up. guessing might be an issue with that..? havent tried with that re-enabled.
Click to expand...
Click to collapse
That was the issue! Turned off security and rebooted the two images and I had SU access. Turned pattern lock with boot enforcement and it broke SU. It is the boot time security that breaks this.
leviwhite9 said:
That was the issue! Turned off security and rebooted the two images and I had SU access. Turned pattern lock with boot enforcement and it broke SU. It is the boot time security that breaks this.
Click to expand...
Click to collapse
Also, for anyone that missed this or didnt know about it (like me), you have to tick off "Enable OEM unlock"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice work! Seems to work well so far - now as others stated I just need busybox - seems Titanium Backup is not detecting root and needs it? Or TB could be incompatible.
Sean09 said:
Nice work! Seems to work well so far - now as others stated I just need busybox - seems Titanium Backup is not detecting root and needs it? Or TB could be incompatible.
Click to expand...
Click to collapse
Get the test build of TB
I have it and its working well
USBhost said:
Get the test build of TB
I have it and its working well
Click to expand...
Click to collapse
Thanks very much, got test 6 from their twitter and it works!
Is there a recovery yet??
I've never done one of these before so I'll give it my best shot. It assumes you know how to get ADB working on your watch.
Go here for adb help.
**This only works on bootloader unlocked, rooted devices. The tool at the link above can help you achieve this requirement.** -thanks 7dk
Download Link: Here
MD5 Checksum: AC0F2B4AA2C1B5199789F2770CDA5B06
Directions:
0) YOU MUST BE ON ANDROID WEAR VERSION 4.4W2 (BUILD KNX01Q) IN ORDER TO FLASH THIS OTA
1) Install ADB and successfully connect to your watch over ADB.
2) Rename the install ZIP to 'update.zip' if not already done so.
3) Move the ZIP to your ADB directory.
4) Open a command prompt in your ADB directory and follow these commands:
adb push update.zip /sdcard/update.zip
adb shell
su
cp /sdcard/update.zip /cache/update.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/update.zip' >> /cache/recovery/command
reboot recovery
Your watch should now reboot and begin updating.
Thanks to reddit users z0mbiexx and TjPhysicist for getting the link and install working.
Thank You sir.
crazyeats said:
Thank You sir.
Click to expand...
Click to collapse
No problem. Let me know if it works for you.
works only on rooted device, so bootloader must be unlocked, and watch must be pre-rooted.
Works with out any problem! thnx! :good:
I keep getting /system/bin/sh: su: not found
127:[email protected]:/ $
I assume I need the device rooted?
EDIT: post above me clarifies that
jackie_jagger said:
I keep getting /system/bin/sh: su: not found
127:[email protected]:/ $
I assume I need the device rooted?
EDIT: post above me clarifies that
Click to expand...
Click to collapse
Thanks for letting me know! I updated the post to include this requirement.
cmdoptesc47 said:
Thanks for letting me know! I updated the post to include this requirement.
Click to expand...
Click to collapse
Nah mate, thank YOU for all the effort for this post. My watch just completed flashing the update and now I'm on the bootscreen waiting for boot. Shouldn't be long now.
EDIT: Android is upgrading screen. <3
cmdoptesc47 said:
No problem. Let me know if it works for you.
Click to expand...
Click to collapse
Worked great sir! I was unlocked and rooted. I did have to flash stock recovery before I could continue of course. Great stuff. Much appreciated!
KGW42Q --> LWX48P
My G Watch is going in fastboot mode but is stuck at <waiting for device> when trying to unlock bootloader. Any help ?
Hi, I´m in Gohma 1.2 rom, can I upgrade from this Rom directly?
Thanks in advance for you effort.
Ashutos1997 said:
My G Watch is going in fastboot mode but is stuck at <waiting for device> when trying to unlock bootloader. Any help ?
Click to expand...
Click to collapse
It sounds like your computer isn't recognizing your watch as an ADB device when it's in fastboot mode. Usually just monkey around in device manager when this happens, but I'm not great at fixing this issue. I'd look through the comments in that thread for more help.
juansur66 said:
Hi, I´m in Gohma 1.2 rom, can I upgrade from this Rom directly?
Thanks in advance for you effort.
Click to expand...
Click to collapse
I used the tool in the post to restore to stock before I updated just to be safe. It might work without a restore, but I've never tried it before. I'd probably recommend a restore, but you're welcome to give it a shot.
Nice
cmdoptesc47 said:
It sounds like your computer isn't recognizing your watch as an ADB device when it's in fastboot mode. Usually just monkey around in device manager when this happens, but I'm not great at fixing this issue. I'd look through the comments in that thread for more help.
Click to expand...
Click to collapse
The device gets recognized in adb devices but not in fastboot.
cmdoptesc47 said:
I used the tool in the post to restore to stock before I updated just to be safe. It might work without a restore, but I've never tried it before. I'd probably recommend a restore, but you're welcome to give it a shot.
Click to expand...
Click to collapse
Thanks for quick reply, I will wait cause I´m little nob.
juansur66 said:
Thanks for quick reply, I will wait cause I´m little nob.
Click to expand...
Click to collapse
I just used the tool and chose option 6 (I think. The the one that says restore)
Ashutos1997 said:
My G Watch is going in fastboot mode but is stuck at <waiting for device> when trying to unlock bootloader. Any help ?
Click to expand...
Click to collapse
If you are using Linux try switching to root user, if Windows right click cmd and run as administrator
good job
very good!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Paulo_Diablo said:
If you are using Linux try switching to root user, if Windows right click cmd and run as administrator
Click to expand...
Click to collapse
Still same prob
Android DollhouseThe Definitive Android Flashtool.
This is the support thread for Pixel 6. If you have another device, please check the other threads:
Pixel 2XL: Support Thread
Pixel 6 Pro: Support Thread
Click to expand...
Click to collapse
I'm releasing the first user-facing preview of this tool, which is a convenient wrapper for common ADB/Fastboot controls.
It already comes preloaded with ADB and Fastboot binaries. There's no need to download anything else.
You need this .net runtime to run it: https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-desktop-5.0.11-windows-x86-installer
For now, this is the first test run, which is Windows only. Mac OS + Linux versions will be released separately depending on how this performs.
Full cross-platform compatibility is planned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
For now, it is still a work in progress. I would like your feedback on this tool. Post here a screenshot of your Device info so I can improve compatibility with your device! Make sure to blur/hide your IMEI!
It includes an auto-updater so you will definitely be getting the latest improved release whenever I make changes.
Download + Source code : Github
General Pixel Development Channel : Telegram
Pixel 6 & 6 Pro Official Chat : Telegram
Click to expand...
Click to collapse
I already have access to the 6 and 6 Pro, although I don't use telegram because I already have enough ways for people to contact me lol
KaptinBoxxi said:
I already have access to the 6 and 6 Pro, although I don't use telegram because I already have enough ways for people to contact me lol
Click to expand...
Click to collapse
Can you use ADB / USB debugging? If possible, please show me the output of
adb devices -l
I will be picking up my Pixel 6 today when BestBuy let's me, I can post the output of this for you. I really want to get this thing running Lineage or CalyxOS asap, so I am open to helping out with development. I see that Lineage already has a stable Android 12 build, so it seems that may be coming first.
Dollscythe said:
Can you use ADB / USB debugging? If possible, please show me the output of
adb devices -l
Click to expand...
Click to collapse
Hi, I have a pixel 6, and here the result of : adb devices -l
theoh88 said:
Hi, I have a pixel 6, and here the result of : adb devices -l
View attachment 5443579
Click to expand...
Click to collapse
Awesome. Tool is out. Download links uploaded
Updated with .net runtime.
Just downloaded this tool, it loaded right up and found my Pixel 6, thank you!
Updated! Just open the program, it should automatically update to the latest version with pixel 6 support.
Dollscythe said:
Updated! Just open the program, it should automatically update to the latest version with pixel 6 support.
Click to expand...
Click to collapse
to install, just adb devices -l only?
trai_th said:
to install, just adb devices -l only?
Click to expand...
Click to collapse
you dont need that anymore
Dollscythe said:
you dont need that anymore
Click to expand...
Click to collapse
I installed .net but I can't run the application, what should I do?
Have the same issues. Have install net but can not start the Tool. Get always the rror i must flash net but i have it.
Hot-Proton said:
Have the same issues. Have install net but can not start the Tool. Get always the rror i must flash net but i have it.
Click to expand...
Click to collapse
I installed from the link provided above and it works now.
Hot-Proton said:
Have the same issues. Have install net but can not start the Tool. Get always the rror i must flash net but i have it.
Click to expand...
Click to collapse
I link the necessary .net binaries in the thread...
Stream the screen works pretty well, just low quality for some reason. My bootloader is not unlocked yet, I bought the device from T-Mobile so God-knows how long it will take.
You say this tool only works on Windows, but you use .NET 5.0 to build it, which is cross platform. What makes it Windows only?
I see there's been no updates or information since November, what is the current state of this project?
Hello everyone,
Recently I found my old galaxy S III GT-I9300 and wanted to "recycle" it by putting a Lineage ROM.
After installing the ROM (installed just fine), I wanted to use Magisk.
I took the official Magisk APK file from GitHub and added the ".zip" extension to it.
When flashing trough TWRP, there was no error, but when I reboot the phone, the Magisk app was shown but I had no root access.
I tried to flash it using the boot.img methods, but I had the same problem: Magisk did not detect any root access.
I checked if magisk could be installed on this ROM and found out that it can.
Now, I've changed my ROM several times, always with the same issue.
Please help me. I'm struggling for a month now, and I still don't know what's going on.
=========
my device
=========
model : Samsung Galaxy S III GT-I9300
android version : android pie (9)
rom : lineage 16 : link
magisk version : latest (v25.2) (flashed by TWRP and patched boot.img method)
modification : recovery (twrp 3.6.0_9-0, link)
=========
I provide my logs too. (only magisk startup beacause I can't upload my recovery logs)
thank you in advance for your help.
maybe like that...
CyberNautica said:
Hello everyone,
Recently I found my old galaxy S III GT-I9300 and wanted to "recycle" it by putting a Lineage ROM.
After installing the ROM (installed just fine), I wanted to use Magisk.
I took the official Magisk APK file from GitHub and added the ".zip" extension to it.
When flashing trough TWRP, there was no error, but when I reboot the phone, the Magisk app was shown but I had no root access.
I tried to flash it using the boot.img methods, but I had the same problem: Magisk did not detect any root access.
I checked if magisk could be installed on this ROM and found out that it can.
Now, I've changed my ROM several times, always with the same issue.
Please help me. I'm struggling for a month now, and I still don't know what's going on.
=========
my device
=========
model : Samsung Galaxy S III GT-I9300
android version : android pie (9)
rom : lineage 16 : link
magisk version : latest (v25.2) (flashed by TWRP and patched boot.img method)
modification : recovery (twrp 3.6.0_9-0, link)
=========
I provide my logs too. (only magisk startup beacause I can't upload my recovery logs)
thank you in advance for your help.
Click to expand...
Click to collapse
ive had the same issue with lineageos19. the problem is you cant just install magisk it will not work. it needs to be patched into the build. just take this one it instead:, it has magisk preinstalled: https://sourceforge.net/projects/re...RR-N-v5.8.5-20171217-i9300-Final.zip/download
best rom for s3 imo.. and then dont update magisk it will also break. just leave as it is. "linux"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok. Thanks for your help. I'll try.
I found something interesting... When I installed the Magisk app, it didn't allow me to install modules or manage root access. However, when I opened the Android terminal app and typed the "su" command, the "grant root access" notification from Magisk popped up on the screen. I was very curious, so I tried to install a root browser, and it worked! I had root access. However, in this case, because I wanted modules, it was not very helpful for me.
Maybe a glitch to report idk...
CyberNautica said:
I found something interesting... When I installed the Magisk app, it didn't allow me to install modules or manage root access. However, when I opened the Android terminal app and typed the "su" command, the "grant root access" notification from Magisk popped up on the screen. I was very curious, so I tried to install a root browser, and it worked! I had root access. However, in this case, because I wanted modules, it was not very helpful for me.
Maybe a glitch to report idk...
Click to expand...
Click to collapse
when magisk fails to install it may still give you root access. with a faulty installation you may also get su / root even without prompt / grant. like a perm root. there are also several steps on uninstallation. removing the app does not remove su.