Hey, everyone, I'm hoping someone can help me with this issue. So, I was avoiding any updates because I didn't want to lose root. Well, I eventually did update Lineage and lost root. Now for some reason I can't regain it. I have a OnePlus 6T (T-Mobile, bottloader unlocked, obviously ), Linkage 17, and Magisk. Originally I flashed TWRP as a temp recovery, installed Magisk and Lineage (and Root Checker), and everything was fine - until the update. Now when I try to sideload with ADB nothing happens. I just receive a CMD error "ADB: requires an argument..." Long story short. I'd like to know how I can just completely start over, from scratch, flash different OS and keep root. Any help would be appreciated. Thanks in advance.
Do you still have twrp as recovery?
Brettroth said:
Do you still have twrp as recovery?
Click to expand...
Click to collapse
No, Lineage has installed itself as the recovery. I still have TWRP (the app) on my phone, but whenever I try to do anything with it, it crashes.
joshua97542 said:
No, Lineage has installed itself as the recovery. I still have TWRP (the app) on my phone, but whenever I try to do anything with it, it crashes. When I look it up to my laptop (the same one I used to root and install everything, ADB will recognize my device, I can run commands, but something won't allow me to actually install anything. I receive "and.exe: requires an argument". I've tried every which way I could think of to try and make it install, but nothing is working.
Click to expand...
Click to collapse
Couldn't you just use fastboot TWRP?
Related
According to the following post, I should be able to gain root on my encrypted phone.
wgspoelstra said:
Yes, decryption is broken right now. On all versions of TWRP available, that support Oxygen OS 3.x.x, decryption is non-functional.
I have a workaround for flashing zips with an encrypted phone:
Boot into recovery, flash SuperSU over ADB Sideload, reboot phone.
You now have working root. Any zips you want to flash, place them in /system/media folder.
I use Root Explorer for this. When you boot back into recovery, mount /system and navigate to /system/media folder.
This way you can still flash all zips you want without decryption.
Click to expand...
Click to collapse
But I am having issues. Most notably, ADB does not recognize my phone unless I connect while in the OS or in stock recovery. If I connect while using any custom recovery (I've tried Hybrid and a few versions of TWRP), ADB does not list my phone when I run ADB devices. It's also very wonky trying to get stock recovery back on my phone afterwards, but that's a different issue.
While attempting to flash SuperSU when using stock recovery, the command sends the file and the phone begins the "update". It runs for about a second and then I get a "Installation Failed" message on my phone's screen. I've tried many different versions of SuperSU.
My current setup is the latest OOS (3.0.2) and stock recovery. The device is encrypted. My bootloader is unlocked, but I do not have root.
Could someone please help me out here? I have to have encryption on the phone for my work, but I really want to have root as well. Being able to customize my phone is why I went with OnePlus, but it's not proving to be any better than my Samsung Galaxy S4!!! Please help!
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377
I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode
I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.
I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?
Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.
Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.
Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)
I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.
highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?
sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here
Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.
Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.
So, according to you... Which is better? SuperSU or Magisk?
SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.
Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.
[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?
Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.
Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!
bigbraintime said:
Galaxy S8 Exynos [SM-G950FD] Android Oreo 8.0.0
Hello. it's my first time posting here. So I've had a successful attempt at flashing TWRP and Magisk into my phone. Today I accidentally plugged in my charger while it was in the process of rebooting, so it entered my device into kind of a bootloop. I solved this by going into Download Mode and pressing 'Cancel', which prompted my device to successfully reboot and work again.
The problem is that I've somehow lost my root. None of my apps can get root access, CPU-Z says no root available, and Magisk Manager said "Magisk is not installed". Idk how I got to this because yesterday all was working, I assume it's because I got a bootloop or went into Download Mode.
I tried to install the official Magisk ZIP file from the Manager, go into recovery mode, and flash it via TWRP. Unfortunately this didn't work. This is the only solution I can come up with besides reflashing Stock and having to flash Magisk again and wipe all my current data. If anyone has any suggestions please comment down below as I'm kinda stuck rn. They would be greatly appreaciated!
Click to expand...
Click to collapse
Check out this guide. It may be of some use
https://www.didgeridoohan.com/magisk/HomePage
spawnlives said:
Check out this guide. It may be of some use]
Click to expand...
Click to collapse
Thanks. I tried the methods listed in the "Lost root randomly" section and unfortunately they didnt work. Do you have any other ideas? Maybe I could "Select and Patch a File" in Magisk's Install but afaik Magisk doesnt have its img./tar. file.
I should probably just flash a fresh stock and redo the root process, but then my data will be wiped and I dont really want that lol
bigbraintime said:
Thanks. I tried the methods listed in the "Lost root randomly" section and unfortunately they didnt work. Do you have any other ideas? Maybe I could "Select and Patch a File" in Magisk's Install but afaik Magisk doesnt have its img./tar. file.
I should probably just flash a fresh stock and redo the root process, but then my data will be wiped and I dont really want that lol
Click to expand...
Click to collapse
Have you tried the uninstaller through magisk or twrp then try again with magisk.
When trying to re-install magisk do you get any errors.
https://github.com/topjohnwu/Magisk/releases
Also if worried about losing apps/data do a backup before trying anything.
The easiest way is to flash firmware and start from scratch again but backup first.
I'm on Android 10. I unlocked the bootloader.. easy.. I downloaded the corresponding file for my device, software channel, version. Ran the boot img through magisk manager. So I have the patched boot img. Before I go further with trying to flash it through fastboot, I was wondering would this successfully root my device? I'm hesitant because I haven't came across anyone discussing there success in doing this with Android 10. I really don't want to proceed until I know I'm ok to go ahead. Thoughts?
Install Twrp, flash Magisk latest zip through twrp, done
HueyT said:
Install Twrp, flash Magisk latest zip through twrp, done
Click to expand...
Click to collapse
Sorry to butt in but that did not work for me. Rooting with magisk removed my installed twrp. Could that be a bug in android 10 or latest magisk?
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
HueyT said:
fastboot flash recovery twrp.img should permanently install twrp recovery into op7t and Magisk flash should not replace it. If you flash oos10 after that then stock recovery will replace twrp recovery
Click to expand...
Click to collapse
I was busy with other things and only just came back to this topic. I agree with you, HueyT, Magisk rooting
(which I do according to the Magisk directions which say to patch the boot.img and then flash it)
should not remove the permanent twrp installation on my phone. But it does
remove it on my phone! I've tried it repeatedly.
What I end up with is a rooted Moto G7 running android 10 and when I :
—power off completely
—volume down + power takes me to the stock recovery (not twrp)
—in that stock recovery if I go to the 'recovery' option I get the open android with red exclamation mark. Happens every time.
—long power hold then reboots phone to rooted android 10.
What I have not tried yet is to permanently install twrp again and then, in twrp install Magisk 23 zip. Maybe that will allow me to keep twrp installed.
Do you think so?
It is just frustrating because this is my main phone and I can't afford to mess it up.
Any other suggestions on how to keep twrp installed on the Magisk rooted phone greatly appreciated.
Thanks for replying.
Definitely
HueyT said:
Definitely
Click to expand...
Click to collapse
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Definitely
HueyT said:
Definitely
Click to expand...
Click to collapse
A man of few words...
Yep
maybeme2 said:
Which I interpret as you agreeing I should try installing the Magisk zip from within twrp.
(That is not what the Magisk instructions say to do).
I will try that later today when I get a chance.
I have also not flashed copypartitions.zip. Should I?
Click to expand...
Click to collapse
That worked.
Rooting by installing Magisk.zip from within TWRP allowed me to both root and retain the TWRP installation.
Thank you HueyT.
NP
It's been two years but I did try injecting Magisk from within TWRP. I've also downloaded "factory" images and rooted those, them installed them. If I remember right, I did the injection method with this G7. It's the best way IMHO because the installed image is tailored your your device.
Over the last two years, the Pie around here has been fantastic.
shadow460 said:
Over the last two years, the Pie around here has been fantastic.
Click to expand...
Click to collapse
You can say that again. I've had several system crashes with 10, something I've never had with pie. Even after clearing cache, updating all apps, etc. So has my wife on her own unrooted G7 which just accepted Moto's own ota update to 10.
I do have a TWRP nandroid backup that I did just before flashing 10 and I've often considered going back to pie. But I worry about 'something' else going wrong like it did when moving to 10. It's my main phone and I can't afford to go through all I went through moving to a rooted 10. Wish I hadn't bothered.