Can I use fireflash to update TWRP whilst using cm12.1 ROM?
I suppose you could, since FireFlash is just an app to flash files outside of recovery, pretty much like flashify. Although, in my experience, i've never updated my Kindles TWRP as i've never seen the need to, but i did update my Samsung Galaxy Tab 3 TWRP from like 2.5 something to 2.8.6.0 by just flashing a zip like normal and then instead of rebooting to system just reboot to recovery again and everything has worked fine with it. Although if you're adamant about doing it through fireflash i'd assume you could.
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
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Aqua1ung said:
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Click to expand...
Click to collapse
https://dl.twrp.me/zeroflte/
datdirtyscrew said:
https://dl.twrp.me/zeroflte/
Click to expand...
Click to collapse
Thank you! One of the things that I find irritating about TWRP Manager is that it asks me to confirm/verify the partition where TWRP gets flashed to. Now how can I possibly know if dev/block/platform/15570000.ufs/by-name/RECOVERY is the right place for my device? (Is it?) The second thing that bothers me about TWRP Manager is that it doesn't correctly detect the latest TWRP version, and often it offers to install an older version.
Did twrp-2.8.7.2-zeroflte.img.tar work for you?
After updating to DOI1, I get boot loops after trying to flash TWRP.
I can get into recovery and download mode just fine, but it won't boot to the OS.
RiskPrime said:
Did twrp-2.8.7.2-zeroflte.img.tar work for you? After updating to DOI1, I get boot loops after trying to flash TWRP. I can get into recovery and download mode just fine, but it won't boot to the OS.
Click to expand...
Click to collapse
I bit the bullet eventually (sesing as flashing TWRP via ODIN is a PITA), and flashed TWRP using TWRP Manager. I got an error message upon flashing, though it looks like TWRP flashed just fine. (Go figure!) Anyway, TWRP Manager flashes TWRP 2.8.7.1. It may be that TWRP people didn't consider TWRP 2.8.7.2 safe enough to flash, which is why TWRP Manager doesn't offer the option. That may be your explanation for your troubles.
I just unlocked my bootloader, and rooted my Nexus 6, and installed TWRP 3.0.0 using the Nexus Root Toolkit.
I just installed Adaway, and unrooted it, cus I use a lot of banking apps.
But the question is, when I want to re-root it, could I just flash supersu zip with the custom recovery and that's it?
or do I have to do the root process all over again?
I remember using TWRP 2.8.6.0 on the oneplus one, and when I rebooted it from the custom recovery, it said something like
'It seems like supersu is not installed would you like to install it?' or something like that.
and 'yes' would re-root it, that simple.
it seems like TWRP 3.0.0 doesn't have that.
Thanks
You don't really want to try to root using the built-in option in TWRP - with the newer Android builds (6.x), that won't work - you need to use the current version of supersu that modifies the boot img - I prefer the systemless version.
Glad to hear that TWRP 3.x has removed the prompt for installing supersu.
You should be able to reroot.
I agree with the above, keep systemless root in twrp's readytoflash folder and boot into twrp and flash that zip as you need it.
Sent from my Nexus 6 using XDA Labs
I think I remember (but not sure) that I read that TWRP 3 is smart enough not to suggest the root option when SuperSU systemless is installed, whereas the older versions tempted unwary users to root their already-rooted device and screwed it up in the process. Smart piece of programming to remove the misleading option.
root > flash kernel (boot.img) and then supersu 2.68 (latest)
un-root > flash kernel
thats it
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
Hello everyone,
I recently wanted to root my galaxy tab s2 and install a custom rom on it to enhance performance, someting i've done before with my old phone where everything worked fine. So i used autoroot to root the tablet which worked fine and choose to install lineageos afterwards. i found a fitting version of lineage on their official website, installed twrp on my tablet and used it to install lineageos and GApps. However i did not unlock my bootloader using adb since i didnt have to do that back when i rooted my phone and i read on a forum that unlocking oem in the developer settings would be enough. This is where the problems start. After i installed the custom rom the tablet would try to boot into the os for a couple of minutes only showing a loading animation just to boot straight into recovery mode afterwards. In an attempt to fix the error i used odin to install a stock rom from sammobile on the tablet. However now it doesnt even boot into recovery anymore. instead it only shows the stock rom loading animation until the battery emptys. Though i can enter download mode from that position and then cancel it in order to reboot the device which enables me to enter recovery mode. Does anyone have an idea how i could boot a normal os again or is the device hard bricked? The only idea i have left is trying to install a new os from an sd card.
I have the same issue. I installed unofficial lineageos 16 to exynos 2015 t810. I have newest odin and twrp. Im wondering if i need to install or unlock the bootloader to get past the logo loop then recovery bootup after 5 minutes. I followed clean tutorials.
Update: i found this to try.
Quote:
Originally Posted by -beluga-
Hi, first of all thanks for the ROM. Unfortunately I am unable to get my T710 running properly with today's packages (it ran 15.1 so far)
- lineage-16.0-20191009-UNOFFICIAL-gts28wifi.zip
- addonsu-16.0-arm-signed.zip
- open_gapps-arm-9.0-pico-20191009.zip (some with nano or stock)
I am doing a full clean install every time (over 10x so far) but only get it to boot using the ROM alone. Any mod, such as addonsu, gapps or even trwp app cause it to show the Lineage boot screen for quite a while until dropping back into TWRP. Since there is a virtually infinite amount of permutations which versions to try - can someone who is successfully installed 16.0 with Gapps on a T710 let me know their version combination please?
Thanks.
pico-20191009 is giving problems with the 1009 build on my T810 too. Pico-20191006 and Magisk 19.4 are doing the trick for me.
Don't know about other combinations
BTW, it's advised not to install the TWRP app as it is known for causing bootloops on this rom.
Don't know for sure, but wiping internal storage before installing rom might be useful too.