*UPDATE* - $20 for the first solution that does not require clean flash.
I'm having trouble regaining root after a dirty flash ROM upgrade (PureNexus on Nexus 6P). The ROM updated fine. I noticed I had lost root so tried to reinstall SuperSU from Android. When that did not work I flashed it from TWRP. Then device then got stuck on boot animation. After that I tried many things -update the boot.img to NBD91K (this one), updated TWRP to 3.0.2-3 and updated SuperSU (immediately after updating TWRP) to 2.78. Still stuck on boot animation. I probably left it on boot animation for at least 30 minutes. I had also installed suhide so along the way of troubleshooting I uninstalled that. I certainly hope to recover without a full ROM clean install. I do believe I got a successful back up somewhere along the way from TWRP but is was post ROM update.
Any advice (other than full wipe and clean install) greatly appreciated.
This solved it!
Blindfold_NL said:
- reboot in recovery
- reinstall ROM
- Install latest vendor image
- Run uninstall suhide script
- in TWRP file manager removed su folder
- restart (booted normally)
Click to expand...
Click to collapse
Related
Hello out there,
my problem is a bit annoying. Everything is fine if I use my OP3T with Oxygen (4.0.3) and TWRP (3.0.3-1). But I want to use LineageOS with TWRP and cant, because my TWRP isnt working after flashing lineage.
"Normal"-Setup:
- TWRP 3.0.3-1
- Oxygen 4.0.2 or 4.0.3 (doesn't matter)
- supersu 2.79
- Encrypted Device
"Lineage"-Setup:
- TWRP 3.0.3-1
- lineageOS (lineage-14.1-20170214-nightly-oneplus3-signed.zip OR lineage-14.1-20170208-nightly-oneplus3-signed.zip - tried both, doesnt matter)
- supersu 2.79
- openGApps for 7.1 nano
- Encrypted Device
My Problem is, that I can boot up lineage and use it, but if I reboot into my TWRP to flash something or make some Backups, it asks for my encryption-passphrase, it says it is okay and boots into the twrp main-windows. After that I can't touch anything (stuck in mainmenu) and after a few seconds it results into a black screen (plus white LED) and I am forced to reboot the device. After that reboot I have to reconfigure lineage (seems to loose data).
Does anyone have an idea how to fix this annoying "bug"?
Thank you very much!
Atomique
EDIT: I found that Thread after searching for a issue like that in the lineageOS official Thread - I will try this and report! - Thank you! https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
I had the exact same problem when I hab LineageOS installed! It would always lose all its data. After flashing and reflashing a hundred times, I ended up reverting my OP3T back to stock using a OnePlus forum guide (I'm a new user, so I can't post the link). I am now back to OOS 4.0.3 but can't even get SuperSU to work. Whenever I flash it (with or without the dm-verity fix) the phone is stuck booting forever.
I found the post you linked to aswell but haven't tried flashing LineageOS using the new TWRP. But I can tell that the new version doesn't help rooting OOS...
Did you have any luck flashing LineageOS by now?
Edit: With the newest Lineage Version I always get an error when trying to flash it. Do you have the same problem? The nightly from two weeks ago seems to work better.
Use latest TWRP 3.0.4.1
nitinvaid said:
Use latest TWRP 3.0.4.1
Click to expand...
Click to collapse
That's what I'm doing... Could the dm-verity be a problem? There are two versions, one with opt and one with force in the name.
Thank you for your replies! The link (TWRP 3.0.4-1) worked like a charme!
@Tafelbomber: I would recommend you to start from scratch. But please be warned: you will loose your data! Make a backup first!
1. Delete everything with fastboot -w
2. Flash the recovery noted in my first post with fastboot flash recovery <twrp-filename.img>
3. Optional: Restart into the TWRP and flash the OOS 4.0.3 to make sure that you have a clean OS installed befor flashing lineage
4. Flash lineage OS + additional ZIPs (like supersu, betterbatterystats, Gapps etc)
5. Clean Dalvik and Cache!
6. Reboot and have fun. --> Sometimes you get problems with the encryption chain (Red Error --> in my case the fastboot -w did it for me)
Good luck - I will close this thread - thanks again for your help!
Atomique
EDIT: I want to close this thread, but I don't know how.
I have a stock Oneplus 3T, updated to 4.1.3. I wanted root access to allow Cerberus more control.
So I followed the Oneplus 3T root guide by "Theunlockr" .com
I downloaded:
TWRP v3.1.0-1-oneplus3t.img
SuperSU v2.78 SR5
No-Verity opt encript v5.1
I followed the instructions as closely as I could, I installed the TWRP and cleared the phone (that booted normally),
Then I went to flash SuperSU and No-Verify, cleared the cache, restarted and my phone, and It didn't boot, the red dot logo animation would just play on a loop, I left it for an hour because it did warn me that it would take a while.
When I was satisfied that it wasn't going to start, I restarted it a couple of time, no-dice.
I also tried flashing a more up-to-date SuperSU. (v2.79), still didn't work.
So, now I've gotten myself further stuck, I flashed the stock recovery back onto the phone and decided i wanted to flash the Open Beta 5 OS.
But now when I go into recovery (stock), I can't connect to ADB properly.
I click " Install from ADB " - I've been using this, but it only seems to allow Sideload, but If I try to sideload it, it tells me it can't read the ROM.
So I changed ADB versions to the ones from mfastbootv2.
and now it says "error: protocol fault (no status)",
I can't use the push command because it just says "Error: closed"
So I'm kinda stuck for what I can do from this point forward to get my phone working again...
Android Debug Bridge version 1.0.31
Any suggestions?
Thanks for your time
Evan
There's so many different builds of SuperSU that it's getting hard to keep track of which one works. I know that flashing an older version does tend to cause endless boot animation. SuperSU 2.79 should work, though you'll likely need to dirty flash OOS again before flashing it.
I've also found ADB to be rather finicky in recovery. My advice is to use an USB OTG adapter and load any files that you need on a flash drive. Afterwards, follow these steps:
1) Boot into fastboot and flash TWRP again using your PC and fastboot commands
2) Download whatever version of OOS you want (stable or open beta) and somehow load it onto your phone, whether through ADB or USB OTG
3) Boot into TWRP and flash the OS that you've downloaded, wipe cache/Dalvik. You can clean flash if you want, though dirty flashing should suffice in this situation.
4) Flash either SuperSU v2.79, or Magisk v12.0. Both Magisk and SuperSU will root your phone, I just prefer Magisk due to its extra capabilities and more straight-forward development.
5) Reboot, the rebooting process shouldn't take more than a few minutes.
Using a flash drive also has other benefits, you can save nandroids directly onto it through TWRP. This both saves space in internal storage and keeps the backups safe in the event that your phone gets inadvertently wiped from any unforeseen incidents.
Additional notes:
-You don't need to flash the no-verity.zip if you flash either SuperSU or Magisk, both of them contains the necessary scripts
Fantastic!
Thanks a ton, that solved my issues completely.
So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0
I just managed to (after spending 2 days figuring this out) get TWRP recovery in my old Xperia Z2 that had android version 6.0.1 Marshmallow. Currently running TWRP 3.0.2-0 (idk if it matters), bootloader is also unlocked. Was installed with SuperUs, and cleaned from it completely. But it never gave me the option to restore back to boot img.
I've been browsing the forum, trying so many solutions but nothing has worked yet. Any help would be appreciated ASAP. And I cant currently access the logs, BUT I have manually written down what the log is and I have no idea what to make of it.
I looked at BootBridge but the explanation is confusing me. So I flash Magisk through another service or whatever to make it able to get flashed? I dont have any other img's or anything to replace the boot partition with, so I got no clue what to do.
* Magisk v17.1 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p14
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Sony ELF32 Format detected
- Please use BootBridge from @AdrianDC to flash Magisk
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/MAGISK/Magisk-v17.1(1700).zip'
Updating partition details...
...done
Edit: I dont have a img backup of the old rom, unfortunately
Alright, a break made me realize how it works. But the bad news is that my phone is now in the boot loop haha. If anyone have additional information on how this all works, that would be appreciated
Another update, now I could uninstall and reinstall magisk in TWRP without failure, but I still get stuck in boot loop so it doesnt work obviously
Another Edit: If I do manage to factory reset the phone back to its original software, is it possible to do a better setup this time and create a good backup? Since SuperUs didnt allow me to backpedal to an earlier state
Alright managed to restore and once again flash my phone so that I can use TWRP, but im still locked by BootBridge looping my phone in bootup, when trying to install magisk v17.1
flash stock ROM
abkdmn said:
flash stock ROM
Click to expand...
Click to collapse
Managed to get it to work! Made a custom ROM from a stock version after it being patched to disable RIC. Now the only problems I have, is to get Magisk working correctly so that I can get away and pass SafetyNet
Have unlocked your bootloader?, If yes then ave you tried boot bridge by adrianDC to flash magisk successfully ?
Leave some additional information like : your ROM version, twrp version, phone model.
If you want to restart to new in order to use a custom ROM or Stock ROM with magisk and bypassing safety net leave details about those ROMs and files which you are going to use.
So, i updated magisk (version 21? EDIT: manager was set to upda te to beta, but 20.4 also bootloops :/ ). Before rebooting, also installed to inactive slot, cause.... If you can do it after a OTA update, why not doing it normally, right? Bootloop. Have to press both the power button and VOL up for it to turn off. Usually just the long press on power buttton would do the trick.
Oneplus 7T OOS 10.012 EU
SOLUTION for the bootloop:
- Installed TWRP 3.4.0.2
- Because it cannot access data partition nor transfer files via USB, i did adb push -p local-pc-file-here /tmp
- So, i installed OOS 10.0.13 from there and it booted fine, however without magisk even tough i installed it from /tmp as well right after the ROM install without reboot.
- Tried to reinstall magisk from TWRP (had to reinstall it too, as OOS deleted it), but it bootlooped again. So, i'll wait for a boot file with it.
Executing Magisk-uninstaller-20201003.zip on TWRP did NOT work, cause it couldn't mount the necessary partitions.
EDIT: I have no magisk modules, so i don't know why all of this mess :/
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Allen77777 said:
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Click to expand...
Click to collapse
Gotcha! All good now. BTW, if anyone needs, there's a patched boot file on 7T's forum for 10.0.13 EU.
I have the same issue with 10.0.13 HD65AA.
First I tried to do the full update like usual with installing Magis 21 into both slots before reboot but then I got stuck on the boot animation.
Tried a lot of things until I found this thread here. Once I got into TWRP I pushed the latest ROM over to the phone and installed it and I could get back into my phone again. But once I tried to install Magisk via TWRP or boot the patched image for 10.0.13 HD65AA from XDA I get stucked in the boot animation again. So I had to once again push the ROM to the phone and install it into the second slot and once again my phone boots again.
So for whatever reason there is an issue with Magisk and both 10.0.13 HD65AA and HD65BA. So at least for me for now no root.
Thank you very much for at least getting into my phone again without losing any data. :good: