I recently upgraded to Nougat 7.1.1 from Marshmallow via Flashfire. I flashed the factory image because it did not automatically recognize the downloaded OTA, and I was concerned that I'd have to go through several incremental OTA upgrades to get where I wanted. I told it to leave my recovery alone (was using TWRP 2.8.6.0 with no problems) and Flashfire went OK. My tablet updated fine, SuperSU 2.82 SR4 (systemless) root was installed, Root Checker says device is rooted and device is reporting in regular recovery that bootloader as unlocked. When I boot into custom recovery, TWRP is still asking for a password (easily bypassed by hitting Cancel), shows none of the file partitions I want, and on reboot system says my "device does not appear to be rooted, install SuperSU now?". I press "Do Not Install" and the tablet boots OK and Root Checker STILL reports the device as being rooted! SuperSU, Titanium, stickmount, etc. all work fine as well.
Are there some settings in TWRP that I need to change? Do I need to upgrade TWRP to 3.1.1.0 flounder? Is it because "Enable OEM unlocking" in Developer Options is off? I looked like crazy last night and can't find a solution . PLEASE HELP!
You will need the latest TWRP to be able to decrypted your device.
Ignore the message from the old version of TWRP about root, it is not detecting the latest root method(systemless).
As for "Enable OEM unlocking" I would advise to enable it, in case of future problems. Is your bootloader unlocked?
Also this months factory image is probably the last version for the device (we might get one more to patch KRACK).
Have you consider backing up apps and switching to a custom rom?
corkiejp said:
You will need the latest TWRP to be able to decrypted your device.
Ignore the message from the old version of TWRP about root, it is not detecting the latest root method(systemless).
As for "Enable OEM unlocking" I would advise to enable it, in case of future problems. Is your bootloader unlocked?
Also this months factory image is probably the last version for the device (we might get one more to patch KRACK).
Have you consider backing up apps and switching to a custom rom?
Click to expand...
Click to collapse
Why is the latest TWRP (3.1.1.0) have "flounder" in it? I thought the Nexus 9 was "volantis". Can I install this latest TWRP image on my tablet without bricking it? Oh, and I can't flash a custom ROM until I get this TWRP crap figured out. Sideloading is not my bag .
Joe_6pak said:
Why is the latest TWRP (3.1.1.0) have "flounder" in it? I thought the Nexus 9 was "volantis". Can I install this latest TWRP image on my tablet without bricking it? Oh, and I can't flash a custom ROM until I get this TWRP crap figured out. Sideloading is not my bag .
Click to expand...
Click to collapse
flounder is just another code name for the device.
You can flash the latest TWRP with fastboot or Install an image from your old TWRP.
Changing TWRP version should not cause a bootloop/bricking.
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
THANK YOU!
BTW, thank you!
Related
Today I've flashed the recovery with TWRP to install SuperSU.
Is there any possibility of installing the stock recovery to be able to install Android updates normally again without losing all data and SuperSU?
You sir, are not alone with this question. Been eagerly looking for an answer for the same question..
reconman said:
Today I've flashed the recovery with TWRP to install SuperSU.
Is there any possibility of installing the stock recovery to be able to install Android updates normally again without losing all data and SuperSU?
Click to expand...
Click to collapse
Use the search function, it has already been covered.
Anarchist77 said:
Use the search function, it has already been covered.
Click to expand...
Click to collapse
I can't find anything for the G5, only for other phones.
The only option I currently know of is to flash the whole KDZ and then install TWRP and SuperSU again. Is there another way?
As long as the system is modified in any way, the only way to install ota updated is through LGUP because before applying the update there is a system integrity check ran and if that fails you will most likely get into bootlops or worst
Here is what I did to get a 10D rooted system
Thank you @gwolfu.
Hey I just picked up this phone and decided I would like to maximize it to its fullest potential, and root it as I have done with previous phones. This ones giving me a hard time, and I just can't seem to find the proper info for it.
I have unlocked the bootloader, flashed TWRP 3.1.1 and want to gain root access. I have followed several guides, used every possible one-click unsuccessfully, and tried installing SuperSU with TWRP. After I reboot, SuperSU is installed. I'll open it up and it tells me the binaries are occupied. I've tried downgrading and updating the binaries but I get errors. (I believe this is because it must be rooted first - of course.)
So I'm stuck unable to get any further. If anyone has any suggestions, I would appreciate it. Is this phone with this configuration unrootable? There must be a way if I have recovery right?
Asus Zenfone 4 Z01KD/ZE554KL
Android Nougat 7.1.1 - 14.1060.1708.63 (NOT 1708.70)
TWRP 3.1.1 installed
One thing I have not tried is using Magisk. When I try it, it stops because I already patched with SuperSU (even though it failed). I never backed up before I did it with SuperSU I really thought it would work.
I read of people doing it with Magisk after updating to Oreo. I want to give that a try but I can't OTA or flash from TWRP. All attempts result in error 7.
I can't find a stock recovery to flash to do the update either. Is there a way to undo this, OTA and repatch with Magisk? Even if I don't bother updating, I would like to find a stock image to flash so I can try patching with Magisk.
Stock rom recovery.img anywhere? Am I alone?
i dont own this device but i read this and it might apply to you. also did you flash the supersu uninstaller and them try magisk?
https://forum.xda-developers.com/zenfone-4-2017/development/twrp-3-1-zenfone-4-2017-ze554kl-t3690349
hey i have the zenfone 4 ze554kl i updated it to android 9 unlocked the bootloader and got Twrp running but not correctly and i can't root the phone .....
It has been a nightmare trying to figure out how to root this thing and I need some help. I've been using Google but every guide and video I come across just don't do it for me. They all say something about installing drivers but don't go any further in explanation and they all say something different. Any help would be appreciated.
TheOneMisfit said:
It has been a nightmare trying to figure out how to root this thing and I need some help. I've been using Google but every guide and video I come across just don't do it for me. They all say something about installing drivers but don't go any further in explanation and they all say something different. Any help would be appreciated.
Click to expand...
Click to collapse
Same simple instructions as for all Nexus.
Unlock bootloader.
Fastboot flash twrp
Use twrp to flash root solution (SuperSU, magisk, etc)
https://forum.xda-developers.com/ne...ll-custom-recovery-root-t3200361/post62804370
All steps work, just need updated files. Like newest SuperSU or Magisk. Search of forum will work. Twrp link is fine. Don't worry about the posts in that thread saying it doesn't work anymore. Twrp has been updated to work perfectly.
I recommend magisk over SuperSU. Stable not beta.
Or you can extract the boot.img from the stock firmware image and patch it with magisk manager if you want to keep stock recovery for whatever reason. You can flash the patched boot.image with fastboot.
madbat99 said:
Same simple instructions as for all Nexus.
Unlock bootloader.
Fastboot flash twrp
Use twrp to flash root solution (SuperSU, magisk, etc)
https://forum.xda-developers.com/ne...ll-custom-recovery-root-t3200361/post62804370
All steps work, just need updated files. Like newest SuperSU or Magisk. Search of forum will work. Twrp link is fine. Don't worry about the posts in that thread saying it doesn't work anymore. Twrp has been updated to work perfectly.
I recommend magisk over SuperSU. Stable not beta.
Or you can extract the boot.img from the stock firmware image and patch it with magisk manager if you want to keep stock recovery for whatever reason. You can flash the patched boot.image with fastboot.
Click to expand...
Click to collapse
I have tried this method many times now and the tablet is not rooted. Looks like TWRP gets wiped every time I reboot?
Is there a new way to root the Nexus 9? Noone seems to have an update version?
relic said:
I have tried this method many times now and the tablet is not rooted. Looks like TWRP gets wiped every time I reboot?
Is there a new way to root the Nexus 9? Noone seems to have an update version?
Click to expand...
Click to collapse
Flash TWRP, then select reboot>recovery. Then TWRP should stick
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!
I have a pocophone f1 which I attempted to root.
I already unlocked it using my MI account with MI unlocker on windows.
I installed TWRP 3.2, as well as SupersU.zip in TWRP.
I go and check root access using various root checker apps from playstore but i have no root access. One of them says that my supersu $Path does not contain a binary.
I tried uninstalling superSu using the supersSu uninstaller.zip in TWRP and then attempted flashing magisk, but i got the error about patched boot image. I wiped everything and then flashed stock global ROM for miui 11. Still i get the patched boot image when trying to flash magisk.
Any ideas?
Follow this
Silvershot said:
I have a pocophone f1 which I attempted to root.
I already unlocked it using my MI account with MI unlocker on windows.
I installed TWRP 3.2, as well as SupersU.zip in TWRP.
I go and check root access using various root checker apps from playstore but i have no root access. One of them says that my supersu $Path does not contain a binary.
I tried uninstalling superSu using the supersSu uninstaller.zip in TWRP and then attempted flashing magisk, but i got the error about patched boot image. I wiped everything and then flashed stock global ROM for miui 11. Still i get the patched boot image when trying to flash magisk.
Any ideas?
Click to expand...
Click to collapse
Just uninstall SuperSU root and root again with magisk! There is unroot option in the SuperSU app which you have to use or:
https://forum.xda-developers.com/showpost.php?p=63615067
@Silvershot
My POV: Noone needs to install TWRP to root phone's Android.
jwoegerbauer said:
@Silvershot
My POV: Noone needs to install TWRP to root phone's Android.
Click to expand...
Click to collapse
i just followed a tutorial on xda. what simple method do you know to root a poco f1? i need root urgent
abhi_tech said:
Just uninstall SuperSU root and root again with magisk! There is unroot option in the SuperSU app which you have to use or:
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
thanks for your reply. I already mentioned i used the supersu uninstaller.zip from the link you provided. but magisk still says the boot image is patched...
Silvershot said:
i just followed a tutorial on xda. what simple method do you know to root a poco f1? i need root urgent
Click to expand...
Click to collapse
It's clear that something has gone very wrong. Instead of wasting time with troubleshooting, I recommend that you restore the phone to its original state via re-flashing its Stock ROM and when that's done retry to root its Android the proper way.
FYI: Once TWRP got installed on phone, you can't get rid off of it unless you re-flash phone's Stock ROM.
jwoegerbauer said:
It's clear that something has gone very wrong. Instead of wasting time with troubleshooting, I recommend that you restore the phone to its original state via re-flashing its Stock ROM and when that's done retry to root its Android the proper way.
FYI: Once TWRP got installed on phone, you can't get rid off of it unless you re-flash phone's Stock ROM.
Click to expand...
Click to collapse
i flashed stock rom. i already said it.... still the problem exists
Silvershot said:
i flashed stock rom. i already said it.... still the problem exists
Click to expand...
Click to collapse
If you flash phone's Stock ROM then neither Magisk nor TWRP is existing , you can't run either of them ...
jwoegerbauer said:
If you flash phone's Stock ROM then neither Magisk nor TWRP is existing , you can't run either of them ...
Click to expand...
Click to collapse
yea, i flashed stock rom, then installed TWRP.
i will now flash stock rom again. i wiped everything using TWRP first.
could you tell me what to do once i flash stock rom again?
i attached a screenshot of trying to flash Force Encryption Disabler V4 for Magisk 18. even the disabler doesnt work... please someone help! i am working with stock clean rom. what is going on
0
Silvershot said:
could you tell me what to do once i flash stock rom again?
Click to expand...
Click to collapse
I could but I don't want to: IMO you simply didn't get it - you do anything without questioning the meaning.
Happy fiddling around with Magisk etc.pp.
jwoegerbauer said:
I could but I don't want to: IMO you simply didn't get it - you do anything without questioning the meaning.
Happy fiddling around with Magisk etc.pp.
Click to expand...
Click to collapse
why are you on this forum if you dont want to help? i explicitly said i tried both supersu and magisk. or how can i root without these 2? why do you say i didnt get it? im pretty sure i did the steps correctly
Silvershot said:
why are you on this forum if you dont want to help?
Click to expand...
Click to collapse
ROFL
BTW: Being active in this forum does not force me to give help in every case. Accept it.
Seppppx said:
You don't have to disable encryption to use magisk. Atleast I think from my experience.
This is the step-by-step tutorial.
1. Flash this global stock miui with TWRP. https://c.mi.com/in/miuidownload/detail?device=1700355 (if this is not the official ROM please correct me, there are a lot of fakes there)
2. Flash Magisk with TWRP. Download and flash it from this github repo. DO NOT DOWNLOAD IT FROM ANYWHERE ELSE!
https://github.com/topjohnwu/Magisk/releases
3. Reboot
Click to expand...
Click to collapse
thank you. this worked. i was using older version of magisk. the latest one did the trick.