Related
I am on ARHD 10.1, it keeps telling me there is a SU Binary update but if I tell it to install it just reboots to recovery and does nothing.
What is the correct method to update the Binary on the One?
Which Super User you have?
SU or SuperSU by Chainfire?
SuperSU - Same issue
Guich said:
Which Super User you have?
SU or SuperSU by Chainfire?
Click to expand...
Click to collapse
I am having this same issue: I have SuperSU. I just finished unlocking bootloader and flashing TWRP. Everything else remains stock.
I get a "The SU binary needs to be updated. Contine?". When i continue i get "If you have custom recovery like TWRP or CWM, that can be used to (try to) install the SU Binary. This is recommended for HTC devices. How would you like to install the SU Binary?"
When i select use TWRP/CWM it boots into recovery but i have no binary file (or i don't know where to find it). if i try the normal way it doesn't work.
(Cancel that!) it worked on the third try ... ? not sure what was different but it rebooted into recovery and updated fine. That inadvertently, it seems, fixed my wifi tether problem as well.
Emh, however...
Here there is the flashable zip of SuperSU...
same problem here but with Superuser, not SuperSu.
it tells me to update the binary but when i click "recovery" it reboots into twrp and nothing happens
kargy said:
same problem here but with Superuser, not SuperSu.
it tells me to update the binary but when i click "recovery" it reboots into twrp and nothing happens
Click to expand...
Click to collapse
Download the zip for superuser or flash the SuperSU
I'm also having an issue with the update, although i've managed to install v1.75 of SuperSU through TWRM, but now the handset force reboots about 10-15 seconds after booting up, every time. Any ideas?
kargy said:
same problem here but with Superuser, not SuperSu.
it tells me to update the binary but when i click "recovery" it reboots into twrp and nothing happens
Click to expand...
Click to collapse
When you are into twrp.
You go to the path /data/data/com.koushikdutta.superuser/files
There is a supersuer.zip, you flash these file and you have the su updated
wingnutz said:
I'm also having an issue with the update, although i've managed to install v1.75 of SuperSU through TWRM, but now the handset force reboots about 10-15 seconds after booting up, every time. Any ideas?
Click to expand...
Click to collapse
Can anyone shed any light on this? I ended up factory resetting the handset just so it was usable, so had a fresh rom installed, and now ive tried to update the binaries again, its still happening. Constant reboot loop, from the time the OS loads to reboot is ~20 seconds.
Any ideas would be greatly appreciated.
I am also stuck on this. Have just changed to ViperRom from Android Revolution and now when I try to back up using Titanium it states I am not rooted. Go into SuperSU and it states the binary SU needs to be updated. I am not getting a boot loop and I have followed all the steps but am not getting anywhere. Am I going to have to re-root?
Have got it working. Researched the problem seemed to be an an app called one tap cleaner. I granted it root access which what was causing the problem. Stopped giving it root access and went into TWRP and deleted all the SuperSU file and reinstalled SuperSU and all is good. Posted incase anyone else was having a similar issue.
I had the same issue. I tried it with the phone plugged into a charger and somehow that made it work.
I was having all the same problems with supersu. Once I had it plugged in and charging the install worked throught "normal" and my tether problem was fixed.:good:
mmm286 said:
When you are into twrp.
You go to the path /data/data/com.koushikdutta.superuser/files
There is a supersuer.zip, you flash these file and you have the su updated
Click to expand...
Click to collapse
I believe this is the right answer. Worked for me.
Thanks
Using the newest SuperSU ( not Superuser ) solve this problem for me.
Flash SuperSU using Recovery
Plugged In
Plugged In to charger and it worked, weird...but I'll take it
im actually having this same issue. ive got an LG G2 AND i just rooted it but for some reason when i go to start TWRP the android icone pops up then it just boots up again with out the issue being fixed. could someone possibly help. =(
Guich said:
Emh, however...
Here there is the flashable zip of SuperSU...
Click to expand...
Click to collapse
I've tried this before but it would just keep on saying "Installation Aborted."
ChristianAvi said:
I've tried this before but it would just keep on saying "Installation Aborted."
Click to expand...
Click to collapse
Strange.
If recovery will say installation aborted there is also a code error.
However, have you flashed latest, right?
Guich said:
Strange.
If recovery will say installation aborted there is also a code error.
However, have you flashed latest, right?
Click to expand...
Click to collapse
I dont know. I used Kingo App. Sometimes I also get this response: There is no SU binary installed. SuperSU cannot install it. This is a problem!
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
dadanepal said:
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
Click to expand...
Click to collapse
I can confirm that this process does work. It's the method I went through when I upgraded my Tab S.
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
ashyx said:
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
Click to expand...
Click to collapse
Thanks for the update. Are you going to keep up with every new SU updated binaries and update TWRP every time the binaries are update. That would be great if you are willing to do that. I rather rely on the actual TWRP and SuperSU Developers to give me the zips etc. and flash my self as long winded as that may seem but people can choose.
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue now.
Regarding cf-autoroot. I don't think people realise there is nothing special about how it roots.
It basically does the same thing that twrp does itself or flashing a super su zip.
Cf-autoroot simply installs a modified stock recovery which runs a script to Install root then flashes back stock recovery.
If someone intends to install a custom recovery anyway then there is no point in running cf-autoroot.
Twrp will do exactly the same thing and so does installing a super su zip.
They all accomplish the same thing using a slightly different method.
The only difference will be that chainfire may keep each cf-autroot updated with the latest binary.
The reason chainfire created it is for people who want to stick with stock recovery instead of custom
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
deno24 said:
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
Mode? Just load it and flash it.
Click to expand...
Click to collapse
ashyx said:
deno24 said:
Mode? Just load it and flash it.
Click to expand...
Click to collapse
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
deno24 said:
ashyx said:
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
That's the one.
Click to expand...
Click to collapse
ashyx said:
deno24 said:
That's the one.
Click to expand...
Click to collapse
cool so i flash twrp and ill have root? been a cpl oif years since ive done this last root was note2
Click to expand...
Click to collapse
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
ashyx said:
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
Click to expand...
Click to collapse
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
d3xtr0 said:
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
Click to expand...
Click to collapse
That's a feature of lollipop. It overwrites with stock recovery. Happens on many devices. You need to boot into recovery immediately after flashing twrp, twrp will then patch it so stock recovery can't replace it.
When flashing uncheck auto reboot in odin. When it finishes flashing hold power + vol down + home. As soon as the screen goes blank hold power +vol up + home to boot into recovery.
Thanks for the information, but now I've flashed your new package root+twrp and it's working great
Thanks again.
Sent from my MI 4W
Whith this method, what is the knox value?
Knox is one ( .. )
Newer thread opened yesterday.
Edit:
http://forum.xda-developers.com/showthread.php?t=3079488
[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805 [Tab S 10.5 ]
Sent from my MI 4W
I accidentally confirmed installation of SuperSU while trying to exit TWRP (I wish TWRP had an option to disable it) ;[
How do I uninstall it? As I'm unable to boot into my phone anymore((
a1exus said:
I by accidented confirmed to install SuperSU while trying to exit TWRP (I wish TWRP had an option to disable it) ;[
How do I uninstall it? As I'm unable to boot into my phone anymore((
Click to expand...
Click to collapse
hi a1exus
i've the same problem, uninstall supersu from its settings panel doesnt work at all... after the required reboot supersu is still there and installed as an system app.
im using a htc one m7. i need to remove supersu to install the OTA update.
any ideas on how to remove supersu?
kind regards
red1337
red1337 said:
hi a1exus
i've the same problem, uninstall supersu from its settings panel doesnt work at all... after the required reboot supersu is still there and installed as an system app.
im using a htc one m7. i need to remove supersu to install the OTA update.
any ideas on how to remove supersu?
kind regards
red1337
Click to expand...
Click to collapse
flash system.img
Sent from my Nexus 9 using Tapatalk
Try to install this zip through TWRP.
http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
@a1exus
thanks for your help.
Unfortunately I didn't made any backup befor rooting. But now I made a nandroid backup after updating to the newest version and before rooting
@Srandista
next time I'll definately try that script. I couldn't find that unSU script when I searched the interwebs. Thanks also for your help!
Kind regards
red1337
red1337 said:
@a1exus
thanks for your help.
Unfortunately I didn't made any backup befor rooting. But now I made a nandroid backup after updating to the newest version and before rooting
Click to expand...
Click to collapse
you can always flash stock image..
Sent from my Nexus 6P using Tapatalk
Srandista said:
Try to install this zip through TWRP.
http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Click to expand...
Click to collapse
I have to thank you, I was stuck on de boot logo, because i had the same problem that he says, and that file solved it.
I have a Moto X Play 6.0
Madvinv said:
I have to thank you, I was stuck on de boot logo, because i had the same problem that he says, and that file solved it.
I have a Moto X Play 6.0
Click to expand...
Click to collapse
Thanks for this. I had CM13 installed on my Redmi 2 and I flashed SUperSU ZIP through TWRP leading to booting error. Through the link shared by you and downloading file provided by @osm0sis I was able to get out of booting issue.
But problem is that now am stuck with no root access. Any idea how to renable it? I have CM13 and in developer options it is on.
Pls guide.
same issue and worst
hi
I was doing standard procedure to root LG4. Everything went ok until I uploaded the UPDATE-SUPERSU-v2.46.zip
Now, LG G4 don't boot anymore...
Until now I was able to boot into TRWP system doing adb commands but now since LG G4 stucks in boot my windows don't recognize the phone.
Am I totally screw?
Do you have any idea?
rubendob said:
hi
I was doing standard procedure to root LG4. Everything went ok until I uploaded the UPDATE-SUPERSU-v2.46.zip
Now, LG G4 don't boot anymore...
Until now I was able to boot into TRWP system doing adb commands but now since LG G4 stucks in boot my windows don't recognize the phone.
Am I totally screw?
Do you have any idea?
Click to expand...
Click to collapse
Does your LG G4 haven't got a key press combination to go to bootloader menu ?
Oooh wait first hit on Google search.
How to Boot into Fastboot Mode on LG G4 with the help of its Hardware Buttons:
First of all, turn off the smartphone.
Then, press and hold the Power and Volume Up keys at the same time for about 6 or 7 seconds.
Plug in the USB cable for your smartphone and connect it to your PC.
Release the keys only when the download mode is being displayed.
Same problem here! Nog able to het Root acces.(su binary not installed), so says Supersu. Probally because cm and Supersu Have a conflict. So how to delete the 'System' Supersu app?
benjg_ said:
Same problem here! Nog able to het Root acces.(su binary not installed), so says Supersu. Probally because cm and Supersu Have a conflict. So how to delete the 'System' Supersu app?
Click to expand...
Click to collapse
You have to use the clean up option in the app or remove the app manually through terminal or adb shell
Sent from my Nexus 5 using XDA-Developers mobile app
i had same problem before, I upload and install super Su in LG G4, turns into soft brick. I was only able to restore all android with kdz file via LGUP.
a1exus said:
flash system.img
Click to expand...
Click to collapse
how ican flash just system.img if ican using Odin3 v3.10
grep_i said:
You have to use the clean up option in the app or remove the app manually through terminal or adb shell
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
How can I remove the app manually? When I open SuperSU, it won't let me open it because SuperSU says something like "cannot install SuperSU" and quits.
Vegerot said:
How can I remove the app manually? When I open SuperSU, it won't let me open it because SuperSU says something like "cannot install SuperSU" and quits.
Click to expand...
Click to collapse
If you mean the app you can simply remove it by long pressing the icon.
When i install super su from twrp it does not install, but super su icon see on my phone, so that i try to un install but it does not open a pop up menu showing on the screen that is super su is not install and su binary need , so how to remove super su for my mobile
Deleted
Srandista said:
Try to install this zip through TWRP.
http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Click to expand...
Click to collapse
It worked. Thank you so much.:good:
Use Magisk Uninstaller
just flash the Magisk Uninstaller zip through recovery and done....
http://forum.xda-developers.com/attachment.php?attachmentid=3893658&d=1475527472
I've been getting "System update available" notifications for a while now, figured I might as well go through with it. But it just boots the phone into TWRP.
Is there a way to update a rooted phone?
You need a stock recovery to update Official OTA.
How do I get it? This and just flash it the same way I flashed TWRP?
Will I then have to flash TWRP again when I'm done? Do I need to back anything up before I start?
koberulz said:
How do I get it? This and just flash it the same way I flashed TWRP?
Will I then have to flash TWRP again when I'm done? Do I need to back anything up before I start?
Click to expand...
Click to collapse
yes you can use that. flash it like TWRP, boot phone and update. then flash TWRP again. DONE
Okay, so I've downloaded the stock recovery, gone into a command prompt window and typed:
fastboot flash recovery "M8_MINI_UL_Stock_Recovery_2.19.401.2.img"
Click to expand...
Click to collapse
Got an error about a missing DLL, and then a 'fastboot.exe has stopped responding' error.
Try to reinstall ADB drivers.
http://www.koushikdutta.com/post/universal-adb-driver
And I won't have to back anything up, yeah?
The other thing...the stock recovery is version 2.19.401.2, and the update it's trying to install is 1.18.841.4. Is that going to be an issue?
koberulz said:
And I won't have to back anything up, yeah?
The other thing...the stock recovery is version 2.19.401.2, and the update it's trying to install is 1.18.841.4. Is that going to be an issue?
Click to expand...
Click to collapse
backup is always a must just in case.
Recovery version as nothing to do with ota version.
tarx1000 said:
Try to reinstall ADB drivers.
http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse
I've done that, I'm still getting this error:
---------------------------
fastboot.exe - Unable To Locate Component
---------------------------
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
---------------------------
OK
---------------------------
koberulz said:
I've done that, I'm still getting this error:
---------------------------
fastboot.exe - Unable To Locate Component
---------------------------
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
get the drivers from here or install HTC sync.
Make sure you are in the right folder too. put all files in one folder.
Okay, that worked...but now I've lost root.
koberulz said:
Okay, that worked...but now I've lost root.
Click to expand...
Click to collapse
After official OTA you need to root again.
That wipes the entire phone, doesn't it?
If I'm going to be doing that anyway, is there a way I can update to the newest Android/Sense version?
koberulz said:
That wipes the entire phone, doesn't it?
If I'm going to be doing that anyway, is there a way I can update to the newest Android/Sense version?
Click to expand...
Click to collapse
the update does not wipe data but always do a backup just in case
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
koberulz said:
Okay, that worked...but now I've lost root.
Click to expand...
Click to collapse
the link i send you contains zip with super user. use TWRP to flash that instead of TWRP normal request. you can then update superuser via Google play
In TWRP, I went to 'install', then selected the SuperSU file, it did stuff, then came back with 'successful', I rebooted the phone...still no root. No SuperSU listed in my apps either.
EDIT: Flashed SuperSU 2.65 instead, and that worked, but the popups don't. Every time I do something that needs root access, it pops up a message asking if I want to grant that app root, and there's a timer, but none of the buttons do anything. Somehow Titanium Backup was still in SuperSU as allowed, and I got Root Checker to somehow go in as 'ask again' so I could manually set it to 'grant', but I can't get ES File Explorer root access at all.
koberulz said:
In TWRP, I went to 'install', then selected the SuperSU file, it did stuff, then came back with 'successful', I rebooted the phone...still no root. No SuperSU listed in my apps either.
EDIT: Flashed SuperSU 2.65 instead, and that worked, but the popups don't. Every time I do something that needs root access, it pops up a message asking if I want to grant that app root, and there's a timer, but none of the buttons do anything. Somehow Titanium Backup was still in SuperSU as allowed, and I got Root Checker to somehow go in as 'ask again' so I could manually set it to 'grant', but I can't get ES File Explorer root access at all.
Click to expand...
Click to collapse
have you try to update via google play? look like its a bit corrupted. try to update
I flashed the newest version of SuperSU, so there was no update. But after updating ES File Explorer, SuperSU works. Don't know if there's a connection though.
Is there a way I can get Marshmallow and Sense 7 on my device?
koberulz said:
I flashed the newest version of SuperSU, so there was no update. But after updating ES File Explorer, SuperSU works. Don't know if there's a connection though.
Is there a way I can get Marshmallow and Sense 7 on my device?
Click to expand...
Click to collapse
Marshmallow only with custom roms like cm12
Sense 7 no because HTC wont update mini 2 and there's no ports due lack of development in this phone
There was an update for Titanium Backup last night, and now SuperSU is broken again.
koberulz said:
There was an update for Titanium Backup last night, and now SuperSU is broken again.
Click to expand...
Click to collapse
:cyclops::cyclops::cyclops: try to flash via TWRP again.
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
Yiannis75 said:
i flashed the TWRP Recovery and flashed the SuperSU zip
Click to expand...
Click to collapse
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
Yiannis75 said:
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still
Click to expand...
Click to collapse
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Yiannis75 said:
Today, after i installed the latest OOS 5.0.1 with Android O 8.0, i decided to root my device.
After successfully unlocking the bootloader, i flashed the TWRP Recovery and flashed the SuperSU zip, i was stuck on the 1+ Boot logo. I tried fixing the contents through advanced options of TWRP recovery and still no luck. I also tried wiping my cache, data, dalvik etc...
So far i tried:
Installed stock recovery via fastboot, then adb sideload. My device was recognized when typing ADB Devices but when i tried to adb sideload ota.zip i got the cannot read *...zip* error. Then i tried everything i could find, my devices are installed correctly, i also tried the Large Address Awarness program and still no luck.
Then i flashed TWRP again through fastboot and try to do the same through TWRP's sideload. Still no luck
Then i tried to adb push the ota.zip so i can install it manually through TWRP recovery.. still no luck
I ran out of ideas.... What can i do?
Thanks in advance
Click to expand...
Click to collapse
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
Which exact version of TWRP did you install?
Are you Greek btw?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
Click to expand...
Click to collapse
You can verify by booting to TWRP. It says version number on the splash screen.
Did you look at, or try my recommendations in my last response?
redpoint73 said:
First of all, why didn't you make a TWRP backup of the stock ROM before trying to root? This is best practice before trying any mods (root, flashing ROMs) for reasons which are probably now obvious. I'm always surprised at how many folks skip this step.
Maybe you planned ahead of time to use the stock recovery image, if you had to. But since it wasn't on the phone when you need it, you're running into the problem of getting it on there now.
What version TWRP, and what version SuperSU?
Honestly, I would recommend Magisk for root, over SuperSU. I've seen a number of folks have problems with recent version SuperSU on this device. And Magisk has a lot of really cool, useful features. I'm normally not one to recommend one method over another. Especially since SuperSU was so tried and true for so long. But at this point, I see no benefit of using SuperSU, but many benefits to Magisk. And seemingly less problems rooting with Magisk. My recommendation would be current version Magisk, which is v16.0.
First of all, make sure you are using the "full" update zip (which will be >1 GB) and not the partial OTA "patch". You can get the full zip from here (Post #2): https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Since you have TWRP installed, boot into TWRP. You should be able to see your internal storage on your computer, just like it's a thumb drive. Just drag/copy and drop the full OTA zip onto the phone's internal storage. Then just flash the zip in TWRP.
The internal storage should be selected to "Mount" in TWRP by default. But if you can't see internal storage on your computer, make sure it's selected in the TWRP "Mount" section.
Click to expand...
Click to collapse
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse) ...thanks in advance
Yiannis75 said:
I did make a nandroid backup from TWRP i just didnt restore it because i thought it was TWRP’s issue due to dm-variety... my bad but whatever
Click to expand...
Click to collapse
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
Yiannis75 said:
Yeah i have read about Magisk i just didnt investigate enough to know exactly what it is was so i thought it would be better to go for SuperSU because thats what i used on every android device i has... my bad aswell here
Click to expand...
Click to collapse
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
Yiannis75 said:
About the full update zip.. i’ll try that because i think i was trying to sidelod the ota patch which was 1.6gb...(but still, is the “cannot read xxx.zip” related with what zip file do i sideload? Whatever ill try it when i get home
Click to expand...
Click to collapse
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Yiannis75 said:
And also i have already tried the mount feature of twrp recovery but my device just wouldnt show up on my computer.... I will try again later when i have the time and i will contact you if i need any help(if thats ok ofcourse)
Click to expand...
Click to collapse
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Yiannis75 said:
I believe i used TWRP 3.2.1-0... the very latest
And yeah am cypriot
Click to expand...
Click to collapse
Inta mou laleis??
Coming to Cyprus soon bro!
About your issue, use TWRP bluespark 8.61, just to be sure.
Never had issues with this version.
Unleashed by my rooted OP3T on 8.0
redpoint73 said:
TWRP and root shouldn't normally trip DM-verity (make the phone not boot).
I don't think it will hurt anything at this point to restore the backup you made. You're already trying to flash stock recovery, anyway (which is not that different).
If the restore is successful (phone boots to OS), then just flash Magisk and be done with it!
I wouldn't say it's "your bad". Magisk is just a suggestion or recommendation. Some folks have had success with SuperSU. But also seems like a lot more folks than usual, having problems (like no boot) with SuperSU than I'm used to seeing. And as I mentioned, I don't see any benefit of SuperSU (over Magisk) at this point. I was slow to change as well. But after trying Magisk, there has been no going back for me since. So therefore, the suggestion.
You didn't mention what version SuperSU, but 2.82 SR5 is recommended. It's in beta now, so if you used the "stable" 2.82 version, that might be the problem right there.
If it was 1.6GB, than it was the full update (at least one of them). I typed ">1 GB" so any OTA zip for this device greater than 1 GB should be okay. It's the OTA zips that are less than 1 GB that you need to watch out for, as it is not a full update, just a partial "patch" (don't flash on a modded device with TWRP or you will soft brick!).
I don't personally use sideload. While I see the convenience, I find it a bit messy. I've seen folks have problems with sideload, when simply putting the ROM on the phone and flashing with TWRP works fine (so in those cases sideload itself was the point of failure).
Now of course, getting the ROM on the phone is the problem, in your case.
Just post to this thread, and I'll see it. That is the best way to contact me. Good luck!
Click to expand...
Click to collapse
So, got home fixed the drivers so that my pc could recognize my device while on TWRP recovery, flashed the zip file through TWRP and it worked like a charm
Thanks for all the help bro
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
mannulko said:
Help pls
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
just like me, if u flash oos 5.0.2 from twrp u will be just fine. Just flash magisk instead of supersu like i did and all will be working just fine
mannulko said:
Hi my oneplus 3t is on Oreo 5.0.2. I flashed twrp recovery(3.2.1-0) nd super su root (v.2.82) but when I restarted the phone it's stuck on black screen with white oneplus logo.what should I do now?my phone is going into twrp recovery
Should I flash stock oos 5.0.2 from twrp recovery? Pls guide
Click to expand...
Click to collapse
If posting on a thread, related to your issue; it would make sense to actually read the responses in the thread. Since your question is already answered.
In short, you need to use SuperSU 2.82 SR5. The "stable" version 2.82 won't work, and will result in no boot. Or use Magisk 16.0.
If the phone still won't boot after (only) flashing the proper version SuperSU or Magisk; then flash the full stock update file using TWRP. Then flash the right version SuperSU or Magisk.