Related
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
egwktm said:
I have a rooted XT1068 and there is an official OTA update to 5.0.2, should I install it? Do I lose my root access?
Click to expand...
Click to collapse
You have to "Full unroot" in SuperSU settings and restore the stock recovery. Otherwise OTA will fail. After the OTA is installed, You can easily return to TWRP and flash SuperSU.
okay thanks! also instead of twrp could I use chainfire again?
Unfortunately, i tried to install OTA and now every time i turn on my phone it reboots and tries to install 5.02 only to get an error and it stays at twrp menu. So what can i do now?
lol after many reboots phone decided to tell me that update was unsuccessful so it works again.
more details pls for a beginner
I made the same mistake trying to flash OTA 5.02 over rooted device 4.4.4 . I got out of the loop by moving the download zip from system/cache to external sd...
just wanting to make sure I do all the right things and in order:
so in Super SU I go the FULL UNROOT
how do I then restore stock recovery?
Once I I have restored it what are the steps for the zip and install via stock recovery?
sorry about the boring questions - it's still a bit of a jungle for a beginner
egwktm said:
okay thanks! also instead of twrp could I use chainfire again?
Click to expand...
Click to collapse
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
dpdp73 said:
Will I be able to install ota updates with stock recovery and after unroot if I do changes to /system?
Click to expand...
Click to collapse
No
doppelhelix said:
Sure. But why? Twrp is superior in every aspect. It's like deliberately crippling your toaster so that only one slice fits.
Click to expand...
Click to collapse
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone? Some people therefore recommend the Chainfire CF-Auto-Root instead.
So after unlocking bootloader can I flash TWRP in fastboot mode and superSU afterwards without those kind of problems?
Wolfcity said:
Nice imagination.
But why do I often read that TWRP will be overwritten by Lollipop with custom recovery when rebooting the phone?
Click to expand...
Click to collapse
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
doppelhelix said:
It's a "feature" introduced by google for their nexus. I will quote the twrp website:
The stock ROM will automatically replace TWRP with the stock recovery. To prevent the stock ROM from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->File Manager. Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak
Or you flash the SuperSU.zip. That will prevent the override too.
Click to expand...
Click to collapse
Thx a lot for your explantion.
This was one of the things that irritated me right from the start when I was checking out the possibilities of custom recovery/root within 5.0.
I heard about the file-renaming thing but didn´t realize that superSu will do the job too and that it is a Nexus "feature" at all.
Helped me very much!
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
It is stock, updated to lollipop 6.0. I got the adb stuff on my pc to run cmds. All I want to do is root it for now. Every search I keep finding is not XT1064(other models show) or if it is, its not on lollipop or it is but not 6.0. I can't seem to find any for XT1064 already running on lollipop 6.0 that just simply needs to be rooted, no custom rom.
TWRP
Just flash by the bootloader the most recent version of TWRP (search for TWRP titan). And then, flash the latest SuperSU on TWRP recovery (search for SuperSU Beta).
Hope i've helped
blades_of_honor said:
It is stock, updated to lollipop 6.0. I got the adb stuff on my pc to run cmds. All I want to do is root it for now. Every search I keep finding is not XT1064(other models show) or if it is, its not on lollipop or it is but not 6.0. I can't seem to find any for XT1064 already running on lollipop 6.0 that just simply needs to be rooted, no custom rom.
Click to expand...
Click to collapse
XPS3Johann said:
Just flash by the bootloader the most recent version of TWRP (search for TWRP titan). And then, flash the latest SuperSU on TWRP recovery (search for SuperSU Beta).
Hope i've helped
Click to expand...
Click to collapse
Latest TWRP recovery for titan: twrp-3.0.2-4-titan.img https://dl.twrp.me/titan/twrp-3.0.2-4-titan.img.html
Latest stable superSU:SuperSU-v2.79-201612051815 https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
You have to flash SuperSU beta otherwise you'll be in a bootloop.
nilanko said:
You have to flash SuperSU beta otherwise you'll be in a bootloop.
Click to expand...
Click to collapse
Thanks, I tried flashing the latest stable supersu (2.79) and no luck. I flashed sr3 supersu and it worked so thanks
Thank you all! Finally got around to doing it. I used the beta SU as nilanko suggested. I ran a backup before trying SU(thank god I didn't forget!). I was stuck on the bootloader unlocked warning after doing it. At first I though maybe it just takes awhile the first time. So I went out for a smoke. Came back & it was still on the bootloader unlock warning screen still. I ran a restore through twrp & rebooted. Booted up fine now. I am wondering what happened exactly.
Only things I can think of is
A)The SU file was corrupted(something in it didn't download right when I downloaded it off my computer)
B)I put the SU file in the internal memory, not on the SD card. I thought it doesn't matter as long as you had the space on either.
SR3-SuperSU-v2.79-SR3-20170114223742 worked!:good:
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.
Just successfully installed Supersu 2.81 (2.81 because the guide I used said it's the most stable version) when my phone rebooted the playstore promted me to update Supersu so. being the clueless noob that I am I updated it. Now it keeps failing when it's trying to update binaries. I can still use supersu and still have root access though. It's just annoying seeing that message to update binaries.
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
fajner said:
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
Click to expand...
Click to collapse
I already fixed mine.
blitzball said:
I already fixed mine.
Click to expand...
Click to collapse
How did you fix it?
fajner said:
How did you fix it?
Click to expand...
Click to collapse
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
blitzball said:
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Sorry for late reply, I've tried uninstalling supersu/unrooting but neither did work or help. I finally ended up rebranding my phone to AL10 and installing the Chinese Oreo rom which works great.