(SOLVED)
Hey guys, first time root here. HTC One AT&T 32gb
I was succesfully through the process, used a guide on htconeroot.com to go through all of the steps. Everything went just as expected and I had root access through superSU (was able to install and use root apps, such as Titanium Backup and AdFree). I used Root Manager to flash Clockworkmod because I saw a ROM I'd like to use in the future that only supported that custom recovery. After succesfully flashing that, I then made a backup using Root Manager. Everything was successful and expected, but upon reboot into my stock ROM from the original unrooted phone I had apparently lost SU binaries and root access. Also, ROM Manager (v5.5.3.0) cannot find any backups.
I tried reflashing superSU from the original rooting guide (UPDATE-SuperSU-v1.65.zip), and while it was successfully rooted, I still did not gain root access. I had read through some forums that using the stock ROM that came with the phone might lose root because of the stock recovery, but not sure if that is what happened. I have not installed a custom ROM on this phone yet.
Any help would be appreciated.
UPDATE: Solved, had to select "No" when rebooting from CWM on stock recovery option
Hello,
These past two days have not been a good day for my phone lol. Some background:
BEFORE:
I had a 4.4.4 Custom ROM [Forgot the name...]
TWRP: 2.5.0.2
AFTER:
I clean flashed http://forum.xda-developers.com/gal...m-cyanogenmod-12-0-nightlies-verizon-t2998057
I cleared cache + Dalvik after the flash and it asked me if I wanted to fix root (From what I read before, you're never supposed to press Fix, rather you're supposed to prses Do not Fix and you'll still keep your root.
However, I accidentally pressed Fix Root and Now I lost my root. The ROM I flashed is glitchy because from what I read is because I have TWRP 2.5.0.2.
Now I'm stuck on this ROM, I have no idea how to upgrade to the latest TWRP and don't know how to get my root back . [Can't get TWRP Manager because I don't have Google apps (I tried flashing the GAPPS by Paranoid but it keeps crashing because I think it's the outdated TWRP)]. I tried to download TWRP manager on my phone via another site, but it doesn't install on my phone for some weird reason.
Thank you,
Jerry
Download, install and run the towelroot.apk file. This will root your phone, takes about 2 minutes
Has anyone had any luck getting Magisk installed and working on a custom rom yet? I tried it on the CM13 Rom but root would just turn back on within a second. link for Magisk install http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Thank you
Wait until Magisk V7 is released.
Its states under known issues "HTC One M9 (yes, this particular device): sepolicy issues, should be fixed in v7" .
If you have a twrp backup of a rom that has the last build in it go to the app store and download an apk backup app and backup the pokemon go.apk and reinstall it in a newer rom build and don't do the update. Older version is still working until they finish rolling out the update.
Just to give an update on this....
I used BadBoys rom and I went into SuperSU and did UNINSTALL UNROOT... Which is the first step you need to do for Magisk.... This allowed me to PASS the Safetynet TEST... I can reverse this in moments since I am S-OFF by reinstalling SuperSU and reflash the binary from TWRP
*****So I am under the impression that when Magisk v7 comes out and works for this phone. It "Should" work with BadBoys. Until then I am just reinstalling SuperSU when I need it
I've gotten magisk to boot up once with phh superuser. However as soon as I tried to flash the systemless xposed from twrp. I would get stuck in a boot loop. I was unable to get it to boot up anytime I flash magisk now. I am S on but I don't think that should do anything with the rom.
Magisk works great on my Nexus 7
tws101 said:
Just to give an update on this....
I used BadBoys rom and I went into SuperSU and did UNINSTALL UNROOT... Which is the first step you need to do for Magisk.... This allowed me to PASS the Safetynet TEST... I can reverse this in moments since I am S-OFF by reinstalling SuperSU and reflash the binary from TWRP
*****So I am under the impression that when Magisk v7 comes out and works for this phone. It "Should" work with BadBoys. Until then I am just reinstalling SuperSU when I need it
Click to expand...
Click to collapse
This is what Ive ended up doing. Thank you
Another update
http://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
As you can see above today we still only have Magisk v6 and not v7 which we need to work with this phone model.... I will update again as soon as I can test v7 which they are still working on.
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
bskov said:
Hey everyone. So, today, I was messing around with my F1 today, and I tried to install MultiROM and was, for the most part, successful. But, when I restarted my phone and tried to boot the secondary ROM, it failed and then I couldn't even get into my intenal ROM.
So, I headed back into TWRP, uninstalled MultiROM and flashed back the non-MultiROM TWRP recovery. All was fine, I installed my primary ROM again and it booted fine, although I'd forgotten to flash GApps and Magisk. I set-up the ROM and then rebooted to TWRP and flashed GApps and Magisk. GApps were working fine, all well set-up, but Magisk wasn't appearing anywhere. CPU-Z also detected the phone as being rooted, but when launching Kernel Adiutor and SD Maid, I wasn't able to get a prompt for root access (Kernel Adiutor even told me I had no root access on the phone).
I also tried to install the Magisk Manager APK to no avail.
Does MultiROM mess with the partition scheme?
So, can anybody tell me what's going on here, what I messed up, so that I can correct it and go back to using Magisk?
BTW: The storage is encrypted, I never got around to use DFE, maybe I'll do so today.
Thanks in advance!
Click to expand...
Click to collapse
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
Yeah, im going to back it all up once I get home and wipe it clean to flash DFE and flash the ROM on top.
Also, I flash Magisk Uninstaller, it told me it couldn't find a stock boot image (and then proceeded to generate one), and then once I restarted the phone I went to CPU-Z to check root access and it changed to "No", so something was taking effect.
SamyakJ said:
I think you should decrypt the storage first then clean install your rom and gapps. Then install magisk. If magisk manager app didn't show then install from apk.
Click to expand...
Click to collapse
So, I tried decrypting, but I can't, because of something with Android Pie. Doesn't matter now, I wiped every storage partition clean and flashed the firmware twice, then flashed Magisk on top, now it's working. Thanks anyway!
That prompt not showing up and magisk manager not showing in app drawer is a common issue for me even though I've never installed MultiROM on my device. You can ignore both.
Here's what I do to resolve the issue:
1) Install Magisk Manager apk.
2) Go to settings, scroll down to "automatic response", click that, click either grant or deny, then click it again and this time set it as prompt.
That should show the superuser prompt.
Hi everyone, for quite some time I never had any issues upgrading mu phone MIUI, but recently the update process keeps failing, with Recovery Project 3.0.2-x complaining that the image zip (miui_MI5SPlusGlobal_9.6.27) is corrupted.
I started looking a bit more into it and it turns out my phone doesn't show as correctly rooted, so I was getting ready for doing a full root procedure, I backed everything up, get back to some tutorials and it seems like I should use TWRP and SuperSU.
It seems like SuperSU has been discontinued, so now I am kinda hanging, not being sure at all what I should do :S I would ideally want to upgrade to the latest MIUI
Any tip?
First Flash latest recovery.
https://dl.twrp.me/natrium/twrp-3.3.1-0-natrium.img
Download this latest Miui rom
https://sourceforge.net/projects/xi...5SPlus_V11.0.2.0.OBGCNXM_v11-8.0.zip/download
Do the wipes and install it.
For root you should flash magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/