Could anyone please point out a way to root my phone(in title), as of this day. There are many methods. So I am confused. I recently read about magisk manager, used to root. Does it work? I just wanted to know the latest method, easier one of any. Also can TWRP manager be used to flash recovery in phone or should it be done flashing TWRP. Img, file.
Please forgive me if i posted in wrong section.
Thanks in advance.
enusri said:
Could anyone please point out a way to root my phone(in title), as of this day. There are many methods. So I am confused. I recently read about magisk manager, used to root. Does it work? I just wanted to know the latest method, easier one of any. Also can TWRP manager be used to flash recovery in phone or should it be done flashing TWRP. Img, file.
Please forgive me if i posted in wrong section.
Thanks in advance.
Click to expand...
Click to collapse
Use PC via ADB (fastboot)to flash TWRP. Flash Magisk in recovery, then dl Magisk manager from play store.
Magisk works very well.
This all is assuming your boot loader is unlocked.
Good luck.
melp57 said:
Use PC via ADB (fastboot)to flash TWRP. Flash Magisk in recovery, then dl Magisk manager from play store.
Magisk works very well.
This all is assuming your boot loader is unlocked.
Good luck.
Click to expand...
Click to collapse
So instead of supersu, we use magisk?
And I read somewhere also that using magisk we can still get updates to our phones. Is that right?
Also there is a TWRP manager in play Store can we use it to flash TWRP instead of ADB?
Thanks for the steps though.
enusri said:
So instead of supersu, we use magisk?
And I read somewhere also that using magisk we can still get updates to our phones. Is that right?
Also there is a TWRP manager in play Store can we use it to flash TWRP instead of ADB?
Thanks for the steps though.
Click to expand...
Click to collapse
My experience with TWRP manager has been it breaks my recovery. No idea why so I flashed via PC. Not sure you can still receive updates when your boot loader has been unlocked. Depends on a lot of factors. Someoneelse will have to answer that question.
melp57 said:
My experience with TWRP manager has been it breaks my recovery. No idea why so I flashed via PC. Not sure you can still receive updates when your boot loader has been unlocked. Depends on a lot of factors. Someoneelse will have to answer that question.
Click to expand...
Click to collapse
OK thanks.
An unlocked bootloader doesn't prevent you from receiving updates from Motorola. But I think rooting the ROM will prevent installation of further updates.
I don't think Motorola is going to push any further updates. So just do anything you want with your phone (personal opinion).
bin.sayantan said:
An unlocked bootloader doesn't prevent you from receiving updates from Motorola. But I think rooting the ROM will prevent installation of further updates.
I don't think Motorola is going to push any further updates. So just do anything you want with your phone (personal opinion).
Click to expand...
Click to collapse
I've never received a update notice.
I would have to agree... There is little chance of getting another update, and if we did it would just be a simple security update and not important.
And no, even with Magisk you cannot apply an OTA update, it will fail.
Unlock your bootloader, flash the twrp recovery using adb fastboot...then wipe the stock rom, flash custom rom along with SuperSU....enjoy! (Processes are same but you should use the latest versions of all these...)
https://forum.xda-developers.com/2015-moto-g/general/guide-osprey-moto-g3-begin-how-to-t3599251
Related
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.
So I'm currently using Honor 8 FRD-L09432 on B394 build. I have unlocked bootloader and am rooted with SuperSU. I wish to remove SuperSU root and switch to Magisk. From Magisk thread instructions I'm supposed have unrooted device and intact boot image.
When I try to unroot with SuperSU I'm greeted with "Uninstallation failed!" window. As an alternative to unroot I decided to just use Huawei Firmware Finder and download latest(B394) update.zip and extract stock boot.img from that. After successfully managing the extraction I tried to flash the newly extracted boot.img via TWRP. My device fails to boot with said boot.img so I had to restore the back up.
So my question is what am I missing here? Or is there some other alternate way to switch to Magisk without rollbacking to stock packages and having all my data wiped. Thanks for your assistance.
Osmosis' unsupersu script should work to remove it, then reboot, then flash magisk.
Hi,
I have the FRD-L04 with the B389 update. I am currently root with SuperSU, and I would like to change to Magisk. I have been reading some guides and posts but I want to be sure before proceeding. I found this guide for the Pixel and I would like to know the opinion from the experts if this would work for my honor 8. Thanks!
juanboja said:
Hi,
I have the FRD-L04 with the B389 update. I am currently root with SuperSU, and I would like to change to Magisk. I have been reading some guides and posts but I want to be sure before proceeding. I found this guide for the Pixel and I would like to know the opinion from the experts if this would work for my honor 8. Thanks!
Click to expand...
Click to collapse
You will need stock boot image, that's pretty much all. So you can try to restore the stock boot image via unroot from SuperSU which is a bad idea and I would highly discourage it. So you either extract the stock boot image for B389 from UPDATE.zip or you restore stock boot image from your own backup if you have it.
After obtaining and flashing stock boot image, flash the Magisk zip from main Magisk thread. I can not verify that latest version works (16.0), I havent tried it. I'm personally on 15.3 and if you really want it I can test 16.0 for you.
After flashing Magisk install Magisk manager which you can obtain again from main Magisk thread. Ofc unistall SuperSU app as well.
You can't brick your device in any way as long as you make a full TWRP backup before attempting any of the above. If you run into any of the errors just restore it and ask for further instructions.
Thanks for the set of instructions, I did as instructed and it worked as a charm! Thanks for everything. I'm in B389 with Magisk now!
Sent from my FRD-L04 using Tapatalk
juanboja said:
Thanks for the set of instructions, I did as instructed and it worked as a charm! Thanks for everything. I'm in B389 with Magisk now!
Sent from my FRD-L04 using Tapatalk
Click to expand...
Click to collapse
Hide function works well with apps that don't work with root, like Google Pay or home banking?
zinko_pt said:
Hide function works well with apps that don't work with root, like Google Pay or home banking?
Click to expand...
Click to collapse
Sorry but I don't use those apps... maybe somebody else can give you feedback.
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
Hi, Im new in this forum, just got my OP 7 Pro. I've been away from anything root related for a long time, since my previous devices couldnt be rooted.
I remember using magisk when it was a new thing, and everyone was using greenify to extend battery life.
I just updated to Android 10 Beta, can I root my device?
If it is possible, what do I lose if I root besides widevine?
The only thing I'm really looking forward is gcam port and the use of aux cams, since a lot of things have to be updated to Android 10, I don't think there's a lot to do right now besides that.
I think you have to come back to the android p stable, root, install the twrp and after you will able to update with the root. Now im on the beta with root and twrp throw a dirty installing
vuoshino said:
I think you have to come back to the android p stable, root, install the twrp and after you will able to update with the root. Now im on the beta with root and twrp throw a dirty installing
Click to expand...
Click to collapse
Hi! Thanks. If you don't mind, can you give point me to a guide or something to downgrade? I'm a total noob with everything OnePlus related.
You don't have to downgrade to Pie.
Do it like this:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
You just need stock boot.img:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
There's also another way which avoids to downgrade.
Flash the magisk patched img you'll find in this forum.
After following instructions from there, you'll be rooted but without TWRP.
If you need that also... flash the TWRP installer zip as a magisk module, reinstall magisk (direct install), reboot and you're done.
Inviato dal mio GM1913 utilizzando Tapatalk
tidschi said:
You don't have to downgrade to Pie.
Do it like this:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
You just need stock boot.img:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Click to expand...
Click to collapse
Wow, thanks!! that seems stupidly easy, even for me. Two questions:
Do I need a PC to do the extraction?
Will this wipe any data?
And as for my initial question, is there anything besides widevine lost when rooting?
donelwero said:
Wow, thanks!! that seems stupidly easy, even for me. Two questions:
Do I need a PC to do the extraction?
Will this wipe any data?
And as for my initial question, is there anything besides widevine lost when rooting?
Click to expand...
Click to collapse
You can download Magisk patched boot.img from second link above.
Flashing boot.img will not wipe any data.
If I remember right, Widevine will get L3 with unlocked bootloader.
tidschi said:
You can download Magisk patched boot.img from second link above.
Flashing boot.img will not wipe any data.
If I remember right, Widevine will get L3 with unlocked bootloader.
Click to expand...
Click to collapse
Awesome!! Thank you very much, thought I had to unlock the bootloader by myself using a PC.
Edit: I'm so dumb, just realized I still have to flash the boot.img using fastboot
I have a question, in order to root and flash twrp coming with android 10 (no root) I must unlock the bootloader, right?
littlejonny17 said:
I have a question, in order to root and flash twrp coming with android 10 (no root) I must unlock the bootloader, right?
Click to expand...
Click to collapse
Yes bootloader must be unlocked to flash TWRP or Root the device also when you unlock the bootloader it will factory reset the device so make sure you backup any personal data you need before unlocking.
Thank you
Hey everyone so I have my OnePlus8T all unlocked and ready to be rooted via Magisk. This includes both OEM unlocking turned on and I have successfully gone through the SIM unlock process with T-Mobile.
However....how can I root with Magisk by doing the step of payload dumper without being able to obtain the latest firmware online? I've looked everywhere but looks like T-Mobile keeps it on a tight leash.
Thanks in advance.
kevinco1 said:
Hey everyone so I have my OnePlus8T all unlocked and ready to be rooted via Magisk. This includes both OEM unlocking turned on and I have successfully gone through the SIM unlock process with T-Mobile.
However....how can I root with Magisk by doing the step of payload dumper without being able to obtain the latest firmware online? I've looked everywhere but looks like T-Mobile keeps it on a tight leash.
Thanks in advance.
Click to expand...
Click to collapse
Hello!
As you haven't specified what firmware is installed on your phone at the moment, i see several variants:
1. You can find patched boot.img here on xda for your firmware and boot it, after install Magisk app as usual (Magisk -> Magisk Install -> "Direct Install (Recommended)")
2. If you're unable to find patched boot for your firmware version, you can temporary boot twrp recovery, and install magisk apk with it.
Sorry should have indicated my firmware which is the latest:
11.0.16.18.KB09CB
After doing another search I find no links through Google or XDA
It's possible to use TWRP temporarily even without root?
kevinco1 said:
Sorry should have indicated my firmware which is the latest:
11.0.16.18.KB09CB
After doing another search I find no links through Google or XDA
It's possible to use TWRP temporarily even without root?
Click to expand...
Click to collapse
Yes you can. Follow the process in A.2 of https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
BillGoss said:
Yes you can. Follow the process in A.2 of https://forum.xda-developers.com/t/guide-root-and-keeping-root-options.4387977/
Click to expand...
Click to collapse
Those instructions apply to the KB2007? I'm not seeing the model discussed anywhere in that thread and don't wanna brick my phone.
If so, when I go through the process to patch the IMG file through Magisk will it wipe the phone like it did when I unlocked the bootloader?
kevinco1 said:
Those instructions apply to the KB2007? I'm not seeing the model discussed anywhere in that thread and don't wanna brick my phone.
If so, when I go through the process to patch the IMG file through Magisk will it wipe the phone like it did when I unlocked the bootloader?
Click to expand...
Click to collapse
The rooting process isn't device specific. And it doesn't wipe your phone.
Also, if you are going to use TWRP, you could take a backup of your phone (see https://forum.xda-developers.com/t/...ect-8t-kebab-2022-03-09.4302449/post-85292199) which you could use to restore your system.
But, as always, there are no guarantees and you do this entirely at your own risk.
And, yes, I understand how scary it is to do these things the first time.