Purchased a Tab2 T713 last night. I powered it up and let it update to nougat.
The I installed TWRP 3.1.0.1 for T713 using ODIN.
Booted into TWRP and Installed SuperSU and no-verity-no-encrypt_ashyx.zip.
Rebooted into system and loaded my user apps from a Titanium backup all was working well.
Rebooted into recovery using Quickboot app.
I made a nandroid backup in TWRP and wiped Davlik and Cache.
When I try to reboot from TWRP, If I choose "System" it boost back to recovery mode and I'm back in TWRP.
If I choose "Power Off", the S2 turns off, but when I turn it back on, it boots back to TWRP recovery
Edit. Even choosing the Reboot - Power off option cause it to reboot into recovery
Second Edit. Found the answer in the TWRP forum. Seems you can't use a reboot App with 3.1.0.1 and S2. Solution was to reflash TWRP using ODIN
Lenster45 said:
Purchased a Tab2 T713 last night. I powered it up and let it update to nougat.
The I installed TWRP 3.1.0.1 for T713 using ODIN.
Booted into TWRP and Installed SuperSU and no-verity-no-encrypt_ashyx.zip.
Rebooted into system and loaded my user apps from a Titanium backup all was working well.
Rebooted into recovery using Quickboot app.
I made a nandroid backup in TWRP and wiped Davlik and Cache.
When I try to reboot from TWRP, If I choose "System" it boost back to recovery mode and I'm back in TWRP.
If I choose "Power Off", the S2 turns off, but when I turn it back on, it boots back to TWRP recovery
Edit. Even choosing the Reboot - Power off option cause it to reboot into recovery
Second Edit. Found the answer in the TWRP forum. Seems you can't use a reboot App with 3.1.0.1 and S2. Solution was to reflash TWRP using ODIN
Click to expand...
Click to collapse
Did supersu install systemlessly? If it did, your gonna have problems because of the safety net api.
Just has same thing happen last night, got error on boot about security and had to wipe. Any link to an easy how to root a T713?
Related
I had cm12.1 on it and only wanted to clear settings in android.
It had to reboot and stuck at twrp begin screen that keeps flashing.
Only odin works now and tried installing another twrp and cwm too, all succesfull but still that twrp boot logo flashing even when cwm installed.
Normally i can manage but have no idea now. If recovery worked it was fine but just thru odin seems that twrp is write potected almost.
Any clues someone
rebooted manually also, uncheckedauto reboot box after flashing twrp new rom
nothing, still stuck
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 was rooting a device for the first time, a new tablet SM-T385i. I got twrp and installed it using Odin(AP). From there I could boot into twrp recovery. I put the Supersu file into my downloads folder and booted fro the first time into twrp. I couldnt find any of the file folders in the install section so I went to mount and checked system. Still nothing. I tried to check data but didnt work. i panikced and went to reboot system. It got stuck on the boot screen over and over, showing the samsung logo. then i booted into twrp and wiped the data. Then i reinstalled twrp and i could see my tab on my pc now. Put supersu again and flashed with twrp. iT SAID MIGHT TAKE SOME TIME BUT then it just switched off. i TRIED TO BOOT INTO TWRP BUT FAILED. i went to the downloader again and installed twrp again. still shows the boot logo and switches off again. at this point i can go to the downlader and i can see the logo thats all. HELP!!!!!!!!!!!!!!!!
Search your rom/other one (custom OS) and install it via TWRP. After that (when your rom booted normally) - try to install Magisk.
https://forum.xda-developers.com/showthread.php?t=3747480
Sent from Redemi 4X (Resurrection Remix based on OS 7.1.2)
Any ideas? It just give me an error 1. Tried several versions and still the same problem.
Is it not needed anymore?
After installing the rom or magisk you must restart from the twrp in recovery mode and voila, you can install. in fact I cannot install 2 things in a row, I must install 1 at a time, restarting in recovery mode
17007501 said:
After installing the rom or magisk you must restart from the twrp in recovery mode and voila, you can install. in fact I cannot install 2 things in a row, I must install 1 at a time, restarting in recovery mode
Click to expand...
Click to collapse
Tried it several times. Wiped cache etc and restarded the phone. Nothing helps.
Try this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
17007501 said:
Try this https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
Click to expand...
Click to collapse
EDIT: Nope Flashing was fine but after the reboot i get a bootloop with only mi logo showing.
So now what?
you can try entering twrp, format data and flash dm
17007501 said:
you can try entering twrp, format data and flash dm
Click to expand...
Click to collapse
Nope. Not working
Use LR twrp, there's "script" file
Boot into recovery
Format data, keep in recovery
Transfer script and flash
Reboot to recovery
Transfer ROM, GAPPS, Magisk, and script
Flash ROM, GAPPS, then script
Reboot to recovery
Flash Magisk then script
Reboot to recovery
Format data, keep in recovery
Transfer script and flash
Reboot to recovery
Reboot to system
I actually had the same error. instead of booting, I flashed the LineageOS ROM I wanted to load and it worked fine.
Perhaps some phones do not have this check ? For me it's a Galaxy S9. I have TWRP 3.5.x now and LineageOS 18.1 and no message of knox tripped or anything yet. Not rooted yet though
Hi,
After I try ti upgrade magisk from magisk manager app my smartphone not enter in recovery mode.
It stucks on Android logo.
I am able ti reboot in normal mode and bootloader mode.
Ant solution?
You have unlocked bootloader? TWRP installed? Official Magisk or Magisk Canary installed? Where does it stop booting? On the yellow realme logo? Adb installed on your PC?
I had this problem with last Magisk version update twice. It has cost me 3 days of hard work and partial data loss. Since then I do not anymore update magisk trough it's own internal update function. Moreover, I do not update it at all as long as the phone is running. From this I learned: Never, never and never again update or change something on a realme phone without having made a Nandroid backup. I know it's too late now for your problem. We may solve it, but it might end up in formatting data, and loosing everything you have no backup.
I have nandroid backup. I think to uninstall magisk and try sgain ti flash twrp. I don't want loose data.
I am unlocked bootloader
It stucks in green Android logo when I try to reboot recovery
Orange Fox twrp installed
Magisk canary installed
Ok then first reinstall TWRP through adb. Then, if your nandroid backup includes Data, what it normally does, then I would just reload the backup.
First reinstall stock recovery.img from fastboot rom, search on xda, then install Twrp you want and enjoy.
Solved thank you guys