I'll do this may be a dumb question, but I'd there any way to install TWRP without a computer? I left for work this morning and didn't notice that TWRP didn't stick, and I'd like to root and setup my phone. I don't have a computer that I can use at work.
It's the any way to install TWRP with just my phone?
GatorsUF said:
I'll do this may be a dumb question, but I'd there any way to install TWRP without a computer? I left for work this morning and didn't notice that TWRP didn't stick, and I'd like to root and setup my phone. I don't have a computer that I can use at work.
It's the any way to install TWRP with just my phone?
Click to expand...
Click to collapse
If you're rooted then use flashify
Sent from my Nexus 6P using Tapatalk
GatorsUF said:
I'll do this may be a dumb question, but I'd there any way to install TWRP without a computer? I left for work this morning and didn't notice that TWRP didn't stick, and I'd like to root and setup my phone. I don't have a computer that I can use at work. It's the any way to install TWRP with just my phone?
Click to expand...
Click to collapse
Not without being rooted. Flashify works just fine for this if you are already rooted. Next time, before you start, copy SuperSU to the root of your phone. Then after you fastboot flash recovery, do a reboot recovery (to TWRP) and then flash SuperSU before you boot to system. This way TWRP will stick.
Related
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
GatorsUF said:
I tried updating to the new 4.2 ota, I installed stock ROM then booted then back to recovery to install 4.2 update. I lost root as expected, however my ota root keeper says the is not root backup file even though I ran it before doing all that. Not sure what happened.
On top of that I can't reboot into recovery without going through boot loader. It seems as though the update removed my custom recovery too.
I could easily fix all this if I were home, but I am at work today...no adb access. Is there a way to fix root and recovery without a computer?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
To enable ADB to go:
Settings-> About Tablet-> Click Build Number for Easter Egg Multiple times! BOOM!
I am not sure if there's a way of rooting without PC and custom recovery.
Hi guys, I have successfully rooted using temporary TWRP + modded magisk method, but now I gain root and checked via Root checker. But the problem is most of the root functions don't work as /system is read-only. Any idea?
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
zazzy24 said:
Ya i have an idea.. Happened to me as well. I tried almoat everything but system won't be accessible anywhere.. I followed the same tutorial and installed magisk 13.4.
The only solution i could find was flash the latest factory image, and root again using supersu. I used the AIO tool by ghpranav and have got my phone rooted with xposed working without any issues.
Click to expand...
Click to collapse
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Cool:good:
Xposed isn't working with magisk? I was planning to install it
amithiel said:
Xposed isn't working with magisk? I was planning to install it
Click to expand...
Click to collapse
Only with SuperSU as I know.
Sent from my Mi A1 using Tapatalk
Guys, this is Magisk from Pixel. You can't expect that it is working. I wrote to MagiskDevs already, they are working on a own Version for Mi A1. Use for that time normal SuperSU (Xposed works normally )
how to??
soralz said:
I also fixed the issue. I flash the modified boot image and I am now gaining proper root access + Xposed. Get it working using Super SU, idk why Magisk keep failing thou. Was wanted to give Magisk a try, but it doesn't work properly on our device.
Click to expand...
Click to collapse
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
maxsan20 said:
Hay how do you Fix the Read only Issue? can you please share the Modified Boot image and process for same, thanks
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
soralz said:
https://desktop.firmware.mobi/device:1748
Just root with replacing the boot image then you are good to go.
Click to expand...
Click to collapse
Hi,
I have TWRP installed and unrooted, what I need to do please?
We7dy said:
Hi,
I have TWRP installed and unrooted, what I need to do please?
Click to expand...
Click to collapse
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
Code:
fastboot oem unlock
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
soralz said:
You need flash back stock boot image first, due to some limitations you can't have TWRP and SuperSU root at the same time. If you don't have the stock boot image. I suggest download the ROM from MIUI and then flash it. You can choose "flash_all_except_storage" option, this will keep your data.
http://en.miui.com/download-333.html
After flashing. Reboot back to fastboot and then:
After that just run root.bat from the cf-auto root folder you downloaded and wait for it to automatically reboot your phone. You should have root now, if you wish you can download SuperSU from the store.
Click to expand...
Click to collapse
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
We7dy said:
Ok, thanks. It's not possible to do that via TWRP? I don't have PC. Currently my bootloader is unlocked, I have TWRP and I'm unrooted.
Click to expand...
Click to collapse
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
soralz said:
I actually tried before, and I tell you the results:
Option 1 TWRP installed + Rooted with Magisk
= Pretty much useless as /system is read-only. Every root app doesn't function, unless it is system-less. But system-less modules nearly all doesn't work as the Magisk version too old. And this method won't trip safetynet
Option 2 no TWRP + Rooted with SuperSU (cf-root method) -- Currently using this state
= Got proper root access, Xposed works but will trip safetynet
Option 3 TWRP installed + Rooted with SuperSU (cf-root method)
= Don't try this, will cause your phone stuck in boot loop
Click to expand...
Click to collapse
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
We7dy said:
So not possible via TWRP? Get root access and remove TWRP? I just need that... The root.
Click to expand...
Click to collapse
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
soralz said:
The best bet and possible trouble free is to first download the stock ROM from MIUI, reflash it and then root.
Click to expand...
Click to collapse
:/ Can't root with TWRP without system read only...
We7dy said:
:/ Can't root with TWRP without system read only...
Click to expand...
Click to collapse
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
We7dy said:
It's possible to root without CF-Auto-Root? Why can't flash SuperSu directly with TWRP?
Click to expand...
Click to collapse
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
soralz said:
No, it will cause your phone stuck it boot loop if you try to flash the SuperSU zip directly from the official ChainFire site. I think probably is the AB partitioning problem or some sort (unsure). As I said you need to run CF-Auto root to get proper root access, otherwise flashing Magisk through TWRP will makes most of the root apps does not work properly unless it also uses system-less root function.
Click to expand...
Click to collapse
Ok I have TWRP installed can I use directly CF auto root?
We7dy said:
Ok I have TWRP installed can I use directly CF auto root?
Click to expand...
Click to collapse
No if you want proper root with CF-auto root you must not have TWRP installed. You either choose TWRP + Magisk (non-working root) or no TWRP but with SuperSU (working root, Xposed works too).
Follow the instruction here to get you on track:
https://forum.xda-developers.com/showpost.php?p=74326169&postcount=2
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
hartleyshc said:
Twrp has decryption issues currently. It's mentioned in the thread.
No need to install it yet, just boot to it.
If you're wanting to install magisk, just go into adb sideload in twrp and sideload magisk from your PC.
Click to expand...
Click to collapse
Thank you for your quick reply!
Is it bad that it is already flashed permanent? Or do I need to flash original recovery again?
I'll try and sideload it. Haven't done that before.
bokkoman said:
I've got my hands on this phone today. So I went on and unlocked bootloader and installed TWRP (with all in one tool).
But now when I want to root my phone through twrp, i can't access my files. I see the root folders, but when I go to /sdcard there are only a bunch of folder with random letters.
I don't know what's wrong. It is not asking for a password or anything.
Click to expand...
Click to collapse
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Funk Wizard said:
The current TWRP has decryption issues as its based on the Oreo tree and encryption/decryption works differently on pie.
Here is a post i did so follow it for easy instructions.
Click to expand...
Click to collapse
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
bokkoman said:
I read in your post that you not recommend to flash twrp, but I already did. How do return to original recovery?
Click to expand...
Click to collapse
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Funk Wizard said:
Nothing to worry about. You can dirty flash the latest full zip from my update thread or just wait for the next OTA as and when it comes flash the full zip that will overwrite the recovery partition to stock. For now TWRP is basically useless so i did not recommend to flash the installer instead just boot in it sideload magisk or kernel if you need to and retain stock recovery.
Feel free to ask anything if you are still in doubt :fingers-crossed:
Click to expand...
Click to collapse
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
bokkoman said:
Thanks for the info! I'll wait for an update.
When that update comes, can i just install it from the settings? Or would i have to manually download it and install it thru TWRP/sideload?
And i guess I lose root after i update so i would have to boot into twrp and install magisk again.
Click to expand...
Click to collapse
As and when the update comes, just let the system download and install the zip. It will auto download and install the full zip when it detects root/system modifications, just make sure you uninstall/deactivate all mods/magisk modules/ substratum overlays before you update. You can check for easy instruction on the third post of the update thread. I will update the thread as and when the OTA is released.
Also you guessed it right the update will unroot the device so you have to root it again so you can either do the same sideload way or just do it from the magisk manager - uninstall - install ota (do not reboot) - install magisk to second slot - reboot :good:
I will again update the detailed instructions for easy understanding and and when we have the update :good:
Just stay subscribed to the update thread :good:
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.
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?