Related
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
This update supersu no longer works. I installed that twrp and did the process for that version of supersu and it said successful. Upon checking supersu, it says the binary files are missing. Then I installed the newer supersu verison through twrp, without deleting the old supersu and now the phone is stuck on htc boot screen. This may work for some, but DO NOT install another supersu over an old one without deleting it first. You WILL get stuck on boot.
Weisheit7 said:
Then I installed the newer supersu verison through twrp
Click to expand...
Click to collapse
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
redpoint73 said:
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
Click to expand...
Click to collapse
You're right, and as of right now I have a different issue. I found a link for the Chinese ROM of the htc m8 eye and I successfully installed it. Now the device is on 4.4.4 rooted. I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
How can I fix the OTA problem through stock recovery? I checked the /system/bin/reboot file and there's nothing there specifically that I can see is corrupted or changed. Is there any possibility that supersu has system permissions and is causing this error? If so, how do I fix the /reboot has unexpected contents problem? How can I delete supersu (su) from having system permissions over everything?
I cannot find a stock Chinese ROM for this device, only the rooted one. I'm at a loss here..
Weisheit7 said:
I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
Click to expand...
Click to collapse
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
redpoint73 said:
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
Click to expand...
Click to collapse
I've read online that if you unroot it the OTA update should go through. It depends on how the root was done, correct? If root has (owner) permissions over system files, how can I put it back to stock? Are you aware of any HTC One M8 eye mels_tuhl stock rom China region? I've scoured the internet forever and cannot find one. If you need my getvar info I'll post it here and I appreciate any help you can potentially give me.
Weisheit7 said:
I've read online that if you unroot it the OTA update should go through.
Click to expand...
Click to collapse
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Weisheit7 said:
It depends on how the root was done, correct?
Click to expand...
Click to collapse
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Weisheit7 said:
Are you aware of any HTC One M8 eye mels_tuhl stock rom China region?
Click to expand...
Click to collapse
Unfortunately, no.
redpoint73 said:
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Unfortunately, no.
Click to expand...
Click to collapse
Thanks for taking the time to reply. Since then I have corrected the problem. I downloaded a TWRP backup of Marshmallow from another user on here in a different thread, placed it into my TWRP backup folder, wiped system, internal storage, cache etc and then flashed the backup. Everything went well...marshmallow is on the phone and root is gone.
necaticetinkaya said:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
Click to expand...
Click to collapse
Can you provide another share of the file? The previous link has expired
So I'm looking into rooting my Nexus 6P, I'm wondering if my build number (MMB29Q) is able to be rooted? Sorry, I'm really new to this. I keep seeing images for MMB29P but not sure if that is compatible?
Yes. Its possible. I'm on MMB29Q and rooted. Although I'm running a custom ROM with root built in. Systemless root is the way to go in my opinion. Read Heisenberg's guide in the general section. That guide is your go to reference for the 6p. He describes in detail how to setup your PC to unlock the bootloader and root the device.
Pain-N-Panic said:
Yes. Its possible. I'm on MMB29Q and rooted. Although I'm running a custom ROM with root built in. Systemless root is the way to go in my opinion. Read Heisenberg's guide in the general section. That guide is your go to reference for the 6p. He describes in detail how to setup your PC to unlock the bootloader and root the device.
Click to expand...
Click to collapse
I read that guide about the Systemless root. The only downside is that you have to reflash TWRP everytime since it's read-only? Is that correct or am I doing something wrong?
Newerabs said:
I read that guide about the Systemless root. The only downside is that you have to reflash TWRP everytime since it's read-only? Is that correct or am I doing something wrong?
Click to expand...
Click to collapse
You don't have to flash it every time. If you want to update though you'll have to flash the stock recovery. Personally, I like to boot directly into twrp from fastboot when I want to make a modification.
Newerabs said:
I read that guide about the Systemless root. The only downside is that you have to reflash TWRP everytime since it's read-only? Is that correct or am I doing something wrong?
Click to expand...
Click to collapse
When you first flashed TWRP did you select to keep it read-only or to allow system modifications? If you selected read-only that's probably why it keeps disappearing on you.
Also, it doesn't matter what build, every build is able to be rooted on a Nexus.
B_I_N_G_E said:
You don't have to flash it every time. If you want to update though you'll have to flash the stock recovery. Personally, I like to boot directly into twrp from fastboot when I want to make a modification.
Click to expand...
Click to collapse
Not entirely correct. You can easily follow step 10 of the same guide and update to latest build with just a few fastboot commands.
Hi all,
let me first start by thanking the good people of xda community for your kind help and contribution. It would not be possible for people like me with extremely limited rooting knowledge to even have the courage to attempt a root if it wasn't for the good people like you here.
I just got my Axon 7 and is trying to work up the courage to attempt a root following tenfar's instruction (I'm extremely scared of bricking my new phone) I also hope that I can continue to play Pokemon Go after I root it, but unfortunately with the latest update, it seems impossible until I discovered Magisk. My question may seem fairly simple but it is extremely confusing to me. In Magisk's instruction it says that in order to install Magisk, one must remove any kind of root and systemless Xposed. Since my phone is not rooted, I do not have to go through the step of removing root and xposed? However, it says that I have to download Magisk and flash it. My confusion rests on the concept on how I can flash Magisk if my phone is not rooted? I thought one can only flash a rom etc after the phone is rooted? So should I follow tenfar's root first and root my axon 7 then try to flash Magisk? or the other way around? Any advice /tips/precautions/high level guides regarding both rooting using the tenfar method and flashing Magisk is greatly appreciate! I may suck at rooting and etc, but what I can do is follow all instructions carefully. Thank you everyone, you are the best!
To flash something (a ROM or an app, like Magisk) you need to have a custom recovery installed (such as TWRP, you boot into the custom recovery to flash the .zip file that contains whatever you want to flash) which generally means having an unlocked boot-loader, neither of those has anything to do with root (other than that they make rooting the phone considerably easier) they don't require it and they don't do it by themselves.
@Nameless One is right, you need a custom recovery (TWRP) to be able to flash Magisk. There is a thread about this in the forums.
However I would advise you to wait until next week when a new update is expected and perhaps some changes to the bootloader unlock policy and hopefully stock ROMs, which will make it much easier to solve any problems.
If you insist on going through with this now, you should take backup images of various partitions so that you can restore your phone to stock to receive the OTA.
How does it work if you have uninstall any kind of root? I would think root would be a requirement.
KyJelly69 said:
How does it work if you have uninstall any kind of root? I would think root would be a requirement.
Click to expand...
Click to collapse
It right on the top of their post
"This mod requires boot image modification, so unlocked bootloaders are required!"
What it does is implement it's own system-less root management module that will not be detected like other root methods. But will conflict with other root methods hence you have to be unrooted
Unlocked bootloader let's you flash custom recovery. That in turn let's you flash anything else including root modifications. In essence tenfar's boot image is modified to allow root. This will do something similar but you have to have the BL unlocked since patching boot image will change the signature.
iirc magisk alters the bootimage, so you need a unlocked Bootloader go get it to work.
And no, root is not a preq, you can use magisk to /aquire/ root though.
What u need:
- unlocked bootloader
- custom recovery
- a somewhat clean and not already modified system
Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!
projectseahorse said:
Thank you all for the helpful replies, I greatly appreciate them.
I'm running out of the box ZTE Axon 7 A2017U with 6.0.1 Android. My goal is to install Magisk then eventually root so I can play Pokemon Go on the phone. Please advise on the next step? What are some of the safety precautions I should take? Thank you all very much!
I'm also planning on waiting until the next update [email protected]'s advice. Can anyone please explain to me the reasoning behind mh127's safety precautions? Thanks!
Click to expand...
Click to collapse
If you have copies of the stock images you will probably be able to fix your phone if something goes wrong and you want to go back to stock.
Not having these copies is like jumping out of a plane without a parachute and hoping you'll hit a haystack, without the pitchfork in it...
There are never any guarantees, every phone is different and as you are playing with important partitions there is a chance, generally through users fault, to brick your device...
Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!
projectseahorse said:
Hello all,
Do we know if the "stock rom" @mh127 was talking about is available? Am I safe to proceed with the the magisk/root installation? Thanks!
Click to expand...
Click to collapse
Well, the stock images have not been released for the B27 update, which would make it much easier to recover if something goes wrong. However, unofficial images are available (look around the forums). So at this point it is your call, just be careful.
I have a v20 US996 (unlocked) that I'm getting ready to unlock the bootloader and then I'll want to root. I've always rooted with SuperSU in the past, but now there is also Magisk.
For our v20s (US996):
1) Should we use Magisk instead of SuperSU?
2) Is it as stable as SuperSU (without random reboots, etc)?
3) If 1+2 are "yes" then where can I find out how to root with Magisk safely without any problems?
Thanks!
I say yes to your first two questions. I accidentally upgraded to 10H on the 996 and I thought I was stuck with an unrootable phone. I had already had an unlocked bootloader and I used ADB to flash TWRP, flashed Magisk and boom. Rooted again. Been happy ever since. I don't have the exact thread for Magisk but if you Google I wanna say Magisk 14.0 you should be able to find it. Been working great for me. Hope that helps.
Anyone else's thoughts?
Also, will I still be able to use the 2nd screen?
And where can I find instructions specific to the v20?
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Sizzlechest said:
Magisk works great and passes SafetyNet. No reason to still use SuperSU. Switching can be problematic. You need to reflash the correct boot.img, then flash Magisk WITHOUT LEAVING TWRP.
Click to expand...
Click to collapse
Especially with chainfire retiring, now is all the more reason to use magisk only. I've been using supersu for the entire duration of my smart phones but I need to make the switch.
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
baldybill said:
Thanks.
I have not yet rooted this phone. Should I follow the instructions from jcadduono to root this and then be sure to flash magisk instead of supersu?
(jcadduono's instructions are here: https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Click to expand...
Click to collapse
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
GreenDinoXD said:
I had this same problem, I asked this question on the subreddit, I got an absolutely amazing response and I fixed the phone. Pretty much just flash the 10f kdz, and then re unlock the bootloader if needed, then flash twrp normally, DO NOT US RECOWVERY. here is the link to the person who helped me with all of this, https://www.reddit.com/r/lgv20/comments/73hsl3/upgrading/. Just read the comments from Pheonix591 and I.
Click to expand...
Click to collapse
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
baldybill said:
Thanks
(I've never rooted this phone, so it's not an issue of re-rooting, it's an issue of rooting to begin with)
Why not use recowvery?
Click to expand...
Click to collapse
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
GreenDinoXD said:
It isn't necessary for our device since we can just flash TWRP through fastboot after unlocking bootloader officially. If you need me to I can write you a step by step guide, it'll be done tomorrow after school but I can write it for ya if need be.
Click to expand...
Click to collapse
Please do, I don't want to mess up my phone.
It's never been unlocked or rooted. [Currently, I'm having trouble getting the unlock image from LG. ]
Okay i am going to copy the exact text that the person who helped me said. It is really well explained and he says the steps very clearly. To do a TWRP backup and restore it it's one of the main buttons on the screen, I highly recommend using an SD card. Use the select storage button to change between internal storage and the SDcard, just check the box for data, and that has all your apps and pretty much everything else. And when you do the kdz part below you can just restore the version f firmware and do the update that way and skip the ota. I copy and pasted most of the rest from the last time I typed this up.
Get a hold of LGUP and downloading the kdz, heres (https://forum.xda-developers.com/v20/how-to/v20-kdz-restore-failing-9-completing-fix-t3546817) a good thread on it, with even all the tools attached except the kdz, for getting on the older more stable twrp just flash flash it in fastboot (use lgup to restore the kdz which gets back to full stock, then use fastboot to get the info needed to fill out the form on LG's site(https://developer.lge.com/resource/mobile/RetrieveBootloader.dev), (basically this guide has it all listed out, plus once you've created an lg account and actually gotten to the form, the page with has directions too(http://www.droidviews.com/unlock-bootloader-on-lg-v20-us996/))
So heres how we're going to get twrp on here from a stock, but unlocked us996. You probably don't need the no-verity-opt-encrypt if also flashing supersu or magisk but I did it anyway to be safe.First get the latest version of no-verity-opt-encrypt.zip from here(https://build.nethunter.com/android-tools/no-verity-opt-encrypt/), and the stable version of Twrp-3.0.2-1-us996.img from a different directory on the same site(https://build.nethunter.com/test-builds/twrp/lge/), if you have an sd card in your phone put the no-verity zip on it ahead of time (and if you want to save a boot, put magisk on there too) (if not twrp should let you transfer it from your pc, but I havn't done it that way). So go ahead and reboot into fastboot (adb reboot bootloader) mode, then fastboot flash the_FULL_PATH_to_twrp-3.0.2-1-us996.img . once it successfully completes, until we flash the no verity zip in twrp if the phone boots into stock it will overwrite twrp and it will need to be reflashed in fastboot mode. So once you've flashed it the first time, pull the battery, wait a second, then put it back in, hold down volume down, hold the power button just until the LG logo appears, then let go of the power button, and immediately press (and release) it once while still holding down volume down, keep holding volume down until, if you've done it successfully, it will ask you to factory reset your phone (for future note, while twrp is installed this will NOT factory reset your phone), say yes both times and twrp will boot shortly.
From here, go to install, and then change to your sd card and install the no-verity-opt-encrypt.zip, then go back and hit wipe (in twrp), on the wipe screen, hit the format data button (the correct button will make you type out yes to confirm), from here twrp will be installed and not tampered with and you can safely install magisk or a custom rom, and/or boot back into stock.
I do not know where i downloaded magisk from but here is the latest version:https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
I'm in a similar situation, with a fresh US996 factory-unlocked. Does this method (stock + magisk + twrp) preserve Android Pay / SafetyNet?
I switched from SuperSU to Magisk and now I can download Netflix from Play Store.
Switch away if you want to.
Thanks, GreenDinaXD, I'll give that a try after a while.
Thanks
GreenDinoXD said:
I recommend getting version 13.3 and then upgrading to version 14. Hope this helps and if you have any questions feel free to ask, im just busy so i may not answer quickly, working on college applications so i apologize in advance
Click to expand...
Click to collapse
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
baldybill said:
Oh, why do you suggest using Magisk 13.3 and then upgrading? Why not just go straight to 14?
Click to expand...
Click to collapse
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
With my experience from MagiskSU, absolutely, Magisk let's you use any anti-root app, like Snapchat, or Netflix, etc... So you don't need to go through the Xposed McCluster**** ordeal
GreenDinoXD said:
Believe I read somewhere that it didn't work as well or gave someone trouble, so I just told you the way I did it and I had no problems. If you want to try going straight to 14, go for it.
Click to expand...
Click to collapse
Are there stability issues with Magisk? Random reboots?
I'm curious since this is my everyday phone and I want it to be running decently. Thanks!
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
stovo06 said:
I've read the guides on how to unlock bootloader, install twrp & gain root (magisk preferred) with 10.3.0 and I still do not quite understand.
This is the best Android I've had and I'd really like to do this right. Would anyone please help me? Thank you, Stephen
Click to expand...
Click to collapse
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
You can't go wrong with the guide here https://r.tapatalk.com/shareLink/to...9&share_fid=3793&share_type=t&link_source=app
It's very simple to follow
Just update to the newest version TWRP and Magisk
Click to expand...
Click to collapse
I thought this was for 9.x.x
stovo06 said:
I thought this was for 9.x.x
Click to expand...
Click to collapse
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Click to expand...
Click to collapse
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
clsA said:
Nothing has changed but the versions of TWRP and Magisk
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
flyoffacliff said:
Thanks for trying to help, but I don't think this is entirely correct. The "fastboot boot" command was removed in a10, and an alternative method was eventually developed AFAIK.
I never did get a successful root on this device after spending a whole day on it. It's difficult because little bits of information are scattered everywhere instead of in a single up-to-date guide. And a few months ago, no one could agree on anything. Just look at how many other people got semi-hard bricked.
Click to expand...
Click to collapse
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Striatum_bdr said:
Fastboot boot command has been allegedly fixed in 10.3.0 and this fix has been confirmed by several people. So yes the philosophy and method hasn't changed since years. At worse you use 'fastboot flash boot' command instead. That's only one change.
You can still extract boot img from payload.bin on your computer, transfer it to your phone and use Magisk manager to patch it and then transfer and flash it with fastboot from your computer. Then you flash twrp installer as a module in Magisk Manager once your phone is rooted. That also hasn't changed for years, this method has always existed.
Most of people bricking their device are doing one thing or another wrong.
Click to expand...
Click to collapse
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
stovo06 said:
This is where I start getting confused lol.
I appreciate the help, but this is not what I'll accustomed to.
Anything you recommend reading to help educate myself?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Striatum_bdr said:
https://forum.xda-developers.com/on...l-oxygenos-beta-1-oneplus-6t-t3881099/page484
Read Cultofluna post
And search Google for it, many tutorials
Click to expand...
Click to collapse
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash boot TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
all he needs is
unlock bootloader
fastboot flash recovery TWRP.img
boot to TWRP / Flash TWRP installer.zip
Reboot recovery
Flash Magisk.zip in TWRP
reboot
done
the guide I linked earlier goes into great detail explaining each of these steps
He could even use the All in one tool after downloading the correct versions of TWRP and Magisk
Click to expand...
Click to collapse
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Striatum_bdr said:
I know that it's the way Android works since years....
But a guy warned him about bricked phones and other very alarming prophecies... So I gave him a plan B in case of...
Click to expand...
Click to collapse
That's what I've read as well. And there are many solutions but I find them scattered all over the forms.
And I don't trust YouTube videos lol
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
stovo06 said:
I just want to make sure it works with 10.3.0.
I can downgrade if necessary but trying to find the easiest method.
Thanks guys for all your help. Maybe I'll post a 10.3.0 thread after this if it's needed to avoid confusion
Click to expand...
Click to collapse
I don't think there is the need of another thread. Many are already talking about rooting and flashing twrp.
What makes people confuse is that perhaps some of them think things have changed... And that methods are bound to an Android version.
Nothing has changed.
Fastbooting TWRP and then flashing it, is the way we do it since years. Patching boot img as an alternative is also a classical way to root.
People are blinded by tiny differences and don't see that the frame hasn't changed. You unlock the bootloader, then boot to twrp and then either you flash only Magisk either you flash twrp then Magisk. Very simple. Always with latest versions.
It's because xda threads are not moderated except for offenses, etc that many users post their 'own' recipe every 2 pages without anybody cleaning and organizing things to make them understandable. And the fact that threads are not well maintained in time, with titles and first posts instructions that can seem obsolete.... Especially on old phones like our when devs are quitting the scene without designating a maintainer
clsA said:
Nice instructions, But I'm curious why you think he needs them ?
Click to expand...
Click to collapse
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
aaron74 said:
Thanks for clarifying.
Even for someone experienced with flashing and modding in the past, but I've been away from the flashing world.
There is a lot of conflicting info about this. Some say to patch boot img manually.
The TWRP thread says to install TWRP as a magisk module.
But seriously, Thanks. I'm glad I came across this thread. I thought the old way of doing things was done with Android 10, until I read this.
Click to expand...
Click to collapse
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Striatum_bdr said:
You can do that, installing TWRP as a module, since one year or so. So you just fastboot boot twrp, flash Magisk zip, then once phone booted back to Android, flash twrp as a module with Magisk Manager
Same thing if you just want to flash kernels, no need to have TWRP, Ex Kernel Manager or Franco Kernel Manager can do this as long as you're rooted
Click to expand...
Click to collapse
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
stovo06 said:
Thank you. Definitely need to get this done.
Atm I think I'm gonna stick with stock ROM but maybe a custom kernel.
Any suggestions?
Click to expand...
Click to collapse
Wait for render zenith
stovo06 said:
@Striatum_bdr you've been very helpful person here in a bit.
Since this a/b partition has come around, I have gotten multiple ways to unlock bootloader and root with my moto x4. And before I owned that Motorola, I've never had a reason to use a/b partitions. Long story short, my TWRP got screwed and I've become hesitant about doing anything with a new device. And this is the best device I've owned in many years so I have to do it right.
Unless any further issues arise, I'm going to go for it.
Thank you everyone that's helped guide me thru this.
Edit :I've no idea what patching a boot img is lol.
Click to expand...
Click to collapse
Yeah, this is an awesome device. Only device I've been happy with since my old Samsung note 4. Biggest thing I miss, it'd be nice to have an SD card slot!
Patching a boot image is what Magisk does when you install it. But you just would manually do this.
Last question, I've been reading too install Magisk 19.4.
Does that still apply?
Apologies for all the questions (and great appreciation for the help), but the information here is scattered and at times contradicting when all I need now is a simple magisk manager and mod ?.
Thank you all for your help.