I've tried asking this question on other threads but no one is replying.
I have installed the official OOS4.0 through TWRP. I was on a CM13 ROM so I flashed the full 3.5.4 zip and then the 4.0 OTA directly after. Then I flashed SuperSU but I guess it didn't work because I don't have root access.
Now I lost access to TWRP as well. So I tried to reflash TWRP through my Mac and though the process runs smoothly, whenever I boot into recovery, it's still stock.
Is there anything I can do to regain TWRP access through a MacBook?
Related
Hey everyone
I've been using the XT1053 Retail US Stock Lollipop Flashable ZIP without issue for quite a while, but decided to update to the modded version 2. So I flashed it, xposed, and supersu again. Booted up, everything was okay. But then it said I needed to update my supersu binary and that I didn't have root, so I went to reboot into recovery and flash supersu once more.
However, now I can't access TWRP and it merely says "no command"
Should I just try installing TWRP again or is there a way to see if it's still installed? It's weird that this happened after flashing a rom
edit: reflashed twrp recovery img, back to normal. Can't explain what caused this though
Hello all,
I have recently been asked to use email on my work phone (instead of my preferred web-app option). My device (S4 i9505 running a Cyanogenmod 12.1 nightly) was/is rooted but after the (standard) encryption process the phone was stuck on a black screen/bootloop/problem.
This was resolved by re-flashing the CM 12.1 rom using TWRP which booted and the device was encrypted with my work email on the phone. SuperSU is installed but the binary needs to be updated and the phone is saying it's not rooted when checking the root using Root Checker.
I want to reinstall/reinstate SuperSU, but I am wondering if this will freeze the phone again, as it is encrypted. What are the known problems with rooted phones/SuperSU and encryption?
Cheers
Solved
Hi all,
Solved it by simply flashing the latest SuperSU zip via TWRP in recovery. It seems that you can use a rooted phone with encryption enabled. However, when I encrypted it (via the standard way) it was stuck in some kind of bootloop problem where the screen was black but the phone was on. To solve this, I presume the problem was with SuperSU. I would first make a backup of your ROM before encrypting then I would temporarily disable SuperSU, or uninstall it, then encrypt the device. Afterwards re-enable or re-flash SuperSU from recovery. If you do get a boot problem, you can flash a ROM or recover your old one and start again.
My steps were: encrytp, then got the boot problem so I flashed a new CM 12.1 nightly. Afterwhich the phone booted normally and the phone was encrypted, but "not" rooted. I then downloaded the latest SuperSU zip and flashed it from the recovery leaving me with an encrypted, rooted phone.
By the way, encryption is annoying as you must enter a pin everytime you use the phone, after it is locked. My S4 only lets you use a pin, no pattern allowed. However, it is preferred by employers/IT.
Hi all,
First of all i am not noob to flashing roms and kernels. I have been flashing rom/kernel since 2011 on different phones. But i never encounter this type of problem. On my N6 i cant get root on my stock rom(not debloated rom by tupac4u).I have tried different supersu zips(2.78, 2.78 SR3 and SR5) but no luck. What i did, went to recovery wipe everything except internal storage, reboot to bootloader, flashed latest factory image( which is NDB91P), setup my device, reboot into bootloader to flash recovery(because you loose twrp when you flash stock images), then flashed SuperSu (tried every versions) and i always get bootloop. Am i missing any step??
OOS 4 just rolled out in Italy so I'd like to update asap, but I can't lose root privileges or twrp. What's the fastest way to do this?
Thanks
Update TWRP to 3.03-1. download the OTA and latest supersu and copy to phone.
Boot I to recovery flash OTA. And supersu then reboot
I followed links in this article
https://www.xda-developers.com/oxygen-os-4-0-2-and-new-open-betas-released-for-the-oneplus-3-and-3t/
Just reflashed 4.02 and instead of SuperSU installed Magiskv10 so can say this also works
Ok guys I figured it out, it simply has been a while since I last flashed roms...
I only dirty flashed 4.0.2 zip over 3.5, then flashed supersu again.
Everything good
Thanks guys!
I have a oneplus 3t and am on OOS 4.0.3 and decided to upgrade to OOS 5.0. I downloaded the ROM, took a backup and then clean wiped my phone. Then I tried installing the ROM but it failed. So I decided to restore my backup from USB OTG. While restore failed and it showed error 255 while restoring data, so I wiped again and then restored everything except data. The phone rebooted and everything is fine except the phone is not detecting my sim card. I have tried restoring again and rebooting but it didn't work. I am using twrp 3.1.1
Please give a solution or tell me which ROM version to flash to solve this problem.
Just follow this guide to get back to factory default. And then try OTA update with the default recovery instead of TWRP.
https://www.google.se/amp/s/forum.x...ck-unbrick-tutorial-oneplus-3t-t3515306/page1
You need a special TWRP in order to upgrade to Android Oreo. Just google for Oneplus3 Oreo TWRP and theres a OnePlus-Forum Thread where you can download the TWRP that is needed for the Oreo Upgrade. Your Backup should work without Problems after you installed Oreo
just install bluSpark TWRP v8.61 from
https://forum.xda-developers.com/devdb/project/dl/?id=27655
and download official 5.0.1 ROM zip file from oneplus official site.
then you can proceed. You can use Magisk 15.3 after ROM installation for root access.
Make sure to reboot TWRP once after wiping everything from TWRP otherwise you may lose TWRP where stock recovery may take place.